Description
Within 3GPP specifications, the US Naval Observatory (USNO) is referenced as a source of precise time information, specifically Coordinated Universal Time (UTC). This external time reference is utilized by network-based and UE-based positioning methods to achieve high accuracy. The primary application is in the Assisted Global Navigation Satellite System (A-GNSS) framework, where the network provides assistance data to the User Equipment (UE) to speed up satellite acquisition and improve positioning accuracy.
Architecturally, a location server in the network, such as the Enhanced Serving Mobile Location Centre (E-SMLC) or Location Management Function (LMF) in 5G, can obtain precise time from a USNO time server via Network Time Protocol (NTP) or similar mechanisms. This time information is then formatted and delivered to the UE as part of the assistance data within the LTE Positioning Protocol (LPP) or NR Positioning Protocol (NRPPa) messages. The assistance data can include parameters like GNSS reference time, satellite ephemeris, and clock corrections, all of which are often referenced to a precise time source like USNO.
When a UE receives this assistance data, it uses the precise time reference to calibrate its local clock and to more accurately calculate the time-of-flight of signals from multiple GNSS satellites (e.g., GPS, Galileo). Since positioning via trilateration requires extremely precise time measurements (errors of nanoseconds can lead to meter-level positioning errors), having a common, high-accuracy reference like USNO time is critical. It allows the UE to correct for clock drift and align its measurements with the global time scale used by the satellite constellations.
Beyond A-GNSS, precise external time references like USNO are also important for network synchronization requirements, such as in Time Division Duplex (TDD) systems or for coordinating features like Coordinated Multipoint (CoMP). While not a 3GPP-defined network element, the inclusion of USNO in specifications like 3GPP TS 36.355 (LPP) underscores the importance of interworking with global timing infrastructures to meet stringent location accuracy requirements for emergency services, navigation, and other location-based applications.
Purpose & Motivation
The reference to the US Naval Observatory in 3GPP standards addresses the need for a highly accurate, stable, and universally recognized time source to enable precise positioning services. Early cellular location services like Cell-ID provided very coarse accuracy. The introduction of A-GNSS in 3GPP required a method to provide UEs with precise timing data to reduce Time-To-First-Fix (TTFF) and improve location accuracy, especially in challenging signal conditions.
Using an external authoritative source like USNO solves the problem of time reference alignment between the cellular network, the UE, and the global satellite constellations. Without a common, precise time reference, the assistance data provided by the network would be less effective, as any error in the network's time would be transferred to the UE, degrading positioning performance. USNO, as a primary time standard for the United States and a contributor to UTC, provides the necessary level of accuracy and reliability.
This integration allows 3GPP systems to meet regulatory requirements for emergency caller location (e.g., E911 in the USA) and enables commercial high-accuracy location-based services. It represents the convergence of telecommunications with global navigation and timing infrastructures, ensuring that cellular networks can act as a reliable platform for precise positioning by leveraging established, trusted time authorities.
Classification
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (5 CRs across 3 releases). Complements the general historical overview above with the evidence-based evolution of this function.
Studied in Rel-8, normative work from Rel-16.
In Release 16, the USNO function was updated to support the BeiDou Navigation Satellite System (BDS) by introducing assistance data for the new B1C signal. Additionally, the existing support for the BDS B1I signal was updated to align with its Interface Control Document (ICD) version 3.0. These changes enhanced the A-GNSS positioning capabilities for user equipment utilizing BDS.
In Release 18, the USNO function was updated through corrections to the support for GNSS-Almanac and GNSS-UTC-Model. These corrections specifically impacted A-GNSS positioning procedures to ensure proper handling of these assistance data models.
- Correction on GNSS-AlmanacSupport and GNSS-UTC-ModelSupport in A-GNSS positioning TS 37.355CR0518
In Release 19, the USNO function was enhanced by introducing support for two new Global Navigation Satellite System (GNSS) signals within the A-GNSS framework. Specifically, support for the NavIC L1 Signal for Positioning Service (SPS) was added to the LTE Positioning Protocol (LPP). Additionally, support for the BeiDou Navigation Satellite System (BDS) B2b signal was introduced for A-GNSS.
Explore further
Broader topics and technologies where USNO plays a role.
Defining Specifications
3GPP specifications that define or reference USNO, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 36.355 vj00 | LTE Positioning Protocol (LPP) | Rel-19 |
| TS 37.355 vj20 | LTE Positioning Protocol (LPP) | Rel-19 |
| TS 44.031 vj00 | Radio Resource LCS Protocol (RRLP) | Rel-19 |