Dynamic Access Control Rules Engine Architecture

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing access control systems require extensive reimplementation to meet different user or customer requirements, lacking flexibility in configuring and executing dynamic rules and associated parameters without customer service intervention.

Innovation Solution

An access control system comprising a client application for configuring rules, a rules engine proxy for dynamic compilation and execution, and a controller to trigger rule execution based on input, allowing users to dynamically update and enforce access control logic without reimplementation.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If access control systems use hard-coded authorization configuration to meet specific user needs, then the system can provide customized access control logic, but the system complexity increases and requires extensive reimplementation for different users

Engineering Contradiction:
Improvecustomization capabilityVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system divides access control logic into separate, configurable rules that can be independently defined and managed. Each rule represents a discrete authorization configuration that can be customized without affecting other rules, allowing complex access control requirements to be broken down into manageable segments.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system transitions from static hard-coded authorization configurations to dynamic, user-configurable rules. Users can modify authorization logic in real-time without requiring system reimplementation, enabling the system to adapt flexibly to changing access control requirements.

Inventive Principle:
Principle #15Dynamics

2Adaptability or versatility

If access control systems are reimplemented to meet different customer requirements, then the system can accommodate diverse user needs, but the time and resources required increase significantly

Engineering Contradiction:
Improverequirements flexibilityVSAvoidreimplementation time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The system pre-establishes a framework of configurable rules and parameters that can be readily adjusted to meet different customer requirements. Instead of reimplementing the entire system, users can quickly configure appropriate rules within the existing framework, significantly reducing the time and resources needed to accommodate new requirements.

Inventive Principle:
Principle #10Preliminary action

3Ease of operation

If access control rules are dynamically updated without customer service intervention, then user autonomy increases, but the system must provide sophisticated configuration capabilities

Engineering Contradiction:
Improveuser autonomyVSAvoidconfiguration capability
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The system enables users to independently configure and modify access control rules without requiring customer service intervention. Users can directly update authorization logic, add or remove rules, and adjust parameters through the system interface, empowering them to manage their own access control requirements autonomously.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS7937669B2Access control system with rules engine architecture
Publication Date: 2011.05.03 HONEYWELL INTERNATIONAL INC
  • US7937669B2 patent drawing
  • US7937669B2 patent drawing
  • US7937669B2 patent drawing

AI summary

As access control system and method is provided. The access control system in one aspect may comprise a client application operable to provide a user interface for allowing a user to dynamically configure rules and associated parameters for controlling access to an entity; a rules engine proxy operable to receive said rules and associated parameters from the client application, the rules engine proxy further operable to dynamically compile and execute said rules; and a controller coupled to the rules engine proxy operable to receive input and further operable to trigger the rules engine proxy to execute one or more of said rules in response to the received input.