Description
The Radio Network Subsystem (RNS) is a fundamental architectural entity within the Universal Mobile Telecommunications System (UMTS) Radio Access Network (UTRAN), as standardized from 3GPP Release 99 onwards. An RNS is responsible for managing all radio-related functions for a set of cells within its geographic control area. It consists of two primary node types: the Radio Network Controller (RNC) and one or more Node B base stations. The RNC acts as the controlling intelligence, while the Node Bs provide the physical radio coverage. A single UMTS network typically contains multiple RNSs to provide nationwide coverage.
Within an RNS, the RNC performs critical control and management tasks. It handles Radio Resource Management (RRM), including admission control, power control, packet scheduling, and handover decisions. The RNC is responsible for establishing, maintaining, and releasing Radio Access Bearers (RABs) as requested by the Core Network (CN). It also performs ciphering and integrity protection for data transmitted over the air interface (Uu). The RNC connects to the Node Bs via the Iub interface, which uses the ATM (Asynchronous Transfer Mode) protocol stack in early releases, carrying both user data and control signaling. The RNC manages the logical resources of its subordinate Node Bs, such as channelization codes and timeslots.
The Node B is the physical unit that houses the radio transceivers and antennas. It converts the data flow from the Iub interface to the radio transmission over the Uu interface and vice versa. Under the command of the RNC, the Node B executes functions like inner-loop power control, physical channel coding/decoding, and spreading/despreading for CDMA. An RNS connects to the Core Network via the Iu interface. The Iu interface is split into Iu-CS (Circuit Switched) for voice and legacy services connecting to the MSC, and Iu-PS (Packet Switched) for data services connecting to the SGSN. The RNS architecture enables soft handover, a key UMTS feature where a UE can be connected to multiple Node Bs simultaneously, with the RNC performing macro-diversity combining and splitting of the data streams.
The RNS concept centralized intelligence in the RNC, contrasting with the distributed architecture of GSM's BSC/BTS and prefiguring the flatter architecture of LTE/EPC where the RNC functions are distributed between the eNodeB and the core. An RNS can be in one of two logical roles relative to a specific UE: Serving RNS (SRNS), which controls the connection and holds the UE context, or Drift RNS (DRNS), which provides additional radio resources during soft handover. The RNS architecture was crucial for delivering the high-speed packet data and advanced mobility features that defined 3G UMTS networks.
Purpose & Motivation
The RNS was created to provide the radio access network architecture for 3G UMTS, addressing the need for a system capable of supporting both high-speed packet-switched data and circuit-switched voice with improved spectral efficiency and quality over 2G systems. It solved the problem of managing a Wideband CDMA (WCDMA) air interface, which required complex centralized control for functions like soft handover and fast power control that were not present in GSM's TDMA-based system.
Historically, the transition from GSM's Base Station Subsystem (BSS) to UMTS's UTRAN and its RNS components was driven by the demand for mobile internet access. The GSM/GPRS network could not efficiently handle the variable data rates and stringent QoS requirements of emerging multimedia services. The RNS architecture, with its RNC, provided the necessary intelligence to manage packet flows, perform efficient radio resource allocation for bursty data traffic, and support simultaneous voice and data sessions. The separation of the Iu interface into CS and PS domains allowed seamless integration with both legacy circuit-switched core networks and new packet-switched cores.
The creation of the RNS standardized the interface between the radio and core networks (Iu) and between the controller and the base stations (Iub), enabling multi-vendor interoperability. This was a key improvement over some proprietary pre-3G systems. The RNS's design supported evolutionary concepts like the Drift RNS, enabling seamless inter-RNC mobility without burdening the core network with every handover. While later 4G LTE adopted a flatter architecture with the eNodeB integrating RNC functions, the RNS was the essential architectural framework that enabled the successful deployment and operation of 3G networks worldwide.
What changed in its specifications
The latest release-to-release comparison of specifications that define RNS. 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 →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
- RNS decomposed into RNC
“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 8 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 Radio Network Subsystem is defined for the first time in R99: one RNC plus Node Bs, with serving and drift RNS roles, and it is used in relocation and handover procedures.
- “RNS can be either a full UTRAN or only a part of a UTRAN.” TS 25.401 v3.10.0
- “A RNS consists of a Radio Network Controller and one or more Node Bs.” TS 25.401 v3.10.0
- “For each connection between User Equipment and the UTRAN, One RNS is the Serving RNS.” TS 25.401 v3.10.0
From Rel-4, as a network option, an RNS can have Iu interfaces to more than one MSC, which an MSC may select during intra-PLMN relocation or BSS-to-RNS handover.
- “From release 4 onwards, as a network option, an RNS can have Iu interfaces to more than one MSC.” TS 23.009 v4.9.0
In Rel-5 the RNS concept was extended so that an RNS can also be a GERAN BSS in Iu mode, with RNS/BSS relocation and roles defined, and an RNS may include an optional SAS.
- “The role of an RNS or BSS (Serving or Drift) is on a per connection basis between an UE and the UTRAN/GERAN Iu mode.” TS 25.401 v5.10.0
- “A RNS consists of a Radio Network Controller one or more Node Bs and optionally one SAS.” TS 25.401 v5.10.0
- “In the context of this specification, the terms RNS or RNC refer also to a GERAN BSS or BSC (respectively) when serving an MS in Iu mode.” TS 23.060 v5.13.0
In Rel-6 the SGSN may be informed by the RNS of the selected core network operator and may send a Reroute Command to the RNS for MOCN network sharing redirection.
- “the SGSN may be informed by the RNS about the identity of the selected core network operator when receiving the Attach Request message” TS 23.060 v6.15.0
- “decide to initiate redirection by sending a Reroute Command to the RNS, as described in TS 23.251 [83]” TS 23.060 v6.15.0
- “3G_MSC-A may send information of the alternative radio access bearer to the target RNS during the intra-3G_MSC handover/relocation” TS 23.009 v6.5.0
Enhanced SRNS Relocation was added between RNSs, where the serving RNS prepares and relocates SRNS functionality to another RNS via Iur before the core network is informed.
- “When the Serving RNS (RNS-A) makes the decision to perform the Enhanced SRNS Relocation procedure it will send an IUR-ENHANCED- RELOCATION-REQUEST message to the new RNS” TS 23.009 v8.3.0
- “In Enhanced Serving RNS Relocation the SRNS functionality is prepared at RAN side and the SGSN is not informed until the preparation and execution” TS 23.060 v8.17.0
- “The Enhanced SRNS Relocation function manages the Iu interface connection mobility from an RNS to another RNS.” TS 25.401 v8.2.0
Rel-9 specifies that an HNB Subsystem appears as an RNS to the core network over Iu-CS and Iu-PS, and that the terms RNC or RNS refer to the HNB subsystem when the MS accesses via an HNB.
- “The HNB Subsystem appears as an RNS to the core network and is connected by means of the Iu-CS interface to the MSC” TS 23.060 v9.14.0
- “the term RNC (or RNS if used instead) refers to the HNB subsystem if the MS accesses the network via a HNB” TS 23.060 v9.14.0
Rel-10 extends RNS-related behaviour: overload messages from the SGSN to RNS are extended, the RNS receives MTC pool-steering indications, and the Serving RNS may connect to a TBSS for 1.28Mcps TDD A/Gb mode mobility.
- “Overload messages from the SGSN to RNS/BSS are extended to aid the RAN in performing the functionality in bullets b, c and d above.” TS 23.060 v10.14.0
- “The BSS and RNS are provided with indications from the MS that permit them to steer "new MTC entrants into a pool area" to specific SGSNs” TS 23.060 v10.14.0
- “For 1.28Mcps TDD, to support UE mobility between UTRAN and GERAN A/Gb mode, the Serving RNS may be connected to the TBSS” TS 25.401 v10.2.0
Rel-11 adds an Extended RNC-ID option in which an RNS partitions the U-RNTI differently, changing the number of UEs and cells per RNS, with legacy UEs unaffected.
- “This is possible by partitioning the 32bits of the U-RNTI in a different manner in RNS which is configured to use the extended RNC-ID.” TS 25.401 v11.1.0
- “The number of UEs and cells in one RNS using the extended RNC-ID are different from the one using the current RNC ID” TS 25.401 v11.1.0
Defining Specifications
3GPP specifications that define or reference RNS, 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 |
| 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.851 v610 | Network Sharing Architecture for 3G Systems | Rel-6 read |
| TR 23.908 v400 | Pre-paging in GSM/UMTS networks | Rel-4 read |
| TR 23.923 v300 | Mobile IP+ Feasibility Study for UMTS/GPRS | R99 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.321 vj00 | MAC Protocol Specification for UTRAN | 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.413 vj00 | Radio Access Network Application Part (RANAP) | Rel-19 read |
| TS 25.420 vj00 | Iur Interface Introduction for UTRAN | Rel-19 read |
| TS 25.423 vj00 | UTRAN RNSAP Specification | Rel-19 read |
| TS 25.430 vj00 | Introduction to Iub Interface Specifications | Rel-19 read |
| TS 25.453 vj00 | PCAP Protocol Specification | Rel-19 read |
| TS 25.471 vj00 | RNSAP User Adaptation (RNA) for Iurh | Rel-19 read |
| TR 25.931 vj00 | UTRAN Signalling Procedures Examples | 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.272 vj00 | Charging for Push-to-Talk over Cellular (PoC) | Rel-19 read |
| TS 33.859 vb10 | UTRAN Key Hierarchy Study | Rel-11 read |
| TS 38.807 vg10 | NR beyond 52.6 GHz Study | Rel-16 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 44.060 vj00 | GERAN RLC/MAC Protocol Specification | Rel-19 read |