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

Glossary term · Mobility

RNSAP Relocation

Radio Network Subsystem Application Part Relocation

Mobility →

RNSAP Relocation is a mobility procedure in 3GPP that enables enhanced relocation of a UE between Home NodeBs via the RNSAP protocol, supporting seamless handover in femtocell deployments within the same HNB Gateway and CSG.

Introduced
Rel-10
Where
Radio Access Network › UTRAN (3G)
Specifications
3 specs
RNSAP Relocation Description Purpose What changed Neighbours Specifications

Description

RNSAP Relocation is a mobility mechanism defined in 3GPP specifications for UMTS networks, specifically for inter-HNB (Home NodeB) relocation using the Radio Network Subsystem Application Part (RNSAP) protocol. RNSAP is the signaling protocol used over the Iur interface between Radio Network Controllers (RNCs) in UMTS. In the context of Home NodeBs (HNBs), which are small cells deployed in homes or enterprises, RNSAP Relocation enables the relocation of a UE from one HNB to another without involving the core network, thereby reducing signaling load and latency. This procedure is defined in 3GPP TS 25.413, TS 25.467, and TS 25.469.

The RNSAP Relocation procedure is part of the enhanced mobility framework for HNBs. When a UE moves from the coverage of one HNB to another, the serving HNB can initiate a relocation via RNSAP to the target HNB. This requires that both HNBs are connected to the same HNB Gateway (HNB-GW) and belong to the same Closed Subscriber Group (CSG). The procedure involves the exchange of RNSAP messages between the source and target HNBs, coordinated by the HNB-GW. The HNB-GW acts as an intermediate node, forwarding RNSAP messages and managing the relocation. The relocation can be intra-PLMN, meaning both HNBs are in the same Public Land Mobile Network.

The RNSAP Relocation procedure includes several steps: the source HNB sends a Relocation Required message to the HNB-GW, which forwards it to the target HNB. The target HNB allocates resources and responds with a Relocation Request Acknowledge. The source HNB then commands the UE to handover to the target HNB. After the UE successfully accesses the target HNB, the target HNB sends a Relocation Complete message to the HNB-GW, which releases resources in the source HNB. This procedure is similar to the SRNS Relocation in macro networks but is optimized for the HNB architecture.

The RNSAP Relocation is limited to specific scenarios: intra-PLMN, intra-HNB-GW, and intra-CSG. This means that the source and target HNBs must be in the same PLMN, connected to the same HNB-GW, and belong to the same CSG. These restrictions ensure that the relocation can be performed without core network involvement and without complex authorization procedures. The procedure is defined in TS 25.467 (UTRAN architecture for Home NodeB) and TS 25.469 (Home NodeB Application Part, HNBAP).

In summary, RNSAP Relocation is a key mobility feature for Home NodeB deployments in UMTS, enabling seamless handover between HNBs within the same HNB-GW and CSG. It reduces core network signaling and improves user experience in femtocell environments.

Purpose & Motivation

RNSAP Relocation was introduced to address the mobility challenges in Home NodeB (femtocell) deployments. In traditional UMTS macro networks, handovers between RNCs are handled via SRNS Relocation, which involves the core network. However, for HNBs, which are low-cost, user-deployed base stations, involving the core network for every handover would be inefficient and costly. RNSAP Relocation provides a localized mobility mechanism that keeps the handover signaling within the HNB-GW, reducing latency and core network load. It also ensures that the handover is restricted to authorized scenarios (same PLMN, HNB-GW, and CSG), maintaining security and policy control. This feature was motivated by the need to support seamless mobility in dense femtocell deployments without overburdening the core network.

What changed in its specifications

The latest release-to-release comparison of specifications that define RNSAP Relocation. Each summary describes the whole specification, not only this term.

TS 25.413Rel-11 → Rel-12

Release 12 adds LIPA and SIPTO procedural handling with new IEs, an MBMS Session Re-establishment Indicator IE, and BDS support including GANSS ID coding value 101.

Full comparison in TS 25.413 →
TS 25.467Rel-18 → Rel-19

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

Full comparison in TS 25.467 →

Release Timeline

Evolution Across Releases

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

Rel-10 Initial

Initial definition introduced RNSAP Relocation for inter-HNB relocation, limited to intra-HNB-GW intra-CSG scenarios. This established the basic mobility framework for HNBs.

The definition was expanded to include intra-PLMN as an additional restriction, clarifying that the procedure is only defined for intra-PLMN intra-HNB-GW intra-CSG scenarios.

Definition carried over unchanged from Rel-11.

Definition carried over unchanged from Rel-11.

Definition carried over unchanged from Rel-11.

Definition carried over unchanged from Rel-11.

Definition carried over unchanged from Rel-11.

Definition carried over unchanged from Rel-11.

Definition carried over unchanged from Rel-11.

Definition carried over unchanged from Rel-11.

Defining Specifications

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

SpecificationTitleRelease
TS 25.413 vj00 Radio Access Network Application Part (RANAP) Rel-19 read
TS 25.467 vj00 UTRAN Architecture for 3G Home Node B Rel-19 read
TS 25.469 vj00 HNBAP Specification for HNB to HNB-GW Interface Rel-19 read