Offline Briefcase Synchronization via Selective Component Extraction
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional approaches for synchronizing mobile applications with remote servers for offline access often download unnecessary data, fail to ensure data consistency between online and offline modes, and perform synchronization at non-optimal times, leading to increased download times, storage requirements, and user interaction disruptions.
Innovation Solution
A system that includes an offline configurator to define which components are available offline, a priming service to create endpoints for downloading necessary data, and a record interest tracker to manage data synchronization, ensuring only relevant data is downloaded and displayed consistently across modes, while synchronizing in the background to avoid user disruption.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If conventional approaches download all data from remote server for offline access, then offline functionality is enabled, but download time and storage requirements increase significantly
Solution Approach 1:
The patent extracts and downloads only the specific components and data that are actually needed for offline functionality, rather than downloading all data. The system identifies and downloads only changed components since the last offline sync, significantly reducing download time and storage requirements while maintaining offline capability.
Solution Approach 2:
The patent segments the offline data synchronization process into two phases: an online phase where changed components are identified and prepared on the server, and an offline phase where only those specific changed components are downloaded to the mobile device. This segmentation allows efficient transfer of minimal necessary data.
2Reliability
If conventional approaches synchronize all data for offline access, then complete offline capability is achieved, but storage space requirements increase
Solution Approach 1:
The system extracts and downloads only the specific changed components that are necessary for offline access, rather than storing all data. By identifying and transferring only the minimal necessary data (changed components), the patent significantly reduces storage space requirements on mobile devices while maintaining complete offline capability for needed functionality.
3Reliability
If synchronization is performed at non-optimal times, then offline data is available, but user interaction with the mobile application is blocked
Solution Approach 1:
The patent performs preliminary actions by identifying and preparing changed components on the remote server during the online phase, before the user needs offline access. This preliminary preparation allows the actual offline data transfer to be minimal and fast, occurring without blocking user interaction, while still ensuring data availability when needed.
4Reliability
If conventional approaches download extraneous data, then offline functionality is ensured, but data consistency between online and offline modes is compromised
Solution Approach 1:
The patent implements a feedback mechanism where the system tracks which components have changed on the remote server since the last offline synchronization. This feedback information guides the selective download of only those specific changed components, ensuring that offline data remains consistent with online data while avoiding extraneous downloads.
Data Source
AI summary
Disclosed herein are system, method, and computer program product embodiments for synchronizing an offline briefcase. An embodiment operates by defining an offline briefcase for a user group that is accessible offline at an application. The embodiment detects a change to a component of the offline briefcase. The embodiment sends a push notification to the application based on the detected change to the component. The embodiment receives a synchronization request from the application in response to the sent push notification. The embodiment then sends the changed component to the application based on the synchronization request.