How SyncE Works in 5G Networks: Synchronous Ethernet for Frequency Synchronization

PTP gets the headlines in 5G timing discussions — and for good reason. But there is a second synchronization technology that runs silently alongside PTP in nearly every modern mobile network: Synchronous Ethernet (SyncE). While PTP delivers absolute time and phase, SyncE delivers frequency synchronization — ensuring that every node in the network runs at exactly the same clock rate. This article explains how SyncE works at the physical layer, why 5G needs both PTP and SyncE, and how they complement each other in a real 5G RAN deployment.

What Is SyncE — and Why Is It Different from PTP?

Synchronous Ethernet, standardized by ITU-T G.8262 and G.8264, is a physical-layer frequency synchronization technology. It works by recovering a clock signal from the incoming Ethernet line bitstream — the same way SDH/SONET networks have distributed frequency for decades. Every Ethernet link carries an embedded clock in its physical coding sublayer (PCS). A SyncE-capable Ethernet PHY extracts this clock, cleans it with a phased-locked loop (PLL), and uses it to clock the outgoing Ethernet links. The result: every node in the chain runs at the same frequency — typically derived from a primary reference clock (PRC) traceable to UTC, with frequency accuracy better than ±1 × 10⁻¹¹.

How SyncE Works: Clock Recovery from the Ethernet Bitstream

SyncE operates entirely at the physical layer. Here is the chain:

1. Primary Reference Clock (PRC): A GNSS-disciplined oscillator — usually a cesium or rubidium atomic reference or a high-quality OCXO locked to GPS/BeiDou — generates the master frequency with accuracy better than ±1 × 10⁻¹¹.

2. SyncE-capable Ethernet PHY: The PRC feeds its clock into a SyncE-capable switch or router. The switch's Ethernet PHY embeds this clock into the transmitted bitstream. Every Ethernet line code (1000BASE-X, 10GBASE-R, 25GBASE-R, etc.) carries an embedded clock that the receiver can recover.

3. Clock recovery at each hop: The downstream node's SyncE PHY recovers the clock from the incoming bitstream, passes it through a PLL to filter jitter, and uses it to drive its own transmit PHYs. Each node in the chain becomes a slave to the one above it.

4. Ethernet Synchronization Messaging Channel (ESMC): Defined in ITU-T G.8264, ESMC carries SSM (Synchronization Status Messages) that tell each node the quality level (QL) of the clock it is receiving. If a node detects clock degradation, ESMC triggers a switch to a backup clock source — the same concept as SDH/SONET SSM, but carried over Ethernet slow-protocol frames.

Because SyncE recovers the clock from the physical bitstream — not from packet timestamps — it is completely immune to packet delay variation, congestion, and network load. A congested link with 90% utilization degrades PTP accuracy; it has zero impact on SyncE frequency accuracy.

Why 5G Needs SyncE: Three Critical Use Cases

1. Radio Frequency Stability (3GPP TS 38.104)

5G NR base stations must maintain ±50 ppb (parts per billion) frequency accuracy for wide-area base stations and ±100 ppb for medium-range and local-area base stations. A gNB that drifts outside this tolerance risks adjacent-channel interference and degraded spectral efficiency. SyncE delivers the frequency reference that keeps the radio local oscillator locked to this tolerance — independent of the PTP time/phase synchronization.

2. CPRI/eCPRI Fronthaul Clocking

In a centralized RAN (C-RAN) or O-RAN split 7.2 architecture, the connection between the Distributed Unit (DU) and Radio Unit (RU) carries digitized I/Q samples over CPRI or eCPRI. These protocols require the DU and RU to run at exactly the same sample clock frequency. If the DU's clock and the RU's clock diverge by even a few ppm, sample slips occur — causing periodic bursts of bit errors that FEC cannot fully correct. SyncE provides a common frequency reference that locks both ends of the fronthaul link to the same clock.

3. Holdover When PTP Fails

PTP is a packet-based protocol — it can fail if the network becomes congested, if a PTP-aware switch fails, or if the grandmaster loses GNSS lock. SyncE provides a frequency fallback: even if PTP time and phase are temporarily lost, the base station's local oscillator stays frequency-locked to the SyncE reference. When PTP recovers, the base station resynchronizes its phase rapidly because its frequency was never lost. This is the frequency-assisted phase recovery pattern, and it significantly reduces the time needed to reacquire PTP lock after an outage.

Deploying SyncE in a 5G Network: Practical Considerations

• Every hop must be SyncE-capable. Unlike PTP with Transparent Clocks, SyncE requires every intermediate Ethernet PHY to support clock recovery and retransmission. If a single non-SyncE switch sits in the chain, the frequency chain breaks.

• ESMC must be enabled end-to-end. Without ESMC (G.8264 SSM messages), nodes cannot verify the quality of the clock they are receiving and cannot fail over to a backup clock source.

• PTP + SyncE is the recommended combination. ITU-T G.8275.1 (Full Timing Support) expects both PTP and SyncE to be deployed. PTP handles time and phase; SyncE handles frequency. The combination delivers the highest synchronization performance with the best resilience to network impairments.

• SyncE works over fiber and copper. 1000BASE-T, 10GBASE-T, and all optical Ethernet standards (1GE–400GE) support SyncE. For wireless backhaul links (microwave, millimeter-wave), SyncE requires the radio to embed the clock in the modem framing — not all microwave radios support this.

APEX GROUP — www.apexallinone.com