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

Glossary term · Protocol

RANAP

Radio Access Network Application Protocol

Protocol →

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.

Introduced
R99
Where
Radio Access Network › UTRAN (3G)
Specifications
23 specs
Also in
Core Network, Services
RANAP Description Purpose What changed Neighbours 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.

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.

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 23.060Rel-18 → Rel-19

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.

R99 Initial

Introduced as the foundational protocol for the Iu interface in the first UMTS release. Defined core procedures for RAB management, SRNS relocation, paging, and transparent NAS transport to support both circuit-switched and packet-switched services over the new WCDMA-based UTRAN.

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 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 Enhancement Study Rel-11 read
TS 37.857 vd10 Study on Indoor Positioning Enhancements 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