Description
The ng-eNB Central Unit (ng-eNB-CU) is a logical node in the NG-RAN architecture introduced in 3GPP Release 15. An ng-eNB is an E-UTRA base station connected to the 5G Core Network via the NG interface, and the ng-eNB-CU is its central unit in a split architecture. According to TS 38.401, the ng-eNB-CU is a logical node hosting the Radio Resource Control (RRC), Service Data Adaptation Protocol (SDAP), and Packet Data Convergence Protocol (PDCP) layers. The lower layers (RLC, MAC, and PHY) are hosted in one or more ng-eNB Distributed Units (ng-eNB-DUs), connected to the CU via the F1 interface.
The split architecture separates the central, control-oriented, and higher-protocol functions from the distributed, latency-sensitive, lower-protocol functions. The ng-eNB-CU terminates the NG interface toward the 5G Core (including the control plane NG-C and user plane NG-U), and it terminates the F1 interface toward the DUs. It may be further split into a Control Plane (ng-eNB-CU-CP) hosting RRC and the control portion of PDCP, and a User Plane (ng-eNB-CU-UP) hosting SDAP and the user plane portion of PDCP, connected via the E1 interface. This functional split enables centralized coordination of radio resource management, mobility, and security while distributing radio processing closer to the antennas.
In operation, the ng-eNB-CU performs RRC connection management, including connection establishment, reconfiguration, and release; it handles mobility within and across ng-eNBs and toward gNBs via the Xn interface; and it manages security activation and key handling. The SDAP layer maps QoS flows from the 5G Core to data radio bearers, marking reflective QoS and handling flow-to-bearer mapping. The PDCP layer provides ciphering, integrity protection, header compression, and reordering. By centralizing these functions, the CU enables coordinated multi-cell decisions and reduces the complexity and cost of distributed units.
The ng-eNB-CU is defined in TS 38.401, the NG-RAN architecture specification, and its E-UTRA-specific aspects are further detailed in TS 37.470, which covers E-UTRA-NR dual connectivity and related split architecture details. The reference in the Release 16 and later definitions to TS 37.470 reflects the maturation of the specification, where the detailed functional and interface requirements for the ng-eNB-CU were consolidated. The CU connects to DUs over F1, to other RAN nodes over Xn, and to the 5G Core over NG, forming a key element of the NG-RAN for operators deploying E-UTRA radio access with a 5G core.
The ng-eNB-CU matters because it allows operators to deploy E-UTRA radio access in a 5G core network with a flexible, cloud-friendly architecture. Centralizing RRC, SDAP, and PDCP supports centralized RRM, efficient mobility, and pooling of control-plane resources, while the distributed units handle the real-time radio processing. This architecture is also foundational for dual connectivity and interworking between E-UTRA and NR, enabling tight coordination between ng-eNBs and gNBs.
Purpose & Motivation
The ng-eNB-CU exists to bring the benefits of a centralized-distributed RAN architecture to E-UTRA base stations connected to the 5G Core. In earlier LTE deployments, the eNB was typically a monolithic node, which limited flexibility in deployment, scaling, and coordination. As 5G introduced the NG-RAN with a split gNB architecture (gNB-CU and gNB-DU), a corresponding split was needed for ng-eNBs so that E-UTRA access could participate in the same architectural model, sharing centralized control functions and distributed radio processing.
The split addresses practical deployment constraints. Centralizing RRC, SDAP, and PDCP allows pooling of control-plane processing and coordinated radio resource management across many cells, while distributing RLC, MAC, and PHY places latency-critical processing near the antennas. This supports cloud-based deployment of the CU, reduces site costs, and enables flexible scaling. It also facilitates dual connectivity and interworking with NR, since centralized PDCP anchoring is essential for split bearers and mobility across radio technologies.
The concept was introduced in Release 15 alongside the 5G NG-RAN architecture and refined in later releases. The Release 16 wording change, which added a reference to TS 37.470, reflects the consolidation of detailed E-UTRA split architecture requirements into a dedicated specification, providing a stable normative basis for multi-vendor CU/DU implementations.
What changed in its specifications
The latest release-to-release comparison of specifications that define ng-eNB Central Unit (ng-eNB-CU). Each summary describes the whole specification, not only this term.
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 →Release Timeline
Evolution Across Releases
An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.
Defining Specifications
3GPP specifications that define or reference ng-eNB Central Unit (ng-eNB-CU), with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 37.876 vf00 | Study on E-UTRAN CU-DU Split Architecture | Rel-15 read |
| TS 38.401 vj30 | NG-RAN Architecture Description | Rel-19 read |