Description
Packet Data Protocol (PDP) is a core concept in 2G (GPRS/EDGE) and 3G (UMTS) packet-switched networks, and its principles extend into 4G (EPS) via the evolved Packet Data Network (PDN) concept. It defines the protocol stack (e.g., IPv4, IPv6, PPP) used for user data transmission over the mobile core network. A PDP context is the central operational entity—it is a set of information parameters established between the User Equipment (UE), the Serving GPRS Support Node (SGSN), and the Gateway GPRS Support Node (GGSN) to facilitate a packet data session. This context contains critical information such as the PDP type (e.g., IPv4), the assigned PDP address (IP address), requested QoS profile, and the Access Point Name (APN) which identifies the external packet data network (e.g., the internet or a private corporate network) the UE wishes to connect to.
The establishment of a PDP context is a multi-step signaling procedure. It begins with an Activate PDP Context Request from the UE to the SGSN, specifying the desired APN and PDP type. The SGSN validates the subscriber, performs authentication, and uses the APN to resolve the address of the appropriate GGSN. It then forwards the request to that GGSN. The GGSN, acting as the gateway to the external network, allocates a dynamic PDP address (or confirms a static one), creates a tunnel endpoint, and establishes a GTP (GPRS Tunneling Protocol) tunnel back to the SGSN for user plane traffic. The SGSN then configures the necessary radio access bearers with the requested QoS and completes the context activation with the UE. Once established, all user IP packets are encapsulated within GTP tunnels between the GGSN and SGSN, and over the radio interface according to the specified PDP type.
The PDP context manages the entire lifecycle of a user's data session. It supports multiple concurrent contexts for a single UE (e.g., one for internet access and another for IMS voice), each with independent QoS settings. The context can be modified (e.g., to change QoS), preserved during intersystem handovers (like 3G to 2G), and deactivated when the session ends. The GGSN uses the context for functions like charging, policy enforcement, and routing packets between the mobile network and the external PDN. In the evolution to 4G EPC, the PDP Context is replaced by the EPS Bearer and PDN Connection, but the fundamental concept of an established, stateful data session with specific QoS parameters remains.
Purpose & Motivation
The PDP context mechanism was created to introduce efficient, always-on packet-switched data services to mobile networks, which were originally designed for circuit-switched voice. Prior to GPRS, data services in GSM were slow and inefficient, using circuit-switched data channels that tied up network resources for the entire duration of a connection, similar to a dial-up modem. The PDP context model solved this by enabling dynamic, on-demand allocation of packet-oriented resources, allowing statistical multiplexing of many users' data over shared channels, which dramatically improved network efficiency and enabled the first practical mobile internet experience.
It provided a standardized framework for managing IP connectivity, addressing, and quality of service in a mobile environment. This was crucial for supporting a wide range of emerging data applications with different requirements, from basic web browsing to corporate VPN access. The PDP context separated the control plane (signaling to establish the context) from the user plane (the actual data flow), allowing for more flexible and scalable network architectures. It also introduced the concept of an Access Point Name (APN), which gave operators control over routing traffic to different external networks (like operator portals, partner services, or the public internet) and enabled advanced services like fixed-mobile convergence.
Furthermore, the PDP context laid the groundwork for essential mobile broadband capabilities like always-on connectivity (where the IP address is retained even during radio idle states) and seamless mobility across different radio access technologies. It established the architectural pattern of tunneling user data through the core network (using GTP), which provided security, mobility anchoring, and simplified integration with external IP networks. This model directly influenced the design of later systems like EPS in 4G and 5GC in 5G.
Key Features
- Defines the protocol (IP, PPP) for user data transmission
- Manages IP address allocation (PDP address) for the UE
- Establishes and maintains a logical connection (PDP Context) between UE, SGSN, and GGSN
- Supports multiple concurrent contexts per UE for different services
- Associates a QoS profile to define priority, delay, and throughput
- Utilizes GTP tunneling for secure user plane transport through the core network
Evolution Across Releases
Introduced the foundational PDP context architecture for UMTS (3G), enabling high-speed packet data services. It defined the PDP Context Activation, Modification, and Deactivation procedures between UE, SGSN, and GGSN, supporting IPv4 as the primary PDP type and establishing GTPv0/GTPv1 for tunneling.
Enhanced support for QoS with the introduction of Traffic Classes (Conversational, Streaming, Interactive, Background) and associated QoS attributes. Improved mobility procedures for SRNS relocation.
Introduced IMS (IP Multimedia Subsystem) support, requiring enhanced PDP context capabilities for SIP signaling and media bearers. Added support for IPv6 as a PDP type and defined procedures for dual-stack IPv4v6 operation.
Enhanced QoS with the introduction of Extended QoS parameters for higher bit rates and lower delays. Defined optimizations for Always-On connectivity and fast context activation procedures to improve user experience.
Marked the transition to EPS (4G LTE). PDP Context remains for 2G/3G access but is complemented by the new EPS Bearer concept for LTE. Defined interworking procedures between GERAN/UTRAN PDP Contexts and E-UTRAN EPS Bearers.
Defining Specifications
| Specification | Title |
|---|---|
| TS 21.905 | 3GPP TS 21.905 |
| TS 21.978 | 3GPP TS 21.978 |
| TS 22.060 | 3GPP TS 22.060 |
| TS 22.944 | 3GPP TS 22.944 |
| TS 23.016 | 3GPP TS 23.016 |
| TS 23.057 | 3GPP TS 23.057 |
| TS 23.060 | 3GPP TS 23.060 |
| TS 23.078 | 3GPP TS 23.078 |
| TS 23.107 | 3GPP TS 23.107 |
| TS 23.207 | 3GPP TS 23.207 |
| TS 23.221 | 3GPP TS 23.221 |
| TS 23.228 | 3GPP TS 23.228 |
| TS 23.327 | 3GPP TS 23.327 |
| TS 23.976 | 3GPP TS 23.976 |
| TS 23.979 | 3GPP TS 23.979 |
| TS 23.981 | 3GPP TS 23.981 |
| TS 24.065 | 3GPP TS 24.065 |
| TS 24.161 | 3GPP TS 24.161 |
| TS 24.167 | 3GPP TS 24.167 |
| TS 24.228 | 3GPP TS 24.228 |
| TS 24.229 | 3GPP TS 24.229 |
| TS 24.305 | 3GPP TS 24.305 |
| TS 25.413 | 3GPP TS 25.413 |
| TS 25.705 | 3GPP TS 25.705 |
| TS 25.996 | 3GPP TS 25.996 |
| TS 26.114 | 3GPP TS 26.114 |
| TS 26.233 | 3GPP TS 26.233 |
| TS 26.346 | 3GPP TS 26.346 |
| TS 26.937 | 3GPP TS 26.937 |
| TS 27.060 | 3GPP TS 27.060 |
| TS 29.060 | 3GPP TS 29.060 |
| TS 29.119 | 3GPP TS 29.119 |
| TS 31.111 | 3GPP TR 31.111 |
| TS 31.829 | 3GPP TR 31.829 |
| TS 32.101 | 3GPP TR 32.101 |
| TS 32.240 | 3GPP TR 32.240 |
| TS 32.251 | 3GPP TR 32.251 |
| TS 32.252 | 3GPP TR 32.252 |
| TS 32.272 | 3GPP TR 32.272 |
| TS 32.808 | 3GPP TR 32.808 |
| TS 33.108 | 3GPP TR 33.108 |
| TS 33.141 | 3GPP TR 33.141 |
| TS 33.794 | 3GPP TR 33.794 |
| TS 33.822 | 3GPP TR 33.822 |
| TS 33.978 | 3GPP TR 33.978 |
| TS 38.151 | 3GPP TR 38.151 |
| TS 38.551 | 3GPP TR 38.551 |
| TS 38.753 | 3GPP TR 38.753 |
| TS 38.761 | 3GPP TR 38.761 |
| TS 38.762 | 3GPP TR 38.762 |
| TS 38.827 | 3GPP TR 38.827 |
| TS 38.843 | 3GPP TR 38.843 |
| TS 43.051 | 3GPP TR 43.051 |
| TS 43.129 | 3GPP TR 43.129 |
| TS 43.318 | 3GPP TR 43.318 |
| TS 43.901 | 3GPP TR 43.901 |
| TS 43.902 | 3GPP TR 43.902 |
| TS 44.060 | 3GPP TR 44.060 |
| TS 44.065 | 3GPP TR 44.065 |
| TS 44.160 | 3GPP TR 44.160 |
| TS 44.318 | 3GPP TR 44.318 |