LAU

Location Area Update

Mobility →
Introduced in Rel-4

LAU is the procedure where a mobile device informs the network of its current Location Area to enable efficient paging and mobility management, triggered by movement into a new area or periodically.

Category
Mobility
Introduced
Rel-4
Where
Radio Access Network › UTRAN (3G)
Specifications
3 specs
LAU Description Purpose Related Classification Specifications

Description

The Location Area Update (LAU) procedure is a fundamental mobility management process in GSM, UMTS, and LTE (though superseded by Tracking Area Update in LTE). A Location Area (LA) is a group of cells defined within the network. The core network, specifically the Visitor Location Register (VLR) and Mobile Switching Center (MSC), tracks the UE's LA to know where to page it for mobile-terminated transactions. The LAU is initiated by the UE when it detects, from broadcast system information, that it has entered a cell belonging to a new LA.

The procedure begins with the UE sending an LAU Request message on the Random Access Channel (RACH), including its Temporary Mobile Subscriber Identity (TMSI) and the old Location Area Identity (LAI). This message is routed to the new VLR/MSC serving the new LA. The new VLR then contacts the old VLR (using the old LAI) or the Home Location Register (HLR) to authenticate the subscriber and retrieve the subscriber's profile. Upon successful authentication and validation, the new VLR updates its database, allocates a new TMSI for privacy, and sends an LAU Accept message to the UE, which includes the new TMSI if reallocation occurred.

Key components are the UE, the Base Station Subsystem (BSS) or Radio Network Subsystem (RNS), the MSC/VLR, and the HLR. The LAU ensures the network's location information for the UE is accurate without requiring constant signaling. It balances the need to locate the UE for incoming calls against the signaling load and UE battery consumption. Periodic LAU timers also force updates even if the UE remains stationary, ensuring the network does not retain stale location data.

Purpose & Motivation

The LAU procedure was created to solve the critical problem of locating a mobile subscriber within a large network without requiring continuous, power-intensive signaling. In early mobile systems, the network needed a method to track approximate user location to deliver calls efficiently. The purpose of LAU is to provide a compromise between precise, real-time location tracking and network/device resource conservation.

It addresses the limitations of not having any location tracking, which would require network-wide paging for every incoming call—a highly inefficient use of radio resources. By grouping cells into Location Areas, the network only needs to know the UE's current LA. The UE updates the network only when crossing an LA boundary, significantly reducing signaling overhead compared to cell-level updates. This design is fundamental for scalability and battery life.

Historically, LAU was a cornerstone of GSM mobility management, enabling nationwide and international roaming. Its creation was motivated by the need for an automated, subscriber-transparent method to keep network location data current. It solves the problems of call delivery failure and excessive paging traffic, forming the basis for mobility management that evolved into Routing Area Update for GPRS and Tracking Area Update for LTE/5G.

Classification

Part ofTAI
Related approachesRAIVLR

Evolution Across Releases

Rel-4 Initial

Defined as a core mobility management procedure in GSM and carried forward into UMTS. Established the signaling flow between UE, MSC, and VLR for updating location. Included mechanisms for periodic updates, IMSI attach/detach, and authentication during the update process to ensure network security and resource management.

Explore further

Broader topics and technologies where LAU plays a role.

Defining Specifications

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

SpecificationTitleRelease
TR 21.905 vj00 3GPP Technical Terms and Definitions Rel-19
TR 25.967 vj00 Home NodeB RF Requirements Technical Report Rel-19
TS 33.859 vb10 UTRAN Key Hierarchy Enhancement Study Rel-11
Patrick Zandl

About the author: Patrick Zandl (b. 1974)

Telecommunications specialist, technology journalist (founder of the Mobil server), and developer who has been running since 2025 — the largest Czech-language resource on AI-assisted programming. Formerly Chief Wizard Architect at Prusa3D and head of development for Turris at CZ.NIC; currently a consultant and instructor on AI implementation in companies.