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

Glossary term · Mobility

TAU

Tracking Area Update

Mobility →

TAU is a procedure where a mobile device updates the network with its current Tracking Area location to enable efficient paging and mobility management for incoming calls or data sessions.

Introduced
Rel-8
Where
Core Network › Evolved Packet Core
Specifications
12 specs
Also in
Services, Security
TAU Description Purpose What changed Neighbours Detected Changes Specifications

Description

The Tracking Area Update (TAU) is a fundamental mobility management procedure in 3GPP EPS (Evolved Packet System) for LTE and continued in 5GS (5G System). It is initiated by the User Equipment (UE) when it detects that it has entered a new Tracking Area (TA) that is not in its registered TA list, or periodically based on a timer. A Tracking Area is a logical grouping of cells defined for location tracking and paging efficiency. The primary purpose of TAU is to inform the core network—specifically the Mobility Management Entity (MME) in LTE or the Access and Mobility Management Function (AMF) in 5G—of the UE's current location at the TA level, allowing the network to efficiently page the UE when there is downlink data or an incoming call.

The procedure involves signaling messages between the UE and the network. When a UE in idle mode (ECM-IDLE in LTE, CM-IDLE in 5G) moves and selects a new cell, it reads the Tracking Area Identity (TAI) broadcast in the system information. If this TAI is not in the list of TAIs the UE received during its last Attach or TAU procedure (the registered TAI list), the UE initiates a TAU Request message to the network via the selected base station (eNB in LTE, gNB in 5G). This message is forwarded to the MME/AMF. The MME/AMF then updates its location context for the UE, may perform authentication and security procedures, and returns a TAU Accept message containing a new registered TA list and possibly a new temporary identifier (GUTI in LTE, 5G-GUTI in 5G). If the UE is moving to a TA served by a different MME/AMF, an inter-MME or inter-AMF TAU occurs, involving context transfer between the old and new core nodes.

TAU is crucial for balancing signaling load and paging overhead. By grouping cells into TAs, the network does not need to know the UE's exact cell; it only needs to page the UE in all cells of its last known TA(s). The TAU procedure ensures this TA-level location is kept updated. The network can assign a UE a list of multiple TAs (a TA List) to reduce the frequency of TAU signaling—the UE can move within all TAs in the list without performing an update. The parameters controlling TAU, like the periodic TAU timer (T3412), are broadcast by the network and configured in the UE's subscription. TAU also serves to re-establish network connectivity, update security keys, and can trigger other procedures like bearer modification.

Purpose & Motivation

The TAU procedure was introduced with the System Architecture Evolution (SAE) in 3GPP Release 8 for LTE to address the limitations of location management in previous 3GPP systems. In 2G/3G networks, location updates were performed at the Location Area (LA) or Routing Area (RA) level, which were relatively static and could lead to inefficient paging or excessive signaling in high-mobility scenarios. TAU, with the concept of configurable Tracking Areas and TA Lists, provides a more flexible and scalable mechanism optimized for the all-IP, flatter architecture of EPS.

It solves the critical problem of how to efficiently locate idle-mode UEs in a packet-switched network without a permanent connection. Efficient location tracking is essential for mobile-terminated services like voice calls (VoLTE) and push notifications. TAU reduces unnecessary signaling compared to cell-level updates while keeping paging areas optimally sized. The ability to assign a TA List allows the network to tailor the mobility management to user mobility patterns—for example, giving a frequently moving UE a larger TA List to minimize updates. This design was motivated by the need to support always-on connectivity with minimal battery drain on the UE and reduced signaling load on the network, which are key requirements for high-capacity LTE and 5G networks.

What changed in its specifications

The latest release-to-release comparison of specifications that define TAU. Each summary describes the whole specification, not only this term.

TS 23.271Rel-18 → Rel-19

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 →
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 (8 CRs across 3 releases). Complements the general historical overview above with the evidence-based evolution of this function.

Rel-15 5 changes
  • Modify Bearer Request during TAU TS 23.401CR3353
  • Negotiation of long periodic TAU timer value TS 23.401CR3443
  • UE Radio Capability Update using TAU procedure TS 23.401CR3444
  • Update of TAU procedure with SGW change and data forwarding TS 23.401CR3324
  • UE CIoT capability in RRC Connection Establishment request for TAU TS 23.401CR3356
Rel-17 2 changes
  • On Connection Release and Paging Restriction during a mobility TAU in a TA outside the current Registration Area TS 23.401CR3665
  • MUSIM capabilities in TAU for Emergency attached UE TS 23.401CR3679
Rel-18 1 change
  • Support of TAU in Cellular IoT TS 23.401CR3774

Defining Specifications

3GPP specifications that define or reference TAU, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TS 23.271 vj00 LCS Stage 2 Specification Rel-19 read
TS 23.401 vk10 Evolved Packet System Architecture Rel-20 read
TS 23.700 vk10 AI/ML Application Layer Support Phase 2 Rel-20 read
TS 29.303 vk00 DNS Procedures for EPS and 5G Interworking Rel-20 read
TS 29.305 vj00 Interworking Functions for EPS-Legacy Systems Rel-19 read
TS 29.805 v800 IWF for MAP-Diameter Interworking Rel-8 read
TS 32.422 vk30 Trace, MDT and UE Measurement Control Rel-20 read
TS 33.108 vj00 LI Handover Interface Specification Rel-19 read
TS 33.401 vj20 EPS Security Architecture Rel-19 read
TS 33.859 vb10 UTRAN Key Hierarchy Enhancement Study Rel-11 read
TR 36.763 vh00 NB-IoT/eMTC Support for Non-Terrestrial Networks Rel-17 read
TS 45.820 vd10 CIoT for Internet of Things Rel-13 read