Docker Task Failover for Production Line Continuity

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Industrial control systems with integrated software/hardware failures lead to prolonged shutdowns and significant losses due to the need for system reinstallations, disrupting production line operations.

Innovation Solution

A system and method utilizing a server to monitor and distribute tasks between computer devices deployed with Docker, allowing normal operation continuity by transferring tasks via a distributed architecture when failures occur, and restoring device configurations using the FIDO device onboarding protocol.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a controller with software/hardware integration fails, then the production line must be shut down for system reinstallation and function resetting, but this causes significant losses and prolonged shutdown time

Engineering Contradiction:
Improvesystem reliabilityVSAvoidshutdown time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent segments the control system into independent functional modules running on separate computer devices. When one device fails, only that specific module needs replacement while other modules continue operating independently, eliminating the need to shut down the entire production line for system-wide reinstallation.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements preliminary action by maintaining a spare computer device with pre-installed control software and configurations. When a failure occurs, the spare device is ready for immediate deployment, eliminating the need for time-consuming on-site reinstallation and function resetting.

Inventive Principle:
Principle #10Preliminary action

2Ease of repair

If a controller with integrated software fails, then spare parts must be replaced, but the production line cannot continue operating immediately due to complex reinstallation requirements

Engineering Contradiction:
Improverepair simplicityVSAvoidproduction continuity
Core Design Contradiction:
Ease of repairVSProductivity

Solution Approach 1:

The patent uses copying by creating a virtual image of the control system on the spare computer device. The control software, configurations, and operational states are replicated in advance, allowing the spare device to be deployed as an exact functional copy without requiring complex reinstallation or reconfiguration processes.

Inventive Principle:
Principle #26Copying

3Ease of manufacture

If the production line shuts down for controller replacement, then hardware failures can be addressed, but task operation continuity is lost resulting in significant losses

Engineering Contradiction:
Improvehardware maintenanceVSAvoidproduction loss
Core Design Contradiction:
Ease of manufactureVSLoss of time

Solution Approach 1:

The patent segments the control system into independent functional modules distributed across multiple computer devices. This allows hardware maintenance on one device to be performed without affecting other modules, enabling continuous production operations while individual components are being serviced or replaced.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS20250370889A1System and method for maintaining task operation continuity
Publication Date: 2025.12.04 ASROCK IND COMPUTER CORP
  • US20250370889A1 patent drawing
  • US20250370889A1 patent drawing
  • US20250370889A1 patent drawing

AI summary

Provided are a system and a method for maintaining task operation continuity. The system includes a server that communicatively coupled to a first computer device and a second computer device. The server is configured to monitor an operating status of each of the first computer device and the second computer device, in which each of the first computer device and the second computer device is at least deployed with a first task on Docker, and the first task is assigned to be run by the first computer device, and in response to determining that the first computer device cannot operate normally, assign the first task to the second computer device that is operating normally to run through a distributed architecture.