Description
Observed Time Difference of Arrival (OTDOA) is a downlink positioning method standardized by 3GPP. It operates by having the User Equipment (UE) measure the Reference Signal Time Difference (RSTD) between signals received from multiple neighboring evolved NodeBs (eNBs) or gNBs and a reference cell, typically the serving cell. These RSTD measurements are reported to the network, specifically to a Location Server (e.g., Evolved Serving Mobile Location Centre - E-SMLC in LTE, Location Management Function - LMF in 5GC). The location server, which knows the precise geographic coordinates and timing of the involved base stations, uses multilateration algorithms (like hyperbolic positioning) to compute the UE's position based on the time differences. The accuracy depends on factors like the number of measurable cells, their geometric distribution, and signal quality.
In the architecture, the UE is the measuring device, while the location server is the calculating entity. The interface between the UE and the location server for positioning protocol messaging is the LTE Positioning Protocol (LPP) in LTE and NR, carried over the user plane or control plane. For the network to support OTDOA, base stations must transmit Positioning Reference Signals (PRS) – specially designed sequences with low interference and high periodicity to improve measurement accuracy and hearability of distant cells. The network must also provide assistance data to the UE, including PRS configuration of neighbor cells, via the LPP protocol to guide the UE's measurements.
OTDOA's role is integral to the 3GPP positioning framework, complementing other methods like Assisted GNSS (A-GNSS) and Enhanced Cell ID (E-CID). It is a primary solution for indoor positioning or scenarios where GNSS signals are unavailable. The method is network-controlled but UE-assisted, balancing processing load. Continuous enhancements across releases have focused on improving accuracy, reducing latency, and supporting new deployment scenarios like indoor, IoT, and vehicle-to-everything (V2X) positioning, making it a cornerstone for commercial and regulatory location-based services.
Purpose & Motivation
OTDOA was created to fulfill regulatory requirements for emergency caller location (e.g., E911 in the USA, E112 in Europe) and to enable commercial location-based services (LBS) within cellular networks. Prior to its standardization, network-based positioning options were limited to less accurate methods like Cell ID (showing the serving cell area) or timing advance, which provided poor granularity. The need for more precise, reliable, and ubiquitous positioning, especially for users without GNSS-capable devices or in GNSS-denied environments like deep indoors, drove the development of OTDOA.
The technology solves the problem of determining a mobile device's geographical location using the existing cellular radio infrastructure itself. It addresses the limitations of satellite-based methods, which fail indoors or in urban canyons, and of simpler network methods that lack precision. By leveraging the synchronized timing of the cellular network, OTDOA provides a standardized, interoperable method that operators can deploy to meet legal mandates for emergency services and to create new revenue streams through asset tracking, navigation, and proximity-based advertising.
Historically, its introduction in 3GPP Release 9 for LTE (with foundational work in earlier UMTS releases) marked a significant step in making cellular networks location-aware. The continuous evolution through subsequent releases reflects the growing demands for higher accuracy (down to meter-level), lower power consumption for IoT devices, and support for new use cases in 5G, such as industrial sensor networks and autonomous systems requiring precise positioning.
What changed in its specifications
The latest release-to-release comparison of specifications that define OTDOA. Each summary describes the whole specification, not only this term.
Rel-18 brings only minor changes to TS 21.905: 0 clauses changed, with no change attributed to a release feature.
Full comparison in TR 21.905 →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
Positioning methods · Radio Access Network › Multi-RAT
- R98 E-OTD
- R99 A-GPS, OTDOA-IPDL
- Rel-9 A-GNSS, E-CID, OTDOA
- Rel-16 DL-AoD, DL-TDOA, Multi-RTT, NR E-CID, UL-AoA, UL-TDOA
Also in this family (introduction release not pinned to a single defining specification): U-TDOA
- OTDOA counterpart in another generation: E-OTD
“For example, GPS is based on TOA, and E-OTD (on GSM) or OTDOA (on UMTS) are based on TDOA.” TS 25.305
- OTDOA counterpart in another generation: DL-TDOA
“In the DL-TDOA positioning method, the UE position is estimated based on DL RSTD (and optionally DL-PRS-RSRP and/or DL-PRS-RSRPP and/or DL-RSCPD) measurements taken at the UE of downlink radio signals from multiple NR TRPs, along with knowledge of the geographical coordinates of the TRPs and their relative downlink timing.” TS 38.305
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 6 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.
TS 36.133 first specifies E-UTRAN intra- and inter-frequency OTDOA RSTD measurement requirements, with the UE required to measure at least 16 cells including the reference cell.
- “the UE shall be able to detect and measure intra-frequency RSTD, specified in 3GPP TS 36.214 [4], for at least n=16 cells” TS 36.133 v9.23.0
- “the UE shall be able to detect and measure inter-frequency RSTD, specified in 3GPP TS 36.214 [4], for at least n=16 cells” TS 36.133 v9.23.0
OTDOA is extended to combine with new positioning methods (Barometric, WLAN, Bluetooth, TBS, AddPos), with new Selected Position Method values such as 'OTDOA or GPS and AddPos' in PCAP and Iupc procedures.
- “ENUMERATED(OTDOA, GPS, OTDOA or GPS, Cell ID, UTDOA, …, GNSS, OTDOA or GNSS,GPS and AddPos, OTDOA or GPS and AddPos)” TS 25.453 v13.1.0
- “can only be configured using RRC signaling together with OTDOA or GPS positioning methods.” TS 25.305 v13.0.0
- “using A-GPS or A-GANSS or OTDOA or Additional Positioning (periodic or non-periodic)” TS 25.453 v13.1.0
TS 36.133 gained new OTDOA RSTD measurement requirements for NB1 UEs, covering intra-frequency and inter-frequency measurements in normal and enhanced coverage while in RRC_IDLE.
- “the UE shall be able to detect and measure intra-frequency RSTD, specified in TS 36.214 [4], for at least n = 16 cells” TS 36.133 v14.24.0
- “4.8.2 OTDOA Intra-Frequency RSTD Measurements for UE category NB1 for enhanced coverage” TS 36.133 v14.24.0
- “4.8.3 OTDOA Inter-Frequency RSTD Measurements for UE category NB1 for normal coverage” TS 36.133 v14.24.0
OTDOA assistance data and support were extended in Rel-15: TDD UL/DL configuration added to OTDOA assistance data, IMU support introduced for OTDOA, and NB-IoT OTDOA enhanced.
OTDOA assistance data support was added for the case of an NR serving cell, and the OTDOA positioning method list was reworded to specify LTE-signal-based OTDOA alongside new NR methods.
- Support OTDOA assistance data for case of NR serving cell TS 38.305CR0062
- “This version of the specification defines OTDOA (based on LTE signals), A-GNSS, E-CID (based on LTE signals)” TS 37.355 v16.14.0
TS 36.133 added OTDOA RSTD measurement requirements for UEs in RRC_IDLE state, detecting and measuring intra- and inter-frequency RSTD for at least 16 cells with reporting delay rules.
- “the UE shall be able to detect and measure intra-frequency RSTD, specified in TS 36.214 [4], for at least n = 16 cells” TS 36.133 v17.16.0
- “the UE shall be able to detect and measure inter-frequency RSTD, specified in TS 36.214 [4], for at least n = 16 cells” TS 36.133 v17.16.0
Defining Specifications
3GPP specifications that define or reference OTDOA, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TR 21.905 vj20 | 3GPP Terminology and Definitions | Rel-19 read |
| TS 23.171 v390 | LCS Stage 2 for UMTS | R99 read |
| TS 23.271 vj00 | LCS Stage 2 Specification | Rel-19 read |
| TR 23.730 ve00 | Study on extended CIoT architecture | Rel-14 read |
| TS 25.305 vj00 | UTRAN UE Positioning Stage 2 | Rel-19 read |
| TS 25.453 vj00 | PCAP Protocol Specification | Rel-19 read |
| TS 29.171 vj10 | LCS-AP between MME and E-SMLC (SLs) | Rel-19 read |
| TS 33.814 vg01 | Security aspects of enhanced Location Services (eLCS) | Rel-16 read |
| TS 36.133 vj60 | LTE Radio Resource Management Requirements | Rel-19 read |
| TS 36.300 vj20 | E-UTRAN Radio Interface Protocol Architecture | Rel-19 read |
| TS 36.305 vj00 | UE Positioning in E-UTRAN Stage 2 | Rel-19 read |
| TS 36.355 vj00 | LTE Positioning Protocol (LPP) | Rel-19 read |
| TS 36.401 vj00 | E-UTRAN Overall Architecture Description | Rel-19 read |
| TS 36.413 vj20 | S1 Application Protocol (S1AP) for E-UTRAN | Rel-19 read |
| TS 36.455 vj00 | LTE Positioning Protocol Annex (LPPa) | Rel-19 read |
| TS 36.809 vc00 | Study on RF Pattern Matching for LTE Positioning | Rel-12 read |
| TS 36.855 vd00 | LTE Positioning Enhancements Study | Rel-13 read |
| TS 37.355 vj30 | LTE Positioning Protocol (LPP) | Rel-19 read |
| TS 37.571 vj00 | UE Conformance for Positioning | Rel-19 read |
| TS 37.857 vd10 | Indoor Positioning Enhancements for UTRA and LTE | Rel-13 read |
| TS 38.133 vk10 | NR Radio Resource Management Requirements | Rel-20 read |
| TS 38.305 vj30 | NG-RAN UE Positioning Stage 2 | Rel-19 read |
| TS 38.413 vj40 | NG Application Protocol (NGAP) Specification | Rel-19 read |
| TS 38.455 vj30 | NR Positioning Protocol A | Rel-19 read |
| TR 43.901 vj00 | Generic Access to A/Gb Interface Feasibility Study | Rel-19 read |