Conflict Resolution Manager for Dynamic Operation Routing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In computing systems, the management of operations among multiple control components (services, consoles, and plugins) leads to issues such as operation failures, duplicate operations, and performance by less capable components due to changes in workload and resource demands, lacking a standardized mechanism for coordination and privilege allocation.

Innovation Solution

A conflict resolution manager (CRM) dynamically registers and ranks control components based on operation capabilities, assigns priority weights, and allocates privileges to ensure the most capable component performs operations, considering current and historical workloads, resource availability, and configurations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If multiple control components are allowed to perform operations, then system versatility and capability are improved, but operation conflicts and duplicate operations occur

Engineering Contradiction:
Improvecontrol component capabilityVSAvoidoperation success rate
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent introduces a conflict resolution manager (CRM) as an intermediary component that mediates between multiple control components competing to perform operations. The CRM receives operation requests, determines which control component should execute each operation based on conflict resolution logic, and routes operations accordingly. This mediator prevents direct conflicts between control components while maintaining the ability of multiple components to perform different operations, thus preserving versatility while improving reliability.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If control components are dynamically selected based on workload, then operation efficiency is improved, but system complexity increases

Engineering Contradiction:
Improveoperation execution efficiencyVSAvoidoperation management complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent segments the operation management function into distinct modular components: a conflict resolution manager for determining operation routing, workload monitors for tracking component status, and priority managers for setting execution priorities. Each module has a specific, well-defined responsibility. This segmentation allows the system to implement dynamic workload-based selection without creating monolithic complexity, as each segment can be independently managed and understood.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system implements dynamic control component selection based on real-time workload conditions, component availability, and operation priorities. The conflict resolution manager continuously evaluates current system state and adjusts operation routing decisions dynamically rather than using static assignments. This dynamic approach optimizes execution efficiency while the modular architecture keeps management complexity tractable through structured adaptability.

Inventive Principle:
Principle #15Dynamics

3Measurement precision

If priority weights are assigned to control components, then operation routing precision is improved, but computational overhead increases

Engineering Contradiction:
Improvecomponent selection accuracyVSAvoidcomputational resource consumption
Core Design Contradiction:
Measurement precisionVSUse of energy by moving object

Solution Approach 1:

The patent uses priority weights as adjustable parameters that quantify the relative preference for selecting specific control components under different conditions. These priority weights are set based on workload characteristics, component capabilities, and operation types. By changing these parameters dynamically, the system achieves precise control over operation routing decisions without requiring complex computational models, thus improving selection accuracy while maintaining reasonable computational overhead.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS20240231895A9Context-aware operation routing for dynamic work-flow layering
Publication Date: 2024.07.11 DELL PROD LP
  • US20240231895A9 patent drawing
  • US20240231895A9 patent drawing
  • US20240231895A9 patent drawing

AI summary

Technology described herein relates to management of operational execution by one or more plugins, services and/or consoles of a computing system. A method can comprise registering, by a conflict resolution manager (CRM) controller of a system, a subset of control components of a set of control components of the system, wherein the registering comprises logging operation capabilities of the subset of control components, ranking, by the CRM controller, respective control components of the subset, wherein the ranking is performed based on an operation comprised by the operation capabilities, and generating, by the CRM controller, a permission for performance of the operation by a selected control component of the subset having a highest rank determined by the ranking. The control components can comprise a plugin of, or to be installed at, at least one of the system or a management console of the system, which can be a computing system.