Description
The Location Management Client (LMC) is a functional entity defined within the 3GPP service-based architecture for location services. It acts as a requestor and consumer of location information. The LMC can be implemented within a User Equipment (UE), an Application Function (AF), or other network entities that require location data. Its primary role is to initiate location requests towards the network's location management system, specifically the Location Management Function (LMF) or the Gateway Mobile Location Centre (GMLC), depending on the architecture and service scenario. The LMC formulates location service requests, which can include parameters such as the target UE's identifier, the required Quality of Service (e.g., accuracy, response time), and the type of location information needed (e.g., immediate location, periodic tracking, or triggered reporting).
Upon sending a request, the LMC communicates over standardized service-based interfaces, such as Nlmf_Location or N5g-eir_LocationReporting, to the appropriate network function. The network processes the request, which may involve coordinating with the Radio Access Network (RAN) and the UE itself to perform positioning measurements using techniques like Observed Time Difference of Arrival (OTDOA), Uplink Time Difference of Arrival (UTDOA), or Assisted Global Navigation Satellite System (A-GNSS). Once the location is determined, the network delivers the location estimate or report back to the LMC.
The LMC's architecture is designed to be flexible, supporting both UE-based and network-based location procedures. In UE-based scenarios, the LMC within the UE may interact directly with the LMF to obtain assistance data for positioning or to report its own calculated location. In AF-based scenarios, an external application server (hosting the LMC) requests location information for a target UE, enabling services like fleet tracking, emergency services, or location-based advertising. The LMC abstracts the complexities of the underlying positioning technologies from the application, providing a standardized API for location service consumption.
Key components of the LMC's operation include its service interface bindings, security context for authenticating and authorizing location requests, and its ability to handle different location service types defined in 3GPP, such as Mobile Terminated Location Request (MT-LR), Mobile Originated Location Request (MO-LR), and Network Induced Location Request (NI-LR). Its role is crucial for enabling the 5G location service ecosystem, ensuring that applications can reliably and securely access UE location data while respecting privacy regulations and network policies.
Purpose & Motivation
The LMC was introduced to standardize and simplify the client-side interface for accessing network-based location services in 5G and beyond. Prior to its definition, location service requests from applications or UEs often relied on proprietary or less integrated methods, leading to fragmentation and increased complexity for application developers and network operators. The LMC provides a unified, service-based approach aligned with the 5G Core Network's architectural principles.
Its creation was motivated by the growing demand for precise, low-latency location services across various verticals, including industrial IoT, automotive (V2X), augmented reality, and public safety. These applications require a reliable and efficient mechanism to request and receive location data. The LMC addresses this by offering a standardized client function that can be embedded in different entities (UEs, AFs), facilitating interoperability and enabling new business models for location-based services.
Furthermore, the LMC supports regulatory requirements, such as enhanced emergency caller location (e.g., for E911 in the US or E112 in Europe), by providing a defined path for emergency service applications to request UE location. It also enhances privacy and security by integrating with 3GPP's authentication and authorization frameworks, ensuring that location information is only disclosed to authorized clients under permitted conditions.
What changed in its specifications
The latest release-to-release comparison of specifications that define LMC. Each summary describes the whole specification, not only this term.
Rel-19 adds Enhanced Mission Critical Architecture changes, including location reporting trigger cancel and override indication. It also adds location reporting and location information request procedures for mission critical clients on non-3GPP devices behind a UE or 5G-RG.
Full comparison in TS 23.280 →Rel-19 added FRMCS Phase 5, including optional functional alias in IWF private calls and optional application-specific data in IWF responses and end requests.
Full comparison in TS 23.283 →Technology family
Location services architecture · Services
- R98 BSSAP-LE, BSSLAP, GMLC, LMU, RRLP, SMLC
- Rel-5 PCAP, SAS
- Rel-6 PPR, R-GMLC
- Rel-7 LRF, SUPL
- Rel-9 E-SMLC, LCS-AP, LPP, LPPa
- Rel-15 LMF, NRPPa
- Rel-18 LCS-UPP, RSPP, SLPP
Also in this family (introduction release not pinned to a single defining specification): H-GMLC, LMC, MLP, V-GMLC
Members and relations were proposed independently by several models and kept only where at least two agree; quotes are verified verbatim against the specifications. Release = first approved version of the defining specification.
Release Timeline
Detected Changes Across Releases
verified against 3GPP sourcesDocumented changes in 2 releases, each verified against the text of 3GPP specifications or approved change requests and shown with the exact wording. The release timeline above shows the same releases. A release without an entry has no documented change for this term.
The Location Management Client (LMC) is introduced in TS 23.280 with defined LMC–LMS location information report, subscription, notification and history request/report message tables.
- “LMC Location Management Client” TS 23.280 v17.10.0
- “Table 10.9.2.5-2: Location information subscription request (LMC – LMS)” TS 23.280 v17.10.0
- “Table 10.9.2.13-1: Location information history request (LMC – LMS)” TS 23.280 v17.10.0
Rel-18 adds LMC behaviour: local restriction of location dissemination, authorization to set or cancel triggers at an LMC, and inter-RAT change reporting from the LMC to the LMS.
- “In accordance with local policies, the LMC can apply local restrictions by stopping providing location information when a location dissemination request has been activated.” TS 23.280 v18.13.1
- “Triggering criteria can contain the inter-RAT trigger information if the inter-system RAT changes information is expected from the LMC” TS 23.289 v18.11.0
- Corrections to inter-RAT change report via LMC and LMS TS 23.289CR0084
Defining Specifications
3GPP specifications that define or reference LMC, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.280 vk51 | Mission Critical Services Architecture | Rel-20 read |
| TS 23.283 vk10 | Mission Critical Communication Interworking | Rel-20 read |
| TS 23.700 vk10 | AI/ML Application Layer Support Phase 2 | Rel-20 read |