Identifier Cache for Reusing Merged Access Control Data

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The process of merging different types of access control information for each object being created and stored in a directory tree becomes a performance bottleneck for the file system, especially when a large number of objects are created and stored in a short amount of time, such as in a distributed version control repository.

Innovation Solution

Implementing a cache in the file system to determine if the merging of access control information has already been performed for a previous object, allowing the system to associate the merged access control information with the current object via a pointer if a match is found, thereby avoiding redundant merging processes.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If the file system merges access control information for each object individually, then access control accuracy is ensured, but processing time increases significantly when creating large numbers of objects

Engineering Contradiction:
Improveaccess control accuracyVSAvoidprocessing time
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The patent applies preliminary action by pre-computing and caching merged access control information for parent directories before objects are created. When an object is created, the system retrieves previously computed access control information from the cache rather than performing redundant merging operations, thus ensuring accuracy while reducing processing time.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent uses copying by creating cached copies of merged access control information from parent directories and storing them in a cache structure. These cached copies are then reused for multiple objects that inherit from the same parent, avoiding repeated computation while maintaining access control accuracy through validation mechanisms.

Inventive Principle:
Principle #26Copying

2Reliability

If the file system performs complete merging operations for every object, then access control reliability is maintained, but system productivity decreases when handling bulk object creation

Engineering Contradiction:
Improveaccess control reliabilityVSAvoidobject creation throughput
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system performs preliminary merging of access control information at the parent directory level and caches the results before object creation occurs. This preliminary action ensures that reliable merged access control information is prepared in advance, allowing bulk object creation to proceed at high speed without compromising reliability.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent merges the computation of access control information at a higher level (parent directory) and combines it with object creation operations. By merging access control information once for the parent and reusing it for multiple child objects, the system maintains reliability while dramatically improving productivity during bulk operations.

Inventive Principle:
Principle #5Merging (Combining)

3Reliability

If memory is allocated for each object's access control information, then individual object security is ensured, but memory consumption increases for large numbers of objects

Engineering Contradiction:
Improveindividual object securityVSAvoidmemory consumption
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The patent merges access control information from parent directories and reuses the same memory structures for multiple child objects that share the same parent. Instead of allocating separate memory for each object's access control information, the system combines and reuses cached access control data, reducing overall memory consumption while maintaining individual object security through proper inheritance mechanisms.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The system creates lightweight cached copies of access control information in memory rather than allocating full duplicate structures for each object. These cached copies are shared among multiple objects, significantly reducing memory consumption while ensuring each object maintains its security properties through the inheritance model.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS20250217296A1Cache for identifiers representing merged access control information
Publication Date: 2025.07.03 MICROSOFT TECHNOLOGY LICENSING LLC
  • US20250217296A1 patent drawing
  • US20250217296A1 patent drawing
  • US20250217296A1 patent drawing

AI summary

The system described herein introduces a cache that a file system uses to determine, for a current object, if the process to merge different types of access control information into merged access control information has already been performed for a previous object. Stated alternatively, the file system uses the cache to determine whether a current object being processed for storage has the same combination of access control information as a previous object that has already been processed for storage. If the current object has the same combination of access control information as the previous object, the file system is able to associate merged access control information for the previous object with the current object via the use of a pointer. Consequently, the file system avoids having to perform the resource-intensive process of merging the different types of access control information for the current object.