Unified Sync Domain for Automation Clock Synchronization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing methods for synchronizing operating and timing clocks in automation networks require multiple synchronization messages and additional hardware, leading to increased complexity and potential disruptions during domain integration or decoupling.

Innovation Solution

A method where a single synchronization message is used to coordinate the operating and timing clocks of sync slaves within a subordinate domain, incorporating the difference between the timing and operating clocks as additional information, allowing for simultaneous synchronization without additional hardware and minimizing network load.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If multiple synchronization messages are used to coordinate operating and timing clocks, then synchronization accuracy is improved, but device complexity and networking complexity increase

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

Solution Approach 1:

The patent combines multiple synchronization messages into a single integrated message that carries both operating clock synchronization data and timing clock synchronization data. This merging eliminates the need for separate message exchanges, reducing networking complexity while maintaining synchronization accuracy for both clock types.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The single synchronization message is designed to serve multiple functions simultaneously: it synchronizes both the operating clock and timing clock of sync slaves, and it provides the difference information between these two clocks. This multi-functionality reduces the number of messages needed while achieving comprehensive synchronization.

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

2Reliability

If additional hardware is deployed for clock synchronization, then synchronization reliability is improved, but device complexity increases

Engineering Contradiction:
Improvesynchronization reliabilityVSAvoidhardware requirements
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The clock sync master automatically determines and includes the difference between timing clock and operating clock within the synchronization message itself, eliminating the need for external hardware to provide this information. The system uses its own internal clock resources to generate all necessary synchronization data.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The existing clock sync master infrastructure is made multi-functional by enabling it to provide both operating clock synchronization and timing clock synchronization through a single message, removing the need for additional dedicated hardware components for each clock type.

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

3Measurement precision

If separate synchronization domains are used for operating clock and timing clock, then clock error is reduced, but device complexity increases

Engineering Contradiction:
Improveclock errorVSAvoiddomain complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The patent merges the previously separate operating clock domain and timing clock domain into a single unified synchronization domain. The clock sync master manages both clock types within one domain, using a single synchronization message that carries all necessary information, thereby reducing domain complexity while maintaining clock accuracy.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

Within the unified domain, the synchronization message is segmented to include distinct information fields: one for operating clock synchronization, one for timing clock synchronization, and one for the difference between them. This logical segmentation maintains precision while allowing unified domain management.

Inventive Principle:
Principle #1Segmentation

4Loss of information

If multiple synchronization messages are transmitted, then synchronization completeness is improved, but networking load increases

Engineering Contradiction:
Improvesynchronization completenessVSAvoidnetworking load
Core Design Contradiction:
Loss of informationVSLoss of energy

Solution Approach 1:

Multiple synchronization messages are merged into a single comprehensive message that contains all necessary synchronization information for both operating and timing clocks. This consolidation reduces the total number of message transmissions, lowering networking load while ensuring complete synchronization information is delivered in one go.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The single synchronization message is designed as a multi-functional carrier that delivers operating clock data, timing clock data, and their difference information simultaneously, ensuring synchronization completeness without requiring multiple separate transmissions.

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

Data Source

PatentUS8892934B2Method for integration of systems with only one sync domain for time of day and clock pulse synchronization into a global time of day synchronization domain
Publication Date: 2014.11.18 SIEMENS AG
  • US8892934B2 patent drawing
  • US8892934B2 patent drawing
  • US8892934B2 patent drawing

AI summary

A method for synchronizing the operating clock and the timing clock of a subordinate domain of an automation network, wherein sync slaves are synchronized by a clock sync master with respect to an operating clock, a clock sync master forms part of a subordinate domain, a single synchronization message serves to synchronize the sync slaves with respect to their respective operating clock and timing clock, wherein the method comprises providing a notification of the difference between the timing clock and the operating clock using the synchronization message, and accepting this difference into the synchronization message as additional information.