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

Glossary term · Mobility

TAC

Tracking Area Code

Mobility →

TAC is a unique identifier assigned to a Tracking Area, a logical grouping of cells within a mobile network, used to page a UE efficiently for an incoming call or data session without knowing its exact cell.

Introduced
Rel-5
Where
Radio Access Network › NG-RAN (5G)
Specifications
23 specs
Also in
Core Network, Services, Management
TAC Description Purpose What changed Neighbours Detected Changes Specifications

Description

The Tracking Area Code (TAC) is a fixed-length code, defined within 3GPP specifications, that uniquely identifies a Tracking Area (TA) within a Public Land Mobile Network (PLMN). A Tracking Area is a collection of one or more cells (eNodeBs/gNBs). The TAC, combined with the PLMN ID, forms the Tracking Area Identity (TAI), which is a globally unique identifier for a TA. The TAC is broadcast in system information (e.g., SIB1 in LTE, SIB1 in NR) by every cell, informing UEs of the TA they are currently located in.

From a UE perspective, the core mobility management procedure involving the TAC is the Tracking Area Update (TAU). A UE is configured with a list of TAIs that form its Registered Tracking Area list. As the UE moves, it monitors the TAC broadcast by the serving cell. If it detects that the current TAI (PLMN ID + TAC) is not present in its registered list, it must perform a TAU procedure with the core network (MME in LTE, AMF in 5GC). This updates the network with the UE's new location at the TA level. The network stores this association between the UE's identifier and its current TA in its databases.

The primary operational role of the TAC is in the paging procedure. When downlink data arrives for an idle UE, the network needs to locate it. Instead of paging the UE in every cell (which would cause excessive signaling), the network pages the UE only in all cells belonging to the TA(s) where the UE is registered. This balances paging load and signaling overhead. The size of a TA is a key network planning parameter: larger TAs reduce the frequency of TAUs (saving UE battery and signaling) but increase the paging load as more cells are involved in a paging request. Smaller TAs have the opposite trade-off. The TAC itself is managed by the network operator and is configured on the base stations and core network elements. In 5G, the concept remains fundamentally the same, though it is managed by the Access and Mobility Management Function (AMF).

Purpose & Motivation

The TAC and Tracking Area concept were introduced to solve the scalability and efficiency problems of earlier location management schemes. In 2G GSM, the location area (LA) served a similar purpose, but with the transition to packet-switched always-on connectivity in 3G/4G, a more efficient method was needed. The core problem is tracking the location of millions of idle UEs to deliver incoming sessions while minimizing signaling overhead and battery consumption.

Before TAs, a network would only know a UE's location at the Routing Area (2G/3G GPRS) or cell level. Paging at the cell level is far too granular and wasteful, while using very large, static location areas could lead to excessive paging traffic in dense areas. The TA concept, introduced with the Evolved Packet System (EPS) in 3GPP Rel-8, provided a flexible, configurable unit for location management. It allows operators to tailor TA sizes and layouts to their traffic and geography. The TAC provides the unambiguous identifier for this logical area. Its creation was motivated by the need for a scalable mobility management framework suitable for the high number of devices and data-centric nature of LTE and later 5G networks, enabling efficient paging and manageable tracking area update signaling.

What changed in its specifications

The latest release-to-release comparison of specifications that define TAC. 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.401Rel-18 → Rel-19

Rel-19 adds Disaster Roaming in EPS, which covers disaster-roaming procedures and attach, tracking area update and mobility signalling. It also adds Time Reference Information Distribution Indication to subscription data and the MME-to-eNB path, along with Store and Forward Satellite operation text.

Full comparison in TS 23.401 →

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

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

Rel-15 9 changes
  • 3 Octet TAC in PANI TS 24.229CR6137
  • Correction of 5GS TAC LSB TS 24.501CR0042
  • Correction of TAC for NG-RAN cells before NSA ASN.1 freeze TS 36.423CR1094
  • Introduction of a Configured TAC into the NR Neighbour Information IE and the Served NR Cell Information IE TS 36.423CR1176
  • Correction of 5GS TAC TS 36.423CR1217
  • Critical correction to the presence of the TAC lists in the Service Area Item IE TS 38.423CR0153

+ 3 more changes

Rel-16 2 changes
  • removing requirement that TAC+SV is used to identify UE model in manufacturer assigned ID TS 23.401CR3549
  • Clarification on TAC presence in Serving Cell Info over X2 TS 36.423CR1539

Defining Specifications

3GPP specifications that define or reference TAC, 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.401 vk10 Evolved Packet System Architecture Rel-20 read
TS 24.229 vk10 IMS SIP/SDP Call Control Protocol Rel-20 read
TS 24.301 vk10 EPS NAS Mobility and Session Management Rel-20 read
TS 24.484 vk10 Mission Critical Services Configuration Management Rel-20 read
TS 24.501 vk10 5GS NAS Protocol Specification Rel-20 read
TS 24.801 v810 CT1 SAE NAS Aspects for EPC Rel-8 read
TS 24.890 vg00 5G NAS Protocol for 5GS Stage 3 Rel-16 read
TS 28.875 vj00 Study on IAB Node Management Rel-19 read
TS 32.836 vc00 NM Centralized Coverage and Capacity Optimization Study Rel-12 read
TS 33.929 3GPP TR 33.929 Rel-5 read
TS 36.300 vj20 E-UTRAN Radio Interface Protocol Architecture Rel-19 read
TS 36.413 vj20 S1 Application Protocol (S1AP) for E-UTRAN Rel-19 read
TS 36.423 vj10 X2 Application Protocol (X2AP) Specification Rel-19 read
TS 36.463 vj00 XwAP Protocol Specification Rel-19 read
TR 36.763 vh00 NB-IoT/eMTC Support for Non-Terrestrial Networks Rel-17 read
TS 37.473 vj00 W1 Application Protocol (W1AP) Specification Rel-19 read
TS 38.401 vj30 NG-RAN Architecture Description Rel-19 read
TS 38.413 vj40 NG Application Protocol (NGAP) Specification Rel-19 read
TS 38.423 vj40 NG-RAN Xn Application Protocol Rel-19 read
TS 38.473 vj40 F1 Application Protocol (F1AP) Rel-19 read
TS 38.742 vk00 GNSS Resilient NR-NTN Operation Study Rel-20 read
TS 48.061 vj00 BTS-TRAU Protocol for HR Speech/Data Rel-19 read