Description
The term Network Service Provider (NSP) in 3GPP standards, referenced in documents like TS 23.435 and TS 24.302, denotes an entity that offers network connectivity services. Within the architecture of mobile networks, particularly from Release 8 onwards with the System Architecture Evolution (SAE), the NSP is typically the provider of external packet data network (PDN) services. The most common example is an Internet Service Provider (ISP). The 3GPP mobile network (the Public Land Mobile Network - PLMN) acts as an access network, providing the radio and core network connectivity that allows a User Equipment (UE) to reach the NSP's services.
The interaction is governed through the Packet Data Network Gateway (PGW in 4G, PDU Session Anchor in 5G). When a UE establishes a data session (PDN connection in 4G, PDU Session in 5G), it specifies an Access Point Name (APN). The APN is a reference that helps the network select the appropriate PGW/UPF and determines the route to the external NSP's network. The mobile operator's network authenticates and authorizes the UE's access to a specific NSP based on subscription data. The NSP itself is responsible for assigning the UE an IP address (often via DHCP), providing further IP-level services (like web hosting, email), and implementing its own policies for traffic within its domain.
In more advanced scenarios like network slicing, an NSP could be an enterprise leasing a dedicated network slice from a mobile operator. In this case, the NSP (the enterprise) provides its internal services (e.g., a private cloud application) over the isolated slice. The 3GPP standards define interfaces and procedures (e.g., in policy control - TS 26.941) to facilitate service interaction between the mobile operator's network and the NSP, ensuring proper QoS, charging, and access control.
Purpose & Motivation
The concept of the NSP is fundamental to the mobile data architecture, creating a clear separation between the access provider (the mobile operator) and the service provider (the NSP). This separation allows for a diverse ecosystem. A single mobile operator can provide access to multiple NSPs (e.g., the Internet, an IMS service provider, a corporate VPN), and a user can choose between them. This model existed before Release 8 but was solidified with the clean separation of control and user plane in the Evolved Packet Core (EPC).
Historically, mobile networks were walled gardens offering only operator-controlled services. The NSP model opened the network to third-party service providers, fueling innovation and the mobile internet economy. It addresses the limitation of the operator being the sole service source. The architecture allows the mobile operator to focus on providing reliable, high-performance access and connectivity management, while the NSP focuses on creating and delivering innovative IP-based applications and content. This division of labor is crucial for scalability and specialization in the telecom industry.
Classification
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (6 CRs across 4 releases). Complements the general historical overview above with the evidence-based evolution of this function.
Studied in Rel-8, normative work from Rel-16.
In Release 16, the NSP (Network Service Provider) function was newly introduced, enabling the NSCE server to act as an NSP towards a VAL customer with a service agreement relating to slice SLA. This introduction is part of defining the NSCE server's role, which can be deployed by various entities including an NOP/MNO or an Edge/Cloud Provider, and operates with policy harmonization to align VAL server policies with those of the MNO and NSCE service provider.
In Release 17, the NSP (Network Service Provider) function was enhanced with new capabilities for multi-slice coordination and policy harmonization. Specifically, it introduced a multiple slices coordinated resource optimization service to allow resource adjustment between a PLMN slice and its associated PNI-NPN slices for efficient resource usage. Furthermore, it defined the policy harmonization service to ensure VAL server policies are compatible with both MNO and NSCE service provider policies.
- Modification of PLMN List IE description TS 24.302CR0735
In Release 18, enhancements for the Network Service Provider (NSP) function included the introduction of a policy harmonization service to ensure compatibility between VAL server policies and those of the MNO and NSCE service provider. Furthermore, the NSCE architecture was extended to provide multiple slices combined management and coordinated resource optimization services between a PLMN and its PNI-NPNs. A correction was also made to the encoding of PLMN lists in the specification annexes.
- Correction to the encoding of PLMN lists in Annex H TS 24.302CR0747
In Release 19, the NSP (Network Service Provider) function introduced support for predictive slice modification within inter-PLMN based slice service continuity procedures. This enhancement allows the NSCE server to proactively trigger slice modifications based on VAL server policies, harmonizing them with MNO and NSCE service provider policies. The update specifically enables this predictive action to maintain service continuity as a user moves between different Public Land Mobile Networks.
Explore further
Broader topics and technologies where NSP plays a role.
Defining Specifications
3GPP specifications that define or reference NSP, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.435 vj30 | Network Slice Capability Exposure Procedures | Rel-19 |
| TS 23.700 vk00 | XR Services Application Enablement Layer | Rel-20 |
| TS 24.302 vj00 | Access to EPC via non-3GPP networks; Stage 3 | Rel-19 |
| TR 26.941 vj01 | 5G Media Slicing Extensions | Rel-19 |
| TS 28.530 vj00 | Network Slicing Concepts & Requirements | Rel-19 |
| TS 28.531 vk00 | Management and Orchestration | Rel-20 |
| TS 28.535 vj00 | Closed Control Loop Assurance Management | Rel-19 |
| TR 28.836 vi00 | Technical Report on Intent Driven Management | Rel-18 |
| TR 28.843 vi10 | Technical Report on Charging Aspects for Vertical Scenarios | Rel-18 |
| TR 32.847 vi00 | Technical Report | Rel-18 |