Description
A Tracking Area (TA) is a core concept in the mobility management of 3GPP systems, defined for the Evolved Packet System (EPS) and continued in 5G System (5GS). It is a logical area comprising one or several cells served by one or more base stations (eNBs in LTE, gNBs in NR). The network groups cells into TAs to manage the location of UEs that are not actively connected (i.e., in RRC_IDLE state in LTE or RRC_INACTIVE/IDLE in NR). Each TA is identified by a Tracking Area Code (TAC), which is broadcast in system information (SIB1) within each cell.
The core procedure involving TAs is the Tracking Area Update (TAU). When a UE in idle mode moves from a cell belonging to one TA to a cell in a different TA not listed in its registered TA list, it must perform a TAU procedure with the core network (MME in EPS, AMF in 5GS). This updates the UE's location at the core network, ensuring the network can page the UE when an incoming session arrives. To provide flexibility and reduce signaling, a UE can be registered to multiple TAs simultaneously (a TA list). The UE does not need to perform an update as long as it is within any TA in its list. The assignment of a TA list is part of the attach or registration procedure.
TA design is a critical network planning task. Larger TAs reduce the frequency of TAUs but increase paging load, as the network must page the UE across all cells in the entire TA (or TA list). Smaller TAs increase TAU signaling but make paging more precise. Networks often deploy a hierarchical or layered TA structure to balance these trade-offs, especially in dense urban environments. In 5GS, the concept is extended with Tracking Area Identity (TAI = MCC + MNC + TAC) and supports features like registration area, which can consist of TAs, or in non-3GPP access, different identifiers. The TA mechanism is integral to the network's ability to efficiently reach UEs for mobile-terminated services while conserving UE battery and network signaling resources.
Purpose & Motivation
The Tracking Area concept was introduced to address the scalability and efficiency challenges of mobility management in packet-switched cellular networks. Earlier circuit-switched systems like GSM used Location Areas (LAs) and Routing Areas (RAs) for similar purposes, but with the always-on nature of IP services in 3G and beyond, a more optimized approach was needed. The TA mechanism solves the problem of how to track a potentially massive number of idle UEs without requiring constant, precise location updates, which would overwhelm signaling channels and drain UE batteries.
Its creation was motivated by the need to reduce signaling overhead associated with mobility in LTE/EPC (from 3GPP R99/Rel-99 concepts evolved). By allowing registration to a list of TAs and requiring updates only upon leaving that list, it significantly decreases the frequency of location update procedures compared to single-area registration. This is crucial for supporting seamless mobility for always-connected devices and for enabling efficient paging—the network only needs to broadcast paging messages within the UE's last known TA(s), not across the entire network. The TA framework provides the foundation for core network entities (MME, AMF) to manage UE mobility states and is essential for the scalability of massive IoT deployments where devices may be stationary or mobile.
What changed in its specifications
The latest release-to-release comparison of specifications that define TA. Each summary describes the whole specification, not only this term.
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 →Rel-19 brings only minor changes to TS 23.271: 0 clauses changed, with no change attributed to a release feature.
Full comparison in TS 23.271 →Release Timeline
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (21 CRs across 5 releases). Complements the general historical overview above with the evidence-based evolution of this function.
- Handling of forbidden PLMNs, forbidden PLMN for GPRS service and equivalent PLMNs list on ATTACH ACCEPT and TRACKING AREA ACCEPT in RLOS TS 24.301CR3294
- Avoiding too frequent tracking area updating procedures due to signalling of UE radio capability ID TS 24.301CR3374
- Service area restrictions, case missing for when UE is out of allowed tracking area list and RA TS 24.501CR1853
- Consistent usage of "tracking area updating procedure" TS 24.301CR3341
- Correction to UE radio capability ID inclusion during TRACKING AREA UPDATE procedure TS 24.301CR3490
- Releasing NAS signalling connection and Paging restriction during mobility TAU in a TA outside the current Tracking Area List for MUSIM UE in EPS TS 24.301CR3645
- Removal of bullet irrelevant to tracking area concept TS 24.501CR2627
- "No suitable cells in tracking area" not applicable to non-3GPP access TS 24.501CR3090
- Condition of including equivalent PLMNs in ATTACH ACCEPT message and TRACKING AREA UPDATE ACCEPT message TS 24.301CR3797
- Clarification on the periodic tracking area updating procedure when timer T3412 expires TS 24.301CR3847
- Handling of the unavailability information in the tracking area updating procedure TS 24.301CR3954
- Deletion of 5GS forbidden tracking area per entry of list of subscriber data. TS 24.501CR5438
- Removal of Editor's note for NTN tracking area handling TS 23.501CR4775
- Support of Store and Forward (S&F) satellite operation - tracking area update procedure TS 24.301CR4209
- RAT utilization control in periodic tracking area updating TS 24.301CR4122
- No RAT utilization control IE in TRACKING AREA UPDATE ACCEPT TS 24.301CR4123
- Access technology utilization control IE in periodic tracking area update procedure TS 24.301CR4479
Defining Specifications
3GPP specifications that define or reference TA, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 03.071 v890 | GSM Location Services Stage 2 | R99 read |
| TR 21.905 vj20 | 3GPP Terminology and Definitions | Rel-19 read |
| TS 23.050 | 3GPP TS 23.050 | R99 read |
| TS 23.171 v390 | LCS Stage 2 for UMTS | R99 read |
| TS 23.271 vj00 | LCS Stage 2 Specification | Rel-19 read |
| TS 23.501 vk30 | 5G System Architecture | Rel-20 read |
| TR 23.758 vh00 | Study on Edge Application Architecture | Rel-17 read |
| TS 24.292 vj00 | IMS Centralized Services (ICS) Protocol | Rel-19 read |
| TS 24.301 vk10 | EPS NAS Mobility and Session Management | Rel-20 read |
| TS 24.501 vk10 | 5GS NAS Protocol Specification | Rel-20 read |
| TS 24.890 vg00 | 5G NAS Protocol for 5GS Stage 3 | Rel-16 read |
| TS 25.224 vj00 | UTRA TDD Physical Layer Procedures | Rel-19 read |
| TS 25.766 vd10 | Network-Assisted Interference Cancellation for UMTS | Rel-13 read |
| TR 25.912 vj00 | Evolved UTRA and UTRAN Technical Report | Rel-19 read |
| TS 27.007 vk00 | AT Command Interface for Mobile Terminals | Rel-20 read |
| TS 28.628 vj00 | SON Policy NRM IRP Information Service | Rel-19 read |
| TS 29.007 vj00 | PLMN-PSTN/ISDN Interworking Requirements | Rel-19 read |
| TS 29.171 vj10 | LCS-AP between MME and E-SMLC (SLs) | Rel-19 read |
| TS 29.513 vk10 | 5G PCC Signalling Flows | Rel-20 read |
| TS 29.518 vk10 | AMF Service Based Interface | Rel-20 read |
| TS 29.565 vk10 | TSCTSF Service-Based Interface | Rel-20 read |
| TS 29.890 vg00 | CT3 5G System Technical Report | Rel-16 read |
| TS 32.102 vj00 | Telecom Management Physical Architecture Framework | Rel-19 read |
| TS 33.929 | 3GPP TR 33.929 | R99 read |
| TS 35.205 vj00 | MILENAGE Algorithm Set: General Overview | Rel-19 read |
| TS 35.234 vj00 | MILENAGE-256 Algorithm Set Specification | Rel-19 read |
| TR 35.909 vj00 | 3GPP MILENAGE Algorithm Design Report | Rel-19 read |
| TR 35.937 vj00 | MILENAGE-256 Algorithm Set Specification | Rel-19 read |
| TS 36.104 vj20 | E-UTRA/NB-IoT Base Station RF Requirements | Rel-19 read |
| TS 36.116 vj00 | E-UTRA Relay RF Requirements | Rel-19 read |
| TS 36.117 vj00 | E-UTRA Relay RF Test Methods & Requirements | Rel-19 read |
| TS 36.141 vj10 | RF Test Methods for LTE and NB-IoT Base Stations | Rel-19 read |
| TS 36.213 vj50 | LTE Physical Layer Procedures | 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 36.331 vj40 | E-UTRA Radio Resource Control (RRC) Protocol | Rel-19 read |
| TR 36.763 vh00 | NB-IoT/eMTC Support for Non-Terrestrial Networks | Rel-17 read |
| TS 36.855 vd00 | E-UTRA Positioning Enhancements Study | Rel-13 read |
| TS 36.896 ve00 | Study on Flexible eNB-ID and Cell-ID in E-UTRAN | Rel-14 read |
| TS 37.320 vj40 | MDT Overall Description (Stage 2) | Rel-19 read |
| TS 38.133 vk10 | NR Radio Resource Management Requirements | Rel-20 read |
| TS 38.174 vk00 | NR Integrated Access and Backhaul Requirements | Rel-20 read |
| TS 38.176 vj40 | IAB Conformance Testing | Rel-19 read |
| TS 38.213 vj50 | NR Physical Layer Control Procedures | Rel-19 read |
| TS 38.300 vj40 | NR and NG-RAN Overall Description | Rel-19 read |
| TS 38.742 vk00 | GNSS Resilient NR-NTN Operation Study | Rel-20 read |
| TR 38.808 vh00 | Study on NR above 52.6 GHz to 71 GHz | Rel-17 read |
| TS 38.811 vf40 | Study on NR Support for Non-Terrestrial Networks | Rel-15 read |
| TS 43.059 vj00 | GERAN LCS Stage 2 Specification | Rel-19 read |
| TS 43.064 vj00 | GPRS Radio Interface Lower-Layer Functions | Rel-19 read |