Hierarchical Node Execution Pattern for Dependency Management

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Modern computing systems face challenges in effective communication and coordination between multiple components, leading to inefficiencies in performing complex tasks without a robust means of dependency management between application nodes.

Innovation Solution

A system is developed where application nodes are arranged in a hierarchical structure with a request-response mechanism, allowing dependent nodes to perform tasks sequentially, with a dependency evaluator determining necessary nodes and a request engine providing requests to the lowest level nodes, and a response engine combining responses from higher-level nodes.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If multiple application nodes are used to perform complex tasks, then task functionality and versatility are improved, but communication coordination complexity and system complexity increase

Engineering Contradiction:
Improvetask functionalityVSAvoidcommunication coordination complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system segments the complex task execution into multiple application nodes arranged in a hierarchical structure, where each node performs specific sub-tasks. The dependency evaluator further segments the coordination complexity by identifying and evaluating dependencies between nodes, allowing independent execution of non-dependent nodes while maintaining proper coordination through the hierarchical arrangement.

Inventive Principle:
Principle #1Segmentation

2Reliability

If a hierarchical structure with dependency evaluation is implemented, then task execution coordination is improved, but system complexity and processing overhead increase

Engineering Contradiction:
Improvetask execution coordinationVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The dependency evaluator performs preliminary action by evaluating and determining the dependency relationships between application nodes before task execution begins. This preliminary evaluation creates a structured hierarchy that guides subsequent task allocation and execution, ensuring proper coordination without requiring complex real-time negotiation between nodes during task performance.

Inventive Principle:
Principle #10Preliminary action

3Reliability

If requests are propagated through multiple hierarchical levels, then proper dependency management is achieved, but response time and execution duration increase

Engineering Contradiction:
Improvedependency managementVSAvoidresponse time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary action by pre-establishing the hierarchical structure and dependency relationships between nodes. This allows requests to be efficiently routed through the predetermined hierarchy without requiring complex real-time dependency resolution, reducing response time while maintaining proper dependency management.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system introduces a hierarchical dimension to organize application nodes, transforming the flat communication model into a multi-level structure. This dimensional change allows requests to flow efficiently through defined paths in the hierarchy, reducing the complexity of coordination and improving response time compared to unstructured peer-to-peer communication.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

Data Source

PatentUS8484657B2Network execution pattern
Publication Date: 2013.07.09 SAP SE
  • US8484657B2 patent drawing
  • US8484657B2 patent drawing
  • US8484657B2 patent drawing

AI summary

A plurality of nodes may be arranged within a hierarchy to perform actions, each node may perform a task associated an action. A dependency evaluator may determine, based on a request to perform an action, the first subset of the nodes configured to perform the action, wherein a first node of a higher level of the hierarchy is dependent upon a response from a second node of a lower level of the hierarchy to perform a task associated with the action. A request engine may provide the request to a lowest level of the hierarchy, wherein the second node of the lowest level may perform a task associated with the requested action and respond to the dependent first node. A response engine may receive the response from one of the nodes on a highest level of the hierarchy, including a performance of the tasks and the requested action.