Rules Execution Platform Standardizing Syntax Across Engines

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing systems face challenges in facilitating communication between applications and rules engines due to varying syntax requirements, making it difficult to manage and execute rules across different engines without specific knowledge of each engine's configuration.

Innovation Solution

A platform protocol is introduced that defines a standardized syntax for rules, associates rules with metadata, and translates them into the specific syntax of each rules engine, allowing for seamless execution across different engines without requiring application users to know the engine's syntax.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If a standardized platform syntax is introduced to simplify rule definition, then ease of operation is improved, but device complexity increases due to the need for translation mechanisms

Engineering Contradiction:
Improveease of rule definitionVSAvoidcomplexity of translation mechanism
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent introduces a platform syntax as an intermediary layer between applications and rules engines. This standardized syntax acts as a mediator that simplifies rule definition for users while automated translation mechanisms handle the conversion to engine-specific syntaxes, isolating users from complexity.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system segments the rule execution architecture into distinct layers: a user-facing platform syntax layer for simplified rule definition, and engine-specific syntax layers for execution. This segmentation allows each layer to be optimized independently, with the translation layer handling the complexity of multiple syntaxes.

Inventive Principle:
Principle #1Segmentation

2Adaptability or versatility

If multiple rules engines with different syntaxes are supported, then adaptability is improved, but ease of operation deteriorates due to the need for engine-specific knowledge

Engineering Contradiction:
Improvesupport for multiple rules enginesVSAvoidease of rule execution
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The platform syntax serves as a universal interface that can define rules for multiple different rules engines. This multi-functional approach allows a single standardized syntax to work across various engines, with the system automatically adapting to the target engine's requirements through translation.

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

Solution Approach 2:

The translation mechanism acts as an intermediary that shields users from engine-specific syntax variations. Users interact only with the standardized platform syntax, while the system handles the complexity of translating to appropriate engine-specific syntaxes based on the target engine.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Productivity

If automated translation from platform syntax to engine syntax is implemented, then productivity is improved, but device complexity increases

Engineering Contradiction:
Improveefficiency of rule executionVSAvoidcomplexity of translation system
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system performs preliminary translation of rules from platform syntax to engine-specific syntax before execution. This advance translation prepares the rules in advance for the target engine, improving execution efficiency while the translation complexity is managed separately during the rule definition phase.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS9412071B2Rules execution platform system and method
Publication Date: 2016.08.09 COMPUTER SCIENCES CORP
  • US9412071B2 patent drawing
  • US9412071B2 patent drawing
  • US9412071B2 patent drawing

AI summary

Methods, mediums, and systems are described for providing a platform coupled to one or more rules engines. The platform may provide runtime rule services to one or more applications. Different rules engines may be used for different types of rules, such as calculations, decisions, process control, transformation, and validation. Rules engines can be added, removed, and reassigned to the platform. When the platform receives a request for services from an application, the platform selects one of the rules engines to handle the request and instructs the selected rules engine to execute the rule. The rules engine may be selected automatically. The platform may be implemented through a service-oriented architecture.