Cache Server Analyzer for Enterprise Content Management Lag

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Users experience lag time when requesting documents from a centralized content server located on the other side of the planet, as their geographically-based cache server has not pre-cached the documents.

Innovation Solution

Implementing a cache server analyzer that identifies content categories frequently requested by users and pre-caches relevant documents before they are actually requested, reducing lag time by ensuring that content is cached closer to users.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If documents are stored on a centralized content server located far from users, then data centralization and security are maintained, but users experience significant lag time when requesting documents

Engineering Contradiction:
Improvedata centralizationVSAvoiddocument access lag time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The cache server performs preliminary actions by pre-caching documents that are likely to be requested by users before they are actually needed. The system analyzes user access patterns and proactively retrieves and stores copies of frequently accessed documents in the cache server located closer to users, thereby eliminating lag time when users request these documents while maintaining data centralization at the origin server.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The cache server acts as an intermediary between the centralized content server and end users. It receives requests from users, checks if the requested documents are already cached, and if not, retrieves them from the centralized server and stores them locally. This intermediary layer provides documents to users without requiring direct communication with the distant centralized server for every request, thus reducing access lag time while preserving data centralization.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Speed

If all documents are cached locally at every cache server, then user access speed is maximized, but network bandwidth and storage resources are wasted on redundant data

Engineering Contradiction:
Improvedocument access speedVSAvoidnetwork bandwidth consumption
Core Design Contradiction:
SpeedVSLoss of energy

Solution Approach 1:

The cache server implements local quality by caching only the specific subset of documents that are relevant to its local user base. Instead of uniformly caching all documents, the system analyzes access patterns specific to each cache server's users and selectively caches only those documents that will be frequently requested by that particular user group. This approach maximizes access speed for local users while minimizing redundant storage and network bandwidth consumption.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The cache server performs partial caching by storing only a portion of the total document collection - specifically, the portion that is most likely to be accessed by local users. Rather than caching all documents (excessive action), the system uses access pattern analysis to determine and cache only the necessary subset (partial action), thereby achieving fast local access speeds while conserving network bandwidth and storage resources.

Inventive Principle:
Principle #16Partial or excessive action

3Speed

If cache servers pre-cache all possible documents, then user access speed is improved, but cache memory resources are exhausted

Engineering Contradiction:
Improvecontent access speedVSAvoidcache memory usage
Core Design Contradiction:
SpeedVSQuantity of substance

Solution Approach 1:

The cache server applies local quality by allocating its limited memory resources to store only the documents that are most relevant to its local user base. Instead of attempting to cache all possible documents uniformly, the system analyzes access patterns and selectively caches documents that will provide the greatest benefit to local users, thereby optimizing access speed within the constraints of available cache memory.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The cache server performs partial caching by storing only a fraction of the total possible documents - specifically, the fraction that provides the most value to local users based on access pattern analysis. This partial action approach ensures that cache memory resources are not exhausted while still achieving significant improvements in access speed for the most frequently requested documents.

Inventive Principle:
Principle #16Partial or excessive action

Solution Approach 3:

The system dynamically changes parameters by adjusting which documents are cached based on evolving access patterns. As user behavior changes over time, the cache server reanalyzes access patterns and modifies its caching strategy accordingly, ensuring that cache memory is always allocated to the most relevant documents while adapting to changing user needs without exhausting resources.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS20230269296A1Method and System for Cache Data Analysis for Enterprise Content Management Systems
Publication Date: 2023.08.24 OPEN TEXT CORP
  • US20230269296A1 patent drawing
  • US20230269296A1 patent drawing
  • US20230269296A1 patent drawing

AI summary

Content categories are identified based on content provided by a server associated with an enterprise content management system. Using the relationship database, a content category is identified based on content associated with a client associated with a user, the content associated with the client associated with the user including content accessed by the user. A document associated with the content category is identified. A message is sent from the server to the client associated with the user to suggest to the user the document associated with the content category.