Implementing Precision Timing / Sync as a Service in a Telecommunications Network#

Phil Carlisle (Chorus)

• Why: Timing distribution is physical-network infrastructure: PTP (IEEE1588v2) and SyncE over terrestrial transport is both a hard operational problem (asymmetry, wander, hop budget) and a growing service as GNSS jamming/spoofing makes antenna-per-site architectures risky. Relevant to anyone building or consuming time-sensitive transport — including sync-sensitive DC fabrics — and a good case study in hardening a WAN service against GNSS vulnerability.
• What: Chorus's investigation and lab/customer trials of delivering precision timing as a network service over its own transport using IEEE1588v2 and SyncE, instead of deploying GNSS receivers at every consumer site, and what rolling that out across the Chorus network implies. (from abstract only)
• How: Terrestrial time transfer over existing fiber transport (PTP with SyncE frequency assist), replacing per-site GNSS clocks — motivated by both deployment cost (clock + antenna + cabling per site at scale) and GNSS's vulnerability to jamming, spoofing, and space weather.
• Where applicable: The trial findings are Chorus/topology-specific (NZ access network), but the pattern — PTP-as-a-service over operator transport to eliminate fragile distributed GNSS — transfers to any operator or large campus/DC environment with sync consumers (mobile, power, finance).