Description
Holdover time is a synchronization resilience concept introduced in 3GPP Release 18 within the service requirements framework for 5G timing and synchronization. It is defined as the time period that is available to repair the first priority timing source when it is lost — for example, when the primary GNSS reference feeding a gNodeB or a synchronization distribution chain disappears. During this holdover window, the network must continue to guarantee the synchronization accuracy requirement, typically by relying on alternate synchronization references such as IEEE 1588 Precision Time Protocol (PTP) from the transport network, SyncE, or a local oscillator/clock that free-runs within specified accuracy bounds.
The concept addresses a fundamental vulnerability of timing-critical services: many 5G use cases, including industrial automation, smart grid, time-sensitive networking (TSN) integration, and coordinated multipoint transmission, depend on tight phase and frequency accuracy (often sub-microsecond phase). If the primary reference is lost, an immediate degradation would break these services. Holdover time formalizes how long the system can bridge that gap while repair actions — such as restoring the GNSS antenna, switching to a backup PTP grandmaster, or dispatching maintenance — are carried out.
Architecturally, holdover time is a requirement parameter rather than a protocol mechanism. It is expressed in service requirement specifications (TS 22.261 for 5G service requirements and TR 22.878 on synchronization service requirements) and is used by network operators and equipment vendors to dimension synchronization architectures. The network must be designed with multiple synchronization references and a defined priority hierarchy: the first priority source (e.g., GNSS) is normally active, and upon its loss the system enters holdover, maintaining accuracy through secondary references or a stable local clock until the primary is repaired or a permanent switch is made.
The length of the holdover time requirement depends on the deployment scenario. In a factory with stringent phase requirements, the holdover time may be short because even brief degradation is unacceptable, driving redundant references. In wide-area networks where GNSS outages are rare but repair may take hours, a longer holdover time with a high-quality local oscillator may be specified. The parameter therefore couples synchronization performance with operational maintenance processes.
In the 3GPP framework, holdover time interacts with synchronization status reporting and reference selection procedures. The definition remained textually identical across Rel-18, Rel-19, and Rel-20, indicating a stable concept whose surrounding normative work (e.g., detailed accuracy budgets and reference models) evolved elsewhere. It is a key input for designing resilient timing distribution for 5G and beyond, especially as networks move toward disaggregated, cloud-native deployments where timing must traverse more hops.
Purpose & Motivation
Holdover time exists to make 5G synchronization resilient to the loss of a primary timing reference. Before this concept was formalized, synchronization requirements focused mainly on steady-state accuracy, without an explicit, standardized notion of how long accuracy must be preserved during an outage. This left a gap: operators needed a common vocabulary to specify, design, and verify backup timing behavior when GNSS or another first-priority source failed.
By defining a repair window during which accuracy must be guaranteed, the concept forces architects to plan multiple synchronization references and to align maintenance response times with network capabilities. It bridges the worlds of service requirements and transport/clock engineering, enabling use cases such as industrial control and power grid protection that cannot tolerate timing discontinuities.
The introduction in Rel-18 reflects the maturation of 5G verticals that depend on precise time, and the need for a standardized parameter that vendors, operators, and vertical industries can use in contracts and deployment specifications.
What changed in its specifications
The latest release-to-release comparison of specifications that define Holdover time. Each summary describes the whole specification, not only this term.
Rel-19 adds to TS 22.261 Indirect Network Sharing, 5G satellite access Phase 3 requirements, a 5G wireless sensing service clause, signalling traffic monitoring, SNPN interconnection clauses, and Localized Mobile Metaverse Services. It also extends disaster roaming to 5G-only UEs and adds Ambient IoT device clauses.
Full comparison in TS 22.261 →Release Timeline
Evolution Across Releases
An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.
Defining Specifications
3GPP specifications that define or reference Holdover time, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 22.261 vk81 | 5G Service and Operational Requirements | Rel-20 read |
| TR 22.878 vi20 | Technical Report on 5G Timing Resiliency | Rel-18 read |