Startup Data Verification Using Cached Integrity Checks

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The existing methods for starting up information handling systems are computationally and time-consuming due to the need for cryptographic verification of data, which can degrade user experience and inefficiently utilize computing resources.

Innovation Solution

Generating verification data and error correction data after initial cryptographic verification, allowing for faster verification and correction of data during subsequent startups, reducing the need for cryptographic verification and minimizing computational resources used for data verification.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If cryptographic verification is performed during each startup, then data trustworthiness is ensured, but startup time and computational resources increase significantly

Engineering Contradiction:
Improvedata trustworthinessVSAvoidstartup time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs cryptographic verification in advance during the first startup and stores the verification result. During subsequent startups, the pre-stored verification result is used instead of repeating the cryptographic verification process, thereby reducing startup time while maintaining data trustworthiness

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system creates a copy of the verification result from the initial cryptographic verification and stores it for future use. This copy allows the system to verify data integrity without repeating the computationally expensive cryptographic verification process during each startup

Inventive Principle:
Principle #26Copying

2Reliability

If cryptographic verification is performed during each startup, then data integrity is confirmed, but computational resources are inefficiently utilized

Engineering Contradiction:
Improvedata integrityVSAvoidcomputational resource efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system performs the computationally intensive cryptographic verification in advance and caches the result. This preliminary action eliminates the need to repeat the verification process during subsequent startups, significantly improving computational resource efficiency while maintaining data integrity

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system serves itself by storing the verification result for future use, eliminating the need to repeatedly perform cryptographic verification. This self-service approach reduces computational overhead and improves resource utilization

Inventive Principle:
Principle #25Self-service

3Reliability

If data corruption occurs during startup, then system reliability is compromised, but frequent rescue operations increase computational costs

Engineering Contradiction:
Improvesystem reliabilityVSAvoidcomputational cost
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The system prepares error correction data in advance alongside the verification data. This beforehand cushioning allows the system to correct common data corruptions without needing to perform costly rescue operations, thereby maintaining system reliability while reducing computational costs

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

Data Source

PatentUS11762756B2System and method for startup data verification
Publication Date: 2023.09.19 DELL PROD LP
  • US11762756B2 patent drawing
  • US11762756B2 patent drawing
  • US11762756B2 patent drawing

AI summary

Methods, systems, and devices for providing for trust during startup of an information handling system (IHS) are disclosed. When an IHS starts up, data may be read into memory and used by a processor of the IHS to begin execution of a startup management entity that places the IHS into a desired operating system. To reduce the likelihood of the data used for IHS startup causing the IHS to enter an undesired state (e.g., due to data corruption or intentional action), the data may be verified prior to be being read into memory. If the data is unverifiable, then corrective action may be taken.