Server Software Update Sequence Control for Vehicle Electronic Control Units

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing software update systems for electronic control units in vehicles only consider the state during downloading of updates, leading to delays in applying high-priority updates when they are added during other states such as installation or activation, resulting in potential safety and security vulnerabilities.

Innovation Solution

A server-based system that manages software updates for in-vehicle control devices, determining whether to interrupt the application of a preceding low-priority update and start a high-priority update based on its current state, priority, and sequence dependencies, ensuring timely application of important updates across various states including downloading, installation, and activation.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If the system only considers the state during downloading of update software, then the downloading process can be managed simply, but subsequent high-priority update software cannot be applied in an early stage when added during other states

Engineering Contradiction:
Improveupdate application speedVSAvoidstate management complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system dynamically adjusts update management based on the current state (downloading, installation, or activation) of the preceding update software. The server determines whether to interrupt the preceding update based on the state and priority of the subsequent update, enabling flexible and timely application of high-priority updates without rigid fixed-state management

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The update process is segmented into distinct states (downloading, installation, activation), with each state having specific interruption determination rules. This segmentation allows the system to manage complexity by handling each state separately while maintaining overall coordination through the server's centralized decision-making

Inventive Principle:
Principle #1Segmentation

2Reliability

If the system applies update software in strict sequence without interruption, then the update process is simple to manage, but high-priority updates are delayed

Engineering Contradiction:
Improveupdate priority handlingVSAvoidinterruption determination complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The server implements a feedback mechanism where it continuously monitors the state of preceding updates and receives notifications about subsequent updates. Based on this feedback, the server determines whether to interrupt the preceding update to apply high-priority subsequent updates, ensuring reliable priority handling through dynamic decision-making

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The system changes the parameter of update sequence based on priority levels. When a high-priority subsequent update is detected, the system transitions from strict sequential execution to priority-based interruption, allowing critical updates to be applied immediately while maintaining normal sequence for standard updates

Inventive Principle:
Principle #35Parameter changes

3Productivity

If the server performs all determination processing centrally, then the update management is unified, but loading concentration occurs on the server

Engineering Contradiction:
Improveprocessing distributionVSAvoiddistributed system complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system extracts specific determination logic from the centralized server and implements it locally in the update software. The server provides framework and coordination, while local components handle state monitoring and basic decision-making, distributing processing load and reducing server concentration while maintaining unified management through the overall architecture

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentEP3770754B1Server, software update system, and software update apparatus
Publication Date: 2023.07.12 HITACHI LTD
  • EP3770754B1 patent drawingFigure 1
  • EP3770754B1 patent drawingFigure 2
  • EP3770754B1 patent drawingFigure 3

AI summary

To apply an important subsequent software update in an early stage in consideration of a preceding software update state in an electronic control unit of a vehicle. The server communicates, via a network, with a software update apparatus that updates software of an in-vehicle control device mounted on a vehicle. The server includes an SW update sequence control unit that manages an application of a software update to the in-vehicle control device. When a subsequent second software update to be applied to the in-vehicle control device is registered in the server during an application of a preceding first software update to the in-vehicle control device, the SW update sequence control unit determines whether to interrupt the application of the first software update and start an application of the second software update to the in-vehicle control device based on information relating to the application of the first software update, information relating to the application of the second software update, and an update processing state of the first software update to the in-vehicle control device.