Cache Manager for Application Information Access Control

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing application information caching tools and techniques fail to effectively utilize cached information and honor access rights for multiple user objects, leading to inefficiencies in fetching and processing application data, especially under poor network conditions.

Innovation Solution

The proposed solution involves converting application information into an enhanced format for caching, allowing it to be stored and retrieved efficiently, while maintaining access control by determining user authorization and storing it in a cache-friendly format, thus reducing the need for repeated conversions and re-fetching from repositories.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If application information is fetched from remote stores, then the information can be obtained, but the fetching time is considerable and network failures occur intermittently

Engineering Contradiction:
Improveinformation access reliabilityVSAvoidfetching time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent applies preliminary action by pre-fetching application information from remote stores and storing it in local caches before it is actually needed. The cache manager proactively retrieves data and converts it to an enhanced format for future use, eliminating the need to wait for remote fetches when applications need the information.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent introduces a cache manager as an intermediary component between applications and remote stores. This cache manager handles the complexity of remote access, performs format conversions, and manages cache storage, shielding applications from remote store failures and delays while providing reliable local access to application information.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If application information is stored in local caches in the original format, then storage space is saved, but repeated format conversions are required increasing processing time

Engineering Contradiction:
Improveinformation processing speedVSAvoidconversion processing energy
Core Design Contradiction:
ProductivityVSLoss of energy

Solution Approach 1:

The patent performs the format conversion action in advance when data is first cached, rather than converting it repeatedly on each access. The cache manager converts application information from the remote store format to an enhanced local format during the initial cache population, so subsequent accesses can use the pre-converted data directly.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent creates a copy of the application information in an enhanced format specifically optimized for local cache usage. Instead of storing the original remote format data, the system creates and stores an enhanced format copy that is more efficient for local processing and access, accepting the one-time conversion cost for long-term performance gains.

Inventive Principle:
Principle #26Copying

3Productivity

If cached information is made accessible to multiple user objects, then access efficiency improves, but access control rights may be violated

Engineering Contradiction:
Improvedata access efficiencyVSAvoidaccess control compliance
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent applies local quality by associating cached information instances with specific user objects and their authorization contexts. Instead of a generic cache accessible to all users, the system creates user-specific cache entries or tags them with authorization metadata, allowing efficient access for authorized users while maintaining security boundaries for each user object.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The patent implements feedback mechanisms where the cache manager continuously monitors and enforces access control policies. When a user object requests cached information, the system checks authorization rights and provides feedback by either granting access to the cached data or redirecting to remote fetch, ensuring access control compliance while maintaining cache efficiency where possible.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS8909863B2Cache for storage and/or retrieval of application information
Publication Date: 2014.12.09 MICROSOFT TECHNOLOGY LICENSING LLC
  • US8909863B2 patent drawing
  • US8909863B2 patent drawing
  • US8909863B2 patent drawing

AI summary

A request for application information can be received from an application running in a process. The application information can be requested from an information repository, and received back from the repository in a first format. The application information can be converted to a second format, and passed to the application in the second format. In addition, the application information can be saved in the second format in a cache in the process. Also, when application information has been cached in response to a request for the information for a first user object, and a subsequent request for the application information for a second user object is received, it can be determined whether the second user object is authorized to access the application information. If so, then the application information can be fetched from the cache and returned for use by the second user object.