Electronic Device Firmware Redundancy and Validity Signatures

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing electronic devices with firmware often face reliability issues due to single-point failures in firmware execution, where errors or failed updates can render the device inoperable, lacking redundancy and efficient update mechanisms.

Innovation Solution

The implementation of multiple firmware copies within a device's memory, each with a validity signature, allows for automatic selection and execution of the most recent valid copy, with a common file system and boot program ensuring seamless operation and efficient updates, including the reception and decompression of additional firmware copies for replacement.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Device complexity

If a single copy of firmware is stored in the device memory, then the device complexity is reduced, but the reliability deteriorates due to single-point failures

Engineering Contradiction:
Improvefirmware storage structureVSAvoidfirmware execution reliability
Core Design Contradiction:
Device complexityVSReliability

Solution Approach 1:

The patent implements multiple copies of firmware in device memory, where each copy can independently execute the device functions. This allows the system to maintain reliability by switching to a valid copy when one becomes faulty, while keeping the added complexity manageable through structured memory organization and validation mechanisms.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The patent prepares backup firmware copies in advance and implements validation mechanisms that detect faults before they cause complete system failure. The system maintains a plurality of firmware copies with validity indicators, allowing it to cushion against potential failures by having pre-prepared alternative versions ready for execution.

Inventive Principle:
Principle #11Beforehand cushioning (Prior cushioning)

2Reliability

If multiple copies of firmware are stored in the device memory, then the reliability is improved through redundancy, but the device complexity increases

Engineering Contradiction:
Improvefirmware execution reliabilityVSAvoidfirmware storage structure
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent merges multiple firmware copies into a unified memory structure with a common file system that is accessible by all copies. This reduces complexity by providing a shared resource management mechanism rather than requiring separate storage and management systems for each firmware copy.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The patent creates a universal boot program that can validate and execute any of the firmware copies, and a common file system that serves all copies. This multi-functional approach reduces overall system complexity by using single, versatile components rather than dedicated separate systems for each firmware instance.

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

3Adaptability or versatility

If firmware updates are performed by replacing existing copies, then the adaptability is improved, but the loss of time increases due to validation and replacement processes

Engineering Contradiction:
Improvefirmware update capabilityVSAvoidboot process time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent performs preliminary validation of firmware copies during the boot process by checking validity indicators before attempting execution. This preliminary action identifies valid copies in advance, allowing the system to quickly boot without extensive validation delays during the actual startup sequence.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent implements a self-validating firmware system where each copy contains its own validity indicator and the boot program automatically validates and selects appropriate copies without external intervention. This self-service mechanism reduces boot time by eliminating manual validation steps and enabling automatic selection of valid firmware.

Inventive Principle:
Principle #25Self-service

4Reliability

If validity checks are performed for each firmware copy, then the reliability is improved, but the boot process time increases

Engineering Contradiction:
Improvefirmware validity assuranceVSAvoidboot process time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent implements partial validation by checking only validity indicators (such as checksums or version tags) rather than performing complete firmware validation during boot. This partial action approach provides sufficient reliability assurance while significantly reducing the time required compared to full validation of each firmware copy.

Inventive Principle:
Principle #16Partial or excessive action

Solution Approach 2:

The patent uses self-validating firmware copies that contain embedded validity indicators, allowing the boot program to quickly verify authenticity without extensive external validation processes. This self-service validation mechanism maintains reliability while minimizing boot time overhead.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS11816466B2Electronic device with firmware, and method of operating thereof
Publication Date: 2023.11.14 STMICROELECTRONICS (GRAND OUEST) SAS
  • US11816466B2 patent drawing
  • US11816466B2 patent drawing
  • US11816466B2 patent drawing

AI summary

An embodiment electronic device includes a memory containing a plurality of copies of firmware of the device.