Vehicle Storage Controller Boot Code Security

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

As the number of electronic control units (ECUs) in vehicles increases, the number of individual storage controllers needed to provide boot codes also increases, leading to resource inefficiencies and potential failures in meeting appropriate automotive safety integrity levels (ASILs).

Innovation Solution

A shared storage structure for vehicles where a single storage controller identifies and provides boot codes to multiple ECUs based on their respective security levels, stored in a first non-volatile memory, ensuring compliance with appropriate ASILs and improving multi-user performance.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Device complexity

If one storage controller provides boot codes to multiple ECUs, then device complexity is reduced, but security level compliance may be compromised

Engineering Contradiction:
Improvenumber of storage controllersVSAvoidsecurity level compliance
Core Design Contradiction:
Device complexityVSReliability

Solution Approach 1:

The patent segments boot codes by associating them with specific security levels (ASIL levels). The storage controller identifies the security level of each ECU and provides the appropriate boot code segment, ensuring that each ECU receives boot code compliant with its required security level while using a single shared storage controller.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent applies local quality by providing different boot codes to different ECUs based on their specific security level requirements. Each ECU receives boot code with the appropriate security characteristics tailored to its function, allowing a single storage controller to serve multiple ECUs with diverse security needs.

Inventive Principle:
Principle #3Local quality

2Reliability

If multiple individual storage controllers are used for each ECU, then security level compliance is ensured, but resource consumption increases

Engineering Contradiction:
Improvesecurity level complianceVSAvoidnumber of storage controllers
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The patent merges multiple storage controllers into a single shared storage controller that serves multiple ECUs. This consolidation reduces the total number of storage controllers while maintaining security compliance through the security level identification and appropriate boot code provision mechanism.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The storage controller is designed with multi-functionality to serve multiple ECUs with different security level requirements. It can identify the security level of any connected ECU and provide the corresponding boot code, making a single controller universal enough to replace multiple dedicated controllers.

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

3Quantity of substance

If a shared storage structure is used, then resource efficiency is improved, but adaptability to different security levels must be maintained

Engineering Contradiction:
Improvenumber of storage controllersVSAvoidsecurity level adaptability
Core Design Contradiction:
Quantity of substanceVSAdaptability or versatility

Solution Approach 1:

The storage controller implements dynamic adaptability by identifying the security level of each ECU in real-time and dynamically selecting and providing the appropriate boot code. This dynamic response allows the single storage controller to adapt to different security level requirements of various ECUs.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent changes the parameter of boot code selection based on the security level parameter of the ECU. The storage controller modifies its output (boot code) according to the input parameter (ECU security level), enabling a single controller to serve multiple ECUs with different security requirements.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS20250147771A1Electronic device mounted on vehicle and method of operating the same
Publication Date: 2025.05.08 SAMSUNG ELECTRONICS CO LTD
  • US20250147771A1 patent drawing
  • US20250147771A1 patent drawing
  • US20250147771A1 patent drawing

AI summary

Provided is a method of operating an electronic device mounted on a vehicle, the method including identifying, by a storage controller, a security level corresponding to each of a plurality of electronic control units (ECUs), and providing, by the storage controller, based on the security levels, boot codes, which respectively correspond to a plurality of ECUs and are stored in a first non-volatile memory, to the respective ECUs.