Radio Access Network Application Protocol

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.

Key Features

• Manages the establishment, modification, and release of Radio Access Bearers (RABs)
• Handles SRNS Relocation for transferring UE context between RNCs
• Transparently transfers Non-Access Stratum (NAS) messages between UE and Core Network
• Controls the overall Radio Interface System (RAB) configuration and QoS parameters
• Initiates paging of UEs in specific service areas
• Supports overload and error handling between the Core Network and UTRAN

Evolution Across Releases

Defining Specifications