Heterogeneous Database Synchronization via Version Number Management
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Data consistency between heterogeneous databases, such as embedded databases on terminal devices and distributed databases on cloud servers, is challenging due to differences in structure and environment, leading to inconsistencies during synchronization.
Innovation Solution
A data synchronization method that modifies storage formats on both terminal and cloud devices using primary key, attribute, version number, and synchronization status fields to ensure data consistency, with version number management and synchronization status management mechanisms to handle operations like insertion, update, and deletion.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If data synchronization is performed between heterogeneous databases (embedded database on terminal and distributed database on cloud), then data consistency is maintained, but the complexity of the synchronization mechanism increases due to structural and environmental differences
Solution Approach 1:
The patent changes the parameter of data representation by introducing a standardized storage format with specific fields (primary key, attribute, version number, synchronization status) that can be universally applied across heterogeneous databases. This parameter standardization allows consistent data synchronization between embedded and distributed databases without requiring complex conversion mechanisms.
Solution Approach 2:
The patent introduces an intermediary synchronization mechanism that uses a unified data format as a mediator between the terminal's embedded database and the cloud's distributed database. This intermediary format acts as a common language that bridges the structural differences between heterogeneous databases, simplifying the synchronization process.
2Reliability
If version number management is implemented to handle concurrent modifications, then data consistency is ensured, but the synchronization process time increases
Solution Approach 1:
The patent applies preliminary action by pre-assigning version numbers to data objects before synchronization occurs. Each data object is equipped with a version number field that is prepared in advance, allowing the system to quickly detect and resolve conflicts during synchronization without requiring complex real-time analysis, thus reducing synchronization time while maintaining consistency.
Solution Approach 2:
The patent implements feedback through the version number field that provides immediate information about the state of data objects. When synchronization occurs, the version numbers serve as feedback signals that indicate whether conflicts exist and what actions are needed, enabling rapid decision-making and reducing the time required for conflict resolution.
3Reliability
If comprehensive synchronization status tracking is performed for all data objects, then data consistency is maintained, but the communication overhead between terminal and cloud increases
Solution Approach 1:
The patent extracts only the essential synchronization information (synchronization status field and version number) from the complete data objects and transmits only these extracted elements during synchronization. This selective extraction allows the system to track the synchronization status of all data objects without transmitting the entire data set, significantly reducing communication overhead while maintaining comprehensive tracking capability.
Solution Approach 2:
The patent changes the parameter of data transmission by converting comprehensive data object transmissions into compact parameter-based transmissions. Instead of syncing entire data objects, the system transmits only the synchronization status and version number parameters, which are sufficient to maintain consistency while minimizing communication data volume.
Data Source
AI summary
A data synchronization method applied to data synchronization between heterogeneous databases includes a terminal device that records a primary key, attribute information, a version number, and a synchronization status of a data object using a first storage format, and a cloud device that records a primary key, attribute information, and a version number of a data object using a second storage format such that the terminal device and the cloud device implement data synchronization between the heterogeneous databases based on the storage formats and version numbers.