Local Content Replication Engine for Offline Access

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current content management systems lack seamless transition from remote access models to synchronized models, particularly for mobile devices, where users need to access shared content objects offline and synchronize changes efficiently.

Innovation Solution

The implementation of a local content management engine that automatically replicates remotely-stored content objects to a locally-stored and synchronized instance, allowing users to manage content offline and synchronize changes when online, reducing the demand for computer resources and network bandwidth.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If content objects are accessed remotely through URL, then network bandwidth and device storage are conserved, but offline access capability is lost

Engineering Contradiction:
Improveoffline access capabilityVSAvoidnetwork bandwidth consumption
Core Design Contradiction:
Ease of operationVSQuantity of substance

Solution Approach 1:

The system performs preliminary action by automatically downloading and caching content objects to local storage before offline access is needed. The synchronization engine proactively replicates content from remote storage to local device, enabling subsequent offline access without real-time network connectivity.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system creates local copies of remotely-stored content objects. The synchronization engine replicates content objects from remote storage to local device storage, allowing users to access content offline. These local copies are maintained and updated through automated synchronization processes.

Inventive Principle:
Principle #26Copying

2Ease of operation

If content objects are downloaded to local storage, then offline access is enabled, but device storage and memory consumption increase

Engineering Contradiction:
Improveoffline access capabilityVSAvoiddevice storage consumption
Core Design Contradiction:
Ease of operationVSWeight of moving object

Solution Approach 1:

The system applies local quality by selectively caching content objects based on user-specific criteria such as access frequency, content type, and user preferences. Different users have different local caches tailored to their needs, optimizing storage usage while maintaining offline access capability for relevant content.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The system dynamically adjusts caching parameters such as cache size limits, eviction policies, and synchronization frequency based on available device storage, network conditions, and usage patterns. This allows the system to adapt storage consumption to current device capacity while maintaining offline access where possible.

Inventive Principle:
Principle #35Parameter changes

3Productivity

If manual synchronization is used, then user control over synchronization timing is maintained, but time consumption and user interaction requirements increase

Engineering Contradiction:
Improvesynchronization efficiencyVSAvoiduser interaction time
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The synchronization engine operates autonomously without requiring user intervention. It automatically detects content changes, initiates synchronization operations, manages conflict resolution, and updates local caches based on predefined policies and triggers, freeing users from manual synchronization tasks.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system implements feedback mechanisms where the synchronization engine continuously monitors content changes, synchronization status, and device state. Based on this feedback, it dynamically adjusts synchronization behavior, triggering updates when content changes are detected and pausing when synchronization is complete or device resources are constrained.

Inventive Principle:
Principle #23Feedback

4Productivity

If automated replication protocol is implemented, then synchronization efficiency improves, but system complexity increases

Engineering Contradiction:
Improvesynchronization efficiencyVSAvoidsystem architecture complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system introduces a synchronization engine as an intermediary layer between local and remote storage systems. This mediator handles the complexity of replication protocols, conflict resolution, and state synchronization, shielding users and applications from these complexities while maintaining efficient automated synchronization.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The synchronization system is segmented into distinct functional modules including content change detection, replication protocol handling, conflict resolution, and cache management. This modular architecture manages system complexity by allowing each component to handle specific tasks independently while working together to achieve automated synchronization.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS11017048B2Synchronized content replication
Publication Date: 2021.05.25 BOX INC
  • US11017048B2 patent drawing
  • US11017048B2 patent drawing
  • US11017048B2 patent drawing

AI summary

Content management in a collaboration system. Ease-of-use of shared content is facilitated. A URL is presented in a user interface. The system determines (e.g., based on user preferences) whether to display the content corresponding to the URL in a browser at the user device, or whether to display the content corresponding to the URL using a non-browser application. If the user device is configured to display the content corresponding to the URL using a non-browser application, then when the user clicks or touches or hovers, or otherwise indicates a selection of a URL, the system displays the content using the non-browser application. In this situation, the system retrieves the content from the collaboration system, stores a local instance of the content in local storage of the user device, and opens the local instance using the non-browser application. Local instance edits are synchronized with the collaboration system using a synchronization protocol.