Distributed Error Correction Architecture for Node Failure Recovery

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Industrial systems face challenges in managing complex IoT devices and software-defined technologies due to heterogeneity, limited flexibility, and high costs, leading to slow and costly updates, and reluctance in adopting new technologies, which hinders the wide-scale deployment of IoT and software-defined technologies in industrial settings.

Innovation Solution

The implementation of a software-defined industrial system (SDIS) with dynamic configuration and re-configuration capabilities through resource abstraction, open architectures, and integrated security features, enabling flexible updates and integration of new technologies without shutting down the system, using peer-to-peer networks for redundancy and orchestration, and leveraging edge and cloud computing for real-time operations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If incremental changes are attempted in industrial systems, then system updates become possible, but management complexity increases significantly

Engineering Contradiction:
Improvesystem update capabilityVSAvoidmanagement complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system segments industrial applications into modular containers that can be independently deployed, updated, and managed. Each container encapsulates specific functionality, allowing incremental changes without affecting the entire system. This modular architecture reduces management complexity by enabling targeted updates rather than system-wide changes.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements a universal container orchestration platform that can manage diverse industrial applications across different hardware platforms. The standardized container interface provides multi-functional capabilities for deployment, monitoring, and updates, reducing the need for platform-specific management procedures and thereby decreasing overall management complexity.

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

2Adaptability or versatility

If new technologies are adopted in industrial systems, then system capabilities improve, but reliability becomes unproven

Engineering Contradiction:
Improvenew technology integrationVSAvoidtechnology reliability
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The system implements redundancy mechanisms where critical industrial applications are deployed in multiple container instances across different physical hosts. This beforehand cushioning ensures that if a new technology component fails, backup instances can take over, maintaining system reliability while allowing adoption of new technologies.

Inventive Principle:
Principle #11Beforehand cushioning (Prior cushioning)

Solution Approach 2:

The containerization approach creates portable, copyable application packages that can be replicated across multiple hosts. These copies ensure continuity of operation and provide failover capabilities, allowing reliable deployment of new technologies through verification on replicated instances before full production adoption.

Inventive Principle:
Principle #26Copying

3Adaptability or versatility

If IoT devices are physically heterogeneous, then device versatility increases, but device management becomes complex

Engineering Contradiction:
Improvedevice heterogeneityVSAvoiddevice management ease
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The patent introduces container runtimes and orchestration platforms as intermediary layers between heterogeneous IoT devices and the management system. These intermediaries standardize device interfaces and communication protocols, allowing diverse physical devices to be managed through unified software commands, thereby simplifying device management while preserving hardware versatility.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The containerization approach creates a homogeneous software environment that runs across heterogeneous hardware platforms. By standardizing the execution environment through containers, the system achieves operational homogeneity despite physical device diversity, making management easier while maintaining the ability to support various device types.

Inventive Principle:
Principle #33Homogeneity

4Productivity

If software is updated in statically configured systems, then system improvements are achieved, but system shutdown is required

Engineering Contradiction:
Improvesystem improvement rateVSAvoidsystem downtime
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The system implements dynamic container deployment and updating mechanisms that allow software changes without shutting down the industrial control system. Containers can be started, stopped, updated, and replaced while the underlying host system continues to operate, enabling continuous production and eliminating downtime associated with software updates.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The orchestration platform performs preliminary actions by preparing container updates in advance and deploying them to standby hosts before switching active services. This preliminary provisioning allows seamless updates where the new container instance is ready to take over immediately, preventing any interruption to system operation.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS11811903B2Distributed dynamic architecture for error correction
Publication Date: 2023.11.07 INTEL CORP
  • US11811903B2 patent drawing
  • US11811903B2 patent drawing
  • US11811903B2 patent drawing

AI summary

Various systems and methods may be used to implement a software defined industrial system. For example, an orchestrated system of distributed nodes may run an application, including modules implemented on the distributed nodes. The orchestrated system may include an orchestration server, a first node executing a first module, and a second node executing a second module. In response to the second node failing, the second module may be redeployed to a replacement node (e.g., the first node or a different node). The replacement mode may be determined by the first node or another node, for example based on connections to or from the second node.