Client-Triggered Redundant Control for Automation Failover
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current distributed automation systems face challenges in maintaining seamless operation during communication channel failures or infrastructure malfunctions, particularly in real-time critical applications, as they require specialized network infrastructure for redundancy and may not efficiently switch between computing resources.
Innovation Solution
A method for redundant control in distributed automation systems, where a client device monitors communication faults and instructs a secondary computing infrastructure to take over, enabling active or passive redundancy without requiring special network infrastructure, allowing for quick resource allocation and efficient recovery.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If redundancy is supported within private infrastructure or at network level, then reliability is improved, but device complexity and infrastructure requirements increase
Solution Approach 1:
The client device autonomously monitors its own operational status and communication channels, detecting faults without requiring external monitoring infrastructure. The device independently activates standby computing resources when faults are detected, eliminating the need for complex centralized redundancy management systems while maintaining high reliability
Solution Approach 2:
Instead of having the network infrastructure or computing infrastructure actively monitor and manage redundancy, the patent inverts the approach by having the client device itself perform monitoring and trigger redundancy activation. This shifts the complexity from infrastructure to endpoint, simplifying overall system architecture while achieving the same reliability goals
2Reliability
If special network infrastructure is used for redundancy, then reliability is improved, but ease of manufacture and deployment worsen
Solution Approach 1:
The patent enables standard computing infrastructure to serve dual purposes: normal operational computing and standby redundancy. The same computing resources can function as primary or backup depending on activation status, eliminating the need for specialized redundant hardware infrastructure and simplifying deployment to existing standard facilities
Solution Approach 2:
The client device acts as an intermediary that coordinates between communication channels and computing infrastructure without requiring special network infrastructure. It monitors communication health and triggers computational redundancy activation, serving as a simple mediator that connects standard communication and computing resources to achieve reliability
3Reliability
If computing resources are permanently allocated for redundancy, then reliability is improved, but loss of energy and resource efficiency worsen
Solution Approach 1:
The patent implements dynamic redundancy activation where standby computing resources remain dormant during normal operation and are activated only when faults are detected. This dynamic switching allows the system to maintain reliability through available backup resources while avoiding continuous energy consumption, as resources are only actively used when needed
Solution Approach 2:
The system discards the use of standby computing resources during normal operation to conserve energy, recovering and activating them only when communication faults or infrastructure failures occur. This approach maximizes resource efficiency by ensuring backup resources serve their redundancy purpose only when actually needed, rather than consuming energy continuously
Data Source
AI summary
A method for redundant control in a distributed automation system, preferably a real-time automation system, for operating a client device of the distributed automation system is discussed. The method includes using the client device to monitor for the occurrence of a fault in communication between the client device and a first computing infrastructure that is part of the distributed automation system and operates the client device. The method may also include using the client device, once the fault occurs, to instruct a second computing infrastructure of the distributed automation system to operate the client device.