BIOS Reversion Assessment and Secure Update Mechanism

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current BIOS management systems lack effective security measures for reverting to prior BIOS versions, ensuring secure updates, and enabling advanced functionalities like instant-on applications during the pre-boot phase without requiring an operating system.

Innovation Solution

The system implements secure storage and verification mechanisms, including checksum and certificate comparisons, hidden network access keys, and an enhanced pre-boot environment that allows for downloadable Linux C++ support, enabling secure BIOS updates and instant-on capabilities without an operating system, along with BIOS Over-the-Air (BOTA) updates and partial reflashing options.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If BIOS update and reversion functionality is added, then system functionality and adaptability are improved, but device complexity and security risks increase

Engineering Contradiction:
ImproveBIOS update and reversion capabilityVSAvoidBIOS management system complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The BIOS system is divided into separate functional modules: update management module, reversion management module, verification module, and execution module. Each module handles specific tasks independently, reducing overall system complexity while enabling comprehensive BIOS management functionality.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system performs preliminary actions by creating backup copies of the current BIOS before updates, pre-verifying update packages, and pre-assessing reversion conditions. This preliminary preparation simplifies the actual update and reversion processes by handling complex validation and safety checks in advance.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If security verification mechanisms (checksum and certificate comparisons) are implemented, then system security is improved, but processing time and operational complexity increase

Engineering Contradiction:
ImproveBIOS security against tamperingVSAvoidBoot process time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

Checksum and certificate verifications are performed preliminarily during BIOS update installation and before allowing reversion operations. By completing security checks in advance rather than during boot, the system ensures security without significantly impacting boot time.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The verification process is optimized to quickly skip through known good checksums and certificates that are stored in the system. Once verification data is cached, subsequent security checks execute rapidly, minimizing the time impact on normal operations.

Inventive Principle:
Principle #21Skipping (Rushing through)

3Adaptability or versatility

If pre-boot environment capabilities are enhanced with downloadable Linux C++ support, then system adaptability and functionality are improved, but device complexity and resource requirements increase

Engineering Contradiction:
ImprovePre-boot environment functionalityVSAvoidPre-boot system complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The pre-boot environment is designed as a universal platform that can execute multiple types of applications including downloadable Linux C++ programs. This multi-functional approach allows the same pre-boot environment to handle traditional BIOS tasks while also supporting modern application execution without requiring separate systems.

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

Solution Approach 2:

An intermediary execution layer is introduced between the BIOS and Linux C++ applications. This intermediary handles the complexity of application management, resource allocation, and environment configuration, allowing the core BIOS to remain relatively simple while still supporting advanced pre-boot functionalities.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Ease of operation

If automated BIOS assessment and reversion control are implemented, then ease of operation is improved, but system complexity and processing requirements increase

Engineering Contradiction:
ImproveBIOS reversion process automationVSAvoidAssessment and control system complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The BIOS system performs self-assessment of update success and self-determination of reversion needs. The system automatically evaluates its own state, compares backup versions, and executes reversion operations without external intervention. This self-service approach simplifies user operation while the underlying complexity is handled by the automated assessment engine.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

An automated feedback loop continuously monitors BIOS update status, system stability, and performance metrics. This feedback mechanism provides real-time information to the control system, enabling intelligent decision-making about whether reversion is necessary and which backup version to restore, thereby simplifying user interaction with complex BIOS management tasks.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS8874892B1Assessing BIOS information prior to reversion
Publication Date: 2014.10.28 PHOENIX TECH EMEA LTD
  • US8874892B1 patent drawing
  • US8874892B1 patent drawing
  • US8874892B1 patent drawing

AI summary

Approaches for assessing information used in reverting to a prior BIOS version. A BIOS analyzes a file to determine whether the file may be used to revert the BIOS to a prior version of the BIOS. The file may contain a map of CMOS information.