Control Unit

Description

The Control Unit (CU) is a logical node defined within the 3GPP Next Generation Radio Access Network (NG-RAN) architecture, specifically as part of the gNB (5G NodeB) or ng-eNB. It represents the centralized control plane entity in the disaggregated RAN model. The CU is responsible for hosting the Radio Resource Control (RRC) protocol and the Service Data Adaptation Protocol (SDAP) for the control plane. It performs critical functions such as connection management, mobility management, radio bearer control, and inter-cell interference coordination. By centralizing these intelligence-heavy functions, the CU enables more efficient resource pooling and coordination across a wider geographical area covered by multiple Distributed Units (DUs).

Architecturally, the CU connects to the 5G Core Network (5GC) via the NG interface and to one or more DUs via the F1 interface, as standardized in 3GPP. The F1 interface is further split into the F1-C (control plane) and F1-U (user plane) parts. The CU terminates the F1-C interface, through which it sends control messages to configure and manage the DUs. This split architecture allows the CU to be deployed in a more centralized location, such as a regional data center, while DUs remain at cell sites. The CU can be implemented as a software function running on commercial off-the-shelf (COTS) hardware, facilitating network function virtualization (NFV) and cloud-native principles.

From an operational perspective, the CU handles the non-real-time layer 3 protocols and functions. When a User Equipment (UE) initiates a connection, the CU is responsible for the RRC procedures, including broadcast of system information, paging, RRC connection establishment, reconfiguration, and release. It makes handover decisions based on measurement reports from the UE and coordinates the handover execution with the source and target DUs. The CU also manages the Quality of Service (QoS) flows by mapping them to Data Radio Bearers (DRBs) in coordination with the core network's Session Management Function (SMF). Its centralized nature is crucial for implementing advanced features like Coordinated Multi-Point (CoMP) transmission/reception and Dual Connectivity (DC).

The introduction of the CU is a fundamental shift from the monolithic base station design. It decouples the evolution of control plane software from the hardware-dependent, real-time processing of the physical layer and parts of the MAC layer, which reside in the DU. This separation provides significant deployment flexibility. Network operators can choose a CU-DU split based on fronthaul latency and bandwidth constraints, with options for a more centralized CU (supporting many DUs) or a more distributed deployment. The CU's software-based nature also simplifies upgrades, scaling, and the introduction of new services, making it a cornerstone for open RAN (O-RAN) initiatives and network slicing in 5G.

Purpose & Motivation

The CU was introduced to address the limitations of traditional, integrated base stations (NodeBs and eNodeBs) which bundled all radio protocol layers into a single, site-located unit. This monolithic architecture made networks rigid, difficult to scale, and costly to upgrade. The primary motivation for creating the CU was to enable a more flexible, efficient, and cost-effective RAN through functional disaggregation. By separating the control plane (CU) from the user plane and lower-layer processing (DU), operators gain the ability to centralize intelligence, pool resources, and leverage cloud economics. This split is essential for meeting the diverse and demanding requirements of 5G, such as enhanced Mobile Broadband (eMBB), Ultra-Reliable Low-Latency Communications (URLLC), and massive Machine-Type Communications (mMTC).

Historically, each base station operated largely independently, with coordination limited to standardized interfaces like X2 in LTE. This made network-wide optimization and the implementation of advanced features like coordinated scheduling complex and inefficient. The CU-centric architecture provides a natural point for centralized control and optimization algorithms that can manage radio resources across dozens or hundreds of cell sites simultaneously. It solves the problem of inefficient resource utilization and suboptimal interference management in dense network deployments. Furthermore, it addresses the operational expenditure (OPEX) challenge by allowing software updates and new feature rollouts to be applied centrally at the CU, rather than requiring manual updates at every cell site.

The creation of the CU was also driven by the industry's move towards virtualization and open interfaces. It enables the RAN to align with the broader telco cloud transformation, where network functions are software-defined and run on general-purpose hardware. This openness, exemplified by the standardized F1 interface between CU and DU, fosters multi-vendor interoperability and innovation. It allows operators to source CU and DU software from different suppliers, breaking vendor lock-in and promoting a competitive ecosystem. Ultimately, the CU exists to future-proof mobile networks, providing an architectural foundation that is scalable, agile, and capable of supporting evolving service demands and new technological paradigms like network slicing and AI-driven RAN optimization.

Key Features

• Hosts the Radio Resource Control (RRC) and SDAP control plane protocols
• Centralizes connection and mobility management for multiple Distributed Units (DUs)
• Terminates the F1 control plane (F1-C) interface towards DUs
• Enables network-wide radio resource optimization and coordination
• Facilitates software-based deployment and upgrades via virtualization
• Provides the control plane anchor for network slicing and QoS flow management

Evolution Across Releases

Defining Specifications