Train Boot Partition Redundancy for Reliable Startup
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing electronic equipment for railway systems faces challenges in restarting efficiently due to the large memory space occupied by boot partitions, which can complicate the boot process and reduce reliability.
Innovation Solution
The implementation of redundant boot partitions with a minimal kernel and optimized memory management, including a primary launch module, network configuration manager, and request manager, allows for efficient integrity checks and selective booting from healthy partitions, minimizing memory usage and ensuring reliable startup.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If boot partitions are made redundant to improve startup reliability, then the reliability of electronic equipment is improved, but the memory space occupied by boot partitions increases
Solution Approach 1:
The boot partition is segmented into two distinct components: a compact kernel (boot image) and a separate configuration file (config.txt). This segmentation allows the kernel to be minimized for space efficiency while the configuration file provides the flexibility to point to multiple boot partitions, thereby achieving both reduced memory occupation and improved startup reliability through redundancy.
Solution Approach 2:
The boot configuration information is extracted from the traditional boot partition structure and placed into a separate config.txt file. This extraction allows the kernel to remain minimal in size while the configuration file can reference multiple boot partitions, enabling redundancy without increasing the kernel's memory footprint.
2Reliability
If multiple boot partitions are implemented to improve startup robustness, then the probability of correct startup is improved, but the complexity of the boot process increases
Solution Approach 1:
The boot program implements self-service functionality by automatically reading the config.txt file, parsing the boot partition information, performing integrity checks on multiple partitions, and autonomously selecting a healthy partition for startup. This automation eliminates the need for manual intervention or complex external management, thereby improving startup robustness without proportionally increasing operational complexity.
Solution Approach 2:
The config.txt file is prepared in advance with all necessary boot partition information, including paths to multiple boot partitions and their integrity check values. This preliminary preparation allows the boot program to efficiently manage multiple partitions without requiring complex real-time decision-making, thereby enhancing startup robustness while keeping the boot process straightforward.
3Adaptability or versatility
If boot partitions occupy larger memory space to ensure complete functionality, then the functionality is improved, but the restarting efficiency is reduced
Solution Approach 1:
The boot system is segmented into a minimal kernel and a separate configuration file, allowing the kernel to occupy minimal memory space while the configuration file provides the necessary functionality for managing multiple boot partitions. This segmentation maintains complete boot functionality while significantly improving restarting efficiency by reducing the memory footprint of the boot partition.
Solution Approach 2:
The system changes the parameter of memory occupation by separating the kernel from the configuration data. The kernel is minimized to essential functions only, while the configuration file stores the functional parameters (boot partition paths, integrity checks). This parameter change enables the system to maintain full functionality with reduced memory occupation, thereby improving restarting efficiency.
Data Source
Figure 1~2
Figure 3
Figure 4
AI summary
This electronic equipment (12), such as railway equipment, comprises: - a processor (22), - a memory unit (24), associated with the processor (22) and including: + a boot program (25), + at least one boot partition (26). Each boot partition (26) includes a kernel (40), a network configuration manager (42), and a request manager (44), the request manager (44) being configured to handle at least one request received from an electronic device external to the electronic equipment (12). The boot program (25) is configured to command, for one or more of the boot partitions (26), the launching of the kernel (40), the network configuration manager (42), and the request manager (44). The request manager (44) is configured so that, after its launch, it is capable of continuously receiving at least one request from the external device.