Radio Network Controller

Description

The Radio Network Controller (RNC) is a critical network element in the 3G Universal Terrestrial Radio Access Network (UTRAN) architecture. It operates as the controlling node for one or more base stations, known as Node Bs. The RNC is responsible for a comprehensive set of control and management functions for the radio resources and user mobility within its domain. Architecturally, the RNC connects to Node Bs via the Iub interface, to other RNCs via the Iur interface, and to the core network (Circuit Switched and Packet Switched domains) via the Iu interface. This positioning makes it the central intelligence of UTRAN, consolidating control from multiple Node Bs.

Functionally, the RNC's responsibilities are extensive. In Radio Resource Management (RRM), it performs tasks such as admission control, congestion control, handover control, and power control. It manages the allocation and release of radio bearers, including dedicated channels (DCH) and common channels like the Random Access Channel (RACH) and Forward Access Channel (FACH). For mobility, the RNC controls all handovers (soft, softer, hard) between cells under its control and coordinates with other RNCs for inter-RNC handovers via the Iur interface. It also handles macro diversity combining and splitting for soft handover connections. From a user plane perspective, the RNC performs ciphering and integrity protection for data and signaling, and it routes user data packets between the Iub and Iu interfaces. For the Control Plane, the RNC terminates the RRC protocol, managing the RRC connection states (IDLE, CELL_FACH, CELL_DCH, etc.) of the User Equipment (UE).

The RNC's role evolved but remained central throughout 3GPP Releases 99 to 14 for UMTS/HSPA networks. In later releases, with the introduction of HSPA+ and features like Continuous Packet Connectivity (CPC) and Enhanced CELL_FACH, the RNC's algorithms became more complex to improve efficiency and reduce latency. The RNC is a centralized element, which provided strong coordination benefits but also presented a potential bottleneck and single point of failure. This architecture contrasted with the flatter, more distributed architecture of 4G LTE, where the RNC functions were largely integrated into the eNodeB, leading to its eventual phase-out in 5G NR.

Purpose & Motivation

The RNC was created as part of the original UMTS architecture (3G) to provide a centralized control point for the radio access network. Prior to 3G, 2G GSM networks used a Base Station Controller (BSC) which served a similar purpose, managing multiple Base Transceiver Stations (BTSs). The RNC was designed to address the greater complexity of WCDMA-based UMTS, which introduced features like soft handover (where a UE is connected to multiple cells simultaneously), fast power control, and more dynamic radio resource management.

The centralized RNC model solved several problems. It allowed for efficient macro diversity combining for soft handover, which required a central point to combine signals from multiple Node Bs. It enabled sophisticated RRM algorithms that could consider the resource status of multiple cells under its control. It also simplified the Node B design, making it a relatively dumb radio unit, which was advantageous from a cost and deployment perspective in the early 2000s. The RNC acted as a single point of contact for the core network, hiding the mobility and radio complexity of UTRAN. However, this centralization also introduced latency, especially for user plane data which had to be routed through the RNC. The evolution towards HSPA, which demanded lower latency, began to push some functions closer to the Node B, setting the stage for the fully distributed architecture of LTE.

Key Features

• Centralized controller for one or more Node B base stations in UTRAN
• Terminates the Radio Resource Control (RRC) protocol for UEs
• Manages all handover types (soft, softer, hard) and macro diversity combining
• Performs Radio Resource Management (RRM) including admission, power, and congestion control
• Provides ciphering and integrity protection for user and control plane data
• Interfaces with core network via Iu interface and with other RNCs via Iur interface

Evolution Across Releases

Defining Specifications