LDR

Location Deferred Request

Services →
Introduced in R99 Also in: Core Network

LDR is a Location Services capability that allows a client to request the location of a target device to be determined and delivered at a specified later time.

Category
Services
Introduced
R99
Where
Services › Codecs
Also touches
1 segments
Specifications
12 specs
LDR Description Purpose Related Classification Detected Changes Specifications

Description

Location Deferred Request (LDR) is a feature of the 3GPP Location Services (LCS) system. It operates within the standardized LCS architecture, which involves a LCS Client, a LCS Server (typically the Gateway Mobile Location Centre - GMLC), and the core network nodes (e.g., MSC, SGSN, MME) interacting with the radio access network and the UE. The LDR mechanism allows an authorized LCS Client to submit a location request with a deferred reporting condition. Instead of triggering an immediate location procedure, the network stores the request and activates it when the specified condition is met. The key components involved include the deferred location request parameters stored in the network (e.g., in the GMLC or a dedicated service node), timers, and event triggers. The request specifies criteria such as a single future absolute time, a periodic interval (e.g., every hour), or a change in area event (e.g., when the UE enters or leaves a defined geographical area). When the triggering condition occurs, the network executes the standard location determination procedure, which could be network-based (e.g., using timing advance or observed time difference of arrival), UE-based (using GNSS like GPS), or assisted/hybrid methods. Once the location is obtained, the network delivers the result (e.g., geographic coordinates) to the requesting LCS Client according to the deferred request's delivery instructions. This process decouples the request from the immediate network and UE resource usage for positioning, allowing for more efficient scheduling and battery-friendly operation for the UE, especially for non-urgent tracking applications. The feature relies on the network's ability to manage and correlate multiple deferred requests, handle their lifecycle (creation, activation, execution, cancellation), and ensure privacy and security as per subscriber consent.

Purpose & Motivation

Location Deferred Request was created to expand the utility of cellular location services beyond simple, immediate "where are you now" queries. Early LCS capabilities were primarily real-time, which limited applications to instant navigation, emergency services (E911), and similar time-critical uses. Many commercial and enterprise applications, however, require location information on a scheduled or event-driven basis without constant active polling. Examples include fleet management for periodic position logging, asset tracking for theft recovery (reporting location only upon movement), location-based advertising triggered by entering a shopping mall, or parental controls that alert when a child leaves a safe zone. Performing these with continuous real-time requests would be highly inefficient, consuming excessive network signaling resources, core network processing capacity, and UE battery life. LDR solves this by allowing a single request to define a future action plan. This reduces signaling overhead, optimizes network resource utilization, and is more considerate of UE power constraints. It enabled a new class of location-based services that are proactive, scheduled, or event-triggered, forming a foundational capability for the Internet of Things (IoT) and Machine-to-Machine (M2M) tracking use cases that emerged later. Its introduction in the R99 timeframe positioned GSM and UMTS networks to offer sophisticated value-added services.

Classification

Part ofLCS
Related approachesSUPL

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-19 1 change

In Release 19, the primary update for the Location Deferred Request (LDR) function was a correction to its technical reference documentation. This refinement ensures clarity and consistency in how the LDR-specific attributes, such as the applicable event triggers and state parameters, are defined and implemented within the location service request framework.

  • Correction on LDR Reference TS 29.572CR0392

Explore further

Broader topics and technologies where LDR plays a role.

Defining Specifications

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

SpecificationTitleRelease
TS 03.071 v7b0 Location Services (LCS) Stage 2 Description Rel-7
TS 23.171 v1300 LCS Stage 2 Specification for UMTS Rel-4
TS 23.271 vj00 LCS Stage 2 Specification Rel-19
TS 23.273 vj50 5G Location Services Stage 2 Architecture Rel-19
TS 23.700 vk00 XR Services Application Enablement Layer Rel-20
TS 23.731 vg00 5G LCS Architecture Enhancement Study Rel-16
TS 24.080 vj20 Mobile radio interface layer 3 supplementary services Rel-19
TS 24.571 vj20 Control Plane LCS Procedures Rel-19
TR 26.926 vj00 Traffic Models & Quality Evaluation for Media/XR in 5G Rel-19
TS 29.515 vj50 Ngmlc Service Based Interface Protocol Rel-19
TS 29.518 vj50 AMF Service Based Interface Protocol Rel-19
TS 29.572 vj50 Nlmf Service Based Interface Stage 3 Rel-19
Patrick Zandl

About the author: Patrick Zandl (b. 1974)

Telecommunications specialist, technology journalist (founder of the Mobil server), and developer who has been running since 2025 — the largest Czech-language resource on AI-assisted programming. Formerly Chief Wizard Architect at Prusa3D and head of development for Turris at CZ.NIC; currently a consultant and instructor on AI implementation in companies.