Firmware Update System Using Identification Code Verification

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing firmware update systems lack the ability to reliably determine the legitimacy of firmware updates, leading to potential incorrect or insecure updates that can cause system malfunction and unnecessary costs.

Innovation Solution

A firmware update method and system that includes writing a first identification code into the memory module, setting a firmware update file with a second identification code, and comparing the update file to a custom structure to ensure legitimacy before allowing the update, using modules for setting, comparing, and updating the firmware.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If firmware update systems use simple file name identification mechanisms, then the ease of operation is improved, but the reliability of firmware verification deteriorates

Engineering Contradiction:
Improveease of firmware update operationVSAvoidreliability of firmware legitimacy verification
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent introduces an intermediary verification mechanism (identification code comparison module) that mediates between the firmware update file and the computer system. This intermediary checks whether the identification code in the firmware update file matches the pre-stored identification code in the computer system, thereby preventing unauthorized or incompatible firmware updates while maintaining ease of operation.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent applies preliminary action by pre-storing an identification code in the computer system before the firmware update process. This pre-stored code serves as a reference for verifying the legitimacy of incoming firmware updates, ensuring that only authorized firmware can be installed without complicating the user interface or operation flow.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If firmware update systems implement strict legitimacy verification, then the reliability is improved, but the device complexity increases

Engineering Contradiction:
Improvereliability of firmware update verificationVSAvoidcomplexity of firmware update system
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent extracts the verification logic into a separate, dedicated module (identification code comparison module) that independently checks firmware legitimacy. This modular approach isolates the complexity of verification mechanisms from the core firmware update functionality, allowing the system to maintain high reliability through rigorous checking while keeping the overall system architecture clean and manageable.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The system performs self-verification by automatically comparing the identification code in the firmware update file with the pre-stored identification code without requiring user intervention or complex external verification processes. This self-service mechanism ensures reliable firmware verification while minimizing system complexity by handling all verification tasks internally through a straightforward comparison process.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS11507367B2Firmware update method and firmware update system thereof
Publication Date: 2022.11.22 GUNITECH
  • US11507367B2 patent drawing
  • US11507367B2 patent drawing
  • US11507367B2 patent drawing

AI summary

A firmware update method and a firmware update system thereof includes the steps of: executing a setting process, which includes writing a first identification code into a memory module, and setting a firmware update file on a firmware providing end to make the firmware update file include a second firmware image file and a second identification code and executing a determining process, which includes receiving the firmware update file and determining whether the firmware update file conforms to a custom structure according to the first identification code. If it does not, then prohibiting the firmware update image file from updating a computer system, and if it does, replacing a first firmware image file with the second firmware image file and writing the second firmware image file into the memory module of the computer system along with the second identification code.