Description
The ng-eNB Distributed Unit (ng-eNB-DU) is a logical node within the NG-RAN architecture that hosts the lower layers of the LTE radio protocol stack — specifically the Radio Link Control (RLC), Medium Access Control (MAC), and Physical (PHY) layers. It is defined in 3GPP TS 37.876 and referenced in TS 38.401 as part of the overall NG-RAN architecture. The ng-eNB-DU exists because 3GPP introduced a functional split of the base station into a Centralized Unit (CU) and a Distributed Unit (DU) starting in Release 15, allowing network operators to deploy radio functions with different degrees of centralization.
The ng-eNB-DU connects to the ng-eNB Centralized Unit (ng-eNB-CU) over the F1 interface, which is specified in TS 38.470 and its application protocol part TS 38.473. The F1 interface carries control plane signalling (F1-C) and user plane data (F1-U). The DU is responsible for real-time, latency-critical radio functions such as scheduling, HARQ management, modulation and coding, and physical layer processing, while the CU handles non-real-time functions like RRC, SDAP, and PDCP. This split allows the DU to be placed close to the antenna site, while the CU can be centralized in an edge cloud or regional data center.
In the NG-RAN, an ng-eNB is the LTE base station variant that connects to the 5G Core (5GC) via the NG interface. When the ng-eNB is split into CU and DU, the DU terminates the F1 interface toward the CU and the lower radio protocols toward the UE. The DU may control one or more cells and manages the radio resources of those cells. It interacts with the CU through F1AP procedures for UE context setup, modification, and release, as well as for paging, system information delivery, and cell configuration management.
The functional split between CU and DU is motivated by deployment flexibility, cost efficiency, and the ability to centralize functions that benefit from coordination across multiple cells (such as dual connectivity and carrier aggregation coordination) while keeping latency-sensitive functions distributed. The ng-eNB-DU is a key building block for operators who want to reuse LTE radio infrastructure while integrating with 5G core networks, and for scenarios where centralized RAN (C-RAN) or cloud RAN (vRAN) architectures are deployed.
From a protocol perspective, the ng-eNB-DU terminates the F1-C and F1-U interfaces, the Uu radio interface toward the UE for the RLC/MAC/PHY layers, and participates in cell-level and UE-level management procedures. It does not terminate RRC or PDCP — those reside in the ng-eNB-CU. This separation means that the DU must support the F1AP and GTP-U protocols for control and user plane transport respectively, and must maintain synchronization and timing alignment with the CU for correct operation.
Purpose & Motivation
The ng-eNB-DU exists to enable a flexible, split base station architecture in which LTE radio functions can be distributed and centralized independently. Before Release 15, LTE base stations (eNBs) were monolithic nodes that combined all protocol layers in a single physical entity. This limited deployment flexibility, made it difficult to centralize coordination functions, and constrained operators' ability to build cloud RAN architectures.
By splitting the ng-eNB into a CU and a DU, 3GPP allows operators to place latency-critical radio processing (RLC, MAC, PHY) close to the antenna, while centralizing non-real-time functions (RRC, PDCP, SDAP) in a data center. This reduces site footprint and power consumption at the radio site, enables pooling of centralized resources, and supports coordinated multipoint and dual connectivity features that benefit from centralized scheduling decisions.
The ng-eNB-DU specifically addresses the need to integrate LTE radio access with the 5G Core. As operators migrate from EPC to 5GC, ng-eNBs provide LTE coverage under the 5G architecture. The DU allows this LTE coverage to be delivered with the same flexible, cloud-native deployment model that gNBs use, ensuring a consistent operational model across 4G and 5G radio access.
What changed in its specifications
The latest release-to-release comparison of specifications that define ng-eNB Distributed Unit (ng-eNB-DU). 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 Distributed Unit (ng-eNB-DU), 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 |