Software Update Apparatus ECU Version Consistency Control

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In vehicle network systems, ensuring consistency among the program versions of multiple electronic control units (ECUs) during software updates is crucial for maintaining system operation, but existing methods fail to guarantee consistency and may lead to unexpected behavior or defects if updates are not properly synchronized.

Innovation Solution

A software update apparatus and method that includes a communication unit for requesting and storing update data, and a control unit to install and activate software on ECUs, ensuring consistency by determining software versions, restricting vehicle operations if necessary, and re-executing updates to resolve inconsistencies, thereby maintaining system consistency and operation.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If software updates are performed on multiple ECUs simultaneously to improve productivity, then update speed increases, but consistency among ECUs may be compromised leading to system defects

Engineering Contradiction:
Improveupdate speedVSAvoidsoftware version consistency
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The system performs preliminary actions by downloading and storing update data for all target ECUs before actually installing them. This allows the update data to be prepared in advance and ensures that all ECUs have access to the same update version, maintaining consistency while enabling parallel installation processes that improve productivity.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements feedback mechanisms by acquiring software version information from each ECU after updates and determining whether consistency exists among all ECUs. Based on this feedback, the system can identify inconsistencies and re-execute updates on specific ECUs to restore consistency, thereby ensuring reliability while maintaining efficient update processes.

Inventive Principle:
Principle #23Feedback

2Reliability

If software updates are performed sequentially on each ECU to ensure consistency, then version consistency is maintained, but update time increases significantly

Engineering Contradiction:
Improvesoftware version consistencyVSAvoidupdate duration
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system downloads and stores update data for all target ECUs in advance before installation begins. This preliminary preparation allows subsequent installation operations to proceed in parallel across multiple ECUs without worrying about data availability or version mismatches, significantly reducing total update time while maintaining consistency through coordinated execution control.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system acquires software version information from all ECUs and determines consistency across the entire system, then selectively re-executes updates only on ECUs that exhibit inconsistencies. This partial re-execution approach rather than re-updating all ECUs reduces unnecessary processing time while ensuring that consistency is restored across the system.

Inventive Principle:
Principle #16Partial or excessive action

3Adaptability or versatility

If update data is stored in each ECU's storage unit during updates, then update capability is improved, but storage capacity is consumed

Engineering Contradiction:
Improveupdate capabilityVSAvoidstorage capacity
Core Design Contradiction:
Adaptability or versatilityVSQuantity of substance

Solution Approach 1:

The system extracts and stores update data in a centralized storage unit separate from the ECUs themselves. This allows ECUs to access update data from the centralized storage during installation without requiring large amounts of storage capacity within each ECU, thereby improving update capability while minimizing the storage burden on individual ECUs.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The centralized storage unit serves multiple functions: it stores update data for multiple different ECUs, manages version information, coordinates update execution, and provides data to all target ECUs. This multi-functional approach improves overall system update capability while efficiently utilizing storage resources rather than duplicating storage capacity across multiple ECUs.

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

Data Source

PatentUS20250103324A1Software update apparatus, software update method, non-transitory storage medium storing program, vehicle, and OTA master
Publication Date: 2025.03.27 TOYOTA JIDOSHA KK
  • US20250103324A1 patent drawing
  • US20250103324A1 patent drawing

AI summary

A software update apparatus includes a communication unit that sends a request for downloading update data to a center, a storage unit that stores the downloaded update data, and a control unit that executes, based on the update data, a control for installing, or installing and activating update software on one or more target electronic control units from among a plurality of electronic control units connected to each other via an in-vehicle network. The control unit acquires software versions of the electronic control units, determines whether there is a consistency in a combination of the acquired software versions, and executes, upon determining that there is an inconsistency in the combination of the acquired software versions, a process for attaining the consistency in the combination of the software versions.