Depth-Based Cache Authoritativeness for Hierarchical Object Consistency

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The inconsistency between local cache and long-term storage systems due to slower event processing times leads to non-authoritative local versions of objects, necessitating a need for efficient cache authoritativeness determination.

Innovation Solution

Implementing depth-based cache authoritativeness determination by associating objects with metadata indicating storage time and freshness intervals derived from their hierarchical depth, and monitoring these objects to ensure timely refreshment from the LTS system.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Speed

If the local cache is used to store customer data, then the access speed is improved, but the data consistency with the LTS system deteriorates due to slower event processing times

Engineering Contradiction:
Improvedata access speedVSAvoiddata consistency
Core Design Contradiction:
SpeedVSReliability

Solution Approach 1:

The patent applies local quality by differentiating cache freshness intervals based on object depth in the hierarchical file system. Objects at greater depths are associated with shorter freshness intervals, while objects at shallower depths have longer intervals. This allows the system to maintain data consistency for frequently accessed shallow objects while allowing deeper objects to expire sooner, resolving the contradiction between fast access and consistency.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The patent implements dynamics by making the cache freshness interval variable rather than fixed. The freshness interval is dynamically determined based on the object's depth in the hierarchical file system, allowing the system to adaptively manage cache authoritativeness based on access patterns and object characteristics, thus balancing speed and reliability.

Inventive Principle:
Principle #15Dynamics

2Reliability

If the cache freshness interval is extended, then the data consistency is improved, but the cache performance and accessibility deteriorate

Engineering Contradiction:
Improvedata consistencyVSAvoidcache performance
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent applies local quality by differentiating cache freshness intervals based on object depth in the hierarchical file system. Objects at greater depths are associated with shorter freshness intervals, while objects at shallower depths have longer intervals. This allows the system to maintain data consistency for frequently accessed shallow objects while allowing deeper objects to expire sooner, resolving the contradiction between fast access and consistency.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The patent implements parameter changes by varying the cache freshness interval parameter based on object depth. The system changes the time parameter dynamically according to the hierarchical position of objects, optimizing the balance between maintaining consistency and ensuring cache performance for different types of data.

Inventive Principle:
Principle #35Parameter changes

3Loss of time

If a crawler application constantly monitors objects in the cache, then the time lag is reduced, but the system complexity and resource consumption increase

Engineering Contradiction:
Improvetime lagVSAvoidsystem complexity
Core Design Contradiction:
Loss of timeVSDevice complexity

Solution Approach 1:

The patent applies periodic action by implementing a crawler application that periodically monitors objects in the cache to determine their authoritativeness. Instead of continuous monitoring, the system performs periodic checks at intervals, reducing the time lag between object changes and metadata updates while avoiding the complexity and resource consumption of continuous real-time monitoring.

Inventive Principle:
Principle #19Periodic action

Solution Approach 2:

The patent implements self-service by having the crawler application automatically monitor and update object metadata based on predefined freshness intervals. The system serves itself by autonomously determining when objects need refreshing without requiring external intervention or complex centralized management, thus reducing time lag while managing complexity.

Inventive Principle:
Principle #25Self-service

4Loss of energy

If the workspace waits until detecting a request for the object before determining authoritativeness, then unnecessary I/O activities are avoided, but the response time increases

Engineering Contradiction:
ImproveI/O activityVSAvoidresponse time
Core Design Contradiction:
Loss of energyVSLoss of time

Solution Approach 1:

The patent applies preliminary action by pre-determining object authoritativeness based on the current time and cached freshness intervals before actual requests occur. The system performs preliminary freshness checks using the formula: current time - cache storage time < freshness interval, allowing the workspace to respond faster without unnecessary I/O activities by having authoritativeness determined in advance.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent implements feedback by using the crawler application to continuously monitor and update object metadata based on actual access patterns and freshness status. The system receives feedback from object access events and adjusts the authoritativeness determination accordingly, allowing the workspace to balance response time with I/O activity by using feedback-driven decisions.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS20250217328A1Systems and Methods for Depth Based Cache Authoritativeness
Publication Date: 2025.07.03 RELATIVITY ODA LLC
  • US20250217328A1 patent drawing
  • US20250217328A1 patent drawing
  • US20250217328A1 patent drawing

AI summary

Techniques for depth-based cache authoritativeness are provided. A method includes receiving a request for an object maintained at long-term storage (LTS) system and associated with a hierarchical directory; retrieving the object from the LTS system; storing the object in the cache such that the object is associated with metadata indicating (i) a storage time at which the storage occurred and (ii) whether the object is authoritative; detecting a stimulus to determine whether the object is authoritative; responsive to detecting the stimulus, determining whether the object is authoritative; and responsive to determining that the object in the cache is non-authoritative, setting the metadata indicating whether the object is authoritative to indicate that the object is not authoritative.