Vehicle ECU OTA Update Switching for Server Compatibility

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Software updates for vehicle electronic control units (ECUs) cannot be performed via over-the-air (OTA) when the OTA software on the server changes, due to compatibility issues between different vendors' software.

Innovation Solution

A software update device and method that includes first and second software, allowing the download of update data from a server by executing either the first or second software, ensuring compatibility even when the server-side OTA software changes.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a single version of OTA software is used on the vehicle, then software compatibility is maintained, but the system cannot adapt when the server-side software changes

Engineering Contradiction:
Improvesoftware compatibilityVSAvoidadaptability to server software changes
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The system dynamically switches between first OTA software and second OTA software based on the server-side software version. The software update device monitors changes in server software and automatically selects the appropriate client software version to maintain compatibility, transforming a static single-version system into a dynamic multi-version system.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system changes the parameter of software version by switching between first OTA software (first version) and second OTA software (second version). This parameter change allows the system to adapt to different server-side software environments while maintaining reliable communication and update functionality.

Inventive Principle:
Principle #35Parameter changes

2Adaptability or versatility

If multiple versions of OTA software are stored, then adaptability to server changes is improved, but device complexity increases

Engineering Contradiction:
Improveadaptability to server software changesVSAvoidsoftware management complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The software update device is designed with multi-functionality to handle both first OTA software and second OTA software. It can execute different software versions, manage multiple software packages, and automatically select the appropriate version based on server compatibility, making the device universally applicable to different server software environments.

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

Solution Approach 2:

The software update device acts as an intermediary between the vehicle's ECU and the server. It manages the complexity of multiple software versions by implementing selection logic and compatibility checking, shielding the upper layers from the complexity of having multiple software versions while enabling adaptability to server changes.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Adaptability or versatility

If OTA software is updated frequently to match server changes, then adaptability is maintained, but loss of time occurs during software transitions

Engineering Contradiction:
Improvesoftware compatibility maintenanceVSAvoidtime for software switching
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The system performs preliminary actions by pre-storing both first OTA software and second OTA software in the device. This advance preparation eliminates the need for time-consuming downloads when server software changes occur, as the appropriate software version is already available for immediate deployment.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system maintains copies of different OTA software versions (first and second versions) locally. By having these copies readily available, the system can quickly switch between versions without time loss, as the software is already present in the device rather than needing to be fetched from external sources during transitions.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS12056481B2Software update device, update control method, and non-transitory storage medium
Publication Date: 2024.08.06 TOYOTA JIDOSHA KK
  • US12056481B2 patent drawing
  • US12056481B2 patent drawing
  • US12056481B2 patent drawing

AI summary

A software update device is configured to control software update of an electronic control unit mounted on a vehicle. The software update device includes: one or more storage devices configured to store first software and second software for downloading update data of the electronic control unit from a server, the first software and the second software being different from each other; and one or more processors configured to download the update data from the server by executing any of the first software and the second software.