Data Synchronization Phase Compression for Unreliable Networks
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current data synchronization systems between desktop and handheld devices are inefficient, particularly in wireless networks with poor coverage, as they require multiple messages and may fail due to unreliable connections, leading to incomplete or corrupted data synchronization.
Innovation Solution
Implementing synchronization phase compression, deferred identifier map transmission, and sync anchor checkpoints to reduce the number of messages, enhance robustness, and allow for incremental progress in synchronization, even over unreliable connections, by compressing negotiation and pull phases into a single protocol message and deferring identifier map transmission to subsequent sessions, and using sync anchors to atomize synchronization sessions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional multi-message synchronization protocol is used, then data synchronization can be achieved, but network traffic increases and synchronization reliability decreases in poor network conditions
Solution Approach 1:
The patent merges the negotiation phase and pull phase into a single protocol message exchange. Instead of using multiple separate messages for negotiation and data transfer, the system combines these operations so that data can be pulled during the same message exchange that establishes synchronization parameters, thereby reducing network traffic and improving reliability in poor network conditions.
Solution Approach 2:
The patent segments the identifier map transmission from the main synchronization flow by deferring it to subsequent sessions. This allows the core synchronization data to be transmitted with minimal overhead, while identifier mappings are handled separately in later communication sessions, reducing the immediate network burden and improving synchronization reliability.
2Productivity
If multiple protocol messages are used for synchronization, then complete data exchange can be achieved, but synchronization time increases and productivity decreases
Solution Approach 1:
By merging negotiation and pull phases into a single message exchange, the patent eliminates the sequential waiting time between negotiation completion and data transfer initiation. This parallel execution approach significantly reduces total synchronization time and improves productivity.
Solution Approach 2:
The system performs preliminary actions by establishing synchronization parameters and initiating data pull within the same message exchange, rather than completing all negotiations before starting data transfer. This overlapping of operations reduces idle time and accelerates the overall synchronization process.
3Loss of information
If identifier map is transmitted immediately, then data mapping accuracy is ensured, but network traffic increases and resource waste occurs
Solution Approach 1:
The patent extracts the identifier map transmission from the primary synchronization message flow and defers it to subsequent sessions. This allows the essential synchronization data to be transmitted with minimal overhead, while the identifier mappings—though important for data mapping accuracy—are handled in a separate, resource-efficient manner.
Solution Approach 2:
The system performs the critical data synchronization first, establishing accurate mappings through the main protocol exchange. The identifier map is then transmitted in subsequent sessions to complete the mapping process, ensuring data accuracy is maintained while optimizing resource usage by avoiding premature transmission of large identifier datasets.
4Reliability
If synchronization is performed in a single session, then data consistency can be maintained, but the system cannot handle poor network conditions or interruptions
Solution Approach 1:
The patent segments the synchronization process into distinct phases (negotiation, pull, and deferred identifier map transmission) that can be completed in a single session but are structured to allow clean interruption and resumption points. This modular structure enables the system to handle network interruptions by resuming from the last successful phase without requiring complete re-synchronization.
Solution Approach 2:
The system performs preliminary synchronization of critical data in the main session, establishing a consistent state before deferred operations like identifier map transmission. This preliminary action ensures that even if the session is interrupted, the core data consistency is maintained, and the system can resume operations without corrupting the datastore.
Data Source
AI summary
Synchronization architectures, methods, systems, and computer readable media are described. In one embodiment, a synchronization session is initiated between a first data processing system and a second data processing system. First data, representing changes to a first data class, is transmitted from the first data processing system to the second data processing system. Second data, representing changes to a second data class, is transmitted from the first data processing system to the second data processing system. Transmission of the second data begins before transmission of the first data is complete. The first data may comprise structured data such as contacts information, to do information, calendar information, or web browsing bookmarks.