Vehicle Software Update Node Waking for Power Reduction

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing software update methods for vehicles consume excessive power and can lead to update malfunctions due to the waking up of multiple electronic control units during scheduled updates, even when only one unit needs updating.

Innovation Solution

Implementing an Ethernet-based vehicle network system where only the target end node is woken up for software updates, with updates performed while the vehicle is turned off to minimize power consumption and prevent malfunctions by controlling network requests and using a communicator to manage software downloads and updates.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If multiple electronic control units are woken up for scheduled software updates, then software updates can be performed across the vehicle network, but power consumption increases significantly

Engineering Contradiction:
Improvesoftware update completionVSAvoidpower consumption
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The patent segments the software update process by identifying and waking up only the specific end node (electronic control unit) that requires software updates, rather than waking up all ECUs in the vehicle network. This is achieved through the communicator transmitting update information that identifies the target end node, and the network controller selectively waking up only that specific node during the scheduled update time.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent extracts the unnecessary action of waking up non-target ECUs from the software update process. By filtering out ECUs that do not require updates, the system eliminates the wasteful power consumption associated with waking up and checking all ECUs, while still maintaining the ability to perform comprehensive software updates when needed.

Inventive Principle:
Principle #2Taking out (Extraction)

2Productivity

If software updates are performed while the vehicle is running, then updates can be applied immediately, but update malfunctions and abnormal operations may occur

Engineering Contradiction:
Improveupdate speedVSAvoidupdate stability
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent implements preliminary actions by checking the vehicle's operating state before performing software updates. The system determines whether the vehicle is in a stopped state or running state, and only proceeds with updates when the vehicle is stopped. This preliminary check prevents updates from being performed during vehicle operation, thereby avoiding potential malfunctions and ensuring update stability.

Inventive Principle:
Principle #10Preliminary action

3Reliability

If all electronic control units are checked during software updates, then comprehensive updates can be ensured, but the update process becomes more complex and time-consuming

Engineering Contradiction:
Improveupdate completenessVSAvoidupdate process complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces dynamic adaptability in the software update process by allowing the system to flexibly determine the number and identity of end nodes requiring updates. Rather than following a fixed procedure to check all ECUs, the system dynamically adjusts the update scope based on received update information, waking up only the necessary number of end nodes. This dynamic approach maintains update completeness while reducing unnecessary complexity.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS10630538B2Software update method and apparatus for vehicle
Publication Date: 2020.04.21 HYUNDAI MOTOR CO LTD
  • US10630538B2 patent drawing
  • US10630538B2 patent drawing
  • US10630538B2 patent drawing

AI summary

An operation method of a first communication node constituting an Ethernet-based vehicle network of a vehicle may comprise waking up by transitioning from a sleep state to a ready state; preventing transmission of network requests to other communication nodes connected to the Ethernet-based vehicle network; and performing update of software. Thus, only a target end node among a plurality of end nodes connected to the Ethernet-based vehicle network can be woken up for update of software so as to reduce power consumption of the vehicle due to the update of software. Also, abnormal operations due to the update of software can be prevented by allowing the update of software to be performed only while the vehicle is not running.