Document Object Synchronization Using Independent Descriptor Resync
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing cloud-based file synchronization protocols struggle with synchronization conflicts and inefficiencies when handling user-modified document objects across multiple devices with different data centers, leading to data loss and inconsistent document versions.
Innovation Solution
The method involves structuring document objects into a content file and an object descriptor file, allowing independent synchronization of these files with a cloud, using timestamps to detect and resolve conflicts, and ensuring consistent document versions across devices.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If cloud-based file synchronization protocols are used to synchronize documents across multiple devices, then document consistency is maintained, but synchronization conflicts occur when different devices modify the same document simultaneously
Solution Approach 1:
The document is segmented into multiple objects, each with its own version history tracked independently. This allows parallel modifications to different objects without conflict, while maintaining overall document consistency through the versioning system.
Solution Approach 2:
Version information is preliminarily established for each document object before modifications occur. This pre-established versioning framework enables automatic conflict resolution by comparing version identifiers, eliminating the need for complex real-time conflict detection and resolution protocols.
2Reliability
If entire files are synchronized whenever any modification occurs, then all modifications are captured, but network bandwidth is wasted transmitting unchanged content
Solution Approach 1:
Only the modified document objects are extracted and transmitted for synchronization, rather than the entire file. The system identifies and separates changed objects from unchanged ones, sending only the necessary updates over the network, thus conserving bandwidth while ensuring all modifications are captured.
Solution Approach 2:
The synchronization protocol changes from file-level to object-level granularity. By tracking modifications at the object level and using version parameters to identify changes, the system transmits only minimal necessary data, reducing network energy consumption while maintaining complete modification detection.
3Productivity
If different data centers use different synchronization protocols, then each center optimizes its own system, but conflicts arise when devices switch between data centers
Solution Approach 1:
The versioning system is designed with universal version identifiers that work across different data centers and protocols. Each document object carries version information that can be compared and reconciled regardless of which data center generated it, enabling seamless cross-data center synchronization without requiring protocol conversion.
Data Source
AI summary
The invention relates to a method implemented by a first device (DV1) cooperating with a cloud (CL) of at least one server for resolving a synchronization conflict over different versions of a document object comprising at least one content file and one object descriptor file (ODF1). The method comprising obtaining a first version of the document object; performing a first synchronization phase comprising sending the first version (ODF1) of the object descriptor file, independently of the first version of the content file, to the cloud (CL); performing a second synchronization phase for resolving the conflict by re-sending the first version (ODF1) of the object descriptor file of the first device (DV1) to the cloud (CL); performing a third synchronization phase subsequent to the second synchronization phase, comprising sending the first version of the content file to the cloud (CL) for storing said first version of content file.