Vehicular Communication System ECU Update Verification

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The increasing complexity of software updates in vehicular electronic control units (ECUs) leads to inconsistent communication among ECUs, making it difficult to verify if communication after an update is expected or not, especially with varying update timings across ECUs.

Innovation Solution

A vehicular communication system that includes a storage unit for scheduled data, an acquiring unit for real-time data during software updates, and a determining unit to compare expected and actual communication data to assess if communication is expected, using a communication confirmation ECU to relay information and determine the status of communication on the bus.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If software programs are updated via wireless network with different update timings for each ECU, then update flexibility and adaptability are improved, but communication inconsistency and system reliability deteriorate

Engineering Contradiction:
Improveupdate flexibilityVSAvoidcommunication consistency
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The system performs preliminary actions by storing expected communication data patterns before software updates occur. The communication verification ECU pre-configures what normal communication should look like, enabling it to detect anomalies after updates with different timings across ECUs.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements feedback by continuously monitoring bus communication and comparing actual communication patterns against expected patterns. When inconsistencies are detected due to staggered updates, the system can identify and report these deviations, enabling corrective actions.

Inventive Principle:
Principle #23Feedback

2Ease of operation

If software updates are executed per ECU individually, then update control flexibility is improved, but verification difficulty and system complexity increase

Engineering Contradiction:
Improveupdate control flexibilityVSAvoidverification complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The communication verification ECU serves as an intermediary that centralizes the verification function. Instead of each ECU needing individual verification capabilities, a single dedicated ECU monitors all communication patterns, simplifying the overall system architecture while maintaining individual ECU update flexibility.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The communication verification ECU performs multiple functions: it monitors bus communication, compares patterns against expected values, detects anomalies, and can trigger warnings. This multi-functional approach consolidates verification complexity into a single component rather than distributing it across multiple ECUs.

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

3Reliability

If real-time monitoring of bus communication is implemented during software updates, then communication reliability verification is improved, but system processing load and time consumption increase

Engineering Contradiction:
Improvecommunication verification accuracyVSAvoidverification time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system applies partial monitoring by focusing verification efforts on communication patterns that are most likely to change during updates. Rather than analyzing every single bus transaction in detail, the system monitors key communication patterns and compares them against expected values, reducing processing overhead while maintaining verification effectiveness.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS11288054B2Vehicular communication system
Publication Date: 2022.03.29 TOYOTA JIDOSHA KK
  • US11288054B2 patent drawing
  • US11288054B2 patent drawing
  • US11288054B2 patent drawing

AI summary

An object of the present disclosure is to determine whether or not communication between ECUs after update of a software program is expected communication. A vehicular communication system includes: a storage unit which stores a first piece of information indicating data scheduled to be transmitted and received on a bus connecting a plurality of ECUs so that the ECUs can communicate with one another; an acquiring unit which acquires a second piece of information indicating data being transmitted and received on the bus when a software program of at least one of the plurality of ECUs is updated; and a determining unit which determines whether or not expected communication is being executed on the bus based on the first piece of information and the second piece of information.