Network Service Provider

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.

Key Features

• Provides IP connectivity and application services external to the 3GPP mobile network
• Identified and selected by the UE via the Access Point Name (APN) parameter
• Responsible for final IP address allocation to the UE (e.g., via DHCP)
• Implements its own service policies, security, and charging within its domain
• Can be an Internet Service Provider (ISP), an enterprise network, or an IMS service provider
• Interworks with the 3GPP network via standardized interfaces at the PGW/UPF

Evolution Across Releases

Defining Specifications