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.
Classification
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (3 CRs across 3 releases). Complements the general historical overview above with the evidence-based evolution of this function.
Explore further
Broader topics and technologies where PDP plays a role.
Defining Specifications
3GPP specifications that define or reference PDP, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TR 21.905 vj20 | 3GPP Terminology and Definitions | Rel-19 |
| TR 21.978 v1300 | CAMEL Control of VoIP Services Feasibility Study | Rel-4 |
| TS 22.060 vj00 | GPRS Stage 1 Service Description | Rel-19 |
| TR 22.944 vj00 | UE Functionality Split Scenarios and Requirements | Rel-19 |
| TS 23.016 vj00 | Subscriber Data Management Stage 2 | Rel-19 |
| TS 23.057 vj00 | Mobile Execution Environment (MExE) Specification | Rel-19 |
| TS 23.060 vj00 | GPRS Stage 2 Service Description | Rel-19 |
| TS 23.078 vj00 | CAMEL Phase 4 Stage 2 Specification | Rel-19 |
| TS 23.107 vj00 | UMTS QoS Framework | Rel-19 |
| TS 23.207 vj00 | End-to-End QoS Framework for GPRS | Rel-19 |
| TS 23.221 vj00 | 3GPP System Architectural Requirements | Rel-19 |
| TS 23.228 vk00 | IP Multimedia Core Network Subsystem (IMS) Stage 2 | Rel-20 |
| TS 23.327 vd10 | 3GPP-WLAN Mobility Stage 2 Description | Rel-13 |
| TR 23.976 vj00 | Push Service Requirements Analysis | Rel-19 |
| TR 23.979 vj00 | PoC over 3GPP Systems Architectural Requirements | Rel-19 |
| TR 23.981 vj00 | IPv4 IMS Interworking and Migration Study | Rel-19 |
| TS 24.065 v1310 | GPRS Subnetwork Dependent Convergence Protocol | Rel-4 |
| TS 24.161 vj00 | Network-Based IP Flow Mobility (NBIFOM) | Rel-19 |
| TS 24.167 vj10 | 3GPP IMS Management Object | Rel-19 |
| TS 24.228 v1590 | IP Multimedia Call Control Signaling Flows | Rel-5 |
| TS 24.229 vk00 | IMS Call Control Protocol based on SIP | Rel-20 |
| TS 24.305 vj00 | Selective Disabling of 3GPP UE Capabilities | Rel-19 |
| TS 25.413 vj00 | Radio Access Network Application Part (RANAP) | Rel-19 |
| TS 25.705 vd00 | UMTS Small Data Transmission Enhancements Study | Rel-13 |
| TR 25.996 vj00 | 3GPP-3GPP2 Spatial Channel Model Specification | Rel-19 |
| TS 26.114 vk00 | Multimedia Telephony Service for IMS | Rel-20 |
| TS 26.233 vf00 | 3GPP Packet-Switched Streaming Service (PSS) | Rel-15 |
| TS 26.346 vj30 | MBMS User Services Specification | Rel-19 |
| TR 26.937 vj00 | 3GPP PSS Characterization | Rel-19 |
| TS 27.060 vj00 | TE-MT Interworking for Packet Domain | Rel-19 |
| TS 29.060 vj00 | GPRS Tunnelling Protocol (GTP) version 1 | Rel-19 |
| TS 29.119 vj00 | GTP for GLR in 3GPP Networks | Rel-19 |
| TS 31.111 vj40 | 3GPP TS 31111 vj40: USIM Application Toolkit | Rel-19 |
| TS 31.829 vd00 | ISIM Conformance Requirements Technical Report | Rel-13 |
| TS 32.101 vj00 | PLMN Management Principles and Requirements | Rel-19 |
| TS 32.240 vk00 | Charging Architecture and Principles in 3GPP | Rel-20 |
| TS 32.251 vj00 | PS Domain Charging Management | Rel-19 |
| TS 32.252 vc00 | 3GPP WLAN Interworking Charging | Rel-12 |
| TS 32.272 vj00 | Charging for Push-to-Talk over Cellular (PoC) | Rel-19 |
| TS 32.808 v1800 | Common User Profile Storage Framework | Rel-8 |
| TS 33.108 vj00 | LI Handover Interface Specification | Rel-19 |
| TS 33.141 vj00 | Security for Presence Service (Ut reference point) | Rel-19 |
| TS 33.794 vj10 | Study on Zero Trust Security Enablers for 5G | Rel-19 |
| TS 33.822 v1800 | Security Architecture for Inter-Access Mobility | Rel-8 |
| TR 33.978 v1800 | Interim Security for Early IMS | Rel-8 |
| TS 38.151 vj10 | MIMO OTA Performance Requirements for NR UEs | Rel-19 |
| TS 38.551 vj00 | NR MIMO OTA Performance Requirements | Rel-19 |
| TS 38.753 vj00 | Spatial Channel Model Study for NR Demodulation | Rel-19 |
| TS 38.761 vj00 | MIMO OTA Performance Measurements for UE | Rel-19 |
| TS 38.762 vj10 | NR FR1 MIMO OTA Dynamic Test Methodology | Rel-19 |
| TS 38.827 vg80 | NR MIMO OTA Radiated Metrics & Test Methodology | Rel-16 |
| TS 38.843 vj00 | Study on AI/ML for NR Air Interface | Rel-19 |
| TS 43.051 vj00 | GERAN Stage 2 Service Description | Rel-19 |
| TS 43.129 vj00 | PS Handover in GERAN A/Gb and GAN Modes | Rel-19 |
| TS 43.318 vj00 | Generic Access Network (GAN) Stage 2 | Rel-19 |
| TR 43.901 vj00 | Generic Access to A/Gb Interface Feasibility Study | Rel-19 |
| TR 43.902 vj00 | GAN Enhancements Feasibility Study | Rel-19 |
| TS 44.060 vj00 | GERAN RLC/MAC Protocol Specification | Rel-19 |
| TS 44.065 vj00 | GPRS SNDCP Specification | Rel-19 |
| TS 44.160 vg00 | GERAN Iu Mode RLC/MAC Protocol Specification | Rel-16 |
| TS 44.318 vj00 | Generic Access Network (GAN) Interface Procedures | Rel-19 |