DRNS

Drift Radio Network Subsystem

Radio Access Network →
Introduced in R99

DRNS is the collective term for a Drift Radio Network Controller (DRNC) and its controlled Node Bs, representing the radio resource domain a UE uses but is not anchored to during inter-RNC soft handover in UMTS.

Category
Radio Access Network
Introduced
R99
Where
Radio Access Network › UTRAN (3G)
Specifications
6 specs
DRNS Description Purpose Related Classification Specifications

Description

The Drift Radio Network Subsystem (DRNS) is a logical grouping within the UMTS Terrestrial Radio Access Network (UTRAN) architecture. It comprises a single Drift Radio Network Controller (DRNC) and all the base stations (Node Bs) that are connected to and controlled by that DRNC. The concept of a DRNS is defined relative to a specific User Equipment (UE). When a UE is in an inter-RNC soft handover state—connected to cells belonging to different RNCs—the RNC that is not the Serving RNC (SRNC) is designated the DRNC for that UE, and its entire controlled domain becomes the DRNS for that UE's connection.

Architecturally, the DRNS is a subset of the UTRAN. It interfaces with the core network via the Iu interface (though typically, the SRNC acts as the sole point of contact with the CN for a given UE). Its most critical external interface is the Iur interface, which connects it to the Serving RNS (SRNS)—the domain of the SRNC. All control signaling and user data pertaining to the UE that traverse between the SRNC and the Node Bs within the DRNS must pass through this Iur link. Internally, the DRNS uses the Iub interface to connect the DRNC to its Node Bs.

The DRNS operates under the command of the SRNC for resources allocated to a specific UE. The SRNC uses the Radio Network Subsystem Application Part (RNSAP) protocol over the Iur interface to request radio link setup, modification, or deletion within the DRNS. The DRNC, as the manager of the DRNS, is responsible for translating these requests into actions on its Iub interfaces, allocating local resources like channelization codes and scrambling codes, and managing the physical radio links. For the user plane, the DRNS acts as a switch: it receives downlink frames from the SRNC, routes them to the correct Node B(s), and combines uplink frames from its Node Bs before forwarding the combined frame to the SRNC. This allows the SRNS to maintain a single, coherent view of the radio connection while utilizing radio resources from multiple RNS domains.

Purpose & Motivation

The DRNS concept was created alongside the DRNC in Release 99 to provide a formal architectural model for managing radio resources outside the serving domain during soft handover. It addresses the need to abstract and manage a set of network elements (an RNC and its Node Bs) as a single, controllable entity from the perspective of the serving controller. Before UMTS, GSM's BSC and its BTSs formed a similar subsystem, but inter-BSC handovers were hard and did not require the sustained, coordinated resource sharing that UMTS soft handover demands.

Defining the DRNS allows the 3GPP specifications to clearly delineate responsibilities and interfaces. It establishes that the SRNC has a peer-to-peer relationship with another complete administrative entity (the DRNS), not just with an individual RNC. This modeling is crucial for specifying procedures like radio link addition, where the SRNC requests a resource from another subsystem. It also simplifies network management and fault domain isolation. The DRNS concept encapsulates all the localized radio resource management functions, allowing the SRNS to focus on end-to-end connection management for the UE. This separation of concerns is key to achieving scalable and robust mobility in a large, multi-vendor UMTS network.

Classification

Part ofUTRAN
Specific typesDRNC
Related approachesSRNS

Evolution Across Releases

R99 Initial

Introduced as the foundational architectural block representing a non-serving radio network domain. Defined its composition (DRNC + Node Bs), its role in inter-RNC soft handover, and its interactions with the Serving RNS via the Iur interface for both control plane (RNSAP) and user plane data forwarding.

Clarifications and enhancements to support circuit-switched core network architecture split (MSC Server vs. MGW). This impacted the overall UTRAN architecture but did not fundamentally alter the internal workings or definition of a DRNS.

Extended the DRNS model to support HSDPA operations. Defined how a DRNS can contain a cell that becomes the HS-DSCH serving cell for a UE, requiring specific data forwarding and control procedures over the Iur interface for high-speed packet data.

Further evolved to incorporate HSUPA (E-DCH) functionality. Specified the DRNS's role in managing E-DCH resources in its cells, including receiving and acting upon uplink scheduling information from the SRNC and handling HARQ processes for data received from its Node Bs.

The DRNS concept remained architecturally stable through later UMTS releases. Enhancements related to HSPA+, MIMO, and other features were integrated as extensions to the existing DRNS procedures, primarily involving updates to the RNSAP protocol and Iur data transport mechanisms, without redefining the core subsystem model.

Explore further

Broader topics and technologies where DRNS plays a role.

Defining Specifications

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

SpecificationTitleRelease
TR 21.905 vj00 3GPP Technical Terms and Definitions Rel-19
TS 25.401 vj00 UTRAN Overall Architecture Rel-19
TS 25.413 vj00 Radio Access Network Application Part (RANAP) Rel-19
TS 25.420 vj00 Iur Interface Introduction for UTRAN Rel-19
TS 25.423 vj00 UTRAN RNSAP Specification Rel-19
TR 25.931 vj00 UTRAN Signalling Procedures Examples Rel-19