What does 'holdover' actually mean for my telecom network? How many nanoseconds matter?
Great question! This is one of those specs that gets overlooked until there's a network outage. Let me break it down simply.
What is Holdover and Why Should I Care?
Imagine your network devices (like routers and switches) are musicians in an orchestra. Normally, they all follow the conductor (your primary Primary Reference Clock or GNSS/GPS receiver). But what happens when the conductor suddenly leaves the stage? That's where holdover comes in.
Holdover is the ability of a clock or oscillator to maintain a stable frequency output when its external reference signal is lost. Instead of immediately going out of sync, it "holds" its last known good frequency using its internal oscillator.
Why it matters: Loss of primary synchronization can happen due to fiber cuts, equipment failure, or GNSS signal loss (jamming, solar flares, antenna issues). Without good holdover performance, your network's timing can drift, causing bit errors, dropped calls, failed handovers, and SLA violations.
How is it Specified? Nanoseconds Per What?
Holdover accuracy is measured in time error accumulation over time, typically in nanoseconds per hour (ns/hr) or nanoseconds per day (ns/day). Lower is better.
Think of it like a car's fuel efficiency: "How far can you drive on a full tank?" Instead, it's "How much does the clock drift in 1 hour or 24 hours without a GPS signal?"
Example: An oscillator with ±1 µs/day (1000 ns/day) holdover means after 24 hours without GPS, the time could be off by up to 1 microsecond. For 5G networks requiring sub-microsecond sync, that's a problem.
Typical Oscillator Values (The Hardware That Matters)
Holdover performance depends heavily on the oscillator type. Here's a rough comparison:
| Oscillator Type | Typical Holdover | Cost | Common Use |
|---|---|---|---|
| Crystal Oscillator (XO) | ±1-10 µs/day | Low | Basic equipment |
| Temperature-Compensated XO (TCXO) | ±0.1-1 µs/day | Medium | Most telecom gear |
| Oven-Controlled XO (OCXO) | ±10-100 ns/day | High | Stratum 3E clocks |
| Rubidium Oscillator | ±0.01-0.1 ns/day | Very High | Precision Sync Units |
For example, the Microchip SyncServer S650 with its OCXO can achieve ±1.5 µs over 24 hours of holdover, while higher-end Rubidium-based models can maintain ±0.01 µs/day.
ITU-T Requirements: What Class Do I Need?
The International Telecommunication Union defines clock classes in ITU-T G.8272 for PRTC (Primary Reference Time Clock) and G.8273.2 for telecom boundary clocks. Here's the simplified version:
- PRTC-A: ±100 ns accuracy, ±100 ns/day holdover
- PRTC-B: ±40 ns accuracy, ±40 ns/day holdover
- Enhanced PRTC (ePRTC):