Enterprise Rule Execution via Intermediate Event Object

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current enterprise computing systems lack a standardized way to interrelate policy, workflow, subscription, and preference frameworks, leading to inefficiencies in managing and accessing large data sets.

Innovation Solution

An enterprise system that automatically executes rules associated with events by creating an intermediate event object, filtering relevant rules, and authorizing access using an effective Access Control List (ACL), while enabling actions such as notification, rule invocation, and preference management.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If multiple policy frameworks (policy, workflow, subscription, preference) are used to manage enterprise systems, then the system can handle complex business rules and user preferences, but the frameworks cannot be interrelated in a standardized way across all elements

Engineering Contradiction:
Improvecapability to handle complex business rulesVSAvoidlack of standardization in interrelating frameworks
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent creates a universal event object structure that serves multiple frameworks (policy, workflow, subscription, preference) simultaneously. The event object acts as a multi-functional container that can be processed by different frameworks through a standardized interface, eliminating the need for separate handling mechanisms for each framework while maintaining their individual capabilities.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The event object serves as an intermediary between the different policy frameworks. Instead of allowing frameworks to directly interact with each other (which would create complexity), the event object mediates by standardizing the interface through which all frameworks receive and process information, enabling seamless interrelation across all system elements.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of operation

If the system filters and evaluates rules against event objects, then relevant rules can be selected and executed, but the process may incur performance overhead

Engineering Contradiction:
Improveautomatic rule executionVSAvoidsystem performance
Core Design Contradiction:
Ease of operationVSProductivity

Solution Approach 1:

The system performs preliminary actions by pre-computing entity states and preparing event objects in advance. The event object is structured with all necessary data and context pre-loaded, so that when rule filtering and evaluation occur, they can proceed efficiently without requiring additional data retrieval or computation during the matching phase.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS7797289B2Method and apparatus for automatically executing rules in enterprise systems
Publication Date: 2010.09.14 ORACLE INT CORP
  • US7797289B2 patent drawing
  • US7797289B2 patent drawing
  • US7797289B2 patent drawing

AI summary

One embodiment of the present invention provides an enterprise system that automatically executes a rule associated with an event. During operation, the system receives an event object at the enterprise system. Next, the system creates an intermediate event object based on the event object, wherein the intermediate object is an invocation context for the rule. The system also filters a set of rules with the intermediate event object to obtain a subset of rules. The system then selects a rule that is associated with the event from the subset of rules. Finally, the system executes the rule.