Application Module Mode Switching for High-Reliability Execution
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing systems face challenges in ensuring high-reliability applications execute correctly during emergency conditions when third-party applications are running concurrently, leading to increased cost and complexity due to the need for multiple microcomputers or complex hypervisor technologies.
Innovation Solution
A system with an application module that switches between normal and high-reliability modes, where the application module generates a message sequence, and a second module monitors this sequence to initiate a high-reliability boot if errors occur, ensuring only high-reliability applications are executed during emergencies.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If multiple microcomputers are used to separate high-reliability and third-party applications, then reliability is improved, but device complexity and cost increase
Solution Approach 1:
The patent segments the execution environment by creating distinct operational modes (normal mode and high-reliability mode) within a single microcomputer. The control module partitions the application execution space through mode switching, where high-reliability applications are isolated in a separate execution context during emergency conditions, eliminating the need for physical separation via multiple microcomputers while maintaining reliability guarantees.
Solution Approach 2:
The system dynamically switches between different operational modes based on system state. The microcomputer transitions from normal mode (executing both high-reliability and third-party applications) to high-reliability mode (executing only high-reliability applications) when emergency conditions are detected. This dynamic reconfiguration allows the system to adapt its execution environment in real-time, providing reliability isolation when needed without permanently increasing hardware complexity.
2Reliability
If hypervisor technology is implemented to separate operating systems, then reliability is improved, but device complexity and debugging difficulty increase
Solution Approach 1:
The patent extracts the complex hypervisor layer and replaces it with a simpler mode-switching mechanism. Instead of implementing a full virtualization layer that manages multiple operating systems with resource allocation and isolation, the system directly switches between operational modes that provide the necessary isolation. This extraction of the hypervisor function simplifies the system architecture while maintaining the ability to guarantee high-reliability application execution.
Solution Approach 2:
The system uses a simpler, lighter-weight mode-switching mechanism rather than a heavy hypervisor. The operational modes are implemented as software configurations that can be quickly switched between, avoiding the complexity of full operating system virtualization. This approach provides sufficient isolation and reliability guarantees without the overhead and complexity of hypervisor technology.
3Device complexity
If third-party applications are allowed to run concurrently with high-reliability applications, then cost and complexity are reduced, but reliability deteriorates
Solution Approach 1:
The system dynamically adjusts its application execution policy based on operational context. During normal conditions, both high-reliability and third-party applications can execute concurrently to maximize functionality. When emergency conditions are detected, the system transitions to high-reliability mode where third-party applications are suspended and only high-reliability applications execute, ensuring reliability guarantees without permanently reducing system functionality.
Solution Approach 2:
The system changes the execution parameter from 'concurrent execution of all applications' to 'exclusive execution of high-reliability applications' based on system state. By monitoring conditions and switching between operational modes, the system adapts its application execution parameters in real-time, allowing third-party applications to run during normal conditions while ensuring high-reliability applications execute exclusively during emergencies.
Data Source
AI summary
A system for executing a high-reliability application and a third party application is provided. The system includes an application module and a second module. The application module has control logic for executing the high reliability application and the third party application. The high reliability application generates a message sequence. The application module includes a normal operating mode, a high reliability mode, and a high reliability boot. The second module is in communication with the application module, and includes a first control logic for monitoring the message sequence when the application module is operating in the normal operating mode. The second module also includes control logic for initiating the high reliability boot in the application module.