MO-LR

Mobile Originated Location Request

Services →
Introduced in R99 Also in: Core Network, Radio Access Network

MO-LR is a location service feature where a mobile device initiates a request to the network to obtain its own geographical position or the position of another target device.

Category
Services
Introduced
R99
Where
Services › IMS
Also touches
2 segments
Specifications
25 specs
MO-LR Description Purpose Related Classification Detected Changes Specifications

Description

Mobile Originated Location Request (MO-LR) is a procedure within the 3GPP Location Services (LCS) architecture that enables a User Equipment (UE) to act as a LCS Client, initiating a request to determine its own location or the location of another specified target UE. The process involves signaling between the UE, the serving core network, and the Location Management Function (LMF) in 5G or the Evolved Serving Mobile Location Centre (E-SMLC) in LTE. The UE sends a location request via a dedicated LCS protocol message over the control plane.

Upon receiving an MO-LR request, the network authenticates and authorizes the requesting UE based on subscriber profiles. For a self-location request, the network then invokes the appropriate positioning method. This could be network-based (e.g., Observed Time Difference of Arrival - OTDOA in LTE, Downlink Time Difference of Arrival - DL-TDOA in NR), UE-based (using assistance data like GPS/GNSS), or hybrid methods. The serving node (MME/AMF) coordinates with the positioning server (E-SMLC/LMF) which calculates the location estimate. The resulting position (latitude, longitude, accuracy) is then delivered back to the requesting UE in a location response message.

If the request is for another target UE (subject to privacy verification), the network performs a location request towards that target (akin to a Mobile Terminated Location Request - MT-LR), obtains the location, and returns it to the originating UE. Key architectural components include the LCS Client in the UE, the LCS protocol in the NAS layer, the core network control node (MSC, SGSN, MME, AMF), the positioning server (SMLC, E-SMLC, LMF), and the radio access network which provides measurement data (e.g., PRS measurements for OTDOA).

The role of MO-LR in the network is to support user-centric location-based services (LBS). It empowers the end-user to actively retrieve location information, differentiating it from network-initiated or emergency location services. It is a fundamental enabler for commercial applications, providing the standardized control-plane mechanism for devices to obtain their own coordinates for use in mapping, social networking, asset tracking, and augmented reality applications. The procedure includes privacy safeguards, requiring user consent and authorization checks.

Purpose & Motivation

MO-LR was developed to standardize a method for mobile devices to actively request location information from the network, enabling a wide range of user-driven location-based services. Prior to standardized LCS, location capabilities were proprietary or limited to network-initiated services (e.g., for lawful intercept). The creation of MO-LR addressed the growing market demand for applications like turn-by-turn navigation, location-aware search, and person-to-person location sharing.

It solved the problem of providing a reliable, secure, and operator-controlled mechanism for devices to obtain accurate positioning. Without MO-LR, applications would rely solely on onboard GPS, which has limitations indoors, in urban canyons, and for devices without GPS hardware. MO-LR leverages network-based positioning methods (e.g., cell-ID, OTDOA) and assisted-GNSS (A-GNSS) to provide faster, more accurate, and more battery-efficient location fixes than standalone GPS.

The technology was motivated by the commercial potential of LBS and the need for interoperability across devices and networks. It provided a standardized API of sorts within the network signaling, allowing application developers to build services knowing that a consistent method to retrieve location existed. It also introduced necessary privacy controls, ensuring that a user's location could not be retrieved by another party without authorization, balancing service innovation with subscriber protection.

Classification

Part ofLCS
Specific typesOTDOAA-GNSS
Related approachesMT-LR

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

Specific changes extracted from the „Change history“ tables of 3GPP specifications (21 CRs across 4 releases). Complements the general historical overview above with the evidence-based evolution of this function.

Rel-16 6 changes

In Release 16, the 5GC-MO-LR procedure was completed and clarified, specifically regarding positioning access selection within the 5G Core network. The release also introduced an additional function to the MO-LR procedure and applied corrections to its specifications for LTE, NR, and the overall stage 2 description. These updates standardized how a mobile station can request its own location, assistance data, or ciphering keys for broadcast messages from the network.

  • Clarification on positioning access selection in the 5GC-MO-LR procedure TS 23.273CR0008
  • Completion of 5GC-MO-LR Procedure for TS 23.273 TS 23.273CR0025
  • Corrections to MO-LR procedure TS 23.273CR0061
  • Additional function of MO-LR procedure TS 24.571CR0003
  • Correction to LTE stage2 spec for MO-LR TS 36.305CR0104
  • Correction to NR stage2 spec for MO-LR TS 38.305CR0072
Rel-17 6 changes

In Release 17, the enhancements to the MO-LR function specifically focused on its integration and operation within the 5G Core (5GC), introducing the new "5GC-MO-LR" procedure. Key additions included the ability for a mobile station to subscribe to and receive location assistance data via MO-LR, and the definition for using a requested maximum age of location within this 5G context. The release also provided clarifications on the use of service type and service identity parameters within the MO-LR procedure.

  • Add MO-LR subscribed Assistance Data TS 23.273CR0145
  • Add the usage of the requested maximum age of location in the 5GC-MO-LR TS 23.273CR0164
  • Assistance Data Delivery in 5G-MO-LR TS 23.273CR0161
  • Clarification on use of service type and service identity in MO-LR procedure TS 23.273CR0194
  • Update MO-LR procedure TS 23.273CR0215
  • LCS Service Type in MO-LR TS 29.515CR0069
Rel-18 7 changes

In Release 18, the key enhancements for the MO-LR function introduced new procedures for Sidelink Positioning and Ranging, specifically the SL-MO-LR procedure. The release also addressed handling for network congestion during an SL-MO-LR response and added support for MBSR within the 5GC-MO-LR procedure. Furthermore, it included updates to UE capability signaling for both SL-MT-LR and SL-MO-LR operations.

  • Ranging and Sidelink Positioning MO-LR procedure TS 23.273CR0322
  • Additional of the SL-MO-LR procedure TS 24.571CR0044
  • SL-MO-LR response in case of network congestion TS 24.571CR0059
  • SL-MO-LR for Ranging and Sidelink Positioning corrections TS 23.273CR0416
  • MBSR support in 5GC-MO-LR procedure TS 23.273CR0461
  • UE Capability Update for SL-MT-LR and SL-MO-LR TS 23.273CR0486

+ 1 more changes

Rel-19 2 changes

In Release 19, the enhancements to the MO-LR function included the addition of a specific message flow for converged charging within the 5G Core Network (5GC) context. Furthermore, a correction was made to the explanatory note in the specification text concerning the normal operation procedure for the SL-MO-LR variant.

  • Add message flow of converged charging for 5GC-MO-LR TS 32.271CR0032
  • Correction to the NOTE in normal operation for SL-MO-LR TS 24.571CR0085

Explore further

Broader topics and technologies where MO-LR plays a role.

Defining Specifications

3GPP specifications that define or reference MO-LR, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TS 03.071 v7b0 Location Services (LCS) Stage 2 Description Rel-7
TR 21.905 vj00 3GPP Technical Terms and Definitions Rel-19
TS 23.171 v1300 LCS Stage 2 Specification for UMTS Rel-4
TS 23.271 vj00 LCS Stage 2 Specification Rel-19
TS 23.273 vj50 5G Location Services Stage 2 Architecture Rel-19
TS 23.700 vk00 XR Services Application Enablement Layer Rel-20
TR 23.730 ve00 Study on extended CIoT architecture Rel-14
TS 24.171 vj00 NAS Protocol for LCS in E-UTRAN Rel-19
TS 24.514 vj30 Ranging & Sidelink Positioning in 5GS Rel-19
TS 24.571 vj20 Control Plane LCS Procedures Rel-19
TS 29.171 vj00 LCS Application Protocol (LCS-AP) Specification Rel-19
TS 29.515 vj50 Ngmlc Service Based Interface Protocol Rel-19
TS 29.522 vj40 5G NEF Northbound APIs Stage 3 Rel-19
TS 32.250 vj00 Circuit Switched Offline Charging Rel-19
TS 32.251 vj00 PS Domain Charging Management 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.293 vj00 Proxy Function in Domestic Service Provider Rel-19
TS 36.305 vj00 UE Positioning in E-UTRAN Stage 2 Rel-19
TS 36.355 vj00 LTE Positioning Protocol (LPP) Rel-19
TS 37.355 vj20 LTE Positioning Protocol (LPP) Rel-19
TS 37.571 vj00 UE Conformance for Positioning Rel-19
TS 38.305 vj00 NG-RAN UE Positioning Stage 2 Rel-19
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
Patrick Zandl

About the author: Patrick Zandl (b. 1974)

Telecommunications specialist, technology journalist (founder of the Mobil server), and developer who has been running since 2025 — the largest Czech-language resource on AI-assisted programming. Formerly Chief Wizard Architect at Prusa3D and head of development for Turris at CZ.NIC; currently a consultant and instructor on AI implementation in companies.