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

Glossary term · Interface

PDU session resource

Protocol Data Unit Session Resource

Interface →

PDU session resource is the fundamental unit of resource management in 5G RAN, comprising NG-RAN interface and radio resources allocated to support a PDU Session across NG, Xn, and E1 interfaces, enabling end-to-end connectivity between UE and data network.

Introduced
Rel-15
Where
Radio Access Network › NG-RAN (5G)
Specifications
5 specs
PDU session resource Description Purpose What changed Neighbours Detected Changes Specifications

Description

The PDU Session Resource is a foundational concept in 5G NR and NG-RAN architecture, representing the set of NG-RAN interface and radio resources that are established and managed to support a single PDU Session for a UE. A PDU Session itself provides connectivity between the UE and a Data Network (DN), such as the Internet or an operator-specific network, and is the 5G equivalent of the EPS bearer in 4G. The PDU Session Resource is the RAN-side realization of that session, encompassing the radio bearers, the NG-U tunnel resources between the gNB and the UPF, and the internal gNB resources (including CU-DU split resources over E1 and F1).

From an architectural perspective, the PDU Session Resource is established during the PDU Session Establishment procedure. The SMF, via the AMF, sends a PDU Session Resource Setup Request to the NG-RAN over the NG interface (N2). This request includes the PDU Session ID, the QoS Flow descriptions (including 5QI, ARP, and GFBR/MFBR), the UL TEID and transport layer address for the NG-U tunnel, and other parameters. The NG-RAN then allocates radio resources, configures the appropriate Data Radio Bearers (DRBs) and maps QoS Flows to DRBs according to the QoS requirements, and returns a PDU Session Resource Setup Response containing the DL TEID and transport layer address for the NG-U tunnel. This response also includes the list of established QoS Flows and any failed QoS Flows with cause values.

The PDU Session Resource is managed across multiple interfaces. Over the NG interface (N2), it is controlled via NGAP messages such as PDU Session Resource Setup, Modification, and Release. Over the Xn interface (Xn-C), it is managed during handover procedures via XnAP messages like Handover Request and Handover Request Acknowledge, which carry the PDU Session Resource to be admitted. Over the E1 interface (between CU-CP and CU-UP), the Bearer Context Management procedures in E1AP are used to set up, modify, and release the PDU Session Resource, including the associated DRBs and QoS Flows. The F1 interface (between CU and DU) also carries the PDU Session Resource information for the DU to configure the lower layers.

The PDU Session Resource concept enables flexible QoS handling in 5G. Unlike 4G EPS bearers, which were tightly coupled to radio bearers, 5G separates the PDU Session (the connectivity service) from the QoS Flows (the granular QoS treatment) and the DRBs (the radio transport). A single PDU Session Resource can support multiple QoS Flows, each with its own 5QI and QoS parameters, and these flows can be multiplexed onto one or more DRBs. This separation allows the RAN to dynamically manage radio resources based on the QoS requirements of each flow, improving spectral efficiency and user experience.

In summary, the PDU Session Resource is the central abstraction for managing user-plane connectivity in the 5G RAN. It is used across NG, Xn, and E1 interfaces to coordinate resource allocation, QoS enforcement, and mobility. Its proper management is essential for ensuring end-to-end service quality, seamless handovers, and efficient utilization of network resources.

Purpose & Motivation

The PDU Session Resource concept was introduced in 3GPP Release 15 as part of the 5G System architecture to provide a clear, standardized way to manage user-plane resources in the NG-RAN. In 4G LTE, the EPS bearer was the primary unit of resource management, but it was tightly coupled to the radio bearer and did not easily support the flexible QoS framework envisioned for 5G. The 5G QoS model introduced QoS Flows, which are more granular than bearers, and the PDU Session Resource was created to bridge the gap between the PDU Session (a logical connectivity service) and the underlying radio and transport resources.

The primary problem it solves is the need for a unified, interface-independent representation of the resources allocated to a PDU Session. Without such a concept, each interface (NG, Xn, E1) would need its own ad-hoc resource description, leading to interoperability issues and complex mapping. By defining the PDU Session Resource as a common abstraction, 3GPP ensures that the same resource information can be exchanged consistently across different interfaces, simplifying implementation and enabling multi-vendor interoperability.

Additionally, the PDU Session Resource supports the separation of control and user planes in the RAN (CU-CP/CU-UP split) by allowing the E1 interface to manage the user-plane resources independently. This enables flexible deployment options, such as centralized control and distributed user plane, which are key for network slicing and edge computing. The concept also facilitates mobility by allowing the source and target gNBs to negotiate the admission of PDU Session Resources during handover, ensuring QoS continuity.

What changed in its specifications

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

TS 38.401Rel-18 → Rel-19

Rel-19 adds Wireless Access Backhaul (WAB) architecture and node procedures to TS 38.401. It also adds multi-hop Layer-2 sidelink UE-to-Network relay with First, Intermediate and Last U2N Relay UE roles. Ambient IoT support is added, including A-IoT session contexts and AMF connectivity.

Full comparison in TS 38.401 →
TS 38.413Rel-18 → Rel-19

Rel-19 adds A-IoT procedures and messages, NTN aerial UE flight reporting, Geography Based MDT, and XR PDU Set and bitrate monitoring to TS 38.413. It also adds NG Removal and WAB-node definitions and MBS User Plane Failure Indication.

Full comparison in TS 38.413 →

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

Specific changes extracted from the „Change history“ tables of 3GPP specifications (17 CRs across 4 releases). Complements the general historical overview above with the evidence-based evolution of this function.

Rel-15 5 changes
  • Correction of ASN.1 for PDU Session Resource Modify Response TS 38.413CR0052
  • Correction of ASN.1 for SON Configuration Transfer and PDU Session Resource Modify Request Transfer TS 38.413CR0066
  • CR38413 for Clarification on PDU Session resource modify TS 38.413CR0071
  • XnAP Correction of PDU Session Resource Setup Response Info – MN terminated TS 38.423CR0112
  • XnAP Correction of PDU Session Resource Setup Complete Info – SN terminated TS 38.423CR0113
Rel-16 8 changes
  • Voice fallback triggered by PDU session resource setup TS 38.413CR0372
  • Correction of PDU Session Resource Modification TS 38.413CR0574
  • Correction on PDU Session Resource Setup procedure TS 38.413CR0735
  • PDU session resource in UE context release TS 38.413CR0337
  • Correction to PDU SESSION RESOURCE MODIFY CONFIRM TS 38.413CR0389
  • Clarification on an abnormal condition in PDU Session Resource Modify Procedure TS 38.413CR0505

+ 2 more changes

Rel-17 2 changes
  • Correction of Interaction with PDU Session Resource Indication TS 38.413CR1036
  • Correction of QoS Flow Mapping Indication IE in PDU Session Resource Modification Required Info - SN terminated TS 38.423CR1075
Rel-18 2 changes
  • Correction of selected NID in PDU Session Resource Setup Info - SN terminated TS 38.423CR1150
  • Correction of TSC Traffic Characteristics in the PDU Session Resource Modification Info - MN terminated TS 38.423CR1337

Defining Specifications

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

SpecificationTitleRelease
TS 37.483 vj40 E1 Application Protocol (E1AP) Rel-19 read
TS 38.401 vj30 NG-RAN Architecture Description Rel-19 read
TS 38.413 vj40 NG Application Protocol (NGAP) Specification Rel-19 read
TS 38.423 vj40 NG-RAN Xn Application Protocol Rel-19 read
TS 38.463 vj00 E1 Application Protocol (E1AP) Rel-19 read