Distributed Processing Orchestration With Node-Level Failure Handling

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing orchestration frameworks for distributed systems lack the necessary mechanisms to enforce real-time, reliability, and safety guarantees required for real-time/safety-critical applications, leading to potential violations of timing constraints and single points of failure.

Innovation Solution

An orchestration device that deploys failure handling software modules directly on processing nodes, enabling real-time reaction mechanisms and fault tolerance without relying on a central orchestrator, allowing for autonomous handling of failures and maintaining real-time operation.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If a central orchestrator is used to manage applications and resources, then system coordination and resource management is improved, but real-time reaction capability and system reliability deteriorate due to single point of failure and communication latency

Engineering Contradiction:
Improvesystem coordinationVSAvoidsystem reliability
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent segments the centralized orchestrator into distributed failure handling software modules deployed autonomously on processing nodes. Each module independently handles failures locally without requiring continuous communication with a central orchestrator, eliminating the single point of failure while maintaining coordinated failure handling through the shared failure specification.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The failure handling software modules are designed to operate autonomously on processing nodes, self-managing failure detection and response without external orchestrator intervention. The modules use the shared failure specification to determine appropriate responses, enabling self-service operation that improves reliability while maintaining system coordination.

Inventive Principle:
Principle #25Self-service

2Reliability

If failure handling software modules are deployed autonomously on processing nodes, then real-time reaction capability and system reliability are improved, but device complexity increases due to additional software components

Engineering Contradiction:
Improvefault toleranceVSAvoidsoftware complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The failure handling software modules are designed as universal components that can be deployed on any processing node and handle multiple failure types according to the shared failure specification. This multi-functionality reduces overall system complexity by using standardized modules rather than node-specific failure handling code.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The system manages complexity by parameterizing failure handling behavior through the shared failure specification, which defines failure types and handling strategies. The actual implementation details are encapsulated in the software modules, allowing complexity to be managed at the parameter level rather than the implementation level.

Inventive Principle:
Principle #35Parameter changes

3Adaptability or versatility

If the orchestrator is deployed remotely, then system scalability and deployment flexibility are improved, but real-time operation and timing constraints may be compromised due to communication latency

Engineering Contradiction:
Improvedeployment flexibilityVSAvoidreaction speed
Core Design Contradiction:
Adaptability or versatilityVSSpeed

Solution Approach 1:

The patent extracts real-time failure handling functionality from the remote orchestrator and embeds it directly in the processing nodes through autonomous software modules. This extraction of time-critical functions to the edge nodes eliminates communication latency while the orchestrator maintains remote deployment flexibility for non-time-critical orchestration tasks.

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentUS20250298689A1Orchestration device for a distributed processing system
Publication Date: 2025.09.25 ROBERT BOSCH GMBH
  • US20250298689A1 patent drawing
  • US20250298689A1 patent drawing
  • US20250298689A1 patent drawing

AI summary

An orchestration device for a distributed processing system. The orchestration device includes an input interface configured to receive a specification of a data processing task to be performed by the distributed processing system and of one or more failure types that the data processing system should be able to handle when performing the data processing task, and a command interface configured to instruct each of a plurality of processing nodes of the distributed processing system to perform at least one respective sub-task of the data processing task and instruct each of at least some of the plurality of processing nodes to implement one or more failure handling software modules which are configured to handle failures of the specified failure types.