In-Vehicle Software Updating with Battery Voltage Prediction

Solution Overview

Problem

In-vehicle software updates often interrupt due to unpredictable battery power consumption, leading to repetitive processing and increased power consumption and time requirements, especially when updating multiple electronic control units (ECUs).

Innovation Solution

An in-vehicle software updating method that calculates predicted voltage values before and during updates, switches to a power-saving mode based on progress rates, and continues updates if the predicted voltage remains above a threshold, ensuring the battery voltage is maintained above a critical level.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Device complexity

If software update is performed using predicted voltage values only, then update process is simple, but actual voltage depletion causes update interruption and repetitive processing

Engineering Contradiction:

Improveupdate control complexityVSAvoidupdate completion time

Core Design Contradiction:

Device complexityVSLoss of time

Solution Approach 1:

The system performs preliminary voltage prediction before starting the software update and calculates a predicted voltage value at the update completion time. Based on this prediction, the system determines in advance whether the update can be completed without interruption, and only starts the update when the prediction indicates sufficient voltage margin. This preliminary assessment prevents unnecessary update interruptions and repetitive processing.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The system implements feedback by acquiring actual voltage measurement values during the software update process and comparing them with predicted values. When the actual voltage deviates from the prediction or approaches critical thresholds, the system adjusts its control actions accordingly. This feedback mechanism allows the system to adapt to actual voltage depletion patterns and prevent update interruptions.

Inventive Principle:

Principle #23Feedback

2Use of energy by moving object

If software update is performed without voltage monitoring, then power consumption is high, but voltage depletion causes update interruption and wasted power

Engineering Contradiction:

Improvepower consumption during updateVSAvoidupdate completion reliability

Core Design Contradiction:

Use of energy by moving objectVSReliability

Solution Approach 1:

The system performs preliminary voltage prediction before starting the software update and calculates a predicted voltage value at the update completion time. Based on this prediction, the system determines in advance whether the update can be completed without interruption, and only starts the update when the prediction indicates sufficient voltage margin. This preliminary assessment prevents unnecessary update interruptions and repetitive processing.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The system implements feedback by acquiring actual voltage measurement values during the software update process and comparing them with predicted values. When the actual voltage deviates from the prediction or approaches critical thresholds, the system adjusts its control actions accordingly. This feedback mechanism allows the system to adapt to actual voltage depletion patterns and prevent update interruptions.

Inventive Principle:

Principle #23Feedback

3Productivity

If multiple ECUs are updated simultaneously, then system productivity is high, but power consumption increases and update interruptions occur

Engineering Contradiction:

Improveupdate processing speedVSAvoidtotal power consumption

Core Design Contradiction:

ProductivityVSUse of energy by moving object

Solution Approach 1:

The system segments the software update process into individual ECU update tasks and manages them sequentially or in controlled batches. The zone control unit processes update requests from multiple ECUs but executes them in a manner that controls peak power consumption. By dividing the update process into manageable segments and controlling their execution timing, the system maintains productivity while preventing power consumption from exceeding battery capacity.

Inventive Principle:

Principle #1Segmentation

Data Source

PatentUS11809853B2In-vehicle software updating method and in-vehicle system

Publication Date: 2023.11.07 YAZAKI CORP

AI summary

An in-vehicle software updating method includes: acquiring, after starting a software update, a voltage measurement value of an in-vehicle power source; and acquiring a progress rate in the software update in a case in which the voltage measurement value is equal to or less than a second threshold. In a case in which the progress rate is less than a set value, the software update is interrupted. In a case in which the progress rate is equal to or greater than the set value, an operation mode of the zone control unit is switched to a power saving mode, and a second predicted voltage value of the in-vehicle power source at the update completion time is calculated. The software update is continued in a case in which the second predicted voltage value is greater than a first threshold.