Firmware Image Generation via Differential Address Modification

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The existing systems for computing firmware, such as BIOS code, are vulnerable to tampering and errors, leading to compromised functionality, and traditional methods of updating or recovering firmware images face challenges due to physical address dependencies and limited memory space.

Innovation Solution

The implementation of differential data to modify physical addresses and content between firmware images, allowing for the creation of updated versions of firmware images from a single updated image, thereby enabling efficient recovery and updating without requiring duplicate images in memory.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If multiple BIOS code images are stored in computing system to allow for recovery from compromise, then system reliability is improved, but memory space consumption increases

Engineering Contradiction:
Improvesystem reliabilityVSAvoidmemory space
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The patent merges multiple BIOS code images by storing only one complete image and generating other images on-demand through differential data application. This combining approach maintains the reliability benefit of having multiple recoverable images while significantly reducing the memory space required, as the differential data occupies minimal space compared to full image duplication.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The patent creates a universal base BIOS image that can serve multiple purposes: it can be used directly as a functional image or serve as the foundation for generating multiple recovered images through differential data application. This multi-functionality allows a single stored image to fulfill the role of multiple images, resolving the contradiction between reliability and memory space consumption.

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Reliability

If traditional methods are used to update or recover firmware images, then system functionality is maintained, but the process becomes complex due to physical address dependencies

Engineering Contradiction:
Improvefirmware functionalityVSAvoidupdate process complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces differential data as an intermediary element that simplifies the update and recovery process. Instead of directly manipulating complex firmware images with physical address dependencies, the system applies compact differential data to base images to generate updated or recovered versions. This intermediary approach maintains functionality while reducing process complexity.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent changes the representation parameters of firmware updates by using differential data with modified physical addresses instead of complete image copies. This parameter change transforms the update process from complex image manipulation to simpler data application, maintaining reliability while reducing complexity.

Inventive Principle:
Principle #35Parameter changes

3Reliability

If complete firmware images are stored for recovery purposes, then recovery reliability is improved, but memory space is wasted

Engineering Contradiction:
Improverecovery reliabilityVSAvoidmemory space waste
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The patent extracts only the essential differential data from complete firmware images, separating the common base content from the unique recovery information. By storing only the extracted differential portions rather than complete images, the system maintains recovery reliability while eliminating memory space waste associated with storing redundant full image copies.

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentEP3028141B1Generating a second code from a first code
Publication Date: 2020.01.08 HEWLETT PACKARD DEVELOPMENT COMPANY LP
  • EP3028141B1 patent drawingFigure 1
  • EP3028141B1 patent drawingFigure 2
  • EP3028141B1 patent drawingFigure 3

AI summary

A second physical-address-dependent code is generated from a first physical-address-dependent code using differential data, where the generating comprises converting a first physical address in a region of the first physical-address-dependent code to a second, different physical address for inclusion in a corresponding region of the second physical-address-dependent code.