Hybrid Secure Boot Parallel Authenticity Validation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Traditional secure boot procedures in automotive systems are sequential and become bottlenecks due to increasing authentication requirements, which can delay startup timing and hinder the execution of safety-critical functionalities.

Innovation Solution

A hybrid system with diverse subsystems, including multiple CPUs and secured storage devices, performs parallel authenticity validation using different hashing and signature algorithms to ensure secure boot operations, allowing for faster execution of safety-critical software while providing robust security checks.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If sequential secure boot procedures are used with increasing authentication requirements, then security is improved, but startup timing is delayed

Engineering Contradiction:
ImprovesecurityVSAvoidstartup timing
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent divides the secure boot authentication process into multiple independent parallel paths. Different subsystems (e.g., safety-critical subsystem and non-safety-critical subsystem) perform authenticity validation simultaneously using different algorithms, rather than sequentially. This segmentation allows security checks to be distributed across multiple processing streams, improving startup timing while maintaining security.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a new dimension of parallel processing by implementing multiple authentication paths with diverse algorithms (e.g., different hashing algorithms, different signature verification methods). This transforms the traditional single-threaded sequential authentication into a multi-dimensional parallel architecture where validations occur concurrently across different computational dimensions, resolving the time-security tradeoff.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

2Loss of time

If multiple diverse subsystems perform parallel authenticity validation, then startup timing is improved, but device complexity increases

Engineering Contradiction:
Improvestartup timingVSAvoidsystem complexity
Core Design Contradiction:
Loss of timeVSDevice complexity

Solution Approach 1:

The patent implements a universal authentication framework where multiple subsystems share common security infrastructure elements such as root of trust, key management mechanisms, and validation protocols. Each subsystem is multi-functional, capable of performing both its primary function and security validation functions. This universality reduces overall system complexity despite the parallel architecture by reusing common components across subsystems.

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

Solution Approach 2:

The patent manages complexity by parameterizing the authentication system, allowing configuration of which subsystems perform validation and which algorithms are used. The system can adapt its complexity level based on operational requirements, enabling simpler configurations when full parallel validation is not needed while supporting complex parallel validation when performance demands it.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS11100229B2Secure hybrid boot systems and secure boot procedures for hybrid systems
Publication Date: 2021.08.24 INFINEON TECHNOLOGIES AG
  • US11100229B2 patent drawing
  • US11100229B2 patent drawing

AI summary

A hybrid device includes a plurality of diverse subsystems, including a first and a second subsystem. The first subsystem includes at least one first secured storage device configured to store a first software and a first CPU configured to boot and execute the first software. The second subsystem includes at least one second secured storage device configured to store a second software and a second CPU configured to boot and execute the second software. The first CPU is configured to generate the first hash of the first software and transmit the generated first hash of the first software to the second subsystem. The second CPU is configured to perform a first authenticity validation check on the first software using the received first hash of the first software, and generate an error signal on a condition that the first authenticity validation check on the first software fails.