Vehicle ECU Update Packaging for Version-Consistent Software Sets

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The efficiency of software updates for electronic control units (ECUs) implementing autonomous driving functions is hindered by the need for consistent software versions across multiple ECUs, leading to inefficient processing when significant version differences require repeated downloads and installations of difference data packages.

Innovation Solution

A center system that determines whether to distribute difference data packages or total data packages based on version differences and update needs, improving the distribution method by dynamically selecting between difference data and total data packages for ECUs, thereby optimizing the software update process.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of substance

If difference data packages are used for software updates, then data transmission volume is reduced, but update processing efficiency deteriorates when version differences are significant

Engineering Contradiction:
Improvedata transmission volumeVSAvoidupdate processing efficiency
Core Design Contradiction:
Loss of substanceVSProductivity

Solution Approach 1:

The system dynamically selects between difference data packages and total data packages based on the version difference between current and latest software versions. When version differences are small, difference data packages are used to reduce transmission volume. When version differences are large, total data packages are used to improve update efficiency, avoiding the inefficiency of repeated incremental updates.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The selection criterion for update packages is changed from a fixed approach to a dynamic approach based on version difference parameters. The center compares the version difference magnitude against a threshold to determine whether to transmit difference data or total data, optimizing the balance between transmission efficiency and update speed.

Inventive Principle:
Principle #35Parameter changes

2Reliability

If multiple ECUs are updated as a set to maintain consistency, then system reliability is improved, but update complexity increases

Engineering Contradiction:
Improvesoftware consistencyVSAvoidupdate complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The update management system segments ECUs into different groups based on their software version relationships. ECUs that require consistent versions are managed as a group, while others are updated independently. This allows the system to maintain necessary consistency without unnecessarily complicating the update process for all ECUs.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The center implements a universal update management mechanism that can handle both grouped updates (for ECUs requiring consistency) and individual updates (for ECUs that can be updated independently). This multi-functional approach simplifies the overall update process by providing a unified interface for managing different update scenarios.

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

3Reliability

If replacement ECUs are updated to latest version, then system consistency is maintained, but update time increases due to repeated processing

Engineering Contradiction:
Improvesystem consistencyVSAvoidupdate time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The center pre-calculates and stores version difference information for multiple ECU versions. When a replacement ECU is detected, the system quickly determines the appropriate update package by comparing stored version information, avoiding time-consuming repeated version checks and enabling faster update deployment.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system replaces manual or sequential version checking processes with an automated version comparison mechanism that uses pre-stored version information. This substitution significantly reduces the time required to determine update requirements for replacement ECUs while maintaining system consistency.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

Data Source

PatentUS11947951B2Center, distribution control method, and non-transitory storage medium
Publication Date: 2024.04.02 TOYOTA JIDOSHA KK
  • US11947951B2 patent drawing
  • US11947951B2 patent drawing
  • US11947951B2 patent drawing

AI summary

A center includes: a storage device storing update management information including a combination of latest versions of pieces of software of first ECUs whose control functions need to be consistent with each other; and one or more processors configured to, when determining, based on the update management information and the current versions of the pieces of software of ECUs in a vehicle, that at least one of the pieces of software of the first ECUs needs to be updated, decide, as a distribution package, an one of a first difference package containing difference data between a previous version and a latest version each of all pieces of software of the first ECUs and a first total data package containing total data of the latest version of one or more pieces of software of the first ECUs that need to be updated, and transmit the distribution package to the vehicle.