Description
The NG User Plane interface (NG-U) is a logical interface in the 5G System (5GS) that connects the Next Generation Radio Access Network (NG-RAN) to the User Plane Function (UPF) in the 5G Core Network (5GC). It is responsible for the transport of user data packets (e.g., IP packets, Ethernet frames) between the UE and the Data Network (DN). NG-U is part of the overall NG interface, which also includes the control plane interface NG-C between the NG-RAN and the Access and Mobility Management Function (AMF). NG-U was introduced in 3GPP Release 19, although earlier releases defined the NG interface in general; Release 19 brought specific enhancements and clarifications for the user plane, as documented in TS 38.410 (NG-RAN overall description) and TS 38.912 (Study on New Radio access technology).
Architecturally, NG-U is established between a gNB (or ng-eNB) and a UPF. It is based on the GPRS Tunnelling Protocol for the User Plane (GTP-U), which encapsulates user data packets within GTP-U tunnels. Each PDU session or QoS flow is associated with a GTP-U tunnel identified by a Tunnel Endpoint Identifier (TEID). The NG-U interface supports multiple QoS flows per PDU session, allowing differentiated treatment of traffic. The interface is also used for the transport of Ethernet PDU sessions, enabling industrial IoT and other Ethernet-based services.
The operation of NG-U involves the establishment, modification, and release of GTP-U tunnels, which are controlled by the Session Management Function (SMF) via the N4 interface to the UPF, and by the AMF via NG-C to the NG-RAN. When a UE requests a PDU session, the SMF selects a UPF and allocates TEIDs for the uplink and downlink directions. These TEIDs are communicated to the NG-RAN via NG-C, and to the UPF via N4. The NG-RAN then uses the uplink TEID to send user data to the UPF, and the UPF uses the downlink TEID to send data to the NG-RAN. The NG-U interface also supports features like reflective QoS, where the UE marks packets based on downlink QoS flow information.
In Release 19, NG-U enhancements focus on supporting new services and improving efficiency. These include support for Multi-Path QUIC proxying (as per MPQUIC-UDP), which may involve the UPF acting as a proxy and using NG-U to transport the encapsulated traffic. Additionally, Release 19 may include optimizations for time-sensitive networking (TSN), reduced capability (RedCap) devices, and network slicing, ensuring that NG-U can handle diverse traffic types with appropriate QoS. The interface also supports the transport of small data transmissions for IoT devices, reducing signaling overhead.
Overall, NG-U is a fundamental interface in the 5G architecture, enabling the separation of control and user planes (CUPS) and allowing flexible deployment of UPFs. It ensures that user data can be efficiently routed from the RAN to the core and beyond, with the necessary QoS and security. Its evolution in Release 19 reflects the ongoing need to support new use cases and technologies in 5G-Advanced and beyond.
Purpose & Motivation
The NG-U interface exists to provide a standardized, efficient, and scalable means of transporting user data between the 5G radio access network and the 5G core network. In earlier generations, the user plane interface (e.g., S1-U in 4G) was tightly coupled with the control plane and had limited flexibility. With 5G, the architecture adopted a service-based, cloud-native approach with separation of control and user planes (CUPS). NG-U was defined to allow the UPF to be deployed flexibly, potentially at the edge or in a centralized data center, and to support diverse QoS requirements through multiple QoS flows per PDU session.
The motivation for NG-U also includes the need to support new services such as ultra-reliable low-latency communication (URLLC), enhanced mobile broadband (eMBB), and massive machine-type communication (mMTC). These services have varying requirements for latency, throughput, and reliability, which NG-U addresses by enabling per-flow QoS handling and efficient tunneling. The use of GTP-U provides a proven, interoperable tunneling mechanism that can be extended with features like Ethernet support and reflective QoS.
Release 19 enhancements to NG-U were driven by the emergence of new use cases like multi-path communication, time-sensitive networking, and the proliferation of IoT devices. The interface needed to evolve to support these without disrupting existing deployments. By specifying NG-U in TS 38.410 and TS 38.912, 3GPP ensures that vendors and operators have a clear reference for implementing and deploying the interface, fostering a competitive ecosystem.
Technology family
RAN interfaces · Radio Access Network
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 5 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.
NG-U user plane transport is specified for the first time in NGAP (TS 38413), covering NG-U UP TNL information, transport bearers and tunnel handling in PDU session resource setup, modify and handover procedures.
- “The purpose of the PDU Session Resource Setup procedure is to assign resources on Uu and NG-U for one or several PDU sessions” TS 38.413 v15.13.0
- “use it as the uplink termination point for the user plane data for this PDU session” TS 38.413 v15.13.0
- “if the GTP-U Error Indication was received from an UPF for a NG-U tunnel other than an indirect forwarding tunnel” TS 23.527 v15.3.0
NG-RAN behaviour on NG-U transport bearers was extended in Rel-16 with redundant and additional NG-U UP TNL information handling, covering setup, modify and indication procedures for redundant transmission and split PDU sessions.
- “if the Redundant UL NG-U UP TNL Information IE is included in the PDU Session Resource Setup Request Transfer IE” TS 38.413 v16.18.0
- “the NG-RAN node may allocate resources for a redundant NG-U transport bearer for some or all of the QoS flows” TS 38.413 v16.18.0
- Including the Redundant UL NG-U UP TNL Information in the Modify Request TS 38.413CR0520
Rel-17 adds NG-U handling for multicast MBS: Distribution Setup/Release procedures in NG-AP to set up and release shared NG-U transport, plus shared NG-U termination in E1AP.
- “The purpose of the Distribution Setup procedure is to assign NG-U resources for a multicast MBS session.” TS 38.413 v17.15.0
- “The purpose of the Distribution Release procedure is to enable the release of already established NG-U resources for a given multicast MBS session” TS 38.413 v17.15.0
- Correction on NG-U tunnel aspect for MBS session TS 37.483CR0058
NG-U gained user plane failure handling: a failed NG-U tunnel can be replaced with new DL NG-U UP TNL information, and GTP-U Error Indication over NG-U triggers PDU session release, plus shared NG-U for broadcast MBS.
- “the NG-RAN node shall, if supported, consider that the NG-U tunnel established for the PDU session experienced a user plane failure” TS 38.413 v18.11.0
- “consider that the PDU session is released due to GTP-U Error Indication received over the NG-U tunnel” TS 38.413 v18.11.0
- “The purpose of the Broadcast Session Transport procedure is to assign NG-U resources for a broadcast MBS session.” TS 38.413 v18.11.0
NG-RAN can react to an MBS User Plane Failure Indication of NG-U path failure by providing new NG-U transport information or releasing the failed one; a multicast NG-U replace request IE is added.
- “set to "NG-U path failure detected", the NG-RAN node may provide new NG-U transport layer information to replace the failed one” TS 38.413 v19.4.0
- “If the MC Bearer Context NG-U TNL Info at NG-RAN Replace Request IE is contained in the MC Bearer Context To Modify IE” TS 37.483 v19.4.0
Defining Specifications
3GPP specifications that define or reference NG-U, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 38.410 vj20 | NG-RAN; NG General Aspects and Principles | Rel-19 read |
| TR 38.912 vj00 | Study on New Radio Access Technology | Rel-19 read |