Timing Synchronization via Event Time Embedding in Data Packets

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Computer servers face challenges in maintaining accurate time-of-day synchronization due to processing capacity limitations and variability in transmission times, leading to imprecise timestamp reflections in packets transmitted between systems.

Innovation Solution

A method and system for timing synchronization between a base computing system and a remote computing system, where packets are sent with embedded send and receive event times, allowing for the calculation of transmission time values using recorded send and receive event times, thereby enhancing timestamp accuracy across systems.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If time stamps are exchanged between computer servers to determine time sequence, then time-of-day synchronization is achieved, but the send time stamp value may not accurately indicate the actual transmission time due to processing delays and variable transmission periods

Engineering Contradiction:
Improvetimestamp accuracyVSAvoidtransmission delay
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The patent applies preliminary action by recording the send event time at the base computing system before the packet is actually transmitted, and recording the receive event time at the remote computing system when the packet is received. These timestamps are embedded in the packet payload, ensuring that the time measurement is captured at the precise moments of send and receive events, not at arbitrary processing points.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent implements feedback by having the remote computing system send back a response packet containing its receive event time to the base computing system. This allows the base computing system to calculate the actual transmission time by comparing the recorded send event time with the received receive event time, thereby obtaining accurate transmission timing information for synchronization purposes.

Inventive Principle:
Principle #23Feedback

2Productivity

If computer servers operate near maximum processing capacity, then productivity is maximized, but the ability to immediately generate and transmit timestamp messages deteriorates

Engineering Contradiction:
Improveprocessing capacityVSAvoidtimestamp generation timing
Core Design Contradiction:
ProductivityVSMeasurement precision

Solution Approach 1:

The patent applies self-service by having the base computing system automatically record the send event time when the base packet is transmitted, and having the remote computing system automatically record the receive event time when the packet is received. The systems use their own internal event time recording mechanisms rather than relying on external timestamp generation, eliminating the need for additional processing overhead for timestamp management.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent uses preliminary action by pre-recording the send event time at the base computing system before transmission occurs, and the receive event time at the remote system upon reception. This ensures that timestamp information is captured at the exact moments needed without requiring real-time processing delays, allowing the systems to operate at maximum capacity while maintaining precise timing measurements.

Inventive Principle:
Principle #10Preliminary action

3Adaptability or versatility

If transmission time period varies between sending and receiving packets, then network flexibility is maintained, but timing synchronization accuracy deteriorates

Engineering Contradiction:
Improvetransmission flexibilityVSAvoidtiming synchronization
Core Design Contradiction:
Adaptability or versatilityVSMeasurement precision

Solution Approach 1:

The patent applies preliminary action by recording the send event time at the base computing system before the packet is transmitted and recording the receive event time at the remote computing system when the packet is received. By capturing timestamps at these specific event points rather than using fixed periodic intervals, the system can accurately measure transmission time even when transmission periods vary, maintaining both flexibility and synchronization accuracy.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent implements feedback by having the remote computing system return its receive event time to the base computing system in a response packet. This feedback mechanism allows the base computing system to calculate the actual transmission time for each individual packet, accommodating variable transmission periods while maintaining precise timing synchronization through per-packet measurement rather than assuming fixed intervals.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS11271838B2Timing synchronization
Publication Date: 2022.03.08 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US11271838B2 patent drawing
  • US11271838B2 patent drawing
  • US11271838B2 patent drawing

AI summary

Embodiments include method, systems and computer program products for timing synchronization. Aspects include sending to a remote system a first base packet, the first base packet is sent at a first send event time and then recording the first send event time in a memory. Aspects also include sending to the remote system a second base packet, wherein the payload comprises instructions for the remote computing system and receiving a first remote packet, wherein a payload comprises a first received time indicating a time the first base packet was received. Aspects then include recording the first received time and recording a second received time, wherein the second received time indicates a time the first remote packet was received by the base system. Aspects include receiving a second remote packet, wherein a payload comprises a second sent time indicating a time the first remote packet was sent.