Predictive File Caching via Sensor Context and Partitioning

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Traditional file caching techniques often cache content that is never used again by the user and prematurely delete content still needed, due to non-distinguishing storage and deletion methods, leading to inefficiencies in network bandwidth usage and storage requirements.

Innovation Solution

A system for predictive file caching and synchronization that uses sensor data to determine a device context and intelligently cache files based on access patterns and similarity to recently accessed files, with dynamic partitioning and cache policies to optimize storage and security, allowing for improved cache hit rates and reduced storage requirements.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of manufacture

If traditional caching schemes store and delete content in a non-distinguishing manner, then implementation is simple, but cache hit rate deteriorates and storage efficiency worsens

Engineering Contradiction:
Improvecaching implementation simplicityVSAvoidcache hit rate
Core Design Contradiction:
Ease of manufactureVSReliability

Solution Approach 1:

The patent segments the cache into multiple partitions, where each partition stores files with specific characteristics or from specific sources. This segmentation allows the system to apply different caching strategies to different partitions, improving cache hit rates while maintaining manageable complexity through structured organization.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent applies local quality by making different parts of the cache serve different purposes. Some partitions are optimized for frequently accessed files, others for recently modified files, and others for files with specific metadata characteristics. This localized optimization improves overall cache effectiveness without requiring complete system redesign.

Inventive Principle:
Principle #3Local quality

2Ease of manufacture

If traditional caching uses predetermined storage periods, then deletion policy is simple, but files still needed are prematurely deleted

Engineering Contradiction:
Improvedeletion policy simplicityVSAvoidfile availability
Core Design Contradiction:
Ease of manufactureVSReliability

Solution Approach 1:

The patent implements feedback mechanisms that continuously monitor file access patterns, modification times, and usage characteristics. This feedback informs dynamic cache retention decisions, allowing the system to extend or shorten storage periods based on actual file importance rather than predetermined schedules, thus preventing premature deletion of needed files.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The patent makes the cache deletion policy dynamic by adjusting retention periods based on real-time observations of file access patterns and user behavior. Files that show continued usage beyond initial expectations are automatically retained longer, while files with declining access patterns are proactively deleted, optimizing both availability and storage efficiency.

Inventive Principle:
Principle #15Dynamics

3Reliability

If more content is cached to improve availability, then cache hit rate improves, but storage requirements increase

Engineering Contradiction:
Improvefile availabilityVSAvoidstorage capacity
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The patent applies partial action by caching only the most valuable subset of files rather than all possible content. Using access pattern analysis and predictive algorithms, the system identifies and caches only those files most likely to be needed, achieving high availability for critical files while avoiding the storage overhead of caching everything.

Inventive Principle:
Principle #16Partial or excessive action

Solution Approach 2:

The patent changes parameters such as cache size allocations, retention periods, and priority levels dynamically based on available storage capacity and observed usage patterns. When storage is abundant, the system caches more files; when storage is constrained, it prioritizes caching only high-value files, thus adapting to storage requirements while maintaining availability.

Inventive Principle:
Principle #35Parameter changes

4Productivity

If cache partitions are added to organize files by characteristics, then file retrieval efficiency improves, but device complexity increases

Engineering Contradiction:
Improvefile retrieval efficiencyVSAvoidcache structure complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent segments the cache into partitions based on file characteristics such as access frequency, modification recency, file type, or source. This segmentation improves retrieval efficiency by directing search operations to relevant partitions rather than scanning the entire cache. The complexity is managed through automated classification rules and metadata tagging systems.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent creates cache partitions that serve multiple functions simultaneously. For example, a partition may store both frequently accessed files and recently modified files, serving both quick retrieval and update tracking needs. This multi-functionality reduces the total number of partitions needed, thereby limiting complexity growth while maintaining retrieval efficiency.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS11436147B2Technologies for predictive file caching and synchronization
Publication Date: 2022.09.06 INTEL CORP
  • US11436147B2 patent drawing
  • US11436147B2 patent drawing
  • US11436147B2 patent drawing

AI summary

Technologies for predictive caching include a computing device to receive sensor data generated by one or more sensors of the computing device and determine a device context of the computing device based on the sensor data. Based on the device context, the computing device determines a file to cache that has similar characteristics to another file recently accessed by a user of the computing device. The computing device includes a file cache with a first partition to store files identified to have similar characteristics to files recently accessed by a user and a second partition to store files identified based on access patterns of the user. The computing device stores the determined file to the first partition.