Description
Location Services (LCS) is a comprehensive service capability within 3GPP systems that enables the network or authorized external clients to obtain an estimate of the geographical location of a User Equipment (UE). It is not a single technology but an entire architectural framework defined across core network and radio access, supporting multiple positioning methods. The LCS architecture defines functional roles such as the LCS Client (the entity requesting location), the LCS Server (managing location requests, often the Gateway Mobile Location Centre - GMLC), and the UE or network-based positioning functions.
The positioning process typically begins when an LCS Client sends a location request to the network, often via the GMLC. The GMLC authenticates and authorizes the request, then routes it to the appropriate serving network node (e.g., MSC for CS, MME for PS). The core network node then engages the relevant radio access network (RAN) to perform positioning measurements. Key positioning methods include: Assisted GNSS (A-GNSS), where the network provides assistance data to the UE's GNSS receiver to improve speed and accuracy; Observed Time Difference of Arrival (OTDOA), where the UE measures timing differences from multiple base stations; and Enhanced Cell ID (E-CID), which uses the serving cell identity plus timing advance and angle-of-arrival measurements for a more precise fix than basic Cell ID.
The RAN, equipped with a Location Measurement Unit (LMU) in some cases, facilitates these measurements. For UE-based methods, the UE calculates its own position. For UE-assisted or network-based methods, measurement results are sent to a positioning server in the network (e.g., Evolved Serving Mobile Location Centre - E-SMLC in LTE, Location Management Function - LMF in 5GC) for calculation. The resulting location estimate (e.g., latitude, longitude, uncertainty) is then formatted and delivered back to the requesting LCS Client via the GMLC. The entire process is governed by strict privacy controls; the UE's subscriber must generally have a defined privacy setting allowing such a request, except for mandated services like emergency calls.
Purpose & Motivation
LCS was created to standardize mobile device positioning across the global cellular ecosystem, solving the critical need for reliable, accurate, and network-efficient location information. Initial drivers were regulatory, most notably for emergency caller location (E911 in the US, E112 in Europe). Prior to LCS standardization, proprietary solutions existed, but they lacked interoperability, hindered roaming, and limited the development of a broad commercial location-based services (LBS) market.
The 3GPP LCS framework, introduced in Release 99, provided a unified, scalable architecture that could evolve with the network. It separated the service logic from the underlying positioning technologies, allowing new methods (like OTDOA or A-GNSS) to be incorporated over time without overhauling the entire service layer. This addressed the limitations of simple Cell-ID-based location, which offered poor accuracy, especially in rural areas. By standardizing interfaces like the Le interface for external clients and the SLg/SLh interfaces between core network and positioning nodes, LCS enabled third-party application providers, network operators, and emergency services to access location data in a consistent, secure, and privacy-conscious manner. Its creation was fundamental for safety, lawful interception, fleet management, navigation, and the vast array of modern location-aware applications.
Classification
Release Timeline
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (105 CRs across 5 releases). Complements the general historical overview above with the evidence-based evolution of this function.
In Release 15, the LCS function was newly introduced for the 5G Core network (5GC). This release also included corrections to the LCS Assistance Data Broadcast procedure and finalized the specification by removing an editor's note related to Mobile-Terminated LCS.
In Release 16, the LCS function introduced new capabilities including an LCS indication in 5GMM and 5GS network capabilities, explicit LCS privacy features with a UE privacy profile, and support for LCS Broadcast Assistance. It also enabled sending location services data from 5GMM-IDLE mode via the Control Plane Service Request message and provided clarifications on LCS QoS and client types.
- Addition of LCS indication in 5GMM capability and 5GS NW capability TS 24.501CR1335
- LCS privacy TS 29.503CR0253
- Provision of UE LCS privacy profile TS 29.503CR0365
- Implementing LCS Broadcast Assistance API TS 29.503CR0444
- Correction on LCS privacy selection flow rule TS 23.273CR0002
- Corrections to LCS Privacy feature TS 23.273CR0005
+ 8 more changes
In Release 17, the LCS function was enhanced to support new deployment scenarios and service types. Key additions included specific support for IoT over Non-Terrestrial Networks (NTN) in EPS, AMF functionality for satellite access, and the applicability of Location Services to Standalone Non-Public Networks (SNPN). The release also introduced a new LCS Service Type and addressed reporting procedures for EDT and MO-LR scenarios.
- LCS enhancement for IoT NTN in EPS TS 23.271CR0436
- AMF LCS functionality for satellite access TS 24.571CR0006
- Location Services applicable to SNPN(s) TS 23.273CR0209
- Replacing NR-RAN with ng-eNB in case of EDT reporting of LCS event TS 23.273CR0213
- Corrected service consumer for LCS Broadcast Assistance data TS 29.503CR0597
- LCS Service Type and External Client Type TS 29.515CR0038
+ 2 more changes
In Release 18, the LCS architecture was significantly expanded to include support for Sidelink positioning procedures and the integration of the NWDAF (Network Data Analytics Function) for analytics-assisted services. It also introduced a dedicated Location Services user plane protocol and architecture, enabling new capabilities like a UE establishing a user plane connection to an LCS Client for event reporting. Furthermore, the release added support for LCS in PNI-NPNs and introduced enhancements for subscription data and supplementary services, including UE verification.
- Introduce new feature: support of LCS in PNI-NPN TS 23.273CR0253
- Support of a UE user plane connection to an LCS Client or AF for periodic or triggered 5GC-MT-LR event reporting TS 23.273CR0264
- Introduce Sidelink positioning procedure into LCS architecture TS 23.273CR0297
- Adding NWDAF to LCS architecture TS 23.273CR0298
- Clarification on establishment of LCS user plane connection TS 23.273CR0308
- LCS User Plane Architecture and Interface TS 23.273CR0325
+ 40 more changes
In Release 19, key enhancements for LCS include support for multiple LCS-UPP connections per UE and the introduction of a converged charging architecture for 5G LCS. The release also adds support for LCS with MWAB, clarifies procedures for a UE served by a MWAB-gNB, and introduces a Routing ID per LCS session. Furthermore, it resolves editor's notes on user consent and corrects several protocol elements like the LCS correlation identifier and the non-existent lcs-SL-MTLR operation.
- LCS with MWAB support TS 23.273CR0546
- NW capability for multiple LCS-UPP connections per UE TS 24.501CR6953
- Extend the scope and charging architecture to support 5G LCS converged charging TS 32.271CR0029
- Extend basic priciples, CDR generation and handling for 5G LCS converged charging TS 32.271CR0030
- Extend data description for 5G LCS converged charging TS 32.271CR0033
- Extend charging information and bindings for 5G LCS converged charging TS 32.271CR0034
+ 28 more changes
Explore further
Broader topics and technologies where LCS plays a role.
Defining Specifications
3GPP specifications that define or reference LCS, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TR 21.905 vj00 | 3GPP Technical Terms and Definitions | Rel-19 |
| TS 22.071 vj00 | 3GPP TS 22.071: Location Services (LCS) Stage 1 | Rel-19 |
| TS 22.105 vj00 | Telecommunication Services Framework | Rel-19 |
| TS 22.121 v1400 | Virtual Home Environment Requirements | Rel-5 |
| TS 22.234 vd10 | 3GPP-WLAN Interworking Index Specification | Rel-13 |
| TS 22.261 vk30 | 5G System Service Requirements | Rel-20 |
| TR 22.899 ve00 | Study on Enhanced User Location Reporting | Rel-14 |
| TR 22.935 vd00 | LCS Feasibility Study for 3GPP-WLAN Interworking | Rel-13 |
| TR 22.949 vj00 | Privacy Requirements Study for 3GPP Services | Rel-19 |
| TS 23.078 vj00 | CAMEL Phase 4 Stage 2 Specification | Rel-19 |
| TS 23.127 v1600 | Virtual Home Environment Stage 2 Specification | Rel-6 |
| TS 23.171 v1300 | LCS Stage 2 Specification for UMTS | Rel-4 |
| TS 23.240 vj00 | 3GPP Generic User Profile (GUP) Architecture | Rel-19 |
| TS 23.271 vj00 | LCS Stage 2 Specification | Rel-19 |
| TS 23.273 vj50 | 5G Location Services Stage 2 Architecture | Rel-19 |
| TS 23.280 vk10 | Common Architecture for Mission Critical Services | Rel-20 |
| TS 23.700 vk00 | XR Services Application Enablement Layer | Rel-20 |
| TR 23.758 vh00 | Study on Edge Application Architecture | Rel-17 |
| TS 24.007 vj40 | GSM Um Interface Layer 3 Architecture | Rel-19 |
| TS 24.171 vj00 | NAS Protocol for LCS in E-UTRAN | Rel-19 |
| TS 24.501 vj50 | 5G NAS Protocols Specification | Rel-19 |
| TS 24.571 vj20 | Control Plane LCS Procedures | Rel-19 |
| TS 24.572 vj50 | 5G LCS User Plane Protocol Specification | Rel-19 |
| TS 25.305 vj00 | UTRAN UE Positioning Stage 2 | Rel-19 |
| TS 25.423 vj00 | UTRAN RNSAP Specification | Rel-19 |
| TS 29.118 vj10 | MME-VLR Interface for CS Fallback & SMS | Rel-19 |
| TS 29.171 vj00 | LCS Application Protocol (LCS-AP) Specification | Rel-19 |
| TS 29.172 vj00 | EPC LCS Protocol (ELP) specification | Rel-19 |
| TS 29.503 vj50 | UDM Service Based Interface Stage 3 | Rel-19 |
| TS 29.515 vj50 | Ngmlc Service Based Interface Protocol | Rel-19 |
| TS 29.517 vj40 | 5G AF Event Exposure Service Stage 3 | Rel-19 |
| TS 29.591 vj40 | 5G NEF Southbound Services Stage 3 | Rel-19 |
| TS 32.102 vj00 | Telecom Management Physical Architecture Framework | Rel-19 |
| TS 32.240 vj40 | Charging Management Architecture & Principles | Rel-19 |
| TS 32.250 vj00 | Circuit Switched Offline Charging | Rel-19 |
| TS 32.270 vj00 | MMS Charging Management Specification | Rel-19 |
| TS 32.271 vj20 | 3GPP LCS Charging Management Spec | Rel-19 |
| TS 32.272 vj00 | Charging for Push-to-Talk over Cellular (PoC) | Rel-19 |
| TS 32.296 vj00 | Online Charging System (OCS) Architecture | Rel-19 |
| TS 32.298 vj30 | Charging Data Record (CDR) Parameter Specification | Rel-19 |
| TS 32.808 v1800 | Common User Profile Storage Framework | Rel-8 |
| TS 32.849 vd00 | IMS Roaming Charging Study | Rel-13 |
| TS 32.850 ve00 | IMS Charging Correlation Methods Study | Rel-14 |
| TS 33.107 vj00 | Lawful Interception Architecture & Functions | Rel-19 |
| TS 33.108 vj00 | LI Handover Interface Specification | Rel-19 |
| TS 33.533 vj00 | Security for 5G Ranging & Sidelink Positioning | Rel-19 |
| TS 33.784 vj00 | Security aspects of AI/ML in core network | Rel-19 |
| TS 33.814 vg01 | Security aspects of enhanced Location Services (eLCS) | Rel-16 |
| TS 36.300 vj00 | E-UTRAN Radio Interface Protocol Architecture Overview | Rel-19 |
| TS 36.305 vj00 | UE Positioning in E-UTRAN Stage 2 | Rel-19 |
| TS 36.455 vj00 | LTE Positioning Protocol Annex (LPPa) | Rel-19 |
| TS 36.873 vc70 | 3D Channel Model for LTE Beamforming and FD-MIMO | Rel-12 |
| TS 37.571 vj00 | UE Conformance for Positioning | Rel-19 |
| TS 37.857 vd10 | Study on Indoor Positioning Enhancements | Rel-13 |
| TS 38.305 vj00 | NG-RAN UE Positioning Stage 2 | Rel-19 |
| TS 38.355 vj00 | Sidelink Positioning Protocol (SLPP) | Rel-19 |
| TS 38.753 vj00 | Spatial Channel Model Study for NR Demodulation | Rel-19 |
| TS 38.855 vg00 | Study on NR Positioning Support | Rel-16 |
| TS 38.856 vg00 | Study on local NR positioning in NG-RAN | Rel-16 |
| TR 38.857 vh00 | Study on NR Positioning Enhancements | Rel-17 |
| TR 38.900 vf00 | Channel Model Study for >6 GHz | Rel-15 |
| TR 38.901 vj10 | Channel Model for 0.5-100 GHz | Rel-19 |
| TS 43.051 vj00 | GERAN Stage 2 Service Description | Rel-19 |
| TR 43.901 vj00 | Generic Access to A/Gb Interface Feasibility Study | Rel-19 |
| TS 44.060 vj00 | GERAN RLC/MAC Protocol Specification | Rel-19 |
| TS 44.064 vj00 | GPRS Logical Link Control (LLC) Protocol | Rel-19 |
| TS 44.160 vg00 | GERAN Iu Mode RLC/MAC Protocol Specification | Rel-16 |
| TS 48.018 vj00 | BSS-SGSN Interface for GPRS Control | Rel-19 |
| TS 51.010 vj00 | SIM Application Toolkit Conformance Testing | Rel-19 |
