Description
The PDU Session is the cornerstone of the 5G Service-Based Architecture (SBA) connectivity model, introduced in 3GPP Release 14 and formalized in TS 23.501. It represents a logical association between a User Equipment (UE) and a Data Network (DN), such as the Internet, an IP Multimedia Subsystem (IMS), or an enterprise network. Unlike the Evolved Packet System (EPS) bearer concept from LTE, the PDU Session provides a much more flexible framework that supports multiple PDU Session types: IPv4, IPv6, IPv4v6, Ethernet, and Unstructured (non-IP). This architectural shift enables 5G to natively support diverse verticals, including industrial IoT, automotive, and fixed wireless access, without requiring complex encapsulation or tunneling overlays.
Architecturally, a PDU Session is established between the UE and the User Plane Function (UPF) via the N1 interface for control signaling and the N3 interface for user data. The control-plane signaling is handled by the Session Management Function (SMF), which communicates with the Access and Mobility Management Function (AMF), the Policy Control Function (PCF), and the UPF over the N4 interface using PFCP (Packet Forwarding Control Protocol). The SMF allocates IP addresses (or prefixes), manages QoS, and selects the appropriate UPF based on factors such as DNN (Data Network Name), S-NSSAI (Single Network Slice Selection Assistance Information), and UE location. The AMF, although not involved in session management per se, provides the transport for NAS Session Management (SM) messages between the UE and SMF.
One of the most significant features of a PDU Session is its support for multiple QoS Flows. Each QoS Flow is identified by a QoS Flow Identifier (QFI) and represents the finest granularity of QoS treatment within a PDU Session. In the downlink, the UPF classifies packets into QoS Flows based on Service Data Flow (SDF) templates provided by the SMF, while in the uplink, the UE uses QoS rules signaled via NAS. This decoupling of the session (connectivity) from the flows (QoS) allows applications with different requirements—such as enhanced Mobile Broadband (eMBB), Ultra-Reliable Low-Latency Communication (URLLC), and massive Machine-Type Communication (mMTC)—to share the same PDU Session while receiving differentiated treatment.
The PDU Session lifecycle is tightly coupled with mobility and network slicing. When a UE moves, the SMF may maintain the session through UPF re-selection or trigger a session release and re-establishment, depending on the session continuity mode (SSC mode 1, 2, or 3). For network slicing, each PDU Session is associated with one S-NSSAI, ensuring that slice-specific resources and policies are applied. In Release 15 and beyond, the PDU Session also supports features such as Ethernet header compression, reflective QoS, and uplink classifiers. The introduction of PDU Set in Release 19 further extends the PDU Session framework to support application-level data units, such as video frames in XR services.
In summary, the PDU Session is not just a connection but a programmable, policy-driven, multi-service conduit that encapsulates 5G's promise of flexibility and service differentiation. It abstracts the complexity of heterogeneous access (3GPP and non-3GPP) and provides a uniform anchor point for mobility, QoS, and charging.
Purpose & Motivation
Prior to 5G, the EPS bearer model in LTE was optimized for IP-based services and lacked native support for non-IP data types such as Ethernet or Unstructured data, which are critical for IoT and industrial applications. The PDU Session was created to address these limitations by providing a more generic and extensible connectivity framework. It decouples the concept of a session from the underlying bearer, allowing multiple QoS flows to coexist and be managed independently. This is essential for supporting the diverse service requirements of 5G, including network slicing, where each slice may require its own session management policies.
The PDU Session also solves the problem of session continuity across different access technologies and mobility scenarios. By defining Session and Service Continuity (SSC) modes, 3GPP enables operators to choose whether to maintain a session when the UE moves (SSC mode 1), break and re-establish immediately (SSC mode 2), or break and re-establish with a new IP address to avoid anchor relocation (SSC mode 3). This flexibility is vital for applications with different tolerance to IP address changes, such as voice over IMS versus HTTP streaming.
Furthermore, the PDU Session architecture supports the separation of control and user plane (CUPS), which allows for scalable and distributed deployments. It also enables edge computing by allowing the SMF to select a UPF close to the UE, reducing latency. The introduction of PDU Sets in Release 19 demonstrates the ongoing evolution of this concept to meet emerging application needs, such as XR and cloud gaming, where the payload of a single application unit may span multiple PDUs and requires coordinated QoS treatment.
What changed in its specifications
The latest release-to-release comparison of specifications that define PDU Session. Each summary describes the whole specification, not only this term.
Rel-19 added MPQUIC steering to multi-access PDU sessions, XR and media handling, and an Energy Information Function. It also added Local Offloading Management for edge computing, Vertical Federated Learning for AI/ML, and Ambient IoT text.
Full comparison in TS 23.501 →Rel-19 adds multi-access ATSSS capabilities, QoS monitoring with available-bitrate parameters, and XR/media policy provisioning such as data burst size and expedited transfer. It also adds local offloading management, non-3GPP device information, and URSP provisioning in EPS support.
Full comparison in TS 29.512 →Technology family
Sessions, bearers and QoS · Core Network
- R96 PDP context
- R99 ARP, GBR, Radio Access Bearer (RAB), TFT, UMTS bearer service
- Rel-7 IP-CAN bearer, IP-CAN session, QCI
- Rel-8 APN-AMBR, Dedicated EPS bearer, Default EPS bearer, EPS bearer, EPS Bearer Identity (EBI), UE-AMBR
- Rel-9 Evolved ARP
- Rel-15 5QI, GFBR, MFBR, PDU Session, QoS Flow, Session-AMBR
- Rel-16 MA PDU Session
- PDU Session counterpart in another generation: PDP context
“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
- PDU Session extended by MA PDU Session
“This component in the UE initiates the establishment of one or more multipath QUIC connections, after the establishment of the MA PDU Session” TS 23.501
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 sourcesDocumented changes in 6 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.
The PDU Session is specified for the first time in Rel-15: it supports types IPv4, IPv6, IPv4v6, Ethernet and Unstructured, uses PDU Session Anchors and multi-homing, and has establishment, modification and release procedures.
- “Each PDU Session supports a single PDU Session type i.e. supports the exchange of a single type of PDU requested by the UE” TS 23.501 v15.13.0
- “N2 PDU Session Request (N2 SM information, NAS message (PDU Session ID, N1 SM container (PDU Session Establishment Accept)))” TS 23.502 v15.17.0
- “A PDU Session may be associated with multiple IPv6 prefixes. This is referred to as multi-homed PDU Session.” TS 23.501 v15.13.0
Rel-16 extended PDU Sessions to multiple access types (MA PDU Session) and added new PDU Session release triggers, such as AMF-requested release on slice authentication failure or V/I-SMF failure.
- “A PDU Session associated with multiple access types is referred to as Multi Access-PDU (MA PDU) Session and it may be requested by ATSSS-capable UEs.” TS 23.502 v16.19.0
- “The AMF may request PDU Session Release towards an alternative V/I-SMF in the same SMF Set when it detects the V/I-SMF has failed” TS 29.502 v16.17.0
- UE Requested PDU Session Establishment with Network Modification to MA PDU Session TS 23.501CR1118
Rel-17 changed PDU Session handling: NSACF now counts PDU Sessions and MA PDU Sessions per slice, and a restricted PDU Session is enabled for remote provisioning, alongside other session procedure changes.
- “the NSACF returns a result parameter indicating that the maximum number of PDU Sessions per network slice has been reached” TS 23.502 v17.15.0
- “Onboarding Services are provided using a PDU Session for DNN and S-NSSAI used for onboarding allowing remote provisioning of UEs via User Plane.” TS 23.501 v17.15.0
- NSAC for maximum number of PDU Sessions and MA PDU Session TS 23.502CR3411
PDU Session procedures changed in Rel-18: release commands carry an Alternative S-NSSAI for re-establishment, and PDU Sessions can be authorized for HR-SBO and kept deactivated outside a slice's area.
- “If the cause value indicates that a PDU Session re-establishment on the Alternative S-NSSAI is required the PDU Session Release Command message also includes the Alternative S-NSSAI.” TS 23.502 v18.14.0
- “the SMF deactivates the PDU Session as described in step 3a in clause 4.3.4.2 of TS 23.502 [3], but the PDU Session context in UE and SMF is not released” TS 23.501 v18.12.0
- The support of Home Routed PDU Session supporting Session Breakout in VPLMN (HR-SBO) TS 23.501CR3830
PDU Session procedures and behaviour were extended in Rel-19, e.g. H-SMF set ID selection in the HPLMN, UPF event exposure during relocation and release, and MPQUIC support for MA PDU Sessions.
- “an SMF and optionally H-SMF set ID in the HPLMN using the S-NSSAI of the HPLMN used for the PDU Session” TS 23.502 v19.9.0
- “The information flow also applies to PDU Session release.” TS 23.502 v19.9.0
- MA PDU Session and PDN connections updates due to MPQUIC-IP/MPQUIC-UDP/MPQUIC-E TS 23.502CR4980
PDU Session behaviour changed in Rel-20: Ethernet BH PDU Session support for MWAB, PDU Session release improvements, and PDU Session-level UPF Abnormal Traffic Pattern measurement and event reporting.
- Support of Ethernet type of BH PDU Session for MWAB TS 23.501CR6330
- Improvement of PDU Session Release TS 29.518CR1337
- “the UPF shall perform the requested measurements for every PDU Session that matches the Event Filter Information and send the information per PDU Session” TS 23.502 v20.3.0
Defining Specifications
3GPP specifications that define or reference PDU Session, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.501 vk30 | 5G System Architecture | Rel-20 read |
| TR 23.799 ve00 | Study on Next Generation System Architecture | Rel-14 read |
| TS 29.512 vk10 | Session Management Policy Control Service Stage 3 | Rel-20 read |
| TS 38.414 vj00 | NG Interface User Plane Protocol | Rel-19 read |