Vehicle Computing Architecture Virtualization Layer

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Conventional vehicle computing architectures face complexity, limited flexibility, and challenges in integrating multiple hardware components, which hampers the introduction of advanced functions and requires frequent updates to the integration layer.

Innovation Solution

A vehicle computing architecture that includes an application layer with virtual functional components, a software virtualization layer with a command registry, a hardware virtualization layer with mapping logic, and a hardware component layer with physical nodes, allowing for decoupling of virtual commands from hardware components and enabling flexible and scalable data exchange.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If point-to-point integrations are used to control hardware components, then each hardware component can be optimized with specific interfaces, but the integration layer becomes complex and requires frequent updates

Engineering Contradiction:

Improvehardware component optimizationVSAvoidintegration layer complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces a virtualization layer as an intermediary between the application layer and hardware components. This virtualization layer includes virtual devices and drivers that abstract the hardware interfaces, allowing optimized hardware components to be integrated without increasing integration layer complexity. The virtualization layer handles the complexity of hardware abstraction and communication protocols.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent segments the system into distinct layers: application layer, virtualization layer, and hardware layer. Each layer has specific responsibilities, with the virtualization layer serving as a boundary that isolates hardware complexity from the application layer. This segmentation allows hardware components to be optimized independently while maintaining a simple integration interface.

Inventive Principle:

Principle #1Segmentation

2Adaptability or versatility

If more hardware components are added to fulfill complex vehicle functions, then advanced functions can be introduced, but the complexity of integrating and managing these components increases

Engineering Contradiction:

Improveadvanced function capabilityVSAvoidsystem integration complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The virtualization layer provides universal interfaces that can accommodate multiple hardware components with different specific interfaces. The virtual devices and drivers in this layer act as multi-functional adapters, allowing diverse hardware components to be integrated through a common abstraction mechanism, thereby enabling advanced functions without proportionally increasing integration complexity.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Solution Approach 2:

The virtualization layer serves as an intermediary that mediates between the application layer and the expanding hardware layer. It provides standardized virtual interfaces that simplify the integration of new hardware components, allowing the system to accommodate advanced functions while maintaining manageable complexity through abstraction.

Inventive Principle:

Principle #24Intermediary (Mediator)

3Reliability

If container technology is applied to virtualize software components, then operational independence and stability are improved, but the fundamental modeling of components and data exchange remains unchanged

Engineering Contradiction:

Improveoperational independenceVSAvoidcomponent modeling flexibility

Core Design Contradiction:

ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent extends the static containerization approach by introducing dynamic virtual device drivers that can adapt to different hardware components. The virtualization layer includes dynamic mapping mechanisms that allow the system to flexibly model and map virtual devices to physical hardware, thereby maintaining operational independence while enhancing component modeling flexibility and adaptability.

Inventive Principle:

Principle #15Dynamics

Data Source

PatentUS20250077264A1Computing architecture for vehicle hardware and feature virtualization

Publication Date: 2025.03.06 IRIDER

AI summary

A vehicle computing architecture (100) includes an application layer (112), a software virtualization layer (114), a hardware virtualization layer (116), and a hardware component layer (118). The application layer includes a plurality of virtual functional components (122) each representing a virtual function. The software virtualization layer includes a command registry (124) having virtual commands. The hardware virtualization layer includes mapping logic (134, 136). The hardware component layer includes a plurality of physical nodes (135) each being a virtual representation of a corresponding hardware component (110). The virtual functional components call a virtual command from the command registry. The hardware virtualization layer selects one of the physical nodes corresponding to the received virtual command and translates the received virtual command to a hardware command using the mapping logic, and communicates the hardware command to the selected physical node. The hardware component layer communicates the hardware command to the hardware component to perform the corresponding vehicle function.