Sync Anchor Data Synchronization Change Log Management
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional data synchronization between a server and a client, particularly in mobile terminals, often results in slow sync processes due to frequent transmission of whole data when last anchors or change logs are different, leading to synchronization delays.
Innovation Solution
Implementing a system where the server and client share a Sync Anchor field for each data item and manage changes using a database, allowing for efficient generation and transmission of change logs based on anchor comparisons, thereby reducing the need for full data transmission.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the client transmits whole data to the server for synchronization, then data synchronization reliability is improved, but synchronization speed deteriorates
Solution Approach 1:
The patent segments data transmission by introducing change log management that transmits only changed data records instead of whole data. The change log contains only the differences between old and new data, enabling selective transmission of modified records while maintaining synchronization reliability.
Solution Approach 2:
The patent implements preliminary action by pre-establishing change log management mechanisms and anchor points before synchronization occurs. The system continuously tracks changes and prepares change logs in advance, so when synchronization is needed, only the pre-recorded changes need to be transmitted rather than performing full data comparison.
2Adaptability or versatility
If the server and client separately manage data, sync anchors, and change logs, then data synchronization flexibility is improved, but device complexity increases
Solution Approach 1:
The patent merges the management of sync anchors and change logs into an integrated change log management system. Instead of separately managing these components, the system combines them into a unified structure that tracks all changes and maintains anchor points simultaneously, reducing overall system complexity.
Solution Approach 2:
The change log management system serves multiple functions simultaneously: it tracks data changes, manages synchronization anchors, determines what needs to be transmitted, and maintains synchronization state. This multi-functional approach reduces the need for separate management mechanisms.
Data Source
AI summary
A data synchronizing method between a server and a client is provided. The server and the client manage database changed after a previous synchronization of data shared by them. The database includes a sync anchor field for each data item. When a sync session is initiated upon request of the client, a last anchor is detected from the database stored in the client and a last anchor from the database stored in the server. The last anchor of the client is compared with the last anchor of the server. A client change log and a server change log are generated according to a comparison result based on a database change that occurred after the last anchor of client or server when the last anchor of the client is identical to the last anchor of the server. The databases are updated according to the client change log and the server change log.