Location Services Feature

Description

The LCS Feature represents the functional capability of a Public Land Mobile Network (PLMN) to provide Location Services (LCS). It encompasses the complete set of network functions, protocols, and procedures that allow a client (such as an emergency service, a law enforcement agency, or a commercial application) to request and obtain the geographic location of a target User Equipment (UE). The feature is defined in 3GPP Technical Specifications 23.171 and 23.271, which specify the stage 2 architecture and the stage 3 procedures for location services in the circuit-switched and packet-switched domains, respectively.

Architecturally, the LCS Feature relies on a client/server model. The LCS Client is an entity that requests location information from the network. The LCS Server is a network entity that manages the location services and interacts with the LCS Client. The core network elements involved include the Gateway Mobile Location Centre (GMLC), which is the first node an external LCS Client accesses, and the Serving Mobile Location Centre (SMLC) or the evolved SMLC (E-SMLC) in the radio access network, which manages the actual positioning of the UE. The Home Subscriber Server (HSS) or Home Location Register (HLR) stores subscription information related to LCS, including privacy settings and allowed QoS. The UE itself may contain a Location Services (LCS) client and may support various positioning methods.

The operation of the LCS Feature involves several key procedures. When an LCS Client requests location information, the request is routed to the GMLC. The GMLC authenticates the client, checks the target UE's privacy profile, and then queries the HSS/HLR for routing information. Subsequently, the GMLC sends a location request to the serving core network node (e.g., MME, SGSN, or MSC), which then forwards it to the radio access network node (e.g., E-SMLC or SMLC). The radio access network node then initiates positioning procedures with the UE, which may involve network-based methods (e.g., Cell ID, OTDOA, Uplink TDOA) or UE-based methods (e.g., A-GNSS, GNSS). Once the location estimate is obtained, it is returned to the LCS Client through the same path.

The LCS Feature supports various Quality of Service (QoS) parameters, such as horizontal and vertical accuracy, response time, and priority. These parameters allow the network to tailor the positioning method and resource allocation to the specific needs of the application. For example, an emergency call may require high accuracy and low latency, while a commercial application may tolerate lower accuracy and longer response times. The feature also includes privacy mechanisms, such as notification and verification, to ensure that the target UE's location is not disclosed without proper authorization.

Over the releases, the LCS Feature has evolved to support new radio technologies (e.g., LTE, NR), new positioning methods (e.g., NR positioning), and new use cases (e.g., IoT, V2X). The terminology has also been updated, with "Target MS" in R99 being replaced by "Target UE" from Rel-4 onwards, reflecting the shift from circuit-switched mobile stations to multi-mode user equipment. The LCS Feature remains a critical enabler for regulatory services (e.g., E911, E112) and commercial location-based services.

Purpose & Motivation

The LCS Feature exists to provide a standardized framework for determining and delivering the geographic location of mobile devices within a PLMN. It was created to address regulatory mandates, such as emergency call location (E911 in the US, E112 in Europe), which require the network to automatically report the caller's location to emergency services. Additionally, it enables commercial location-based services, such as navigation, asset tracking, and targeted advertising, by offering a secure and controlled way for external clients to request location information.

Before the introduction of LCS, location determination was often proprietary and limited to specific access technologies. The LCS Feature, standardized in 3GPP Release 99, provided a unified architecture that could work across different radio access networks (GSM, UMTS, LTE, and later NR) and core network domains (CS and PS). It solved the problem of interoperability by defining standard interfaces and procedures, allowing LCS Clients to request location from any compliant PLMN. It also introduced privacy and security mechanisms to protect user location data, which was a major concern for both users and regulators.

The feature has continuously evolved to meet new requirements. For instance, the shift from "Target MS" to "Target UE" in Rel-4 reflected the need to support a wider range of devices beyond traditional mobile phones. Later releases added support for new positioning methods, such as A-GNSS and OTDOA, to improve accuracy and availability. The LCS Feature remains essential for public safety, lawful interception, and the growing ecosystem of location-based services.