Location Dependent Service

Description

A Location Dependent Service, as defined in 3GPP TS 23.171 and TS 23.271, is a service provided either by a teleoperator or a third-party service provider that is available (pull type) or is activated (push type) when the user arrives in a certain area. It does not require any subscription in advance, but the push type activation shall be confirmed by the user. The offered service itself can be any kind of service, such as a public Xerox machine or the discount list in a store. This definition is part of the Location Services (LCS) framework and describes a specific class of location-based services that are triggered by the user's presence in a geographic area.

Location Dependent Services are characterized by their area-based triggering. In pull mode, the service is made available to the user when they enter the area, and the user can choose to access it. For example, a user walking into a shopping mall might receive a notification that a discount list is available for download. In push mode, the service is automatically activated when the user enters the area, but the activation must be confirmed by the user to respect privacy and prevent unwanted notifications. This confirmation step is a key privacy safeguard.

The technical realization of Location Dependent Services involves several components of the LCS architecture. The network must be able to detect when a UE enters a specific geographic area. This can be achieved through periodic location reporting, event-based reporting (e.g., geofencing), or network-initiated location requests. The LCS client, which represents the service provider, interacts with the LCS server (e.g., GMLC) to request location information or to subscribe to area event notifications. When the UE enters the target area, the LCS server notifies the LCS client, which then triggers the service logic. The service delivery itself may occur through various channels, such as SMS, IP-based messaging, or application-specific protocols.

Key components include the UE, the RAN, the CN with LCS entities (GMLC, LRF), and the external LCS client. The LCS client is responsible for defining the target area and the trigger conditions. The network ensures that the location information is accurate enough to reliably detect area entry. The user's confirmation for push services is typically handled through a user interface prompt on the UE. Privacy and security are paramount: the user must have control over which services can track their location and when. 3GPP specifications include privacy requirements and mechanisms to protect user location information.

The definition of Location Dependent Service has remained remarkably stable since R99, with only minor wording changes. The core concept—a service triggered by the user's presence in an area, without advance subscription—has not changed. This stability reflects the enduring nature of the service concept, even as the underlying technologies have evolved from 2G to 5G. The examples (public Xerox machine, discount list) may seem dated, but they illustrate the principle: any service that can be tied to a location can be a Location Dependent Service. In modern networks, this concept is realized through technologies like geofencing, proximity services, and location-based advertising.

Purpose & Motivation

The Location Dependent Service concept exists to define a class of services that are inherently tied to the user's geographic location and are triggered by their presence in a specific area. It addresses the need for services that do not require advance subscription, making them easily accessible to users on an ad-hoc basis. This is particularly useful for commercial services (e.g., promotions, information) and public services (e.g., emergency alerts, tourist information). By standardizing the definition, 3GPP enables interoperability and provides a framework for service providers to offer such services across different networks.

Historically, location-dependent services were envisioned as a key differentiator for 3G networks, leveraging the ability to determine user location with reasonable accuracy. The concept was introduced in R99 as part of the LCS specifications. The pull and push models were defined to accommodate different user interaction patterns. The requirement for user confirmation in push mode was included to address privacy concerns and to comply with regulations. Over time, the concept has been applied to a wide range of services, from location-based advertising to intelligent transportation systems.

The definition has remained stable because the fundamental idea is sound and technology-agnostic. However, the implementation has evolved with advances in positioning accuracy, network speed, and device capabilities. Today, location-dependent services are often implemented using IP-based protocols and can be integrated with mobile apps and cloud services. The 3GPP definition provides a solid foundation, while other specifications detail the technical mechanisms for area detection, notification, and service delivery. This separation of concerns allows for innovation while ensuring interoperability.