Method and system for testing remote control of a vehicle

Abstract

This invention discloses a testing method and system for remote vehicle control. The method relates to the field of intelligent vehicles and includes: after a mobile terminal sends a remote vehicle control command to the vehicle, monitoring first data transmitted on the vehicle's bus, wherein the first data characterizes data corresponding to the remote vehicle control command; based on the first data, determining whether the vehicle successfully received the remote vehicle control command; and if the vehicle did not successfully receive the remote vehicle control command, generating a test result corresponding to the remote vehicle control command based on first log data. This invention solves the technical problem of low testing efficiency for remote vehicle control.

Description

Technical Field

[0001] This invention relates to the field of intelligent vehicles, and more specifically, to a test method for remote vehicle control. Background Technology

[0002] With the advancement of technology, mobile terminal vehicle control functions are becoming increasingly rich, enabling remote control of vehicle start, stop, lock doors, and turn on / off air conditioning. However, traditional remote vehicle control testing relies on a traversal method to determine the fault location when a fault occurs, which cannot quickly obtain remote vehicle control test results, resulting in low efficiency in remote vehicle control testing.

[0003] There is currently no effective solution to the above problems. Summary of the Invention

[0004] This invention provides a testing method and system for remote vehicle control, which at least solves the technical problem of low testing efficiency for remote vehicle control.

[0005] According to one aspect of the present invention, a test method for remote vehicle control is provided, comprising: after a mobile terminal sends a remote vehicle control command to a vehicle, monitoring first data transmitted on the vehicle's bus, wherein the first data is used to characterize data corresponding to the remote vehicle control command; determining, based on the first data, whether the vehicle has successfully received the remote vehicle control command; and, if the vehicle has not successfully received the remote vehicle control command, generating a test result corresponding to the remote vehicle control command based on first log data.

[0006] Optionally, based on the first data, determining whether the vehicle has successfully received the remote control command includes: determining whether the first data changes to a first target value within a preset time period; if the first data does not change to the first target value within the preset time period, determining that the vehicle has not successfully received the remote control command; if the first data changes to the first target value within the preset time period, determining that the vehicle has successfully received the remote control command.

[0007] Optionally, the test results include: fault type, fault cause, and remote vehicle control success rate. Based on the first log data, test results corresponding to the remote vehicle control command are generated, including: when the vehicle fails to receive the remote vehicle control command, obtaining log data from the mobile terminal, the vehicle, and the server to obtain the first log data, wherein the server is used to forward the remote vehicle control command from the mobile terminal to the vehicle; determining the fault type as the first type; determining the fault cause based on the first log data; and reducing the historical success rate of the remote vehicle control command to obtain the remote vehicle control success rate.

[0008] Optionally, if the vehicle successfully receives the remote control command, the method further includes: monitoring second data transmitted on the bus, wherein the second data is used to characterize the feedback data generated by the vehicle executing the remote control command; determining whether the vehicle successfully executes the remote control command based on the second data; and generating test results based on the second log data if the vehicle fails to execute the remote control command.

[0009] Optionally, based on the second data, determining whether the vehicle has successfully executed the remote vehicle control command includes: determining whether the second data has changed to the second target value within a preset time period; if the second data has not changed to the second target value within the preset time period, determining that the vehicle has not successfully executed the remote vehicle control command; if the second data has changed to the second target value within the preset time period, determining that the vehicle has successfully executed the remote vehicle control command.

[0010] Optionally, the test results include: fault type, fault cause, and success rate of remote vehicle control. Based on the second log data, the test results are generated, including: obtaining the log data generated by the vehicle in accordance with the remote vehicle control command when the vehicle fails to execute the remote vehicle control command, and obtaining the second log data; determining the fault type as the second type; determining the fault cause based on the second log data; and reducing the historical success rate of the remote vehicle control command to obtain the success rate of remote vehicle control.

[0011] Optionally, if the vehicle successfully executes the remote control command, the method further includes: monitoring third data of a preset interface connected to the mobile terminal, wherein the third data is used to characterize feedback data; determining whether the execution status of the remote control command is correct based on the third data; generating test results based on the third log data if the execution status is incorrect; and determining that the remote control command test is successful if the execution status is correct.

[0012] Optionally, determining whether the execution status of the remote vehicle control command is correct based on the third data includes: obtaining the preset execution data corresponding to the remote vehicle control command, wherein the preset execution data is generated by the vehicle successfully executing the remote vehicle control command; determining that the execution status is incorrect if the third data fails to match the preset execution data; and determining that the execution status is correct if the third data matches the preset execution data successfully.

[0013] Optionally, the test results include: fault type, fault cause, and success rate of remote vehicle control. Based on the third log data, the test results are generated, including: in the case of an execution state error, obtaining the log data generated by the vehicle in the process of sending feedback data to the mobile terminal to obtain the third log data; determining the fault type as the third type; determining the fault cause based on the third log data; and reducing the historical success rate of remote vehicle control commands to obtain the success rate of remote vehicle control.

[0014] According to another aspect of the present invention, a test apparatus for remote vehicle control is also provided, comprising: a monitoring module, configured to monitor first data transmitted on the vehicle's bus after a mobile terminal sends a remote vehicle control command to the vehicle, wherein the first data is used to characterize data corresponding to the remote vehicle control command; a determining module, configured to determine, based on the first data, whether the vehicle has successfully received the remote vehicle control command; and a generating module, configured to generate a test result corresponding to the remote vehicle control command based on first log data if the vehicle has not successfully received the remote vehicle control command.

[0015] According to another aspect of the present invention, a remote vehicle control testing system is also provided, comprising: a mobile terminal for sending remote vehicle control commands; a vehicle connected to the mobile terminal for executing the remote vehicle control commands; and an automated testing device connected to the vehicle's bus and the mobile terminal for monitoring first data transmitted on the vehicle's bus, determining, based on the first data, whether the vehicle has successfully received the remote vehicle control commands, and generating test results corresponding to the remote vehicle control commands based on first log data if the vehicle has not successfully received the remote vehicle control commands, wherein the first data is used to characterize data corresponding to the remote vehicle control commands.

[0016] According to another aspect of the present invention, a computer-readable storage medium is also provided, the computer-readable storage medium including a stored program, wherein, when the program is executed, it controls the device where the computer-readable storage medium is located to perform the remote vehicle control test method of the above embodiments.

[0017] According to another aspect of the present invention, an electronic device is also provided, including a memory and a processor. The memory stores a computer program, and the processor is configured to run the computer program to perform the remote vehicle control test method of the above embodiments.

[0018] In this embodiment of the invention, after the mobile terminal sends a remote vehicle control command to the vehicle, the first data on the vehicle bus is monitored; based on the first data, it is determined whether the vehicle has successfully received the remote vehicle control command; if the vehicle has not successfully received the remote vehicle control command, a test result corresponding to the remote vehicle control command is generated based on the first log data. It should be noted that monitoring the first data can promptly determine the type of remote vehicle control test fault, and further generating the corresponding test result based on the first log data can accurately determine the remote vehicle control fault and generate the corresponding test result, thereby improving the efficiency of remote vehicle control testing. This achieves the technical effect of quickly performing remote vehicle control testing and obtaining test results, thus solving the technical problem of low efficiency in remote vehicle control testing. Attached Figure Description

[0019] The accompanying drawings, which are included to provide a further understanding of the invention and form part of this application, illustrate exemplary embodiments of the invention and, together with their description, serve to explain the invention and do not constitute an undue limitation thereof. In the drawings:

[0020] Figure 1 This is a flowchart of a test method for remote vehicle control according to an embodiment of the present invention;

[0021] Figure 2 This is a schematic diagram of an optional automated testing device according to an embodiment of the present invention;

[0022] Figure 3 This is a flowchart of an optional remote vehicle control testing method according to an embodiment of the present invention;

[0023] Figure 4 This is a schematic diagram of a remote vehicle control testing device according to an embodiment of the present invention;

[0024] Figure 5 This is a schematic diagram of a remote vehicle control testing system according to an embodiment of the present invention. Detailed Implementation

[0025] To enable those skilled in the art to better understand the present invention, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings of the embodiments of the present invention. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of the present invention.

[0026] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this invention are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of the invention described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover a non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0027] Example 1

[0028] According to an embodiment of the present invention, an embodiment of a test method for remote vehicle control is provided. It should be noted that the steps shown in the flowchart in the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions. Furthermore, although a logical order is shown in the flowchart, in some cases, the steps shown or described may be executed in a different order than that shown here.

[0029] Figure 1 This is a flowchart of a remote vehicle control testing method according to an embodiment of the present invention, such as... Figure 1 As shown, the method includes the following steps:

[0030] Step S102: After the mobile terminal sends a remote vehicle control command to the vehicle, monitor the first data transmitted on the vehicle's bus, wherein the first data is used to represent the data corresponding to the remote vehicle control command.

[0031] The aforementioned mobile terminal can be a computer device used while in motion, for sending user-selected remote vehicle control commands to automated testing equipment and receiving feedback data corresponding to the remote vehicle control commands, including but not limited to: mobile phones. The remote vehicle control commands can be instructions for remotely controlling the vehicle. The automated testing equipment can be a device that automatically performs remote vehicle control tests, or a testing device capable of analyzing acquired data, directly connected to the vehicle, determining whether the vehicle is transmitting relevant command data based on the acquired data, and thus judging whether the vehicle has successfully received the data.

[0032] The aforementioned vehicles can be those capable of performing corresponding functions according to remote control commands, including but not limited to: autonomous vehicles, manually driven vehicles, and semi-autonomous vehicles. The bus can be a line for transmitting vehicle data.

[0033] The aforementioned first data can be data transmitted from the mobile terminal to the vehicle, or data transmitted from the mobile terminal to the vehicle during the process, including but not limited to: CAN (Controller Area Network) data from the mobile terminal transmitting remote vehicle control commands to the vehicle.

[0034] In one optional embodiment, after the mobile terminal sends a remote vehicle control command to the vehicle, the automated testing equipment monitors the CAN bus data of the entire vehicle and then obtains the first data corresponding to the process of the mobile terminal transmitting the remote vehicle control command to the vehicle.

[0035] In another alternative embodiment, after the mobile terminal transmits the data corresponding to the remote vehicle control command to the vehicle via the cloud, the automated test setup monitors the first data corresponding to the remote vehicle control command in real time, wherein the mobile terminal and the vehicle are connected via a wireless network.

[0036] Step S104: Based on the first data, determine whether the vehicle has successfully received the remote vehicle control command.

[0037] In one optional embodiment, the automated testing equipment monitors first data and whether the first data changes to a first target value within a preset time. If the first data changes to the first target value within the preset time, it is determined that the vehicle has received a remote vehicle control command. The automated testing equipment continues to monitor bus data and the execution and feedback of the remote vehicle control command. If the first data does not change to the first target value within the preset time, it is determined that the vehicle has not successfully received the remote vehicle control command, and then the corresponding test result is generated.

[0038] Step S106: If the vehicle fails to receive the remote control command, generate the test result corresponding to the remote control command based on the first log data.

[0039] The aforementioned first log data can be log data generated on the mobile terminal, the cloud, and the vehicle during the process of the mobile terminal sending remote vehicle control commands to the vehicle.

[0040] The test results described above can be the results of testing remote vehicle control, including but not limited to: fault type, fault cause, and remote vehicle control success rate. The fault type can be the type of problem that led to the failure of remote vehicle control, including but not limited to: the vehicle not receiving the remote control command sent by the mobile terminal, the vehicle failing to execute the remote control command, and the remote control command reporting an error in execution status. The fault cause can be the specific reason why remote vehicle control was unsuccessful. The remote vehicle control success rate can be the success rate of the remote vehicle control test.

[0041] In one optional embodiment, if the vehicle fails to receive the remote control command, the corresponding log data between the mobile terminal and the vehicle is obtained to determine the reason why the vehicle failed to receive the remote control command, and the test result corresponding to the remote control command is generated based on the log data.

[0042] In another optional implementation, if the vehicle fails to receive the remote control command, log data from the mobile terminal, the cloud, and the vehicle is obtained. The corresponding log data is obtained, and the fault type is determined to be a data transmission problem between the mobile terminal and the vehicle, which is a front-end problem. The fault location is determined, and based on the corresponding log data, the reason why the vehicle failed to receive the remote control command is determined. The historical success rate of the remote control command is reduced to determine the success rate of remote control. The test results of remote control are determined based on the fault type, fault cause, and remote control success rate, and then sent to the user, after-sales personnel, or maintenance personnel.

[0043] Through the above steps, after a remote vehicle control command is sent from the mobile terminal to the vehicle, the system monitors the first data on the vehicle's bus; based on this first data, it determines whether the vehicle successfully received the remote vehicle control command; if the vehicle did not successfully receive the remote vehicle control command, it generates the corresponding test result based on the first log data. It should be noted that monitoring the first data can promptly determine the type of remote vehicle control test fault, and further generating corresponding test results based on the first log data allows for accurate identification of remote vehicle control faults and the generation of corresponding test results, thereby improving the efficiency of remote vehicle control testing. This achieves the technical effect of quickly performing remote vehicle control tests and obtaining test results, thus solving the technical problem of low efficiency in remote vehicle control testing.

[0044] It should be noted that data is transmitted between the mobile terminal and the vehicle via the cloud. Automated testing equipment connects to both the vehicle and the mobile terminal via cables to monitor the data on the bus, thereby obtaining the corresponding test results. Specifically, in this embodiment of the invention, Figure 2 This is a schematic diagram of an optional automated testing device according to an embodiment of the present invention, such as... Figure 2 As shown, the automated testing equipment connects to the mobile terminal via a USB (Universal Serial Bus) cable. The automated testing equipment also connects to the CAN board via the USB cable. The CAN board connects to the OBD (On-Board Diagnostics) port on the vehicle gateway via an OBD (On-Board Diagnostics) cable, thereby monitoring the data on the bus. The automated testing equipment deploys ADB (Android Debug Bridge) debugging software, automated testing software, and a CAN driver. The ADB debugging software obtains the on / off status of the remote vehicle control software on the mobile terminal and receives remote vehicle control commands. The CAN driver enables the use of the automated testing equipment and manages the transmission and reception of CAN data. The automated testing software loads and parses CAN data, writes automated test sequences, calls the ADB and CAN driver software interfaces to execute automated test cases, and outputs a test report.

[0045] Optionally, based on the first data, determining whether the vehicle has successfully received the remote control command includes: determining whether the first data changes to a first target value within a preset time period; if the first data does not change to the first target value within the preset time period, determining that the vehicle has not successfully received the remote control command; if the first data changes to the first target value within the preset time period, determining that the vehicle has successfully received the remote control command.

[0046] The aforementioned preset time can be a time set in advance according to requirements, used to detect whether the remote vehicle control command has been successfully sent / received, or whether the remote vehicle control command has been successfully executed, including but not limited to: 1 minute, 3 minutes, and 5 minutes. The first target value is used to indicate the data corresponding to the successfully received remote vehicle control command.

[0047] In one optional embodiment, after the mobile terminal sends a remote vehicle control command, the automated testing equipment monitors the first data and determines whether the first data changes to a first target value within a preset time. If the first data changes to the first target value within the preset time, it is determined that the vehicle has successfully received the remote vehicle control command; if the first data does not change to the first target value within the preset time, it is determined that the vehicle has not successfully received the remote vehicle control command.

[0048] In another optional embodiment, the automated testing equipment monitors the first data and determines whether the first data changes to a first target value within a preset time. Since the preset time is set by the user, if the preset time is too short, the first data may not change to the first target value in a timely manner, meaning there may be a slow response. If the automated testing equipment detects that the first data has not changed to the first target value within the user-set preset time period, and the preset time is too short, the automated testing equipment waits for a further period and monitors whether the first data changes to the first target value. If the first data changes to the first target value, it is determined that the vehicle has successfully received the remote control command; if the first data still has not changed to the first target value, it is determined that the vehicle has not successfully received the remote control command.

[0049] In another optional embodiment, the automated testing equipment monitors the first data. If the vehicle has enabled the remote vehicle control test function but has not received a remote vehicle control command within a preset time period, it sends a signal indicating that no remote vehicle control command has been received to the automated testing equipment. The automated testing equipment automatically checks the first data to determine whether the first data has changed to a first target value within the preset time period. If the first data has changed to the first target value within the preset time period, it is determined that the vehicle has received the remote vehicle control command; if the first data has not changed to the first target value within the preset time period, it is determined that the vehicle has not successfully received the remote vehicle control command.

[0050] Optionally, the test results include: fault type, fault cause, and remote vehicle control success rate. Based on the first log data, test results corresponding to the remote vehicle control command are generated, including: when the vehicle fails to receive the remote vehicle control command, obtaining log data from the mobile terminal, the vehicle, and the server to obtain the first log data, wherein the server is used to forward the remote vehicle control command from the mobile terminal to the vehicle; determining the fault type as the first type; determining the fault cause based on the first log data; and reducing the historical success rate of the remote vehicle control command to obtain the remote vehicle control success rate.

[0051] The aforementioned server can be a computing device, a medium for data transmission between the mobile terminal and the vehicle, or a device for obtaining remote vehicle control test results based on the transmitted data.

[0052] The first type mentioned above can be a problem where the vehicle does not receive the remote control command sent by the mobile terminal, or a problem where the remote control command fails to be transmitted from the mobile terminal to the vehicle. It can be, but is not limited to, a front-end problem.

[0053] The aforementioned log data can be data that records the transmission and execution process of remote vehicle control commands, including but not limited to: the time of the CAN data transmission / execution process corresponding to the remote vehicle control command, and the specific location of the transmission / execution process of the remote vehicle control command.

[0054] In one optional embodiment, when the vehicle fails to receive the remote control command, the automated testing equipment acquires log data from the mobile terminal, the vehicle, and the server. Since the vehicle failed to receive the remote control command, it indicates a fault occurred during the transmission of the command from the mobile terminal to the vehicle, thus classifying the fault as type one. Based on the acquired log data, the specific fault location and cause are determined, and the historical success rate of the remote control command is reduced by a certain percentage to obtain the overall success rate of remote control.

[0055] Optionally, if the vehicle successfully receives the remote control command, the method further includes: monitoring second data on the bus, wherein the second data is used to characterize the feedback data generated by the vehicle executing the remote control command; determining whether the vehicle successfully executes the remote control command based on the second data; and generating test results based on the second log data if the vehicle fails to execute the remote control command.

[0056] The second data mentioned above can be data generated by the vehicle executing remote control commands, or CAN data generated during the process of the vehicle executing remote control commands. The second log data can be log data from the vehicle executing remote control commands.

[0057] In one optional embodiment, after the vehicle successfully receives the remote control command, the vehicle performs the corresponding function according to the remote control command and provides feedback data such as the execution status of the remote control command. The automated testing equipment further monitors the vehicle's execution status and obtains second data. Based on the second data, it is determined whether the vehicle successfully executed the remote control command. If the vehicle successfully executed the remote control command, the automated testing equipment continues to monitor the CAN data; if the vehicle failed to execute the remote control command, log data of the vehicle's execution process according to the remote control command is obtained, and corresponding test results are generated based on the log data.

[0058] Optionally, based on the second data, determining whether the vehicle has successfully executed the remote vehicle control command includes: determining whether the second data changes to the second target value within a preset time period; if the second data does not change to the second target value within the preset time period, determining that the vehicle has not successfully executed the remote vehicle control command; if the second data changes to the second target value within the preset time period, determining that the vehicle has successfully executed the remote vehicle control command.

[0059] In one optional embodiment, second data corresponding to the vehicle executing a remote vehicle control command is obtained, and it is determined whether the second data changes to a second target value within a preset time. If the second data changes to the second target value within the preset time, it is determined that the vehicle has successfully executed the remote vehicle control command; if the second data does not change to the second target value within the preset time, it is determined that the vehicle has not successfully executed the remote vehicle control command.

[0060] In another optional embodiment, second data corresponding to the vehicle's execution of the remote control command is acquired, and it is determined whether the second data changes to the second target value within a preset time. Since the preset time is set in advance by the user according to their needs, the preset time may be short, and the second data may not change to the second target value in time, meaning there may be a slow response. To avoid slow response, the automated testing equipment can wait for a period after the preset time has ended, monitoring whether the second data changes to the second target value. If the second data changes to the second target value, it is determined that the vehicle has successfully executed the remote control command; if the second data still has not changed to the second target value, it is determined that the vehicle has not successfully executed the remote control command.

[0061] Optionally, the test results include: fault type, fault cause, and success rate of remote vehicle control. Based on the second log data, the test results are generated, including: obtaining the log data generated by the vehicle in accordance with the remote vehicle control command when the vehicle fails to execute the remote vehicle control command, and obtaining the second log data; determining the fault type as the second type; determining the fault cause based on the second log data; and reducing the historical success rate of the remote vehicle control command to obtain the success rate of remote vehicle control.

[0062] The second type mentioned above can be a problem type where the vehicle fails to execute remote control commands, including but not limited to: backend issues.

[0063] In one optional embodiment, when the vehicle fails to execute the remote control command, log data of the vehicle's execution process according to the remote control command is acquired. At this point, the vehicle has received the remote control command but failed to execute it, indicating a fault type of "unable to execute remote control command," i.e., fault type two. Further, second log data of the vehicle's execution of the remote control command is acquired. Based on the second log data, the specific location and cause of the fault are determined. Simultaneously, the historical success rate of the remote control command is reduced by a certain percentage to obtain the success rate of remote control.

[0064] Optionally, if the vehicle successfully executes the remote control command, the method further includes: monitoring third data of a preset interface connected to the mobile terminal, wherein the third data is used to characterize feedback data; determining whether the execution status of the remote control command is correct based on the third data; generating test results based on the third log data if the execution status is incorrect; and determining that the remote control command test is successful if the execution status is correct.

[0065] The aforementioned preset interface can be a pre-configured interface used to feed back third data to the mobile terminal. This third data can be data fed back from the vehicle, including but not limited to CAN data corresponding to remote vehicle control commands at the mobile terminal interface.

[0066] The aforementioned execution status can be the status after the vehicle executes the remote control command, including but not limited to: execution successful or execution failed.

[0067] In one optional embodiment, when the vehicle successfully executes the remote control command, the vehicle sends feedback data to the mobile terminal in real time. The mobile terminal obtains the feedback data corresponding to the remote control command and determines the test result of the remote control command. Automated testing equipment monitors the feedback data sent from the vehicle to the mobile device to determine whether the execution status of the remote control command is correct. If the execution status is incorrect, third log data is obtained, and a corresponding test result is generated based on the third log data.

[0068] In another optional embodiment, when the vehicle successfully executes the remote control command, the automated testing equipment monitors the feedback data from the vehicle to the mobile device to determine whether the execution status displayed on the mobile terminal is consistent with the execution status reported by the vehicle. If the execution status sent by the vehicle is inconsistent with the execution status displayed on the mobile terminal, it indicates an execution status error, and third log data is obtained to generate a corresponding test result based on the log data; if the execution status sent by the vehicle is consistent with the execution status displayed on the mobile terminal, it indicates a correct execution status, and a corresponding test result is generated, for example, the remote control test is successful and there is no fault.

[0069] Optionally, determining whether the execution status of the remote vehicle control command is correct based on the third data includes: obtaining the preset execution data corresponding to the remote vehicle control command, wherein the preset execution data is generated by the vehicle successfully executing the remote vehicle control command; determining that the execution status is incorrect if the third data fails to match the preset execution data; and determining that the execution status is correct if the third data matches the preset execution data successfully.

[0070] The aforementioned preset execution data can be the data generated after the vehicle successfully executes the remote vehicle control command, or it can be images or text captured in advance according to the remote vehicle control command, including but not limited to: images or text of remote vehicle control execution sent by the mobile terminal captured in advance by the ADB debugging software, and images of remote vehicle control feedback results.

[0071] In one optional embodiment, third data and preset instruction data corresponding to the remote vehicle control command are obtained through a preset interface. The third data is compared with the preset instruction data to determine whether the third data is consistent with the preset execution data. If the third data is inconsistent with the preset execution data, the execution status is determined to be incorrect; if the third data is consistent with the preset execution data, the execution status is determined to be correct.

[0072] In another optional embodiment, the automated testing equipment calls the ADB debugging software interface, obtains third data through the interface, and obtains the execution data of the remote vehicle control command that has been successfully executed in the resource library. The third data is matched with the execution data. If the third data fails to match the preset execution data, the execution status is determined to be incorrect; if the third data matches the preset execution data successfully, the execution status is determined to be correct.

[0073] In another optional embodiment, the on / off status of the remote vehicle control software on the mobile device is obtained. Simultaneously, the automated testing equipment calls the ADB debugging software interface to obtain third-party data and pre-determined execution data of successfully executed remote vehicle control commands from the resource library. First, it is determined whether the remote vehicle control software on the mobile terminal is running. If the remote vehicle control software is off, it indicates that the execution status of the remote vehicle control commands is incorrect due to the software not being running, and the remote vehicle control software needs to be restarted and the test repeated. If the remote vehicle control software is running, the third-party data is further matched with the execution data. If the third-party data fails to match the preset execution data, the execution status is determined to be incorrect; if the third-party data matches the preset execution data successfully, the execution status is determined to be correct.

[0074] Optionally, the test results include: fault type, fault cause, and success rate of remote vehicle control. Based on the third log data, the test results are generated, including: in the case of an execution state error, obtaining the log data generated by the vehicle in the process of sending feedback data to the mobile terminal to obtain the third log data; determining the fault type as the third type; determining the fault cause based on the third log data; and reducing the historical success rate of remote vehicle control commands to obtain the success rate of remote vehicle control.

[0075] The aforementioned third log data may be log data generated during the process of the vehicle sending remote control commands to the mobile terminal.

[0076] The aforementioned feedback data can be data fed back from the vehicle to the mobile terminal, including but not limited to: data fed back by the vehicle after completing the remote vehicle control command, and test results generated by the server based on third-party data analysis.

[0077] The third type mentioned above can be a problem type where the execution status feedback of the remote vehicle control command is incorrect, including but not limited to: the mobile terminal failed to receive the execution status feedback from the vehicle, or the mobile terminal did not receive the correct execution status corresponding to the remote vehicle control command.

[0078] In one optional embodiment, in the event of an execution status error, log data of the vehicle-to-mobile terminal transmission line is acquired. At this time, the mobile terminal has not received the correct execution status, indicating a problem has occurred during the vehicle-to-mobile terminal transmission process; that is, the fault type is type three. Further acquisition of third log data of the vehicle-to-mobile terminal transmission line is then performed. Based on the third log data, the specific location and cause of the fault are determined. Simultaneously, the historical success rate of remote vehicle control commands is reduced by a certain percentage to obtain the success rate of remote vehicle control.

[0079] Figure 3 This is a flowchart of an optional remote vehicle control test method according to an embodiment of the present invention. The following is based on... Figure 3 An optional test method of the present invention will be described in detail, such as... Figure 3As shown, the automated testing equipment acquires remote vehicle control commands sent by the mobile terminal through debugging software and monitors the first data on the bus. It determines whether the vehicle has received the remote control command based on the first data. If the first data does not change to the first target value within a preset time period, the fault type is determined to be Type 1, a log is recorded, and the cause of the fault and the remote vehicle control success rate are determined. If the first data changes to the first target value within the preset time period, it monitors the second data corresponding to the remote vehicle control command on the bus. It determines whether the vehicle has executed the remote control command according to the second data. If the second data does not change to the second target value within the preset time period, the fault type is determined to be Type 2, a log is recorded, and the cause of the fault and the remote vehicle control success rate are determined. If the second data changes to the second target value within the preset time period, it monitors the third data on the bus. It determines whether the execution status of the remote vehicle control command is correct based on the third data. If the third data does not match the preset execution data, the fault type is determined to be Type 3, a log is recorded, and the cause of the fault and the remote vehicle control success rate are determined; if the third data matches the preset execution data, a log is recorded, and the corresponding test results are fed back.

[0080] Example 2

[0081] According to another aspect of the present invention, a test device for remote vehicle control is also provided. This device can perform the test method for remote vehicle control described in the above embodiments. The specific implementation method and preferred application scenarios are the same as those described in the above embodiments, and will not be repeated here.

[0082] Figure 4 This is a schematic diagram of a remote vehicle control testing device according to an embodiment of the present invention, as shown below. Figure 4 As shown, the device includes the following components: a first monitoring module 40, a first determining module 42, and a first generating module 44.

[0083] The first monitoring module 40 is used to monitor the first data transmitted on the vehicle's bus after the mobile terminal sends a remote vehicle control command to the vehicle. The first data is used to represent the data corresponding to the remote vehicle control command.

[0084] The first determining module 42 is used to determine, based on the first data, whether the vehicle has successfully received the remote vehicle control command;

[0085] The first generation module 44 is used to generate test results corresponding to the remote vehicle control command based on the first log data when the vehicle fails to successfully receive the remote vehicle control command.

[0086] Optionally, the first determining module includes: a first determining unit, used to determine whether the first data changes to the first target value within a preset time period; a second determining unit, used to determine that the vehicle has not successfully received the remote vehicle control command if the first data does not change to the first target value within the preset time period; and a third determining unit, used to determine that the vehicle has successfully received the remote vehicle control command if the first data changes to the first target value within the preset time period.

[0087] Optionally, the first generation module includes: a first acquisition unit, used to acquire log data from the mobile terminal, the vehicle, and the server to obtain first log data when the vehicle fails to receive the remote control command, wherein the server is used to forward the remote control command from the mobile terminal to the vehicle; and a fourth determination unit, used to determine the fault type as the first type.

[0088] Optionally, if the vehicle successfully receives the remote control command, the device further includes: a second monitoring module for monitoring second data transmitted on the bus, wherein the second data is used to characterize the feedback data generated by the vehicle executing the remote control command; a second determining module for determining whether the vehicle has successfully executed the remote control command based on the second data; and a second generating module for generating test results based on the second log data if the vehicle has not successfully executed the remote control command.

[0089] Optionally, the second determining module includes: a fifth determining unit, used to determine whether the second data changes to the second target value within a preset time period; a sixth determining unit, used to determine that the vehicle has not successfully executed the remote vehicle control command if the second data has not changed to the second target value within the preset time period; and a seventh determining unit, used to determine that the vehicle has successfully executed the remote vehicle control command if the second data changes to the second target value within the preset time period.

[0090] Optionally, the second generation module includes: a second acquisition unit, used to acquire log data generated by the vehicle in accordance with the remote control command when the vehicle fails to execute the remote control command, and obtain second log data; an eighth determination unit, used to determine the fault type as the second type; a ninth determination unit, used to determine the cause of the fault based on the second log data; and a first addition unit, used to reduce the historical success rate of the remote control command to obtain the success rate of the remote control.

[0091] Optionally, when the vehicle successfully executes the remote vehicle control command, the device further includes: a third monitoring module for monitoring third data of a preset interface connected to the mobile terminal, wherein the third data is used to characterize feedback data; a third determination module for determining whether the execution status of the remote vehicle control command is correct based on the third data; a third generation module for generating test results based on third log data when the execution status is incorrect; and a fourth determination module for determining that the remote vehicle control command test is successful when the execution status is correct.

[0092] Optionally, the third determining module includes: a third acquiring unit, used to acquire preset execution data corresponding to the remote vehicle control command, wherein the preset execution data is data generated by the vehicle successfully executing the remote vehicle control command; a tenth determining unit, used to determine an execution status error if the third data fails to match the preset execution data; and an eleventh determining unit, used to determine a correct execution status if the third data successfully matches the preset execution data.

[0093] Optionally, the third generation module includes: a fourth acquisition unit, used to acquire log data generated during the process of the vehicle feeding back feedback data to the mobile terminal in the event of an execution status error, to obtain third log data; a twelfth determination unit, used to determine the fault type as the third type; a thirteenth determination unit, used to determine the cause of the fault based on the third log data; and a second addition unit, used to reduce the historical success rate of remote vehicle control commands to obtain the success rate of remote vehicle control.

[0094] Example 3

[0095] According to another aspect of the present invention, a test system for remote vehicle control is also provided. This system can execute the test method for remote vehicle control described in the above embodiments. The specific implementation method and preferred application scenarios are the same as those described in the above embodiments, and will not be repeated here.

[0096] Figure 5 This is a schematic diagram of a remote vehicle control testing system according to an embodiment of the present invention. Figure 5 The system 50 may include: a mobile terminal 51, a vehicle 52, and an automated testing device 53.

[0097] Mobile terminal 51 is used to send remote vehicle control commands;

[0098] Vehicle 52 is connected to a mobile terminal for executing remote vehicle control commands;

[0099] An automated testing device 53 is connected to the vehicle's bus and mobile terminal to monitor the first data transmitted on the vehicle's bus. Based on the first data, it determines whether the vehicle has successfully received the remote control command. If the vehicle has not successfully received the remote control command, it generates the test result corresponding to the remote control command based on the first log data. The first data is used to characterize the data corresponding to the remote control command.

[0100] Example 4

[0101] According to another aspect of the present invention, a computer-readable storage medium is also provided, the computer-readable storage medium including a stored program, wherein, when the program is executed, it controls the device where the computer-readable storage medium is located to perform the remote vehicle control test method of the above embodiments.

[0102] Example 5

[0103] According to another aspect of the present invention, an electronic device is also provided, including a memory and a processor. The memory stores a computer program, and the processor is configured to run the computer program to perform the remote vehicle control test method of the above embodiments.

[0104] The sequence numbers of the above embodiments of the present invention are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0105] In the above embodiments of the present invention, the descriptions of each embodiment have different focuses. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions of other embodiments.

[0106] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. The device embodiments described above are merely illustrative; for example, the division of units can be a logical functional division, and in actual implementation, there may be other division methods. For instance, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the displayed or discussed mutual coupling, direct coupling, or communication connection may be through some interfaces; the indirect coupling or communication connection between units or modules may be electrical or other forms.

[0107] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0108] Furthermore, the functional units in the various embodiments of the present invention can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0109] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, read-only memory (ROM), random access memory (RAM), portable hard drives, magnetic disks, or optical disks.

[0110] The above description is only a preferred embodiment of the present invention. It should be noted that for those skilled in the art, several improvements and modifications can be made without departing from the principle of the present invention, and these improvements and modifications should also be considered within the scope of protection of the present invention.

Claims

1. A method of testing a remote control vehicle, the method comprising: include: After the mobile terminal sends a remote vehicle control command to the vehicle, the system monitors the first data transmitted on the vehicle's bus. The first data is used to characterize the data corresponding to the remote vehicle control command. The first data is the CAN data transmitted by the mobile terminal to the vehicle. Based on the first data, determine whether the vehicle has successfully received the remote vehicle control command; If the vehicle fails to receive the remote vehicle control command, a test result corresponding to the remote vehicle control command is generated based on the first log data. The first log data represents the log data generated on the mobile terminal, the cloud, and the vehicle during the process of the mobile terminal sending the remote vehicle control command to the vehicle. The test result includes the fault type, the fault cause, and the success rate of remote vehicle control. If the vehicle successfully receives the remote control command, the method further includes: monitoring second data transmitted on the bus using automated testing equipment, wherein the second data is used to characterize feedback data generated by the vehicle executing the remote control command; determining whether the vehicle successfully executes the remote control command based on the second data; generating the test result based on second log data if the vehicle fails to execute the remote control command, wherein the second log data represents log data of the vehicle executing the remote control command; and continuing to monitor the second data transmitted on the bus using the automated testing equipment if the vehicle successfully executes the remote control command. Based on the first data, determining whether the vehicle has successfully received the remote vehicle control command includes: in response to the vehicle activating the remote vehicle control test function and the vehicle not receiving the remote vehicle control command within a preset time period, acquiring the first data through the automated testing equipment; determining whether the first data changes to a first target value within the preset time period; if the first data does not change to the first target value within the preset time period, determining that the vehicle has not successfully received the remote vehicle control command; if the first data changes to the first target value within the preset time period, determining that the vehicle has successfully received the remote vehicle control command. Based on the first log data, the test results corresponding to the remote vehicle control command are generated, including: when the vehicle fails to receive the remote vehicle control command, acquiring log data from the mobile terminal, the vehicle, and the server to obtain the first log data, wherein the server is used to forward the remote vehicle control command from the mobile terminal to the vehicle, and the log data includes: the time of the transmission or execution process of the CAN data corresponding to the remote vehicle control command, and the location of the transmission or execution process of the remote vehicle control command; determining the fault type as a first type; based on the first log data, determining the cause and location of the fault; and reducing the historical success rate of the remote vehicle control command to obtain the success rate of the remote vehicle control.

2. The method of claim 1, wherein, Based on the second data, determining whether the vehicle successfully executed the remote vehicle control command includes: Determine whether the second data changes to the second target value within a preset time period; If the second data does not change to the second target value within the preset time period, it is determined that the vehicle has failed to execute the remote vehicle control command. If the second data changes to the second target value within the preset time period, it is determined that the vehicle has successfully executed the remote vehicle control command.

3. The method of claim 1, wherein, The test results include: fault type, fault cause, and success rate of remote vehicle control. These test results are generated based on the second log data and include: If the vehicle fails to execute the remote vehicle control command, the log data generated by the vehicle executing the remote vehicle control command is obtained to obtain the second log data; The fault type is determined to be the second type; Based on the second log data, the cause of the failure was determined; The success rate of remote vehicle control is obtained by reducing the historical success rate of the remote vehicle control command.

4. The method of claim 2, wherein, If the vehicle successfully executes the remote vehicle control command, the method further includes: The third data is monitored through a preset interface connected to the mobile terminal, wherein the third data is used to characterize the feedback data; Based on the third data, determine whether the execution status of the remote vehicle control command is correct; In the event of an execution status error, the test results are generated based on third-party log data. If the execution status is correct, the remote vehicle control command test is confirmed to be successful.

5. The method of claim 4, wherein, Based on the third data, determining whether the execution status of the remote vehicle control command is correct includes: Obtain preset execution data corresponding to the remote vehicle control command, wherein the preset execution data is generated by the vehicle successfully executing the remote vehicle control command; If the third data fails to match the preset execution data, the execution status is determined to be incorrect. If the third data successfully matches the preset execution data, the execution status is determined to be correct.

6. The method of claim 4, wherein, The test results include: fault type, fault cause, and success rate of remote vehicle control. These test results are generated based on third-party log data and include: In the event of an execution error, the log data generated by the vehicle during the process of sending the feedback data back to the mobile terminal is obtained to obtain the third log data; The fault type is determined to be the third type; Based on the third log data, the cause of the failure was determined; The success rate of remote vehicle control is obtained by reducing the historical success rate of the remote vehicle control command.

7. A test system for remote control of a vehicle, characterized in that include: The mobile terminal is used to send remote vehicle control commands; The vehicle is connected to the mobile terminal to execute the remote vehicle control command; An automated testing device, connected to the vehicle's bus and the mobile terminal, is used to monitor first data transmitted on the vehicle's bus. This first data characterizes data corresponding to the remote control command, and is the CAN data transmitted from the mobile terminal to the vehicle containing the remote control command. Based on the first data, it determines whether the vehicle successfully received the remote control command. If the vehicle fails to receive the remote control command, it generates a test result corresponding to the remote control command based on first log data. This first log data represents the data generated on the mobile terminal, the cloud, and the vehicle during the process of the mobile terminal sending the remote control command to the vehicle. The log data includes test results such as fault type, fault cause, and success rate of remote vehicle control; when the vehicle successfully receives the remote vehicle control command, it monitors second data transmitted on the bus, wherein the second data characterizes feedback data generated by the vehicle executing the remote vehicle control command; based on the second data, it determines whether the vehicle successfully executes the remote vehicle control command; when the vehicle fails to execute the remote vehicle control command, it generates the test result based on the second log data, wherein the second log data represents log data of the vehicle executing the remote vehicle control command; when the vehicle successfully executes the remote vehicle control command, it continues to monitor the second data transmitted on the bus. In response to the vehicle activating the remote vehicle control test function, and the vehicle not receiving the remote vehicle control command within a preset time period, the automated testing equipment is further configured to acquire the first data; determine whether the first data changes to a first target value within the preset time period; if the first data does not change to the first target value within the preset time period, determine that the vehicle has not successfully received the remote vehicle control command; if the first data changes to the first target value within the preset time period, determine that the vehicle has successfully received the remote vehicle control command. The automated testing equipment is further configured to, when the vehicle fails to receive the remote vehicle control command, acquire log data from the mobile terminal, the vehicle, and the server to obtain the first log data. The server is configured to forward the remote vehicle control command from the mobile terminal to the vehicle. The log data includes: the time of transmission or execution of the CAN data corresponding to the remote vehicle control command, and the location of the transmission or execution of the remote vehicle control command; determine the fault type as a first type; determine the cause and location of the fault based on the first log data; and reduce the historical success rate of the remote vehicle control command to obtain the success rate of the remote vehicle control.

Images