In-Vehicle Software Update Compatibility Control

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing systems for updating software modules in in-vehicle devices and mobile terminals connected for cooperation often fail to ensure compatibility, leading to issues with utilizing the cooperation function between the two, especially when the mobile terminal-side update status is not synchronized with the in-vehicle device-side update requirements.

Innovation Solution

An in-vehicle device with a control unit that updates its software module based on information received from a mobile terminal, using an information management device to transmit and install update files automatically, ensuring compatibility and preventing erroneous installations by checking for downward compatibility and vehicle state.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If the in-vehicle device updates its software module independently without checking mobile terminal compatibility, then the update speed is fast, but compatibility between the in-vehicle device and mobile terminal cannot be ensured

Engineering Contradiction:
Improveupdate speedVSAvoidcompatibility
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The control unit performs a compatibility determination process before executing the software update. It receives software information from the mobile terminal, determines whether the software modules are compatible, and only then proceeds with the update. This preliminary compatibility check ensures that updates do not break the cooperation function between the in-vehicle device and mobile terminal.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements a feedback mechanism where the control unit continuously monitors the software version information from the mobile terminal and adjusts the update process accordingly. When incompatibility is detected, the update is prevented or adjusted to maintain compatibility, creating a closed-loop control system that balances update speed with compatibility assurance.

Inventive Principle:
Principle #23Feedback

2Reliability

If the system checks software compatibility before every update, then compatibility is ensured, but the update process becomes complex and time-consuming

Engineering Contradiction:
ImprovecompatibilityVSAvoidupdate process complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The compatibility determination is performed as a preliminary step that automatically executes before the update process. By embedding this check in the update workflow, the system manages complexity through structured process design rather than adding separate complex compatibility management systems.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The control unit automatically performs the compatibility determination using software information received from the mobile terminal without requiring manual intervention. The system self-manages the compatibility check process, reducing the operational complexity for users while ensuring reliability.

Inventive Principle:
Principle #25Self-service

3Reliability

If the in-vehicle device waits for mobile terminal update status before updating, then compatibility is maintained, but the update timing is delayed

Engineering Contradiction:
ImprovecompatibilityVSAvoidupdate timing
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The control unit uses feedback from the mobile terminal's software information to determine the appropriate update timing. Rather than waiting passively, the system actively monitors software version information and initiates updates when compatibility conditions are met, optimizing the timing based on real-time feedback.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The update timing is made dynamic rather than static. The system adjusts the update schedule based on the mobile terminal's software status, enabling updates to proceed as soon as compatibility is confirmed rather than following a fixed waiting period. This dynamic approach reduces time loss while maintaining compatibility.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentEP2856311B1In-vehicle device, mobile terminal, information management device and information communication system
Publication Date: 2018.02.21 TOYOTA JIDOSHA KK
  • EP2856311B1 patent drawingFigure 1
  • EP2856311B1 patent drawingFigure 2
  • EP2856311B1 patent drawingFigure 3

AI summary

An information communication system includes an in-vehicle device mounted on a vehicle and a mobile terminal connected to the in-vehicle device so as to be able to cooperate with the in-vehicle device. In the information communication system, when a first software module embedded in the mobile terminal has been updated, a second software module embedded in the in-vehicle device is updated on the basis of software information about the updated first software module.