Description
The Location Triggering Function (LTF) is a core component within the 3GPP security architecture, specifically defined for 5G systems. It operates as a logical function that can be integrated within network entities like the Lawful Interception Function (LIF) or the Gateway Mobile Location Centre (GMLC). Its primary role is to generate and manage triggers for location requests based on pre-configured criteria or dynamic events. These triggers are essential for services that require the network to determine a user equipment's (UE) geographical position under specific circumstances, such as when a lawful interception warrant is activated or when an emergency call is initiated.
Architecturally, the LTF interfaces with other network functions to request and receive location information. In the context of lawful interception, it interacts with the Lawful Interception Administration Function (LIAF) to receive authorization and configuration for interception-related location triggers. For emergency services, it may interface with the GMLC and the Access and Mobility Management Function (AMF) to trigger location procedures for emergency calls. The LTF defines the conditions under which a location request should be initiated, such as call establishment, mobility events, or periodic intervals, ensuring that location retrieval is performed only when legally or operationally justified.
The function works by monitoring for specific triggering events as defined in 3GPP specifications. When a configured event occurs, the LTF formulates a location request message and sends it to the appropriate location determination system, such as the GMLC. This system then coordinates with the Radio Access Network (RAN) and UE to obtain the location estimate using methods like Observed Time Difference of Arrival (OTDOA) or Assisted GNSS. The obtained location data is then delivered to the requesting entity, such as a law enforcement agency or public safety answering point. The LTF's operation is governed by strict security and privacy protocols to prevent unauthorized access and ensure compliance with regulatory requirements.
Key components of the LTF include the trigger event definitions, the policy enforcement mechanisms for when to activate a location request, and the interfaces for communication with administrative and location retrieval functions. Its role is critical in decoupling the triggering logic from the actual location determination process, allowing for a modular and scalable security architecture. By standardizing this function, 3GPP ensures that location-based services for security and emergency purposes are implemented consistently across different network deployments and vendors, facilitating interoperability and regulatory compliance.
Purpose & Motivation
The Location Triggering Function was introduced to address the growing need for standardized, secure, and efficient mechanisms to trigger location requests in mobile networks, particularly for lawful interception and emergency services. Prior to its standardization, implementations for triggering location-based procedures were often vendor-specific or tied to specific network architectures, leading to interoperability challenges and inconsistent security controls. As 5G networks introduced new service-based architectures and enhanced privacy features, a dedicated function was required to manage the complex policies and events associated with location triggering in a secure manner.
The creation of the LTF was motivated by regulatory requirements worldwide that mandate telecommunications providers to assist law enforcement with lawful interception capabilities, which increasingly include location information. Additionally, the critical nature of emergency services, where accurate and timely location data can save lives, necessitated a robust and reliable triggering mechanism within the network core. The LTF provides a clear architectural point for implementing these legally required functions, ensuring that location requests are triggered only under authorized conditions and that the process adheres to strict data protection standards.
By defining the LTF in 3GPP Release 16 and beyond, the standards body aimed to future-proof location triggering for evolving network technologies and use cases. It addresses limitations of previous ad-hoc approaches by providing a unified framework that integrates with the 5G core network's service-based interfaces and security frameworks. This allows network operators to deploy compliant systems more efficiently and enables law enforcement and emergency services to rely on consistent, high-quality location information when it is most needed.
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (48 CRs across 5 releases). Complements the general historical overview above with the evidence-based evolution of this function.
In Release 15, the Location Triggering Function (LTF) was introduced with clarifications on the procedures for location information derivation and delivery, and corrections were made to the LI_T3 triggering mechanism. This function, as part of the broader Triggering Function (TF) framework, is responsible for managing the interception state and sending necessary interception rules to triggered Points of Interception (POIs) based on network events. The enhancements specifically involved the interfaces and procedures for handling location acquisition requests and delivering location information to the Law Enforcement Agency (LEA) via defined interfaces like LI_HILA.
In Release 16, the Location Triggering Function (LTF) enhancements included refined procedures for location update triggering and additional details for Location Update at the AMF, as indicated by the CR titles. Specifically, the release introduced enhanced AMF Location Update Reporting with Dual Connectivity support and expanded the triggering scenarios to include the inclusion of a Product XID. Furthermore, the update defined the LARF's role in handling location requests from the LAF within the 5GC, strengthening the interface between the Triggering Function and the points of interception for location acquisition.
- Update Serving System and support of Subscriber Record Change and Cancel Location (x)IRIs TS 33.128CR0147
- Enhanced AMF Location Update Reporting with Dual Connectivity TS 33.128CR0083
- Location update triggering TS 33.128CR0038
- Additional details on Location Update at AMF TS 33.128CR0121
- Inclusion of Product XID in triggering scenarios TS 33.128CR0053
In Release 17, the LTF (Location Triggering Function) saw enhancements including the introduction of separated location reporting and RCS Stage 3 triggering. The release also provided clarifications on procedures such as ID mapping for location delivery, the use of the payload direction field, and LALS triggering with the LMISF-IRI. Furthermore, it aligned location handling for N3GPP access and clarified the default behavior for the Location Type at the Mediation and Delivery Function (MDF).
- N9HRLI and S8HR LI – Part III (Phase 1 – BBIFF-U triggering) TS 33.128CR0241
- Separated Location Reporting TS 33.128CR0273
- RCS Stage 3 Triggering TS 33.128CR0275
- Clarification on ID Mapping Location Delivery TS 33.127CR0107
- Clarification of Location Translation Stage 2 TS 33.127CR0172
- Location: clarification on the payload direction field TS 33.128CR0186
+ 3 more changes
In Release 18, the LTF (Location Triggering Function) enhancements included explicit support for location acquisition requests via both the T2P (Target to POI) and P2T (POI to Target) models, aligning with TS 33.128. The release also introduced clarifications and corrections for provisioning, particularly for Location Only Reporting in EPS, and added a new location type for reporting IMS location information. Furthermore, it detailed the Location Acquisition Function's (LAF) role in processing requests via the LI_HILA interface and the Location Acquisition Requesting Function's (LARF) handling within both EPC and 5GC architectures.
- Location acquisition architectures TS 33.127CR0176
- Support of location information request for both T2P and P2T requests in alignment with TS 33.128 TS 33.127CR0180
- Location acquisition interfaces for the EPC TS 33.127CR0206
- Intermediate Location LALS TS 33.127CR0210
- Location Reporting for Identity Association Record TS 33.128CR0376
- Location acquisition interfaces TS 33.128CR0396
+ 19 more changes
In Release 19, the LTF (Location Triggering Function) enhancements introduced location acquisition based on measurement reporting and the addition of coarse location to the location structure. The release also added Cell Radio Information to location structures and provided clarifications on location in RAN Information. Furthermore, it included corrections and consolidation for triggering details related to Lawful Interception functions in the UPF.
- Location acquisition based on measurement reporting TS 33.127CR0241
- Location acquisition based on measurement reporting TS 33.128CR0664
- Addition of Cell Radio Information to location structures TS 33.128CR0701
- Addition of coarse location to location structure TS 33.128CR0746
- Corrections to XID allocation and triggering criteria for LI for Home Routed Roaming TS 33.128CR0776
- Clarification on location in RAN Information TS 33.128CR0700
+ 1 more changes
Explore further
Broader topics and technologies where LTF plays a role.
Defining Specifications
3GPP specifications that define or reference LTF, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 33.127 vj50 | Lawful Interception Architecture and Functions | Rel-19 |
| TS 33.128 vj50 | 3GPP TS 33.128: Lawful Interception Protocols | Rel-19 |