Vehicle Function Software Updates for Subcomponent Compatibility

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing vehicle software update methods can lead to compatibility issues among subcomponents, resulting in impaired vehicle functions due to component-centric updates rather than function-centric approaches.

Innovation Solution

A method and system that update operating software based on vehicle functions, involving detection of trigger signals, creation of function matrices, comparison of actual and target software statuses, and targeted software updates to ensure compatibility among subcomponents.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If operating software is updated for individual subcomponents independently, then update flexibility and speed are improved, but compatibility and reliability of vehicle functions deteriorate

Engineering Contradiction:
Improveupdate speedVSAvoidfunction compatibility
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent segments the update process into two levels: individual subcomponent software updates and vehicle function-level coordination. Each subcomponent can be updated independently at its own pace, but the system ensures compatibility by managing updates at the vehicle function level, where multiple subcomponents working together are considered as a unit. This allows both fast individual updates and reliable coordinated operation.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements a feedback mechanism where the system monitors the update status and compatibility of subcomponents within each vehicle function. When a subcomponent is updated, the system checks whether this affects the compatibility of the entire vehicle function and coordinates subsequent updates accordingly. This feedback loop ensures that updates maintain system reliability while allowing individual components to be updated independently.

Inventive Principle:
Principle #23Feedback

2Reliability

If operating software is updated for all subcomponents involved in a vehicle function, then compatibility and reliability are improved, but update complexity and time consumption increase

Engineering Contradiction:
Improvefunction compatibilityVSAvoidupdate process complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent creates a universal update management system that handles multiple subcomponents through a single coordinated process. Instead of managing each subcomponent update separately, the system treats all subcomponents involved in a vehicle function as a unified update target. This universal approach simplifies the update process by providing a single management interface while ensuring all necessary subcomponents are updated together, reducing overall complexity.

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

Solution Approach 2:

The patent merges the update management of multiple subcomponents into a single vehicle function-level operation. By combining the coordination of all subcomponents into one unified update process, the system reduces the number of separate management tasks required. The merging approach allows the system to handle compatibility checks and coordinate updates for all subcomponents in a single operation, simplifying the overall update complexity.

Inventive Principle:
Principle #5Merging (Combining)

3Reliability

If operating software is updated for all subcomponents involved in a vehicle function, then compatibility is improved, but update time and resource consumption increase

Engineering Contradiction:
Improvefunction compatibilityVSAvoidupdate time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent performs preliminary actions by pre-identifying and grouping all subcomponents that are involved in each vehicle function before the actual update process begins. This preliminary grouping allows the system to know exactly which subcomponents need to be updated together, avoiding unnecessary updates and reducing overall update time. The preliminary action of creating these groups enables efficient coordination without requiring sequential checking during the update process.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent applies partial action by updating only the specific subcomponents that are necessary for each vehicle function, rather than updating all subcomponents in the vehicle. The system identifies and updates only the relevant subset of subcomponents involved in the target vehicle function, avoiding waste of time and resources on unrelated components. This selective partial update approach maintains compatibility while minimizing update time and resource consumption.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS12468523B2Method and system for updating operating software of subcomponents of a motor vehicle
Publication Date: 2025.11.11 AUDI AG
  • US12468523B2 patent drawing
  • US12468523B2 patent drawing

AI summary

A method and a system for updating operating software of subcomponents of a motor vehicle. The updating is not component-specific but vehicle-function-specific.