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

Glossary term · Interface

Iur

Iur Interface (RNC–RNC Interface)

Interface →

Iur is the logical interface between two Radio Network Controllers (RNCs) in UMTS, enabling soft handover, inter-RNC mobility, and radio resource coordination across RNC boundaries within UTRAN.

Introduced
R99
Where
Services
Specifications
2 specs
Iur Description Purpose What changed Family Neighbours Detected Changes Specifications

Description

The Iur interface is the standardized logical interface between two Radio Network Controllers (RNCs) in the UMTS Terrestrial Radio Access Network (UTRAN). It is defined in 3GPP TS 25.401 and referenced in the vocabulary specification TS 21.905. Architecturally, Iur connects RNCs within the same UTRAN, allowing a UE to maintain radio links with cells controlled by different RNCs. This is essential for soft handover, where the UE simultaneously communicates with multiple Node Bs that may be under the control of different RNCs.

Functionally, Iur carries two main categories of traffic: control plane signalling and user plane data. The control plane uses the Radio Network Subsystem Application Part (RNSAP) protocol, which manages radio link setup, addition, deletion, and reconfiguration across RNCs. RNSAP also supports mobility procedures such as serving RNC (SRNC) relocation, where the role of the SRNC is transferred from one RNC to another as the UE moves. The user plane carries dedicated channel (DCH) and later HSDPA/HSUPA data frames using the Iur Frame Protocol, which is similar in structure to the Iub Frame Protocol but adapted for inter-RNC transport.

The Iur interface introduces the concept of the Drift RNC (DRNC). When a UE is connected to an RNC that is not its serving RNC, that RNC acts as a DRNC and provides radio resources to the UE on behalf of the SRNC. The SRNC controls the connection and communicates with the DRNC over Iur. This SRNC/DRNC split is a defining feature of UTRAN and allows seamless mobility across RNC boundaries without interrupting the user's session.

Transport-wise, Iur was originally carried over ATM, with AAL2 for user plane and AAL5 for control plane, similar to Iub. From Rel-5 onwards, IP transport became increasingly common, with SCTP for RNSAP signalling and UDP/IP for user plane framing. The logical interface definition does not mandate a specific physical realization; the Iur may be implemented over point-to-point links, leased lines, or packet-switched backhaul. This flexibility is important because RNCs may be geographically separated and interconnected through an operator's transport network.

In terms of evolution, the Iur definition was revised in Rel-6, where the wording changed from "two RNCs" to "two RNC" and from "need not be" to "may not be" a point-to-point link. This is a minor editorial change rather than a functional one. From Rel-6 through Rel-19, the definition remained essentially the same, with only formatting and minor wording variations. The Iur interface remained a stable part of UTRAN throughout its lifecycle, even as HSPA enhancements added new frame types and procedures.

Purpose & Motivation

The Iur interface exists to enable seamless mobility and coordinated radio resource management across RNC boundaries in UMTS. Without Iur, a UE moving between cells controlled by different RNCs would experience a hard handover, which can cause interruption and degradation of service. Iur allows soft handover across RNCs, where the UE maintains simultaneous radio links with multiple Node Bs, improving coverage and reliability at cell edges.

A second motivation is the need for a standardized inter-RNC protocol. Before Iur, inter-RNC coordination was proprietary or limited, which restricted multi-vendor deployment and made it difficult to build large, contiguous UMTS networks. By defining Iur in 3GPP specifications, the industry enabled RNCs from different vendors to interoperate, supporting flexible network planning and vendor diversity.

Finally, Iur supports the SRNC/DRNC architecture, which separates the control anchor from the radio access point. This separation allows the network to keep a stable control anchor while the UE moves across RNCs, reducing signalling to the core network and improving handover performance. The Iur interface is therefore a foundational element of UTRAN mobility and resource management.

What changed in its specifications

The latest release-to-release comparison of specifications that define Iur. 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 25.401Rel-18 → Rel-19

Rel-19 brings only minor changes to TS 25.401: 0 clauses changed, with no change attributed to a release feature.

Full comparison in TS 25.401 →

Technology family

RAN interfaces · Radio Access Network

  1. Phase 1 A interface, Abis
  2. R99 Iu, Iu-BC, Iu-CS, Iu-PS, Iub, Iur, NBAP, Uu
  3. Rel-5 Iur-g
  4. Rel-8 S1, S1-MME, S1-U, S1AP, X2
  5. Rel-15 E1, E1AP, F1, F1-C, F1-U, F1AP, NG, NG-C, NG-U, NGAP, Xn, Xn-C, Xn-U
  • Iur counterpart in another generation: X2
    “The interface allowing to interconnect eNBs with each other is referred to as the X2 interface.” TS 36.420

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 sources

Documented changes in 6 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.

R99 introduced

The Iur is specified for the first time as a logical interface between RNCs in UTRAN, with its signalling (RNSAP), transport network and frame protocols for common and dedicated transport channels.

  • “Inside the UTRAN, the RNCs of the Radio Network Subsystems can be interconnected together through the Iur.” TS 25.401 v3.10.0
  • “Iur: logical interface between two RNCs” TS 25.401 v3.10.0
  • “Radio Network Subsystem Application Part: Radio Network Signalling over the Iur” TS 25.401 v3.10.0
Rel-5 specification text

Iur gains HS-DSCH support with an Iur HS-DSCH Frame Protocol between Controlling and Serving RNC, while the Iur CPCH Frame Protocol model is removed and Iur-g signalling is added.

  • “In this case, Iur HS-DSCH Frame Protocol is used to interwork the Flow Control function at the Controlling RNC with the MAC-d at the Serving RNC.” TS 25.401 v5.10.0
  • “- Signalling network for Iu, Iur, Iur-g and Iupc;” TS 25.401 v5.10.0
Rel-6 specification text

Iur gained support for Network Assisted Cell Change from UTRAN to GERAN, MBMS binding identifiers carrying UDP ports, and SRNC requests to the DRNC for system information.

  • “Introduction of Iu and Iur support of Network Assisted Cell Change from UTRAN to GERAN” TS 25.401 v6.9.0
  • “the Binding ID may also be used to carry the UDP port on Iub and Iur interfaces.” TS 25.401 v6.9.0
  • “The SRNC to request the DRNC (via Iur interface) to provide this system information, if available.” TS 25.401 v6.9.0
Rel-7 specification text

The Iur HS-DSCH protocol model was extended to cover HS-DSCH for UEs in Cell_FACH, Cell_PCH and URA_PCH, with Iur HS-DSCH Frame Protocol interworking MAC-c flow control and MAC-d, and with MAC-ehs added.

  • “Iur HS-DSCH Frame Protocol is used to interwork the Flow Control function at the MAC-c at Controlling RNC with the MAC-d at the Serving RNC.” TS 25.401 v7.6.0
  • “The protocol model in Figure 24 is applied for HS-DSCH configured for UEs in Cell_DCH.” TS 25.401 v7.6.0
Rel-8 specification text

The HS-DSCH protocol models with separate Controlling and Serving RNC over Iur (Figures 24 and 25B) now also apply to 1.28 Mcps TDD, not only FDD.

  • “[FDD and 1.28 Mcps TDD - Figure 25B shows the protocol model for the HS-DSCH transport channel configured for UE in Cell_FACH, Cell_PCH and URA_PCH” TS 25.401 v8.2.0
  • “[FDD and 1.28 Mcps TDD – The protocol model in Figure 24 is applied for HS-DSCH configured for UEs in Cell_DCH.]” TS 25.401 v8.2.0
Rel-11 specification text

Rel-11 adds configuration requirements for Iur connections between RNCs using legacy and extended RNC-IDs, including a restriction on connecting legacy and upgraded RNCs.

  • “Not configure the Iur interface connection between legacy RNC and upgraded RNC using the extended RNC-ID.” TS 25.401 v11.1.0
  • “configure the legacy RNC-ID so that legacy RNC-ID will not be the same as the 12 bit of MSB of any of extended RNC-ID” TS 25.401 v11.1.0

Defining Specifications

3GPP specifications that define or reference Iur, 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 25.401 vj00 UTRAN Overall Architecture Rel-19 read