Metadata Structure Migration for Firmware Version Compatibility

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Conventional firmware update systems face challenges in updating between non-subsequent versions, often resulting in incompatibility issues and a lack of downward compatibility, making it difficult to revert to previous versions or perform efficient metadata structure updates.

Innovation Solution

A metadata firmware update system that generates migration structures and arrays for respective versions of firmware, comparing attributes to ensure compatibility and iteratively perform necessary migration actions, reducing processing expenses and avoiding full reinitialization of metadata structures.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of time

If conventional firmware update systems skip intermediate versions to update from an older version to a newer version, then update time is reduced, but incompatibility issues arise and reliability deteriorates

Engineering Contradiction:

Improvefirmware update timeVSAvoidfirmware compatibility

Core Design Contradiction:

Loss of timeVSReliability

Solution Approach 1:

The system performs preliminary actions by generating migration structures and compatibility data for all intermediate firmware versions before the actual update occurs. This allows the system to pre-identify necessary migration actions and ensure compatibility pathways exist, enabling reliable skipping of intermediate versions without causing incompatibility issues.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The system introduces migration structures as intermediary elements that mediate between different firmware versions. These structures contain compatibility information and migration actions that enable safe transitions across version gaps, acting as a bridge that maintains reliability even when skipping intermediate versions.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Reliability

If firmware downgrade is blocked by conventional systems, then system stability is maintained, but adaptability deteriorates when current version has fundamental flaws

Engineering Contradiction:

Improvesystem stabilityVSAvoidfirmware version flexibility

Core Design Contradiction:

ReliabilityVSAdaptability or versatility

Solution Approach 1:

The system makes the firmware update policy dynamic by using compatibility bitmaps and migration structures to determine whether downgrades are permitted. Instead of a fixed block policy, the system dynamically evaluates compatibility information to allow or prevent downgrades, providing both stability when appropriate and flexibility when needed.

Inventive Principle:

Principle #15Dynamics

Solution Approach 2:

The system implements feedback mechanisms through compatibility bitmaps that provide information about whether a downgrade path is safe. This feedback allows the system to make informed decisions about allowing downgrades, balancing stability and adaptability based on actual compatibility data rather than rigid policies.

Inventive Principle:

Principle #23Feedback

3Reliability

If full reinitialization of metadata structure is performed during firmware update, then compatibility is ensured, but processing time and computational cost increase

Engineering Contradiction:

Improvemetadata compatibilityVSAvoidupdate processing efficiency

Core Design Contradiction:

ReliabilityVSProductivity

Solution Approach 1:

The system segments the metadata structure into individual blocks and applies migration actions selectively to only those blocks that require changes. By dividing the metadata structure into manageable segments and processing only the necessary portions, the system maintains compatibility while avoiding the computational overhead of full reinitialization.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The system applies different migration actions to different metadata blocks based on their specific requirements. Instead of uniformly reinitializing all metadata, the system applies local quality changes only where needed, optimizing the balance between compatibility and processing efficiency.

Inventive Principle:

Principle #3Local quality

4Reliability

If firmware update mechanisms account for all differences between non-subsequent versions, then compatibility is improved, but device complexity increases

Engineering Contradiction:

Improveversion compatibilityVSAvoidupdate mechanism complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The system uses copying mechanisms to replicate migration structures and compatibility information across different firmware versions. By copying proven migration patterns and compatibility data, the system handles complexity systematically rather than requiring unique handling for each version pair, reducing overall system complexity while maintaining comprehensive compatibility.

Inventive Principle:

Principle #26Copying

Data Source

PatentUS11099828B2Updating a metadata structure for a firmware update

Publication Date: 2021.08.24 MICROSOFT TECHNOLOGY LICENSING LLC

AI summary

The present disclosure relates to a method for updating a metadata structure to be compatible with an update between the first version of firmware and a second version of firmware, including formation of migration data (e.g., migration arrays) associated with corresponding blocks of metadata for different versions of firmware, and comparing of attributes of the migration data to determine various migration actions to perform in generating an updated metadata structure that is compatible with an update between versions of firmware.