RAI

Routing Area Identity

Identifier →
Introduced in R99 Also in: Radio Access Network, Services

RAI is a location area identifier used in 2G and 3G packet-switched networks that uniquely identifies a Routing Area within a PLMN for paging and tracking mobile devices for packet data services.

Category
Identifier
Introduced
R99
Where
Core Network › Legacy Core
Also touches
2 segments
Specifications
21 specs
RAI Description Purpose Related Classification Detected Changes Specifications

Description

The Routing Area Identity (RAI) is a critical identifier in the 2G (GPRS) and 3G (UMTS) packet-switched domain architecture. It uniquely identifies a Routing Area (RA), which is a subdivision of a Location Area (LA) used for circuit-switched services. An RA is a set of cells defined for the purpose of tracking and paging User Equipment (UE) that are using packet data services. The RAI is constructed from several components: the Mobile Country Code (MCC), the Mobile Network Code (MNC), the Location Area Code (LAC), and the Routing Area Code (RAC). Structurally, RAI = MCC + MNC + LAC + RAC. This hierarchical structure allows the network to precisely locate a UE at the routing area level for efficient packet-switched mobility management.

How it works is integral to the GPRS Mobility Management (GMM) and UMTS Mobility Management (MM) procedures. When a UE attaches for packet data services, it performs a Routing Area Update (RAU) procedure with the Serving GPRS Support Node (SGSN), providing its current RAI. The SGSN stores this RAI in the UE's mobility context. While the UE is in a ready state (actively communicating), the network knows its exact cell. When it moves to an idle state, it only performs an RAU when it detects it has entered a new Routing Area (by reading the RAI broadcast on the cell's system information). If an incoming packet arrives for an idle UE, the SGSN initiates paging across all cells belonging to the RAI stored in its context, thereby locating the UE without needing cell-level precision.

Its role is to balance signaling load and paging efficiency. Without RAs, the network would have to page across an entire Location Area (which could be very large) for packet data, increasing paging channel load. By defining smaller RAs specifically for packet-switched traffic, paging is more targeted. The RAI is used in messages between the UE and SGSN (e.g., Attach, RAU requests) and within the core network between SGSNs during inter-SGSN routing area updates. It is a foundational concept for packet-switched mobility, preceding the Tracking Area (TA) concept used in 4G LTE and 5G.

Purpose & Motivation

The RAI was created with the introduction of General Packet Radio Service (GPRS) to enable efficient mobility management for packet-switched data. Prior to GPRS, GSM networks only had Location Areas (LAs) for circuit-switched voice mobility. Packet data traffic patterns (more bursty, potentially longer idle periods) demanded a different granularity for tracking and paging to optimize signaling and resource usage.

The RAI solves the problem of how to locate a packet-data-capable mobile device without incurring excessive signaling overhead. By defining Routing Areas as subsets of Location Areas, the network can track packet-switched UEs more precisely than with the larger LA, leading to more efficient paging. This was a key innovation that separated packet-switched and circuit-switched mobility management, allowing each to be optimized for its respective traffic characteristics. It addressed the limitations of using a single, coarse location area for all services, which would have been inefficient for the nascent mobile data services.

Classification

Related approachesLAITAI

Detected Changes Across Releases

from 3GPP Change Requests

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

Rel-15 2 changes

In Release 15, there were no specific new introductions for the Routing Area Identity (RAI) function detailed in the provided context. The listed Change Requests for this release focus on other areas, such as identity attestation and verification support, and enhancements to NB-IoT contention resolution procedures. Therefore, based on the given materials, Release 15 did not introduce technical modifications to the RAI.

  • Support for identity attestation and verification TS 23.228CR1184
  • Introduction of support for MAC PDU containing UE contention resolution identity MAC control element without RRC response message in NB-IoT TS 36.306CR1570
Rel-16 1 change

In Release 16, the new feature for RAI involved enhancing subscriber identity mapping for HSS selection. This was achieved by introducing a UDR service for mapping an IMS Public Identity to an HSS Group ID. This provides a mechanism to route signaling based on application-specific identities like an IMPU.

  • UDR service for mapping IMS Public Identity to HSS Group ID for HSS selection TS 23.228CR1226
Rel-19 5 changes

In Release 19, the updates to the RAI function focused on enhancing IMS procedures to support third-party user identity information and to optimize media routing for UE-Satellite-UE communication. Specifically, new procedures were introduced for handling third-party identities and for continuing the optimization of media routing in satellite-based scenarios. These changes involved updating the referenced processes for signing and verifying this third-party identity information within the IMS framework.

  • Support of third party user identity information in IMS TS 23.228CR1478
  • Procedure for supporting of third party user identity information in IMS TS 23.228CR1524
  • Mobility procedure for UE-Satellite-UE communication in IMS - continuation of optimized media routing TS 23.228CR1521
  • Update the IETF reference to the process of signing and verifying third party user identity information TS 23.228CR1652
  • Procedure update for optimizing media routing (UE-Satellite-UE communication) TS 23.228CR1680

Explore further

Broader topics and technologies where RAI plays a role.

Defining Specifications

3GPP specifications that define or reference RAI, 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.221 vj00 3GPP System Architectural Requirements Rel-19
TS 23.228 vj50 IMS Stage-2 Service Description Rel-19
TS 23.236 vj00 Intra Domain Connection of RAN Nodes to Multiple CN Nodes Rel-19
TS 23.731 vg00 5G LCS Architecture Enhancement Study Rel-16
TS 23.851 v1600 Network Sharing Architecture for 3G Systems Rel-6
TR 23.923 v1300 Mobile IP+ Feasibility Study for UMTS/GPRS Rel-4
TS 25.331 vj00 UTRAN RRC Protocol Specification Rel-19
TR 25.931 vj00 UTRAN Signalling Procedures Examples Rel-19
TS 29.303 vj10 DNS Procedures for Evolved Packet System Rel-19
TS 32.299 vj00 Diameter Charging Applications for 3GPP Rel-19
TS 32.808 v1800 Common User Profile Storage Framework Rel-8
TS 33.102 vj10 3G Security Architecture Specification Rel-19
TS 33.107 vj00 Lawful Interception Architecture & Functions Rel-19
TS 36.306 vj00 E-UTRA UE Radio Access Capability Parameters Rel-19
TS 36.321 vj00 E-UTRA MAC Protocol Specification Rel-19
TS 36.331 vj00 LTE RRC Protocol Specification Rel-19
TS 43.318 vj00 Generic Access Network (GAN) Stage 2 Rel-19
TR 43.902 vj00 GAN Enhancements Feasibility Study Rel-19
TS 44.318 vj00 Generic Access Network (GAN) Interface Procedures Rel-19