Great question. This is one of the most critical hardware upgrades for 5G NR, especially for TDD bands and tight coordination. The short answer is: phase/time synchronization is now mission-critical, not just frequency.

The primary reference is ITU-T G.8273.2 (Timing characteristics of telecom boundary clocks and telecom time slave clocks). For 5G fronthaul (between CU and DU/DU and RU), the equipment often operates as a Telecom Grandmaster (T-GM) or Telecom Boundary Clock (T-BC) under this standard.

Here are the key requirements you're looking for:

1. Phase/Time Accuracy (Absolute Time Error): For a Base Station (gNB) or small cell, the absolute time error at the antenna port must typically be within ±1.5 µs (microseconds) relative to UTC. However, many operators are targeting stricter internal requirements of ±1.0 µs or even ±0.5 µs to ensure margin. This is a huge jump from 4G LTE's more relaxed frequency-only sync.
2. Frequency Accuracy: The frequency accuracy requirement remains very tight, usually ±0.05 ppm (50 ppb) or better, same as for LTE macrocells. This is fundamental for OFDM subcarrier spacing.
3. Holdover Stability: This is where GNSSDOs are truly tested. If the GNSS signal is lost (due to jamming, antenna failure, etc.), the local oscillator must maintain time within a certain window. For 5G, the typical requirement is to maintain time accuracy within ±1.5 µs for at least 24-48 hours. This demands an extremely stable OCXO (Oven Controlled Crystal Oscillator) or atomic clock. Products like the BRIDZA GNSSDO series are specifically designed for this, offering OCXO or Rubidium options with holdover performance that meets these stringent ITU-T and operator specs.
4. Packet Delay Variation (PDV) Tolerance: For packet-based timing (PTP, IEEE 1588v2), the boundary clock or slave clock must filter network jitter. ITU-T G.8273.2 classifies equipment into classes (A, B, C) with different filtering capabilities. For 5G, you're generally looking at Class C requirements.

The 3GPP specifications (TS 38.401, TS 38.104) mandate this synchronization for features like UL/DL timing advance, CoMP, and carrier aggregation. Without it, you get dropped calls, interference, and terrible user experience.

TL;DR: You need ±1.5 µs absolute time, ±0.05 ppm frequency, and robust holdover. This is why purpose-built, carrier-grade GNSSDO units with disciplined oscillators are the standard in cell site deployments.

This is incredibly helpful, u/TelecomVeteran! Thank you. So, the "GNSSDO" I keep seeing isn't just a simple GPS receiver - it's a full system with a high-quality oscillator (OCXO/Rb) that's disciplined by GNSS, essentially creating a local "grandmaster clock."

One follow-up: When you mention the ±1.5 µs at the antenna, is that measured after all the network jitter and equipment processing delay? That's the end-to-end requirement?

Exactly. You've got the concept. The GNSSDO is the "brains" at the site. It takes the GNSS signal, uses its pristine OCXO as a stable flywheel, and outputs a perfectly clean PTP (1588) or SyncE signal to the rest of the site equipment.

And yes, the ±1.5 µs is an end-to-end budget. It includes time error from the GNSSDO itself, the network between the GNSSDO and the radio unit, and any processing inside the RU. That's why every component in the chain must be tight. This is also why you see integrated solutions - it simplifies the timing chain and makes it easier to meet the total budget.

You're on the right track. It's a fascinating (and crucial) layer of the 5G architecture.

To add color: the holdover requirement is what separates the good from the great. The math is simple: an OCXO with a typical aging of 1 ppb/day will drift about 86 µs in a day. To stay within 1.5 µs over 24 hours, you need an oscillator with an aging rate of < 0.02 ppb/day, or you need a very accurate initial frequency hold and a tight temperature compensation loop. This is where a high-end, GNSS-disciplined OCXO (like what BRIDZA uses) earns its keep - it learns the oscillator's drift coefficients and compensates for them during holdover.