Vehicle Computational Function Block Update Readiness Control

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing vehicle software update systems are inefficient as they require vehicles to be switched off or inactive to update computational function blocks, leading to delayed updates and limited flexibility in timing.

Innovation Solution

An apparatus and method that determine the individual preparedness of each computational function block for updating, allowing updates to be triggered at suitable times by communicating with the blocks or using a ruleset based on vehicle and function block states, enabling updates during vehicle use without waiting for inactivity.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If updates are performed only when the vehicle is switched off or inactive, then system stability is maintained, but update timing is delayed and flexibility is reduced

Engineering Contradiction:
Improvesystem stabilityVSAvoidupdate delay
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent segments the vehicle software system into multiple computational function blocks (CFBs), each capable of independent evaluation of update readiness. This allows selective updating of individual CFBs based on their specific operational state, rather than requiring the entire system to be inactive for any update to occur.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a dynamic evaluation mechanism where each CFB continuously monitors its own operational state and communicates readiness status to the update management system. This dynamic approach allows the system to adapt update timing to the actual operational state of each function block, enabling updates during vehicle operation when specific CFBs are ready.

Inventive Principle:
Principle #15Dynamics

2Reliability

If updates are performed only when the vehicle is switched off or inactive, then system stability is maintained, but update flexibility is reduced

Engineering Contradiction:
Improvesystem stabilityVSAvoidupdate timing flexibility
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent segments the vehicle software system into multiple computational function blocks (CFBs), each capable of independent evaluation of update readiness. This allows selective updating of individual CFBs based on their specific operational state, rather than requiring the entire system to be inactive for any update to occur.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a dynamic evaluation mechanism where each CFB continuously monitors its own operational state and communicates readiness status to the update management system. This dynamic approach allows the system to adapt update timing to the actual operational state of each function block, enabling updates during vehicle operation when specific CFBs are ready.

Inventive Principle:
Principle #15Dynamics

3Device complexity

If a generic ready-for-update evaluation is performed based on vehicle inactivity, then the update process is simplified, but individual function block readiness is not determined

Engineering Contradiction:
Improveupdate process complexityVSAvoidfunction block readiness detection
Core Design Contradiction:
Device complexityVSMeasurement precision

Solution Approach 1:

The patent segments the vehicle software system into multiple computational function blocks (CFBs), each capable of independent evaluation of update readiness. This allows selective updating of individual CFBs based on their specific operational state, rather than requiring the entire system to be inactive for any update to occur.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements a feedback mechanism where each CFB reports its operational state and readiness status to the update management system. This feedback loop enables precise determination of individual function block readiness while maintaining a manageable update process through standardized communication protocols.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS20240411547A1A concept for controlling an update process of a computational function block in a vehicle
Publication Date: 2024.12.12 VOLKSWAGEN AG
  • US20240411547A1 patent drawing
  • US20240411547A1 patent drawing
  • US20240411547A1 patent drawing

AI summary

Various aspects relate to an apparatus, a method, and a computer program for controlling an update process of a computational function block in a vehicle, to a computational function block and a corresponding method and computer program, and to a corresponding vehicle. The apparatus for controlling an update process of a computational function block in a vehicle comprises at least one interface for communicating with the computational function block. The apparatus comprises one or more processors, configured to determine information on a preparedness of the computational function block for updating the computational function block. The information on the preparedness indicates the individual preparedness of the computational function block. The one or more processors are configured to trigger an update of the computational function block if the information on the preparedness indicates that the computational function block is ready to be updated.