Network Requested PDP Context Activation

Description

Network Requested PDP Context Activation (NRP) is a core network procedure defined for 2.5G (GPRS) and 3G (UMTS) packet-switched domains. A PDP (Packet Data Protocol) context is a logical association between a mobile device (MS/UE) and the network that defines parameters for a data session, such as the IP address, QoS profile, and the serving GGSN. Normally, the mobile device initiates PDP context activation. NRP reverses this flow, allowing the network, specifically the Gateway GPRS Support Node (GGSN), to trigger the activation of a PDP context towards a device that is GPRS-attached but may not have an active data session.

The procedure works as follows: When an external Packet Data Network (PDN), like the Internet or a corporate network, has data destined for a mobile subscriber, it sends the data packets to the subscriber's GGSN. If the GGSN finds no active PDP context for that subscriber (i.e., the device has no IP session established), it can initiate the NRP procedure. The GGSN sends a PDP context activation request message to the SGSN currently serving the subscriber. This request contains key parameters like the Access Point Name (APN), requested QoS, and the PDP address (IP address) to be assigned. The SGSN then locates the mobile device and forwards a request to activate a specific PDP context.

Upon receiving this network-initiated request, the mobile device typically responds by initiating the standard mobile-originated PDP context activation procedure towards the network, using the parameters provided by the GGSN. This establishes the data session bi-directionally. Key network components involved are the GGSN (which initiates the request), the SGSN (which routes the request to the correct serving area and manages the mobility context), and the HLR (Home Location Register) or, in later architectures, the HSS, which the GGSN may query to determine the current serving SGSN for the subscriber if it is unknown.

NRP's role is critical for enabling mobile-terminated packet data services. It allows the network to 'wake up' a device to receive data, supporting the 'always-on' experience where the device is reachable without maintaining a constant data bearer, thus saving device battery and radio resources. It is the underlying mechanism for push services, where a server needs to initiate communication with a mobile client. The procedure ensures that the necessary data bearer with appropriate QoS is established just-in-time to deliver the incoming data, optimizing network resource usage compared to maintaining permanent sessions for all attached devices.

Purpose & Motivation

NRP was created to address a fundamental limitation in early GPRS networks: the inability for the network to initiate a data session to a mobile device. In the standard model, only the mobile device could activate a PDP context. This was sufficient for client-initiated services like web browsing but broke server-initiated services like receiving an email notification, an instant message, or a mobile-terminated VoIP call. Without NRP, a device would only be reachable for data if it had pre-established and maintained an active PDP context, which was inefficient for battery and network resources.

The primary problem NRP solves is enabling push-based and mobile-terminated data services in a resource-efficient manner. It allows the network to trigger the setup of the data path on-demand when data arrives for a subscriber. This was a crucial enabler for the always-connected user experience envisioned for 2.5G and 3G data services. The motivation was to make packet-switched networks as receptive to incoming sessions as circuit-switched networks were for voice calls, thereby supporting a new generation of interactive and push services.

Historically, before NRP, workarounds were inefficient, such as devices periodically polling servers or maintaining always-on contexts. NRP, introduced in 3GPP Release 6 as part of enhanced IP Multimedia Subsystem (IMS) and general data service requirements, provided a standardized, network-efficient solution. It addressed the limitations of the mobile-originated-only model by defining the precise signaling between GGSN, SGSN, and the UE. This development was key to the success of services like BlackBerry push email, Presence services, and later, rich IMS applications, making the mobile device a true bidirectional IP endpoint.

Key Features

• Enables the GGSN to initiate PDP context establishment towards a GPRS/UMTS mobile device
• Triggers activation when incoming data arrives for a subscriber with no active session
• Utilizes standard GTP-C signaling between GGSN and SGSN for the request
• Allows the network to propose session parameters (APN, QoS, IP address)
• Essential for push services (email, messaging) and mobile-terminated data sessions
• Promotes resource efficiency by establishing bearers on-demand rather than maintaining always-on sessions

Evolution Across Releases

Defining Specifications