Menu
Latest
12 meetings · Prague, Jeju · 12–16 Oct
Reports
RAN1#126-bis · SA2#177

Glossary term · Core Network

PDP Context

Packet Data Protocol Context

Core Network →

PDP Context is an information set held in the Mobile Station and GPRS Support Nodes that describes an active packet data session, containing parameters like the PDP address, QoS profile, and APN to enable data transfer.

Introduced
R96
Where
Core Network › Legacy Core
Specifications
3 specs
PDP Context Description Purpose What changed Family Neighbours Detected Changes Specifications

Description

A PDP Context is a fundamental concept in GPRS and UMTS networks, representing the session state for a packet data protocol (PDP) connection between a Mobile Station (MS) and a Gateway GPRS Support Node (GGSN). It is essentially a set of information stored in both the MS and the GSNs (SGSN and GGSN) that defines the characteristics of the data session, including the PDP address (IP address), the Access Point Name (APN), the Quality of Service (QoS) profile, and other parameters such as the PDP type (IPv4, IPv6, IPv4v6). The PDP Context is identified by a PDP Context Identifier (a numeric value) and is used to route user data between the MS and the external packet data network. Without an active PDP Context, the MS cannot send or receive IP packets.

The establishment of a PDP Context involves a signaling procedure called PDP Context Activation. The MS initiates this by sending an Activate PDP Context Request to the SGSN, which includes parameters like the APN, PDP type, and requested QoS. The SGSN validates the request, selects a GGSN based on the APN, and sends a Create PDP Context Request to the GGSN. The GGSN allocates an IP address (if not provided by the MS) and returns a Create PDP Context Response. The SGSN then sends an Activate PDP Context Accept to the MS, completing the procedure. At this point, the PDP Context is active in the MS, SGSN, and GGSN, and user data can flow. The context remains active until it is deactivated, either by the MS (e.g., when the application closes) or by the network (e.g., due to inactivity or policy).

Each PDP Context is associated with a specific QoS profile, which defines parameters like maximum bit rate, guaranteed bit rate, and traffic class. The network can modify the QoS of an active PDP Context through a PDP Context Modification procedure, which may be triggered by the MS, SGSN, or GGSN. This allows dynamic adaptation to changing network conditions or application requirements. The PDP Context also includes the PDP address, which is the IP address assigned to the MS for that session. In dual-stack scenarios (IPv4v6), a single PDP Context can have two IP addresses (one IPv4 and one IPv6), as specified in Release 9 and later. This was an enhancement over earlier releases where only one PDP address was supported per context.

The PDP Context is stored in the MS and GSNs as a set of information elements. In the MS, it is managed by the Non-Access Stratum (NAS) layer. In the SGSN and GGSN, it is part of the packet data protocol state machine. The context includes the Tunnel Endpoint Identifier (TEID) for GTP tunnels, which are used to carry user data between the SGSN and GGSN. The SGSN maintains a mapping between the PDP Context and the radio access bearer (RAB) for the MS, ensuring that data is correctly routed over the air interface. When the MS moves, the SGSN may change, but the PDP Context can be transferred to the new SGSN through a Routing Area Update procedure, maintaining session continuity.

In EPS (LTE), the PDP Context concept was largely replaced by the EPS Bearer and PDN Connection, but it still exists for interworking with legacy GPRS/UMTS networks. When a UE moves from LTE to UTRAN/GERAN, the PDN Connection is mapped to a PDP Context to preserve the IP session. The PDP Context is defined in 3GPP TS 23.060 (GPRS service description) and related specs like TS 29.060 (GTP) and TS 29.119 (GTP' for charging). Understanding PDP Context is essential for engineers working on legacy networks, as it forms the basis for packet data session management in 2G and 3G.

Purpose & Motivation

The PDP Context was created to manage packet data sessions in GPRS and UMTS networks, providing a standardized way to establish, maintain, and release IP connectivity for mobile devices. Before its introduction, circuit-switched data was the norm, which was inefficient for bursty IP traffic. The PDP Context introduced a packet-switched approach, allowing multiple users to share network resources and enabling always-on connectivity. It solved the problem of how to allocate and manage IP addresses, QoS, and routing for mobile data sessions in a scalable manner.

One of the key motivations was the need to support different QoS levels for various applications. The PDP Context includes a QoS profile that can be negotiated and modified, allowing operators to offer differentiated services. It also enabled the concept of multiple PDP Contexts per MS, so a user could have simultaneous sessions to different APNs (e.g., Internet and corporate intranet) with different IP addresses and QoS. This was a significant advancement over previous technologies.

Furthermore, the PDP Context facilitated roaming and interworking with external packet data networks by using the APN to identify the target network. It also provided a framework for charging, as each PDP Context could be tracked for data volume and duration. The evolution of the PDP Context to support dual-stack (IPv4v6) in Release 9 addressed the growing need for IPv6 transition. Although EPS introduced the PDN Connection, the PDP Context remains relevant for legacy interworking and is still defined in 3GPP specifications. In essence, the PDP Context was the foundation for mobile packet data, paving the way for the all-IP architectures of LTE and 5G.

What changed in its specifications

The latest release-to-release comparison of specifications that define PDP Context. Each summary describes the whole specification, not only this term.

TS 29.060Rel-18 → Rel-19

Rel-19 brings only minor changes to TS 29.060: 0 clauses changed, with no change attributed to a release feature.

Full comparison in TS 29.060 →

Technology family

Sessions, bearers and QoS · Core Network

  1. R96 PDP context
  2. R99 ARP, GBR, Radio Access Bearer (RAB), TFT, UMTS bearer service
  3. Rel-7 IP-CAN bearer, IP-CAN session, QCI
  4. Rel-8 APN-AMBR, Dedicated EPS bearer, Default EPS bearer, EPS bearer, EPS Bearer Identity (EBI), UE-AMBR
  5. Rel-9 Evolved ARP
  6. Rel-15 5QI, GFBR, MFBR, PDU Session, QoS Flow, Session-AMBR
  7. Rel-16 MA PDU Session
  • PDP Context counterpart in another generation: EPS bearer
    “The SGSN sets the EPS Bearer Identity to an equivalent value as the NSAPI for the Bearer associated with the MS.” TS 23.060
  • PDP Context counterpart in another generation: PDU Session
    “The UE and the SMF+PGW-C store the association between the EPS Context and the PDU Session Context to use it in the case of handover from EPS to 5GS.” TS 23.502

Members and relations were proposed independently by several models and kept only where at least two agree; quotes are verified verbatim against the specifications. Release = first approved version of the defining specification.

Release Timeline

Detected Changes Across Releases

verified against 3GPP sources

Documented changes in 15 releases, each verified against the text of 3GPP specifications or approved change requests and shown with the exact wording. The release timeline above shows the same releases. A release without an entry has no documented change for this term.

R96 introduced

Introduced in R96 (release dating of the term; no individual change cited).

R99 2 CRs

R99 specifies PDP context handling in GTP: Create PDP Context Request/Response procedures and PDP Context IE changes, including added NSAPI, PDP Context Identifier, TEID Data I and GGSN user plane address.

  • “A valid request initiates the creation of a tunnel between a PDP Context in a SGSN and a PDP Context in a GGSN.” TS 29.060 v3.19.0
  • Adding Uplink TEID Data I and user plane GGSN address to PDP Context IE TS 29.060CR155r4
  • Correction on the handling of the PDP Context at unsuccessful PDP Context modification TS 29.060CR140
Rel-4 2 CRs

PDP context handling was changed in Rel-4: the Service Request procedure now covers regained radio coverage, the GGSN's Update PDP Context Response handling was corrected, and Charging Characteristics inclusion in Create PDP Context was specified.

  • Charging Characteristics Inclusion in Create PDP Context Message TS 29.060CR245r1
  • GGSN address for control plane must not be changed in "Update PDP Context Response" TS 29.060CR268r1
  • “the PDP context is preserved, but the maximum bit rate is downgraded to 0 kbit/s (both for uplink and downlink) when the associated RAB is released” TS 23.060 v4.11.0
Rel-5 1 CR

PDP context handling changed: Create PDP Context Request is no longer allowed for an already active context, PCO is carried in more PDP context messages, and the SGSN sends the serving network identity to the GGSN in Update PDP Context Request.

  • “The SGSN shall not send a Create PDP Context Request for an already active context.” TS 29.060 v5.14.0
  • “The SGSN should send the serving network identity to the GGSN.” TS 23.060 v5.13.0
  • Introduction of PCO IE in session management messages used in the Network-Requested PDP Context Activation Procedure (direction NW to MS) TS 29.060CR355
Rel-6 1 CR

PDP context signalling changed in Rel-6: Update PDP Context Request/Response gained CGI/SAI, RAT type, Prohibit Payload Compression and APN Restriction, and the SGSN must now send the serving network identity.

  • “The GGSNs update their PDP context fields and return Update PDP Context Response (TEID, Prohibit Payload Compression, APN Restriction).” TS 23.060 v6.15.0
  • “then the SGSN shall reject any Activate PDP Context requests to a different APN” TS 23.060 v6.15.0
  • Add the Common Flags IE to GGSN-Initiated Update PDP Context Request message TS 29.060CR537r1
Rel-7 specification text

PDP context signalling changed: Update PDP Context Request gained NRSN, BCM and CGI/SAI/RAI change parameters, Direct Tunnel handling, and QoS upgrade negotiation by the GGSN.

  • “NRSN indicates SGSN support of the network requested bearer control.” TS 23.060 v7.11.0
  • “the GGSN shall, following a SGSN-Initiated PDP Context Modification (triggered by SGSN change), perform a GGSN-Initiated PDP Context Modification” TS 23.060 v7.11.0
  • “If the SGSN has indicated support for upgrade of QoS in the request message, the QoS values may also be negotiated upwards by the GGSN.” TS 29.060 v7.17.0
Rel-8 1 CR

PDP context handling was extended in Rel-8: PDP contexts now also exist in S-GW/P-GW, Gn and S4 contexts are mutually exclusive per MS, and PDP address allocation and GTP Update PDP Context messages were revised.

  • “The same PDP address may appear in one or more PDP contexts in the MS, the SGSN, the S‑GW, the P‑GW and the GGSN.” TS 23.060 v8.17.0
  • “If an MS is sending an Activate PDP Context Request for an APN using Gn, the activation will be rejected by the SGSN if a PDP Context using S4 already exists” TS 23.060 v8.17.0
  • TFT in Initiate PDP Context Activation Request message TS 29.060CR0661r1
Rel-9 1 CR

PDP context signalling was extended in Rel-9: Update PDP Context Request now carries Negotiated Evolved ARP and User CSG Information, and Delete PDP Context Request gains IPv4v6 and Teardown Ind handling.

  • “The new SGSN sends Update PDP Context Request (new SGSN Address, TEID, QoS Negotiated, Negotiated Evolved ARP, serving network identity, CGI/SAI, User CSG Information” TS 23.060 v9.14.0
  • “The Teardown Ind is used to indicate whether all PDP contexts that share the PDP address or two IP addresses” TS 29.060 v9.14.0
  • Evolved ARP in Network Initiated Secondary PDP Context Activation TS 29.060CR0749r1
Rel-10 specification text

PDP context procedures changed in Rel-10: SGSN may reject PDP context requests with a back-off timer for congested APNs, LIPA PDP contexts restrict secondary contexts, and GTP messages gain APN congestion cause and back-off time.

  • “The SGSN may reject the Session Management (SM) requests from the MS (e.g. Activate PDP Context, Secondary PDP Context and Modify PDP Context Requests)” TS 23.060 v10.14.0
  • “The PDN GW/GGSN shall reject any MS initiated Secondary PDP Context Activation Procedure or any PDP Context Modification Procedure that is for the LIPA PDN Connection.” TS 23.060 v10.14.0
  • “The GGSN Back-Off Time information element indicates the time during which the SGSN should refrain from sending subsequent PDP Context requests” TS 29.060 v10.12.0
Rel-11 1 CR

Rel-11 adds PDP context handling: SGSN can deactivate PDP contexts of a congested APN with a Session Management back-off timer, and Delete PDP Context Request now carries CGI/SAI.

  • “The SGSN may deactivate PDP contexts belonging to a congested APN by sending the Deactivate PDP Context Request message to the MS” TS 23.060 v11.12.0
  • “the MS shall not initiate any Session Management procedures for the congested APN. The MS may initiate Session Management procedures for other APNs.” TS 23.060 v11.12.0
  • Addition of PS to CS handover indication in Delete PDP Context Request TS 29.060CR0932r1
Rel-12 specification text

PDP Context procedures changed: Update PDP Context Request now carries the CN Operator Selection Entity, and the SGSN must include it in shared networks. The P-CSCF restoration indication and LIPA/SIPTO rejection handling for PDP contexts were added.

  • “The SGSN shall send the serving network identity and the CN Operator Selection Entity to the GGSN.” TS 23.060 v12.11.0
  • “In shared networks, the SGSN shall include the CN Operator Selection Entity IE during the Primary PDP Context Activation procedure” TS 29.060 v12.9.0
  • “The PCRI (P-CSCF Restoration Indication) bit field is relevant for the SGSN-initiated Update PDP Context Request” TS 29.060 v12.9.0
Rel-13 specification text

PDP context signalling was extended for Rel-13: the SGSN can reject PDP context requests with a back-off timer and with a 'not reachable due to power saving' cause for delay-tolerant connections.

  • “The SGSN may deactivate PDP contexts from the MSs, belonging to this particular group and attaching to this particular APN” TS 23.060 v13.8.0
  • “the SGSN rejects the Initiate PDP Context Activation message with a rejection cause indicating that the MS is temporarily not reachable due to power saving” TS 23.060 v13.8.0
  • “is used by the SGSN in the Initiate PDP Context Activation Response and Update PDP Context Response message to reject the corresponding network initiated procedures” TS 29.060 v13.7.0
Rel-14 specification text

PDP Context handling gained a Non-IP PDP type (no header compression, SCEF or Gi/SGi delivery chosen per APN) and PS Data Off support indication in Create/Update PDP Context responses.

  • “If the SGSN establishes a PDP contexct of PDP type Non-IP, header compression shall not be used for the PDP context.” TS 23.060 v14.8.0
  • “the GGSN shall include the 3GPP PS Data Off Support Indication in the Create PDP Context Response PCO if it supports the 3GPP PS Data Off feature.” TS 23.060 v14.8.0
  • “For a PDP Type "Non-IP" the SGSN shall send the Create PDP Context Request to the GGSN only if the SGSN learns” TS 29.060 v14.4.0
Rel-15 1 CR

Rel-15 lets the MS send a PDP Context Modification to report 3GPP PS Data Off status while the SM back-off timer runs, and corrects the SGSN-initiated Update PDP Context Request.

  • “The MS is allowed to perform MS-initiated PDP Context Modification procedure to report 3GPP PS Data Off status change when the Session Management back off timer is running.” TS 23.060 v15.5.0
  • Correction to the SGSN-Initiated Update PDP Context Request TS 29.060CR1063
  • “The IMSI, if available, should be included and the GGSN should use the IMSI to verify if the Update PDP Context Request message is received for the right UE context.” TS 29.060 v15.6.0
Rel-16 specification text

TS 23.060 now says that at PDP Context activation the SGSN can use additional inputs beyond network local policy, which changes the activation behaviour.

  • “At PDP Context activation, in addition to network local policy, it shall be possible for SGSN to use:” TS 23.060 v16.0.0
  • “At PDP Context activation, it shall be possible for SGSN to use:” TS 23.060 v16.0.0

Defining Specifications

3GPP specifications that define or reference PDP Context, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TS 23.016 vj00 Subscriber Data Management Stage 2 Rel-19 read
TS 29.060 vj00 GPRS Tunnelling Protocol (GTP) version 1 Rel-19 read
TS 29.119 vj00 GTP for GLR in 3GPP Networks Rel-19 read