RANAP

Radio Access Network Application Protocol

Protocol →
Introduced in R99 Also in: Core Network, Services

RANAP is the signaling protocol between the Core Network and the UMTS Radio Access Network that manages bearers, mobility, and security to enable core network control and service delivery.

Category
Protocol
Introduced
R99
Where
Radio Access Network › UTRAN (3G)
Also touches
2 segments
Specifications
23 specs
RANAP Description Purpose Related Classification Detected Changes Specifications

Description

The Radio Access Network Application Protocol (RANAP) is a critical signaling protocol defined within the 3GPP UMTS architecture, operating over the Iu interface. This interface connects the Core Network (CN), specifically the Mobile Switching Center (MSC) for circuit-switched services and the Serving GPRS Support Node (SGSN) for packet-switched services, to the UMTS Terrestrial Radio Access Network (UTRAN). RANAP is an application layer protocol that utilizes lower-layer transport protocols, such as SCCP and MTP3-B over ATM or IP, to carry its messages. Its primary function is to provide a standardized, reliable mechanism for the CN to control and manage the resources and operations of the UTRAN, abstracting the radio-specific complexities from the core network entities.

RANAP operates through a set of Elementary Procedures (EPs), which are the fundamental units of signaling exchange. These procedures are categorized into three classes: Class 1 procedures require a response (success or failure), Class 2 procedures do not require a response, and Class 3 procedures involve multiple request/response messages. Key procedures include Radio Access Bearer (RAB) management for establishing, modifying, and releasing user data bearers; relocation procedures for handing over control of a user between Radio Network Controllers (RNCs) or between RNCs and the core network; and paging to locate idle User Equipment (UE). It also handles the transfer of Non-Access Stratum (NAS) messages, such as mobility management and call control signaling, transparently between the UE and the CN.

Architecturally, RANAP messages are processed by the RANAP protocol entity within the RNC and the corresponding CN node (MSC or SGSN). The protocol supports both connection-oriented and connectionless signaling. For user-specific signaling related to an active UE, a dedicated Iu signaling connection is established. For common or broadcast signaling not tied to a specific UE, connectionless transport is used. RANAP's design ensures that the core network can command the RAN to perform specific tasks—like setting up a radio bearer with certain quality of service (QoS) parameters—without needing to understand the intricate details of the radio resource management algorithms implemented in the UTRAN. This clear separation of concerns is a foundational principle of the UMTS architecture.

Purpose & Motivation

RANAP was created to address the need for a robust, standardized signaling interface between the new, more complex UMTS Radio Access Network and the evolving core network. Prior to 3G, GSM used the Base Station System Application Part (BSSAP) protocol between the MSC and the Base Station Controller (BSC). However, the introduction of UTRAN, with its new architecture featuring Node Bs and RNCs, and support for advanced services with varied QoS requirements, necessitated a more powerful and flexible protocol. RANAP was designed to provide this functionality, enabling the core network to effectively control the richer set of capabilities offered by WCDMA-based UTRAN.

The protocol solves the problem of abstracting radio network specifics from the service logic in the core. It allows the MSC and SGSN to manage mobility, session, and bearer control using service-oriented primitives, while the RNC handles the radio-dependent mapping of these requests into physical radio resources. This separation allows for independent evolution of the radio and core networks. Furthermore, RANAP supports essential 3G features like soft handover (where a UE is connected to multiple Node Bs simultaneously), which requires complex coordination between the RNC and the core network for bearer management during mobility events.

Its creation was motivated by the transition from circuit-switched dominated 2G services to a mixed-mode 3G network supporting high-speed packet data. RANAP needed to manage both circuit-switched voice bearers and packet-switched data bearers with dynamic QoS. It provided the necessary procedures for the core network to request the establishment of a Radio Access Bearer with specific traffic class, maximum bitrate, and delay characteristics, which was a significant advancement over the simpler bearer management in GSM.

Classification

Part ofNAS
Specific typesEPHRRITIRCRNLRUA
Related approachesSGSNMSC

Detected Changes Across Releases

from 3GPP Change Requests

Specific changes extracted from the „Change history“ tables of 3GPP specifications (4 CRs across 1 releases). Complements the general historical overview above with the evidence-based evolution of this function.

Rel-15 4 changes

In Release 15, RANAP was updated to support enhanced IP addressing capabilities between IPv4/IPv6 capable SGSNs and GGSNs, including during intra-SGSN scenarios. The release also introduced corrections to the SGSN-initiated Update PDP Context Request procedure. Furthermore, it defined support for the User Plane Protocol over the N9 interface.

  • Correction to the SGSN-Initiated Update PDP Context Request TS 29.060CR1063
  • IP addressing between IPv4/IPv6 capable SGSN and GGSN TS 29.060CR1064
  • IP addressing between IPv4/IPv6 capable SGSN/GGSN during intra-SGSN scenarios TS 29.060CR1065
  • User Plane Protocol over N9 TS 29.281CR0095

Explore further

Broader topics and technologies where RANAP plays a role.

Defining Specifications

3GPP specifications that define or reference RANAP, 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 23.060 vj00 GPRS Service Description Stage 2 Rel-19
TS 23.171 v1300 LCS Stage 2 Specification for UMTS Rel-4
TS 23.205 vj00 Bearer Independent CS Core Network Stage 2 Rel-19
TS 23.221 vj00 3GPP System Architectural Requirements Rel-19
TS 23.271 vj00 LCS Stage 2 Specification Rel-19
TS 25.305 vj00 UTRAN UE Positioning Stage 2 Rel-19
TS 25.401 vj00 UTRAN Overall Architecture Rel-19
TS 25.410 vj00 Iu Interface Introduction for UTRAN Rel-19
TS 25.412 vj00 Iu Interface Signalling Transport Specification Rel-19
TS 25.413 vj00 Radio Access Network Application Part (RANAP) Rel-19
TS 25.415 vj00 Iu Interface User Plane Protocol Rel-19
TS 25.423 vj00 UTRAN RNSAP Specification Rel-19
TS 25.820 v820 3G Home NodeB Study Report Rel-8
TR 25.931 vj00 UTRAN Signalling Procedures Examples Rel-19
TS 29.060 vj00 GPRS Tunnelling Protocol (GTP) version 1 Rel-19
TS 29.281 vj20 GTPv1-U Protocol Specification Rel-19
TS 32.251 vj00 PS Domain Charging Management Rel-19
TS 32.408 vj00 UMTS/GSM Performance Management Measurements Rel-19
TS 33.859 vb10 UTRAN Key Hierarchy Enhancement Study Rel-11
TS 37.857 vd10 Study on Indoor Positioning Enhancements Rel-13
TS 43.051 vj00 GERAN Stage 2 Service Description Rel-19
TS 44.060 vj00 GERAN RLC/MAC Protocol Specification Rel-19