Vehicle ECU Update Activation After Shutdown Across Bank Types

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing vehicle software update methods face challenges in efficiently updating both single-bank and dual-bank electronic control units (ECUs) simultaneously, as single-bank ECUs require software installation and activation after shutdown, while dual-bank ECUs can update before shutdown, leading to complexity and limited update timing.

Innovation Solution

A vehicle system with a control device that determines the type of ECU and requests user acceptance for software activation after shutdown, allowing single-bank ECUs to install and activate software after shutdown and dual-bank ECUs to update before shutdown, simplifying the acceptance process and enabling prompt software updates for both types.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of manufacture

If the vehicle control system is stopped to install software in single-bank ECUs, then software installation can be performed, but software update timing is limited and productivity decreases

Engineering Contradiction:
Improvesoftware installation capabilityVSAvoidsoftware update timing
Core Design Contradiction:
Ease of manufactureVSProductivity

Solution Approach 1:

The control device downloads update software for single-bank ECUs in advance while the vehicle is operating, storing it in the storage unit before the vehicle stops. This preliminary download ensures that when the vehicle stops, the software is ready for immediate installation and activation, eliminating waiting time and improving update timing without requiring the vehicle to be stopped for downloading.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If separate acceptance requests are made for single-bank and dual-bank ECUs, then each ECU type can be updated appropriately, but device complexity and user operation complexity increase

Engineering Contradiction:
ImproveECU update appropriatenessVSAvoidacceptance process complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The control device merges the acceptance request process into a single unified notification sent to the notification device after the vehicle stops. This single notification covers both single-bank and dual-bank ECUs, allowing the user to accept or decline the update for all ECUs simultaneously. The control device then determines the ECU type and executes the appropriate update process, thereby simplifying the user interface and reducing operational complexity while maintaining reliable updates for different ECU types.

Inventive Principle:
Principle #5Merging (Combining)

3Speed

If software is downloaded and installed immediately for dual-bank ECUs, then update speed is improved, but the system cannot wait for user acceptance before activation

Engineering Contradiction:
Improvesoftware update speedVSAvoiduser acceptance control
Core Design Contradiction:
SpeedVSEase of operation

Solution Approach 1:

The control device downloads update software for dual-bank ECUs in advance while the vehicle is operating, storing it in the storage unit before the vehicle stops. This preliminary download enables fast activation after the vehicle stops because the software is already prepared and ready, requiring only user acceptance and a brief activation process, thus maintaining high update speed while preserving user control.

Inventive Principle:
Principle #10Preliminary action

4Reliability

If the vehicle stops to perform all software updates, then all ECUs can be updated, but loss of time and productivity decrease

Engineering Contradiction:
Improvesoftware update completenessVSAvoidvehicle stop time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The control device performs preliminary downloads of update software for all ECUs (both single-bank and dual-bank) while the vehicle is operating. This advance download ensures that when the vehicle stops, only the final installation and activation steps are needed, which are quickly completed. This approach ensures complete software updates for all ECUs while minimizing the time the vehicle needs to be stopped, thereby reducing time loss and improving productivity.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS20240176612A1Vehicle, software update method, and non-transitory storage medium
Publication Date: 2024.05.30 TOYOTA JIDOSHA KK
  • US20240176612A1 patent drawing
  • US20240176612A1 patent drawing
  • US20240176612A1 patent drawing

AI summary

A vehicle including an ECU configured to execute software update by using software distributed from a server includes a start switch configured to stop a control system of the vehicle when the start switch is turned OFF, and a control device. The control device is configured to request acceptance to execute activation after the start switch is turned OFF. The control device is configured to, when the ECU is a single-bank computer: download the software; and then instruct the ECU to install the downloaded software in the ECU and activate the installed software after a user accepts to execute the activation. The control device is configured to, when the ECU is a dual-bank computer, instruct the ECU to activate the installed software after the user accepts to execute the activation.