In-Vehicle OTA Master Reducing User Inquiry Frequency

Solution Overview

Problem

Frequent user inquiries during software updates in vehicles can be annoying, as existing systems do not differentiate between types of software updates, leading to unnecessary user consent requests.

Innovation Solution

An in-vehicle device with a determination unit that assesses the necessity of user consent based on software type, automatically performing updates when consent is not required, and prompting users only when necessary, thereby reducing inquiry frequency.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the system performs frequent software updates, then the software remains updated and secure, but the number of user inquiries increases causing user annoyance

Engineering Contradiction:

Improvesoftware update frequencyVSAvoiduser inquiry frequency

Core Design Contradiction:

ReliabilityVSEase of operation

Solution Approach 1:

The patent applies local quality by differentiating treatment based on software type. Critical software updates require user consent inquiries, while non-critical updates are performed automatically without user intervention. This localized differentiation resolves the contradiction by maintaining reliable updates while reducing user annoyance for non-critical updates.

Inventive Principle:

Principle #3Local quality

Solution Approach 2:

The system performs self-service by automatically executing non-critical software updates without requiring user consent inquiries. The determination unit automatically identifies update types and the control unit executes appropriate actions, eliminating the need for frequent user interactions while maintaining update reliability.

Inventive Principle:

Principle #25Self-service

2Reliability

If the system asks users for consent for every software update, then user control and transparency are maintained, but the frequency of interruptions increases

Engineering Contradiction:

Improveuser consent controlVSAvoidupdate process interruption

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The patent applies local quality by differentiating treatment based on software type. Critical software updates require user consent inquiries, while non-critical updates are performed automatically without user intervention. This localized differentiation resolves the contradiction by maintaining reliable updates while reducing user annoyance for non-critical updates.

Inventive Principle:

Principle #3Local quality

Solution Approach 2:

The determination unit performs preliminary action by pre-determining whether user consent is necessary based on software type before the update process begins. This preliminary classification allows the system to automatically execute non-critical updates without user interruption while maintaining user control for critical updates.

Inventive Principle:

Principle #10Preliminary action

3Device complexity

If the system treats all software updates uniformly, then the system logic remains simple, but user experience deteriorates due to unnecessary inquiries

Engineering Contradiction:

Improvesystem logic simplicityVSAvoiduser experience

Core Design Contradiction:

Device complexityVSEase of operation

Solution Approach 1:

The patent applies local quality by differentiating treatment based on software type. Critical software updates require user consent inquiries, while non-critical updates are performed automatically without user intervention. This localized differentiation resolves the contradiction by maintaining reliable updates while reducing user annoyance for non-critical updates.

Inventive Principle:

Principle #3Local quality

Solution Approach 2:

The system introduces dynamic behavior by adjusting the update process based on real-time determination of software type. The determination unit dynamically assesses each update and the control unit adapts its behavior accordingly, improving user experience without significantly complicating the overall system logic.

Inventive Principle:

Principle #15Dynamics

Data Source

PatentUS20240378046A1Vehicle device

Publication Date: 2024.11.14 TOYOTA JIDOSHA KK

AI summary

OTA master mounted on the vehicle is configured as an in-vehicle device that manages updating of the software of the vehicle. The OTA master determines whether user consent is necessary based on the type of software. Then, when determining that user consent is necessary, the OTA master makes an inquiry to the user as to whether to execute a process for the update of the software.