Time Addressable Storage for Data Reconciliation

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing file systems and database systems lack the ability to efficiently traverse and reconcile discrepancies between a data environment and a live environment over time, leading to inconsistencies that can propagate and become difficult to manage.

Innovation Solution

A method and system that allow data objects to be moved through time by determining a point-in-time, retrieving relevant events from a journal, and applying inverse events to revert or progress data objects to a selected state, enabling time traversal and reconciliation of discrepancies.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional file systems and database systems are used to store and manage data, then data can be stored efficiently, but the system lacks the ability to traverse and reconcile discrepancies between data environment and live environment over time

Engineering Contradiction:

Improvedata consistencyVSAvoidtime traversal capability

Core Design Contradiction:

ReliabilityVSAdaptability or versatility

Solution Approach 1:

The system performs preliminary actions by continuously logging all data modification events in a journal with timestamps before discrepancies can propagate. This preemptive recording enables later time traversal and reconciliation without requiring real-time detection mechanisms

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

A time-traversal interface acts as an intermediary between the data environment and live environment, allowing users to query and reconcile discrepancies at specific points in time without disrupting normal operations. The journal serves as a mediator that bridges past and present states

Inventive Principle:

Principle #24Intermediary (Mediator)

2Reliability

If the system monitors and detects discrepancies immediately, then data consistency can be maintained, but this requires complex real-time monitoring mechanisms that increase system complexity

Engineering Contradiction:

Improvediscrepancy detectionVSAvoidmonitoring system complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The monitoring function is extracted from the core data management system and separated into a passive journaling mechanism. The journal independently records events without requiring active monitoring logic, reducing system complexity while maintaining detection capability

Inventive Principle:

Principle #2Taking out (Extraction)

Solution Approach 2:

The journaling system operates autonomously, automatically recording all data modifications without requiring external monitoring or intervention. The system self-documented its state changes, eliminating the need for complex monitoring infrastructure

Inventive Principle:

Principle #25Self-service

3Loss of time

If backup and restore mechanisms are used to retrieve earlier data states, then data recovery is possible, but the process is time-consuming and cannot enable bidirectional time traversal

Engineering Contradiction:

Improvedata recovery timeVSAvoidtime traversal flexibility

Core Design Contradiction:

Loss of timeVSEase of operation

Solution Approach 1:

Instead of performing recovery actions when needed, the system preliminarily records all state changes in a journal with timestamps. This pre-recording enables instant retrieval of any past state by simply querying the journal, eliminating recovery time delays

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The system transforms static backup points into dynamic, continuously accessible time states. Users can traverse forward and backward through time by querying different timestamps in the journal, enabling flexible bidirectional navigation rather than fixed restore points

Inventive Principle:

Principle #15Dynamics

4Adaptability or versatility

If the system stores complete history of all data changes, then full time traversal is enabled, but storage requirements increase significantly

Engineering Contradiction:

Improvetime traversal capabilityVSAvoidstorage space

Core Design Contradiction:

Adaptability or versatilityVSQuantity of substance

Solution Approach 1:

The complete data history is segmented into individual event records in the journal, each containing only the essential modification information. This segmentation allows selective storage and retrieval of specific changes rather than duplicating entire data states, reducing storage requirements

Inventive Principle:

Principle #1Segmentation

Data Source

PatentUS7814367B1Method and system for time addressable storage

Publication Date: 2010.10.12 OPEN TEXT CORPORATION

AI summary

Method and system for allowing temporal navigation or time travel of data or data object across time are disclosed. In one embodiment, events that affected data objects are retrieved and inversed to revert the data objects back to a selected point-in-time, forward events are applied to move data objects to forward point-in-time. A sliding bar or a time dial allows a user to move data objects back and forward in time. Events that are applied may be a selected subset of events, altered events, new events, or events generated synthetically or any combinations thereof, for instance, to create counterfactual history.