KR-20260067268-A - SYSTEM AND METHOD FOR VERIFYING VIRTUAL ECU BASED ON DOCKER HOST

KR20260067268AKR 20260067268 AKR20260067268 AKR 20260067268AKR-20260067268-A

Abstract

A virtual ECU verification system based on a Docker host is provided. The system includes a network configuration unit that creates a virtual bridge and a virtual bus for vehicle communication in a virtual environment based on network configuration information, a network configuration unit that connects the virtual ECU to the virtual bridge and the virtual bus, and a network management unit that monitors the virtualized network environment by selecting and logging the virtual bus or a specific signal. The network configuration unit creates an entire virtual bus based on the network configuration information, but if the virtual bus is not created, it checks whether there is a problem with the path of the image file for creating the virtual bus or the image file itself and generates error information.

Inventors

이인호
양안나
한우진

Assignees

주식회사 드림에이스

Dates

Publication Date: 20260512
Application Date: 20241226

Claims (10)

A network configuration unit that generates a virtual bridge and a virtual bus for vehicle communication in a virtual environment based on network configuration information, and A network configuration unit that connects the above virtual ECU to the above virtual bridge and virtual bus, and A network management unit including a network monitoring unit that monitors a virtualized network environment by selecting and logging the virtual bus or specific signals, and The above network monitoring unit receives a message generated by a simulation model of an external commercial tool and transmits it to the virtual ECU, records a response from the virtual ECU, and then determines whether the recorded response is identical to the response in the test case. Docker host-based virtual ECU verification system.
In paragraph 1, The above network configuration unit checks for errors during the creation of the virtual bridge and, if an error occurs, determines whether the error is caused by a conflict in the bridge name or bridge IP; however, if it is determined that there is no conflict in the bridge name or bridge IP, it determines that the error is due to insufficient system resources. Docker host-based virtual ECU verification system.
In paragraph 1, The above network configuration unit determines whether there is an error caused by a bus name conflict or a bus IP conflict during the creation of the virtual bus when the virtual bus is not created and it is determined that the problem is not with the path of the image file for the creation of the virtual bus or with the image file itself, and determines that the error is due to a lack of system resources when it is determined that there is no error during the creation of the virtual bus. Docker host-based virtual ECU verification system.
In paragraph 1, The above network configuration unit configures a one-to-one connection between the virtual bus protocol and the virtual bridge, and configures a virtual bus connection between the virtual bridge and at least one virtual ECU. Docker host-based virtual ECU verification system.
In paragraph 1, The above network monitoring unit, upon receiving a selection input for a virtual bus protocol, outputs a virtual bus list corresponding to the selected virtual bus protocol, searches the virtual bus list upon receiving a selection input for the virtual bus list and outputs it as a virtual bus list to be monitored, and starts monitoring after setting the ASIL grade of the virtual ECU corresponding to the virtual bus list to be monitored. Docker host-based virtual ECU verification system.
In paragraph 1, The above network monitoring unit outputs a signal list corresponding to a selected virtual ECU among the list of virtual ECUs, extracts and provides a bus list containing the specific signal upon receiving a selection input for the specific signal among the signal list, and starts monitoring after setting the ASIL grade for the selected virtual ECU. Docker host-based virtual ECU verification system.
In paragraph 1, The above network monitoring unit, upon initiating the monitoring, monitors the status of the virtual bus to check for errors when the virtual bus status can be verified, and when the virtual bus status cannot be verified, checks whether a transmission item is set and then transmits a message to determine whether the abnormal status of the virtual bus has been resolved. Docker host-based virtual ECU verification system.
In paragraph 1, The above network monitoring unit returns the logging results of data transmitted and received between multiple virtual ECUs to an external commercial tool for determining appropriateness, The above external commercial tool generates an appropriateness judgment result by comparing the above logging result with the simulation result according to the test case, Docker host-based virtual ECU verification system.
In paragraph 1, The above network monitoring unit extracts the results of a simulation with an external commercial tool and transmits them to the external commercial tool, and the external commercial tool compares the simulation results with the simulation results according to test cases to generate a result for determining appropriateness. Docker host-based virtual ECU verification system.
In a method performed by a Docker host-based virtual ECU verification system, A step of creating a virtual bridge and a virtual bus for vehicle communication in a virtual environment based on network configuration information; A step of connecting the virtual ECU to the virtual bridge and virtual bus; and The method includes the step of monitoring a virtualized network environment by selecting and logging the virtual bus or a specific signal. The step of monitoring a virtualized network environment by selecting and logging the above virtual bus or specific signal is, Receiving a message generated by a simulation model of an external commercial tool and transmitting it to the virtual ECU, recording a response from the virtual ECU, and then determining whether the recorded response is identical to the response in the test case. Docker host-based virtual ECU verification method.

Description

System and Method for Verifying Virtual ECU Based on Docker Host The present invention relates to a Docker host-based virtual ECU verification system and method. Figure 1 is a diagram illustrating the verification process of a multi-ECU network in the prior art. Generally, for network verification of multiple ECUs (103) in a vehicle embedded system, multiple ECUs (103) are connected to a single communication line (101) to conduct the test, and a network monitor (105) is used as a tool to observe messages on the bus. At this time, the network monitor (105) can monitor communication between ECUs (103) in real time and check message transmission and reception, data consistency, etc. Figure 2 is a diagram illustrating the verification process of a multi-ECU network having different communication protocols in the prior art. In order to communicate between ECUs (211, 221, 231) with different communication protocols in an embedded vehicle system, a separate network must be established for each communication protocol (210, 220, 230), and then information about each bus must be monitored individually through a network monitor (212, 222, 232). In data conversion as well, tasks such as changing the message format according to the protocol and transmitting the data to the corresponding bus must be performed through separate network management software. Figure 1 is a diagram illustrating the verification process of a multi-ECU network in the prior art. Figure 2 is a diagram illustrating the verification process of a multi-ECU network having different communication protocols in the prior art. FIG. 3 is a block diagram of a virtual ECU verification system (300) according to one embodiment of the present invention. FIG. 4 is a detailed block diagram of a virtual ECU verification system according to one embodiment of the present invention. FIG. 5 is a diagram illustrating an embodiment of verifying a virtual ECU in the present invention. FIG. 6 is a flowchart of a Docker host-based virtual ECU verification method according to one embodiment of the present invention. FIG. 7 is a detailed block diagram of a virtual ECU verification system according to a second embodiment of the present invention. FIG. 8 is a flowchart of a virtual ECU verification method according to a second embodiment of the present invention. FIG. 9 is a diagram illustrating the process of creating a virtual bridge in the second embodiment of the present invention. FIG. 10 is a diagram illustrating the process of creating a virtual bus in a second embodiment of the present invention. FIG. 11 is a diagram illustrating the process of connecting a virtual bus and a virtual bridge in the second embodiment of the present invention. FIG. 12 is a diagram illustrating the process of connecting a virtual ECU and a virtual bridge in the second embodiment of the present invention. FIG. 13 is a diagram illustrating a network monitoring process in a second embodiment of the present invention. FIG. 14 is a diagram illustrating the process of selecting a monitoring target during the network monitoring process in the second embodiment of the present invention. FIG. 15 is a diagram illustrating the monitoring connection setup process during the network monitoring process in the second embodiment of the present invention. FIG. 16 is a diagram illustrating the bus monitoring process during the network monitoring process in the second embodiment of the present invention. FIG. 17 is a diagram illustrating the signal monitoring process during the network monitoring process in the second embodiment of the present invention. FIG. 18 is a diagram illustrating the process of handling abnormal termination of monitoring during the network monitoring process in the second embodiment of the present invention. FIG. 19 is a diagram illustrating the process of setting up an external usage tool connection during a network monitoring process in the second embodiment of the present invention. FIG. 20 is a flowchart of the connection process between an external commercial tool and a network monitoring unit in one embodiment of the present invention. FIG. 21 is a flowchart of the simulation process of an external commercial tool and a network monitoring unit in one embodiment of the present invention. FIG. 22 is a flowchart of the log verification process of an external commercial tool and a network monitoring unit in one embodiment of the present invention. FIG. 23 is a flowchart of the process for verifying the simulation results of an external commercial tool and a network monitoring unit in one embodiment of the present invention. FIG. 24 is a flowchart of the error verification process of an external commercial tool and a network monitoring unit in one embodiment of the present invention. The advantages and features of the present invention and the methods for achieving them will become clear by referring to the embodiments described below in detail together with the accompanying drawings