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

Glossary term · Services

LRF

Location Retrieval Function

Services →

LRF is the IMS core network element that provides User Equipment location information to authorized entities, primarily for emergency services, by interacting with access network location functions and subscriber databases.

Introduced
Rel-7
Where
Services › IMS
Specifications
7 specs
Also in
Core Network
LRF Description Purpose What changed Neighbours Specifications

Description

The Location Retrieval Function (LRF) is a critical functional entity within the 3GPP IP Multimedia Subsystem (IMS) architecture, defined across multiple specifications including TS 23.167 (IMS emergency sessions) and TS 23.271 (Location Services). Architecturally, the LRF resides in the home IMS network or a visited network and interfaces with several other network nodes. Its primary role is to act as a location server and a gateway for retrieving and providing the geographic position of a User Equipment (UE) to authorized Application Functions (AFs), most notably the Emergency Call Session Control Function (E-CSCF) during an IMS Emergency Session.

The LRF operates through a series of standardized interfaces and procedures. When an emergency call is initiated via IMS, the E-CSCF queries the LRF for the caller's location. The LRF then orchestrates the retrieval of this location information. It may obtain the location directly from the UE if it supports location reporting, or more commonly, it interacts with the underlying access network's location infrastructure. For 3GPP access (like LTE or 5G NR), this involves communicating with the Gateway Mobile Location Centre (GMLC) via the Le interface. The LRF may also query the Home Subscriber Server (HSS) or Subscription Locator Function (SLF) to determine which GMLC serves the user.

Once the location is acquired (either as civic address or geodetic coordinates), the LRF formats it according to the required protocol (e.g., using the Presence Information Data Format - Location Object (PIDF-LO)) and delivers it to the requesting entity. Beyond emergency services, the LRF can also support other location-based services (LBS) as defined by the operator. Key components of the LRF include its service logic for handling location requests, its interfaces (Le towards GMLC, Ml towards E-CSCF, etc.), and its integration with IMS routing and subscription databases. Its function is indispensable for regulatory compliance with emergency caller location mandates (like E911 in the USA) in all-IP IMS networks.

Purpose & Motivation

The LRF was created to solve the problem of providing accurate caller location in IP-based telephony networks, specifically IMS, which lacked the inherent location capabilities of traditional circuit-switched mobile networks. In legacy GSM/UMTS circuits-switched calls, the cell ID could be easily passed to the emergency services network. With the migration to all-IP core networks and the decoupling of service layers (IMS) from access networks, a new, standardized mechanism was needed to query and retrieve a UE's location regardless of its access technology (3GPP, non-3GPP like WiFi).

The driving motivation was regulatory: governments worldwide mandate that emergency services must receive the caller's location. The LRF provides a standardized, access-agnostic function within the IMS architecture to meet this requirement. It addresses the limitations of earlier, proprietary, or access-specific solutions by defining a uniform interface (Ml) from the IMS core to a dedicated location retrieval system. This allows emergency services to work seamlessly across heterogeneous access networks and different device capabilities, future-proofing the IMS emergency call framework as new radio technologies emerge.

What changed in its specifications

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

TS 23.167Rel-17 → Rel-18

Rel-18 adds signal level Enhanced Network Selection, covering emergency-session and eCall-over-IMS behaviour for UEs in limited service state, tied to the ims-EmergencySupport broadcast bit. The overview lists only this one feature, so no further items can be named from the provided material.

Full comparison in TS 23.167 →
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 →

Evolution Across Releases

An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.

Rel-7 Initial

Introduced in 3GPP Release 7 as part of the IMS-based emergency services architecture (TS 23.167). The initial definition established the LRF as a standalone functional entity with the Ml interface to the E-CSCF and the Le interface to the GMLC, providing a standardized mechanism for retrieving subscriber location for IMS emergency calls.

Defining Specifications

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

SpecificationTitleRelease
TS 23.167 vk10 IMS Emergency Services Rel-20 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.501 vk30 5G System Architecture Rel-20 read
TS 24.229 vk10 IMS SIP/SDP Call Control Protocol Rel-20 read
TR 29.949 vj00 VoLTE IMS Roaming Architecture & Procedures Rel-19 read
TS 32.240 vk10 3GPP Charging Architecture and Principles Rel-20 read