Vehicle Program Package Startup Method

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Vehicle functions are often difficult to modify or update without visiting a workshop, requiring hardware replacement, which is disruptive and inefficient.

Innovation Solution

A method for starting up a new program package on vehicle computing units, involving loading, validating, and deploying the package, which can be done wirelessly, and includes emulation and authentication to support various hardware platforms, allowing for dynamic function assignment and redundancy.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If vehicle functions are implemented statically during manufacture, then hardware reliability is improved, but adaptability and ease of updating deteriorate

Engineering Contradiction:
Improvehardware reliabilityVSAvoidease of updating
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The system separates vehicle functions into static hardware components and dynamic software program packages. The program packages are divided into manageable units that can be independently loaded, validated, and deployed to specific computing units, allowing updates without hardware changes.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Program packages are copied from a central archive to a vehicle-specific archive, and then deployed to target computing units. This copying mechanism enables distribution and updating of software functions across multiple computing units without modifying the underlying hardware.

Inventive Principle:
Principle #26Copying

2Manufacturing precision

If program packages are loaded and deployed manually in workshops, then validation accuracy is improved, but productivity and time consumption deteriorate

Engineering Contradiction:
Improvevalidation accuracyVSAvoidupdate speed
Core Design Contradiction:
Manufacturing precisionVSProductivity

Solution Approach 1:

The system implements automated validation and deployment processes. The validation unit automatically validates program packages against validation rules, and the deployment unit automatically deploys validated packages to appropriate computing units, eliminating the need for manual workshop intervention while maintaining validation accuracy.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system incorporates validation rules and automatic feedback mechanisms to ensure program packages meet required standards before deployment. The validation unit provides feedback on whether packages are suitable for deployment, enabling automated decision-making while maintaining high validation accuracy.

Inventive Principle:
Principle #23Feedback

3Manufacturing precision

If program packages are validated manually, then validation thoroughness is improved, but time consumption and operational complexity deteriorate

Engineering Contradiction:
Improvevalidation thoroughnessVSAvoidvalidation time
Core Design Contradiction:
Manufacturing precisionVSLoss of time

Solution Approach 1:

Validation rules are prepared in advance and stored in the validation unit. Program packages are validated against these pre-configured rules automatically during the deployment process, eliminating the need for time-consuming manual validation while maintaining thoroughness through comprehensive rule sets.

Inventive Principle:
Principle #10Preliminary action

4Adaptability or versatility

If hardware is replaced to update vehicle functions, then functional capability is improved, but cost and operational disruption deteriorate

Engineering Contradiction:
Improvefunctional capabilityVSAvoidcost and disruption
Core Design Contradiction:
Adaptability or versatilityVSEase of manufacture

Solution Approach 1:

The system replaces mechanical hardware replacement with software-based program package deployment. Instead of physically replacing hardware components to update vehicle functions, the system loads and deploys software packages to existing computing units, dramatically reducing cost and operational disruption while maintaining functional capability.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

Data Source

PatentUS20240430334A1Method for starting up program packets in vehicles
Publication Date: 2024.12.26 CONTINENTAL AUTOMOTIVE TECHNOLOGIES GMBH
  • US20240430334A1 patent drawing
  • US20240430334A1 patent drawing
  • US20240430334A1 patent drawing

AI summary

The present disclosure relates to a method for starting up program packages in vehicles, in particular for starting up a new program package on at least one vehicle computing unit of a vehicle. The method includes the following steps: loading the program package from a central archive; storing the program package in a vehicle-specific archive; validating the program package in the vehicle-specific archive; determining the vehicle computing unit from a multiplicity of computing units of the vehicle; providing the validated program package on the vehicle computing unit; and starting the validated program package on the vehicle computing unit, wherein the program package performs a vehicle function.