ULI

User Location Information

Services →
Introduced in Rel-8 Also in: Services

ULI is a set of data parameters that identify the geographic or network-based location of a User Equipment for services like emergency calls, lawful interception, and network optimization.

Category
Services
Introduced
Rel-8
Where
Core Network › Evolved Packet Core
Also touches
1 segments
Specifications
6 specs
ULI Description Purpose Related Classification Detected Changes Specifications

Description

User Location Information (ULI) is a comprehensive term within 3GPP standards encompassing various data elements that pinpoint the position of a mobile device (User Equipment or UE) within the cellular network. It is not a single coordinate but a collection of parameters that can describe location at different levels of granularity, from a large geographic area like a country to a precise set of GPS coordinates. ULI is generated, stored, and processed by multiple network functions across both the Core Network (CN) and the Radio Access Network (RAN). Key sources include the Mobility Management Entity (MME) in 4G, the Access and Mobility Management Function (AMF) in 5G, the serving base station (eNB/gNB), and the UE itself if it has GNSS capabilities. The specific ULI parameters are defined in contexts such as the Evolved Packet System (EPS) Location Information (ELI) in 4G or the 5G Location Information in 5GC.

The composition of ULI can include several distinct elements. At the network level, it typically contains the Cell Global Identity (CGI), which uniquely identifies the serving cell, and the Tracking Area Identity (TAI) or Routing Area Identity (RAI), which indicate a larger group of cells for paging purposes. For more granular, geometric location, ULI may include the Geographic Location (GeoLoc) parameters, such as latitude, longitude, altitude, and uncertainty estimates. This geometric data can be derived from network-based methods like Observed Time Difference of Arrival (OTDOA) in LTE or Downlink Time Difference of Arrival (DL-TDOA) in 5G NR, or from UE-based methods like Assisted-GNSS (A-GNSS). The ULI is carried within protocol messages on various interfaces, such as the S1-MME, N2, and N4 interfaces, and is a key information element in the Packet Data Unit (PDU) session context and mobility management signaling.

ULI plays a critical operational role throughout the network. For emergency services, the network is legally obligated to provide accurate ULI to the Public Safety Answering Point (PSAP) when an emergency call is initiated. This process involves the Gateway Mobile Location Centre (GMLC) querying the network for the UE's location. For lawful interception, ULI is a crucial component of the Intercept Related Information (IRI) provided to law enforcement agencies. From a network management perspective, ULI enables location-based policy control and charging (e.g., differentiated tariffs for home vs. roaming zones), fraud detection by identifying improbable location changes, and analytics for network planning and optimization. The evolution from 4G to 5G has seen ULI become more precise and accessible, with 5G core network services like the Location Management Function (LMF) and Network Exposure Function (NEF) providing standardized APIs for authorized third-party applications to request location information, subject to user consent and privacy regulations.

Purpose & Motivation

ULI exists to fulfill a diverse set of regulatory, commercial, and operational requirements that are intrinsic to mobile telecommunications. The most critical driver is regulatory compliance for emergency services. Following mandates like E911 in the US and eCall in the EU, mobile networks must be capable of providing accurate caller location to emergency responders to save lives. ULI provides the standardized mechanism to meet this legal obligation. Commercially, ULI enables a vast ecosystem of Location-Based Services (LBS), such as navigation, local search, targeted advertising, and fleet tracking, creating significant revenue streams for operators and application providers.

From a network operations perspective, prior to sophisticated location tracking, networks had limited visibility into user distribution beyond cell-level attachment. This made tasks like capacity planning, hotspot identification, and roaming management challenging. ULI solves this by providing data for advanced analytics. It is also essential for security functions; sudden, impossible jumps in location (e.g., from New York to London in minutes) can indicate SIM box fraud or account takeover attempts. The creation and standardization of ULI across 3GPP releases was motivated by the need for a unified, interoperable framework. Early cellular systems had proprietary or limited location capabilities. Starting in Release 8 with EPS, 3GPP systematically defined the architecture (involving nodes like GMLC, MME) and protocols for location services, ensuring that a UE's location could be determined and reported consistently, whether the UE was stationary or moving at high speed, and across different vendor equipment.

The evolution of ULI also addresses the limitations of earlier, less precise methods. While Cell-ID provides a coarse location, the integration of A-GNSS and advanced network-based positioning methods like OTDOA into the ULI framework solved the problem of indoor or urban canyon environments where GPS signals are weak. The ongoing enhancements in 5G, with support for sensor-aided positioning and higher accuracy requirements for industrial IoT, demonstrate that ULI is a continuously evolving capability central to enabling new vertical applications and meeting increasingly stringent performance benchmarks.

Classification

Part ofLMF
Related approachesGMLCNEF

Detected Changes Across Releases

from 3GPP Change Requests

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

Studied in Rel-8, normative work from Rel-15.

Rel-15 13 changes

In Release 15, the User Location Information (ULI) function was enhanced to include the PSCell (Primary SCell) information for reporting to the Core Network. This release also introduced corrections and clarifications for ULI, such as its presence in the HANDOVER NOTIFY message and procedures for location reporting with a minimum interval. Furthermore, support was added for reporting WLAN location during a UE-initiated IPsec tunnel update procedure.

  • Procedure description on optional IEs in CU to DU RRC information IE. TS 38.401CR0068
  • Correction of User Location Information IE presence in HANDOVER NOTIFY TS 38.413CR0015
  • Transfer of the PSCell information to Core Network TS 38.413CR0027
  • Clarification on the usage of TNL information TS 38.413CR0037
  • Location Report Request Type TS 38.413CR0096
  • Correction of CN Assistance Information TS 38.413CR0111

+ 7 more changes

Rel-16 14 changes

In Release 16, the ULI function was enhanced with several specific new capabilities and corrections. Key additions included the reporting of Presence Reporting Area information during S1 handover, the propagation of user consent details in Xn inter-PLMN handover, and the inclusion of V2X and DAPS Handover information within the UE Context. The release also addressed various failure cases and enabled multiple location reporting requests and reports.

  • Correction the text of stage 2 for DL Xn-U address information transfer (CR to TS 38.401, R16) TS 38.401CR0188
  • Addition of the PSCell information in the path update procedure TS 38.413CR0314
  • Including the Redundant UL NG-U UP TNL Information in the Modify Request TS 38.413CR0520
  • Correction on RAT Information Handling TS 38.413CR0537
  • Correction on the use of the Core Network Assistance Information for RRC INACTIVE IE TS 38.413CR0610
  • Correcting Presence of the Cell CAG Information IE in ASN.1 TS 38.413CR0631

+ 8 more changes

Rel-17 8 changes

In Release 17, the User Location Information (ULI) function was enhanced with new capabilities for specific deployment scenarios. The release introduced the addition of serving PLMN information in ULI for Non-Terrestrial Networks (NTN) and enabled additional ULI provision with PScell information. Furthermore, corrections were made to the reporting of ULI for non-3GPP access.

  • Remove the editor's notes related to consent information TS 38.401CR0214
  • Providing MBS QoS Flow Information during Multicast Session Establishment TS 38.401CR0275
  • Adding serving PLMN information in ULI for NTN TS 38.413CR0776
  • Correction of Paging eDRX Information TS 38.413CR0866
  • Additional ULI provision with PScell information TS 38.413CR0901
  • Correction of ULI for non-3GPP access TS 38.413CR0947

+ 2 more changes

Rel-18 11 changes

In Release 18, enhancements to User Location Information included corrections and clarifications for specific access types and reporting procedures. This involved corrections for wireline access and N3IWF user location, as well as clarifications for UE History Information usage and UE radio capability for paging. Furthermore, the release introduced support for reporting ECN Marking or Congestion Information Reporting Status during Xn-based and NG-based handovers.

  • Introduction of Aerial authorization information and A2X services support TS 38.413CR0618
  • Correction on Location Reporting Control [LRC-Enh] TS 38.413CR0877
  • Location Reporting Enhancements [LRC-Enh] TS 38.413CR0911
  • Correction of user location information for wireline access TS 38.413CR1041
  • Stage 2 correction for reporting of requested DL LBT information TS 38.401CR0417
  • Correction of MBS Assistance Information Support TS 38.413CR1084

+ 5 more changes

Rel-19 5 changes

In Release 19, the ULI function was enhanced to support the reporting of Aerial UE Flight Information to the Core Network, including a specific procedure for reporting failures of this information in a FAILURE INDICATION message. The release also introduced support for Time Reference Information Distribution Indication and included corrections and procedural specifications for the related Aerial UE Flight Information Reporting Control and Core Network Assistance Information for RRC INACTIVE information elements.

  • Support of Time Reference Information Distribution Indication TS 29.274CR2113
  • Support Aerial UE Flight Information Reporting to CN TS 38.413CR1259
  • Support Aerial UE Flight Information Failure Reporting in FAILURE INDICATION message TS 38.413CR1296
  • Specifying procedure texts for the Core Network Assistance Information for RRC INACTIVE IE TS 38.413CR1288
  • Correction on Aerial UE Flight Information Reporting Control IE TS 38.413CR1430

Explore further

Broader topics and technologies where ULI plays a role.

Defining Specifications

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

SpecificationTitleRelease
TS 23.041 vj30 Cell Broadcast Service and Public Warning System Rel-19
TS 23.700 vk00 XR Services Application Enablement Layer Rel-20
TS 23.843 vc00 Signalling Overload Scenarios & Solutions Rel-12
TS 29.274 vj50 GTPv2-C Control Plane Protocol Specification Rel-19
TS 38.401 vj10 NG-RAN Architecture Specification Rel-19
TS 38.413 vj10 NG Application Protocol (NGAP) Rel-19