Description
The Tracking Area Identifier (TAI) is a structured code that uniquely identifies a Tracking Area within a Public Land Mobile Network (PLMN). A Tracking Area is a logical grouping of one or more cells, defined by the network operator for the purpose of tracking and paging User Equipment (UE) in idle or inactive states. The TAI is constructed from the Mobile Country Code (MCC), Mobile Network Code (MNC), and a Tracking Area Code (TAC). The MCC and MNC identify the PLMN, while the TAC, typically 16 bits in length, is assigned by the operator to differentiate Tracking Areas within that PLMN. This hierarchical structure ensures global uniqueness and efficient routing of location management messages.
Architecturally, the TAI is a key parameter used by both the Radio Access Network (RAN) and the Core Network (CN), particularly the Access and Mobility Management Function (AMF) in 5G. When a UE moves, it performs Tracking Area Updates (TAU) to inform the network when it enters a new TA, as identified by a change in TAI. The network maintains a list of TAIs for each UE, known as the Tracking Area Identity List (TAI List), which allows the UE to move within multiple TAs without frequent updates, optimizing signaling. The AMF uses the TAI to determine the appropriate serving area and to manage paging; when a downlink message arrives for an idle UE, the network pages the UE across all cells belonging to the TAIs in its registered list.
In operation, the TAI is broadcast by each cell in the System Information Blocks (SIBs), allowing the UE to detect its current TA. During initial registration or attach procedures, the UE reports the TAI of the cell it is camped on. The AMF validates this TAI against its configured areas and may assign a new TAI List. For mobility, if a UE in idle mode detects a TAI not in its assigned list, it triggers a TAU procedure. The TAI also plays a role in network slicing and policy enforcement, as certain slices or services may be restricted to specific Tracking Areas. Its design balances the need for precise location knowledge with the imperative to minimize signaling, a critical consideration for network scalability and UE battery life.
Purpose & Motivation
The TAI was introduced to address the challenges of location management and paging efficiency in cellular networks, particularly as networks evolved to support packet-switched services and increased mobility. Prior to the concept of Tracking Areas, location management was often cell-based, leading to excessive signaling overhead as UEs moved, especially in idle mode. This was inefficient for both network resources and UE battery consumption. The creation of Tracking Areas, identified by TAIs, allowed networks to group cells into larger logical areas, enabling the network to track UEs at a coarser granularity during idle periods, thereby reducing the frequency of location update signaling.
Historically, in 2G/GSM, location areas served a similar purpose, but with the advent of 3G/UMTS and especially 4G/LTE (where TAI was formally standardized in Release 8), the need for a more streamlined, IP-centric architecture became apparent. The TAI provides a standardized, scalable method for mobility management that is independent of the underlying radio technology, supporting seamless evolution from LTE to 5G. It solves the problem of efficiently locating a UE for incoming calls or data sessions without requiring constant, fine-grained location reporting. By optimizing the trade-off between location accuracy and signaling load, the TAI enables networks to support massive numbers of devices, a necessity for the Internet of Things (IoT) and widespread mobile broadband.
Furthermore, the TAI facilitates network operations such as load balancing, emergency service routing, and regulatory compliance for location reporting. It is a foundational element for features like Registration Areas in 5G, which extend the concept to include multiple types of areas (e.g., Tracking Areas, Registration Areas). The TAI's design ensures backward compatibility and forward flexibility, allowing operators to reconfigure their TA layouts as network topology and traffic patterns change without impacting core protocols.
Classification
Release Timeline
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (69 CRs across 5 releases). Complements the general historical overview above with the evidence-based evolution of this function.
In Release 15, key clarifications and corrections were introduced for the Tracking Area Identity (TAI) function, including the provision of the TAI list to the RAN by the AMF for RRC Inactive UEs and clarifications on TAI list assignment for different 5G RATs. The release also resolved editor's notes concerning different TAIs for 4G and 5G and specified the use of TAI in procedures such as NgRanTargetId selection. Furthermore, it defined the advertisement of the 5GS TAI by a UE-to-Network Relay to assist remote UEs, as part of the 5G ProSe architecture.
- Clarification on TAI list assignment for different 5G RATs TS 23.501CR0145
- Clarification on N3GPP TAI TS 23.501CR0304
- Correction to TAI list generation TS 23.501CR0488
- TAI List provision to RAN by AMF for RRC Inactive UE TS 23.501CR0605
- Correction on TAI list coding TS 24.301CR2952
- TAI removed from list of Servie area lists after reject from network TS 24.501CR0263
+ 3 more changes
In Release 16, enhancements to the Tracking Area Identifier (TAI) function included clarifications and corrections for Standalone Non-Public Networks (SNPN), specifically regarding forbidden TAI lists and the usage of the last visited registered TAI during SNPN registration. The release also introduced clarifications on the TAI Slice Support List and refined procedures for handling Allowed NSSAI when a Registration Area includes a TAI belonging to an Equivalent PLMN. Furthermore, it addressed abnormal cases in the UE Configuration Update procedure related to new TAI lists and the handling of NAS message transmission failures with delayed TAI changes.
- Clarification to forbidden TAI lists for SNPN TS 24.501CR1551
- Correction to UCU procedure abnormal cases on NW side for a new TAI list TS 24.501CR1848
- Clarification of forbidden TAI lists for SNPN TS 24.501CR1923
- Handling of allowed NSSAI when the RA includes the TAI belonging to EPLMN TS 24.501CR2198
- NAS message transmission failure indication with delayed TAI change TS 24.501CR2375
- Clarification to the usage of last visited registered TAI in SNPN registration TS 24.501CR2562
+ 6 more changes
In Release 17, key enhancements for the Tracking Area Identifier (TAI) function included new support for Non-Terrestrial Networks (NTN), such as indicating a last visited registered TAI for NR Satellite and IoT NTN access. The release also introduced refinements for slice-based restrictions using TAI(s) based on analytics and clarified the handling and configuration of forbidden TAI lists, including for non-3GPP access and within broadcast TACs. Furthermore, procedures were defined for the delivery of forbidden TAI(s) to the UE by both the MME and AMF, and cleanup was performed on current TAI selection and terminology.
- Indicating a last visited TAI in a Registration for NR Satellite Access TS 23.501CR3379
- Forbidden TAI list IEs in ATTACH and TAU REJECT messages TS 24.301CR3761
- Definition and handling of current TAI(s) TS 24.301CR3737
- Definition of last visited registered TAI for IoT NTN in EPS TS 24.301CR3743
- Update Non-3GPP TAI to support N3SLICE TS 24.501CR3336
- Handling of forbidden TAI(s) within broadcast TACs in registration procedure TS 24.501CR4131
+ 18 more changes
In Release 18, enhancements to the Tracking Area Identifier (TAI) function included improved handling for non-3GPP access by including the last visited registered TAI for the registration procedure. The release also introduced TAI-based location assistance information for 5G ProSe Layer-3 Remote UEs and provided clarifications and corrections for procedures involving forbidden TAI lists, deregistration, and the handling of the current TAI.
- Equivalent SNPNs: last visited TAI TS 24.501CR5029
- TAI Range List in AreaOfValidity TS 29.518CR0988
- Correction to the term Current TAI TS 24.301CR3983
- Handling of current TAI in case of reception of Forbidden TAI IEs TS 24.501CR4848
- Corrections to TAI list handling in deregistration and FTAI storing TS 24.501CR5052
- Including last visited registered TAI for registration procedure over non-3gpp access TS 24.501CR5453
+ 9 more changes
In Release 19, enhancements to the TAI function clarified UE behavior when both a Forbidden TAI list and an Access technology utilization control IE are received, and specified that the current TAI is not stored in the list of forbidden tracking areas for roaming. The release also defined TAI list allocation procedures and refined the Tracking Area Update (TAU) procedure triggered by the UE being out of its TAI list, including its interaction with the service request procedure.
- No TAI to FTAI list due to RAT restriction TS 24.301CR4270
- No TAI to FTAI list due to RAT restriction TS 24.501CR6751
- TAI list allocation TS 23.401CR3943
- TAU procedure triggered by the UE being out of the TAI list overrides timer T3451 - service request procedure TS 24.301CR4384
- UE behaviour if both the Forbidden TAI(s) for the list of Forbidden tracking areas for roaming IE and the Access technology utilization control IE are included TS 24.301CR4440
- Current TAI is not stored in list of forbidden tracking areas for roaming TS 24.301CR4478
+ 3 more changes
Explore further
Broader topics and technologies where TAI plays a role.
Defining Specifications
3GPP specifications that define or reference TAI, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.304 vk00 | 5G Proximity Services (ProSe) Stage 2 | Rel-20 |
| TS 23.401 vj50 | Evolved Packet System (EPS) Stage 2 Description | Rel-19 |
| TS 23.501 vk00 | 5G System Architecture Stage 2 | Rel-20 |
| TS 23.558 vk00 | Architecture for Edge Applications | Rel-20 |
| TS 23.700 vk00 | XR Services Application Enablement Layer | Rel-20 |
| TS 23.712 vd00 | Enhancements to Warning Status Reporting Mechanisms | Rel-13 |
| TR 23.758 vh00 | Study on Edge Application Architecture | Rel-17 |
| TS 24.301 vj60 | NAS protocol for Evolved Packet System | Rel-19 |
| TS 24.501 vj50 | 5G NAS Protocols Specification | Rel-19 |
| TS 24.801 v810 | CT1 SAE NAS Aspects for EPC | Rel-8 |
| TS 24.890 vg00 | 5G NAS Protocol for 5GS Stage 3 | Rel-16 |
| TR 26.917 vj00 | TV Service Enhancements over 3GPP | Rel-19 |
| TR 28.840 vi10 | Technical Report | Rel-18 |
| TS 28.875 vj00 | Study on IAB Node Management | Rel-19 |
| TS 29.122 vj40 | T8 Reference Point for Northbound APIs | Rel-19 |
| TS 29.303 vj10 | DNS Procedures for Evolved Packet System | Rel-19 |
| TS 29.518 vj50 | AMF Service Based Interface Protocol | Rel-19 |
| TS 29.522 vj40 | 5G NEF Northbound APIs Stage 3 | Rel-19 |
| TS 29.543 vj20 | 5G Data Transfer Policy Control Services Stage 3 | Rel-19 |
| TS 29.554 vj10 | 5G Background Data Transfer Policy Control Service | Rel-19 |
| TS 29.558 vj40 | Enabling Edge Applications | Rel-19 |
| TS 29.890 vg00 | CT3 5G System Technical Report | Rel-16 |
| TS 31.117 vj10 | USIM Application Toolkit Test for Non-Removable UICC | Rel-19 |
| TS 31.127 vi40 | UICC-terminal interaction testing specification | Rel-18 |
| TS 32.299 vj00 | Diameter Charging Applications for 3GPP | Rel-19 |
| TS 33.127 vj50 | Lawful Interception Architecture and Functions | Rel-19 |
| TS 33.401 vj10 | EPS Security Architecture | Rel-19 |
| TS 33.701 vj00 | Study on mitigations against bidding down attacks | Rel-19 |
| TS 33.897 vd10 | Security for Isolated E-UTRAN Operation (IOPS) | Rel-13 |
| TS 36.413 vj10 | S1 Application Protocol (S1AP) | Rel-19 |
| TS 36.875 vd10 | Dual Connectivity Extension Requirements | Rel-13 |
| TS 37.473 vj00 | W1 Application Protocol (W1AP) Specification | Rel-19 |
| TS 37.822 vc10 | SON Enhancements for UE Types and Active Antennas | Rel-12 |
| TS 38.413 vj10 | NG Application Protocol (NGAP) | Rel-19 |
| TS 38.423 vj10 | Xn Application Protocol (XnAP) specification | Rel-19 |
| TS 38.473 vj10 | 5G F1 Application Protocol (F1AP) | Rel-19 |
| TS 43.318 vj00 | Generic Access Network (GAN) Stage 2 | Rel-19 |
| TS 44.318 vj00 | Generic Access Network (GAN) Interface Procedures | Rel-19 |
| TS 48.018 vj00 | BSS-SGSN Interface for GPRS Control | Rel-19 |
