Firmware Patching with Reserved Memory for Reboot-Free Updates

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Modern computer systems face security vulnerabilities due to firmware attacks, leading to revenue loss, productivity loss, and data leaks, and existing firmware update methods are cumbersome, risking system failure and user hesitation.

Innovation Solution

A method and apparatus for firmware patching that allows updates to be tested and stored in reserved memory before being written to nonvolatile memory, enabling seamless updates without rebooting the system, using a system-on-a-chip architecture with a security controller and update agent to manage firmware updates in a protected memory environment.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If firmware updates are applied directly to production systems, then security vulnerabilities can be mitigated, but system stability and reliability deteriorate due to risk of update failures

Engineering Contradiction:
Improvesystem stabilityVSAvoidsecurity vulnerabilities
Core Design Contradiction:
ReliabilityVSObject-affected harmful factors

Solution Approach 1:

The patent segments firmware into multiple images stored in different memory regions (first firmware image in first memory region, second firmware image in second memory region). This allows the system to maintain a backup firmware image while applying updates, thereby mitigating security vulnerabilities without compromising system stability through direct in-place updates.

Inventive Principle:
Principle #1Segmentation

2Reliability

If firmware updates are tested extensively before deployment, then reliability improves, but update time and complexity increase

Engineering Contradiction:
Improveupdate success rateVSAvoidupdate time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent performs preliminary actions by storing multiple firmware images in advance in different memory regions and validating their integrity before deployment. The system checks checksums and validates firmware images beforehand, so that when an update is needed, the pre-validated firmware can be quickly switched to without extensive testing during the actual update process.

Inventive Principle:
Principle #10Preliminary action

3Manufacturing precision

If firmware updates require system reboots, then update completeness improves, but productivity and availability deteriorate due to downtime

Engineering Contradiction:
Improveupdate completenessVSAvoidsystem availability
Core Design Contradiction:
Manufacturing precisionVSProductivity

Solution Approach 1:

The patent introduces a firmware switch mechanism as an intermediary between the firmware update process and system operation. The firmware switch can selectively execute different firmware images without requiring system reboots, allowing updates to be applied while maintaining system availability and productivity.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Ease of operation

If firmware updates are simplified and automated, then ease of operation improves, but security control and validation may be compromised

Engineering Contradiction:
Improveupdate simplicityVSAvoidsecurity validation
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent implements self-service mechanisms where the system automatically validates firmware images through checksum verification, compares multiple firmware images for consistency, and performs integrity checks without requiring manual intervention. This automation maintains security validation rigor while improving ease of operation.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS12578956B2Method and apparatus for firmware patching
Publication Date: 2026.03.17 INTEL CORP
  • US12578956B2 patent drawing
  • US12578956B2 patent drawing
  • US12578956B2 patent drawing

AI summary

A method of handling a firmware update for a device is disclosed, comprising: determining a device to be in an updatable state; setting the device into an updating state after determining the updatable state; and after the device is in the updating state, writing a firmware update to memory for the device. After writing the firmware update, the device is switchable to a working state in which the device operates based on the firmware update.