Rule Framework Inversion for Deterministic Conflict Resolution

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Developers face challenges in managing custom rules within software frameworks, where different input values can lead to the same output value, causing conflicts and errors, and determining all possible inputs leading to a specific output is difficult and time-consuming.

Innovation Solution

A system converts software rules into an inverted form, storing both the original and inverted versions, allowing for deterministic execution by mapping each output value to its associated conditions, thereby eliminating conflicts and improving performance.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If developers create custom rules with different input values mapping to the same output value, then the software can handle diverse customer requirements, but rule conflicts occur and execution becomes error-prone

Engineering Contradiction:
Improvecustom rule flexibilityVSAvoidrule execution reliability
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent inverts the traditional rule execution approach by pre-calculating and storing all possible input-output mappings during rule creation. Instead of executing rules at runtime to determine outputs, the system stores deterministic mappings that directly provide outputs for any given input, eliminating execution conflicts and errors while maintaining full rule flexibility

Inventive Principle:
Principle #13The other way round (Inversion)

2Reliability

If developers execute rules periodically to test for conflicts, then rule interactions can be detected, but the process becomes time-consuming and expensive

Engineering Contradiction:
Improverule conflict detectionVSAvoidtesting time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent performs conflict detection and resolution in advance during rule creation and activation. The system pre-calculates all possible input-output mappings and stores them in a deterministic structure, eliminating the need for periodic testing. This preliminary action ensures rule reliability is established upfront rather than through repeated execution and validation cycles

Inventive Principle:
Principle #10Preliminary action

3Measurement precision

If all rules are executed to retrieve output for a given input, then complete rule evaluation is performed, but system performance deteriorates

Engineering Contradiction:
Improverule evaluation completenessVSAvoidsystem performance
Core Design Contradiction:
Measurement precisionVSProductivity

Solution Approach 1:

The patent extracts the essential input-output mappings from rule execution and stores them in a deterministic structure. Instead of executing all rules during runtime, the system retrieves pre-stored mappings that directly provide the output for any given input. This extraction eliminates unnecessary rule execution overhead while maintaining complete and accurate rule evaluation

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentUS12411682B2Inversion process for rules framework
Publication Date: 2025.09.09 SAP SE
  • US12411682B2 patent drawing
  • US12411682B2 patent drawing
  • US12411682B2 patent drawing

AI summary

Provided is a system and method for inverting custom rules of a software program to ensure compatibility with other possible rules of the software program. The inverted rules are always stored in a unified format. In one example, the method may include detecting a custom rule within a software program. The custom rule may include one or more input values, one or more output values, and a plurality of conditions for converting the one or more input values into the one or more output values, The method may also include generating an inverse of the custom rule, wherein the inverse of the custom rule comprises a plurality of inverse statements, and each inverse statement includes an output value mapped to an input value and a different condition among the plurality of conditions. The method may also include updating a rules repository associated with the software program with the inverse of the custom rule.