Controller for Distributed Computing State Management

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Distributed computing systems face challenges in maintaining coherent and consistent operation states across multiple components due to complex dependencies, requiring efficient mechanisms to manage state transitions and ensure overall system integrity.

Innovation Solution

A computer-implemented method and apparatus that utilize a controller to manage the state of distributed computing system components by defining a system hierarchy, state models, and execution dependencies, allowing for automatic sequencing of operations to maintain system coherence and consistency, with a controller receiving requests to place components into desired states.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual management of component states is used in distributed computing systems, then flexibility in operation is maintained, but system coherence and consistency deteriorate due to complex dependencies

Engineering Contradiction:
Improvesystem coherenceVSAvoiddependency management complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces a controller as an intermediary component that manages state transitions of distributed system components. The controller receives requests to place components in desired states, determines appropriate transition sequences based on defined dependencies, and coordinates the transitions to maintain system coherence. This mediator approach resolves the contradiction by automating dependency management while preserving operational flexibility.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system performs preliminary actions by pre-defining execution dependencies and transition sequences between component states. Before actual state transitions occur, the dependency relationships are established and stored, allowing the controller to automatically determine the correct transition sequence without manual intervention during operation. This preliminary structuring reduces runtime complexity while ensuring reliability.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If automated state transition management is implemented, then system consistency is improved, but control flexibility is reduced

Engineering Contradiction:
Improvestate consistencyVSAvoidoperational flexibility
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The patent implements dynamic state transition management where the controller adapts transition sequences based on current system state and defined dependencies. Rather than rigid predetermined sequences, the system dynamically determines the appropriate transition path by evaluating component states and dependency relationships in real-time. This dynamic approach maintains automated consistency while preserving operational flexibility.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The controller employs feedback mechanisms by continuously monitoring component states and using this information to determine appropriate transition sequences. The system receives feedback about current states, compares them against desired states, and automatically adjusts the transition plan based on dependency definitions and current conditions. This feedback loop ensures consistency while maintaining adaptability to changing operational requirements.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS8935371B2Hierarchical system operation in an adaptive computing environment
Publication Date: 2015.01.13 SAP SE
  • US8935371B2 patent drawing
  • US8935371B2 patent drawing
  • US8935371B2 patent drawing

AI summary

Methods and apparatus, including computer program products, are provided for controlling the state of components of a system. In one aspect, there is provided a computer-implemented method. The method may include receiving a request to place a system into a state. The system may include one or more components of a distributed computing system. A controller may place, based on a defined structure for the system, the one or more components into the state by sending one or more messages to the one or more components. Related apparatus, systems, methods, and articles are also described.