Data Management Node Using Logical Clock Markers

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In distributed processing systems with eventual consistency, it is impossible to identify when data values corresponding to multiple keys have been fixed at a certain time point due to the continuous advancement of logical clock values.

Innovation Solution

A data management method that involves registering history elements and markers with logical clock values, allowing identification of data values at specific times by detecting when the system's fixed clock value exceeds the marker's logical clock value, enabling the retrieval of data values from history elements with clock values equal to or less than the marker's value.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If logical clock values continuously advance in a distributed processing system, then the system maintains eventual consistency, but it becomes impossible to identify when data values have been fixed at a certain time point

Engineering Contradiction:
Improvedata consistencyVSAvoidtime point identification
Core Design Contradiction:
ReliabilityVSLoss of information

Solution Approach 1:

The patent segments the continuous logical clock space by introducing markers at specific logical clock values. These markers divide the continuous time flow into discrete checkpoints, allowing the system to identify specific time points while maintaining continuous clock advancement. Each marker records a snapshot of data values at its associated logical clock value, enabling retrospective identification of fixed data states.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent performs preliminary action by pre-registering markers at specific logical clock values before data queries are made. These markers are placed in advance at predetermined logical clock points, creating a framework of known time references that enable later identification of data values at those specific time points without disrupting the continuous operation of the distributed system.

Inventive Principle:
Principle #10Preliminary action

2Measurement precision

If markers are registered for every reference request to enable time-specific data retrieval, then accurate time point identification is achieved, but system complexity increases

Engineering Contradiction:
Improvetime point identification accuracyVSAvoiddata management complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The patent applies local quality by making markers optional rather than universal. Instead of registering markers for every possible reference request, the system selectively places markers at logically significant points where time-specific data retrieval is actually needed. This localized approach maintains measurement precision where required while avoiding unnecessary complexity in other areas of the system.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The marker structure serves as an intermediary between the continuous logical clock system and discrete time-point queries. Rather than modifying the fundamental clock mechanism or creating complex query processing, the markers act as intermediate reference points that bridge the gap between continuous time advancement and the need for discrete time-specific data access.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS8756343B2Data management method and node apparatus
Publication Date: 2014.06.17 FUJITSU LTD
  • US8756343B2 patent drawing
  • US8756343B2 patent drawing
  • US8756343B2 patent drawing

AI summary

When receiving a predetermined command regarding an assigned key to a node apparatus, a history element is registered, which includes a first Logical Clock Value (LCV) at a first time the predetermined command was received, and a data value at a second time represented by the first LCV. When receiving a reference request to reference a data value at a third time represented by a specific LCV, a first marker is registered, which includes, as the specific LCV, a second LCV at a time when the reference request was received or a third LCV designated by the reference request, and further includes information concerning the reference request. When a fixed LCV in a system becomes not less than the specific LCV, a data value corresponding to the assigned key at the third time is identified from the history elements including first LCVs that are not greater than the specific LCV.