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

Glossary term · Identifier

RAI

Routing Area Identity

Identifier →

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.

Introduced
R99
Where
Radio Access Network › E-UTRAN (LTE)
Specifications
21 specs
Also in
Core Network, Services
RAI Description Purpose What changed Neighbours 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.

What changed in its specifications

The latest release-to-release comparison of specifications that define RAI. 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 →

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

Formally defined and standardized as part of the 3GPP UMTS Release 99 specifications, which integrated GPRS into the 3G architecture. Established the RAI's structure and its central role in packet-switched mobility management procedures between the UE and the SGSN.

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 vj20 3GPP Terminology and Definitions Rel-19 read
TS 23.060 vj00 GPRS Stage 2 Service Description Rel-19 read
TS 23.221 vj00 3GPP System Architectural Requirements Rel-19 read
TS 23.228 vk10 IP Multimedia Core Network Subsystem Rel-20 read
TS 23.236 vj00 Intra Domain Connection of RAN Nodes to Multiple CN Nodes Rel-19 read
TS 23.731 vg00 5G LCS Architecture Enhancement Study Rel-16 read
TS 23.851 v610 Network Sharing Architecture for 3G Systems Rel-6 read
TR 23.923 v300 Mobile IP+ Feasibility Study for UMTS/GPRS R99 read
TS 25.331 vj01 UTRAN Radio Resource Control Protocol Rel-19 read
TR 25.931 vj00 UTRAN Signalling Procedures Examples Rel-19 read
TS 29.303 vk00 DNS Procedures for EPS and 5G Interworking Rel-20 read
TS 32.299 vj00 Diameter Charging Applications for 3GPP Rel-19 read
TS 32.808 v800 Common Profile Storage Framework for User Data Rel-8 read
TS 33.102 vj10 3G Security Architecture Specification Rel-19 read
TS 33.107 vj00 Lawful Interception Architecture & Functions Rel-19 read
TS 36.306 vj30 E-UTRA UE Radio Access Capability Parameters Rel-19 read
TS 36.321 vj30 E-UTRA MAC Protocol Specification Rel-19 read
TS 36.331 vj40 E-UTRA Radio Resource Control (RRC) Protocol Rel-19 read
TS 43.318 vj00 Generic Access Network (GAN) Stage 2 Rel-19 read
TR 43.902 vj00 GAN Enhancements Feasibility Study Rel-19 read
TS 44.318 vj00 Generic Access Network (GAN) Interface Procedures Rel-19 read