Network layer Service Access Point Identifier

Description

The Network layer Service Access Point Identifier (NSAPI) is a critical identifier in 3GPP packet-switched systems, such as GPRS, UMTS, and EPS. It is a value, typically ranging from 0 to 15, that uniquely identifies a specific Network Service Access Point (NSAP) instance associated with a Packet Data Protocol (PDP) context. The NSAPI is used by both the mobile station (UE) and the network nodes, like the SGSN and GGSN, to reference a particular data session. When a PDP context is activated, the NSAPI is assigned and remains associated with that context for its lifetime, allowing the network layer to route data and manage signaling for that specific session independently of others.

Operationally, the NSAPI works in conjunction with the Tunnel Endpoint Identifier (TEID) and the PDP address (e.g., IP address). During PDP context activation, the UE proposes an NSAPI value, which the network accepts or may reassign. This NSAPI is then used in all subsequent messages related to that PDP context, such as modification or deactivation requests. In the user plane, the NSAPI helps in multiplexing and demultiplexing data packets belonging to different PDP contexts over the same physical radio bearer. For example, a smartphone might have one PDP context for internet browsing (NSAPI=5) and another for IMS voice (NSAPI=6), each with distinct QoS parameters; the NSAPI ensures that data for each service is correctly processed.

The NSAPI is a key component in the protocol stacks defined in specifications like 23.060. It is used in the Session Management (SM) messages between the UE and SGSN, and it is also mapped to identifiers in the Gn/Gp interface (like TEID) between SGSN and GGSN. This mapping allows end-to-end correlation of a data session across multiple network elements. The NSAPI's limited range (0-15) constrains the number of simultaneous PDP contexts per UE, but this is typically sufficient for most use cases. Its role is foundational for supporting multiple active data sessions, enabling features like dedicated bearers in LTE and network slicing in 5G, where different slices or services require separate logical channels.

Purpose & Motivation

The NSAPI was introduced to solve the problem of managing multiple concurrent packet data sessions on a single mobile device. Before its standardization, early data services lacked a robust mechanism to distinguish between different data flows, limiting devices to essentially one data context at a time. The NSAPI provides a simple yet effective identifier that allows the network and the UE to handle several PDP contexts simultaneously, each potentially with different QoS requirements, such as one for best-effort web browsing and another for low-latency VoIP.

Its creation was driven by the evolution from basic GPRS to more advanced UMTS services, where users demanded simultaneous access to diverse applications. The NSAPI enables the network to apply specific policies, charging, and QoS per context. For instance, an IMS voice call can be prioritized over background email synchronization because each has its own NSAPI-tagged PDP context. This granularity addresses the limitations of monolithic data sessions, supporting the complex service offerings of modern mobile networks. The NSAPI remains relevant in 4G and 5G as part of the EPS bearer and PDU session concepts, ensuring backward compatibility and consistent session management principles.

Key Features

• Uniquely identifies a PDP context/NSAP instance within a UE and network
• Numerical value range 0-15, with specific values reserved (e.g., 0 for signaling)
• Used in Session Management signaling for context activation, modification, deactivation
• Enables multiplexing of multiple data sessions over shared radio resources
• Maps to other identifiers like TEID for inter-node correlation
• Supports independent QoS profile application per NSAPI

Evolution Across Releases

Defining Specifications