A High-Precision Clock Synchronization System for the CEPC Accelerator

This paper presents an enhanced White Rabbit-based clock synchronization system for the CEPC accelerator that achieves a measured end-node precision of 7.30 ps under temperature variations, significantly surpassing the required 30 ps synchronization budget through architectural improvements including a Si5345A DSPLL, reduced restart uncertainty, and reinforcement learning-based PID control.

Original authors: Jun Hu, Xin Zhou, Xiaoshan Jiang, Dapeng Jin

Published 2026-06-11
📖 5 min read🧠 Deep dive

Original authors: Jun Hu, Xin Zhou, Xiaoshan Jiang, Dapeng Jin

Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer

Imagine a massive, 100-kilometer-long underground racetrack where tiny particles (electrons and positrons) race around at nearly the speed of light. To keep these particles in a tight, perfect bunch and make them collide exactly where scientists want them to, every single control station along the track needs to be synchronized to the same "heartbeat."

This heartbeat is a clock signal. The challenge? The track is so long, and the physics so precise, that if two stations are even a tiny fraction of a second out of sync, the experiment fails. The goal for this project (the CEPC accelerator) was to keep all 192 stations perfectly synchronized within 30 picoseconds.

To put that in perspective: A picosecond is to a second what a second is to about 32 years. It is an almost unimaginably small amount of time.

Here is how the team solved the problem, explained simply:

1. The Problem: The "Old Way" Was Too Noisy

The team started with a standard system called "White Rabbit," which is like a high-tech walkie-talkie network that keeps clocks in sync. However, they found that the standard system had a "noisy engine."

  • The Analog Noise: The old system used a mix of digital chips and analog knobs (like a volume dial) to adjust the clock speed. This was like trying to tune a radio by turning a rusty, wobbly knob while standing next to a loud fan. The "knob" (analog circuit) introduced too much static noise, making the clock jittery.
  • The Restart Glitch: Every time the system was turned off and on again (like rebooting a computer), the clocks would wake up slightly confused. They would take a "guess" at what time it was, leading to a big jump in error (up to 88.8 picoseconds) before settling down.

2. The Solution: A Digital "Smart Engine"

To fix the noise, the team replaced the old "rusty knob" system with a brand-new, all-digital engine called the Si5345A.

  • The Metaphor: Instead of a human turning a wobbly analog dial, imagine a super-precise robot arm that can move in steps so small they are invisible to the naked eye. This new chip generates the clock signal entirely inside its own digital brain. It doesn't need external analog parts, so it's immune to electrical "static" and power fluctuations.
  • The Result: This removed the biggest source of noise, making the clock signal incredibly smooth and stable.

3. The Fix for the "Restart Confusion"

To stop the clocks from getting confused when they restart, the team wrote a new "wake-up routine" in the software (firmware).

  • The Metaphor: Imagine a choir of 192 singers. In the old system, when they started singing again after a break, everyone started on a slightly different beat, and it took a while to find the right rhythm.
  • The New Routine: The new system forces every singer to check their position against a master conductor immediately upon waking up. If they are even a tiny bit off, the system resets them and tries again until they are perfectly aligned.
  • The Result: The "waking up" error dropped from a huge 88.8 picoseconds down to a tiny 12 picoseconds.

4. The "Conductor" for the Whole Orchestra

With 192 stations spread over 100 km, simply having good individual clocks isn't enough. If Station A is slightly off, Station B (which listens to A) will be even more off, and Station C even more so. This is called "cascading error."

  • The Old Way: Each station tried to fix itself independently. Sometimes they over-corrected; sometimes they under-corrected.
  • The New Way: The team built a "Global Conductor" (a computer program) that listens to all 192 stations at once.
    • Temperature Compensation: Clocks drift when they get hot or cold. The system measures the temperature of every station and automatically adjusts the clock speed to cancel out the heat, like a thermostat that knows exactly how much to cool the room.
    • AI Learning: To figure out the perfect settings for this conductor, they used a type of Artificial Intelligence (Reinforcement Learning). The AI played a game where it tried to get all the clocks to sync up. Once it learned the best strategy, it locked those settings in.
  • The Result: Even with 12 stations in a row (a deep chain), the final station was only off by about 6.66 picoseconds, well within the safety limit.

The Final Scorecard

The team tested their new system in the lab:

  • Short distance (1 meter): Synchronized to 3.38 picoseconds.
  • Long distance (50 km): Synchronized to 3.92 picoseconds.
  • Deep chain (12 stations): Synchronized to 6.66 picoseconds.
  • Restarting: The "waking up" error is now 2.82 picoseconds.

Conclusion:
The team successfully built a clock synchronization system that is roughly 5 to 10 times more precise than the previous standard. They achieved this by swapping out noisy analog parts for a clean digital chip, writing a smarter "wake-up" routine, and using an AI-trained conductor to manage the whole network. This ensures that the massive CEPC accelerator can keep its 192 control nodes perfectly in step, allowing for the precise particle collisions needed to study the universe's fundamental secrets.

Drowning in papers in your field?

Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.

Try Digest →