Vehicle-road cloud collaborative test method and device, electronic equipment and computer storage medium

Abstract

The embodiment of the invention provides a vehicle-road cloud collaborative test method and device, electronic equipment and a computer storage medium. The method comprises the steps that configuration information of a test case is received, and the configuration information is configured by a user on a configuration interface; configuring a first device as a virtual roadside device according to the configuration information, so that the virtual roadside device generates test data of the test case; establishing communication connection between the virtual roadside equipment and an ECU to be tested; and sending the test data generated by the virtual roadside equipment to the ECU to be tested, so as to test the ECU to be tested by using the test data. According to the invention, the test can be carried out in a simulation environment, the test complexity is reduced, and the test comprehensiveness and accuracy are improved.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of computer technology, and in particular to a vehicle-road-cloud collaborative testing method, device, electronic device, and computer storage medium. Background Art

[0002] Vehicle to Everything (V2X) is a vehicle communication system that integrates and interacts vehicle, pedestrian and road facility information through vehicle-to-vehicle communication and vehicle-to-road and pedestrian interaction to achieve a more intelligent and autonomous transportation system.

[0003] With the development of vehicle-road-cloud collaboration, testing and verification work is needed for vehicle-road-cloud collaboration. However, the equipment used to test vehicle-road-cloud collaboration is complex, and traditional testing methods rely on actual vehicles to be implemented. Summary of the invention

[0004] In view of this, an embodiment of the present application provides a vehicle-road-cloud collaborative testing method, device, electronic device and computer storage medium to at least partially solve the above-mentioned problems.

[0005] According to a first aspect of an embodiment of the present application, a vehicle-road-cloud collaborative testing method is provided, the method comprising:

[0006] Receive configuration information of the test case, wherein the configuration information is configured by a user in a configuration interface;

[0007] Configuring the first device as a virtual roadside device according to the configuration information, so that the virtual roadside device generates test data for the test case;

[0008] Establishing a communication connection between the virtual roadside equipment and the ECU to be tested;

[0009] The test data generated by the virtual roadside equipment is sent to the ECU to be tested, so as to test the ECU to be tested using the test data.

[0010] In some embodiments, the configuration information includes a test case name, interface information, and communication parameters;

[0011] The configuring the first device as a roadside device according to the configuration information includes:

[0012] Parsing the configuration information to obtain the test case name, the interface information and the communication parameters;

[0013] The first device is configured as the virtual roadside device according to the test case name, the interface information and the communication parameters.

[0014] In some embodiments, the communication parameters are IP address and MAC address;

[0015] The configuring the first device as the virtual roadside device according to the test case name, the interface information and the communication parameters includes:

[0016] Obtain the IP address and the MAC address;

[0017] The address of the network card of the first device is configured as the IP address and the MAC address, so as to configure the first device as the virtual roadside device according to the test case name, the interface information and the communication parameters.

[0018] In some embodiments, establishing a communication connection between the virtual roadside device and the ECU to be tested includes:

[0019] Receiving the IP address and MAC address of the ECU to be tested, wherein the IP address and MAC address of the ECU to be tested are configured by the user in a configuration interface;

[0020] The IP address and MAC address of the ECU to be tested are added to the address resolution protocol of the virtual roadside device to establish a communication connection between the virtual roadside device and the ECU to be tested.

[0021] In some embodiments, sending the test data generated by the virtual roadside equipment to the ECU to be tested, so as to test the ECU to be tested using the test data, includes:

[0022] Sending the test data generated by the virtual roadside equipment to the ECU to be tested;

[0023] The ECU to be tested parses the received test data to obtain a first display position of a display element in the test data;

[0024] Displaying the display element on the display interface according to the first display position of the display element;

[0025] The display result of the display interface determines the test result of the ECU to be tested.

[0026] In some embodiments, the display result of the display interface determines the test result of the ECU to be tested, including:

[0027] Acquire a first display position of the display element on the display interface;

[0028] If the first display position is the same as the preset display position in the test data, determining that the ECU to be tested passes the test;

[0029] If the first display position is different from a preset display position in the test data, it is determined that the ECU to be tested has failed the test.

[0030] In some embodiments, the method further comprises:

[0031] If the ECU under test fails the test, the ECU under test sends a fault message to the virtual roadside device.

[0032] According to a second aspect of an embodiment of the present application, a vehicle-road-cloud collaborative testing device is provided, the device comprising:

[0033] A receiving module, used to receive configuration information of a test case, wherein the configuration information is configured by a user in a configuration interface;

[0034] A configuration module, configured to configure the first device as a virtual roadside device according to the configuration information, so that the virtual roadside device generates test data for the test case;

[0035] A communication module, used to establish a communication connection between the virtual roadside equipment and the ECU to be tested;

[0036] The test module is used to send the test data generated by the virtual roadside equipment to the ECU to be tested, so as to test the ECU to be tested using the test data.

[0037] According to the third aspect of an embodiment of the present application, there is provided an electronic device, comprising: a processor, a memory, a communication interface and a communication bus, wherein the processor, the memory and the communication interface communicate with each other through the communication bus; the memory is used to store at least one executable instruction, and the executable instruction enables the processor to perform operations corresponding to the vehicle-road-cloud collaborative testing method described in the first aspect.

[0038] According to a fourth aspect of an embodiment of the present application, a computer storage medium is provided, on which a computer program is stored. When the program is executed by a processor, the vehicle-road-cloud collaborative testing method as described in the first aspect is implemented.

[0039] According to the vehicle-road-cloud collaborative testing method provided in the embodiment of the present application, the configuration information of the test case configured by the user in the configuration interface is first received. Further, according to the configuration information of the test case, the first device is configured as a virtual roadside device that can generate test data of the test case to simulate the roadside device. Further, a communication connection is established between the virtual roadside device and the ECU to be tested, so that the virtual roadside device sends the generated test data to the ECU to be tested, thereby directly testing the ECU to be tested using the test data. The embodiment of the present application uses the first device to simulate the virtual roadside device to directly test the ECU to be tested, which can be separated from the physical roadside equipment and vehicles required for the test, reduces the complexity of the test, and performs the test in a simulated environment, avoiding system safety risks caused by the test and enhancing the safety of the test. At the same time, by configuring the test case, more test scenarios and boundary conditions can be covered, improving the comprehensiveness and accuracy of the test. BRIEF DESCRIPTION OF THE DRAWINGS

[0040] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in the embodiments of the present application. For ordinary technicians in this field, other drawings can also be obtained based on these drawings.

[0041] Figure 1 A flowchart of a vehicle-road-cloud collaborative testing method according to an embodiment of the present application;

[0042] Figure 2 is a flowchart of a vehicle-road-cloud collaborative testing method according to another embodiment of the present application;

[0043] Figure 3 is a structural block diagram of a vehicle-road-cloud collaborative testing device according to an embodiment of the present application;

[0044] Figure 4 It is a schematic diagram of the structure of an electronic device according to an embodiment of the present application. DETAILED DESCRIPTION

[0045] In order to enable those skilled in the art to better understand the technical solutions in the embodiments of the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. All other embodiments obtained by ordinary technicians in this field based on the embodiments in the embodiments of the present application should fall within the scope of protection of the embodiments of the present application.

[0046] The specific implementation of the embodiment of the present application is further explained below in conjunction with the accompanying drawings of the embodiment of the present application.

[0047] Vehicle to Everything (V2X) is a vehicle communication system that integrates and interacts vehicle, pedestrian and road facility information through vehicle-to-vehicle communication and vehicle-to-road and pedestrian interaction to achieve a more intelligent and autonomous transportation system.

[0048] Before the vehicle-road-cloud collaboration goes online, it needs to be tested and verified to ensure that the vehicle's ECU can correctly parse the data sent by the roadside equipment. However, the existing test scheme relies on actual equipment, that is, it needs to use vehicles and roadside equipment for testing, which increases the difficulty of testing.

[0049] In view of this, an embodiment of the present application provides a vehicle-road-cloud collaborative testing method, which can be specifically executed by a control unit of a first device, and the first device can specifically be a computer. The specific steps are as follows: Figure 1 As shown, including:

[0050] S101, receiving configuration information of a test case.

[0051] In the embodiment of the present application, the control unit receives the configuration information of the test case configured by the user in the configuration interface. Specifically, the user configures the test case according to the actual test requirements, and when the user configuration is completed, the control unit can receive the configuration information of the test case.

[0052] In one example, when a user configures a test case in the configuration interface, the test case can be configured according to the test case name, interface information, and communication parameters in the ARXML file. Specifically, the test case name may include function, name, and identifier; the interface information may include method, event, and field; and the communication parameters may include IP address, port number, and virtual local area network (VLAN).

[0053] In an example, the test cases may specifically include a traffic sign recognition test, a traffic light recognition test, and the like.

[0054] S102: Configure the first device as a virtual roadside device according to the configuration information, so that the virtual roadside device generates test data of the test case.

[0055] In an embodiment of the present application, after receiving the configuration information of the test case, the control unit parses the configuration information and configures the first device according to the parsing result to configure the first device as a roadside device that can generate test data for the test case.

[0056] In an example, if the test case is a traffic sign recognition test, the control unit configures the first device according to the configuration information of the traffic sign recognition test, so that the first device can generate test data required for the traffic sign recognition test.

[0057] In one example, when configuring the first device, the control unit configures the network card of the first device according to the analysis result, so as to configure the first device as a roadside device that can generate test data of the test case.

[0058] S103: Establish a communication connection between the virtual roadside equipment and the ECU to be tested.

[0059] In the embodiment of the present application, after configuring the first device as a virtual roadside device, the control unit establishes a communication connection between the virtual roadside device and the ECU to be tested.

[0060] In an example, the virtual roadside device and the ECU to be tested are connected by wire, and the virtual roadside device and the ECU to be tested are connected by a 1G network cable.

[0061] In one example, the virtual roadside equipment and the ECU to be tested may also be connected wirelessly.

[0062] S104, sending the test data generated by the virtual roadside equipment to the ECU to be tested, so as to test the ECU to be tested using the test data.

[0063] In an embodiment of the present application, after establishing a communication connection between the virtual roadside equipment and the ECU under test, the control unit sends the test data generated by the virtual roadside equipment to the ECU under test, so as to test the ECU under test using the test data, thereby testing the vehicle-road-cloud collaboration.

[0064] The vehicle-road-cloud collaborative testing method provided in the embodiment of the present application first receives the configuration information of the test case configured by the user in the configuration interface, and further configures the first device as a virtual roadside device that can generate test data of the test case according to the configuration information of the test case to simulate the roadside device, and further establishes a communication connection between the virtual roadside device and the ECU to be tested, so that the virtual roadside device sends the generated test data to the ECU to be tested, thereby directly testing the ECU to be tested using the test data. By using the first device to simulate the virtual roadside device to directly test the ECU to be tested, the embodiment of the present application can be separated from the physical roadside equipment and vehicles required for the test, reducing the complexity of the test, and conducting the test in a simulated environment, avoiding system safety risks caused by the test, and enhancing the safety of the test. At the same time, by configuring the test case, more test scenarios and boundary conditions can be covered, improving the comprehensiveness and accuracy of the test.

[0065] Furthermore, the configuration information of the embodiment of the present application includes a test case name, interface information, and communication parameters. Configuring the first device as a roadside device according to the configuration information may include the following steps:

[0066] S1021, parse the configuration information to obtain the test case name, interface information and communication parameters.

[0067] In an embodiment of the present application, after receiving the configuration information of the test case, the control unit parses the configuration information to determine the test case name, interface information, and communication parameters carried in the configuration information.

[0068] S1022: Configure the first device as a virtual roadside device according to the test case name, interface information, and communication parameters.

[0069] In an embodiment of the present application, after obtaining the test case name, interface information and communication parameters, the control unit uses the test case name, interface information and communication parameters to configure the first device as a virtual roadside device, so that the first device is configured as a virtual roadside device that can generate test data for the test case.

[0070] In one example, the communication parameters of an embodiment of the present application include an IP address and a MAC address. When configuring the first device, the IP address and the MAC address in the communication parameters are obtained to configure the first device as a virtual roadside device using the test case name, interface information, IP address, and MAC address.

[0071] By parsing the configuration information, the embodiment of the present application can accurately configure the first device according to the test requirements, so that the first device can simulate the roadside equipment to generate test data, thereby performing vehicle-road-cloud collaborative testing without the physical device, reducing the complexity of the vehicle-road-cloud collaborative testing.

[0072] Furthermore, in the embodiment of the present application, establishing a communication connection between the virtual roadside device and the ECU to be tested may include the following steps:

[0073] S1031, receiving the IP address and MAC address of the ECU to be tested.

[0074] In an embodiment of the present application, when establishing a communication connection between the virtual roadside equipment and the ECU to be tested, the control unit first receives the IP address and MAC address of the ECU to be tested. Specifically, the IP address and MAC address of the ECU to be tested are configured by the user in the configuration interface. After the user completes the configuration of the IP address and MAC address of the ECU to be tested in the configuration interface, the control unit receives the IP address and MAC address of the ECU to be tested.

[0075] S1032, adding the IP address and MAC address of the ECU to be tested to the address resolution protocol of the virtual roadside device to establish a communication connection between the virtual roadside device and the ECU to be tested.

[0076] In an embodiment of the present application, after obtaining the IP address and MAC address of the ECU under test, the control unit sends the IP address and MAC address of the ECU under test to the address resolution protocol of the virtual roadside device so that the virtual roadside device can communicate with the ECU under test.

[0077] Specifically, the control unit of the embodiment of the present application adds the MAC address of the ECU under test to the address resolution protocol (ARP) of the simulated ECU, and the command may be: netsh-cii add neighbors <network port number><IP address of the ECU under test><MAC address of the ECU under test>. The command for querying the network port number may be: netsh ii show in; the IP address of the ECU under test and the MAC address of the ECU under test are obtained from the description file. The above commands can be operated in the Windows command line (CMD). Among them, ARP is a network layer protocol used to resolve the network layer (IP layer) address into the MAC address of the link layer (such as Ethernet).

[0078] Furthermore, in the embodiment of the present application, the test data generated by the virtual roadside equipment is sent to the ECU to be tested, so as to test the ECU to be tested using the test data, which may include the following steps:

[0079] S1041, sending the test data generated by the virtual roadside equipment to the ECU to be tested.

[0080] In the embodiment of the present application, when the ECU to be tested is tested, the control unit sends the test data generated by the virtual roadside equipment to the ECU to be tested, so that the test data can be used to test the ECU to be tested.

[0081] S1042: The ECU to be tested parses the received test data to obtain a first display position of a display element in the test data.

[0082] In the embodiment of the present application, after receiving the test data, the ECU to be tested parses the test data and obtains the first display position of the display element in the test data.

[0083] In one example, if the test case is a traffic sign recognition test, the test data includes the location information of the traffic sign. After receiving the test data, the ECU to be tested parses the test data to determine the first display position of the display element (traffic sign).

[0084] S1043: Display the display element on the display interface according to the first display position of the display element.

[0085] In the embodiment of the present application, the ECU under test displays the display element on a display interface connected to the ECU under test according to the acquired first display position of the display element.

[0086] In one example, taking the above embodiment as an example, the ECU to be tested displays the traffic sign on the real interface at the first display position of the traffic sign.

[0087] S044, determining the test result of the ECU to be tested according to the display result of the display interface.

[0088] In the embodiment of the present application, when the ECU under test displays a display element on a display interface, the ECU under test compares the first position information of the display element on the display interface with the preset position information to determine whether the first display position parsed by the ECU under test is the same as the preset position information in the test data; if the first display position is the same as the preset display position in the test data, it is determined that the ECU under test has passed the test; if the first display position is different from the preset display position in the test data, it is determined that the ECU under test has failed the test.

[0089] Specifically, the test data of the embodiment of the present application includes a preset display position and a packaged preset display position. After receiving the test data, the ECU to be tested processes the packaged preset display position to obtain the first display position of the display element, and further displays the first display position of the display element on the display interface. The ECU to be tested compares the first display position with the preset display position to determine the test result of the ECU to be tested.

[0090] In one example, the test data may also only include a package preset display position. After receiving the test data, the package preset display position is processed to obtain the first display position of the display element. Further, after the first display position of the display element is displayed on the display interface, the user can observe through the display interface whether the first display position of the display element meets expectations to determine the test result of the ECU to be tested.

[0091] The embodiment of the present application parses the test data through the ECU under test to obtain the first display position of the display element, further uses the first display position to display the display element on the display interface, and then determines whether the ECU under test passes the test through the display interface, thereby being separated from the physical roadside equipment and vehicles required for the test, reducing the complexity, and conducting the test in a simulated environment, avoiding the system safety risks caused by the test, and enhancing the safety of the test. At the same time, by configuring the test cases, more test scenarios and boundary conditions can be covered, improving the comprehensiveness and accuracy of the test.

[0092] Furthermore, in the embodiment of the present application, if the ECU under test determines that it has failed the test, the ECU under test sends fault information to the virtual roadside device to provide the user with fault inspection.

[0093] In one example, the vehicle-road-cloud collaborative testing method of an embodiment of the present application can be implemented based on SOA. Furthermore, in the SOA testing scenario, a role service relationship can be set for the virtual roadside device and the ECU to be tested. Specifically, the role of the virtual roadside device can be set as a service provider, and the role of the ECU to be tested can be set as a service consumer.

[0094] Furthermore, the present application embodiment provides another vehicle-road-cloud collaborative testing method, the specific steps are as follows: Figure 2 As shown, including:

[0095] The user configures the test case on the test interface according to the actual test requirements to obtain the configuration information of the test case, and configures the IP address and MAC address of the ECU to be tested. The control unit of the first device receives the configuration information of the test case, parses the configuration information, and obtains the test case name, interface information, IP address and MAC address in the test case, so as to configure the first device as a virtual roadside device using the test case name, interface information, IP address and MAC address in the test case. Furthermore, the control unit of the first device obtains the IP address and MAC address of the ECU to be tested, and after the IP address and MAC address of the ECU to be tested are transmitted to the address resolution protocol of the virtual roadside device, so that the virtual roadside device can communicate with the ECU to be tested.

[0096] Furthermore, the virtual roadside equipment generates test data, and the control unit sends the test data to the ECU under test. The ECU under test parses the test data to obtain the first display position of the display element in the test data. Further, the ECU under test displays the display element on a display interface connected to the ECU under test. The ECU under test compares the first position information of the display element on the display interface with the preset position information to determine whether the first display position parsed by the ECU under test is the same as the preset position information in the test data. If the first display position is the same as the preset display position in the test data, it is determined that the ECU under test has passed the test. If the first display position is different from the preset display position in the test data, it is determined that the ECU under test has failed the test, thereby completing the vehicle-road-cloud collaborative test.

[0097] Furthermore, the present application provides a vehicle-road-cloud collaborative testing device, specifically Figure 3 As shown, the device comprises:

[0098] The receiving module 301 is used to receive configuration information of the test case, wherein the configuration information is configured by the user in the configuration interface;

[0099] A configuration module 302, configured to configure the first device as a virtual roadside device according to the configuration information, so that the virtual roadside device generates test data of the test case;

[0100] The communication module 303 is used to establish a communication connection between the virtual roadside equipment and the ECU to be tested;

[0101] The testing module 304 is used to send the test data generated by the virtual roadside equipment to the ECU to be tested, so as to test the ECU to be tested using the test data.

[0102] The vehicle-road-cloud collaborative testing device of this embodiment is used to implement the corresponding vehicle-road-cloud collaborative testing methods in the aforementioned multiple method embodiments, and has the beneficial effects of the corresponding method embodiments, which will not be repeated here. In addition, the functional implementation of each module in the deadlock handling device of this embodiment can refer to the description of the corresponding parts in the aforementioned method embodiments, which will not be repeated here.

[0103] Reference Figure 4 , shows a schematic diagram of the structure of an electronic device according to an embodiment of the present application. The specific embodiment of the present application does not limit the specific implementation of the electronic device.

[0104] like Figure 4 As shown, the electronic device may include: a processor (processor) 402 , a communication interface (Communications Interface) 404 , a memory (memory) 406 , and a communication bus 408 .

[0105] in:

[0106] The processor 402 , the communication interface 404 , and the memory 406 communicate with each other via a communication bus 408 .

[0107] The communication interface 404 is used to communicate with other electronic devices or servers.

[0108] The processor 402 is used to execute the program 410, and specifically can execute the relevant steps in the above-mentioned vehicle-road-cloud collaborative testing method embodiment.

[0109] Specifically, the program 410 may include program codes, which include computer operation instructions.

[0110] The processor 402 may be a central processing unit (CPU), or an application-specific integrated circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of the present application. The one or more processors included in the smart device may be processors of the same type, such as one or more CPUs; or processors of different types, such as one or more CPUs and one or more ASICs.

[0111] The memory 406 is used to store the program 410. The memory 406 may include a high-speed RAM memory, and may also include a non-volatile memory (non-volatile memory), such as at least one disk memory.

[0112] The program 410 may be specifically configured to enable the processor 502 to perform the following operations:

[0113] In an optional implementation, the program 510 is also used to enable the processor 402 to implement each step in the program 410. The specific implementation can refer to the corresponding steps and corresponding descriptions in the units in the above-mentioned vehicle-road-cloud collaborative testing method embodiment, which will not be repeated here. Those skilled in the art can clearly understand that for the convenience and simplicity of description, the specific working process of the above-described devices and modules can refer to the corresponding process description in the above-mentioned method embodiment, which will not be repeated here.

[0114] An embodiment of the present application also provides a computer program product, including computer instructions, which instruct a computing device to perform operations corresponding to any vehicle-road-cloud collaborative testing method in the above-mentioned multiple method embodiments.

[0115] It should be pointed out that, according to the needs of implementation, the various components / steps described in the embodiments of the present application can be split into more components / steps, or two or more components / steps or partial operations of components / steps can be combined into new components / steps to achieve the purpose of the embodiments of the present application.

[0116] The above-mentioned method according to the embodiment of the present application can be implemented in hardware, firmware, or implemented as software or computer code that can be stored in a recording medium (such as a CD ROM, RAM, floppy disk, hard disk or magneto-optical disk), or implemented as computer code originally stored in a remote recording medium or a non-temporary machine-readable medium downloaded through a network and to be stored in a local recording medium, so that the method described herein can be stored in such software processing on a recording medium using a general-purpose computer, a dedicated processor or programmable or dedicated hardware (such as an ASIC or FPGA). It can be understood that a computer, a processor, a microprocessor controller or programmable hardware includes a storage component (e.g., RAM, ROM, flash memory, etc.) that can store or receive software or computer code, and when the software or computer code is accessed and executed by a computer, a processor or hardware, the vehicle-road-cloud collaborative testing method described herein is implemented. In addition, when a general-purpose computer accesses the code for implementing the vehicle-road-cloud collaborative testing method shown herein, the execution of the code converts the general-purpose computer into a dedicated computer for executing the vehicle-road-cloud collaborative testing method shown herein.

[0117] Those of ordinary skill in the art will appreciate that the units and method steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of the embodiments of the present application.

[0118] The above implementation methods are only used to illustrate the embodiments of the present application, and are not limitations on the embodiments of the present application. Ordinary technicians in the relevant technical field can make various changes and modifications without departing from the spirit and scope of the embodiments of the present application. Therefore, all equivalent technical solutions also belong to the scope of the embodiments of the present application. The scope of patent protection of the embodiments of the present application should be limited by the claims.

Claims

1. A vehicle-road-cloud collaborative testing method, characterized in that: The method comprises: Receive configuration information of the test case, wherein the configuration information is configured by a user in a configuration interface; Configuring the first device as a virtual roadside device according to the configuration information, so that the virtual roadside device generates test data for the test case; Establishing a communication connection between the virtual roadside equipment and the ECU to be tested; The test data generated by the virtual roadside equipment is sent to the ECU to be tested, so as to test the ECU to be tested using the test data.

2. The method according to claim 1, characterized in that: The configuration information includes test case name, interface information and communication parameters; The configuring the first device as a roadside device according to the configuration information includes: Parsing the configuration information to obtain the test case name, the interface information and the communication parameters; The first device is configured as the virtual roadside device according to the test case name, the interface information and the communication parameters.

3. The method according to claim 2, characterized in that The communication parameters IP address and MAC address; The configuring the first device as the virtual roadside device according to the test case name, the interface information and the communication parameters includes: Obtain the IP address and the MAC address; The address of the network card of the first device is configured as the IP address and the MAC address, so as to configure the first device as the virtual roadside device according to the test case name, the interface information and the communication parameters.

4. The method according to claim 1, characterized in that: The establishing of a communication connection between the virtual roadside equipment and the ECU to be tested includes: Receiving the IP address and MAC address of the ECU to be tested, wherein the IP address and MAC address of the ECU to be tested are configured by the user in a configuration interface; The IP address and MAC address of the ECU to be tested are added to the address resolution protocol of the virtual roadside device to establish a communication connection between the virtual roadside device and the ECU to be tested.

5. The method according to claim 1, characterized in that The step of sending the test data generated by the virtual roadside equipment to the ECU to be tested, so as to test the ECU to be tested using the test data, includes: Sending the test data generated by the virtual roadside equipment to the ECU to be tested; The ECU to be tested parses the received test data to obtain a first display position of a display element in the test data; Displaying the display element on the display interface according to the first display position of the display element; The test result of the ECU to be tested is determined according to the display result of the display interface.

6. The method according to claim 5, characterized in that The display result of the display interface determines the test result of the ECU to be tested, including: Acquire a first display position of the display element on the display interface; If the first display position is the same as the preset display position in the test data, determining that the ECU to be tested passes the test; If the first display position is different from a preset display position in the test data, it is determined that the ECU to be tested has failed the test.

7. The method according to claim 1, characterized in that The method further comprises: If the ECU under test fails the test, the ECU under test sends a fault message to the virtual roadside device.

8. A vehicle-road-cloud collaborative testing device, characterized in that: The device comprises: A receiving module, used to receive configuration information of a test case, wherein the configuration information is configured by a user in a configuration interface; A configuration module, configured to configure the first device as a virtual roadside device according to the configuration information, so that the virtual roadside device generates test data for the test case; A communication module, used to establish a communication connection between the virtual roadside equipment and the ECU to be tested; The test module is used to send the test data generated by the virtual roadside equipment to the ECU to be tested, so as to test the ECU to be tested using the test data.

9. An electronic device, comprising: A processor, a memory, a communication interface and a communication bus, wherein the processor, the memory and the communication interface communicate with each other via the communication bus; The memory is used to store at least one executable instruction, and the executable instruction enables the processor to perform operations corresponding to the vehicle-road-cloud collaborative testing method as described in any one of claims 1-7.

10. A computer storage medium having a computer program stored thereon, which, when executed by a processor, implements the vehicle-road-cloud collaborative testing method as described in any one of claims 1 to 7.

Images