MO-LR

Mobile Originated Location Request

Services
Introduced in R99
MO-LR is a location service (LCS) feature that allows a mobile device to request its own geographical position or the position of another target device from the network. It enables user-initiated location applications like navigation, friend-finder services, and location-based information requests.

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.

Key Features

  • UE-Initiated Request: The mobile device originates the location request procedure via standardized LCS control plane signaling.
  • Support for Self and Third-Party Location: Can request the location of the requesting UE itself or, with authorization, the location of another target UE.
  • Multiple Positioning Methods: Can utilize network-assisted GNSS (A-GNSS), Observed Time Difference of Arrival (OTDOA), Enhanced Cell ID (E-CID), and other standardized methods.
  • Privacy Authorization: Includes mandatory privacy verification for requests targeting another subscriber, involving the Home Subscriber Server (HSS) or Privacy Profile Register.
  • QoS Parameters: Allows the requesting UE to specify Quality of Service parameters like desired accuracy and response time for the location estimate.
  • Interworking with Core Network: Works across GSM, UMTS, LTE, and 5G core networks via the serving MSC, SGSN, MME, or AMF interfacing with the relevant positioning server.

Evolution Across Releases

R99 Initial

Introduced the basic MO-LR procedure in the GSM/UMTS LCS architecture. Defined the control plane signaling between the UE (LCS Client) and the network, using the MSC/SGSN and the Serving Mobile Location Centre (SMLC). Established fundamental capabilities for self-location requests and basic privacy mechanisms.

Defining Specifications

SpecificationTitle
TS 03.071 3GPP TR 03.071
TS 21.905 3GPP TS 21.905
TS 23.171 3GPP TS 23.171
TS 23.271 3GPP TS 23.271
TS 23.273 3GPP TS 23.273
TS 23.700 3GPP TS 23.700
TS 23.730 3GPP TS 23.730
TS 24.171 3GPP TS 24.171
TS 24.514 3GPP TS 24.514
TS 24.571 3GPP TS 24.571
TS 29.171 3GPP TS 29.171
TS 29.515 3GPP TS 29.515
TS 29.522 3GPP TS 29.522
TS 32.250 3GPP TR 32.250
TS 32.251 3GPP TR 32.251
TS 32.271 3GPP TR 32.271
TS 32.272 3GPP TR 32.272
TS 32.293 3GPP TR 32.293
TS 36.305 3GPP TR 36.305
TS 36.355 3GPP TR 36.355
TS 37.355 3GPP TR 37.355
TS 37.571 3GPP TR 37.571
TS 38.305 3GPP TR 38.305
TS 38.856 3GPP TR 38.856
TS 38.857 3GPP TR 38.857