Hierarchical Rule Merging for Enterprise Software Conflict Resolution

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

The existing systems for delivering software content to enterprises face conflicts and contradictions in rule sets due to changes made by different entities in the software distribution chain, leading to operational issues and potential termination of applications, necessitating a method to identify and resolve rule conflicts and merge enhanced rules with previous rules.

Innovation Solution

A system and method that determine differences between initial and enhanced content data, identify the issuer status, and incorporate enhanced data into a production table to create a revised rule set, ensuring proper operation by establishing an issuer hierarchy and precedence to manage rule changes and updates effectively.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If rule content is changed by multiple entities (developer, vendor, customer) in the software distribution chain, then the rule set becomes more customized and adaptable to specific needs, but conflicts and contradictions arise between different rule versions

Engineering Contradiction:

Improverule customizationVSAvoidrule conflict

Core Design Contradiction:

Adaptability or versatilityVSReliability

Solution Approach 1:

The patent segments the rule set into multiple hierarchical layers (developer layer, vendor layer, customer layer), where each layer can independently define and modify rules without affecting others. This segmentation allows simultaneous customization at different levels while maintaining system integrity through layer isolation.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent implements a nested hierarchical structure where rules from different entities are organized in nested layers. The customer layer nests within the vendor layer, which nests within the developer layer, allowing each entity's customizations to coexist in a structured manner with clear precedence relationships.

Inventive Principle:

Principle #7Nested doll (Nesting)

2Adaptability or versatility

If rule content is updated with new releases over time, then the software remains current with business requirements and legal changes, but existing customizations from lower layers may be disturbed or overwritten

Engineering Contradiction:

Improverule update capabilityVSAvoidcustomization stability

Core Design Contradiction:

Adaptability or versatilityVSStability of the object's composition

Solution Approach 1:

The patent establishes a predetermined hierarchical structure and conflict resolution mechanism before rule conflicts occur. The system pre-defines the precedence order (customer > vendor > developer) and automatically applies this hierarchy during rule merging, eliminating the need for manual conflict resolution when updates occur.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The patent implements dynamic rule merging where the system automatically detects and resolves conflicts between different rule layers based on the hierarchical structure. When new releases are applied, the system dynamically adjusts the rule set by merging updates while preserving lower-layer customizations that do not conflict with higher-layer requirements.

Inventive Principle:

Principle #15Dynamics

3Device complexity

If conflicts between rule versions are not resolved, then the system maintains all original rule sets, but application execution may be prevented or terminated due to contradictory rules

Engineering Contradiction:

Improverule set completenessVSAvoidapplication executability

Core Design Contradiction:

Device complexityVSEase of operation

Solution Approach 1:

The patent introduces a rule management system that acts as an intermediary between different rule layers. This intermediary automatically detects conflicts, applies the hierarchical precedence rules to resolve them, and generates a unified executable rule set, eliminating the need for manual intervention while ensuring application executability.

Inventive Principle:

Principle #24Intermediary (Mediator)

4Ease of operation

If a hierarchical structure with issuer precedence is implemented to manage rule conflicts, then rule changes can be managed systematically, but the system complexity increases

Engineering Contradiction:

Improverule managementVSAvoidsystem structure

Core Design Contradiction:

Ease of operationVSDevice complexity

Solution Approach 1:

The patent creates a universal hierarchical framework that can accommodate any number of entities (developers, vendors, customers) and any type of rule modifications. This single multi-functional structure handles all rule management tasks including conflict detection, resolution, merging, and execution, replacing multiple separate management mechanisms.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Data Source

PatentUS8433664B2Method and system for enhancing and merging computer object rules

Publication Date: 2013.04.30 SAP SE

AI summary

A method, a machine-readable storage medium and a system are provided for revising content in a computer rule set. The revisions may be made by an issuer of content. In an embodiment, it is determined whether a difference exists between content data in a production table corresponding to a computer rule set and enhanced content data in an enhanced data table. If a difference is determined to exist, the content data is read from the production table and the enhanced content data is read from the enhanced data table. The enhancement data is identified as that assigned to the first issuer. Whether the rule enhanced in the computer rule set is allowed to be revised is confirmed. Based on the results of the determining and confirming, the enhanced data from the enhanced data table is incorporated into the production data table to provide a revised computer rule set.