Timestamp Alignment Across Distributed Computing Devices

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Timestamps recorded across multiple computing devices are often inconsistent due to network latency and non-synchronized server clocks, leading to inaccurate transaction time evaluations.

Innovation Solution

A method and system for aligning timestamps by creating a data structure that matches identifiers and associates timestamps across multiple servers, using a management server to aggregate transaction fragments and align timestamps based on activity identifiers and communication types, with adjustments for clock misalignments and network latency.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If timestamps are recorded independently on each server, then each server can track its own transaction activities, but the timestamps become inconsistent across multiple servers due to network latency and non-synchronized clocks

Engineering Contradiction:
Improvetimestamp accuracyVSAvoidtimestamp consistency
Core Design Contradiction:
Measurement precisionVSReliability

Solution Approach 1:

The patent introduces a management server as an intermediary that receives transaction fragments from multiple computing devices, aligns timestamps using activity identifiers and communication types, and creates a unified data structure. This mediator resolves the timestamp inconsistency problem by centralizing the alignment process while preserving the distributed nature of transaction processing.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent segments transactions into transaction fragments that are distributed across multiple computing devices, each maintaining local timestamp records. By dividing the transaction into manageable fragments with activity identifiers, the system enables subsequent alignment of timestamps from different sources while maintaining the benefits of distributed processing.

Inventive Principle:
Principle #1Segmentation

2Reliability

If a centralized system aligns timestamps from multiple servers, then timestamp consistency is improved, but system complexity increases due to additional processing and coordination requirements

Engineering Contradiction:
Improvetimestamp consistencyVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent applies preliminary action by embedding activity identifiers and communication type information in transaction fragments before they are processed by the management server. This pre-preparation of alignment data reduces the complexity of the timestamp alignment process, as the management server receives pre-structured information that facilitates automated alignment without requiring complex real-time coordination.

Inventive Principle:
Principle #10Preliminary action

3Loss of information

If transaction fragments are aggregated from multiple sources, then comprehensive transaction tracking is achieved, but data processing time increases due to matching and alignment operations

Engineering Contradiction:
Improvetransaction information completenessVSAvoidprocessing time
Core Design Contradiction:
Loss of informationVSLoss of time

Solution Approach 1:

The patent changes the parameter of transaction fragment structure by incorporating activity identifiers and communication type metadata. This parameter change enables efficient matching and alignment operations, as the management server can use these identifiers to quickly correlate fragments from different sources without requiring exhaustive comparison of all transaction data, thereby reducing processing time while maintaining completeness.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS10474185B2Timestamp alignment across a plurality of computing devices
Publication Date: 2019.11.12 RED HAT INC
  • US10474185B2 patent drawing
  • US10474185B2 patent drawing
  • US10474185B2 patent drawing

AI summary

Methods, systems, and computer program products are included for aligning timestamps of activities. A method includes receiving a first entry from a first server, the first entry corresponding to an activity, wherein the first entry includes a first timestamp corresponding to the activity. The method further includes receiving a second entry from a second serve, the second entry including a second entry corresponding to the activity, wherein the second entry includes a second timestamp corresponding to the activity. The method further includes determining an aligned timestamp of the activity by adjusting the first timestamp or the second timestamp by an offset.