Vehicle OTA Update Segmentation and Node Switching

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Vehicles face challenges in completing software updates due to issues such as data integrity problems, signal strength issues, and version mismatches, which can lead to incomplete or unreliable software installations.

Innovation Solution

A method where a vehicle receives an initial portion of a software update from a first node, detects issues, and then requests and receives the remaining portion from a second node, ensuring complete software installation by combining the initial and remaining portions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the vehicle receives software update from a single node continuously, then the update process is simple, but the reliability of software installation deteriorates due to potential data integrity issues and signal strength problems

Engineering Contradiction:
Improvesoftware installation reliabilityVSAvoidupdate process complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The software update process is segmented into multiple portions that can be received from different nodes. The vehicle receives an initial portion from a first node and then requests a remaining portion from a second node, dividing the update transmission into manageable segments to improve reliability while maintaining manageable complexity

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The vehicle acts as an intermediary that coordinates between multiple update nodes. It receives the initial portion from the first node, detects issues, and then requests the remaining portion from the second node, serving as a mediator that ensures complete and reliable software installation by combining portions from different sources

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If the vehicle stops software update upon encountering an issue, then data integrity can be maintained, but the productivity of software updates deteriorates due to incomplete installations

Engineering Contradiction:
Improvedata integrityVSAvoidsoftware update completion
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The update is segmented into an initial portion and a remaining portion. The vehicle receives the initial portion from the first node, stops upon detecting an issue to maintain data integrity, then requests and receives the remaining portion from a second node to complete the installation, thus maintaining both integrity and productivity

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The vehicle serves as an intermediary that ensures data integrity by stopping the initial portion upon detecting issues, while simultaneously maintaining productivity by requesting the remaining portion from an alternative second node, thereby completing the software update process

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS20240272892A1Vehicle OTA security validation
Publication Date: 2024.08.15 TOYOTA MOTOR ENG & MFG NORTH AMERICA INC
  • US20240272892A1 patent drawing
  • US20240272892A1 patent drawing
  • US20240272892A1 patent drawing

AI summary

An example operation includes one or more of receiving, by a vehicle, a software update from a first node, responsive to the software update encountering an issue, ceasing, by the vehicle, the software update resulting in an initial portion of the software update being received by the vehicle, requesting, by the vehicle, a remaining portion of the software update, and receiving, by the vehicle, the remaining portion of the software update from a second node.