Predefined Failover Configurations for Node Failure Recovery

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing autonomous vehicle systems face challenges in efficiently handling fault state transitions, particularly in maintaining operational reliability and redundancy in the event of node failures within the computing system.

Innovation Solution

Implementing a redundant architecture with switched fabrics for power and data pathways, along with dynamic reconfiguration of CPU packages and virtual machines to ensure continuous operation by reallocating processes and maintaining communication between sensors and CPU packages.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a node in the computing system fails, then system reliability deteriorates, but implementing redundant architecture and dynamic reconfiguration increases device complexity

Engineering Contradiction:
Improvesystem reliabilityVSAvoiddevice complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The computing system is segmented into multiple independent nodes (CPU packages, virtual machines, processes) that can operate independently. When one node fails, others continue functioning, maintaining system reliability without requiring complete system redundancy.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system pre-configures multiple virtual machines and process allocations across different CPU packages before failures occur. This preliminary arrangement enables immediate failover to alternative configurations, ensuring reliability while managing complexity through pre-planned redundancy rather than ad-hoc responses.

Inventive Principle:
Principle #10Preliminary action

2Productivity

If dynamic reconfiguration is implemented to maintain operation after node failure, then productivity is maintained, but device complexity increases

Engineering Contradiction:
Improveoperational continuityVSAvoidreconfiguration complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system implements dynamic reconfiguration capabilities where virtual machine allocations and process assignments can be automatically adjusted in response to node failures. This dynamic adaptation maintains productivity by ensuring continuous operation through automated redistribution of computational tasks to available nodes.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The computing system performs self-diagnosis and self-reconfiguration when node failures are detected. The system automatically identifies failed nodes, determines appropriate alternative configurations, and executes reallocation without external intervention, maintaining productivity while managing complexity through automated self-management.

Inventive Principle:
Principle #25Self-service

3Reliability

If redundant pathways are implemented for power and data, then reliability improves, but loss of energy increases

Engineering Contradiction:
Improveoperational reliabilityVSAvoidenergy consumption
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The redundant power and data pathways are designed to serve multiple functions: they provide backup capacity during failures and enable load balancing during normal operation. This multi-functionality justifies the energy overhead by allowing the same redundant infrastructure to both maintain reliability and optimize performance under varying conditions.

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

Data Source

PatentUS12608288B1Fault state recovery using predefined configurations
Publication Date: 2026.04.21 APPLIED INTUITION INC
  • US12608288B1 patent drawing
  • US12608288B1 patent drawing
  • US12608288B1 patent drawing

AI summary

Fault state recovery using predefined configurations, including: determining that a first node of a plurality of nodes has failed; identifying, based on the first node failing, a failure state from a plurality of predefined failure states each corresponding to a different combination of one or more failed nodes, wherein each of the plurality of predefined failure states corresponds to a respective configuration of a plurality of configurations; and applying the respective configuration corresponding to the identified failure state, wherein applying the respective configuration comprises at least one of: updating one or more memory mapping tables based on the respective configuration or copying data from memory locations used based on a previous configuration to memory locations indicated in the respective configuration.