Virtual ECU Network Verification Across Mixed Automotive Protocols
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing automotive embedded systems face challenges in efficiently verifying network communication between ECUs with different communication protocols, requiring manual bus generation or separate software development, and lack effective monitoring and data exchange in complex networks.
Innovation Solution
A system and method for verifying a virtual ECU that simulates network communication by connecting a network management unit and virtual ECUs in a 1:1 manner, supporting data conversion between different protocols, and integrating a network monitoring unit for comprehensive data logging and error detection.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If multiple separate networks are constructed for ECUs with different communication protocols, then each protocol can be individually monitored, but the system complexity and number of network monitors required increases
Solution Approach 1:
The patent merges multiple protocol-specific network monitors into a single network monitor that can handle multiple protocols (CAN, LIN, Ethernet) simultaneously. This consolidation reduces the number of separate monitoring devices needed while maintaining the ability to monitor each protocol individually, thus reducing system complexity without compromising monitoring accuracy
Solution Approach 2:
The network monitor is designed with multi-functionality to support multiple communication protocols through a single device. It includes protocol-specific processing units that can identify and process different protocol types, enabling one monitor to perform the functions previously requiring multiple separate monitors
2Reliability
If manual bus generation or separate software development is performed for each protocol, then protocol-specific communication can be verified, but the verification process time and resource consumption increases
Solution Approach 1:
The system performs preliminary configuration by pre-defining communication patterns, message formats, and protocol specifications before actual verification begins. Test cases are prepared in advance with expected message sequences and validation criteria, allowing the verification process to execute automatically without manual intervention during testing
Solution Approach 2:
The verification system is designed to be self-sufficient by automatically generating test messages, monitoring communications, validating protocols, and producing verification reports without requiring manual bus generation or separate software development for each protocol. The system autonomously handles the entire verification process
3Ease of operation
If a network management unit is connected to multiple virtual ECUs, then centralized communication management is achieved, but the data routing and protocol conversion complexity increases
Solution Approach 1:
The network management unit acts as an intermediary between virtual ECUs with different protocols. It includes protocol conversion functionality that automatically translates messages between different protocol formats, and routing logic that directs messages to appropriate destinations based on protocol type and communication patterns, simplifying management while handling complexity internally
Data Source
AI summary
A system for verifying a virtual ECU for an automotive embedded system is provided. The system includes a docker management unit configured to perform setting on a plurality of virtual ECUs based on first setting information and to construct a network between the plurality of virtual ECUs based on second setting information and a docker host managed by the docker management unit. The docker host includes a resource management unit including a device driver for each board for generating each virtual ECU and an application builder for building an embedded software-based application according to the AUTOSAR standard to be mounted on the virtual ECU, the plurality of virtual ECUs each configured to drive the built application, and a network management unit connected to the plurality of virtual ECUs and configured to support network communication between the virtual ECUs.