Menu
Latest
12 meetings · Prague, Jeju · 12–16 Oct
Reports
RAN1#126-bis · SA2#177

Glossary term · Radio Access Network

RNS

Radio Network Subsystem

Radio Access Network →

RNS is the UMTS (3G) network component comprising Radio Network Controllers (RNCs) and their controlled Node Bs, which manages radio resources, handovers, and connects user equipment to the core network.

Introduced
R99
Where
Radio Access Network › UTRAN (3G)
Specifications
26 specs
Also in
Core Network
RNS Description Purpose What changed Neighbours Specifications

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.

TR 21.905Rel-17 → Rel-18

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 →
TS 23.009Rel-18 → Rel-19

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 Across Releases

An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.

R99 Initial

Introduced the RNS as the core component of the new UMTS Terrestrial Radio Access Network (UTRAN). Defined its architecture comprising the RNC and Node B, the Iu and Iub interfaces, and its core functions for supporting WCDMA-based 3G services including packet-switched data.

Defining Specifications

3GPP specifications that define or reference RNS, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
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 Enhancement 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