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

Glossary term · Services

LIR

Location Information Request

Services →

LIR is a request message used by an application or network node to query the network for the geographic or civic location of a mobile device, triggering various positioning methods.

Introduced
R99
Where
Core Network › 5G Core
Specifications
11 specs
Also in
Services, Security
LIR Description Purpose What changed Neighbours Detected Changes Specifications

Description

A Location Information Request (LIR) is a core procedural element within 3GPP architectures for obtaining the position of a mobile device. It is not a single protocol message but a conceptual service request that is realized through specific protocols and interfaces, such as the LTE Positioning Protocol (LPP) over the SLs interface, or the OMA SUPL protocol, or via core network interfaces like the Gateway Mobile Location Centre (GMLC) using the Le or SLg interfaces. An LIR is initiated by a Location Service (LCS) Client, which could be an external application (e.g., a mapping service), an internal network service (e.g., for lawful interception), or the UE itself. The request contains parameters such as the target UE's identifier (MSISDN, IMSI), the required Quality of Service (QoS) for the location (e.g., accuracy, response time), and the type of location information needed (e.g., geographic coordinates, civic address).

Upon receiving an LIR, the network's location system engages the appropriate positioning methods. For network-based positioning, the network may use measurements from base stations (e.g., Observed Time Difference of Arrival - OTDOA in LTE, Downlink Time Difference of Arrival - DL-TDOA in 5G). For UE-based positioning, the network provides assistance data (e.g., satellite ephemeris for A-GNSS) to the UE, which then computes its own fix and may report it back. Hybrid methods combine both. The control and coordination of this process are managed by network entities like the Evolved Serving Mobile Location Centre (E-SMLC) in LTE or the Location Management Function (LMF) in 5G. These entities select the positioning method based on the LIR's QoS, UE capabilities, and available network measurements.

The result of processing an LIR is a Location Information Response, which delivers the estimated location data to the requesting client. The entire procedure involves multiple network domains: the core network for client authorization and request routing, the radio access network for measurement collection, and potentially the UE. Privacy is a critical aspect; the network must verify that the LCS Client is authorized to request the location of the specific target UE, based on subscriber privacy settings and regulatory rules. The LIR mechanism is thus the triggering event for a complex, standardized sequence that transforms radio signals or satellite data into a usable geographic location for services.

Purpose & Motivation

The concept of the Location Information Request emerged to standardize how applications and services could programmatically obtain a mobile subscriber's location. Before its standardization, location services were proprietary and fragmented, hindering the development of widespread location-based applications. The primary problem it solves is providing a unified, secure, and reliable interface for authorized entities to request UE location, which is essential for commercial services (friend-finder, location-based advertising), emergency services (E-911/112), and network optimization.

Historically, the need was driven by regulatory mandates for emergency caller location and the commercial potential of location-based services. The LIR framework, evolving since 3GPP Release 99, created a clear architectural separation between the entity requesting location (the LCS Client) and the network's positioning capabilities. This addressed the limitations of ad-hoc solutions by defining standardized protocols (e.g., LPP, SUPL), interfaces (e.g., Le, SLg), and privacy control mechanisms. It enabled a ecosystem where network operators could expose location capabilities to third-party application providers in a controlled manner, fueling innovation in mobile services while ensuring subscriber privacy and network security.

What changed in its specifications

The latest release-to-release comparison of specifications that define LIR. 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 →
TS 23.273Rel-18 → Rel-19

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 →

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

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

Rel-18 1 change
  • Support of location information request for both T2P and P2T requests in alignment with TS 33.128 TS 33.127CR0180

Defining Specifications

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

SpecificationTitleRelease
TS 03.071 v890 GSM Location Services Stage 2 R99 read
TS 23.171 v390 LCS Stage 2 for UMTS R99 read
TS 23.271 vj00 LCS Stage 2 Specification Rel-19 read
TS 23.273 vj70 5G Location Services Architecture Stage 2 Rel-19 read
TS 23.380 vk00 IMS Restoration Procedures Rel-20 read
TS 29.518 vk10 AMF Service Based Interface Rel-20 read
TS 29.572 vk10 5G LMF Service-Based Interface Rel-20 read
TR 29.949 vj00 VoLTE IMS Roaming Architecture & Procedures Rel-19 read
TS 32.808 v800 Common Profile Storage Framework for User Data Rel-8 read
TS 33.127 vj80 Lawful Interception Architecture Rel-19 read
TS 33.128 vj80 Lawful Interception Protocols and Procedures Rel-19 read