Menu
Latest
12 meetings · Prague, Jeju · 12–16 Oct
Reports
RAN1#126-bis · SA2#177

Glossary term · Protocol

MLP

Mobile Location Protocol

Protocol →

MLP is an application-level protocol standardized by the OMA and referenced by 3GPP for exchanging location information between a Location Server and a client to enable access to mobile device positioning.

Where
Services › IMS
Specifications
4 specs
MLP Description Purpose What changed Family Neighbours Detected Changes Specifications

Description

The Mobile Location Protocol (MLP) is an XML-based application-layer protocol used for requesting and delivering location information of a Mobile Station (MS). It operates between a Location Service (LCS) Client and a Location Server, such as a Gateway Mobile Location Center (GMLC) in a 3GPP network. MLP provides a standardized interface that abstracts the underlying network-specific positioning technologies (e.g., Cell-ID, OTDOA, A-GPS), allowing service applications to request location in a uniform manner. The protocol defines a set of service primitives for different location request types, including immediate location, triggered location reporting, and standard location reporting.

The core of MLP is its request-response model using XML documents over HTTP/HTTPS or other transport. A typical MLP exchange involves the LCS Client sending a standardized MLP Service Request (e.g., a Standard Location Immediate Request - SLIR) to the Location Server. This request contains parameters such as the target MSISDN or IMSI, the required quality of service (QoS) like accuracy and response time, and the type of location estimate (e.g., latitude/longitude). The Location Server authenticates and authorizes the request, interacts with the mobile network's positioning subsystems (like the Serving Mobile Location Center - SMLC) to obtain the location fix, and then formulates an MLP Service Answer (e.g., Standard Location Immediate Answer - SLIA) back to the client, containing the location estimate or an error code.

MLP supports multiple service types to cater to different application needs. The Immediate Service is for one-time location retrieval. The Triggered Service allows a client to set up a subscription for periodic or event-driven location reports (e.g., when a device enters a defined area). The Reporting Service is used by the network to push location information to a client, often following a triggered event. MLP also defines elements for privacy and security, ensuring that location requests comply with the user's privacy settings and that communication between client and server is secure. Within 3GPP, MLP is specified as a key external interface (Le interface) for the Gateway Mobile Location Center (GMLC), enabling lawful intercept, emergency services (E911/E112), and commercial location-based services (LBS) like navigation, friend-finder, and asset tracking.

Purpose & Motivation

MLP was developed to solve the problem of proprietary and fragmented interfaces for accessing mobile device location. In the early days of location-based services, network equipment vendors and service providers often used bespoke protocols, hindering interoperability and slowing the development of a broad ecosystem of LBS applications. The creation of a standardized, application-level protocol was motivated by the need to provide a single, consistent way for authorized external applications to request location information, regardless of the underlying network technology (GSM, UMTS, LTE) or the positioning method used.

Its adoption by 3GPP and standardization by the Open Mobile Alliance (OMA) provided the necessary common language between service providers and mobile operators. This enabled the scalable deployment of commercial LBS, emergency services (where standardized interfaces are critical for connecting PSAPs), and value-added services. MLP abstracts the complexities of the radio access network, allowing application developers to focus on service logic rather than network integration, thereby fostering innovation in the location services market.

What changed in its specifications

The latest release-to-release comparison of specifications that define MLP. Each summary describes the whole specification, not only this term.

TS 23.271Rel-18 → Rel-19

Rel-19 brings only minor changes to TS 23.271: 0 clauses changed, with no change attributed to a release feature.

Full comparison in TS 23.271 →

Technology family

Location services architecture · Services

  1. R98 BSSAP-LE, BSSLAP, GMLC, LMU, RRLP, SMLC
  2. Rel-5 PCAP, SAS
  3. Rel-6 PPR, R-GMLC
  4. Rel-7 LRF, SUPL
  5. Rel-9 E-SMLC, LCS-AP, LPP, LPPa
  6. Rel-15 LMF, NRPPa
  7. 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 sources

Documented changes in 5 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.

Rel-5 specification text

TS 23.271 introduces references to the LIF Mobile Location Protocol specification for the Le interface, adding MLP to the specification for the first time.

  • “Adding references to the LIF MLP specification for the Le interface” TS 23.271 v5.13.0
  • “LIF TS 101 "Mobile Location Protocol Specification" (Location Interoperability Forum)” TS 23.271 v5.13.0
Rel-6 specification text

TS 23.271 now states that the attributes for information exchange between LCS Client and LCS Server are standardized by OMA in MLP, replacing the earlier LIF MLP reference.

  • “The attributes for the information exchange between the LCS Client and the LCS Server have been standardized by OMA in MLP [31].” TS 23.271 v6.13.0
  • “Clarification of MLP and RLP usage in 23.271” TS 23.271 v6.13.0
Rel-14 specification text

TS 33.108 Rel-14 first specifies handover interface use of OMA MLP, mapping LALS extended location parameters from MLP pos elements and MLP response messages into ASN.1 Location objects.

  • “LALS extended location parameters are mapped from the MLP pos element parameters” TS 33.108 v14.6.0
  • “the MLP response message into an ASN.1 Location object.” TS 33.108 v14.6.0
  • “LALS location error codes are the OMA MLP result identifiers defined in [88], Clause 5.4” TS 33.108 v14.6.0
Rel-15 specification text

TS 33.127 in Rel-15 specifies LALS as based on OMA MLP, with the Le interface specified in the OMA MLP specification, and the MLP reference was corrected.

  • “LALS is based on the Location Services (LCS) capabilities defined in the TS 23.271 [5] and in the OMA MLP specification [6].” TS 33.127 v15.5.0
  • “NOTE: The Le interface is specified in the OMA MLP specification [6].” TS 33.127 v15.5.0
Rel-18 specification text

Lawful interception location requests to the LI-LCS Client may carry parameters, referencing OMA MLP definitions, enabling multiple intermediate location responses to a single LIR, including a flag and maximum response time.

  • “These parameters include the flag for acceptance of intermediate location estimates and the maximum response time for final location result (see OMA MLP [6]” TS 33.127 v18.15.0

Defining Specifications

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

SpecificationTitleRelease
TS 23.271 vj00 LCS Stage 2 Specification Rel-19 read
TR 23.730 ve00 Study on extended CIoT architecture Rel-14 read
TS 26.851 vb20 MBMS Multimedia Service Enhancements Rel-11 read
TS 29.199 3GPP TS 29.199 Rel-5 read