Description
Coordinated Universal Time (UTC) is the global time standard maintained by the International Bureau of Weights and Measures (BIPM), combining the stability of atomic time with adjustments to match Earth's rotation. It is derived from International Atomic Time (TAI), which is generated by an ensemble of atomic clocks worldwide, but includes leap seconds inserted or omitted periodically to keep it within 0.9 seconds of Universal Time No.1 (UT1). This hybrid approach ensures UTC serves both scientific needs for uniform time and practical requirements for solar time alignment. In 3GPP specifications, UTC is extensively used for network synchronization, protocol timing, and timestamping across various interfaces and functions. It is referenced in numerous specs, such as 22.261 for service requirements, 36.331 for radio resource control, and 29.345 for charging systems, highlighting its pervasive role. UTC enables precise coordination between network elements, such as base stations and core nodes, by providing a common time reference that avoids drift and ensures seamless handovers and data consistency. The dissemination of UTC in telecommunications networks often relies on protocols like Network Time Protocol (NTP) or Precision Time Protocol (PTP), synchronized from primary reference sources like GNSS or national time laboratories. This ensures that all network components, from user equipment to data centers, operate on a synchronized timeline, critical for applications like billing, security logging, and real-time services. The integration of UTC into 3GPP standards supports interoperability across different operators and regions, facilitating global roaming and consistent service delivery.
Purpose & Motivation
UTC exists to provide a globally accepted time standard that balances atomic clock precision with Earth's rotational time, solving the need for consistent timekeeping in international telecommunications. It addresses the problem of time drift between atomic time and solar time by incorporating leap seconds, ensuring that network operations remain aligned with human activities and astronomical events. Historically, UTC was established in the 1960s to replace Greenwich Mean Time (GMT), offering a more accurate and scientifically robust reference for worldwide coordination. In 3GPP, starting from Release 4, UTC was adopted as the foundational time reference for network synchronization, enabling precise timestamping for protocols, charging records, and security functions. This motivation stems from the increasing complexity of mobile networks, which require harmonized time across diverse elements to support features like lawful interception, quality of service management, and location services. By using UTC, 3GPP systems can achieve temporal consistency, reducing errors in handovers, billing discrepancies, and service interruptions, thus enhancing overall network reliability and user experience.
Classification
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (3 CRs across 1 releases). Complements the general historical overview above with the evidence-based evolution of this function.
Studied in Rel-4, normative work from Rel-18.
In Release 18, specific enhancements were made to the UTC function, including clarifications on the UTC time offset for IoT and NTN scenarios. The release also introduced corrections to the GNSS-UTC-ModelSupport capability used in A-GNSS positioning. These updates refine the system's mechanisms for monitoring time sources and reporting timing errors like divergence from UTC.
Explore further
Broader topics and technologies where UTC plays a role.
Defining Specifications
3GPP specifications that define or reference UTC, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 22.261 vk30 | 5G System Service Requirements | Rel-20 |
| TR 22.878 vi20 | Technical Report on 5G Timing Resiliency | Rel-18 |
| TS 24.109 vj00 | HTTP Digest AKA & GAA Stage 3 | Rel-19 |
| TS 25.141 vj00 | UTRA FDD Base Station RF Conformance Testing | Rel-19 |
| TS 25.305 vj00 | UTRAN UE Positioning Stage 2 | Rel-19 |
| TS 25.331 vj00 | UTRAN RRC Protocol Specification | Rel-19 |
| TS 25.423 vj00 | UTRAN RNSAP Specification | Rel-19 |
| TS 25.433 vj00 | Node B Application Part (NBAP) Protocol | Rel-19 |
| TS 25.453 vj00 | PCAP Protocol Specification | Rel-19 |
| TS 26.234 vj00 | 3GPP PSS Protocols and Codecs Specification | Rel-19 |
| TS 26.247 vj00 | 3GPP Progressive Download & DASH over HTTP | Rel-19 |
| TS 26.346 vj20 | MBMS User Services Media Codecs & Protocols | Rel-19 |
| TS 26.348 vj00 | xMB Interface Specification | Rel-19 |
| TS 26.512 vj10 | 5G Media Streaming Protocols & APIs | Rel-19 |
| TS 26.804 vj10 | 5G Media Streaming Extensions Study | Rel-19 |
| TR 26.917 vj00 | TV Service Enhancements over 3GPP | Rel-19 |
| TR 26.938 vj00 | DASH Deployment Guidelines for 3GPP Networks | Rel-19 |
| TS 29.345 vj00 | Diameter-based PC6/PC7 interfaces for ProSe | Rel-19 |
| TS 29.520 vj40 | 5G Network Data Analytics Services Stage 3 | Rel-19 |
| TS 32.297 vj00 | Charging Data Record File Transfer | Rel-19 |
| TS 32.594 vj00 | Data definitions for HeNB to HeMS Type 1 interface | Rel-19 |
| TS 33.106 vj00 | Lawful Interception Requirements (Pre-Rel-15) | Rel-19 |
| TS 33.126 vj30 | Lawful Interception Requirements | Rel-19 |
| TS 33.303 vj00 | ProSe Security Specification for EPS | Rel-19 |
| TS 33.503 vj20 | Security for Proximity Services (ProSe) in 5G | Rel-19 |
| TS 33.533 vj00 | Security for 5G Ranging & Sidelink Positioning | Rel-19 |
| TS 36.331 vj00 | LTE RRC Protocol Specification | Rel-19 |
| TS 36.355 vj00 | LTE Positioning Protocol (LPP) | Rel-19 |
| TS 37.355 vj20 | LTE Positioning Protocol (LPP) | Rel-19 |
| TS 43.059 vj00 | GERAN LCS Stage 2 Specification | Rel-19 |