WebAssembly Interface Assembly for Vehicle System Test Separation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing vehicle testing methods require additional hardware and communication interfaces to separate the application or system under test from the environment, leading to increased hardware and performance demands.
Innovation Solution
An assembly utilizing a Web Assembly Interface Type (WIT) to facilitate data transmission and analysis between entities within a vehicle system, allowing for decoupled communication and data filtering/transforming without external hardware, enabling real-world testing of applications.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If dedicated hardware and communication interfaces are added to separate the system under test from the environment, then system separation and testing capability are improved, but device complexity and performance overhead increase
Solution Approach 1:
The patent creates a virtual copy of the communication interface using WebAssembly that mirrors the functionality of dedicated hardware interfaces. The WIT-defined interface replicates data transmission and reception capabilities without requiring physical hardware duplication, allowing the system under test to be separated virtually while avoiding hardware complexity increases.
Solution Approach 2:
The patent replaces mechanical/physical hardware interfaces with a software-based WebAssembly interface. The WIT-defined communication channel substitutes dedicated hardware communication paths, enabling system separation through virtualization rather than physical isolation, thereby reducing device complexity while maintaining reliability.
2Loss of information
If dedicated hardware components are added for data transmission, then data separation and analysis capability are improved, but cost and performance overhead increase
Solution Approach 1:
The WebAssembly interface defined by WIT serves multiple functions simultaneously: it separates data streams for testing, enables analysis of the system under test, and maintains communication efficiency. This universal interface handles data transmission, reception, and analysis coordination without requiring separate dedicated hardware components for each function, reducing both cost and performance overhead.
Solution Approach 2:
The patent creates a virtual data path through the WebAssembly interface that copies necessary data flows for analysis purposes. This virtual copying mechanism separates test data from production data without requiring physical hardware duplication, achieving data separation while minimizing performance overhead compared to hardware-based solutions.
3Loss of information
If all input data are included in official vehicle communication, then data availability for testing is improved, but communication overhead and system complexity increase
Solution Approach 1:
The patent extracts only the necessary data flows required for testing through the WebAssembly interface. The WIT definition specifies which data channels are needed for the system under test, separating these from the complete official vehicle communication set. This extraction approach ensures data availability for testing while reducing communication overhead by excluding unnecessary data streams.
Solution Approach 2:
The WebAssembly interface acts as an intermediary layer between the official vehicle communication system and the system under test. It selectively receives and forwards only the data required for testing, mediating between full system communication and test-specific data needs, thereby reducing communication complexity while maintaining data availability.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
An assembly for analyzing a system including a first entity, configured to send and receive data, a second entity, configured to send and receive data, at least one third entity, configured to receive the data from the first entity and/or the data of the second entity; and an interface, configured to transmit the data of the first entity to the second entity and to the third entity and/or to transmit the data of the second entity to the first entity and to the third entity, wherein the interface is of a Web assembly Interface Type, WIT, or a Web assembly Interface Type definition file, and wherein data from an egress of the third entity is used for analyzing the system.