Description
The Radio Access Network Application Part (RANAP) is the protocol responsible for all control signaling between the UMTS Terrestrial Radio Access Network (UTRAN) and the Core Network (CN), specifically across the Iu interface. It operates over the Signalling Connection Control Part (SCCP) and can use either a connection-oriented or connectionless transport service. RANAP encapsulates a wide range of functions into distinct Elementary Procedures (EPs), which can be classified as Class 1 (with response), Class 2 (without response), or Class 3 (possibly multiple responses). Its primary responsibilities are divided into several key areas: Radio Access Bearer (RAB) Management, which includes the establishment, modification, and release of user-plane channels for carrying user data; Mobility Management, handling SRNS Relocation (serving RNS change) and the transfer of UE context between RNCs; UE-CN Signaling Transport, providing a transparent tunnel for non-access stratum (NAS) messages like Attach, Routing Area Update, and Activate PDP Context between the UE and the core network entities (MSC/VLR or SGSN/MME); and Paging, initiating paging requests from the CN to the RNC. The protocol also manages the overall Iu interface resource, including the reset and overload control procedures. RANAP signaling is initiated by either the Serving RNC (SRNC) or the CN node (MSC Server for CS, SGSN for PS). It plays a critical role in separating RAN-specific functions from core network functions, allowing for independent evolution of the radio and core network technologies.
Purpose & Motivation
RANAP was created as part of the UMTS architecture to define a clean, standardized interface (Iu) between the radio access network and the core network. This separation was a key design principle, moving away from the more tightly integrated BSSAP protocol used in GSM between the BSC and MSC. The purpose was to allow different vendors to supply RAN and CN equipment independently, fostering competition and innovation. RANAP solves the problem of coordinating complex radio resource management (handled by the RNC) with core network mobility and session management (handled by MSC/SGSN). It enables the core network to request the establishment of a guaranteed QoS bearer (RAB) for a voice call or data session without needing to understand the specifics of the WCDMA radio technology. It also facilitates efficient mobility, such as soft handover within UTRAN and SRNS relocation, by providing the signaling to transfer UE context. Its creation was motivated by the need for a flexible, future-proof protocol that could support the new packet-switched domain (PS) alongside the circuit-switched domain (CS) from the inception of 3G. RANAP addressed the limitations of previous GSM interfaces by providing a more comprehensive and structured set of procedures, enabling advanced services, better QoS handling, and seamless mobility that were essential for 3G multimedia applications.
What changed in its specifications
The latest release-to-release comparison of specifications that define RANAP. Each summary describes the whole specification, not only this term.
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 →Rel-19 brings only minor changes to TS 23.060: 0 clauses changed, with no change attributed to a release feature.
Full comparison in TS 23.060 →Protocol Stack
Evolution Across Releases
An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.
RANAP was introduced as the defining protocol for the new Iu interface in the initial UMTS (3G) specifications. It established the complete set of elementary procedures for connecting the UTRAN (RNC) to both the circuit-switched core network (Iu-CS to MSC) and the packet-switched core network (Iu-PS to SGSN), enabling all fundamental mobility, bearer management, and signaling transport functions.
Defining Specifications
3GPP specifications that define or reference RANAP, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TR 21.905 vj20 | 3GPP Terminology and Definitions | Rel-19 read |
| TS 23.060 vj00 | GPRS Stage 2 Service Description | Rel-19 read |
| TS 23.171 v390 | LCS Stage 2 for UMTS | R99 read |
| TS 23.205 vj00 | Bearer Independent CS Core Network Stage 2 | Rel-19 read |
| TS 23.221 vj00 | 3GPP System Architectural Requirements | Rel-19 read |
| TS 23.271 vj00 | LCS Stage 2 Specification | Rel-19 read |
| TS 25.305 vj00 | UTRAN UE Positioning Stage 2 | Rel-19 read |
| TS 25.401 vj00 | UTRAN Overall Architecture | Rel-19 read |
| TS 25.410 vj00 | Iu Interface Introduction for UTRAN | Rel-19 read |
| TS 25.412 vj00 | Iu Interface Signalling Transport Specification | Rel-19 read |
| TS 25.413 vj00 | Radio Access Network Application Part (RANAP) | Rel-19 read |
| TS 25.415 vj00 | Iu Interface User Plane Protocol | Rel-19 read |
| TS 25.423 vj00 | UTRAN RNSAP Specification | Rel-19 read |
| TS 25.820 v820 | 3G Home NodeB Study Report | Rel-8 read |
| TR 25.931 vj00 | UTRAN Signalling Procedures Examples | Rel-19 read |
| TS 29.060 vj00 | GPRS Tunnelling Protocol (GTP) version 1 | Rel-19 read |
| TS 29.281 vj20 | GTPv1-U Protocol Specification | Rel-19 read |
| TS 32.251 vj00 | PS Domain Charging Management | Rel-19 read |
| TS 32.408 vj00 | UMTS/GSM Performance Management Measurements | Rel-19 read |
| TS 33.859 vb10 | UTRAN Key Hierarchy Study | Rel-11 read |
| TS 37.857 vd10 | Indoor Positioning Enhancements for UTRA and LTE | Rel-13 read |
| TS 43.051 vj00 | GERAN Stage 2 Service Description | Rel-19 read |
| TS 44.060 vj00 | GERAN RLC/MAC Protocol Specification | Rel-19 read |