Firmware Update Parity Reconstruction for Low-Downtime Deployment
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Traditional firmware updates in computing systems require multiple write operations, leading to prolonged system unavailability and increased storage costs due to the need for staging and maintaining additional copies of the updated firmware.
Innovation Solution
A system that optimizes firmware updates by comparing and computing parity values between current and updated firmware portions, storing only the parity values and differences, and using these to regenerate the updated firmware as needed, thereby reducing the number of write operations and storage requirements.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional firmware update method with multiple write operations is used, then firmware can be updated, but system downtime is prolonged and storage costs increase
Solution Approach 1:
The patent applies preliminary action by downloading and validating the firmware update package before the actual update is needed. The system retrieves the update package, verifies its integrity, and prepares it in advance, so that when an update is required, the system can apply it quickly without prolonged downtime. This is evident in the workflow where the system checks for available updates and prepares them before system restart.
Solution Approach 2:
The patent segments the firmware update process into distinct phases: download phase, validation phase, and application phase. By separating these operations, the system can perform lengthy download and validation tasks without keeping the system unavailable, and only requires brief downtime for the actual firmware application. This segmentation reduces the perceived system downtime while maintaining update reliability.
2Reliability
If traditional firmware update method with staging location is used, then firmware can be updated, but storage costs increase due to maintaining additional copies
Solution Approach 1:
The patent uses copying by downloading the firmware update package to a temporary location in volatile memory for validation and preparation. This temporary copy replaces the need for permanent staging storage, as the update package is discarded after successful application. The system maintains only the current operational firmware in non-volatile storage, not multiple copies as in traditional methods.
Solution Approach 2:
The patent changes the storage parameter from permanent non-volatile staging storage to temporary volatile memory storage. By utilizing volatile memory for the update package during preparation and validation, the system eliminates the need for dedicated staging storage space in the firmware storage medium, thereby reducing the quantity of storage space required while maintaining update reliability.
Data Source
AI summary
Examples of the present disclosure describe devices, systems, and methods for optimizing firmware updates. In examples, a firmware update system receives, in a volatile storage, an update to a stored firmware in a non-volatile storage. The update and the stored firmware comprise multiple portions that can be updated. The firmware update system identifies differences between each portion of the update and a corresponding portion of the stored firmware. Upon identifying a difference in corresponding portions, the firmware update system computes a parity value using the portion of the update and the corresponding portion of the stored firmware. The firmware update system then associates the parity value with the updated portion and stores the parity value and the association. After the comparison is completed and parity values are computed for all portions of the update, the update is copied to non-volatile storage to replace the previously stored firmware.