Multiple Domain Embedded System Firmware Update Isolation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing firmware update mechanisms for multiple domain embedded systems are inefficient, as they often update all domains simultaneously, which can lead to errors and impair other system functions, especially when only certain domains require updates.
Innovation Solution
A system that identifies connected devices, determines affected domains, and updates only the necessary drivers by transferring configuration labels and binary data through a configuration database, ensuring that only the affected domains are updated, while others remain unchanged.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of manufacture
If all domains are updated simultaneously during firmware update, then the update process is simple to implement, but errors occur and other system functions are impaired
Solution Approach 1:
The patent segments the firmware update process by domain, creating separate update operations for each domain rather than a single bulk update. The system identifies affected domains through configuration labels and updates only those specific domains, isolating the update process to prevent errors from propagating across the entire system.
Solution Approach 2:
The patent implements partial action by updating only the necessary domains that are affected by the firmware change, rather than updating all domains. The system determines the minimal set of affected domains through configuration label analysis and performs updates selectively, avoiding unnecessary updates to unaffected domains.
2Reliability
If only necessary domains are updated, then system reliability is improved, but the update process complexity increases
Solution Approach 1:
The patent performs preliminary action by analyzing configuration labels before the actual update to identify which domains are affected. The system prepares a list of affected domains in advance by comparing configuration labels, so that only the necessary domains are selected for update, avoiding the need for complex runtime decision-making during the update process.
Solution Approach 2:
The patent introduces configuration labels as an intermediary mechanism to bridge the firmware update process and domain identification. The configuration labels serve as a mediator that automatically maps firmware changes to affected domains, simplifying the update process by providing a clear interface between the update operation and domain selection.
3Manufacturing precision
If configuration labels are used to identify affected domains, then update precision is improved, but information processing requirements increase
Solution Approach 1:
The patent uses configuration labels as a simplified copy or representation of the complex domain-firmware relationships. Instead of processing entire domain configurations or firmware structures, the system works with compact configuration label data that captures the essential mapping information, reducing data processing requirements while maintaining identification precision.
Data Source
AI summary
A system for updating a multiple domain embedded system may include a processor that can identify a device associated with the embedded system and a driver that supports the device. The processor can determine a domain associated with the driver and a first configuration label of a first configuration of the multiple domain embedded system. The processor can also determine a second configuration label of a second configuration of the multiple domain embedded system, based on the first configuration label, an identification of the driver, and an identification of the device. Further, the processor can update the driver based on the second configuration label.