Blockchain-like Synchronization Blocks for File Metadata
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing file/folder synchronization methods face issues with scalability, reliability, and incompatibility when replicating contents across a large number of devices, leading to inefficient message handling and potential errors.
Innovation Solution
A synchronization structure using a blockchain-like data structure is implemented, where changes are tracked in synchronization blocks, allowing for efficient communication of file metadata and updates between devices, reducing the number of messages required and enhancing reliability.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional file synchronization methods are used to replicate contents across a large number of devices, then the synchronization can be performed, but the number of messages becomes very large and reliability issues occur
Solution Approach 1:
The patent segments the synchronization process into two distinct phases: a metadata propagation phase where only change information is transmitted, and a data transfer phase where actual file contents are sent. This segmentation reduces the number of messages by avoiding redundant data transmissions and improves reliability by separating critical metadata synchronization from bulk data operations.
Solution Approach 2:
The patent performs preliminary actions by first propagating metadata changes to all devices before initiating actual data transfers. Change information including file attributes, timestamps, and modification details is transmitted beforehand, allowing devices to prepare for synchronization and reducing the overall message count during subsequent data transfer operations.
2Productivity
If traditional synchronization methods are used, then file replication can occur, but message handling becomes inefficient and errors increase
Solution Approach 1:
The patent implements feedback mechanisms where devices send acknowledgment messages confirming receipt of metadata changes and data transfers. This feedback loop allows the synchronization system to track which devices have received which information, enabling error detection and correction while improving overall efficiency through selective retransmission of only failed messages.
Solution Approach 2:
The patent extracts critical synchronization information into separate metadata structures that are propagated independently from file data. By taking out change information and transmitting it separately, the system reduces message overhead and improves handling efficiency while maintaining reliability through focused error correction on metadata before data transfer.
3Adaptability or versatility
If existing synchronization implementations are used, then basic file replication works, but scalability to large numbers of devices is poor
Solution Approach 1:
The patent segments synchronization operations into metadata propagation and data transfer phases, allowing the system to scale by handling device connections and metadata separately from bulk data operations. This segmentation reduces message handling complexity as devices can be added without proportionally increasing the complexity of individual synchronization operations.
Solution Approach 2:
The patent creates a universal synchronization protocol that handles multiple operations (file creation, modification, deletion, attribute changes) through a unified metadata structure and standardized message formats. This multi-functionality approach improves scalability by allowing the same message handling mechanisms to work across diverse synchronization scenarios and large numbers of devices.
Data Source
AI summary
A synchronization structure that indicates changes to files that are to be synchronized is created. The synchronization structure is stored as a series of synchronization blocks. A first synchronization message is received from a communication device. The first synchronization message includes a next block number. A second synchronization message is sent to the communication device. The second synchronization message comprises one or more synchronization blocks that are identified based on the next block number. A third synchronization message is received from the communication device. The third synchronization message requests a number of files to be synchronized. The number of files to be synchronized are sent to the communication device.