Data Synchronization via Vector Comparison and Transaction Logs

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In complex network infrastructures, efficiently and reliably synchronizing data among control elements is challenging, especially in scenarios where network failures lead to data inconsistencies across separated network cores.

Innovation Solution

A method and system for data synchronization that involves connecting computers via a network connection, receiving and comparing remote and local tables, updating tables based on transaction logs, and managing conflict flags and alarms to ensure data consistency across peer computers.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If data synchronization is performed frequently among control elements, then data consistency is improved, but network traffic and processing overhead increase

Engineering Contradiction:
Improvedata consistencyVSAvoidnetwork traffic
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The patent extracts only the essential synchronization information (vectors and transaction logs) from the complete data sets, transmitting only these critical components over the network. This selective extraction minimizes network traffic while ensuring data consistency by capturing the minimal necessary information for synchronization.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The system performs preliminary actions by maintaining local transaction logs and vectors that record all data changes before synchronization occurs. This preliminary tracking allows the system to determine what needs to be synchronized and reduces the amount of data that must be transmitted, as only changes need to be propagated rather than complete data sets.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If comprehensive data comparison is performed to ensure consistency, then data integrity is improved, but processing time increases

Engineering Contradiction:
Improvedata integrityVSAvoidprocessing time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent replaces comprehensive mechanical data comparison with a more efficient mechanism based on vector comparison and transaction log analysis. Instead of comparing entire data sets, the system uses vectors (compact data structures) and transaction logs to identify changes, significantly reducing processing time while maintaining data integrity through the mathematical properties of vectors and systematic change tracking.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

Solution Approach 2:

The system changes the parameters of data representation by using vectors instead of complete data sets for comparison. This parameter transformation allows for much faster comparison operations while maintaining the ability to detect all necessary changes, as vectors provide a compact mathematical representation that enables efficient equality and difference detection.

Inventive Principle:
Principle #35Parameter changes

3Reliability

If redundancy is implemented at higher levels of management infrastructure, then system availability is improved, but data synchronization complexity increases

Engineering Contradiction:
Improvesystem availabilityVSAvoidsynchronization complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments the synchronization process into distinct, manageable components: vector comparison, transaction log analysis, change detection, and data propagation. This segmentation reduces synchronization complexity by breaking down the overall task into smaller, independent operations that can be executed systematically, while redundancy at higher levels ensures system availability through failover capabilities.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS10866965B2Data replicating systems and data replicating methods
Publication Date: 2020.12.15 NECTAR HLDG
  • US10866965B2 patent drawing
  • US10866965B2 patent drawing
  • US10866965B2 patent drawing

AI summary

Methods and systems for synchronizing data may enable a computer to synchronize data by connecting to a peer computer via a network connection. The computer may receive a remote table from the peer computer, wherein the remote table comprises an object comprising a vector. The computer may determine whether the object is present in a local table. When the object is present in the local table, the computer may determine whether the vector in the remote table and the vector in the local table match. When the vectors do not match, the computer may determine whether a record of a change to the object is present in a local transaction log. The computer may receive data from the peer computer indicating whether a record of a change to the object is present in a remote transaction log when the vectors do not match. The computer may replace the vector in the local table with the vector in the remote table and record a change to the object in the local transaction log when the record of the change to the object in the local transaction log is less recent than the record of the change to the object in the remote transaction log.