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

Glossary term · Identifier

RAC

Routing Area Code

Identifier →

RAC is a numeric code that uniquely identifies a Routing Area within a Location Area in GSM and UMTS networks for efficient device tracking and paging.

Introduced
R99
Where
Radio Access Network › UTRAN (3G)
Specifications
15 specs
Also in
Core Network, Services
RAC Description Purpose What changed Neighbours Specifications

Description

The Routing Area Code (RAC) is a fundamental identifier within the mobility management architecture of 2G (GSM/GPRS) and 3G (UMTS) networks. It is defined as part of the Routing Area Identity (RAI), which itself is structured as RAI = MCC + MNC + LAC + RAC. The RAC is an 8-bit value, allowing for 256 unique codes per Location Area. A Routing Area (RA) is a subdivision of a Location Area (LA) and represents a group of cells. While an LA is used for circuit-switched (CS) mobility (like voice calls), the RA concept was introduced specifically for packet-switched (PS) domain mobility management in GPRS. The Serving GPRS Support Node (SGSN) uses the RAI to manage the mobility context of attached User Equipment (UE). When a UE moves between RAs, it performs a Routing Area Update (RAU) procedure with the network, informing the SGSN of its new location for efficient packet data routing.

Operationally, the RAC enables more granular location tracking than the LAC alone. For idle mode UE in the PS domain, the network knows the UE's registered RA. When downlink packet data arrives, the network pages the UE across all cells within that specific RA, rather than the entire LA, reducing paging channel load and improving network efficiency. The RAC is broadcast by each cell in the system information, allowing the UE to detect when it has crossed an RA boundary. The definition and management of RACs are network planning decisions, typically aligned with SGSN service areas and traffic patterns.

The RAC's role is integral to the GPRS/UMTS attach and routing area update procedures. During attach, the UE provides its last known RAI (if available) to the network. The SGSN uses this, along with the LAC, to potentially retrieve the UE's MM context from a previous SGSN. The RAC remains a stable identifier across 3GPP releases for 2G/3G systems, though its relevance diminishes with the introduction of Tracking Areas (TAs) in LTE/EPC, which serve a similar but more advanced purpose for 4G mobility management. Nonetheless, for legacy interworking and multi-RAT operations, understanding RAC is essential.

Purpose & Motivation

The RAC was created to introduce efficient packet-switched mobility management in GSM networks with the advent of GPRS. Prior to GPRS, GSM used Location Areas (LAs) for circuit-switched mobility, but paging an entire LA for sporadic packet data traffic was inefficient and consumed excessive radio resources. The RAC enables subdivision of LAs into smaller Routing Areas, allowing the network to track UE location with finer granularity for packet data services. This reduces the paging load for data sessions, conserves UE battery life through less frequent location updates compared to cell-level tracking, and optimizes signaling traffic on the radio interface and core network.

Historically, the separation of CS and PS location management was a key design principle. The LA, identified by the LAC, remained for voice services, while the new RA, identified by the RAC, was introduced for data. This dual-mobility management approach allowed operators to deploy and scale GPRS independently of their existing voice network architecture. The RAC solved the problem of applying circuit-switched paging strategies, which were designed for regularly incoming calls, to the bursty and unpredictable nature of early mobile data traffic. It established a foundation for always-on IP connectivity in mobile networks.

What changed in its specifications

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

Introduced as a core component of GPRS mobility management within the UMTS Release 99 framework. The RAC was defined as an 8-bit field within the Routing Area Identity, enabling the subdivision of a Location Area for more efficient packet-switched paging and location tracking. Its architecture and purpose were established in the core GPRS specifications, such as TS 23.060.

Defining Specifications

3GPP specifications that define or reference RAC, 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
TR 23.923 v300 Mobile IP+ Feasibility Study for UMTS/GPRS R99 read
TS 25.423 vj00 UTRAN RNSAP Specification Rel-19 read
TS 25.467 vj00 UTRAN Architecture for 3G Home Node B Rel-19 read
TR 25.912 vj00 Evolved UTRA and UTRAN Technical Report Rel-19 read
TS 32.251 vj00 PS Domain Charging Management Rel-19 read
TS 32.272 vj00 Charging for Push-to-Talk over Cellular (PoC) Rel-19 read
TS 32.293 vj00 Proxy Function in Domestic Service Provider Rel-19 read
TS 36.300 vj20 E-UTRAN Radio Interface Protocol Architecture Rel-19 read
TS 36.302 vj00 E-UTRA Physical Layer Services 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