Multi-Device Synchronization Using Truth Table and Canonical Data
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing synchronization methods involve numerous redundant comparison steps and rely on device system clocks, which can be modified intentionally or malevolently, leading to inefficient and unreliable data synchronization between devices.
Innovation Solution
The method involves storing indications of devices involved in synchronization events and logging data changes, using an Administration Table and Truth Table to optimize comparison steps and apply data changes efficiently, independent of device clock modifications.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If traditional synchronization methods are used, then data synchronization between devices is achieved, but a large number of redundant comparison steps are involved
Solution Approach 1:
The patent applies preliminary action by pre-establishing a canonical format for data and pre-creating a Truth Table that records the state of data across all devices before synchronization begins. This allows the synchronization engine to efficiently compare only necessary data elements against the pre-computed Truth Table rather than performing exhaustive comparisons between all devices, thereby reducing redundant comparison steps and improving synchronization efficiency.
Solution Approach 2:
The patent uses copying by creating a canonical formatted copy of data from each device and storing it in the Truth Table. This canonical copy serves as a reference standard that all devices must conform to during synchronization. By working with copies in a standardized format rather than directly comparing original data between devices, the system reduces the complexity and number of comparison steps required.
2Reliability
If device system clocks are used for synchronization, then synchronization timing is determined, but the clocks can be modified intentionally or malevolently leading to unreliable synchronization
Solution Approach 1:
The patent introduces an intermediary mechanism in the form of a synchronization engine that mediates between devices and their system clocks. Instead of directly relying on device clocks for synchronization decisions, the engine uses a canonical format and Truth Table as intermediaries to determine data states and synchronization requirements. This intermediary layer isolates the synchronization process from clock manipulation vulnerabilities while maintaining reliable synchronization based on actual data changes.
3Reliability
If all devices are synchronized serially with the Truth Table, then complete synchronization is achieved, but the process becomes complex and time-consuming
Solution Approach 1:
The patent applies segmentation by dividing the synchronization process into distinct phases: first, each device is synchronized individually with the Truth Table to establish a consistent state; second, the synchronized devices are then used to update each other based on their canonical formatted data. This segmentation allows the complex multi-device synchronization to be broken down into manageable steps, reducing overall complexity while maintaining completeness.
Data Source
AI summary
Hitherto synchronization of a number of devices has involved a large number of comparison steps between actual data or changes in data. Such comparison has potentially involved extensive redundant comparison steps. Another problem with existing synchronization methods is that such synchronization has been effected based upon the systems clocks defined by the devices. Those system clocks can be modified either intentionally or malevolently with disastrous consequences for subsequent synchronization of the devices. Accordingly, the present invention relates to a method of synchronization between three or more devices, the method involves: storing an indication of the device or devices involved in each synchronization event; storing data changes received during a current synchronization event together with the device submitting those changes; and applying the data changes subsequent to the stored synchronization event for the or each device.