Vehicle ECU Update Sequencing for Stable Rollback Control

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The complexity of updating multiple electronic control units in vehicles, especially when errors occur, leads to a situation where some units are not completely updated, causing system failures due to different software versions, and existing rollback processes are difficult to manage.

Innovation Solution

An update control device that determines an update order for electronic control units, ensuring that basic software updates are executed after application software updates, and manages rollback processes to maintain system stability.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If multiple electronic control units are updated simultaneously, then productivity is improved, but reliability deteriorates due to system failures from different software versions

Engineering Contradiction:
Improveupdate speedVSAvoidsystem stability
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent segments the update process into distinct phases: application software updates are executed first for all relevant ECUs, then basic software updates are executed afterward. This segmentation prevents mixing of different software versions during simultaneous updates, maintaining system reliability while still allowing parallel update execution within each phase.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent performs preliminary actions by first updating application software before updating basic software. This preliminary sequencing ensures that when basic software is updated, the application software layer is already at its target version, preventing version mismatch conflicts and enabling more reliable simultaneous basic software updates across multiple ECUs.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If rollback processes are implemented for failed updates, then reliability is improved, but device complexity increases

Engineering Contradiction:
Improveerror recoveryVSAvoidrollback management
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent divides the rollback process into segmented steps corresponding to the update phases. Rollback is first attempted for application software updates, and only if those succeed does the system proceed to basic software updates. This segmented approach simplifies rollback management compared to handling all updates simultaneously, as each phase can be independently rolled back without affecting the other phase's state.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements preliminary rollback preparation by establishing the update sequence before execution. The system prepares rollback mechanisms for application software first, then for basic software. This preliminary structuring of rollback procedures reduces operational complexity during actual update failures, as the rollback path is pre-determined and follows the same phased approach as the update process.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS12504965B2Update control device, update control method, and non-transitory computer readable storage medium
Publication Date: 2025.12.23 DENSO CORP
  • US12504965B2 patent drawing
  • US12504965B2 patent drawing
  • US12504965B2 patent drawing

AI summary

An update control device is connected to first and second electronic control units installing first and second software, respectively. First and second update files for updating the first and second software, respectively, are acquired. An update order is determined such that the updating of the second software is executed after the updating of the first software is executed when the first update file is for updating the first software as an application software, and the second update file is for updating the second software as a basic software. The updating of the first and second software using the first and second update files are instructed according to the update order.