Cache Device Shared Data Retention Strategy

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing cache systems struggle to dynamically distinguish between independent and shared data during operation, leading to inefficient data retention and cache hit rates.

Innovation Solution

A cache device and system that dynamically differentiate between independent and shared data by using a cache unit and storage area control unit to prioritize shared data retention, managing storage areas and discarding less frequently accessed data when capacity is limited.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If data are retained in both server cache and storage cache, then data availability is improved, but cache storage efficiency deteriorates due to redundant retention of independent data

Engineering Contradiction:
Improvedata availabilityVSAvoidcache storage efficiency
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments cache data into two categories: shared data (accessed by multiple servers) and independent data (accessed by a single server). The storage cache selectively retains only shared data, while server caches retain their respective independent data. This segmentation eliminates redundancy and improves storage efficiency while maintaining data availability through the distributed cache structure.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent applies local quality by assigning different retention policies to different types of data in the storage cache. Shared data are retained in the storage cache for potential access by multiple servers, while independent data are excluded from storage cache retention. This differentiated approach optimizes cache utilization by matching data characteristics with appropriate retention strategies.

Inventive Principle:
Principle #3Local quality

2Productivity

If shared data are prioritized in storage cache, then cache hit rate is improved, but cache management complexity increases

Engineering Contradiction:
Improvecache hit rateVSAvoidcache management complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The storage cache controller implements a feedback mechanism by monitoring data access patterns across multiple servers. When data are determined to be shared (accessed by multiple servers), the controller provides feedback to retain these data in the storage cache. This feedback-driven approach automatically optimizes cache hit rates for shared data without requiring complex manual management, as the system self-adjusts based on observed access patterns.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The cache system performs self-service by automatically identifying shared data through access pattern analysis and making retention decisions without external intervention. The storage cache controller autonomously determines which data should be retained based on their sharing status, eliminating the need for complex external cache management while improving hit rates for shared data.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS9858204B2Cache device, cache system, and cache method
Publication Date: 2018.01.02 NEC CORP
  • US9858204B2 patent drawing
  • US9858204B2 patent drawing
  • US9858204B2 patent drawing

AI summary

A cache device connected to a storage device and connected to a plurality of sources, including a cache unit that relays a read request and a read response between a source and a storage device, and a storage area control unit that stores the source as a first history in association with specification of first data in a read request, and, if the first data are not retained by the cache unit and a storage area sufficient for retaining the first data does not exist, selects data associated with a less number of the sources in the first history as second data in preference to data associated with a greater number of the sources out of the first data or data retained by the cache unit, and, if the second data differ from the first data, causes the cache unit to discard the second data and then store the first data.