Unified Access Management Policy Caching for Low-Latency Authorization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Cloud-based access servers experience high latency in processing authentication requests due to the need to download large amounts of data for each user access, which can diminish user satisfaction and overwhelm the system with concurrent requests.

Innovation Solution

Implementing a system that anticipates future authentication requests by pre-loading dependent data and evaluating them in advance using historical user access patterns and preemptive processing techniques, including the use of a replay server to generate and evaluate additional authorization requests.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the access server downloads large amounts of data for each user access, then the authentication can be thorough and secure, but the processing latency increases and system performance deteriorates

Engineering Contradiction:
Improveauthentication accuracyVSAvoidprocessing latency
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary actions by anticipating future authentication requests and pre-loading dependent data before actual requests occur. The replay service generates and evaluates authorization requests in advance using historical patterns, so when real requests arrive, the data is already prepared and latency is reduced.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system segments authentication processing into two parts: frequently accessed policies are pre-loaded and cached separately, while less frequent policies are loaded on-demand. This segmentation allows the system to optimize for common cases without compromising the ability to handle rare cases, reducing average latency while maintaining thorough authentication.

Inventive Principle:
Principle #1Segmentation

2Device complexity

If the access server processes each authentication request individually, then the processing is simple and straightforward, but the system becomes overwhelmed with concurrent requests

Engineering Contradiction:
Improveprocessing complexityVSAvoidconcurrent request handling capacity
Core Design Contradiction:
Device complexityVSProductivity

Solution Approach 1:

The replay service performs preliminary processing of authorization requests in advance, evaluating them before actual user requests arrive. This preliminary action distributes the processing load over time, preventing the system from being overwhelmed by concurrent requests while maintaining simple individual processing logic.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The replay service creates copies of authentication requests from historical data and processes these copies in advance. This allows the system to evaluate multiple potential requests beforehand without affecting the simplicity of processing actual requests, thereby increasing concurrent request handling capacity.

Inventive Principle:
Principle #26Copying

3Loss of time

If the system pre-loads dependent data for anticipated requests, then the latency is reduced, but the data storage requirements and memory usage increase

Engineering Contradiction:
Improveauthentication latencyVSAvoiddata storage volume
Core Design Contradiction:
Loss of timeVSQuantity of substance

Solution Approach 1:

The system applies local quality by caching data specifically for frequently accessed policies and their dependencies, rather than pre-loading all possible data. The cache is selectively populated based on access patterns, storing only the portion of data that will actually be needed, thus reducing memory usage while still achieving latency reduction for common cases.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The system performs partial pre-loading by anticipating only the most likely future requests based on historical patterns, rather than pre-loading all possible requests. This partial action reduces the quantity of pre-loaded data while still achieving significant latency reduction for the majority of cases.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS12598214B2Processing authentication requests for unified access management systems and applications using frequently invoked policies
Publication Date: 2026.04.07 NVIDIA CORP
  • US12598214B2 patent drawing
  • US12598214B2 patent drawing
  • US12598214B2 patent drawing

AI summary

Disclosed are apparatuses, systems, and techniques that improve efficiency and decrease latency of processing of authorization requests by cloud-based access servers that evaluate access rights to access various cloud-based services. The techniques include but are not limited to generating and processing advanced authorization requests that anticipate future authorization requests that may be generated by cloud-based services. The techniques further include processing of frequently accessed policies and policy data dependencies and preemptive generation and processing of authorization requests that are replicated from existing authorization requests.