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.
What changed in its specifications
The latest release-to-release comparison of specifications that define RNC. Each summary describes the whole specification, not only this term.
Rel-18 brings only minor changes to TS 21.905: 0 clauses changed, with no change attributed to a release feature.
Full comparison in TR 21.905 →Rel-19 brings only minor changes to TS 23.009: 0 clauses changed, with no change attributed to a release feature.
Full comparison in TS 23.009 →Evolution Lineage
- Evolved from: BSC (2G→3G)
- Succeeded by: eNB (3G→4G)
- Network evolution overview →
Technology family
Base stations and RAN nodes · Radio Access Network
- Phase 1 BSC, BSS, BTS
- R99 Node B, RNC, RNS
- Rel-8 eNB, HeNB, HNB, HNB-GW
- Rel-10 DeNB, HeNB-GW, RN
- Rel-15 en-gNB, gNB, gNB-CU, gNB-CU-CP, gNB-CU-UP, gNB-DU, ng-eNB
- Rel-16 IAB-donor, IAB-DU, IAB-MT, IAB-node
- Rel-18 Mobile IAB-node
- RNC counterpart in another generation: BSC
“BSC/SRNC: the BSC for GERAN and SRNC for UTRAN receive authenticated location requests from the CN” TS 23.002
- RNC part of RNS
“The RNS consists of one Radio Network Controller (RNC) and one or more Node B.” TS 23.002
- RNC used together with Node B
“The RNS consists of one Radio Network Controller (RNC) and one or more Node B.” TS 23.002
Members and relations were proposed independently by several models and kept only where at least two agree; quotes are verified verbatim against the specifications. Release = first approved version of the defining specification.
Release Timeline
Detected Changes Across Releases
verified against 3GPP sourcesDocumented changes in 14 releases, each verified against the text of 3GPP specifications or approved change requests and shown with the exact wording. The release timeline above shows the same releases. A release without an entry has no documented change for this term.
The RNC is defined for the first time as the logical node in the RNS controlling radio resources, with Controlling/Serving/Drift roles, Iu/Iub interfaces and RAB assignment and SRNS relocation procedures.
- “Radio Network Controller: logical node in the RNS in charge of controlling the use and the integrity of the radio resources” TS 25.401 v3.10.0
- “The Controlling RNC has the overall control of the logical resources of its node B's.” TS 25.401 v3.10.0
- “The RNC shall pass the contents of RAB ID IE to the radio interface protocol for each RAB requested to establish or modify.” TS 25.413 v3.14.0
RNC behaviour changed in RANAP and relocation procedures: it must initialise the user plane before reporting RAB success, fail with 'RNC unable to establish all RFCs', and apply default priority and response-time values for location requests.
- “If the RNC can not initialise the requested user plane mode for any of the user plane mode versions in the UP Mode Versions IE” TS 25.413 v4.12.0
- “When no Positioning Priority IE is included, the RNC shall consider the request as if “Normal Priority” value had been received.” TS 25.413 v4.12.0
- “The source RNC shall start the data-forwarding timer.” TS 23.060 v4.11.0
RNC gained new roles in Rel-5: connection to a standalone A-GPS SAS over Iupc and to GERAN BSS over Iur-g, with RNC identifiers now unique across UTRAN and GERAN Iu mode.
- “the RNC may have full internal support for this function and/or may be connected to one SAS via the Iupc interface.” TS 25.401 v5.10.0
- “The RNC may be connected to BSS supporting GERAN Iu mode via the Iur-g interface.” TS 25.401 v5.10.0
- “An RNC node is uniquely identified by its RNC Identifier among the nodes in UTRAN and GERAN Iu mode” TS 25.401 v5.10.0
RNC behaviour changed in Rel-6: it performs MBMS UE linking/de-linking, stores trace session information at relocation, and handles relocation RABs and the selected PLMN ID differently; E-DCH MAC-es reordering is placed in the RNC.
- “the RNC shall, if supported, use the CN MBMS Linking Information IE to perform suitable UE linking as described in [42].” TS 25.413 v6.16.0
- “the target RNC shall use this information to send it to the UE.” TS 25.413 v6.16.0
- “E-DCH scheduling is performed by MAC-e in the Node B and reordering is performed by MAC-es in the RNC.” TS 25.401 v6.9.0
RNC behaviour changed in Rel-7: it must consider and use the Extended Maximum/Guaranteed Bit Rate IEs in RAB setup and modification, ignoring the legacy bit rate IEs when the extended ones are present.
- “if the Extended Maximum Bit Rate IE (respectively Extended Guaranteed Bit Rate IE) is present, the RNC shall consider it and ignore the Maximum Bit Rate IE” TS 25.413 v7.10.0
- “If the Selected PLMN identity IE is contained in the RELOCATION REQUEST message, the target RNC shall use this information to send it to the UE.” TS 25.413 v7.10.0
- “The RNC shall indicate the Cause IE set to "GTP Resources Unavailable" for the reasons specified in [21].” TS 25.413 v7.10.0
RNC procedures changed in Rel-8: it must handle extended and supported bit rate IEs in RAB assignment, may start enhanced relocation, and collects UE history information.
- “the RNC shall consider it and ignore the Maximum Bit Rate IE (respectively Guaranteed Bit Rate IE).” TS 25.413 v8.8.0
- “The RNC shall either invoke relocation by sending a RELOCATION REQUIRED message to the active CN node(s) or enhanced relocation” TS 25.413 v8.8.0
- “the target RNC shall collect the same type of information as that included in the UE History Information IE.” TS 25.413 v8.8.0
RNC behaviour changed in Rel-9: it handles CSG Id/membership during relocation (target RNC validates CSG Id, accepts only emergency bearers for non-members) and stores the SPID for RAT/Frequency priority.
- “If the CSG Id IE is received in the RELOCATION REQUEST message, the UTRAN shall validate it by comparing it with the CSG ID broadcast by the target cell.” TS 25.413 v9.10.0
- “the target RNC shall store the received Subscriber Profile ID for RAT/Frequency priority and use it as defined in TS 36.300 [52].” TS 25.413 v9.10.0
- “If the target cell is a CSG cell, and if the CSG Membership Indication is "non member", the target RNC only accepts the emergency bearers.” TS 23.060 v9.14.0
The RNC gained new behaviour in Rel-10: handling MDT configuration in CN INVOKE TRACE, and ECN-based congestion marking of PDCP SDUs in uplink and downlink.
- “then the RNC shall, if supported, initiate the requested trace function and MDT function as described in TS 32.422 [38].” TS 25.413 v10.10.0
- “The RNC should set the Congestion Experienced (CE) codepoint ('11') in PDCP SDUs in the downlink direction to indicate downlink (radio) congestion” TS 25.401 v10.2.0
- “the RNC shall ignore the MDT Configuration.” TS 25.413 v10.10.0
RNC behaviour changed in Rel-11: it may trigger Extended Access Barring, handles extended RNC-ID, and has new handover/relocation rules such as not triggering E-UTRAN handover for signalling-only UEs.
- “The RNC shall not trigger handover or redirection to E-UTRAN for a UE with a signaling connection only;” TS 25.413 v11.6.0
- “The RNC may trigger EAB as specified in TS 23.060 [36] subclause 5.3.6.4 and TS 23.251[28] subclause 4.6.” TS 25.401 v11.1.0
- “In case of rSRVCC operation, the RNC shall only initate the Relocation Preparation procedure on the Iu-CS signalling connections existing for the UE.” TS 25.413 v11.6.0
RNC behaviour changed: it must use the SIPTO Correlation ID for SIPTO@LN, fail RABs carrying both correlation IDs, and the target RNC includes the Local Home Network ID in Relocation Complete.
- “the RNC shall use it for SIPTO@LN operation for the concerned RAB.” TS 25.413 v12.4.0
- “the RNC shall consider the establishment of the corresponding RAB as failed.” TS 25.413 v12.4.0
- “the target RNC shall include the Local Home Network ID of the target cell in the Relocation Complete message.” TS 23.060 v12.11.0
RNC gained new Rel-13 behaviour: storing the Power Saving Indicator, rerouting NAS to a DCN on SGSN request, and a new UE Registration Query procedure for CS/PS coordination in MOCN.
- “The RNC shall, if supported, reroute the INITIAL UE MESSAGE message to the DCN indicated by the SGSN Group Identity IE.” TS 25.413 v13.2.0
- “The RNC initiates the procedure by sending a UE REGISTRATION QUERY REQUEST message to one of the CN domains.” TS 25.413 v13.2.0
- “the RNC shall if supported, store this information and use it when determining to send the UE back to the PSM mode” TS 25.413 v13.2.0
RNC gained QoE/UE application layer measurement handling: storing configuration at relocation, initiating QoE on trace, reporting capability in INITIAL UE MESSAGE, and selecting SGSN by DCN-ID.
- “the RNC shall, if supported, initiate the requested trace function and QoE function as described in TS 25.300 [72].” TS 25.413 v14.1.0
- “the RNC shall if supported include the UE Application Layer Measurement Capability IE in the INITIAL UE MESSAGE message.” TS 25.413 v14.1.0
- “RNC selects serving SGSN based on the DCN-ID provided by the UE and the configuration in RNC” TS 25.401 v14.0.0
Target RNC may store and consider that SRVCC is from 5G to 3G when the SRVCC Source IE is present in the Source RNC to Target RNC Transparent Container.
- “the target RNC may store and consider that the SRVCC is from 5G to 3G” TS 25.413 v16.0.0
Defining Specifications
3GPP specifications that define or reference RNC, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TR 21.905 vj20 | 3GPP Terminology and Definitions | Rel-19 read |
| TR 22.980 vj00 | Network Composition Feasibility Study | Rel-19 read |
| TS 23.009 vj00 | Handover Procedures in PLMNs | Rel-19 read |
| TS 23.060 vj00 | GPRS Stage 2 Service Description | Rel-19 read |
| TS 23.171 v390 | LCS Stage 2 for UMTS | R99 read |
| TS 23.207 vj00 | End-to-End QoS Framework for GPRS | Rel-19 read |
| TS 23.221 vj00 | 3GPP System Architectural Requirements | Rel-19 read |
| TS 23.236 vj00 | Intra Domain Connection of RAN Nodes to Multiple CN Nodes | Rel-19 read |
| TS 23.251 vj00 | Network Sharing Stage 2 Specification | Rel-19 read |
| TS 23.271 vj00 | LCS Stage 2 Specification | Rel-19 read |
| TS 23.802 v700 | Enhanced End-to-End QoS Architecture | Rel-7 read |
| TS 23.851 v610 | Network Sharing Architecture for 3G Systems | Rel-6 read |
| TR 23.923 v300 | Mobile IP+ Feasibility Study for UMTS/GPRS | R99 read |
| TS 25.123 vj00 | Radio Resource Management for TDD | Rel-19 read |
| TS 25.133 vj00 | UTRAN RRM Requirements for FDD | Rel-19 read |
| TS 25.211 vj00 | UTRA FDD Layer 1: Transport & Physical Channels | Rel-19 read |
| TS 25.301 vj00 | UE-UTRAN Radio Interface Protocol Architecture | Rel-19 read |
| TS 25.302 vj00 | UTRA Physical Layer Services | Rel-19 read |
| TS 25.305 vj00 | UTRAN UE Positioning Stage 2 | Rel-19 read |
| TS 25.321 vj00 | MAC Protocol Specification for UTRAN | Rel-19 read |
| TS 25.323 vj00 | Packet Data Convergence Protocol (PDCP) Specification | Rel-19 read |
| TS 25.331 vj01 | UTRAN Radio Resource Control Protocol | Rel-19 read |
| TS 25.401 vj00 | UTRAN Overall Architecture | Rel-19 read |
| TS 25.402 vj00 | UTRAN Synchronisation Mechanisms | Rel-19 read |
| TS 25.410 vj00 | Iu Interface Introduction for UTRAN | Rel-19 read |
| TS 25.412 vj00 | Iu Interface Signalling Transport Specification | Rel-19 read |
| TS 25.413 vj00 | Radio Access Network Application Part (RANAP) | Rel-19 read |
| TS 25.414 vj00 | UTRAN Iu Interface User Plane Transport Protocols | Rel-19 read |
| TS 25.419 vj00 | Service Area Broadcast Protocol (SABP) | Rel-19 read |
| TS 25.420 vj00 | Iur Interface Introduction for UTRAN | Rel-19 read |
| TS 25.422 vj00 | Signalling Transport for Iur Interface | Rel-19 read |
| TS 25.423 vj00 | UTRAN RNSAP Specification | Rel-19 read |
| TS 25.425 vj00 | UTRAN Iur Interface User Plane Protocols | Rel-19 read |
| TS 25.430 vj00 | Introduction to Iub Interface Specifications | Rel-19 read |
| TS 25.432 vj00 | Iub NBAP Signalling Transport Specification | Rel-19 read |
| TS 25.433 vj00 | Node B Application Part (NBAP) Protocol | Rel-19 read |
| TS 25.434 vj00 | UTRAN Iub Interface Data Transport and Signalling | Rel-19 read |
| TS 25.442 vj00 | Node B Implementation Specific O&M Transport via RNC | Rel-19 read |
| TS 25.450 vj00 | Iupc Interface Introduction for UTRAN Positioning | Rel-19 read |
| TS 25.452 vj00 | Iupc Interface Signalling Transport for PCAP | Rel-19 read |
| TS 25.453 vj00 | PCAP Protocol Specification | Rel-19 read |
| TS 25.703 vc00 | HNB Emergency Warning Area Study for UTRA | Rel-12 read |
| TS 25.766 vd10 | UMTS Network-Assisted Interference Cancellation | Rel-13 read |
| TS 25.874 vb00 | HSPA Feedback and Signalling Enhancements | Rel-11 read |
| TR 25.931 vj00 | UTRAN Signalling Procedures Examples | Rel-19 read |
| TR 25.993 vj00 | UTRA RAB Examples and Radio Interface Mapping | Rel-19 read |
| TR 26.937 vj00 | 3GPP PSS Characterization | Rel-19 read |
| TS 28.062 vj00 | Tandem Free Operation (TFO) Service Description | Rel-19 read |
| TS 28.622 vk40 | Generic Network Resource Information Service | Rel-20 read |
| TS 28.652 vj00 | UTRAN Network Resource Model (NRM) IRP Information Service | Rel-19 read |
| TS 28.655 vj00 | GERAN NRM IRP Information Service | Rel-19 read |
| TS 28.732 vj00 | Transport Network NRM IRP Information Service | Rel-19 read |
| TS 28.734 vj00 | STN Interface NRM IRP Requirements | Rel-19 read |
| TS 29.060 vj00 | GPRS Tunnelling Protocol (GTP) version 1 | Rel-19 read |
| TS 29.108 vj00 | RANAP on E-interface for 3G MSC Relocation | Rel-19 read |
| TS 29.281 vj20 | GTPv1-U Protocol Specification | Rel-19 read |
| TS 32.101 vj00 | PLMN Management Principles and Requirements | Rel-19 read |
| TS 32.102 vj00 | Telecom Management Physical Architecture Framework | Rel-19 read |
| TS 32.240 vk10 | 3GPP Charging Architecture and Principles | Rel-20 read |
| TS 32.250 vj00 | Circuit Switched Offline Charging | Rel-19 read |
| TS 32.251 vj00 | PS Domain Charging Management | Rel-19 read |
| TS 32.272 vj00 | Charging for Push-to-Talk over Cellular (PoC) | Rel-19 read |
| TS 32.293 vj00 | Proxy Function in Domestic Service Provider | Rel-19 read |
| TS 32.401 vj00 | Performance Management Concept & Requirements | Rel-19 read |
| TS 32.404 vj00 | Performance Management Definitions & Template | Rel-19 read |
| TS 32.405 vj00 | UTRAN Performance Measurements Specification | Rel-19 read |
| TS 32.406 vj00 | Performance Management for CN PS Domain | Rel-19 read |
| TS 32.407 vj00 | PM; CN CS Domain; UMTS/GSM measurements | Rel-19 read |
| TS 32.583 vj00 | HNB OAM&P Procedure Flows for Type 1 Interface | Rel-19 read |
| TS 32.600 vj00 | 3GPP Configuration Management Specification | Rel-19 read |
| TS 32.611 vj00 | Bulk CM IRP Requirements | Rel-19 read |
| TS 32.622 vb10 | Generic Network Resources NRM | Rel-11 read |
| TS 32.641 vb00 | UTRAN Network Resources IRP Requirements | Rel-11 read |
| TS 32.642 vb50 | UTRAN Network Resource Model | Rel-11 read |
| TS 32.652 vc00 | GERAN Network Resources NRM for Configuration Management | Rel-12 read |
| TS 32.712 vb10 | Transport Network NRM Information Service | Rel-11 read |
| TS 32.741 vb00 | STN Interface NRM IRP Requirements | Rel-11 read |
| TS 32.833 vb00 | Fixed-Mobile Convergence Management Study | Rel-11 read |
| TS 32.856 vf00 | Energy Efficiency Assessment for RAN OAM | Rel-15 read |
| TS 33.105 vj00 | 3G Security: Cryptographic Algorithm Requirements | Rel-19 read |
| TS 33.859 vb10 | UTRAN Key Hierarchy Study | Rel-11 read |
| TS 35.205 vj00 | MILENAGE Algorithm Set: General Overview | Rel-19 read |
| TR 35.909 vj00 | 3GPP MILENAGE Algorithm Design Report | Rel-19 read |
| TR 35.934 vj00 | Tuak algorithm set for 3GPP auth & key gen | Rel-19 read |
| TS 36.133 vj60 | LTE Radio Resource Management Requirements | Rel-19 read |
| TS 36.300 vj20 | E-UTRAN Radio Interface Protocol Architecture | Rel-19 read |
| TS 37.320 vj40 | MDT Overall Description (Stage 2) | Rel-19 read |
| TS 43.129 vj00 | PS Handover in GERAN A/Gb and GAN Modes | Rel-19 read |
| TS 43.130 vj00 | Iur-g Interface Overview | Rel-19 read |
| TS 43.318 vj00 | Generic Access Network (GAN) Stage 2 | Rel-19 read |
| TS 44.060 vj00 | GERAN RLC/MAC Protocol Specification | Rel-19 read |
| TS 44.160 vg00 | GERAN Iu Mode RLC/MAC Protocol Specification | Rel-16 read |