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.
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 →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
- R98 BSSAP-LE, BSSLAP, GMLC, LMU, RRLP, SMLC
- Rel-5 PCAP, SAS
- Rel-6 PPR, R-GMLC
- Rel-7 LRF, SUPL
- Rel-9 E-SMLC, LCS-AP, LPP, LPPa
- Rel-15 LMF, NRPPa
- 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 sourcesDocumented changes in 10 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.
The LRF is specified for the first time: it retrieves UE location for the E-CSCF, may invoke an RDF to obtain PSAP routing information, and serves the PSAP via correlation information such as an ESQK.
- “Location Retrieval Function (LRF): This functional entity handles the retrieval of location information for the UE including, where required, interim location information” TS 23.167 v7.13.0
- “The E-CSCF can request location information and routeing information from the LRF.” TS 24.229 v7.34.0
- “The LRF sends the location information and/or the routing information to the IMS core.” TS 23.167 v7.13.0
The LRF description was generalised from interacting with a GMLC to a generic Location Server, and the LRF/RDF/LS configuration text was reworded accordingly, removing GMLC-specific references.
- “The LRF may interact with a separate Location Server or contain an integrated Location Server in order to obtain location information.” TS 23.167 v8.6.0
- “The LRF may interact with a separate GMLC or contain an integrated GMLC in order to obtain location information.” TS 23.167 v8.6.0
In TS 24.229 the LRF gains specified SIP behaviour: it acts as a redirect server returning 300 responses with PSAP addresses and subscribes to E-CSCF dialog state, and TS 23.271 defines the LRF's role and Ml interface.
Compared with Rel-7: intermediate versions are not available, so this change may date from any release since Rel-7.
- “The LRF shall respond to all received initial requests for a dialog, and to all standalone requests, as a redirect server” TS 24.229 v9.31.0
- “the LRF shall set the Contact header field of the response to a list (one or more) address(es) of PSAP(s)” TS 24.229 v9.31.0
- “the LRF shall generate a SUBSCRIBE request to the dialog state event package” TS 24.229 v9.31.0
LRF-related procedures were revised: the E-CSCF may send the P-Asserted-ID or UE identification to the LRF subject to local regulation, and the LRF's reference identifier and location handling text was updated.
- “Subject to local regulation, the E‑CSCF may send the contents of the P-asserted ID or UE identification to the LRF.” TS 23.167 v10.11.0
- “Sending of location information from LRF to E-CSCF” TS 24.229 v10.29.0
- “if operator policy determines that an LRF is to be used, forward the request to the LRF” TS 24.229 v10.29.0
LRF behaviour in IMS emergency calls was extended: it may provide location by value in 3XX Contact header fields per operator policy, with E-CSCF handling that location, and the LRF can obtain location from the GMLC.
- “if required by operator local policies, the LRF shall include geographical information, encoded as header fields of the URI in a Contact header field of the 300 (Multiple Choices) response” TS 24.229 v11.31.0
- “if operator policy allows any LRF to provide a location by value using the mechanism defined in subclause 5.11.3. the E-CSCF shall provide the UA role.” TS 24.229 v11.31.0
- “If the operator policy requires network provided location using the LRF-based solution for the UE location (e.g. serving cell), the P-CSCF forwards the emergency request to E-CSCF.” TS 23.167 v11.11.0
LRF behaviour in TS 24.229 changed: the LRF now also returns the "icid-value" parameter in P-Charging-Vector, and the SUBSCRIBE handling from the LRF was corrected.
- “the LRF shall insert a P-Charging-Vector header field containing the "orig-ioi" header field parameter, if received in the request, a type 3 "term-ioi" header field parameter and the "icid-value" header field parameter.” TS 24.229 v12.27.0
- “Correcting E-CSCF P-Charging-Vector handling for SUBSCRIBE from LRF” TS 24.229 v12.27.0
- “perform step 11 of subclause 5.11.2 before sending the INVITE request to the LRF.” TS 24.229 v12.27.0
LRF gained new behaviour in Rel-14: it can query HSS over Sh for NPLI for WLAN access, retrieve UPLI from the UE via the IMS core, and subscribe to UE location in SIP presence.
- “If configured to provide an NPLI for WLAN access, and if the UE is not roaming, the LRF queries HSS for every access” TS 23.167 v14.6.0
- “the LRF shall generate a SUBSCRIBE request to the presence event package in accordance with RFC 6665 [28] and RFC 3856 [74]” TS 24.229 v14.21.0
- Support for Sh in LRF for NPLI and Support for UE updated Location mid-emergency session over emergency signalling channel TS 23.167CR0289
TS 23.273 first specifies the LRF in the 5G location services architecture: its role for IMS emergency sessions, collocation with a GMLC, and emergency location request procedures with the AMF.
- “The Location Retrieval Function (LRF) may be collocated with a GMLC or separate and is responsible for retrieving or validating location information” TS 23.273 v16.13.0
- “4.3.4 Location Retrieval Function, LRF” TS 23.273 v16.13.0
- “The external emergency services client (e.g. a PSAP) sends a request to the LRF for a location for the target UE” TS 23.273 v16.13.0
AMF's location response may now include the timestamp of the location estimate, and the AMF stores the UE Positioning Capability in UE context when received from LMF.
- “may include information about the positioning method and the timestamp of the location estimate. The AMF stores the UE Positioning Capability in UE context when received from LMF.” TS 23.273 v17.11.0
New LRF step 2B: for 3GPP-NR-ProSe-L3UNR access type, if the location retrieved via the U2N-relay-ID does not match the user-provided location, the LRF does not use the user-provided location for PSAP selection.
- “the retrieved location does not match the user-provided location from the P-Access-Network-Info header field not containing the "network-provided" parameter” TS 24.229 v18.11.0
Defining Specifications
3GPP specifications that define or reference LRF, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| 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 |