Predefined Area

Description

A Predefined area is a geographical zone defined independently of cellular radio coverage — that is, it is not equivalent to a cell, a location area, a routing area, or any other radio-network topology element. Instead, it is a logical geographic region that the network and the mobile station both understand, and the mobile may take special action when it recognizes that it has entered or left such an area. This concept is specified in 3GPP TS 23.171 (Location Services enhancements) and TS 23.271 (Functional stage 2 description of Location Services), and it has been part of the 3GPP vocabulary since Release 99.

The Predefined area concept works by combining the mobile's ability to determine its own position (via GPS, OTDOA, cell ID, or other positioning methods) with a stored definition of one or more geographic zones. These zones can be defined by the network operator or by the user, and they are typically expressed as geographic coordinates, polygons, or other geometric shapes. When the mobile detects that its current position lies inside or outside a defined area, it can trigger a range of actions: reporting its location to the network, starting or stopping a particular application, changing its behavior (e.g., disabling certain radios), or notifying the user. The key distinction from cell-based area concepts is that the Predefined area is purely geographic — it does not change when cells are added, removed, or reconfigured, and it can span multiple cells or networks.

Architecturally, the Predefined area is supported by the Location Services (LCS) framework. The LCS architecture includes the Gateway Mobile Location Centre (GMLC), the Serving Mobile Location Centre (SMLC), and the Location Retrieval Function (LRF), which together manage positioning requests and deliver location information. The mobile's role is to monitor its position and compare it against the stored area definitions. In some implementations, the network may also monitor the mobile's location and send triggers, but the definition explicitly allows the mobile itself to recognize entry or exit and take action autonomously. This makes the concept flexible: it can be used for network-controlled services (e.g., emergency call routing based on location) as well as user-centric services (e.g., reminders when arriving home or at work).

The Predefined area is closely related to other location concepts such as the Location Area (LA) and Routing Area (RA), but it differs fundamentally in that those are radio-network constructs used for paging and mobility management, whereas the Predefined area is a service-oriented geographic construct. It also relates to the concept of a 'geofence' in modern terminology. In 3GPP, the Predefined area enables features like Location-Based Services (LBS), zone-based charging, and area-triggered notifications. Because it is not tied to cell coverage, it remains stable across handovers, cell reselections, and even roaming between networks, provided the mobile can determine its position.

Over successive releases, the definition has remained remarkably stable, reflecting the enduring utility of the concept. Minor editorial changes (e.g., 'a geographical area' vs. 'geographical area') have appeared, but the core meaning — a geographic zone independent of radio coverage, with entry/exit triggering special mobile actions — has not changed from R99 through Rel-19. This stability underscores the fact that the Predefined area is a service-level abstraction that does not depend on the underlying radio access technology, making it applicable to GERAN, UTRAN, E-UTRAN, and NR alike.

Purpose & Motivation

The Predefined area concept was created to enable location-based services and area-triggered behaviors that cannot be adequately expressed using cell or radio coverage boundaries. In early cellular networks, the only way to approximate a user's location was by identifying the cell or location area they were in. However, cells vary widely in size and shape, and their coverage changes with network deployment, making them unsuitable for defining stable geographic zones for services. A user's home, workplace, or a specific city district does not map cleanly to a cell, and cell boundaries can shift with new base station deployments or radio parameter tuning. The Predefined area solves this by decoupling the service definition from the radio topology: it defines a geographic region in absolute terms, so that the same area remains valid regardless of how the network is deployed or reconfigured.

Historically, the concept emerged in Release 99 alongside the first standardized Location Services (LCS) architecture in 3GPP. Before LCS, location-based triggers were proprietary or based on coarse cell-ID information. The introduction of positioning methods such as Cell-ID, OTDOA, and GPS in UMTS made it feasible for mobiles to determine their position with sufficient accuracy to support geographic zones. TS 23.171 and TS 23.271 defined how these zones could be used, including the ability for the mobile to autonomously detect entry and exit. This was particularly important for regulatory services like emergency call location and for commercial services like fleet management, asset tracking, and personalized notifications.

The Predefined area also addresses the need for user privacy and autonomy. Because the mobile can take action locally upon recognizing entry or exit, the user's location need not be continuously reported to the network. This allows services to operate with minimal signaling overhead and improved privacy. In later releases, the concept has been extended to support more sophisticated geofencing and IoT applications, where devices may need to trigger actions based on their geographic context without constant network interaction. The enduring presence of the Predefined area in 3GPP specifications from R99 to Rel-19 demonstrates its fundamental value as a building block for location-aware services across multiple generations of mobile technology.