Boot Software Buffer Updates for Interrupt-Resilient Security

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing security modules in vehicles fail to flexibly cope with unexpected situations during boot software updates, leading to potential vulnerabilities and permanent non-functionality of electronic devices.

Innovation Solution

A method involving storing a new boot in a buffer area, removing the existing boot, copying it to the boot area, and deleting it from the buffer, with checksum verification and marker patterns to ensure robustness against unexpected interruptions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a security module with the strongest reaction is used to prevent external intrusions, then security is improved, but the system cannot flexibly cope with unexpected situations during updates

Engineering Contradiction:
ImprovesecurityVSAvoidflexibility to cope with unexpected situations
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The update process is segmented into distinct phases: downloading new boot to buffer area, verifying checksum, removing existing boot, copying new boot to boot area, and deleting buffer. This segmentation allows the system to handle unexpected situations at specific phases rather than failing the entire update process, improving adaptability while maintaining security.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system performs preliminary actions before critical operations: it verifies the checksum of the new boot in the buffer area before removing the existing boot. This preliminary verification ensures that only valid updates proceed, allowing flexible handling of unexpected situations without compromising security.

Inventive Principle:
Principle #10Preliminary action

2Productivity

If the existing boot is removed before verifying the update success, then update speed is improved, but false detection occurs when unexpected situations arise

Engineering Contradiction:
Improveupdate speedVSAvoidfalse detection prevention
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The system performs preliminary verification by checking the checksum of the new boot in the buffer area before removing the existing boot from the boot area. This ensures update validity is confirmed in advance, preventing false detections while maintaining fast update execution.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The buffer area serves as an intermediary storage between the downloaded update and the actual boot area. The system verifies the update in the buffer before committing it to the boot area, acting as a safety intermediary that prevents false detections while enabling rapid updates.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Measurement precision

If checksum verification is performed continuously, then detection precision is improved, but system complexity increases

Engineering Contradiction:
Improvedetection precisionVSAvoidsystem complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

Checksum verification is segmented into specific critical phases rather than continuous verification: after downloading to buffer, before removing existing boot, and after copying to boot area. This segmented approach maintains high detection precision while avoiding unnecessary complexity from continuous verification.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS20250231760A1Method and device for updating boot software
Publication Date: 2025.07.17 HYUNDAI AUTOEVER
  • US20250231760A1 patent drawing
  • US20250231760A1 patent drawing
  • US20250231760A1 patent drawing

AI summary

A method for updating boot software, which is performed by a computing device, includes storing a new boot to a buffer area, in response to success of the storing the new boot to a buffer area, removing an existing boot of an update target host, copying the new boot to the boot area of the update target host, and deleting the new boot stored in the buffer area.