Communication Server Synchronization With Peer-Validated Time References

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing timestamping methods in virtual data-spaces rely on a single time reference, which can be compromised or faulty, leading to inaccurate or inoperative synchronization, especially in multi-participant contexts, and require costly trusted third parties for security, complicating implementation.

Innovation Solution

A method for synchronizing communication servers involves selecting a primary server through an algorithm, transmitting an initialization message with time information, and validating this information through acknowledgement messages from secondary servers, ensuring reliable time reference determination and reducing the risk of malicious interference.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Device complexity

If a single time reference is used for all connectors, then synchronization is simplified, but the system becomes vulnerable to single-point failures and compromised security

Engineering Contradiction:
Improvesynchronization mechanism complexityVSAvoidsynchronization reliability
Core Design Contradiction:
Device complexityVSReliability

Solution Approach 1:

The patent divides the single time reference system into multiple independent time references, one for each connector. Each connector maintains its own local time reference instead of relying on a centralized master clock, thereby eliminating the single-point failure vulnerability while preserving synchronization simplicity through peer-to-peer validation mechanisms.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent changes the fundamental parameter of time reference architecture from centralized to distributed. By allowing each connector to use its own local time reference and validating timestamps through cryptographic proof-of-work mechanisms, the system achieves both simplicity and reliability simultaneously.

Inventive Principle:
Principle #35Parameter changes

2Reliability

If a trusted third party is introduced to secure time reference, then security is improved, but implementation cost and complexity increase

Engineering Contradiction:
Improvetime reference securityVSAvoidimplementation complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent enables connectors to self-validate time references through cryptographic proof-of-work mechanisms without requiring external trusted third parties. Each connector independently verifies the validity of time references using distributed validation, eliminating the need for costly and complex trusted intermediary infrastructure.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent replaces the traditional trusted third-party intermediary with a distributed cryptographic validation mechanism. Instead of relying on a central authority, the system uses proof-of-work based validation where any connector can verify time reference authenticity through cryptographic proofs, reducing implementation complexity and cost.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS12418350B2Method for synchronizing a plurality of communication servers, and corresponding computer devices and programs
Publication Date: 2025.09.16 ORANGE SA
  • US12418350B2 patent drawing
  • US12418350B2 patent drawing
  • US12418350B2 patent drawing

AI summary

A method for synchronizing a plurality of servers of a communication network, which are capable of exchanging time-stamped data using a time reference. The method is implemented by a primary server of the plurality and includes: transmitting to the other servers, called secondary servers, an initialization message containing an identifier of the primary server, a data item resulting from execution of an algorithm for selecting the primary server from the plurality of servers, and a piece of transmission time information on the initialization message; receiving from at least one secondary server a message acknowledging the transmitted initialization message; and validating a synchronization challenge comprising a difference between a recorded transmission time reference and the piece of transmission time information on the initialization message. The piece of transmission time information replaces the recorded time reference for the time-stamping of the data exchanged between the servers once the validation is complete.