Vehicle Controller Functionality Expansion via Segmented Runtime

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing vehicle controllers face challenges in efficiently expanding or altering their functionality post-production without causing unintended side effects, as existing methods often result in high complexity and limited assessment of side effects on other software components.

Innovation Solution

A vehicle controller design that allocates static processor access times and memory areas for basic functionalities, allowing for the execution of augmenting modules through a runtime environment, which uses message queues for communication and metadata checks to ensure resource availability and integrity, enabling platform-independent expansion without affecting original functionalities.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If vehicle controller functionality is expanded or altered post-production, then adaptability and versatility are improved, but device complexity and risk of side effects increase

Engineering Contradiction:

Improvefunctionality expansion capabilityVSAvoidcontroller complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The controller software is segmented into multiple independent application modules, each with statically allocated processor access times and memory areas. This modular structure allows individual modules to be updated or expanded without affecting others, enabling functionality expansion while maintaining manageable complexity through clear separation of concerns.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The controller is designed with a universal runtime environment that can execute different augmenting modules with varying functionalities. This multi-functionality approach allows the same hardware platform to support multiple different functional expansions through software modules, improving adaptability without increasing hardware complexity.

Inventive Principle:

Principle #6Universality (Multi-functionality)

2Adaptability or versatility

If vehicle controller functionality is expanded or altered post-production, then adaptability and versatility are improved, but reliability may deteriorate due to unintended side effects

Engineering Contradiction:

Improvefunctionality expansion capabilityVSAvoidfunctional integrity

Core Design Contradiction:

Adaptability or versatilityVSReliability

Solution Approach 1:

The system performs metadata checks and resource availability verification before executing augmenting modules. These preliminary checks cushion against potential reliability issues by detecting conflicts or resource shortages before they can cause functional integrity problems, allowing safe functionality expansion.

Inventive Principle:

Principle #11Beforehand cushioning (Prior cushioning)

Solution Approach 2:

By segmenting the controller into isolated application modules with dedicated resources, the system ensures that changes in one module cannot adversely affect others. This segmentation protects functional integrity while allowing individual modules to be expanded or modified.

Inventive Principle:

Principle #1Segmentation

3Reliability

If static processor access times and memory areas are allocated for basic functionalities, then reliability is improved, but adaptability deteriorates

Engineering Contradiction:

Improvefunctional stabilityVSAvoidfunctionality expansion capability

Core Design Contradiction:

ReliabilityVSAdaptability or versatility

Solution Approach 1:

The controller architecture segments resources into statically allocated portions for basic functionalities and dynamically allocatable portions for augmenting modules. This segmentation maintains reliable baseline operation while creating dedicated space for functional expansion through the runtime environment.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

While basic functionalities have static allocations for reliability, the system incorporates dynamic elements through the runtime environment that can load, unload, and execute different augmenting modules. This dynamic capability enables adaptability without compromising the stable foundation provided by static allocations.

Inventive Principle:

Principle #15Dynamics

4Ease of operation

If augmenting modules are executed in a runtime environment, then ease of operation is improved, but device complexity increases

Engineering Contradiction:

Improvefunctionality expansion easeVSAvoidcontroller architecture complexity

Core Design Contradiction:

Ease of operationVSDevice complexity

Solution Approach 1:

The runtime environment acts as an intermediary layer between the hardware/controller architecture and the augmenting modules. This intermediary simplifies the execution process by providing standardized interfaces and resource management, making functionality expansion easier while encapsulating the underlying architectural complexity.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The runtime environment provides universal support for executing different types of augmenting modules through a common interface and execution mechanism. This multi-functionality approach enables easy operation across diverse functional expansions without requiring separate handling for each module type, despite the underlying architectural complexity.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Data Source

PatentUS9880927B2Functionally expandable vehicle control device and method for supplementing the functionality of a vehicle control device

Publication Date: 2018.01.30 VOLKSWAGEN AG

AI summary

A vehicle control device for supplementing/changing the functionality of a vehicle control device. A vehicle control device is created having at least one processor, a memory coupled to the processor, a plurality of application modules, and at least one communication interface for interchanging data with other vehicle control devices or an external vehicle device. Also disclosed is a method for supplementing/changing the functionality of a vehicle control device.