Local Cache Handling for Content Management Systems

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Content management systems face underutilization due to user resistance to unfamiliar interfaces and performance issues with synchronization, especially over unreliable connections and large data sets, leading to latency and poor user experience.

Innovation Solution

A local cache content management system that presents a remote content management system as a native local or shared drive, with intelligent handling of temporary files and permissions, and a caching mechanism to ensure smooth access and synchronization, even in unreliable conditions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If web-based interfaces are used for content management, then users can access stored files through browsers, but users are not familiar with such interfaces and resist learning them, causing underutilization

Engineering Contradiction:

Improveuser familiarity with interfaceVSAvoidsystem utilization

Core Design Contradiction:

Ease of operationVSProductivity

Solution Approach 1:

The patent creates a local cache that copies and stores file data locally on the user's device, presenting it through the native file interface that users are already familiar with. This copying approach allows users to access content management system files through their existing operating system file explorer, eliminating the need to learn new web-based interfaces while maintaining full access to stored files

Inventive Principle:

Principle #26Copying

Solution Approach 2:

The local cache acts as an intermediary layer between the content management system and the user. It translates between the remote file system and the local native file interface, allowing users to interact with remotely stored files as if they were local files through the familiar native interface, while the system handles synchronization and remote access in the background

Inventive Principle:

Principle #24Intermediary (Mediator)

2Ease of operation

If local copies are synchronized with remote copies, then users can access files locally, but synchronization performance is poor and latency increases, especially over unreliable connections

Engineering Contradiction:

Improvelocal file accessVSAvoidsynchronization latency

Core Design Contradiction:

Ease of operationVSLoss of time

Solution Approach 1:

The system performs preliminary actions by pre-loading and caching file data locally before it is needed by the user. When files are accessed, they are already present in the local cache, eliminating the need for real-time synchronization during user operations. This advance preparation reduces latency and allows the system to handle unreliable connections more effectively

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The patent segments the file access process into distinct phases: initial data retrieval and caching, local access operations, and background synchronization. By separating these functions, the system can provide immediate local access without waiting for synchronization to complete, and can perform synchronization in smaller, manageable increments rather than requiring complete file transfers

Inventive Principle:

Principle #1Segmentation

3Reliability

If complete synchronization is performed, then data consistency is maintained, but large amounts of data increase latency and provide poor user experience

Engineering Contradiction:

Improvedata consistencyVSAvoidsynchronization time

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The system performs partial synchronization by caching only the specific file data that users actually access and need, rather than synchronizing entire file systems or directories. This selective approach maintains data consistency for accessed files while dramatically reducing the time and bandwidth required compared to complete synchronization of all data

Inventive Principle:

Principle #16Partial or excessive action

Solution Approach 2:

The patent implements local quality by maintaining different data states in different locations: frequently accessed files are cached locally with full data for immediate access, while less accessed files remain on the remote server. The system dynamically determines what to cache locally based on access patterns, optimizing the balance between data consistency and synchronization performance for each specific file

Inventive Principle:

Principle #3Local quality

4Reliability

If connection reliability is improved, then synchronization works well, but in intermittent connection scenarios, caching mechanisms are needed to maintain access

Engineering Contradiction:

Improveconnection reliabilityVSAvoidaccess availability

Core Design Contradiction:

ReliabilityVSEase of operation

Solution Approach 1:

The system provides beforehand cushioning by maintaining a local cache of file data that serves as a buffer during connection interruptions. When the connection is available, data is cached locally; when the connection fails, the local cache continues to provide file access without interruption. This advance preparation cushions users against connection unreliability and maintains operational availability

Inventive Principle:

Principle #11Beforehand cushioning (Prior cushioning)

Data Source

PatentUS11470178B2System and method for robust local cache handling

Publication Date: 2022.10.11 SHINYDOCS

AI summary

A local cache content management is configured to improve the speed and reliability of access of the content management system across poor or intermittent connections. Additional techniques are used to allow document use and storage when the content management system is unavailable, and to maintain synchronization between the local cache and the content management system.