Description
The Radio Network Subsystem Application Part (RNSAP) is a critical signaling protocol defined by 3GPP for UMTS (and adapted for GSM) networks, operating over the Iur interface between Radio Network Controllers (RNCs) in different Radio Network Subsystems (RNS). An RNS consists of one RNC and its controlled Node Bs (base stations), and RNSAP enables coordination between these subsystems to support mobility and resource management. The protocol is part of the Radio Access Network Application Part (RANAP) family and uses lower-layer transport mechanisms, such as Signalling Connection Control Part (SCCP) over IP or ATM, to exchange messages between RNCs. Its primary role is to facilitate procedures that require inter-RNC communication, ensuring that user equipment (UE) can move seamlessly between cells controlled by different RNCs without service interruption.
RNSAP works by defining a set of elementary procedures and messages that cover various scenarios. Key functions include radio link management during soft handover, where a UE communicates with multiple Node Bs across different RNSs; RNSAP coordinates the addition, deletion, and modification of radio links to maintain call quality. It also handles SRNS (Serving RNS) relocation, which transfers the serving RNC role from one RNC to another due to UE mobility, involving context transfer and resource reallocation. Additionally, RNSAP manages measurement reporting, paging coordination, and common channel management, enabling efficient use of radio resources and load balancing across the network. The protocol operates in a request-response manner, with messages like RADIO LINK SETUP REQUEST and RELOCATION REQUIRED initiating procedures, and corresponding confirmations or failures completing them.
The architecture of RNSAP is layered, with the application part relying on underlying signaling transport. It includes error handling mechanisms, such as timers and retransmissions, to ensure reliability. In specifications like 25.423, RNSAP is detailed with information elements that encode parameters like UE identifiers, radio resource configurations, and measurement results. Its evolution has seen enhancements for interoperability with later technologies, but its core remains vital for UMTS networks. By enabling inter-RNC coordination, RNSAP supports key features like macro diversity in soft handover, which improves coverage and reduces drop calls, contributing to the overall performance and reliability of 3G radio access networks.
Purpose & Motivation
RNSAP was created to address the need for coordinated signaling between Radio Network Subsystems (RNS) in UMTS networks, which introduced a distributed architecture with multiple RNCs. Prior to UMTS, GSM networks relied on simpler handover mechanisms between base station controllers (BSCs), but UMTS's soft handover and tighter integration required a dedicated protocol for inter-RNC communication. Without RNSAP, mobility management across RNS boundaries would be inefficient, leading to service disruptions, increased signaling overhead, and suboptimal resource usage during UE movements.
The protocol solves problems related to seamless mobility, particularly in scenarios where a UE is in soft handover between Node Bs controlled by different RNCs. It enables procedures like radio link addition and SRNS relocation, ensuring that the UE maintains continuous connectivity without call drops. Additionally, RNSAP facilitates load balancing and resource optimization by allowing RNCs to share measurement data and coordinate channel allocations. Its development was motivated by the complexity of UMTS's WCDMA-based radio interface, which benefits from macro diversity and requires precise timing and synchronization across multiple points.
Historically, RNSAP's introduction in 3GPP R99 laid the foundation for advanced mobility features in 3G networks, supporting the transition from circuit-switched to packet-switched services. It addressed limitations of earlier protocols that lacked the granularity for inter-RNC signaling, enabling scalable and robust radio access networks. As networks evolved toward 4G and 5G, concepts from RNSAP influenced later protocols like X2-AP in LTE, though RNSAP remains essential for existing UMTS deployments.
Key Features
- Manages signaling over the Iur interface between RNCs
- Supports soft handover procedures with radio link coordination
- Handles Serving RNS relocation for UE mobility
- Facilitates measurement reporting and resource management
- Uses SCCP-based transport for reliable message delivery
- Defines elementary procedures for inter-RNC communication
Evolution Across Releases
Introduced as the signaling protocol for the Iur interface in UMTS, enabling communication between Radio Network Controllers in different Radio Network Subsystems. Initial capabilities included support for soft handover, SRNS relocation, and basic radio resource management. Specifications like 25.423 defined the message set and procedures for inter-RNC coordination.
Defining Specifications
| Specification | Title |
|---|---|
| TS 21.905 | 3GPP TS 21.905 |
| TS 25.401 | 3GPP TS 25.401 |
| TS 25.420 | 3GPP TS 25.420 |
| TS 25.422 | 3GPP TS 25.422 |
| TS 25.423 | 3GPP TS 25.423 |
| TS 25.471 | 3GPP TS 25.471 |
| TS 25.931 | 3GPP TS 25.931 |
| TS 43.051 | 3GPP TR 43.051 |
| TS 43.130 | 3GPP TR 43.130 |
| TS 44.060 | 3GPP TR 44.060 |