Description
The gNB-CU-Control Plane (gNB-CU-CP) is a fundamental logical node in the 3GPP 5G NR architecture, introduced in Release 15 as part of the centralized unit (CU) and distributed unit (DU) functional split. It is responsible for hosting the Radio Resource Control (RRC) protocol and the control plane portion of the Packet Data Convergence Protocol (PDCP). This separation allows for flexible deployment scenarios where the control plane functions can be centralized while user plane functions are distributed, optimizing network performance and resource utilization.
Architecturally, the gNB-CU-CP terminates two critical interfaces: the E1 interface, which connects it to the gNB-CU-User Plane (gNB-CU-UP), and the F1-C interface, which connects it to the gNB-DU. The E1 interface facilitates the exchange of control information between the control and user plane parts of the CU, enabling coordinated management of user data flows. The F1-C interface carries control signaling between the CU and DU, supporting functions such as UE context management, paging, and system information broadcasting. This interface architecture is defined in 3GPP TS 38.401 and TS 28.540.
In dual connectivity (DC) operations, the gNB-CU-CP takes on specific roles depending on whether the node acts as a master or secondary node. The MgNB-CU-CP designates the gNB-CU-CP of a gNB or en-gNB acting as the master node, while the SgNB-CU-CP designates the gNB-CU-CP of a node acting as the secondary node. This distinction is crucial for managing radio resources and mobility across multiple cells and radio access technologies, ensuring seamless connectivity and efficient handover procedures.
The gNB-CU-CP plays a pivotal role in the overall network architecture by centralizing control plane functions, which simplifies network management and reduces latency for control signaling. It enables advanced features such as network slicing, where different slices can have tailored control plane policies, and supports the integration of 4G and 5G networks through EN-DC (E-UTRA-NR Dual Connectivity). By decoupling control and user plane functions, the gNB-CU-CP facilitates scalable and flexible deployments, allowing operators to adapt to varying traffic demands and service requirements.
From a protocol perspective, the gNB-CU-CP handles RRC messages, which are essential for connection establishment, reconfiguration, and release. It also manages the control plane aspects of PDCP, including ciphering and integrity protection for signaling radio bearers. The node interacts with the Access and Mobility Management Function (AMF) in the 5G Core via the N2 interface, ensuring that control plane signaling is properly routed and managed. This integration with the core network is vital for supporting features like mobility management, session management, and policy control.
Purpose & Motivation
The gNB-CU-CP was created to address the need for a flexible and scalable radio access network architecture in 5G. Traditional monolithic base stations (e.g., eNodeB in LTE) combined all protocol layers in a single unit, which limited deployment flexibility and made it difficult to adapt to diverse service requirements. The CU/DU split introduced in 5G NR allows for centralization of control plane functions, reducing the cost and complexity of deploying and managing radio access networks.
By separating the control plane from the user plane, the gNB-CU-CP enables independent scaling and optimization of control and user plane resources. This is particularly important for handling massive machine-type communications (mMTC) and ultra-reliable low-latency communications (URLLC), where control signaling and user data have different performance requirements. The gNB-CU-CP also facilitates dual connectivity, allowing devices to connect simultaneously to multiple cells, which improves throughput and reliability.
Historically, the limitations of previous approaches included rigid hardware dependencies and inefficient use of network resources. The gNB-CU-CP, along with the overall CU/DU split, addresses these by promoting virtualization and cloud-based deployments. It allows operators to deploy control plane functions in centralized data centers, while user plane functions can be placed closer to the edge for latency-sensitive applications. This architectural evolution is a cornerstone of 5G's ability to support diverse use cases and network slicing.
What changed in its specifications
The latest release-to-release comparison of specifications that define gNB-CU-Control Plane (gNB-CU-CP). Each summary describes the whole specification, not only this term.
Rel-19 adds management clauses for Ambient IoT, IAB nodes, and regenerative NTN with UE-Satellite-UE communication. It also shifts NTN responsibility from 5GC to 3GPP.
Full comparison in TS 28.540 →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 gNB-CU-Control Plane (gNB-CU-CP), with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 28.540 vk40 | 5G Network Resource Model (NRM) Stage 1 | Rel-20 read |
| TS 38.401 vj30 | NG-RAN Architecture Description | Rel-19 read |