PRC

Pseudo-Range Correction

Services →
Introduced in Rel-8

PRC is a correction parameter used in OTDOA positioning to compensate for base station timing differences, improving a UE's location accuracy.

Category
Services
Introduced
Rel-8
Where
Radio Access Network › E-UTRAN (LTE)
Specifications
4 specs
PRC Description Purpose Related Classification Detected Changes Specifications

Description

Pseudo-Range Correction (PRC) is a key parameter in the 3GPP standardized Observed Time Difference of Arrival (OTDOA) positioning method. OTDOA is a network-assisted, UE-based positioning technique where the UE measures the time difference of arrival between reference signals (e.g., Positioning Reference Signals - PRS in LTE/NR) from multiple neighboring base stations (eNodeBs/gNodeBs) and a reference cell. The raw measured time difference is called the Reference Signal Time Difference (RSTD). However, these measurements are not perfectly synchronized due to imperfections in the network's timing distribution.

The PRC is the correction value, transmitted by the network to the UE, that accounts for the relative timing offset between the transmission instants of the positioning reference signals from different base stations. Conceptually, if the UE measures an RSTD, the actual geometric time difference of arrival (which is needed for hyperbolic positioning calculations) is approximately RSTD + PRC. The PRC is typically provided by a Location Server (e.g., Evolved Serving Mobile Location Centre - E-SMLC or Location Management Function - LMF) which has knowledge of the network's timing relationships, often derived from measurements by Location Measurement Units (LMUs) or from the base stations themselves if they are synchronized via GNSS or IEEE 1588.

Architecturally, PRCs are part of the assistance data delivered to the UE in the OTDOA procedure. The UE receives a list of neighbor cells for OTDOA measurement, along with their PRS configuration and the associated PRC values (and possibly a related parameter, RSTD uncertainty). The UE performs the RSTD measurements, applies the received PRCs, and then uses the corrected pseudo-ranges (proportional to the corrected time differences) to solve a set of hyperbolic equations to determine its own coordinates. The calculation can be performed in the UE (UE-based) or the measurements can be sent back to the network for calculation (UE-assisted).

The accuracy of the PRC directly impacts the final positioning accuracy. If the network is perfectly synchronized (e.g., all gNBs have a common time source like GPS), the PRCs would be zero. In real deployments, especially in asynchronous or partially synchronized networks (common in indoor or dense urban scenarios), the PRCs are non-zero and vital. The generation and distribution of accurate, low-latency PRCs are therefore critical functions of the positioning architecture, enabling OTDOA to meet regulatory (e.g., E-911) and commercial location-based service requirements.

Purpose & Motivation

PRC was introduced to enable accurate OTDOA positioning in practical, non-ideal cellular network deployments. The fundamental principle of OTDOA requires that the time of transmission of the positioning signals from different base stations is known relative to a common time reference. In an ideal, perfectly synchronized network, this condition holds, and the UE's raw RSTD measurements directly reflect the geometric time differences. However, achieving and maintaining perfect synchronization across all cells in a large network is costly and often impractical, especially for small cells or in environments where GNSS signals for synchronization are unavailable.

PRC solves this problem by decoupling the requirement for perfect real-time synchronization from the positioning functionality. It allows the network to operate with ordinary synchronization levels (or even be asynchronous) while still supporting high-accuracy positioning. The Location Server calculates the timing offsets between cells based on its knowledge of the network (from LMUs or base station reports) and provides these offsets as PRCs to the UE as correction data. This approach is more flexible and cost-effective than mandating ultra-precise network-wide synchronization.

Historically, as location-based services and regulatory mandates for emergency caller location (e.g., FCC E-911) gained importance, 3GPP needed robust positioning methods for LTE (introduced in Release 9). OTDOA was developed as a primary method, and the PRC mechanism was a key innovation to make it work in real-world conditions. It addressed the limitations of earlier cellular positioning methods like Cell-ID and Enhanced Cell-ID, which offered poor accuracy, and provided a standardized, scalable technique that could leverage the existing cellular infrastructure without imposing prohibitive synchronization requirements, paving the way for subsequent enhancements in NR.

Classification

Part ofOTDOA
Related approachesRSTDPRS

Detected Changes Across Releases

from 3GPP Change Requests

Specific changes extracted from the „Change history“ tables of 3GPP specifications (78 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 8 changes

In Release 15, the PRC function was enhanced to support new capabilities for OTDOA positioning, specifically for NR. Key introductions included support for IMU (Inertial Measurement Unit) sensor assistance data and the addition of TDD UL/DL configuration to OTDOA assistance data. Furthermore, assistance data request procedures were extended to NR, and an SFN offset parameter was added for OTDOA.

  • Introduction of IMU support for OTDOA TS 36.355CR0204
  • Corrections to TDD in 36.355 TS 36.355CR0218
  • OTDOA Assistance Data Request for NR TS 36.355CR0222
  • Addition of TDD UL/DL configuration to OTDOA assistance data TS 36.355CR0213
  • SFN offset for OTDOA TS 36.355CR0229
  • Sensor Assistance Data Elements Correction TS 36.355CR0232

+ 2 more changes

Rel-16 20 changes

In Release 16, the PRC (Pseudo-Range Correction) function saw specific technical corrections and clarifications to improve its operation. These included corrections to the PRS (Positioning Reference Signal) configuration, the DL-PRS (Downlink PRS) capability field description, and the NR-DL-PRS-ResourcesCapability. Additionally, the release introduced a correction for the BDS (BeiDou Navigation Satellite System) B2I clock model to enhance the accuracy of satellite-based corrections.

  • Sensor Provide Location Information Elements Correction TS 37.355CR0002
  • LPP miscellaneous corrections TS 37.355CR0272
  • Clarification of quality and time stamp for RSTD measurements TS 37.355CR0274
  • Correction of hanging ASN.1 code after END TS 37.355CR0280
  • Correction on LPP spec TS 37.355CR0282
  • Corrections on the field description of commonIEsProvideAssistanceData in TS37.355 TS 37.355CR0284

+ 14 more changes

Rel-17 25 changes

In Release 17, the PRC function saw updates through corrections to the transmission of SSR (State Space Representation) Assistance Data specifically for the BDS B1C signal. Furthermore, miscellaneous corrections were made to the overall LPP (LTE Positioning Protocol) capabilities and procedures that support PRC and other positioning functions.

  • LPP Updates and ASN.1 Corrections TS 37.355CR0347
  • Corrections on LPP capabilities TS 37.355CR0359
  • Correction on the GNSS Orbit and Clock Integrity Bounds in TS 37.355 TS 37.355CR0377
  • Miscellaneous LPP Corrections TS 37.355CR0378
  • Correction to UE capability for DL-AoD TS 37.355CR0379
  • Various LPP Corrections TS 37.355CR0386

+ 19 more changes

Rel-18 20 changes

In Release 18, the PRC function was enhanced through corrections and clarifications to the underlying LPP and RINEX Interface Layer (RIL) specifications. These updates included specific corrections for the NR-DL-TDOA-MeasurementCapability, GNSS-AlmanacSupport, and the NavIC almanac set information element. Furthermore, the release introduced miscellaneous RIL corrections for GNSS LOS/NLOS scenarios and for Bluetooth AoA/AoD positioning to improve the delivery and application of pseudo-range corrections.

  • ASN.1 corrections for TEI18 [PosL2RemoteUE] TS 37.355CR0488
  • Correction on NR NTN in TS 37.355 TS 37.355CR0489
  • Corrections to TS 37.355 (rapporteur's CR) TS 37.355CR0490
  • Corrections to Local Cartesian Coordinates [PosLocalCoords] TS 37.355CR0494
  • Miscellaneous RIL corrections for GNSS LOS/NLOS [GNSS LOS/NLOS] TS 37.355CR0495
  • Miscellaneous RIL corrections for Bluetooth AoA/AoD [BT-AoA-AoD] TS 37.355CR0496

+ 14 more changes

Rel-19 5 changes

In Release 19, the updates to the PRC function primarily involved corrections and clarifications to existing UE capabilities and assistance data procedures. These included specific corrections for UE capability related to uplink time window (UTW) in positioning SRS frequency hopping, both generally and for non-RedCap UEs. The release also introduced corrections to downlink AI/ML positioning and miscellaneous LPP corrections concerning GNSS line-of-sight and non-line-of-sight signaling.

  • Correction on UE capability for UTW in positioning SRS frequency hopping for nonRedCap UE [Pos_SRSHop] TS 37.355CR0565
  • Corrections to DL AI/ML Positioning TS 37.355CR0566
  • Miscellaneous LPP Corrections [GNSS LOS/NLOS] TS 37.355CR0567
  • Correction on UE capability for UTW in positioning SRS frequency hopping in 37355-r19 TS 37.355CR0564
  • Correction on description of nr-PosCalcAssistanceSupport in the table of NR-DL-AoD-ProvideCapabilities field descriptions TS 37.355CR0571

Explore further

Broader topics and technologies where PRC plays a role.

Defining Specifications

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

SpecificationTitleRelease
TS 25.305 vj00 UTRAN UE Positioning Stage 2 Rel-19
TS 25.453 vj00 PCAP Protocol Specification Rel-19
TS 36.355 vj00 LTE Positioning Protocol (LPP) Rel-19
TS 37.355 vj20 LTE Positioning Protocol (LPP) Rel-19