Location Client Function

Description

The Location Client Function (LCF) is a key component in 3GPP location services (LCS) architecture, acting as the endpoint that requests and consumes location information. It resides either within the User Equipment (UE) as a mobile-originated location request (MO-LR) client or in an external entity such as a service provider's server (known as a value-added LCS client). The LCF formulates a location request, specifying parameters like the target UE (or itself if in the UE), required quality of service (QoS) such as accuracy and response time, and the type of location information needed (e.g., current or periodic location). This request is sent via standardized interfaces to the network's Location Server, typically the Gateway Mobile Location Centre (GMLC) or Evolved Serving Mobile Location Centre (E-SMLC), depending on the network generation.

Upon receiving the request, the network's location system (involving the Radio Access Network and core network nodes) performs the positioning calculation using methods like Observed Time Difference of Arrival (OTDOA), Assisted GNSS (A-GNSS), or Enhanced Cell ID (E-CID). The resulting location estimate is then delivered back to the LCF through the same interfaces. If the LCF is external, the response is routed via the GMLC and possibly the Home Subscriber Server (HSS) for authorization. If internal to the UE, the response may come directly from the serving network's location server. The LCF may also support deferred location requests, where the location is reported at a later time or upon a triggering event, requiring the LCF to manage session continuity.

The LCF plays a crucial role in enabling a wide range of location-based services (LBS), including emergency services (e.g., E911), navigation, fleet tracking, and proximity-based marketing. It must adhere to privacy regulations, often involving user consent mechanisms as defined in 3GPP specs. Architecturally, the LCF interfaces with the Le reference point (for external clients) or the LTE positioning protocol (LPP) for UE-based interactions. Its implementation ensures that applications can obtain location data without needing to understand the underlying radio access technology, abstracting the complexities of positioning techniques into a standardized service request model.

Purpose & Motivation

The Location Client Function (LCF) was created to standardize how clients request and receive location information from 3GPP networks, addressing the growing demand for location-based services (LBS). Prior to its formalization, proprietary solutions led to fragmentation, making it difficult for service providers to develop applications across different networks and devices. The LCF, introduced in R99 as part of the Location Services (LCS) feature, provided a unified interface for location requests, enabling interoperability and scalability.

The primary problem the LCF solves is the decoupling of location service consumers from the complex network positioning mechanisms. By defining a clear client role, 3GPP allowed diverse entities—from UE applications to external servers—to access location data seamlessly. This was particularly critical for regulatory services like emergency calling, where reliable and fast location retrieval is mandatory. The LCF also addresses privacy and security concerns by incorporating authentication and authorization procedures, ensuring that only permitted clients can access a user's location, thus building trust in LBS adoption.

Historically, the motivation stemmed from the evolution of mobile networks beyond voice to value-added services. As GSM transitioned to UMTS, the need for a standardized location framework became apparent to support emerging applications. The LCF, along with other LCS components, provided the foundation for commercial and safety services, fostering innovation in areas like navigation and asset tracking. Its continued evolution through releases reflects enhancements in accuracy, reduced latency, and support for new positioning methods, ensuring it meets the demands of modern use cases such as IoT and V2X communications.

Key Features

• Initiates location requests for itself or other UEs
• Supports mobile-originated and external client scenarios
• Specifies QoS parameters like accuracy and response time
• Interfaces with network location servers via standardized protocols
• Handles deferred and periodic location reporting
• Incorporates privacy and authorization controls

Evolution Across Releases

Defining Specifications