Description
Clock synchronicity is a 5G system performance requirement that bounds the time error between a reference master clock and the local clock of any UE within a synchronisation domain. It is defined in the 3GPP service requirements specifications (22.104, 22.804, 22.826, 22.827) as part of the broader time-sensitive communication (TSC) framework introduced for vertical industries. The concept is central to cyber-physical systems such as industrial automation, power grid control, and motion control, where distributed devices must act on a shared time base with tight tolerances.
Architecturally, a synchronisation domain consists of a grandmaster clock (often derived from GNSS or a PTP grandmaster), a 5G system acting as a time distribution bridge, and one or more UEs with local clocks. The 5G system transports timing information using IEEE 1588 Precision Time Protocol (PTP) or the 5G-specific time distribution mechanisms defined in TS 23.501 and TS 24.539. The clock synchronicity requirement specifies the worst-case offset that any UE clock may exhibit relative to the master, covering all error contributions: grandmaster accuracy, transport delay asymmetry, residence time in the 5G system, and UE-side clock servo error.
The 5G system supports time synchronisation through several mechanisms. In the transparent clock approach, the UPF and gNB measure and compensate for residence times, while the UE runs a PTP slave. In the boundary clock approach, the gNB or UPF terminates PTP and regenerates timing. 3GPP also defines 5G access stratum time distribution (TS 38.331, TS 24.539) where the gNB broadcasts or unicasts reference time information to UEs, enabling devices without PTP support to align their clocks. The choice of mechanism depends on the required accuracy: typical TSC classes range from 1 µs for motion control to 1 ms for less demanding applications.
Key components include the grandmaster, the 5G system as a time-aware bridge, the UE clock, and the synchronisation domain boundary. Performance depends on factors such as gNB and UPF residence-time measurement accuracy, fronthaul and backhaul latency symmetry, and UE clock quality. 3GPP specifies requirements on the 5G system's contribution to the overall error budget, allowing verticals to design their end-to-end synchronisation chains.
Clock synchronicity matters because many industrial and critical-infrastructure applications cannot function without a common time reference. It enables deterministic behaviour, coordinated actuation, and accurate timestamping for analytics and control. As 5G expands into vertical markets, clock synchronicity has become a first-class QoS and service requirement, driving enhancements in RAN, core, and UE specifications across Releases 16 through 19.
Purpose & Motivation
Clock synchronicity exists to guarantee that distributed devices in industrial and critical-infrastructure environments share a common time base with bounded error. Before 5G, such applications relied on wired fieldbuses (e.g., PROFINET, EtherCAT) or dedicated PTP networks, which limited mobility and flexibility. 5G NR promised to replace cables, but wireless transport introduces variable latency and asymmetry that can degrade timing. The 3GPP requirement defines an explicit accuracy bound so that verticals can trust 5G as a time-distribution medium.
The concept addresses the need for a standardized, quantifiable performance target that spans the entire 5G system. Earlier cellular systems offered only coarse timing (e.g., frame-level sync), insufficient for microsecond-level industrial control. By defining clock synchronicity in service requirements, 3GPP enables equipment vendors and operators to design and verify 5G networks that meet specific TSC classes, fostering interoperability and market adoption.
Historically, the requirement emerged from studies in 22.804 (factory automation) and 22.104 (cyber-physical control), which identified time synchronisation as a key gap. Releases 16–19 refined the wording and scope, aligning it with the evolving 5G system architecture and time distribution mechanisms. The requirement motivates features such as residence-time compensation, PTP support in the UPF, and AS-level time distribution, making 5G a viable replacement for wired industrial networks.
What changed in its specifications
The latest release-to-release comparison of specifications that define Clock synchronicity. Each summary describes the whole specification, not only this term.
Rel-19 adds an industrial edge computing clause covering production systems and mobile robot edge control. It also tightens 5G clock synchronisation budgets to 700 ns.
Full comparison in TS 22.104 →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.
Initial definition introduced: 'the maximum allowed time offset within a synchronisation domain between the sync master and any sync device.' This established the fundamental accuracy bound for time-sensitive communication in 5G, supporting industrial automation and cyber-physical control use cases.
Wording changed to: 'the maximum allowed time offset within a synchronisation domain between the master clock and any individual UE clock.' The revision replaced 'sync master' and 'sync device' with 'master clock' and 'individual UE clock', clarifying that the requirement applies specifically to UE clocks in the 5G system.
Defining Specifications
3GPP specifications that define or reference Clock synchronicity, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 22.104 vj20 | Service requirements for cyber-physical control applications | Rel-19 read |
| TR 22.804 vg30 | 5G Automation in Vertical Domains Study | Rel-16 read |
| TR 22.826 vh20 | Study on 5G for Critical Medical Applications | Rel-17 read |
| TR 22.827 vh10 | Study on Audio-Visual Service Production Stage 1 | Rel-17 read |