Dynamic Storage Block Validation for Secure ECU Boot
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current systems that validate software integrity before the boot sequence in vehicles extend the boot time, delaying the operational readiness of electronic control units (ECUs), which is a concern for both performance and security.
Innovation Solution
A system and method that dynamically validates storage blocks during the boot process using a hardware security module (HSM) and memory protection unit (MPU), allowing access only to validated blocks while maintaining minimal boot time by selectively validating and enabling access to storage blocks based on their execution or access timeline.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If software integrity is validated prior to boot sequence, then security is improved, but boot time is extended
Solution Approach 1:
The patent divides the boot process into multiple stages with selective validation. Critical code segments are validated before execution while non-critical segments are validated later or in the background, allowing the boot process to proceed without waiting for complete validation of all software components.
Solution Approach 2:
The patent performs preliminary validation of critical code segments that must be executed during boot, while deferring validation of less critical segments. This preliminary action on essential components enables secure boot without extending total boot time significantly.
Solution Approach 3:
The patent implements background validation that continues during system operation. While critical validation occurs before boot, non-critical validation proceeds in the background during normal operation, maintaining continuous security validation without interrupting the boot process.
2Reliability
If complete software validation is performed before boot, then security is improved, but operational readiness is delayed
Solution Approach 1:
The patent segments software into critical and non-critical code segments. Critical segments required for immediate operational readiness are validated and executed, while validation of non-critical segments is deferred to background processes, ensuring both security and timely operational readiness.
Solution Approach 2:
The patent applies partial validation by validating only the necessary critical code segments required for boot and immediate operation, rather than validating the entire software suite before boot. This partial action achieves sufficient security for operational readiness without unnecessary delays.
3Reliability
If all storage blocks are validated before access, then software integrity is ensured, but boot process time is extended
Solution Approach 1:
The patent divides storage blocks into critical and non-critical categories. Only critical storage blocks containing essential boot code are validated before access, while non-critical blocks are validated later. This segmentation ensures software integrity for essential functions without extending boot process time.
Solution Approach 2:
The patent performs preliminary validation only on critical storage blocks that contain code segments needed for immediate boot and operation. This selective preliminary action on essential blocks ensures integrity where needed while avoiding time extension from validating all blocks.
Data Source
Figure 1
Figure 2
Figure 3A~3B
AI summary
A system and method for booting a computing device may include, during a boot process of the device: preventing access to a set of storage blocks including a software object; selectively validating one or more storage blocks in the set; and enabling access to validated storage blocks.