Description
The Location Management Function (LMF) is a critical component of the 5G Core Network's location service architecture, defined as a Network Function (NF) within the Service-Based Architecture (SBA). It is the primary entity responsible for orchestrating all positioning-related activities to determine the geographical location of a User Equipment (UE). The LMF receives location service requests from other network functions, such as the Gateway Mobile Location Centre (GMLC) for external applications or the Access and Mobility Management Function (AMF) for network-initiated requests. Upon receiving a request, the LMF initiates a positioning session with the target UE and the Radio Access Network (RAN).
The LMF's operation involves several key steps. First, it selects the appropriate positioning method based on the requested Quality of Service (QoS), UE capabilities, and network conditions. Supported methods include LTE/5G NR downlink and uplink techniques like Observed Time Difference of Arrival (OTDOA), Uplink Time Difference of Arrival (UTDOA), Multi-Cell Round Trip Time (Multi-RTT), and Assisted Global Navigation Satellite System (A-GNSS). The LMF coordinates with the NG-RAN (Next Generation RAN) via the AMF using the NLs interface to instruct gNBs to perform necessary measurements (e.g., timing measurements for OTDOA) or to configure positioning reference signals. For UE-based methods, the LMF may provide assistance data (e.g., satellite ephemeris, base station almanac) to the UE to facilitate its own position calculation.
Architecturally, the LMF exposes service-based interfaces, primarily Nlmf_Location, to other NFs. It interacts with the AMF (Nlmf_Location service) to reach the UE and RAN, and with the GMLC (Ngl interface) for external location requests. The LMF also interfaces with the Unified Data Management (UDM) for subscriber data and policy retrieval. It performs the location calculation by processing measurement reports received from the RAN (e.g., gNB measurements) and/or the UE. The final location estimate, which can be in the form of geographical coordinates (latitude, longitude) with an uncertainty ellipse, is then returned to the requesting entity.
Beyond basic positioning, the LMF supports advanced features such as periodic and triggered location reporting, velocity estimation, and barometric sensor data fusion for vertical positioning. It also handles error cases, fallback procedures, and QoS negotiation. In a network slicing context, the LMF can be instantiated as part of a slice to provide dedicated location services for specific verticals (e.g., high-accuracy positioning for factory automation). Its design emphasizes scalability, low latency, and support for diverse use cases from mass-market consumer services to mission-critical industrial applications.
Purpose & Motivation
The LMF was introduced in 3GPP Release 15 as part of the new 5G System (5GS) to provide a unified, flexible, and enhanced location management capability. It addresses the limitations of previous generations (e.g., 4G E-SMLC) by being natively integrated into the 5G Service-Based Architecture, offering improved scalability, lower latency, and support for new radio technologies like 5G NR. The shift to a cloud-native, microservices-based design allows the LMF to be deployed dynamically to meet varying service demands.
Its creation was driven by the need for more accurate and reliable location services to support emerging 5G use cases. These include Vehicle-to-Everything (V2X) communication for autonomous driving, which requires cm-level accuracy; Industrial IoT for asset tracking and automation; and enhanced emergency services (e.g., Advanced Mobile Location) mandated by regulators. The LMF provides the core intelligence to coordinate multiple positioning sources and methods to meet these stringent requirements.
Furthermore, the LMF enables network operators to offer location as a service to third-party application providers in a standardized and secure manner. By centralizing positioning coordination, it reduces complexity in the RAN and UE, allows for optimized resource usage, and facilitates the introduction of new positioning technologies (like sidelink positioning) in future releases. It is a foundational element for realizing 5G's vision of pervasive, high-precision location awareness.
What changed in its specifications
The latest release-to-release comparison of specifications that define LMF. Each summary describes the whole specification, not only this term.
Rel-19 adds LMF-based AI/ML positioning support with Nlmf_DataExposure services. It also adds periodic location event procedures based on NRPPa measurements, MWAB location service clauses, and enhanced network automation enablers.
Full comparison in TS 23.273 →Rel-19 added MPQUIC steering to multi-access PDU sessions, XR and media handling, and an Energy Information Function. It also added Local Offloading Management for edge computing, Vertical Federated Learning for AI/ML, and Ambient IoT text.
Full comparison in TS 23.501 →Architecture
Where it sits in the network
- Mobile Network → 5G Core → LMF (Location Services)
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
- LMF counterpart in another generation: E-SMLC
“Similarly, to the E-SMLC in the LTE architecture (TS 36.305 [25]), the LMF either includes or has an interface to an SPC function, as defined in OMA SUPL V2.0 ([15], [16]).” TS 38.305
- LMF used together with LPP
“A target device is the UE in the control-plane case or SET or UE in the user-plane case, and a positioning server is the LMF in the control-plane case or SLP or LMF in the user-plane case.” TS 38.305
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 6 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 LMF is specified for the first time in Rel-15: it manages positioning of UEs, selects positioning methods, and offers the Nlmf service-based interface.
- “The LMF manages the support of different location services for target UEs, including positioning of UEs and delivery of assistance data to UEs.” TS 38.305 v15.10.0
- “The Location Management Function (LMF) is the network entity in the 5G Core Network (5GC) supporting the following functionality:” TS 29.572 v15.7.0
- “The LMF offers to other NFs the following services:” TS 29.572 v15.7.0
LMF gained new Rel-16 roles: broadcasting positioning assistance data via NG-RAN with ciphering keys, periodic/triggered location, and NR RAT-dependent positioning interactions with gNB (SRS configuration).
- “An LMF can interact with any NG-RAN node reachable from any of the AMFs with signalling access to the LMF in order to provide assistance data information for broadcasting.” TS 38.305 v16.10.0
- “LocationContextTransfer: It enables a consumer NF to transfer location context information for periodic or triggered location of a target UE to a new LMF.” TS 29.572 v16.11.0
- Addition of the LMF Broadcast Service Operations TS 29.572CR0042
In Rel-17 the LMF gained new behaviour: it determines local or geographical coordinates by LCS client type, supports scheduled location time, selects positioning methods for integrity, and handles on-demand PRS.
- “The coordinate type(s) is determined by LMF when receiving a location request, based on LCS Client type and supported GAD shapes.” TS 23.273 v17.11.0
- “When sending a location request to the UE, the LMF may include the scheduled location time.” TS 23.273 v17.11.0
- “Support of this feature implies the LMF shall be able to provide the integrity result for location estimates” TS 29.572 v17.13.0
Rel-18 extends the LMF with user plane positioning to the UE over a secure connection, PRU association handling, and MBSR location derivation, plus new service operations and local LMF selection.
- “LMF supports verification of a PRU initiated Association or Disassociation by checking whether there is an PRU verified indication from AMF.” TS 23.273 v18.12.0
- “To trigger the UE to establish or re-establish an LCS secured user plane connection between the UE and the LMF, the LMF shall provide the user plane connection information” TS 24.572 v18.5.0
- Procedures of positioning over the user plane connection between UE and LMF TS 23.273CR0310
In Rel-19 the LMF gains LMF-based AI/ML positioning: it can calculate UE location with an ML model, obtain models from NWDAF, and provide input data for training and monitoring.
- “The LMF may calculate the UE location and estimate the achieved accuracy by using LMF-based AI/ML Positioning.” TS 23.273 v19.7.0
- “LMF may obtain ML model from NWDAF for performing AI/ML Positioning.” TS 23.273 v19.7.0
- LMF enhancements for LMF-based AI/ML Positioning TS 23.273CR0574
The cause #5 condition for a missing source LCS secured user plane connection now looks up the connection by source LMF routing information instead of the source LMF LCS-UP address.
- “the LCS secured user plane connection cannot be found with the source LMF routing information” TS 24.572 v20.0.0
- “the LCS secured user plane connection cannot be found with the source LMF LCS-UP address” TS 24.572 v20.0.0
Defining Specifications
3GPP specifications that define or reference LMF, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.273 vj70 | 5G Location Services Architecture Stage 2 | Rel-19 read |
| TS 23.501 vk30 | 5G System Architecture | Rel-20 read |
| TS 23.700 vk10 | AI/ML Application Layer Support Phase 2 | Rel-20 read |
| TS 24.501 vk10 | 5GS NAS Protocol Specification | Rel-20 read |
| TS 24.571 vj50 | 5G NAS Location Services (LCS) | Rel-19 read |
| TS 24.572 vk00 | 5G LCS User Plane Protocol | Rel-20 read |
| TS 24.890 vg00 | 5G NAS Protocol for 5GS Stage 3 | Rel-16 read |
| TS 29.517 vk10 | AF Event Exposure Service | Rel-20 read |
| TS 29.518 vk10 | AMF Service Based Interface | Rel-20 read |
| TS 29.520 vk10 | 5G NWDAF Services | Rel-20 read |
| TS 29.552 vk10 | 5G Network Data Analytics Procedures | Rel-20 read |
| TS 29.572 vk10 | 5G LMF Service-Based Interface | Rel-20 read |
| TS 29.574 vk10 | DCCF Service Based Interface | Rel-20 read |
| TS 29.576 vk10 | MFAF Service Based Interface | Rel-20 read |
| TS 29.591 vk10 | NEF Southbound Services | Rel-20 read |
| TS 33.127 vj80 | Lawful Interception Architecture | Rel-19 read |
| TS 33.533 vj00 | Security for 5G Ranging & Sidelink Positioning | Rel-19 read |
| TS 33.814 vg01 | Security aspects of enhanced Location Services (eLCS) | Rel-16 read |
| TR 33.893 vi01 | Security and Privacy Aspects of Ranging and Sidelink Positioning | Rel-18 read |
| TS 37.171 vj00 | UE Positioning Performance Requirements | Rel-19 read |
| TS 37.355 vj30 | LTE Positioning Protocol (LPP) | Rel-19 read |
| TS 38.171 vj10 | 5G A-GNSS UE Positioning Requirements | Rel-19 read |
| TS 38.305 vj30 | NG-RAN UE Positioning Stage 2 | Rel-19 read |
| TS 38.355 vj20 | Sidelink Positioning Protocol (SLPP) Specification | Rel-19 read |
| TS 38.413 vj40 | NG Application Protocol (NGAP) Specification | Rel-19 read |
| TS 38.455 vj30 | NR Positioning Protocol A | Rel-19 read |
| TS 38.473 vj40 | F1 Application Protocol (F1AP) | Rel-19 read |
| TS 38.843 vj00 | Study on AI/ML for NR Air Interface | Rel-19 read |
| TS 38.856 vg00 | Study on local NR positioning in NG-RAN | Rel-16 read |
| TR 38.857 vh00 | Study on NR Positioning Enhancements | Rel-17 read |