On-Demand File Synchronization via Client-Side Storage
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Document management systems face inefficiencies in managing access to current file versions, particularly when network bandwidth is low or file sizes are large, due to the need for frequent transmission of updated files between central servers and client devices.
Innovation Solution
Implementing a method where the current version of a file is stored locally on the client device, with notifications of file updates sent to the server instead of the file itself, allowing for on-demand transmission of updated files when requested by other users for editing.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If the current version of a file is stored at a central server, then file access and version control are simplified, but network bandwidth is consumed frequently when files are updated and synchronized across client devices
Solution Approach 1:
The patent changes the storage dimension from centralized (server-only) to distributed (client-side storage). Instead of all file versions residing at the central server, the current working version is stored locally at the client device, transforming the architecture from a single-point storage model to a distributed storage model across multiple dimensions of the network system.
Solution Approach 2:
The file is downloaded and stored at the client device before editing begins. This preliminary action of pre-loading the file to the client reduces subsequent network traffic by enabling local editing operations without requiring continuous server communication during the editing process.
2Reliability
If the current version of a file is transmitted to the server upon completion of editing, then the server maintains an updated copy, but network communication overhead increases especially for large files
Solution Approach 1:
The patent extracts the file storage function from the central server and places it at the client device. The server retains only the metadata and version control information, while the actual file data resides at the client. This extraction reduces the quantity of data that needs to be transmitted over the network while maintaining version synchronization through selective updates.
Solution Approach 2:
Instead of transmitting the entire file upon each editing completion, the system transmits only partial updates or metadata changes when necessary. The full file remains at the client device, and only incremental changes or version information are communicated to the server, reducing overall network data transmission volume.
3Loss of information
If file updates are synchronized automatically to the server, then all users access the latest version, but system productivity decreases due to frequent network communications
Solution Approach 1:
The system implements periodic or on-demand synchronization rather than continuous automatic updates. File version consistency is maintained through scheduled checks or event-triggered updates (e.g., when the user explicitly saves or closes the file), rather than constant real-time synchronization, thereby reducing network communication frequency and improving system productivity.
Solution Approach 2:
The client device autonomously manages its local file version and determines when synchronization with the server is necessary. The system provides self-service by automatically detecting local modifications and initiating selective synchronization only when changes occur, eliminating the need for continuous server-pushed updates and reducing overall network traffic.
Data Source
AI summary
Techniques are described for managing access and synchronization of one or more files of a document management system stored locally at a client device. The techniques may include receiving, by a document management system executing on a server device, a file update notification message from a first client device to notify the document management system that a file was modified by the first client device. The file update notification message may include an indication of the modified file on the first client device without including the modified file. The document management system may receive a file editing request from a second client device to request the file. In response, the document management system may send a file upload request to the first client device, receive the modified file from the first client device, and send the modified file to the second client device.