Network Clock Synchronization Using a Common Time-Base Controller

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing communication network synchronization methods, such as master-slave and distributed synchronization, face challenges in maintaining accurate timing due to clock instabilities and resource-intensive algorithms, and are vulnerable to failures when the common source fails.

Innovation Solution

A network architecture that includes a synchronization system determining a common time-base for master clocks without relying on slave clocks, using slave clock synchronisation data from selected master clocks to control slave clocks, ensuring reliability and simplicity in design.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If master-slave synchronisation is used to set nodes to a common time-base, then timing accuracy is improved, but the system becomes vulnerable to failures when the common source fails

Engineering Contradiction:
Improvetiming accuracyVSAvoidsystem vulnerability to common source failure
Core Design Contradiction:
Measurement precisionVSReliability

Solution Approach 1:

The patent segments the synchronisation function by introducing a dedicated synchronisation unit separate from the common source. This unit receives timing information from the common source and independently determines the time-base, creating a functional separation that isolates the system from common source failures while maintaining timing accuracy.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The synchronisation unit acts as an intermediary between the common source and the nodes. It receives timing information from the common source, processes it to determine the time-base, and provides it to nodes. This intermediary layer protects the system from direct exposure to common source failures while preserving timing precision.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If distributed synchronisation is used to exchange timing information between nodes, then reliability is improved by eliminating single point of failure, but device complexity and resource requirements increase

Engineering Contradiction:
Improveresistance to single point of failureVSAvoidcomplexity of synchronisation unit and algorithms
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent extracts the complex time-base determination algorithms from the nodes and concentrates them in a dedicated synchronisation unit. The nodes only need to receive and apply timing information, while the synchronisation unit handles the complex processing of timing data from multiple sources to determine the optimal time-base.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The synchronisation unit serves multiple functions: it receives timing information from the common source, processes this information along with data from other nodes, determines the optimal time-base, and distributes it to all nodes. This multi-functional approach consolidates complexity in a single unit rather than distributing it across all nodes.

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

Data Source

PatentUS8130014B2Network and method for setting a time-base of a node in the network
Publication Date: 2012.03.06 NXP USA INC
  • US8130014B2 patent drawing
  • US8130014B2 patent drawing
  • US8130014B2 patent drawing

AI summary

A data communication network may, include a first sub-network and a second sub-network. The first sub-network may include two or more two master clocks, and a synchronization system connected to the master clocks. The synchronization system may, for determine a time-base for the master clocks and control the master clocks based on the determined time-base. The first sub-network may include one or more slave synchronization data source for generating slave clock synchronization data derived from time information of the master clocks. The second sub-network may include one or more slave clocks and a slave clock time-base controller connected to the slave synchronization data source. The time-base controller may receive the slave clock synchronization data and control one or more of the one or more slave clocks in accordance with the slave clock synchronization data.