Offline Work Unit Synchronization With Deferred Conflict Handling
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing field data collection systems face challenges with intermittent and unreliable network connectivity, leading to inefficient data synchronization and high bandwidth consumption, especially in scenarios like insurance claims adjustment with large documentation needs.
Innovation Solution
Implementing deferred data synchronization that allows offline modifications on client devices with intermittent connectivity, using priority queues to store and prioritize data updates, and resolving conflicts through predefined rules when reconnecting to the system of record.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If continuous data synchronization is implemented between mobile device and central server, then data is continuously updated while being gathered, but bandwidth consumption increases significantly and connectivity requirements become more stringent
Solution Approach 1:
The system implements periodic synchronization instead of continuous synchronization. Data is synchronized at predetermined intervals or when specific conditions are met (such as connection availability), rather than continuously updating. This reduces bandwidth consumption while maintaining data synchronization reliability through scheduled updates.
Solution Approach 2:
The system performs preliminary actions by queuing data changes locally on the mobile device before synchronization occurs. Data is buffered and prioritized in local queues, with critical data marked for earlier synchronization. This preliminary organization reduces the actual data transfer needed during synchronization events.
2Reliability
If data is continuously updated between mobile device and central server, then data integrity is maintained, but connectivity requirements become more stringent and impractical in field conditions
Solution Approach 1:
The system dynamically adapts its synchronization behavior based on connectivity conditions. When connectivity is available, synchronization occurs; when unavailable, the system continues operating with local data and queues changes for later synchronization. This dynamic approach maintains data integrity while adapting to varying connectivity conditions in field environments.
Solution Approach 2:
The system prepares for connectivity interruptions by implementing local queuing and data buffering mechanisms beforehand. When connection is lost, the system can continue operating with cached data and queue accumulated changes without interruption. This beforehand cushioning ensures data integrity is maintained even when connectivity is unavailable.
3Loss of information
If large amounts of documentation are constantly synchronized, then data completeness is maintained, but bandwidth consumption becomes impractical in field scenarios
Solution Approach 1:
The system extracts and synchronizes only the essential or changed portions of data rather than constantly synchronizing complete documentation sets. By identifying and transferring only necessary data elements (such as changed fields or critical information), the system maintains data completeness while significantly reducing bandwidth consumption for large documentation sets.
Solution Approach 2:
The system performs preliminary data processing to identify changes and prioritize synchronization needs before actual data transfer. By pre-processing data to determine what needs synchronization and organizing it in priority queues, the system ensures data completeness is maintained while minimizing the actual bandwidth consumed during transfer.
Data Source
AI summary
Deferred data synchronization includes obtaining at least a portion of a copy of a work unit from a system of record, the work unit comprising a plurality of categories, each category comprising a set of one or more elements; while a client device is offline with respect to the system of record, performing an offline action that includes a modification to an element of the copy of the work unit, recording locally the modification to the element of the copy of the work unit, and deferring synchronization of the modification with the system of record; and synchronizing the modification with the system of record, including causing the system of record to detect whether the modification is in conflict with the work unit on the system of record.