Offline Data Synchronization via Local Caching and Mediator Protocols
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing systems and methods fail to allow client devices to perform data operations and reflect these operations locally and to the data provider when connectivity is lost and then restored, leading to incomplete data synchronization.
Innovation Solution
The system enables client devices to store and process data locally when disconnected, allowing operations to be performed and then synchronizing changes with the data provider when connectivity is restored, using data model mapping and protocols like OData and SYBASE SQL Anywhere MobiLink for efficient data communication.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the client device operates online and communicates with the data provider, then data synchronization is maintained, but the client device cannot perform operations when connectivity is lost
Solution Approach 1:
The system performs preliminary actions by storing data locally on the client device before connectivity is lost. This allows the client to process and modify data offline using the previously cached data, and then synchronize these changes with the data provider when connectivity is restored.
Solution Approach 2:
The patent introduces an intermediary mechanism that manages data synchronization between the client device and data provider. This intermediary handles the complexity of offline/online transitions, conflict resolution, and data synchronization, allowing the client to operate offline while maintaining data consistency with the provider.
2Adaptability or versatility
If the client device processes operations offline, then connectivity requirements are reduced, but the operations cannot be reflected to the data provider
Solution Approach 1:
The system implements feedback mechanisms that track data modifications made offline on the client device. When connectivity is restored, these modifications are automatically reflected back to the data provider, ensuring data consistency. The feedback loop includes conflict detection and resolution to handle cases where the provider data has changed since the offline modification.
Solution Approach 2:
The client device performs preliminary data processing and modification offline, storing these changes locally. When connectivity is restored, the system executes the preliminary modifications and synchronizes them with the data provider, ensuring that offline operations are not lost but properly reflected in the centralized data source.
3Adaptability or versatility
If the system requires data provider reprogramming to support offline operations, then offline functionality can be implemented, but system complexity and deployment difficulty increase
Solution Approach 1:
The client device is designed to be self-sufficient for offline operations, maintaining its own local copy of data and the ability to process operations independently. The client autonomously manages offline data processing and synchronization without requiring modifications to the data provider, as it uses standard data access protocols to retrieve and update data.
Solution Approach 2:
The system employs universal data access protocols (such as OData) that allow the client device to interact with the data provider in both online and offline modes without requiring provider reprogramming. The client can cache data, process operations, and synchronize changes using standardized protocols, making the solution broadly applicable without custom integration work.
Data Source
AI summary
A method for processing data requests may include storing data on a client device received from a data provider maintaining the data. A request may be received to modify the data maintained by the data provider. After connectivity to the data provider is available, the request may be sent to the data provider. After connectivity is not available the request may be processed based on the data stored on the client device and the modified data may be stored on the client device.