Presence Server Authorization Rule Caching

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The evaluation of authorization rules in presence servers is a resource-heavy process, leading to reduced capacity and increased latency due to tasks like database access, XML parsing, and manipulation, which are bottlenecks in handling subscriptions and notifications.

Innovation Solution

A method that involves evaluating authorization rules once and storing rule identifiers and action results, allowing subsequent authorization processes to perform actions independently, reducing the need for repeated rule evaluations by using stored profiles and only retrieving applicable rules when necessary.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If authorization rules are evaluated completely for each subscription request and notification, then authorization accuracy is maintained, but resource consumption increases and processing speed decreases

Engineering Contradiction:
Improveauthorization accuracyVSAvoidprocessing speed
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent applies preliminary action by evaluating and caching authorization rules in advance before they are needed for actual subscription processing. The system pre-evaluates rules against presence information changes and stores the results, so that when subscription requests or notifications occur, the pre-computed authorization decisions can be rapidly applied without repeating the full evaluation process. This resolves the contradiction by maintaining accurate authorization (through thorough pre-evaluation) while dramatically improving processing speed (by avoiding repeated evaluations).

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent merges the authorization rule evaluation process with the presence information change detection process. Instead of separately evaluating authorization rules for each subscription request or notification, the system combines these operations by evaluating rules once when presence information changes and caching the results for multiple subsequent operations. This consolidation maintains authorization accuracy while reducing overall processing time and resource consumption across multiple requests.

Inventive Principle:
Principle #5Merging (Combining)

2Reliability

If authorization rules are evaluated for every subscription request and notification, then authorization completeness is ensured, but resource consumption increases due to repeated database access, XML parsing, and manipulation

Engineering Contradiction:
Improveauthorization completenessVSAvoidresource consumption
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The system performs authorization rule evaluation in advance and caches the results before they are needed for actual subscription processing. By pre-evaluating rules against presence information changes and storing the outcomes, the system ensures complete authorization coverage while avoiding the resource-intensive operations of repeated database access, XML parsing, and manipulation that would occur if full evaluation were performed for each request.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent creates and stores copies of authorization rule evaluation results in a cache structure. Instead of repeatedly accessing and re-evaluating the original authorization rules stored in XML format (which requires parsing and manipulation), the system creates simplified copies of the evaluation results that can be rapidly applied. This copying approach maintains authorization completeness while dramatically reducing resource consumption by eliminating repeated parsing and manipulation operations.

Inventive Principle:
Principle #26Copying

3Reliability

If full authorization rule evaluation is performed for each operation, then authorization correctness is maintained, but response latency increases

Engineering Contradiction:
Improveauthorization correctnessVSAvoidresponse latency
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent applies preliminary action by evaluating authorization rules in advance and caching the results before they are needed for subscription requests or notifications. The system pre-computes authorization decisions when presence information changes and stores these results, enabling rapid retrieval and application during actual operations. This approach maintains authorization correctness (through thorough pre-evaluation) while dramatically reducing response latency (by avoiding repeated evaluation during time-critical operations).

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent merges authorization rule evaluation with presence information change detection into a single integrated process. By evaluating rules once when presence information changes and caching the results for multiple subsequent subscription requests and notifications, the system maintains authorization correctness while reducing the time required for each individual operation. This consolidation eliminates the latency that would result from separate evaluation processes for each request.

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS8677456B2Accelerated reevaluation of authorization rules
Publication Date: 2014.03.18 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US8677456B2 patent drawing
  • US8677456B2 patent drawing
  • US8677456B2 patent drawing

AI summary

A method for evaluating authorization rules, the method including evaluating a plurality of authorization rules in connection with an authorization process for a subject, storing in a computer-readable storage medium and in association with the subject a rule identifier of any of the rules that are applicable to the subject, and performing, in connection with a subsequent authorization process for the subject, a computer-based action indicated by any of the rules identified by any of the stored rule identifiers, where the performing step is performed independent from an evaluation of the applicability of any of the authorization rules in connection with the subsequent authorization process.