Vehicle control link test method and device, storage medium and electronic device

Abstract

The invention provides a test method and device of a vehicle control link, a storage medium and an electronic device.The method comprises the steps that an application program on a mobile terminal is controlled to send a remote test signal to the vehicle control link, and the vehicle control link comprises the mobile terminal, a cloud end and a vehicle end of a simulation rack which are connected in a closed loop mode; monitoring a signal sending state of an electronic control unit VI U device on the vehicle end; querying log data based on the signal sending state; and positioning an abnormal node on the vehicle control link according to a query result of the log data. Through the embodiment of the invention, the technical problem that a real use scene cannot be restored when a full-link test is carried out on the automobile in related technologies is solved, the test difficulty and the test cost are reduced, and the test efficiency is improved.

Description

Technical Field

[0001] The present invention relates to the field of vehicle technology, and in particular to a vehicle control link testing method and device, a storage medium, and an electronic device. Background Art

[0002] In related technologies, with the rapid development of mobile Internet, remote control of vehicles through mobile phones has become the main label of smart cars. Remote control usually includes functions such as remote car search, vehicle start-up, remote door unlocking, remote air conditioning, and remote vehicle status viewing, which greatly improves the convenience and comfort of car owners. Due to the increasing complexity of remote control functions, in actual usage scenarios, remote control functions often have problems such as remote control failure and long command response time. The stability of this function is highly related to the user experience and is the focus of automobile research and development testing. However, since remote control involves the linkage of multiple system functions and a long data link, testing is difficult, inefficient, difficult to reproduce, and has a long problem location cycle.

[0003] In related technologies, it is not easy to conduct full-link testing for vehicle remote control testing because the test link is too long. Most of them choose to MOCK (forge) certain links in the link to achieve the effect of full-link testing, which cannot achieve automated testing that is close to the user's actual usage scenarios.

[0004] With respect to the above-mentioned problems existing in the related technologies, no efficient and accurate solutions have been found yet. Summary of the invention

[0005] The present invention provides a vehicle control link testing method and device, a storage medium, and an electronic device to solve technical problems in related technologies.

[0006] According to one embodiment of the present invention, a method for testing a vehicle control link is provided, comprising: controlling an application on a mobile terminal to send a remote test signal to the vehicle control link, wherein the vehicle control link includes the mobile terminal, the cloud, and a vehicle end of a simulation test bench in a closed loop connection; monitoring the signal sending status of an electronic control unit VI U device on the vehicle end; querying log data based on the signal sending status; and locating abnormal nodes on the vehicle control link according to the query results of the log data.

[0007] Optionally, monitoring the signal sending status of the VI U device on the vehicle side includes: monitoring a designated bus signal output by the VI U device on the vehicle side through a bus analysis device, wherein the designated bus signal corresponds to the remote test signal; if the designated bus signal is monitored, determining that the signal sending status of the VI U device is that the designated bus signal has been issued; if the designated bus signal is not monitored, determining that the signal sending status of the VI U device is that the designated bus signal has not been issued.

[0008] Optionally, querying log data based on the signal sending status includes: if the signal sending status is that the designated bus signal is not issued, querying the historical request data port of the cloud; obtaining the historical request record of the historical request data port; determining whether there is a designated request record of the mobile terminal in the historical request record; if the designated request record of the mobile terminal does not exist in the historical request record, querying the terminal log data on the mobile terminal.

[0009] Optionally, after determining whether there is a specified request record of the mobile terminal in the historical request record, the method further includes: if there is a specified request record of the mobile terminal in the historical request record, requesting a remote control log query interface of the cloud; using the remote control log query interface to query a first remote control log and a second remote control log of the cloud, wherein the first remote control log is a remote control log that records the cloud requested by the application, and the second remote control log is a remote control log that records the cloud requesting the vehicle.

[0010] Optionally, after using the remote control log query interface to query the first remote control log and the second remote control log in the cloud, the method further includes: if the first remote control log and the second remote control log in the cloud are queried, querying the TBOX log from the Internet of Vehicles TBOX on the vehicle side.

[0011] Optionally, querying log data based on the signal sending status includes: if the signal sending status is that the specified bus signal has been sent, determining whether the graphical interface of the application has changed accordingly; if the graphical interface of the application has not changed accordingly, requesting the data acquisition log interface of the cloud; using the data acquisition log interface to query the first data acquisition log and the second data acquisition log, wherein the first data acquisition log is a data acquisition log recording the data acquisition log from the vehicle to the cloud, and the second data acquisition log is a data acquisition log recording the data acquisition log from the cloud to the application.

[0012] Optionally, locating the abnormal node on the vehicle control link according to the query result of the log data includes: if the query result is that the terminal log data is queried, parsing the terminal log data, and locating the abnormal node on the vehicle control link as the application; if the query result is that the first remote control log is not queried, locating the abnormal node on the vehicle control link as the link between the application and the cloud; if the query result is that the first remote control log is queried and the second remote control log is not queried, locating the abnormal node on the vehicle control link as the link between the cloud and the vehicle end; if the query result is that the TBOX log is queried, detecting whether a specified keyword exists in the TBOX log, and locating the abnormal node on the vehicle control link according to the detection result; if the query result is that the first data acquisition log is not queried, locating the abnormal node on the vehicle control link as the link between the vehicle end and the cloud; if the query result is that the first data acquisition log is queried and the second data acquisition log is not queried, locating the abnormal node on the vehicle control link as the link between the cloud and the application.

[0013] Optionally, locating the abnormal node on the vehicle control link according to the detection result includes: if the detection result is that the specified keyword is not detected, locating the abnormal node on the vehicle control link as the TBOX on the vehicle side; if the detection result is that the specified keyword is detected, locating the abnormal node on the vehicle control link as the VI U device on the vehicle side.

[0014] According to one embodiment of the present invention, another method for testing a vehicle control link is provided, comprising: controlling an application on a mobile terminal to send a remote test signal to the vehicle control link, wherein the vehicle control link includes the mobile terminal, the cloud, and a physical vehicle end connected in a closed loop; determining a test type of the remote test signal, wherein the test type includes a stateful test in which the remote test signal causes a graphic interface change of the application and a stateless test in which the remote test signal does not cause a graphic interface change of the application; querying log data based on the test type; and locating abnormal nodes on the vehicle control link according to the query results of the log data.

[0015] Optionally, querying log data based on the test type includes: if the test type is a stateful test, determining whether the image interface of the application has changed; if the image interface of the application has changed, querying the historical request data port on the cloud; obtaining the historical request records of the historical request data port; determining whether there is a specified request record of the mobile terminal in the historical request records; if there is no specified request record of the mobile terminal in the historical request records, querying the terminal log data on the mobile terminal.

[0016] Optionally, after determining whether there is a specified request record of the mobile terminal in the historical request record, the method further includes: if there is a specified request record of the mobile terminal in the historical request record, requesting a remote control log query interface of the cloud; using the remote control log query interface to query a first remote control log and a second remote control log of the cloud, wherein the first remote control log is a remote control log that records the cloud requested by the application, and the second remote control log is a remote control log that records the cloud requesting the vehicle.

[0017] Optionally, after using the remote control log query interface to query the first remote control log and the second remote control log on the cloud, the method also includes: if the first remote control log and the second remote control log on the cloud are queried, querying the TBOX log from the Internet of Vehicles TBOX on the vehicle side; detecting whether the TBOX log contains specified keywords; if the specified keywords exist, using the data acquisition log interface to query the first data acquisition log and the second data acquisition log, wherein the first data acquisition log is a data acquisition log recording from the vehicle side to the cloud, and the second data acquisition log is a data acquisition log recording from the cloud side to the application.

[0018] Optionally, querying log data based on the test type includes: if the test type is a stateless test, querying the historical request data port of the cloud; obtaining the historical request records of the historical request data port; determining whether there is a specified request record of the mobile terminal in the historical request records; if the specified request record of the mobile terminal does not exist in the historical request records, querying the terminal log data on the mobile terminal.

[0019] Optionally, after determining whether there is a specified request record of the mobile terminal in the historical request record, the method further includes: if there is a specified request record of the mobile terminal in the historical request record, requesting a remote control log query interface on the cloud; using the remote control log query interface to query a first remote control log and a second remote control log on the cloud, wherein the first remote control log is a remote control log recording the cloud requested by the application, and the second remote control log is a remote control log recording the cloud requesting the vehicle end; if the first remote control log and the second remote control log on the cloud are queried, querying the TBOX log from the Internet of Vehicles TBOX on the vehicle end.

[0020] Optionally, locating the abnormal node on the vehicle control link according to the query result of the log data includes: if the query result is that the terminal log data is queried, parsing the terminal log data, and locating the abnormal node on the vehicle control link as the application; if the query result is that the first remote control log is not queried, locating the abnormal node on the vehicle control link as the link between the application and the cloud; if the query result is that the first remote control log is queried and the second remote control log is not queried, locating the abnormal node on the vehicle control link as the link between the cloud and the vehicle end; if the query result is that the TBOX log is queried, detecting whether a specified keyword exists in the TBOX log, and if the specified keyword does not exist, locating the abnormal node on the vehicle control link as the TBOX; if the query result is that the first data acquisition log is not queried, locating the abnormal node on the vehicle control link as the link between the vehicle end and the cloud; if the query result is that the first data acquisition log is queried and the second data acquisition log is not queried, locating the abnormal node on the vehicle control link as the link between the cloud and the application.

[0021] According to another embodiment of the present invention, a test device for a vehicle control link is provided, comprising: a control module, used to control an application on a mobile terminal to send a remote test signal to the vehicle control link, wherein the vehicle control link includes the mobile terminal, the cloud, and the vehicle end of the simulation test bench in a closed loop connection; a monitoring module, used to monitor the signal sending status of the electronic control unit VIU device on the vehicle end; a query module, used to query log data based on the signal sending status; and a positioning module, used to locate abnormal nodes on the vehicle control link according to the query results of the log data.

[0022] According to another embodiment of the present invention, another vehicle control link testing device is provided, including: a control module, used to control an application on a mobile terminal to send a remote test signal to the vehicle control link, wherein the vehicle control link includes the mobile terminal, the cloud, and the physical vehicle end connected in a closed loop; a determination module, used to determine the test type of the remote test signal, wherein the test type includes a stateful test in which the remote test signal causes a graphic interface change of the application and a stateless test in which the remote test signal does not cause a graphic interface change of the application; a query module, used to query log data based on the test type; and a positioning module, used to locate abnormal nodes on the vehicle control link according to the query results of the log data.

[0023] According to another aspect of an embodiment of the present application, a storage medium is further provided, which includes a stored program, and the above steps are executed when the program is run.

[0024] According to another aspect of an embodiment of the present application, there is also provided an electronic device, including a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory communicate with each other via the communication bus; wherein: the memory is used to store computer programs; and the processor is used to execute the steps in the above method by running the program stored in the memory.

[0025] The embodiment of the present application also provides a computer program product including instructions, which, when executed on a computer, enables the computer to execute the steps in the above method.

[0026] Beneficial effects of the present invention:

[0027] 1. For the remote control test on the test bench, the analog controller sends bus signals to the VIU to complete the data link closed loop, and the remote control function is automatically tested through a simple ring network test bench, which significantly reduces the test cost;

[0028] 2. For the remote control test of the real vehicle, only two USB cables are needed to connect the real vehicle and the mobile phone respectively. The deployment is much simpler than the ring network test bench, and the test scenarios are also richer than the test bench. BRIEF DESCRIPTION OF THE DRAWINGS

[0029] The drawings described herein are used to provide a further understanding of the present invention and constitute a part of this application. The exemplary embodiments of the present invention and their descriptions are used to explain the present invention and do not constitute an improper limitation of the present invention. In the drawings:

[0030] Figure 1 is a hardware structure block diagram of a car according to an embodiment of the present invention;

[0031] Figure 2 is a flow chart of a method for testing a vehicle control link according to an embodiment of the present invention;

[0032] Figure 3 is a flow chart of a remote vehicle control service in an embodiment of the present invention;

[0033] Figure 4 is a timing diagram of vehicle remote control in an embodiment of the present invention;

[0034] Figure 5 is a topological diagram of a bench remote control test in an embodiment of the present invention;

[0035] Figure 6 is a flow chart of a test bench remote control automation test in an embodiment of the present invention;

[0036] Figure 7 is a flow chart of another vehicle control link testing method according to an embodiment of the present invention;

[0037] Figure 8is a topological diagram of a real vehicle remote control test in an embodiment of the present invention;

[0038] Fig. 9 is a flow chart of a real vehicle state test in an embodiment of the present invention;

[0039] Fig.10 is a flow chart of a real vehicle stateless test in an embodiment of the present invention;

[0040] Fig.11 is a structural block diagram of a vehicle control link testing device according to an embodiment of the present invention;

[0041] Fig.12 It is a structural block diagram of another vehicle control link testing device according to an embodiment of the present invention. DETAILED DESCRIPTION

[0042] In order to enable those skilled in the art to better understand 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 embodiments of a part of the present application, not all embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in the field without creative work should fall within the scope of protection of the present application. It should be noted that the embodiments in the present application and the features in the embodiments can be combined with each other without conflict.

[0043] It should be noted that the terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments of the present application described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, a process, method, product or device comprising a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0044] Example 1

[0045] The method embodiment provided in the first embodiment of the present application can be executed in a computer, a test host, a host computer, a processor, a controller or a similar processing device. Taking running on a computer as an example, Figure 1 is a hardware structure block diagram of a computer according to an embodiment of the present invention. Figure 1 As shown, the computer may include one or more ( Figure 1Only one is shown in the figure) a processor 102 (the processor 102 may include but is not limited to a processing device such as a microprocessor MCU or a programmable logic device FPGA) and a memory 104 for storing data. Optionally, the computer may also include a transmission device 106 and an input / output device 108 for communication functions. It can be understood by those skilled in the art that Figure 1 The structure shown is only for illustration and does not limit the structure of the above-mentioned computer. Figure 1 More or fewer components as shown, or with Figure 1 Different configurations are shown.

[0046] The memory 104 can be used to store computer programs, for example, software programs and modules of application software, such as a computer program corresponding to a test method for a vehicle control link of a computer in an embodiment of the present invention. The processor 102 executes various functional applications and data processing by running the computer program stored in the memory 104, that is, to implement the above method. The memory 104 may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some examples, the memory 104 may further include a memory remotely arranged relative to the processor 102, and these remote memories may be connected to the computer via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0047] The transmission device 106 is used to receive or send data via a network. The specific example of the above network may include a wireless network provided by a communication provider of the computer. In one example, the transmission device 106 includes a network adapter (Network Interface Controller, referred to as NIC), which can be connected to other network devices through a base station so as to communicate with the Internet. In one example, the transmission device 106 can be a radio frequency (RF) module, which is used to communicate with the Internet wirelessly.

[0048] In this embodiment, a method for testing a vehicle control link is provided. Figure 2 is a flow chart of a method for testing a vehicle control link according to an embodiment of the present invention. Figure 2 As shown, the process includes the following steps:

[0049] Step S202, controlling the application on the mobile terminal to send a remote test signal to the vehicle control link, wherein the vehicle control link includes the mobile terminal, the cloud, and the vehicle end of the simulation test bench in a closed loop connection;

[0050] Optionally, the mobile terminal may be a user terminal device such as a mobile phone.

[0051] The first link and the second link of the vehicle control link in this embodiment, the first link includes mobile phone APP->cloud->vehicle side, and the second link includes vehicle side->cloud->mobile phone APP, forming a complete closed-loop link from mobile phone side->cloud->vehicle side->cloud->mobile phone side.

[0052] Step S204, monitoring the signal transmission status of the electronic control unit VIU device on the vehicle end;

[0053] The data link is closed by sending CAN / LIN signals from the analog controller to the VIU. The controller and VIU communicate via bus signals and can be simulated via bus signal equipment.

[0054] Step S206, querying log data based on the signal sending status;

[0055] Step S208: locating abnormal nodes on the vehicle control link according to the query result of the log data.

[0056] Through the above steps, the application on the mobile terminal is controlled to send a remote test signal to the vehicle control link, and the signal sending status of the electronic control unit VIU device on the vehicle side is monitored; the log data is queried based on the signal sending status; the abnormal nodes on the vehicle control link are located according to the query results of the log data, and the remote control function is automatically tested through a simple ring network test bench, which solves the technical problem that the relevant technology cannot restore the real usage scenario when performing full-link testing on the car, reduces the test difficulty and test cost, and improves the test efficiency.

[0057] Figure 3 is a flow chart of the remote vehicle control service in an embodiment of the present invention, Figure 4It is a timing diagram of vehicle remote control in an embodiment of the present invention. Through the above analysis of the complete link of the remote vehicle control business process, the tested business can be divided into three modules, APP side / mobile phone side, cloud side, and vehicle side. A parsing device is inserted in each module to provide the feasibility of automated testing. It illustrates the data flow when the remote vehicle is successfully controlled. First, the user operates the mobile phone APP, and the mobile phone APP sends the remote control command to the cloud proxy module through MQTT (Message Queuing Telemetry Transport), and the cloud proxy module forwards the remote control command to the cloud remote control module through the message middleware; the cloud remote control module converts the remote control command into the vehicle-side MQTT related protocol and sends it to the vehicle-side proxy module in TBOX; the vehicle-side proxy module parses the vehicle-side MQTT protocol, and then forwards the remote control command to the vehicle-side remote control module; the vehicle-side remote control module parses the control command after receiving it, and calls VIU (Vehicle Information Unit, electronic control unit) proxy module to trigger the call of RPC (remote procedure call) control service module, or directly call the RPC control service module; when the RPC control service module receives the call, it returns a specified code (such as 2000, 2001) to represent that the instruction has been received, and when the execution result is completed, it returns a specified code to represent that the execution result is completed; the vehicle-side remote control service module returns the returned result to the cloud through the vehicle-side proxy module; the cloud-side remote control module forwards the status information uploaded by the vehicle and the returned result to the mobile phone APP through the cloud-side proxy module; finally, the mobile phone APP makes corresponding display on the page according to the result returned by the cloud-side proxy module.

[0058] In one implementation of the present embodiment, monitoring the signal sending status of the VIU device on the vehicle side includes: monitoring a designated bus signal output by the VIU device on the vehicle side through a bus analysis device, wherein the designated bus signal corresponds to the remote test signal; if the designated bus signal is monitored, determining that the signal sending status of the VIU device is that the designated bus signal has been issued; if the designated bus signal is not monitored, determining that the signal sending status of the VIU device is that the designated bus signal has not been issued.

[0059] In a test scenario of the present embodiment, querying log data based on the signal sending status includes: if the signal sending status is that the designated bus signal is not sent, querying the historical request data port of the cloud; obtaining the historical request record of the historical request data port; determining whether there is a designated request record of the mobile terminal in the historical request record; if the designated request record of the mobile terminal does not exist in the historical request record, querying the terminal log data on the mobile terminal.

[0060] In this scenario, click the test APP, and read the VIU device through the bus analysis device. The device does not send out the specified CAN / LIN signal, and the test is judged to have failed. Continue to analyze the cause of the failure, query the cloud historical request data interface (the interface is deployed in the cloud, and the interface can query the historical data of the request cloud interface), and if the specified data is not obtained, pull the test APP log to the local computer, parse the test APP log, and locate the failure to the test APP, and provide the reason for the test APP log error.

[0061] The function of the historical request data interface is to obtain the historical records of requests sent to the cloud. For example, after successfully clicking the APP to turn on the air conditioner, this interface can be used to obtain the historical data of the remote control request made by the test app to the cloud to turn on the air conditioner. This data will carry the relevant parameters for turning on the air conditioner.

[0062] In a test scenario of the present embodiment, after determining whether there is a specified request record of the mobile terminal in the historical request record, it also includes: if there is a specified request record of the mobile terminal in the historical request record, requesting the remote control log query interface of the cloud; using the remote control log query interface to query the first remote control log and the second remote control log of the cloud, wherein the first remote control log is a remote control log that records the cloud requested by the application, and the second remote control log is a remote control log that records the cloud requesting the vehicle end.

[0063] In this scenario, click the test APP, and read the VIU device through the bus analysis device. The device does not send out the specified CAN / LIN signal, and the test is judged to have failed. Continue to analyze the cause of the failure, query the cloud history request data interface, obtain the specified data, extract the cloud-related fields requested from the data, and continue to request the cloud remote control log query interface. First, check whether the APP to cloud log (first remote control log) and the cloud to vehicle log (second remote control log) are normal. If the APP to cloud log is not detected, the failure is located to the failure of the APP to cloud link; if the APP to cloud log is detected and the cloud to vehicle log is not detected, the failure is located to the failure of the cloud to vehicle link.

[0064] The cloud remote control log query interface is deployed in the cloud. The function of this interface is to query the cloud to send remote control specified log records. The log records are in ES (Elastic Search). By calling the interface and passing the specified parameters, the required log information can be filtered.

[0065] In a test scenario of this embodiment, after using the remote control log query interface to query the first remote control log and the second remote control log on the cloud, it also includes: if the first remote control log and the second remote control log on the cloud are queried, query the TBOX log from the Internet of Vehicles TBOX on the vehicle side.

[0066] In this scenario, click the test APP, and read the VIU device through the bus analysis device. The specified CAN / LIN signal is not sent, and the test is judged to have failed. Continue to analyze the cause of the failure, query the cloud historical request data interface, obtain the specified data, extract the cloud-related fields requested from the data, and continue to request the cloud remote control log query interface. First, check that the APP to cloud log and the cloud to vehicle log are normal, pull the TBOX log, and check the specified keywords in the TBOX log. If not detected, the failure is located at the TBOX failure. If detected, parse the VIU message and locate the VIU module failure.

[0067] In a test scenario of the present embodiment, querying log data based on the signal sending status includes: if the signal sending status is that the specified bus signal has been sent, determining whether the graphical interface of the application has changed accordingly; if the graphical interface of the application has not changed accordingly, requesting the data acquisition log interface of the cloud; using the data acquisition log interface to query the first data acquisition log and the second data acquisition log, wherein the first data acquisition log is a data acquisition log recording the data acquisition log from the vehicle to the cloud, and the second data acquisition log is a data acquisition log recording the data acquisition log from the cloud to the application.

[0068] For example, in the test APP, click to turn on the air conditioner on the vehicle side, and then read the signal information of VIU through the bus analysis device. It is read that VIU has sent the expected signal (specified bus signal) related to turning on the air conditioner. At this time, the bus device can be used to simulate the lower pendant of the air conditioner to send a feedback signal to VIU.

[0069] In this scenario, click on the test APP, read the specified bus signal sent by VIU through the bus analysis device, and send the corresponding signal to VIU through the bus device simulation controller. Check whether the test APP UI has made corresponding changes. If the test APP UI has not changed, the test is judged to have failed. Continue to analyze the cause of the failure, request the cloud data collection log interface, and successively check whether the vehicle-to-cloud data collection log and the cloud-to-APP data collection log are normal. If the vehicle-to-cloud data collection log is not detected, the failure is located to the failure of the vehicle-to-cloud data collection link; if the vehicle-to-cloud data collection log is detected and the cloud-to-APP data collection log is not detected, the failure is located to the failure of the cloud-to-APP data collection link.

[0070] In the present embodiment, when the test fails, locating the abnormal node on the vehicle control link according to the query result of the log data includes: if the query result is that the terminal log data is queried, parsing the terminal log data, and locating the abnormal node on the vehicle control link as the application; if the query result is that the first remote control log is not queried, locating the abnormal node on the vehicle control link as the link between the application and the cloud; if the query result is that the first remote control log is queried and the second remote control log is not queried, locating the abnormal node on the vehicle control link as the link between the cloud and the vehicle end; if the query result is that the TBOX log is queried, detecting whether there is a specified keyword in the TBOX log, and locating the abnormal node on the vehicle control link according to the detection result; if the query result is that the first data acquisition log is not queried, locating the abnormal node on the vehicle control link as the link between the vehicle end and the cloud; if the query result is that the first data acquisition log is queried and the second data acquisition log is not queried, locating the abnormal node on the vehicle control link as the link between the cloud and the application.

[0071] In one example, locating the abnormal node on the vehicle control link according to the detection result includes: if the detection result is that the specified keyword is not detected, locating the abnormal node on the vehicle control link as the TBOX on the vehicle side; if the detection result is that the specified keyword is detected, locating the abnormal node on the vehicle control link as the VIU device on the vehicle side.

[0072] The above test scenarios are all test failure scenarios. In the test success scenario, click the test APP, read the specified signal sent by VIU through the bus analysis device, and send the corresponding signal to VIU through the bus device simulation controller. Check whether the test APP UI has changed accordingly. If the test APP UI has changed, the test is judged to be successful.

[0073] In the above test scenarios, the vehicle is replaced by a simulated bench. For bench remote control testing, Figure 5 This is a topology diagram of the bench remote control test in the embodiment of the present invention, which provides a set of automated test deployment diagrams for the ring network bench. Since the bench environment has no real hanging parts, in this solution, the bus signal simulation device is used to simulate the controller receiving the signal sent by the VIU, and simulate sending CAN / LIN signals to the VIU to complete the data link closed loop. According to the test deployment diagram, Figure 6 It is a flow chart of the test bench remote control automation test in an embodiment of the present invention, from which a variety of test scenarios can be obtained, specifically the multiple test scenarios described above.

[0074] The above embodiments are for the bench environment. The scheme for testing on the bench has specific prerequisites. The controller and VIU of the function to be tested must communicate through bus signals. In this scheme, the bus signal simulation device is used for testing. Through this scheme, such types of remote control functions can be automatically tested through a simple ring network bench deployment, which can significantly reduce the cost of testing. In this deployment scheme, a host computer is required to be connected to the mobile phone and the bus signal device respectively through a USB cable. The host computer interacts with the cloud data query interface through the office network, and the host computer is connected to the ring network bench through a switch.

[0075] In this embodiment, a method for testing a vehicle control link is provided. Figure 7 FIG. 1 is a flow chart of another method for testing a vehicle control link according to an embodiment of the present invention. Figure 7 As shown, the process includes the following steps:

[0076] Step S702, controlling the application on the mobile terminal to send a remote test signal to the vehicle control link, wherein the vehicle control link includes the mobile terminal, the cloud, and the physical vehicle end in a closed loop connection;

[0077] Step S704, determining the test type of the remote test signal, wherein the test type includes a stateful test in which the remote test signal causes a graphic interface change of the application program and a stateless test in which the remote test signal does not cause a graphic interface change of the application program;

[0078] Step S706, querying log data based on the test type;

[0079] Step S708: locating abnormal nodes on the vehicle control link according to the query result of the log data.

[0080] Figure 8 It is a topology diagram of the real vehicle remote control test in the embodiment of the present invention, and provides a set of real vehicle automated test deployment diagrams. Since the real vehicle has real hanging parts, it can be tested by combining data detection test and UI image recognition, which is more in line with the real use scenario. Since some functions change the UI after operation, this function is called stateful real vehicle test; but some functions do not change the UI after operation, and this function is called stateless real vehicle test.

[0081] Fig. 9 This is a flowchart of the real vehicle stateful test in the embodiment of the present invention. The stateful real vehicle automated test process, since the UI is expected to change after the operation, mainly uses the detection of UI changes combined with data link detection as the result judgment criterion. A variety of test scenarios can be obtained from it, and examples are given here:

[0082] In a test scenario, click the test APP to detect whether the test APPUI I has been changed accordingly. If the test APPUI I has been changed, the test is judged to be successful.

[0083] In one implementation of the stateful real vehicle test in the present embodiment, querying log data based on the test type includes: if the test type is a stateful test, determining whether the image interface of the application has changed; if the image interface of the application has changed, querying the historical request data port on the cloud; obtaining the historical request records of the historical request data port; determining whether there is a specified request record of the mobile terminal in the historical request records; if there is no specified request record of the mobile terminal in the historical request records, querying the terminal log data on the mobile terminal.

[0084] In a test scenario, click the test app and check that the test app UI has not changed, judging that the test has failed. Continue to analyze the cause of the failure, query the cloud historical request data interface, and if no data is obtained, pull the test app log to the local computer and locate the failure to the test app.

[0085] In one implementation scenario, after determining whether there is a specified request record of the mobile terminal in the historical request record, it also includes: if there is a specified request record of the mobile terminal in the historical request record, requesting the remote control log query interface of the cloud; using the remote control log query interface to query the first remote control log and the second remote control log of the cloud, wherein the first remote control log is a remote control log that records the cloud requested by the application, and the second remote control log is a remote control log that records the cloud requesting the vehicle end.

[0086] In this test scenario, click the test APP, check that the test APPUI I has not changed, and judge that the test has failed. Continue to analyze the cause of the failure, query the cloud history request data interface, obtain the data, extract the relevant fields of the request cloud from the data, and continue to request the cloud remote control log query interface to check whether the APP to cloud log and the cloud to car log are normal. If the APP to cloud log is not detected, the failure is located to the failure of the APP to cloud link; if the APP to cloud log is detected and the cloud to car log is not detected, the failure is located to the failure of the cloud to car link.

[0087] In one implementation scenario, after using the remote control log query interface to query the first remote control log and the second remote control log on the cloud, it also includes: if the first remote control log and the second remote control log on the cloud are queried, query the TBOX log from the Internet of Vehicles TBOX on the vehicle side; detect whether the TBOX log contains specified keywords; if the specified keywords exist, use the data acquisition log interface to query the first data acquisition log and the second data acquisition log, wherein the first data acquisition log is a data acquisition log that records the data from the vehicle side to the cloud, and the second data acquisition log is a data acquisition log that records the data from the cloud side to the application.

[0088] In a test scenario based on this implementation scenario, click on the test APP, check that the test APPUI I has not changed, and judge that the test has failed. Continue to analyze the cause of the failure, query the cloud historical request data interface, obtain the data, extract the relevant fields of the request cloud from the data, continue to request the cloud remote control log query interface, successively check that the APP to cloud log and the cloud to car log are normal, pull the TBOX log, and check the specified keywords in the TBOX log. If not detected, the failure is located at TBOX failure.

[0089] In another test scenario based on this implementation scenario, click on the test APP, check that the test APPUI I has not changed, and judge that the test has failed. Continue to analyze the cause of the failure, query the cloud historical request data interface, obtain the data, extract the cloud-related fields requested from the data, and continue to request the cloud remote control log query interface, successively check that the APP to cloud log and the cloud to car log are normal, pull the TBOX log, and detect the specified keywords of the TBOX log. Request the cloud data collection log interface, successively check whether the car-to-cloud data collection log and the cloud-to-APP data collection log are normal. If the car-to-cloud data collection log is not detected, the failure is located to the failure of the car-to-cloud data collection link; if the car-to-cloud data collection log is detected, and the cloud-to-APP data collection log is not detected, the failure is located to the failure of the cloud-to-APP data collection link.

[0090] Fig.10 This is a flowchart of the real vehicle stateless test in the embodiment of the present invention. The stateless real vehicle automated test process, since the UI will not change after the operation, all such functions are tested through full-link data flow detection as the test judgment standard. A variety of test scenarios can be obtained from it, and examples are given here:

[0091] In one implementation of the stateless real vehicle test in the present embodiment, querying log data based on the test type includes: if the test type is a stateless test, querying the historical request data port on the cloud; obtaining the historical request records of the historical request data port; determining whether there is a specified request record of the mobile terminal in the historical request records; if there is no specified request record of the mobile terminal in the historical request records, querying the terminal log data on the mobile terminal.

[0092] In a test scenario, click on the test APP to query the cloud historical request data interface. If no data is obtained, pull the test APP log and locate the failure to the test APP.

[0093] In one implementation scenario, after determining whether there is a specified request record of the mobile terminal in the historical request record, it also includes: if there is a specified request record of the mobile terminal in the historical request record, requesting the remote control log query interface of the cloud; using the remote control log query interface to query the first remote control log and the second remote control log of the cloud, wherein the first remote control log is a remote control log that records the cloud requested by the application, and the second remote control log is a remote control log that records the cloud requesting the vehicle end; if the first remote control log and the second remote control log of the cloud are queried, query the TBOX log from the Internet of Vehicles TBOX of the vehicle end.

[0094] In a test scenario based on this implementation scenario, click the test APP to query the cloud historical request data interface to obtain data, extract the cloud-related request fields from the data, and continue to request the cloud remote control log query interface to check whether the APP-to-cloud log and the cloud-to-car log are normal. If the APP-to-cloud log is not detected, the failure is located to the failure of the APP-to-cloud link; if the APP-to-cloud log is detected and the cloud-to-car log is not detected, the failure is located to the failure of the cloud-to-car link.

[0095] In another test scenario based on this implementation scenario, click the test APP to query the cloud historical request data interface, obtain the data, extract the cloud-related fields requested from the data, continue to request the cloud remote control log query interface, first check that the APP to cloud log and the cloud to car log are normal, pull the TBOX log, and detect the specified keywords in the TBOX log. If not detected, the failure is located at TBOX failure.

[0096] In an embodiment based on actual vehicle testing, locating the abnormal node on the vehicle control link according to the query result of the log data includes: if the query result is that the terminal log data is queried, parsing the terminal log data, and locating the abnormal node on the vehicle control link as the application; if the query result is that the first remote control log is not queried, locating the abnormal node on the vehicle control link as the link between the application and the cloud; if the query result is that the first remote control log is queried and the second remote control log is not queried, locating the abnormal node on the vehicle control link as the link between the cloud and the vehicle end; if the query result is that the TBOX log is queried, detecting whether there is a specified keyword in the TBOX log, if the specified keyword does not exist, locating the abnormal node on the vehicle control link as the TBOX; if the query result is that the first data acquisition log is not queried, locating the abnormal node on the vehicle control link as the link between the vehicle end and the cloud; if the query result is that the first data acquisition log is queried and the second data acquisition log is not queried, locating the abnormal node on the vehicle control link as the link between the cloud and the application.

[0097] In a test scenario, click the test APP to query the cloud historical request data interface, obtain the data, extract the cloud-related fields requested from the data, continue to request the cloud remote control log query interface, first check that the APP to cloud log and the cloud to car log are normal, pull the TBOX log, and detect the specified keywords in the TBOX log, then the execution is judged to be successful.

[0098] The above embodiment is for remote control automation testing of real vehicles. In this solution, a real vehicle and a mobile phone are required to be connected to the host computer via a USB cable. The deployment is much simpler than that of the test bench, and the test scenarios are richer and cover a wider range than the test bench. However, the test resource requirements are higher.

[0099] This embodiment considers the use scenarios of real users and proposes a set of link analysis and automated testing methods based on the remote control function of the vehicle. By simulating human operation of the mobile phone, the data uplink and data downlink are tested at the same time, and finally the mobile phone display results are judged to achieve the purpose of full link testing.

[0100] In order to better achieve the effect of covering the entire link, two automated implementation plans are provided at the same time. For the remote control test on the test bench, the data link is closed by sending CAN / LIN signals to the VIU through the simulated controller. The premise of this solution is that the controller and VIU communicate through bus signals and can be simulated through bus signal equipment. This type of remote control function is automatically tested through a simple ring network test bench, and the test cost is significantly reduced; for the remote control test of the actual vehicle, there is no need to simulate the data link closed loop with the actual lower hanging parts. In this solution, only two USB cables are required to connect the actual vehicle and the mobile phone respectively. The deployment is much simpler than the ring network test bench, and the test scenarios are richer than the test bench, but the test resources are required to be higher. Through the mutual complementation of the two sets of automated implementation plans, the test scenarios in remote vehicle control can be fully covered. Both solutions trigger remote control through APP, check cloud logs to confirm the data flow of the link from mobile APP->cloud->vehicle, and then check data acquisition logs to confirm the data flow of the link from vehicle->cloud->mobile APP. Pull Tbox device logs to check the internal data flow of tbox, and finally check APPUI changes to complete the complete test link closed loop. The content of each data flow node in the link is recorded and generated into a visual test report, which can quickly locate the problem point.

[0101] In the above two test solutions, both are based on the host computer device, which provides a set of Python-based automated test frameworks, which are applicable to both real vehicle and bench test solutions. In this set of automated test frameworks, the following capabilities are provided:

[0102] Function point 1, the ability to send and receive CAN / LIN signals from multiple manufacturers and types of bus analysis devices (such as Zhou Ligong USBCANFD, Zhou Ligong CANFDNET, Hirain V60 series and Vector devices), which is used to receive bus signals and send specified signals to achieve the purpose of simulating controllers;

[0103] Function point 2: Provides the ability to simulate human operation of the mobile app UI and the car machine UI, and provides image recognition and text recognition capabilities to improve the accuracy and robustness of UI automation;

[0104] Function point 3: Provides DDS service simulation calling capability, which is used to simulate DDS service calling in the test bench environment;

[0105] Function point 4: Provide the vehicle computer public interface calling capability, which is used to obtain vehicle computer specific information query or set vehicle computer specific information; voice interface capability is used to simulate human-computer voice interaction scenarios;

[0106] Function point 5: Provide the ability to analyze the logs of the tested device: analyze the logs of the APP end, analyze the logs of the cloud end, analyze the EDC (Electronic Data Capture) logs of the vehicle end, analyze the TBOX logs, and analyze the VIU message parsing capabilities;

[0107] Function point 6 provides common testing framework capabilities, including test case management, execution, and visual report display capabilities.

[0108] Based on the functions provided by the test framework, the test engineering script can be directly written using the test framework. In the test process of the bench, since there is no actual hanging part in this scene, it is mainly through simulating UI clicks, simulating controller bus signals, and randomly and step by step detecting link data flow. Through this test framework, you can directly call function point 2 to simulate human operation, then call function point 1 to send and receive bus signals, and finally call function point 5 to perform data link analysis to complete the development of the test engineering script; in the stateless test process of the actual vehicle, since this type of function has no UI changes, it is mainly through simulating UI clicks, randomly and step by step detecting link data flow. Through this test framework, you can directly call function point 2 to simulate human operation, and then call function point 5 to perform data link analysis to complete the development of the test engineering script; in the stateful test process of the actual vehicle, it is mainly through control properties, text recognition detection or image comparison recognition to detect UI changes for judgment. Through this test framework, you can simulate human operation by calling function point 2, then call function point 2 for image or text recognition, and synchronously call function point 5 for data link analysis to complete the development of the test engineering script. Function point 3 is mainly used to simulate DDS services in the bench test process, and is mainly used in some pre-test script work, such as some functions that require early shifting or power-on. Function point 6 is the basic function of all test frameworks. In the framework, allure is integrated to perform step verification on each node in the link, so when the script is executed, the result can be located very quickly. Other basic functions are here, and I will not introduce them in detail.

[0109] Function point 2, in order to improve the accuracy of this function point. When developing and designing the text recognition function point, we compared multiple open source OCR projects, Easyocr, Tesseract and PaddleOCR. Easyocr is relatively easy to install and call, but its accuracy in detecting Chinese is average, its speed is slow, and Easyocr occupies a large amount of memory; Tesseract has good scalability and is relatively easy to use, but its recognition accuracy is relatively low; PaddleOCR can meet the scene application of personalized training, with high recognition accuracy and fast speed, but the learning cost is high. Since PaddleOCR can train a text recognition model that is more suitable for the project by adding a data set, and further improve the text recognition accuracy, PaddleOCR was finally selected. The test framework developer completes the operation of making a data set training model and directly provides the model in the test framework. The test framework users can reduce the learning cost and call it directly; the cosine similarity comparison algorithm is used in image recognition, which is a common method used in automated testing and has high accuracy.

[0110] Function point 4 is common to both test scenarios. Function point 4 is mainly used to detect some test states. For example, in the scenario of turning on the air conditioner for testing, the air conditioner needs to be turned off first. You can query the air conditioner on / off state or directly set the air conditioner on / off state by calling function point 4. When developing and designing this function point, we referred to the principle of u2, asked the developer to provide the corresponding SDK, developed the test framework apk and pushed it into the car computer, and ran an http service to open the car computer's public interface to the test framework user for calling. In some scenarios where you don't need to pay attention to changes in the car computer UI, you can quickly obtain vehicle-specific information through the interface; or in some test scenarios, complete the test pre-conditioning to make the vehicle reach the specified state.

[0111] Through the description of the above implementation methods, those skilled in the art can clearly understand that the method according to the above embodiment can be implemented by means of software plus a necessary general hardware platform, and of course can also be implemented by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present invention, or the part that contributes to the prior art, can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, a magnetic disk, or an optical disk), and includes a number of instructions for a terminal device (which can be a mobile phone, a computer, a server, or a network device, etc.) to execute the methods described in each embodiment of the present invention.

[0112] Example 2

[0113] In this embodiment, a test device for a vehicle control link is also provided, which is used to implement the above-mentioned embodiments and preferred implementation modes, and the descriptions that have been made will not be repeated. As used below, the term "module" can be a combination of software and / or hardware that implements a predetermined function. Although the devices described in the following embodiments are preferably implemented in software, the implementation of hardware, or a combination of software and hardware, is also possible and conceivable.

[0114] Fig.11 is a structural block diagram of a vehicle control link test device according to an embodiment of the present invention, such as Fig.11 As shown, the device comprises:

[0115] The control module 110 is used to control the application on the mobile terminal to send a remote test signal to the vehicle control link, wherein the vehicle control link includes the mobile terminal, the cloud, and the vehicle end of the simulation test bench in a closed loop connection;

[0116] A monitoring module 112 is used to monitor the signal transmission status of the electronic control unit VI U device on the vehicle side;

[0117] A query module 114, configured to query log data based on the signal sending status;

[0118] The positioning module 116 is used to locate abnormal nodes on the vehicle control link according to the query result of the log data.

[0119] Fig.12 is a structural block diagram of a vehicle control link test device according to an embodiment of the present invention, such as Fig.12 As shown, the device comprises:

[0120] The control module 120 is used to control the application on the mobile terminal to send a remote test signal to the vehicle control link, wherein the vehicle control link includes the mobile terminal, the cloud, and the physical vehicle end in a closed loop connection;

[0121] A determination module 122, configured to determine a test type of the remote test signal, wherein the test type includes a stateful test in which the remote test signal causes a graphical interface change of the application program and a stateless test in which the remote test signal does not cause a graphical interface change of the application program;

[0122] A query module 124, configured to query log data based on the test type;

[0123] The positioning module 126 is used to locate abnormal nodes on the vehicle control link according to the query result of the log data.

[0124] It should be noted that the above modules can be implemented by software or hardware. For the latter, it can be implemented in the following ways, but not limited to: the above modules are all located in the same processor; or the above modules are located in different processors in any combination.

[0125] Example 3

[0126] An embodiment of the present invention further provides a storage medium, in which a computer program is stored, wherein the computer program is configured to execute the steps of any of the above method embodiments when running.

[0127] Optionally, in this embodiment, the storage medium may be configured to store a computer program for performing the following steps:

[0128] S1, controlling the application on the mobile terminal to send a remote test signal to the vehicle control link, wherein the vehicle control link includes the mobile terminal, the cloud, and the vehicle end of the simulation test bench in a closed loop connection;

[0129] S2, monitoring the signal sending status of the electronic control unit VIU device on the vehicle end;

[0130] S3, querying log data based on the signal sending status;

[0131] S4: locate abnormal nodes on the vehicle control link according to the query result of the log data.

[0132] Optionally, in this embodiment, the above-mentioned storage medium may include but is not limited to: a USB flash drive, a read-only memory (ROM), a random access memory (RAM), a mobile hard disk, a magnetic disk or an optical disk, and other media that can store computer programs.

[0133] An embodiment of the present invention further provides an electronic device, including a memory and a processor, wherein a computer program is stored in the memory, and the processor is configured to run the computer program to execute the steps in any one of the above method embodiments.

[0134] Optionally, the electronic device may further include a transmission device and an input / output device, wherein the transmission device is connected to the processor, and the input / output device is connected to the processor.

[0135] Optionally, in this embodiment, the processor may be configured to perform the following steps through a computer program:

[0136] S1, controlling the application on the mobile terminal to send a remote test signal to the vehicle control link, wherein the vehicle control link includes the mobile terminal, the cloud, and the vehicle end of the simulation test bench in a closed loop connection;

[0137] S2, monitoring the signal sending status of the electronic control unit VIU device on the vehicle end;

[0138] S3, querying log data based on the signal sending status;

[0139] S4: locate abnormal nodes on the vehicle control link according to the query result of the log data.

[0140] Optionally, the specific examples in this embodiment may refer to the examples described in the above embodiments and optional implementation modes, and this embodiment will not be described in detail here.

[0141] The device embodiments described above are merely illustrative, wherein the units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0142] Through the description of the above implementation methods, those skilled in the art can clearly understand that each implementation method can be implemented by means of software plus a general hardware platform, and of course, by hardware. Based on this understanding, the above technical solution is essentially or the part that contributes to the relevant technology can be embodied in the form of a software product, and the computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, a disk, an optical disk, etc., including a number of instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to execute the methods described in each embodiment or some parts of the embodiments.

[0143] It should be understood that the terms used herein are only for the purpose of describing specific example embodiments and are not intended to be limiting. Unless the context clearly indicates otherwise, the singular forms "one", "an" and "said" as used herein may also be meant to include plural forms. The terms "include", "comprise", "contain", and "have" are inclusive, and therefore specify the existence of stated features, steps, operations, elements and / or parts, but do not exclude the existence or addition of one or more other features, steps, operations, elements, parts, and / or combinations thereof. The method steps, processes, and operations described herein are not interpreted as necessarily requiring them to be performed in the specific order described or illustrated, unless the execution order is clearly indicated. It should also be understood that additional or alternative steps may be used.

[0144] The foregoing is merely a specific embodiment of the present invention, which enables those skilled in the art to understand or implement the present invention. Various modifications to these embodiments will be apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present invention. Therefore, the present invention will not be limited to the embodiments shown herein, but rather to the widest scope consistent with the principles and novel features claimed herein.

Claims

1. A method for testing a vehicle control link, characterized in that: include: Controlling the application on the mobile terminal to send a remote test signal to the vehicle control link, wherein the vehicle control link includes the mobile terminal, the cloud, and the vehicle end of the simulation test bench in a closed loop connection; Monitor the signal sending status of the electronic control unit VIU device on the vehicle end; querying log data based on the signal sending status; The abnormal node on the vehicle control link is located according to the query result of the log data.

2. The method according to claim 1, characterized in that: Monitoring the signal transmission status of the VIU device on the vehicle side includes: Monitoring a designated bus signal output by the VIU device on the vehicle side through a bus analysis device, wherein the designated bus signal corresponds to the remote test signal; If the designated bus signal is monitored, it is determined that the signal sending state of the VIU device is that the designated bus signal has been sent; if the designated bus signal is not monitored, it is determined that the signal sending state of the VIU device is that the designated bus signal has not been sent.

3. The method according to claim 1, characterized in that Querying log data based on the signal sending status includes: If the signal sending status is that the designated bus signal is not sent, query the historical request data port of the cloud; Obtaining the historical request record of the historical request data port; Determining whether there is a designated request record of the mobile terminal in the historical request record; If the designated request record of the mobile terminal does not exist in the historical request record, query the terminal log data on the mobile terminal.

4. The method according to claim 3, characterized in that After determining whether there is a designated request record of the mobile terminal in the historical request record, the method further includes: If the designated request record of the mobile terminal exists in the historical request record, requesting the remote control log query interface of the cloud; The remote control log query interface is used to query the first remote control log and the second remote control log of the cloud, wherein the first remote control log is a remote control log recording the cloud being requested by the application, and the second remote control log is a remote control log recording the cloud requesting the vehicle end.

5. The method according to claim 4, characterized in that After using the remote control log query interface to query the first remote control log and the second remote control log on the cloud, the method further includes: If the first remote control log and the second remote control log in the cloud are found, the TBOX log is queried from the Internet of Vehicles TBOX on the vehicle side.

6. The method according to claim 1, characterized in that Querying log data based on the signal sending status includes: If the signal sending status is that the designated bus signal has been sent, determining whether the graphical interface of the application program has changed accordingly; If the graphical interface of the application program does not change accordingly, requesting the data collection log interface of the cloud; The data acquisition log interface is used to query the first data acquisition log and the second data acquisition log, wherein the first data acquisition log is a data acquisition log recording the data from the vehicle to the cloud, and the second data acquisition log is a data acquisition log recording the data from the cloud to the application.

7. The method according to any one of claims 1 to 6, characterized in that: Locating abnormal nodes on the vehicle control link according to the query result of the log data includes: If the query result is that the terminal log data is found, the terminal log data is parsed, and the abnormal node on the vehicle control link is located as the application; If the query result is that the first remote control log is not found, the abnormal node on the vehicle control link is located as a link between the application and the cloud; If the query result is that the first remote control log is found and the second remote control log is not found, the abnormal node on the vehicle control link is located as the link between the cloud and the vehicle end; If the query result is that a TBOX log is found, detecting whether the specified keyword exists in the TBOX log, and locating the abnormal node on the vehicle control link according to the detection result; If the query result is that the first data acquisition log is not found, the abnormal node on the vehicle control link is located as the link between the vehicle end and the cloud; If the query result is that the first data acquisition log is found and the second data acquisition log is not found, the abnormal node on the vehicle control link is located as a link between the cloud and the application.

8. The method according to claim 7, characterized in that Locating the abnormal node on the vehicle control link according to the detection result includes: If the detection result is that the specified keyword is not detected, the abnormal node on the vehicle control link is located as the TBOX on the vehicle end; If the detection result is that the specified keyword is detected, the abnormal node on the vehicle control link is located as the VIU device on the vehicle side.

9. A method for testing a vehicle control link, characterized in that: include: Controlling the application on the mobile terminal to send a remote test signal to the vehicle control link, wherein the vehicle control link includes the mobile terminal, the cloud, and the physical vehicle end in a closed loop connection; Determine a test type of the remote test signal, wherein the test type includes a stateful test in which the remote test signal causes a graphic interface change of the application program and a stateless test in which the remote test signal does not cause a graphic interface change of the application program; querying log data based on the test type; The abnormal node on the vehicle control link is located according to the query result of the log data.

10. The method according to claim 9, characterized in that Querying log data based on the test type includes: If the test type is a stateful test, determining whether the graphical interface of the application program changes; If the graphical interface of the application program changes, query the historical request data port of the cloud; Obtaining the historical request record of the historical request data port; Determining whether there is a designated request record of the mobile terminal in the historical request record; If the designated request record of the mobile terminal does not exist in the historical request record, query the terminal log data on the mobile terminal.

11. The method according to claim 10, characterized in that After determining whether there is a designated request record of the mobile terminal in the historical request record, the method further includes: If the designated request record of the mobile terminal exists in the historical request record, requesting the remote control log query interface of the cloud; The remote control log query interface is used to query the first remote control log and the second remote control log of the cloud, wherein the first remote control log is a remote control log recording the cloud being requested by the application, and the second remote control log is a remote control log recording the cloud requesting the vehicle end.

12. The method according to claim 11, characterized in that After using the remote control log query interface to query the first remote control log and the second remote control log on the cloud, the method further includes: If the first remote control log and the second remote control log in the cloud are found, query the TBOX log from the Internet of Vehicles TBOX on the vehicle side; Detect whether the TBOX log contains a specified keyword; If there is a specified keyword, the data acquisition log interface is used to query the first data acquisition log and the second data acquisition log, wherein the first data acquisition log is a data acquisition log recording the data from the vehicle to the cloud, and the second data acquisition log is a data acquisition log recording the data from the cloud to the application.

13. The method according to claim 9, characterized in that Querying log data based on the test type includes: If the test type is a stateless test, query the historical request data port of the cloud; Obtaining the historical request record of the historical request data port; Determining whether there is a designated request record of the mobile terminal in the historical request record; If the designated request record of the mobile terminal does not exist in the historical request record, query the terminal log data on the mobile terminal.

14. The method according to claim 13, characterized in that After determining whether there is a designated request record of the mobile terminal in the historical request record, the method further includes: If the designated request record of the mobile terminal exists in the historical request record, requesting the remote control log query interface of the cloud; The remote control log query interface is used to query the first remote control log and the second remote control log of the cloud, wherein the first remote control log is a remote control log recording the cloud being requested by the application, and the second remote control log is a remote control log recording the cloud requesting the vehicle end; If the first remote control log and the second remote control log in the cloud are found, the TBOX log is queried from the Internet of Vehicles TBOX on the vehicle side.

15. The method according to any one of claims 9 to 12, characterized in that: Locating abnormal nodes on the vehicle control link according to the query result of the log data includes: If the query result is that the terminal log data is found, the terminal log data is parsed, and the abnormal node on the vehicle control link is located as the application; If the query result is that the first remote control log is not found, the abnormal node on the vehicle control link is located as a link between the application and the cloud; If the query result is that the first remote control log is found and the second remote control log is not found, the abnormal node on the vehicle control link is located as the link between the cloud and the vehicle end; If the query result is that a TBOX log is found, detecting whether the specified keyword exists in the TBOX log, and if the specified keyword does not exist, locating the abnormal node on the vehicle control link as the TBOX; If the query result is that the first data acquisition log is not found, the abnormal node on the vehicle control link is located as the link between the vehicle end and the cloud; If the query result is that the first data acquisition log is found and the second data acquisition log is not found, the abnormal node on the vehicle control link is located as a link between the cloud and the application.

16. A vehicle control link test device, characterized in that: include: A control module, used to control the application on the mobile terminal to send a remote test signal to the vehicle control link, wherein the vehicle control link includes the mobile terminal, the cloud, and the vehicle end of the simulation test bench in a closed loop connection; A monitoring module, used to monitor the signal sending status of the electronic control unit VIU device on the vehicle end; A query module, used for querying log data based on the signal sending status; A positioning module is used to locate abnormal nodes on the vehicle control link according to the query result of the log data.

17. A vehicle control link test device, characterized in that: include: A control module, used to control the application on the mobile terminal to send a remote test signal to the vehicle control link, wherein the vehicle control link includes the mobile terminal, the cloud, and the physical vehicle end in a closed loop connection; A determination module, used to determine a test type of the remote test signal, wherein the test type includes a stateful test in which the remote test signal causes a graphic interface change of the application program and a stateless test in which the remote test signal does not cause a graphic interface change of the application program; A query module, used for querying log data based on the test type; A positioning module is used to locate abnormal nodes on the vehicle control link according to the query result of the log data.

18. A storage medium, characterized in that: The storage medium stores a computer program, wherein the computer program is configured to execute the method according to any one of claims 1 to 15 when executed.

19. An electronic device comprising a memory and a processor, characterized in that: A computer program is stored in the memory, and the processor is configured to run the computer program to perform the method according to any one of claims 1 to 15.

Images