Cluster Clock Synchronization for Nanosecond 5G Routing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Distributed computing systems face challenges in achieving nanosecond-level synchronization precision for 5G cellular networks, particularly in disaggregated radio systems using commodity hardware, where cluster elements require synchronization and appear as a single logical unit.

Innovation Solution

Implementing a dual synchronization plane within the cluster, utilizing IEEE 1588 and Synchronous Ethernet (Sync-E) over an out-of-band management network, and optionally using a dedicated timing device, to synchronize cluster elements for precise time stamping and clock distribution.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If clock correction is performed at every network node to achieve nanosecond-level synchronization precision, then synchronization precision is improved, but device complexity and operational overhead increase

Engineering Contradiction:
Improvesynchronization precisionVSAvoidsystem complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The system divides synchronization into two independent planes: a control plane for clock distribution and time synchronization management, and a data plane for traffic forwarding. This segmentation allows complex synchronization tasks to be handled by dedicated control plane functions rather than requiring every network node to perform complex clock correction operations, thereby achieving nanosecond-level precision without overwhelming device complexity.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a dedicated timing device as an intermediary component that centralizes clock correction functions. This timing device acts as a mediator between the external clock source and multiple cluster elements, performing the complex clock correction calculations and distributing corrected timing information to all nodes. This eliminates the need for each network node to independently perform complex clock correction, reducing overall system complexity while maintaining nanosecond-level synchronization precision.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If proprietary chassis cages with dedicated synchronization lanes are used to achieve intra-chassis synchronization, then synchronization reliability is improved, but adaptability and ease of deployment deteriorate

Engineering Contradiction:
Improvesynchronization reliabilityVSAvoidsystem adaptability
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent makes the timing device and synchronization functions universal by implementing them as software-based solutions that can run on standard, off-the-shelf hardware platforms. The control plane software can be deployed across different network architectures and hardware configurations, eliminating the need for proprietary chassis cages. This universal approach maintains synchronization reliability through proven protocols while significantly improving adaptability to various deployment scenarios and hardware platforms.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The patent replaces the mechanical/physical dedicated synchronization lanes with software-based logical channels over standard network interfaces. Instead of requiring specialized physical infrastructure (proprietary chassis with dedicated lanes), the system uses software to establish synchronization pathways over conventional Ethernet or other standard network connections. This substitution maintains synchronization reliability through protocol-level guarantees while dramatically improving adaptability and ease of deployment across diverse hardware platforms.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

3Ease of manufacture

If standard off-the-shelf components are used to build distributed clusters, then ease of manufacture and cost-effectiveness are improved, but achieving nanosecond-level synchronization precision becomes more difficult

Engineering Contradiction:
Improveease of deploymentVSAvoidsynchronization precision
Core Design Contradiction:
Ease of manufactureVSMeasurement precision

Solution Approach 1:

The dedicated timing device serves as an intermediary that compensates for the lower inherent precision of off-the-shelf components. By centralizing clock correction functions in this timing device, the system can achieve nanosecond-level synchronization precision even when using standard hardware with less precise internal clocks. The timing device performs detailed clock correction calculations and distributes corrected timing information, enabling high-precision synchronization without requiring expensive specialized hardware at each node.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent implements virtual timing devices and software-based clock correction mechanisms that create a logical copy of precise timing functionality across the distributed cluster. Instead of requiring each physical component to have inherent high-precision timing capabilities, the system creates software copies of the timing function that can be synchronized to nanosecond precision through the control plane. This allows standard off-the-shelf components to achieve high-precision synchronization through software-based timing virtualization and coordination.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS12476905B2Synchronization in distributed communication systems
Publication Date: 2025.11.18 DRAJVNETS LTD
  • US12476905B2 patent drawing
  • US12476905B2 patent drawing

AI summary

A distributed routing system is provided for use in a communication network, wherein the distributed routing system includes at least one cluster comprising a plurality of cluster elements and characterized in that the cluster elements that are used for forwarding communication traffic from among the plurality of cluster elements are synchronized there-between to a single clock and then synchronized to an external communication element, such as a client clock. Optionally, all the cluster elements that are used for forward communication traffic, are configured to implement IEEE 1588 standard and/or Synchronous Ethernet (Sync-E).