Dynamic Firmware Updating System Without Reboot

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

In large-scale computing environments, updating firmware typically requires restarting the system, which can be time-consuming and disrupts critical workloads, and existing methods fail to preserve the system state during the update process.

Innovation Solution

A method that involves building an initial stack, quiescing I/O operations, suspending execution of all but one firmware module, updating the remaining module, and initiating execution of the updated module without rebooting the system, allowing for seamless firmware updates while maintaining the system's state.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If firmware is updated by overwriting existing firmware and restarting the system, then the firmware update is complete and functional, but the system experiences long downtime and workload interruption

Engineering Contradiction:

Improvefirmware update completenessVSAvoidsystem downtime

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The system divides firmware into multiple segments or images that can be loaded and executed separately. Instead of replacing all firmware at once requiring a full restart, the updated firmware segments are loaded incrementally while the system continues to operate on remaining original firmware segments, thereby reducing downtime and avoiding complete workload interruption.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The updated firmware is prepared and validated in advance before being activated. The system loads the updated firmware image into memory and performs preliminary checks to ensure compatibility and integrity. This preliminary action allows the system to switch to updated firmware without requiring a full restart, as the updated firmware is already in readiness state.

Inventive Principle:

Principle #10Preliminary action

2Reliability

If firmware is updated by restarting the computing system, then the new firmware takes control of hardware resources, but the system state is not preserved and workloads may be lost or need reexecution

Engineering Contradiction:

Improvefirmware update effectivenessVSAvoidworkload state

Core Design Contradiction:

ReliabilityVSLoss of information

Solution Approach 1:

The system creates a copy of the updated firmware in memory while the original firmware continues to execute. This copy can be activated selectively for specific hardware resources or partitions without affecting the overall system state. The workload state is preserved because the system transitions from one firmware copy to another rather than performing a complete restart that would lose in-memory state.

Inventive Principle:

Principle #26Copying

Solution Approach 2:

The firmware update process is made dynamic and flexible, allowing the system to switch between original and updated firmware segments on-the-fly based on operational requirements. Rather than a static all-or-nothing update requiring system restart, the dynamic approach enables selective activation of updated firmware while maintaining system continuity and preserving workload state.

Inventive Principle:

Principle #15Dynamics

3Reliability

If firmware update requires complete system shutdown and restart, then all firmware modules are updated uniformly, but critical workloads are interrupted for extended periods

Engineering Contradiction:

Improvefirmware update uniformityVSAvoidworkload execution continuity

Core Design Contradiction:

ReliabilityVSProductivity

Solution Approach 1:

The firmware update process is segmented to allow different parts of the system to be updated at different times. Critical workloads can continue to run on firmware segments that have not yet been updated, while non-critical functions can transition to updated segments. This segmentation maintains firmware update uniformity within each segment while preserving overall system productivity and workload continuity.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The system maintains continuous operation of critical workloads during the firmware update process by keeping them running on stable, unupdated firmware segments. The update process occurs in the background or during non-critical periods, ensuring that useful actions (workload execution) continue uninterrupted while firmware updates are applied to non-critical components or scheduled during maintenance windows.

Inventive Principle:

Principle #20Continuity of useful action

Data Source

PatentUS8972964B2Dynamic firmware updating system for use in translated computing environments

Publication Date: 2015.03.03 UNISYS CORP

AI summary

Systems and methods for updating firmware executing on a computing system are disclosed. One method includes building an initial stack for use by an updated firmware module, and quiescing I/O operations occurring on the computing system. The method also includes halting all but a remaining firmware module from among one or more firmware modules to be updated and that are executing on the computing system, and, with the remaining firmware module executing on the computing system, indicating to perform a firmware update. The method further includes halting execution of a partition including the remaining firmware module. The method also includes updating the remaining firmware module executing on the computing system with the updated firmware module, and initiating execution of the updated firmware module using the initial stack.