Vehicle Update Center Out-of-Order Notification Handling

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The center may erroneously determine an abnormality in software update processing if it fails to receive notifications from the OTA master, leading to discrepancies in update status management.

Innovation Solution

The center is configured to receive and manage notifications from the OTA master, advancing the update status in a predetermined order as long as notifications are received correctly and setting the status based on the most recent notification if they are not, thereby preventing erroneous abnormality determinations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the center expects notifications in a predetermined order and determines abnormalities based on missing notifications, then abnormality detection capability is improved, but false positive abnormality determination occurs when notifications are received out of order

Engineering Contradiction:
Improveabnormality detection accuracyVSAvoidupdate status management accuracy
Core Design Contradiction:
ReliabilityVSMeasurement precision

Solution Approach 1:

The center dynamically adjusts its notification processing logic based on the sequence number of received notifications. When a notification with sequence number n is received, the center updates the expected sequence number to n+1, allowing flexible handling of notifications received out of order while maintaining accurate abnormality detection

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The center uses feedback from received notifications to continuously update its understanding of the update status. Each notification provides feedback about the current processing state, and the center adjusts its expected sequence number based on this feedback, enabling accurate status tracking even when notifications arrive out of order

Inventive Principle:
Principle #23Feedback

2Device complexity

If the center waits for notifications in strict sequential order, then abnormality detection is simplified, but update status management becomes inaccurate when notifications are lost or delayed

Engineering Contradiction:
Improvenotification processing complexityVSAvoidupdate status management accuracy
Core Design Contradiction:
Device complexityVSMeasurement precision

Solution Approach 1:

The OTA master performs preliminary actions by including a sequence number in each notification, indicating which notification it should be in the expected sequence. This allows the center to verify whether the notification is the expected one without complex waiting logic, and to detect abnormalities when the sequence number does not match the expected value

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The center changes its expected sequence number parameter dynamically based on received notifications. When a notification with sequence number n is received, the expected sequence number is updated to n+1. This parameter change approach allows the center to handle out-of-order notifications gracefully while maintaining accurate status management

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS11960876B2Center, update management method, and non-transitory storage medium
Publication Date: 2024.04.16 TOYOTA JIDOSHA KK
  • US11960876B2 patent drawing
  • US11960876B2 patent drawing
  • US11960876B2 patent drawing

AI summary

A center is configured to communicate with an OTA master configured to control software update of an electronic control unit installed in a vehicle. The center includes one or more processors configured to: receive a notification indicating progress of software update processing of the electronic control unit from the OTA master; manage an update status indicating an processing state of the software update processing in the vehicle based on the notification received by the one or more processors; and when the one or more processors receive a third notification following a first notification, set the update status based on the third notification, the third notification being different from a second notification scheduled to be received following the first notification.