Offline Data Synchronization via Temporary Client Key Mapping
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional enterprise systems face issues with non-persistent data when data is created offline and subsequently changed before synchronization with the server, resulting in different backend keys for the original and changed data, leading to data inconsistencies.
Innovation Solution
A framework that generates and processes offline change data on a client device, determining the change data type to associate either a new unique client key or an existing backend key, and stores this information in a synchronization queue for later synchronization with the server, ensuring data persistence by mapping client keys to backend keys.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If data is created offline and subsequently changed before synchronization, then offline data processing capability is improved, but data persistence is worsened due to different backend keys being generated
Solution Approach 1:
The system performs preliminary actions by generating a temporary client key for offline data before synchronization occurs. This client key is assigned during offline creation and modification operations, allowing the data to be persisted locally with a stable identifier. When synchronization happens later, the system then maps this pre-generated client key to the final backend key, ensuring the data maintains consistent identity throughout the offline-online transition cycle.
Solution Approach 2:
The patent introduces a key mapping mechanism that acts as an intermediary between client keys and backend keys. The key mapping table stores associations between temporary client-generated keys and permanent backend keys, allowing the system to bridge the gap between offline data operations (which need immediate key assignment) and online synchronization (which requires backend key consistency). This intermediary layer resolves the contradiction by allowing different keys at different stages while maintaining data persistence.
2Adaptability or versatility
If separate backend keys are generated for original and changed offline data, then data modification capability is improved, but data consistency is worsened
Solution Approach 1:
The system assigns a preliminary client key to data at the time of offline creation, allowing subsequent modifications to reference this same client key. This preliminary key assignment enables multiple modifications to be tracked under a single identifier during offline operations. The preliminary action of key assignment ensures that even as data changes, its identity remains consistent through the client key, which is later mapped to a single backend key upon synchronization.
Solution Approach 2:
The key mapping table serves as an intermediary that resolves the consistency issue between multiple modifications and single data identity. When data is modified offline, the system continues to use the same client key rather than generating new ones. During synchronization, the key mapping mechanism ensures that all modifications associated with that client key are consolidated under a single backend key, maintaining data consistency while allowing flexible offline modifications.
3Measurement precision
If a key mapping mechanism is implemented to associate client keys with backend keys, then data synchronization accuracy is improved, but system complexity is worsened
Solution Approach 1:
The patent implements a key mapping table as an intermediary data structure that stores associations between client keys and backend keys. This mapping mechanism improves synchronization accuracy by ensuring that data created or modified offline with a client key is correctly associated with the corresponding backend key after synchronization. The mapping table acts as a bridge that resolves key mismatches and ensures data consistency across offline and online environments, justifying the added complexity through improved synchronization reliability.
Solution Approach 2:
The key mapping mechanism is designed to be self-managing through automated operations. When data is synchronized from offline to online, the system automatically creates or updates the key mapping entries without requiring manual intervention. The mapping table self-updates as new data is synchronized, and the system automatically resolves key associations, reducing the operational complexity despite the increased structural complexity of the mapping infrastructure.
Data Source
AI summary
An enterprise system which facilitates synchronization of offline data. Offline data created during an offline session or sessions (collectively an offline session) prior to synchronization is assigned a temporary key. Changes of offline data created during an offline session is assigned the temporary key of the data to which the change is associated. The temporary key is mapped to a new created backend key and stored in a mapping table. Using the mapping table, temporary keys associated with the changes are swapped with backend keys which the temporary keys are mapped. This maintains data persistency of newly created and change data during an offline session.