Selective Synchronization Orphan Objects Hierarchical Folders
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Mobile devices face challenges in efficiently synchronizing data with servers due to limited storage capacity and bandwidth constraints, leading to time-consuming and bandwidth-intensive deletion and download processes when files on the server change.
Innovation Solution
A computer-implemented method and system that selectively synchronizes data by converting orphan objects stored on the mobile device into inaccessible entities, reducing network bandwidth usage by storing them locally until adoption by another object, and synchronizing only necessary files, using a hierarchical folder structure and synchronization engine to manage data traversal and synchronization.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If all files are synchronized between server and mobile device, then data consistency is improved, but network bandwidth usage and synchronization time increase
Solution Approach 1:
The patent segments the file synchronization process by introducing folder objects that act as containers. Instead of synchronizing individual files independently, the system synchronizes folders as units, allowing selective synchronization of file groups based on folder-level operations, thereby reducing unnecessary network bandwidth usage while maintaining data consistency.
Solution Approach 2:
The patent implements partial synchronization by allowing the mobile device to operate with a subset of files stored locally while the complete file set remains on the server. The folder object mechanism enables selective downloading of only necessary files or folders, performing partial action rather than complete file synchronization, thus conserving network bandwidth.
2Reliability
If files are deleted and re-downloaded during synchronization, then data consistency is improved, but synchronization time and bandwidth consumption increase
Solution Approach 1:
The patent applies preliminary action by creating folder objects and their hierarchical structure on the mobile device before actual file synchronization occurs. This pre-structure allows the system to efficiently manage file operations by working with folder containers, reducing the need for repeated delete-and-download cycles and thereby reducing synchronization time.
Solution Approach 2:
The patent uses copying by creating local copies of folder objects and their metadata on the mobile device. Instead of constantly deleting and re-downloading files, the system maintains local copies of folder structures and selectively updates only the necessary file content, significantly reducing synchronization time and bandwidth consumption.
3Ease of operation
If complete folder structure is maintained on mobile device, then data accessibility is improved, but local storage requirements increase
Solution Approach 1:
The patent extracts the essential folder structure and metadata from the complete file set and stores only these extracted elements locally on the mobile device. The actual file contents remain on the server, allowing the device to maintain data accessibility through the folder hierarchy while minimizing local storage requirements by storing only the structural framework.
Solution Approach 2:
The patent implements nesting by creating a hierarchical folder object structure where folders contain references to other folders and files. This nested structure allows the mobile device to maintain the complete folder hierarchy locally for easy navigation and accessibility, while the actual file data is stored externally on the server, effectively reducing local storage requirements.
Data Source
AI summary
A technique is described to selectively synchronize content on a client database with content from a server database. As the user traverses a hierarchical folder structure of the client database, he may run into content that has been deleted or moved in the server database. If the content is something that the user wishes to store locally, the content can be stored as an orphan. An orphan is content stored on the client that cannot be traversed by the hierarchical folder structure. When the user traverses to a node in the hierarchical folder structure that is missing an object existing on the server, a determination can be made as to whether the orphan object is the missing object. If so, the orphan object can be connected once against to the hierarchical folder structure. This may minimize the content that needs to be re-downloaded from the server.