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

Glossary term · Services

Change of Area

Change of Area

Services →

Change of Area is a deferred location event in which the network reports a subscriber's location or event occurrence immediately after processing a mobility event such as Location Update, Tracking Area Update, or Handover.

Introduced
Rel-8
Where
Services
Specifications
2 specs
Change of Area Description Purpose What changed Neighbours Specifications

Description

Change of Area is a location services (LCS) event defined in 3GPP specifications 22.071 and 22.935. It is one of the events supported for deferred location requests, meaning that the location request is not fulfilled immediately but is instead triggered when a specific condition occurs. In this case, the condition is a change in the subscriber's serving area, which is detected when the network processes a mobility-related procedure for that subscriber. The event is fundamental to location-based services that need to track subscriber movement across network boundaries without continuous polling.

The mechanism works as follows: a Location Services (LCS) client requests a deferred location report for a target subscriber, specifying Change of Area as the triggering event. The network stores this request and monitors the subscriber's mobility events. When the subscriber moves and the network processes a Location Update, Tracking Area Update, Handover, Routing Area Update (RAU), Registration, or RANAP Location Report, the network detects that the subscriber's serving area has changed. The location or the occurrence of the event is then reported to the requesting client in a triggered fashion. The key indicator of area change is typically a change in the Service Area Identifier (SAI) or an equivalent location area identifier, which signals that the subscriber has moved into a new serving area.

The architecture relies on the core network nodes, specifically the Mobile Switching Center (MSC) and the Serving GPRS Support Node (SGSN), to process mobility events and detect area changes. These nodes are responsible for tracking the subscriber's location at the granularity of location areas, routing areas, or tracking areas. When a mobility event occurs, the MSC or SGSN evaluates whether the new location falls outside the previously known area. If so, and if a Change of Area deferred location request is active for that subscriber, the node generates the location report and forwards it to the LCS client through the appropriate gateway. This event-driven approach is efficient because it leverages the existing mobility management signaling rather than requiring dedicated location polling.

Change of Area is particularly important for applications such as fleet management, asset tracking, and location-based billing, where the client needs to know when a subscriber enters or leaves a defined geographic area. It is also used in emergency services and lawful interception scenarios where tracking subscriber movement across network boundaries is required. The event is defined with a high degree of flexibility, allowing the client to specify the target area and the conditions under which the report should be generated. The specifications 22.071 and 22.935 provide the stage 1 and stage 2 service descriptions, respectively, outlining the requirements and functional architecture for LCS.

In summary, Change of Area is a deferred location event that leverages the network's mobility management procedures to detect and report subscriber area changes. It is a core component of the LCS framework, enabling efficient, event-driven location reporting that integrates seamlessly with the core network's mobility management functions. Its definition has remained stable across releases from Rel-8 through Rel-19, reflecting its maturity and foundational role in location services.

Purpose & Motivation

Change of Area exists to provide an efficient, event-driven mechanism for location-based services that need to track subscriber movement across network areas without continuous location polling. Traditional location requests are either immediate (one-shot) or periodic, both of which can be inefficient for applications that only care about area transitions. Change of Area solves this by triggering a location report only when the subscriber actually moves to a new area, leveraging the network's existing mobility management signaling to detect the change. This reduces signaling overhead and battery consumption on the device while providing timely and relevant location information to the LCS client.

Historically, location services in 3GPP networks evolved from basic emergency call location to a rich set of value-added services. The deferred location request framework, including events like Change of Area, was introduced to support applications such as fleet tracking, geo-fencing, and location-based charging. Before this event was standardized, clients had to implement their own polling logic, which was inefficient and placed unnecessary load on the network and devices. The Change of Area event standardized the interaction between the LCS client and the network, ensuring interoperability and consistent behavior across vendors and operators.

The event also addresses the need for scalable location services in mobile networks. As the number of connected devices grows, especially with IoT and machine-type communication, efficient location tracking becomes critical. Change of Area provides a lightweight mechanism that piggybacks on mobility procedures, making it suitable for large-scale deployments. Its stability across releases from Rel-8 to Rel-19 demonstrates its enduring value and the effectiveness of its design.

What changed in its specifications

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

TS 22.071Rel-18 → Rel-19

Rel-19 brings only minor changes to TS 22.071: 1 clause changed, with no change attributed to a release feature.

Full comparison in TS 22.071 →

Release Timeline

Evolution Across Releases

An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.

Rel-8 Initial

Initial definition of Change of Area as a deferred location event, specifying that the network reports the location or event occurrence immediately after processing a mobility event for the new subscriber location, typically detected via Location Update, Tracking Area Update, Handover, RAU, Registration, or RANAP Location Report.

The definition carried over unchanged from Rel-8; no textual revision to the event description.

The definition carried over unchanged from Rel-8; the event continued to be specified identically.

The definition carried over unchanged from Rel-8; no change to the event semantics.

The definition carried over unchanged from Rel-8; the event remained stable.

The definition carried over unchanged from Rel-8; no textual revision.

The definition carried over unchanged from Rel-8; the event description remained identical.

The definition carried over unchanged from Rel-8; no change to the event semantics.

The definition carried over unchanged from Rel-8; the event continued to be specified identically.

The definition carried over unchanged from Rel-8; no textual revision.

The definition carried over unchanged from Rel-8; the event remained stable.

The definition carried over unchanged from Rel-8; no change to the event description.

Defining Specifications

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

SpecificationTitleRelease
TS 22.071 vj00 Location Services (LCS) Stage 1 Rel-19 read
TS 22.935 vd00 LCS Feasibility Study for 3GPP-WLAN Interworking Rel-13 read