OTA upgrade test method and equipment
By controlling the vehicle's power-on status and simultaneously displaying the upgrade progress through mobile devices, automated OTA upgrade testing has been achieved, solving the problems of low efficiency and difficulty in ensuring accuracy in existing technologies, and improving testing efficiency and accuracy.
Patent Information
- Application Number
- CN202411072589.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-08-06
- Publication Date
- 2024-11-12
AI Technical Summary
In existing technologies, OTA upgrade testing is inefficient and its accuracy is difficult to guarantee, requiring a large number of repetitive manual operations.
The system sends upgrade test requests to cloud devices via a mobile device control client, automatically controls the vehicle's power-on status, and displays upgrade progress information simultaneously, thus achieving automated OTA upgrade testing.
It improves the efficiency of OTA upgrade testing, reduces manual operation, avoids human error, and improves the accuracy and automation of testing.
Smart Images

Figure CN118939295A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of testing technology, and in particular to an OTA upgrade testing method and device. Background Art
[0002] With the development of science and technology, the degree of intelligence of automobiles is getting higher and higher, and the update of vehicle systems is becoming more and more frequent. In order to improve the efficiency of updates, OTA (Over-the-Air Technology) came into being. OTA technology allows cars to update software through wireless networks without sending the vehicle to a repair shop for upgrades. In order to smoothly carry out OTA upgrades after the vehicle leaves the factory, it is necessary to test the OTA upgrade function of the vehicle to ensure that the OTA upgrade function is normal and stable. At present, manual methods are usually used for OTA upgrade testing. For example, the tester manually connects the vehicle to the cloud server and selects OTA upgrade on the in-vehicle screen to download the software package from the cloud server. The cloud server sends the software package to be tested, and then transfers the software package to the vehicle. The user selects upgrade on the in-vehicle screen to complete the upgrade test. However, the manual method for OTA upgrade testing is inefficient. During the test, a large number of manual repetitive operations are required, and the accuracy of the test is difficult to guarantee. Summary of the invention
[0003] The present application provides an OTA upgrade test method, apparatus, device and storage medium to solve the problem of low efficiency of OTA upgrade testing in manual mode.
[0004] In view of the above technical problems, the technical solution of this application is solved by the following embodiments:
[0005] An embodiment of the present application provides an OTA upgrade test method, which is applied to a mobile device, including: controlling a client to send an upgrade test request to a cloud device for a target vehicle, so that when the cloud device determines that the target vehicle has software to be upgraded based on the upgrade test request, the cloud device returns an upgrade message to the client and sends a software upgrade task to the target vehicle; after determining that the client has received the upgrade message returned by the cloud device, controlling the target vehicle to be in a target power-on state; after the target vehicle is in the target power-on state, controlling the target vehicle to execute the software upgrade task, and synchronizing and displaying the upgrade progress information of the target vehicle.
[0006] Wherein, controlling the target vehicle to be in a target power-on state includes: monitoring the vehicle state of the target vehicle; when the vehicle state is a power-off state, if the target vehicle is identified to be in a locked state by controlling the client and / or the target vehicle is determined to be in an offline state by the cloud device, then unlocking the target vehicle by controlling the client; after unlocking the target vehicle, controlling a relay connected to a door control motor in the target vehicle so that the door control motor drives the corresponding door to open, so that the target vehicle enters a power-on state.
[0007] Wherein, after controlling the target vehicle to be in the target power-on state through the client, it also includes: monitoring the vehicle state of the target vehicle; wherein, the target vehicle is a Zengcheng vehicle; when the vehicle state is in the power-on state, monitoring the battery power of the target vehicle; if the battery power is less than a preset battery power threshold, querying the upgrade task status corresponding to the target vehicle from the cloud device; wherein, the target vehicle starts from attempting to execute the software upgrade task, and reports the upgrade task status to the cloud device; if the upgrade task status is that the vehicle power battery is insufficient, controlling the target vehicle to enter the fuel replenishment state.
[0008] Wherein, the synchronization and display of the upgrade progress information of the target vehicle includes: monitoring the upgrade progress information of the target vehicle, and displaying the monitored upgrade progress information of the target vehicle; or monitoring the upgrade progress information of the target vehicle; obtaining the upgrade progress information of the target vehicle from the cloud device; wherein, during the process of the target vehicle executing the software upgrade task, the target vehicle reports the upgrade progress information to the cloud device; if the monitored upgrade progress information of the target vehicle is different from the obtained upgrade progress information of the target vehicle, the upgrade progress information corresponding to the shortest network delay is selected for display.
[0009] Wherein, after controlling the target vehicle to execute the software upgrade task, it includes: after monitoring that the target vehicle has completed the software upgrade task, querying the upgrade task status of the target vehicle from the cloud device; wherein, the target vehicle reports the upgrade task status to the cloud device during the process of executing the software upgrade task; if the upgrade task status is that the target vehicle is executing the software upgrade task, controlling the target vehicle to reconnect to the cloud device; if the upgrade task status is that the target vehicle has completed the software upgrade task, controlling the client to send the next upgrade test request to the cloud device for the target vehicle, so as to perform the next OTA upgrade test.
[0010] An embodiment of the present application also provides an OTA upgrade test method, which is applied to a client, comprising: under the control of the mobile device, sending an upgrade test request to a cloud device for a target vehicle, so that when the cloud device determines that there is software to be upgraded in the target vehicle according to the upgrade test request, it returns a message to be upgraded and sends a software upgrade task to the target vehicle; after receiving the message to be upgraded returned by the cloud device, under the control of the mobile device, controlling the target vehicle to be in an unlocked state, so that the mobile device controls the target vehicle to enter a target power-on state and executes the software upgrade task; during the process of the target vehicle executing the software upgrade task, synchronizing and displaying the upgrade progress information of the target vehicle from the cloud device.
[0011] Wherein, under the control of the mobile device, controlling the target vehicle to be in an unlocked state includes: under the control of the mobile device, triggering a simulated click of a lock button on the mobile device; after a preset lock status information pops up, sending a lock status message to the mobile device; under the control of the mobile device, triggering a simulated click of an unlock button on the mobile device, sending an unlock instruction to the target vehicle, so as to unlock the target vehicle.
[0012] Wherein, during the process of the target vehicle executing the software upgrade task, the upgrade progress information of the target vehicle is synchronously displayed, including: receiving and displaying the upgrade progress information of the target vehicle sent by the cloud device; wherein, during the process of the target vehicle executing the software upgrade task, the target vehicle reports the upgrade progress information to the cloud device.
[0013] An embodiment of the present application also provides an OTA upgrade test method, which is applied to a cloud device, and includes: receiving an upgrade test request; wherein the upgrade test request is issued by a client to a target vehicle under the control of a mobile device; sending a version detection request to the target vehicle and receiving vehicle software information returned by the target vehicle; when it is determined that the target vehicle has software to be upgraded based on the vehicle software information, returning the information to be upgraded to the client and sending a software upgrade task to the target vehicle; during the process of the target vehicle executing the software upgrade task, monitoring and synchronizing the upgrade progress information of the target vehicle to the mobile device.
[0014] An embodiment of the present application also provides an OTA upgrade test device, comprising: at least one communication interface; at least one bus connected to the at least one communication interface; at least one processor connected to the at least one bus; and at least one memory connected to the at least one bus, wherein the processor is configured to: execute an OTA upgrade test program stored in the memory to implement any of the above-mentioned OTA upgrade test methods executed on a mobile device, or to implement any of the above-mentioned OTA upgrade test methods executed on a client, or to implement the above-mentioned OTA upgrade test method executed on a cloud device.
[0015] The above technical solution provided by the embodiment of the present application has the following advantages over the prior art: the method provided by the embodiment of the present application can control the client to send an upgrade test request to the cloud device for the target vehicle, so that when the cloud device determines that the target vehicle has software to be upgraded according to the upgrade test request, it returns a message to be upgraded to the client and sends a software upgrade task to the target vehicle; after determining that the client receives the message to be upgraded returned by the cloud device, the target vehicle is controlled to be in the target power-on state; after the target vehicle is in the target power-on state, the target vehicle is controlled to perform the software upgrade task, and the upgrade progress information of the target vehicle is synchronized and displayed. Through the embodiment of the present application, a multi-terminal interactive control method is adopted to complete the automated OTA upgrade test process, without the need for manual operation during the OTA upgrade test process, which improves the test efficiency and avoids errors introduced by manual operation. BRIEF DESCRIPTION OF THE DRAWINGS
[0016] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.
[0017] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.
[0018] One or more embodiments are exemplarily described by pictures in the corresponding drawings, and these exemplified descriptions do not constitute limitations on the embodiments. Elements with the same reference numerals in the drawings represent similar elements, and unless otherwise stated, the figures in the drawings do not constitute proportional limitations.
[0019] Figure 1 is a flow chart of an OTA upgrade test method performed on a mobile device according to an embodiment of the present application;
[0020] Figure 2 is a flowchart of an OTA upgrade test method performed on a client according to an embodiment of the present application;
[0021] Figure 3 It is a flowchart of an OTA upgrade test method performed on a cloud device according to an embodiment of the present application;
[0022] Figure 4 is a structural diagram of an OTA upgrade test system according to an embodiment of the present application;
[0023] Figure 5 It is a structural diagram of an OTA upgrade test device set in a mobile device according to an embodiment of the present application;
[0024] Figure 6 It is a structural diagram of an OTA upgrade test device arranged on a client according to an embodiment of the present application;
[0025] Figure 7 This is a structural diagram of an OTA upgrade test device set in a cloud device according to an embodiment of the present application;
[0026] Figure 8 It is a structural diagram of an OTA upgrade test device according to an embodiment of the present application. DETAILED DESCRIPTION
[0027] In order to make the purpose, technical solution and advantages of the embodiments of the present application clearer, the technical solution 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 part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of this application.
[0028] The disclosure below provides many different embodiments or examples to realize the different structures of the present application. In order to simplify the disclosure of the present application, the parts and settings of specific examples are described below. Of course, they are only examples, and the purpose is not to limit the present application. In addition, the present application can repeat reference numbers and / or letters in different examples. This repetition is for the purpose of simplification and clarity, and does not itself indicate the relationship between the various embodiments and / or settings discussed.
[0029] The present application embodiment provides an OTA upgrade test method performed on a mobile device. Figure 1 , which is a flow chart of an OTA upgrade test method performed on a mobile device according to an embodiment of the present application.
[0030] In step S110, the mobile device controls the client to send an upgrade test request to the cloud device for the target vehicle, so that when the cloud device determines that the target vehicle has software to be upgraded according to the upgrade test request, it returns an upgrade message to the client and sends a software upgrade task to the target vehicle.
[0031] The upgrade test request is used to request the cloud device to start OTA software upgrade testing.
[0032] The mobile device can send a preset instruction to the client, and the client sends an upgrade test request to the cloud device for its corresponding target vehicle based on the instruction.
[0033] The mobile device is connected to the client, the cloud device and the target vehicle respectively; the cloud device is also connected to the client and the target vehicle respectively. The mobile device completes this embodiment based on the connection with the client, the cloud device and the target vehicle. There is an association relationship between the client and the target vehicle. The target device can be controlled by operating the client. In addition, the client can be installed in the mobile device, or it can be installed in other user terminals independent of the mobile device.
[0034] Step S120 , after determining that the client has received the to-be-upgraded message returned by the cloud device, the mobile device controls the target vehicle to be in a target power-on state.
[0035] The target power-on state means that the target vehicle is in a power-on state, or the target vehicle is in a power-on state and the battery power is greater than or equal to a preset battery power threshold.
[0036] The mobile device monitors the client and the target vehicle in real time respectively, and after determining through the monitoring that the client has received the message to be upgraded returned by the cloud device, controls the target vehicle to be in a target power-on state.
[0037] Specifically, the mobile device can monitor the vehicle status of the target vehicle; when the vehicle status is a power-off state, if the target vehicle is identified as being in a locked state by controlling the client and / or the target vehicle is determined to be in an offline state by the cloud device, the target vehicle is unlocked by controlling the client; after unlocking the target vehicle, the door control motor drives the corresponding door to open by controlling a relay connected to the door control motor in the target vehicle, so that the target vehicle enters a power-on state.
[0038] The vehicle status of the target vehicle includes: power-on status and power-off status. The mobile device can view the vehicle status of the target vehicle through the client, or query the vehicle status reported by the target vehicle from the cloud device.
[0039] Furthermore, when the target vehicle is in a powered-on state, a preset online message is reported to the cloud device every preset time period; the cloud device sets the state of the target vehicle to an online state according to the online message. If the cloud device fails to receive the online message or receives an offline message reported by the target vehicle, the state of the target vehicle is set to an offline state.
[0040] Furthermore, the client is controlled to perform simulation operations in a simulation operation manner, and whether the target vehicle is in a locked state is identified according to the response of the client. Wherein, under the control of the mobile device, the user interface of the client is opened; in the opened user interface, a button simulated by the mobile device is triggered to be clicked; if the button is a lock button, a message that the target vehicle is in a locked state is reported to the mobile device, and the mobile device is waited for to simulate clicking an unlock button; if the button is an unlock button, an unlock instruction is sent to the target vehicle.
[0041] In the embodiment of the present application, the types of target vehicles include but are not limited to: extended-range vehicles. After the mobile device controls the target vehicle to be in the target power-on state through the client, the mobile device monitors the vehicle state of the target vehicle; wherein, the target vehicle is a Zengcheng vehicle; when the vehicle state is in the power-on state, the battery power of the target vehicle is monitored; if the battery power is less than a preset battery power threshold, the upgrade task state corresponding to the target vehicle is queried from the cloud device; wherein, the target vehicle reports the upgrade task state to the cloud device starting from attempting to execute the software upgrade task; if the upgrade task state is that the vehicle power battery is insufficient, the target vehicle is controlled to enter the fuel replenishment state. Furthermore, after controlling the target vehicle to enter the fuel replenishment state, the mobile device can control the relay connected to the door control motor in the target vehicle so that the door control motor drives the corresponding door to close. After a preset time period, the mobile device controls the target vehicle to be in the target power-on state again through the client.
[0042] Furthermore, the upgrade task status is used to reflect the execution status of the software upgrade task. The types of upgrade task status include but are not limited to: executing the software upgrade task, completing the software upgrade task, and software upgrade task error. Software upgrade task errors include but are not limited to: insufficient vehicle power battery. Among them, insufficient vehicle power battery means that the battery power of the target vehicle is less than the preset battery power threshold.
[0043] Step S130, after the target vehicle is in the target power-on state, controlling the target vehicle to execute the software upgrade task and synchronizing and displaying the upgrade progress information of the target vehicle.
[0044] The upgrade progress information is used to reflect the upgrade progress. It allows users to intuitively see the completed and uncompleted proportions of the software upgrade tasks.
[0045] In an embodiment of the present application, in order to avoid manual operation during the OTA upgrade process, after the target vehicle is in the target power-on state, a simulation operation is used to control the target vehicle to perform the software upgrade task, and in the process of the target vehicle performing the software upgrade task, the upgrade progress information of the target vehicle is synchronized and displayed.
[0046] Furthermore, when controlling the target vehicle to perform a software upgrade task, the task operation steps corresponding to the software upgrade task are determined; wherein the task operation steps include: a plurality of operation objects having an execution order; obtaining interface elements in a preset screen of the target vehicle; and according to the plurality of operation objects having an execution order, in the screen of the target vehicle, sequentially simulating clicking on the interface elements corresponding to each of the operation objects. The preset screen may be an IVI (In-Vehicle Infotainment)
[0047] Furthermore, when the upgrade progress information of the target vehicle is synchronized and displayed, the upgrade progress information of the target vehicle can be monitored and the monitored upgrade progress information of the target vehicle can be displayed. When the upgrade progress information of the target vehicle is synchronized and displayed, the upgrade progress information of the target vehicle can also be monitored; the upgrade progress information of the target vehicle can be obtained from the cloud device; wherein, during the process of the target vehicle executing the software upgrade task, the target vehicle reports the upgrade progress information to the cloud device; if the upgrade progress information of the monitored target vehicle is different from the upgrade progress information of the acquired target vehicle, the upgrade progress information corresponding to the shortest network delay is selected for display; if the upgrade progress information of the monitored target vehicle is the same as the upgrade progress information of the acquired target vehicle, the upgrade progress information of the monitored target vehicle is directly displayed.
[0048] In an embodiment of the present application, the network delay between the target vehicle and the cloud device can be queried in the cloud device, and the network delay between the target vehicle and the mobile device can be measured in the mobile device. In order to shorten the time of the OTA upgrade test, a fixed network delay parameter can be set according to the connection method between the target vehicle and the cloud device and the mobile device. For example: if the target vehicle and the cloud device are connected wirelessly, a larger network delay parameter is set; if the target vehicle and the mobile device are connected by wire, a smaller network delay parameter is set. By default, it is considered that the network delay between the target vehicle and the mobile device is less than the network delay between the target vehicle and the cloud device. Due to network delay, the upgrade progress information monitored by the cloud device and the mobile device may be different, and the reference network delay can realize the correction of the upgrade progress information. Generally speaking, compared with the cloud device located at the remote end, the mobile device is wired to the target vehicle, and the communication conditions between the mobile device and the target vehicle are optimal, and the network delay is short, so the upgrade progress information of the monitored target vehicle can be directly displayed.
[0049] Furthermore, the upgrade progress information includes: download progress information and installation progress information of the software to be upgraded. When the target vehicle performs the software upgrade task, the download progress information of the software to be upgraded and the installation progress information of the software to be upgraded are monitored and displayed.
[0050] Furthermore, the upgrade progress information can be displayed in the form of a progress bar. When the target vehicle is downloading the software to be upgraded, the download progress bar of the software to be upgraded is synchronized and displayed; when the target vehicle is installing the software to be upgraded, the installation progress bar of the software to be upgraded is synchronized and displayed. The style of the upgrade progress bar is not limited, for example: rectangular bar progress bar, circular progress bar, dynamic progress bar, etc.
[0051] In an embodiment of the present application, multiple OTA upgrade tests can be performed on the target vehicle in order to perform stress testing on the target vehicle. To this end, after monitoring that the target vehicle has completed the software upgrade task, the upgrade task status of the target vehicle is queried from the cloud device; wherein, the target vehicle reports the upgrade task status to the cloud device during the execution of the software upgrade task; if the upgrade task status is that the target vehicle is executing the software upgrade task, the target vehicle is controlled to reconnect to the cloud device; if the upgrade task status is that the target vehicle has completed the software upgrade task, the client is controlled to send the next upgrade test request to the cloud device for the target vehicle in order to perform the next OTA upgrade test. Due to network reasons, the target vehicle may have been disconnected from the cloud device, resulting in the cloud device failing to receive the message reported by the target vehicle that the software upgrade task has been completed. At this time, the mobile device monitors that the target device has completed the software upgrade task, but it is queried from the cloud device that the target device is executing the software upgrade task. In this case, the next OTA upgrade test cannot be performed, so it is necessary to control the target vehicle to reconnect with the cloud device.
[0052] In an embodiment of the present application, the mobile device controls the client to send an upgrade test request to the cloud device for the target vehicle, so that when the cloud device determines that the target vehicle has software to be upgraded according to the upgrade test request, it returns a message to be upgraded to the client and sends a software upgrade task to the target vehicle; after determining that the client receives the message to be upgraded returned by the cloud device, the target vehicle is controlled to be in the target power-on state; after the target vehicle is in the target power-on state, the target vehicle is controlled to perform the software upgrade task, and the upgrade progress information of the target vehicle is synchronized and displayed. Through the embodiment of the present application, the automated OTA upgrade test process is completed by adopting a multi-terminal interactive control method, without the need for manual operation during the OTA upgrade test process, which improves the test efficiency and avoids errors introduced by manual operation.
[0053] Corresponding to the above-mentioned OTA upgrade test method performed on the mobile device, the embodiment of the present application also provides an OTA upgrade test method performed on the client. Figure 2 , which is a flowchart of an OTA upgrade test method performed on a client according to an embodiment of the present application.
[0054] In step S210, under the control of the mobile device, the client sends an upgrade test request to the cloud device for the target vehicle, so that when the cloud device determines that the target vehicle has software to be upgraded based on the upgrade test request, it returns an upgrade message and sends a software upgrade task to the target vehicle.
[0055] In step S220, after receiving the upgrade message returned by the cloud device, the client controls the target vehicle to be unlocked under the control of the mobile device, so that the mobile device controls the target vehicle to enter the target power-on state and executes the software upgrade task.
[0056] The mobile device can adopt a simulation operation mode, that is, the simulation operation is performed in the client, and the client performs the simulation operation to control the target vehicle to be in an unlocked state. Among them, the simulation operation can simulate clicking a function button displayed in the client to trigger the operation corresponding to the function button.
[0057] Specifically, under the control of the mobile device, the mobile device simulates clicking a lock button, and after a preset lock status information pops up, a lock status message is sent to the mobile device; under the control of the mobile device, the mobile device simulates clicking an unlock button, and sends an unlock instruction to the target vehicle to unlock the target vehicle. The lock status information may be a pop-up window of "the vehicle is in the current state".
[0058] Step S230 , when the target vehicle is executing the software upgrade task, the client synchronizes and displays the upgrade progress information of the target vehicle from the cloud device.
[0059] During the process of the target vehicle executing the software upgrade task, the cloud device monitors the upgrade progress information of the target vehicle and sends the monitored upgrade progress information of the target vehicle to the client. The client receives and displays the upgrade progress information of the target vehicle sent by the cloud device. Furthermore, during the process of the target vehicle executing the software upgrade task, the target vehicle reports the upgrade progress information to the cloud device so that the cloud device can monitor the upgrade progress information of the target vehicle.
[0060] Corresponding to the above-mentioned OTA upgrade test method performed on the mobile device and the client, the embodiment of the present application also provides an OTA upgrade test method performed on the cloud device. Figure 3 , which is a flow chart of an OTA upgrade test method performed on a cloud device according to an embodiment of the present application.
[0061] In step S310, the cloud device receives an upgrade test request, wherein the upgrade test request is issued by the client to the target vehicle under the control of the mobile device.
[0062] Step S320: the cloud device sends a version detection request to the target vehicle and receives vehicle software information returned by the target vehicle.
[0063] The version detection request is used to request the target vehicle to report vehicle software information so that the cloud device can determine whether the target vehicle has a software upgrade task based on the vehicle software information.
[0064] Step S330, when the cloud device determines that the target vehicle has software to be upgraded based on the vehicle software information, it returns the upgrade information to the client and sends a software upgrade task to the target vehicle.
[0065] The existence of software to be upgraded in the target vehicle indicates that there is a software upgrade task in the target vehicle.
[0066] Step S340 , the cloud device monitors and synchronizes the upgrade progress information of the target vehicle to the mobile device during the process of the target vehicle executing the software upgrade task.
[0067] During the process of the target vehicle executing the software upgrade task, the target vehicle reports the upgrade progress information to the cloud device; the cloud device sends the upgrade progress information to the target vehicle.
[0068] Furthermore, the software upgrade task includes: the software to be upgraded download phase and the software to be upgraded installation phase. In the software to be upgraded download phase, when the download starts, the cloud device can send the total data volume of the software to be upgraded to the target vehicle. During the download process, the software to be upgraded is sent to the target vehicle in the form of data packets; the target vehicle determines the amount of data that has been received based on the received data packets, generates upgrade progress information based on the total data volume of the software to be upgraded and the amount of data that has been received, and reports it to the cloud device. In the software to be upgraded installation phase, the target vehicle can estimate the installation time based on the total data volume of the software to be upgraded. During the installation process, the installed time is continuously updated, and the upgrade progress information is generated based on the installed time and reported to the cloud device.
[0069] In the embodiment of the present application, the cloud device, mobile device, client and target vehicle cooperate with each other to realize automated OTA upgrade test, which is convenient for users to use, improves test efficiency, shortens test time and improves test accuracy. In the embodiment of the present application, even if the user leaves the target vehicle, the upgrade progress information can be viewed through the client anytime and anywhere, avoiding the problem that after the software upgrade task is completed, if the user is not at the target vehicle, the software upgrade task cannot be known to have been completed, which leads to the problem that the stability of the OTA upgrade cannot be analyzed.
[0070] In order to make the embodiment of the present application easier to understand, a more specific example is given below to further describe the OTA upgrade test method of the embodiment of the present application.
[0071] In the embodiment of the present application, the OTA upgrade test method of the embodiment of the present application is described based on the OTA upgrade test system. Figure 4 , which is a structural diagram of an OTA upgrade test system according to an embodiment of the present application.
[0072] The OTA upgrade test system includes: client, mobile device, target vehicle and cloud device. The mobile device is connected to the target vehicle and client through wired means, for example, through USB. Both the client and the target vehicle are connected to the cloud device wirelessly.
[0073] Furthermore, the embodiment of the present application adopts the ATX architecture. ATX software is installed in the client, mobile device and target vehicle. Furthermore, ATX Agent is installed in the client. ATX Server is installed in the mobile device. ATX plug-in is installed in the vehicle system of the target vehicle. In order to realize the control of the client and the target vehicle by the mobile device, a Python script for performing OTA upgrade test is also installed in the mobile device.
[0074] The mobile device controls the client to send an upgrade test request to the cloud device for the target vehicle.
[0075] The cloud device receives the upgrade test request; sends a version detection request to the target vehicle and receives the vehicle software information returned by the target vehicle; when it is determined that the target vehicle has software to be upgraded based on the vehicle software information, returns the upgrade information to the client and sends a software upgrade task to the target vehicle.
[0076] After receiving the upgrade pending message returned by the cloud device, the client controls the target vehicle to be unlocked under the control of the mobile device.
[0077] After the target vehicle is in the unlocked state, the mobile device controls the target vehicle to enter the target power-on state, and after the target vehicle is in the target power-on state, controls the target vehicle to perform a software upgrade task, and synchronizes and displays the upgrade progress information of the target vehicle.
[0078] When the target vehicle is performing a software upgrade task, the client synchronizes and displays the upgrade progress information of the target vehicle from the cloud device.
[0079] When the target vehicle is performing a software upgrade task, the cloud device monitors and synchronizes the upgrade progress information of the target vehicle to the mobile device.
[0080] The following is a detailed description of the steps performed by each part in the OTA upgrade test system.
[0081] The mobile device sends a preset instruction to the client, and after receiving the preset instruction, the client sends an upgrade test request to the cloud device.
[0082] The cloud device receives the upgrade test request sent by the client and sends a version detection request to the target vehicle.
[0083] The target vehicle receives the version detection request sent by the cloud device, turns on high voltage on the vehicle, obtains the VIN (Vehicle Identification Number) and the current ECU version, forms the vehicle software information and sends it to the cloud device, and then turns off high voltage on the target vehicle.
[0084] After receiving the vehicle software information, the cloud device identifies the latest ECU version corresponding to the VIN. If the latest ECU version is later than the current ECU version, it means that the target vehicle has software to be upgraded, and returns True (upgrade information) to the client. Of course, if the latest ECU version is earlier than the current ECU version or the latest ECU version is the same as the current ECU version, it means that the target vehicle does not have software to be upgraded, and returns False to the client.
[0085] The ATX installed in the mobile terminal and the client can realize the monitoring of the client by the mobile terminal, and then can know that the client has received the information to be upgraded. At this time, the mobile device queries the vehicle status of the target vehicle from the cloud device; when the vehicle status of the target vehicle is powered off, the mobile device determines whether the target vehicle meets the unlocking conditions through the Python script. In this embodiment, the unlocking conditions are: unlocking condition 1 and unlocking condition 2.
[0086] Explanation condition 1: The Python script in the mobile device controls the client to open the "My Vehicle" page in the user interface. The ATX in the mobile device obtains the page elements and simulates clicking the "lock car icon". If the page pops up a window prompting "The vehicle is locked", it returns True, indicating that the target vehicle is locked.
[0087] Explanation condition 2: The Python script in the mobile device accesses the cloud device and queries the VIN of the target vehicle to obtain whether the target vehicle is online. If the target vehicle is offline, True is returned, indicating that the target vehicle is in a locked state.
[0088] When the Python script in the mobile device determines that both unlocking condition 1 and unlocking condition 2 are met, it determines that the target vehicle has the interpretation condition. The ATX in the mobile device obtains the page element in the "My Vehicle" page of the client, simulates clicking the "unlock icon", and the client sends an unlocking command to the target vehicle so that the target vehicle is unlocked.
[0089] The Python script in the mobile device controls the relay connected to the door control motor in the target vehicle to close, controls the door control motor (high level) to open the corresponding door, and puts the target vehicle into a power-on state.
[0090] After determining that the target vehicle has software to be upgraded, the cloud device sends a software upgrade task to the target vehicle, and the target vehicle receives the software upgrade task.
[0091] The Python script in the mobile device simulates clicking on the car screen (home button). The ATX in the mobile device obtains the interface elements in the car screen and simulates clicking "Settings" and "Download". The download progress bar (automatic download) will pop up on the interface. After the download is complete, it simulates clicking "Upgrade".
[0092] During the downloading process of the software to be upgraded, the mobile device and the client display the download progress information.
[0093] 1. The Python script in the mobile device obtains the download progress information from the cloud device.
[0094] 2. The Python script in the mobile device monitors the upgrade interface of the target vehicle's large screen through the ATX in the mobile device, and the upgrade interface includes download progress information.
[0095] 3. The client receives the download progress information sent by the cloud device.
[0096] Generally speaking, the download progress information of 1, 2, and 3 is the same. However, if the download progress information of 2 is different from the download progress information of 1 and 3, the download progress information of 2 shall prevail.
[0097] The ATX in the mobile device can monitor the download progress information in the target vehicle in real time. After the download progress information of the target vehicle shows that the download is complete, an upgrade button will pop up in the interface of the target vehicle, and the Python script in the mobile device simulates clicking the upgrade button.
[0098] The ATX in the mobile device monitors the installation progress information of the target vehicle. If the Python script in the mobile device detects that the target vehicle is in the installation detection, it waits for the target vehicle to enter the state of waiting for upgrade and software installation. If the Python script in the mobile device detects that the installation preparation of the target vehicle is complete, the ATX in the mobile device monitors the installation progress information of the target vehicle.
[0099] Regardless of whether the upgrade result of the target vehicle is a success or a failure, it will be reported to the cloud device and the upgrade result will be displayed on the interface of the vehicle screen. The ATX in the mobile device monitors the upgrade result displayed on the interface of the vehicle screen and controls the client to send an upgrade test request so that the cloud device can send the software upgrade task to the target device again.
[0100] In an embodiment of the present application, when the target vehicle is an extended-range vehicle, in order to ensure that the OTA upgrade test can proceed normally, a precondition can be set for the software upgrade task. The precondition may be that the battery power is greater than a preset battery power threshold to prevent the target vehicle from running out of power during the OTA upgrade test and being unable to continue the OTA upgrade test. The battery power is not the power battery of the target vehicle. The battery power threshold is an empirical value or a value obtained through experiments. For example, the battery power threshold is set to 65%.
[0101] The Python script in the mobile device simulates clicking the car screen (home button), and the ATX in the mobile device obtains the interface elements, simulates clicking "Settings" and "Download", and the interface will pop up a download progress bar (automatic download). After the download is completed, simulate clicking "Upgrade", and the interface of the car screen pops up "Insufficient power battery". When the ATX in the mobile device monitors the value "Insufficient battery" returned by the car screen, the Python script in the mobile device queries the cloud device to see whether the error message returned by the software upgrade task is "Insufficient power battery". If both the target vehicle and the cloud device return "Insufficient battery". The Python script in the mobile device will control the car screen to return to the "Main Interface" through the ATX in the mobile device, simulate clicking "Energy" to enter the energy interface, and then simulate clicking the "Fuel Recharge" button to make the target vehicle enter the fuel recharge state. The Python script in the mobile device controls the relay, sends a high level to close the door, waits for the preset time length, and the Python script in the mobile device restarts to determine whether the target vehicle has the unlocking conditions. The preset time length is an empirical value or a value obtained through experiments. For example: set the preset time length to 15 minutes.
[0102] In the embodiment of the present application, in order to solve the problem that after the target vehicle software upgrade task is completed, the target vehicle exits the upgrade interface, and the progress bar of the cloud device is stuck, the Python script in the mobile device queries the upgrade task status of the target vehicle from the cloud device. If the upgrade task status is "upgrading" (executing the software upgrade task), the ATX in the mobile device monitors whether the upgrade result is displayed on the vehicle screen of the target vehicle, because after the upgrade is completed, the vehicle screen will pop up "upgrade success" or "upgrade failure". If one of the fields is detected, it can be considered that the upgrade task status has completed the software upgrade task. If the status of the target vehicle and the cloud device is inconsistent, that is: the target vehicle has completed the software upgrade task, and the cloud device is "upgrading", the Python script in the mobile device controls the vehicle screen to enter "engineering mode" through the ATX in the mobile device, simulates clicking "from mode", and the Python script in the mobile device calls the ADB command to control the vehicle screen, query TBOX and restart TBOX, so that the target vehicle and the cloud device re-establish connection. After that, the mobile device queries the upgrade task status of the target device from the cloud device. If the upgrade task status is "completed" (the software upgrade task has been completed), the Python script in the mobile device will continue to control the client and perform the next OTA upgrade test.
[0103] The embodiment of the present application realizes a highly automated OTA upgrade test. Furthermore, the embodiment of the present application controls the cloud device through a Python script to automatically send the software package to be tested, thereby improving the automation of the test and reducing the tediousness and error rate of manual operation.
[0104] The embodiments of the present application effectively improve the test efficiency. Furthermore, the embodiments of the present application set the preconditions so that the ATX software is installed in the vehicle system, the relay is connected to the door control motor module, the client is connected to the mobile device, and the mobile device is connected to the target vehicle, thereby achieving OTA upgrade testing when the vehicle is powered on or off, thereby improving the test efficiency.
[0105] The embodiment of the present application can effectively improve the user experience. Furthermore, the embodiment of the present application will display "upgrade successful" or "upgrade failed" on the target vehicle, and after the upgrade is completed, an upgrade log will be sent back to the cloud device, so that the user can intuitively understand the status and results of the upgrade, thereby optimizing the user experience.
[0106] The embodiment of the present application can perform real-time monitoring and data analysis. Furthermore, the embodiment of the present application uses a Python script to compare the upgrade progress bar sent by the cloud device with the upgrade progress bar of the target vehicle in real time, and can compare the version information uploaded to the cloud by the ECU after the upgrade is successful with the software package information sent for testing, thereby achieving real-time monitoring and data analysis of the entire test process, which is conducive to the evaluation of test results and the location of problems.
[0107] The present application also provides an OTA upgrade test device provided in a mobile device. Figure 5 , which is a structural diagram of an OTA upgrade test device set in a mobile device according to an embodiment of the present application.
[0108] The OTA upgrade test device, on a mobile device, includes:
[0109] The first sending module 510 is used to control the client to send an upgrade test request to the cloud device for the target vehicle, so that when the cloud device determines that the target vehicle has software to be upgraded based on the upgrade test request, it returns an upgrade message to the client and sends a software upgrade task to the target vehicle.
[0110] The first control module 520 is used to control the target vehicle to be in a target power-on state after determining that the client has received the upgrade message returned by the cloud device; after the target vehicle is in the target power-on state, control the target vehicle to perform a software upgrade task.
[0111] The first display module 530 is used to synchronize and display the upgrade progress information of the target vehicle.
[0112] The functions of the device described in the embodiment of the present application have been described in the above method embodiment. Therefore, for any details not provided in the description of this embodiment, please refer to the relevant descriptions in the above embodiment and will not be repeated here.
[0113] The present application also provides an OTA upgrade test device arranged on a client. Figure 6 , which is a structural diagram of an OTA upgrade test device arranged at a client according to an embodiment of the present application.
[0114] The OTA upgrade test device, on the client side, includes:
[0115] The second sending module 610 is used to send an upgrade test request to the cloud device for the target vehicle under the control of the mobile device, so that when the cloud device determines that the target vehicle has software to be upgraded based on the upgrade test request, it returns an upgrade message and sends a software upgrade task to the target vehicle.
[0116] The second control module 620 is used to control the target vehicle to be in an unlocked state under the control of the mobile device after receiving the upgrade message returned by the cloud device, so that the mobile device controls the target vehicle to enter the target power-on state and executes the software upgrade task.
[0117] The second display module 630 is used to synchronize and display the upgrade progress information of the target vehicle from the cloud device when the target vehicle executes the software upgrade task.
[0118] The functions of the device described in the embodiment of the present application have been described in the above method embodiment. Therefore, for any details not provided in the description of this embodiment, please refer to the relevant descriptions in the above embodiment and will not be repeated here.
[0119] The present application also provides an OTA upgrade test device set in a cloud device. Figure 7 , which is a structural diagram of an OTA upgrade test device set in a cloud device according to an embodiment of the present application.
[0120] The OTA upgrade test device, in the cloud device, includes:
[0121] The receiving module 710 is used to receive an upgrade test request; wherein the upgrade test request is issued by the client to the target vehicle under the control of the mobile device.
[0122] The sending and receiving module 720 is used to send a version detection request to the target vehicle and receive vehicle software information returned by the target vehicle.
[0123] The return and send module 730 is used to return the upgrade information to the client and send a software upgrade task to the target vehicle when it is determined that the target vehicle has software to be upgraded according to the vehicle software information.
[0124] The monitoring and synchronization module 740 is used to monitor and synchronize the upgrade progress information of the target vehicle to the mobile device during the process of the target vehicle executing the software upgrade task.
[0125] The functions of the device described in the embodiment of the present application have been described in the above method embodiment. Therefore, for any details not provided in the description of this embodiment, please refer to the relevant descriptions in the above embodiment and will not be repeated here.
[0126] The present application also provides an OTA upgrade test device, such as Figure 8 , which is a structural diagram of an OTA upgrade test device according to an embodiment of the present application.
[0127] The OTA upgrade test device includes: a processor 810, a communication interface 820, a memory 830 and a communication bus 840. The processor 810, the communication interface 820, and the memory 830 communicate with each other through the communication bus 840.
[0128] The memory 830 is used to store computer programs.
[0129] In one embodiment of the present application, the processor 810, when executing the program stored in the memory 830, implements the OTA upgrade test method provided by any of the aforementioned method embodiments and executed on a mobile device, including: controlling the client to send an upgrade test request to a cloud device for a target vehicle, so that when the cloud device determines that the target vehicle has software to be upgraded according to the upgrade test request, it returns an upgrade message to the client and sends a software upgrade task to the target vehicle; after determining that the client has received the upgrade message returned by the cloud device, controlling the target vehicle to be in a target power-on state; after the target vehicle is in the target power-on state, controlling the target vehicle to execute the software upgrade task, and synchronizing and displaying the upgrade progress information of the target vehicle.
[0130] Wherein, controlling the target vehicle to be in a target power-on state includes: monitoring the vehicle state of the target vehicle; when the vehicle state is a power-off state, if the target vehicle is identified to be in a locked state by controlling the client and / or the target vehicle is determined to be in an offline state by the cloud device, then unlocking the target vehicle by controlling the client; after unlocking the target vehicle, controlling a relay connected to a door control motor in the target vehicle so that the door control motor drives the corresponding door to open, so that the target vehicle enters a power-on state.
[0131] Wherein, after controlling the target vehicle to be in the target power-on state through the client, it also includes: monitoring the vehicle state of the target vehicle; wherein, the target vehicle is a Zengcheng vehicle; when the vehicle state is in the power-on state, monitoring the battery power of the target vehicle; if the battery power is less than a preset battery power threshold, querying the upgrade task status corresponding to the target vehicle from the cloud device; wherein, the target vehicle starts from attempting to execute the software upgrade task, and reports the upgrade task status to the cloud device; if the upgrade task status is that the vehicle power battery is insufficient, controlling the target vehicle to enter the fuel replenishment state.
[0132] Wherein, the synchronization and display of the upgrade progress information of the target vehicle includes: monitoring the upgrade progress information of the target vehicle, and displaying the monitored upgrade progress information of the target vehicle; or monitoring the upgrade progress information of the target vehicle; obtaining the upgrade progress information of the target vehicle from the cloud device; wherein, during the process of the target vehicle executing the software upgrade task, the target vehicle reports the upgrade progress information to the cloud device; if the monitored upgrade progress information of the target vehicle is different from the obtained upgrade progress information of the target vehicle, the upgrade progress information corresponding to the shortest network delay is selected for display.
[0133] Wherein, after controlling the target vehicle to execute the software upgrade task, it includes: after monitoring that the target vehicle has completed the software upgrade task, querying the upgrade task status of the target vehicle from the cloud device; wherein, the target vehicle reports the upgrade task status to the cloud device during the process of executing the software upgrade task; if the upgrade task status is that the target vehicle is executing the software upgrade task, controlling the target vehicle to reconnect to the cloud device; if the upgrade task status is that the target vehicle has completed the software upgrade task, controlling the client to send the next upgrade test request to the cloud device for the target vehicle, so as to perform the next OTA upgrade test.
[0134] In another embodiment of the present application, the processor 810 is used to implement the OTA upgrade test method performed on the client provided by any of the aforementioned method embodiments when executing the program stored on the memory 830, including: under the control of the mobile device, sending an upgrade test request to a cloud device for a target vehicle, so that when the cloud device determines that there is software to be upgraded in the target vehicle according to the upgrade test request, it returns a message to be upgraded and sends a software upgrade task to the target vehicle; after receiving the message to be upgraded returned by the cloud device, under the control of the mobile device, controlling the target vehicle to be in an unlocked state, so that the mobile device controls the target vehicle to enter a target power-on state and executes the software upgrade task; while the target vehicle executes the software upgrade task, synchronizing and displaying the upgrade progress information of the target vehicle from the cloud device.
[0135] Wherein, under the control of the mobile device, controlling the target vehicle to be in an unlocked state includes: under the control of the mobile device, triggering a simulated click of a lock button on the mobile device; after a preset lock status information pops up, sending a lock status message to the mobile device; under the control of the mobile device, triggering a simulated click of an unlock button on the mobile device, sending an unlock instruction to the target vehicle, so as to unlock the target vehicle.
[0136] Wherein, during the process of the target vehicle executing the software upgrade task, the upgrade progress information of the target vehicle is synchronously displayed, including: receiving and displaying the upgrade progress information of the target vehicle sent by the cloud device; wherein, during the process of the target vehicle executing the software upgrade task, the target vehicle reports the upgrade progress information to the cloud device.
[0137] In another embodiment of the present application, the processor 810, when executing the program stored in the memory 830, implements the OTA upgrade test method provided by any of the aforementioned method embodiments and executed on a cloud device, including: receiving an upgrade test request; wherein the upgrade test request is issued by a client to a target vehicle under the control of a mobile device; sending a version detection request to the target vehicle and receiving vehicle software information returned by the target vehicle; when it is determined that the target vehicle has software to be upgraded based on the vehicle software information, returning the information to be upgraded to the client and sending a software upgrade task to the target vehicle; during the process of the target vehicle executing the software upgrade task, monitoring and synchronizing the upgrade progress information of the target vehicle to the mobile device.
[0138] The embodiment of the present application also provides a computer-readable storage medium on which a computer program is stored. When the computer program is executed by a processor, the steps of the OTA upgrade test method performed on a mobile device as provided in any of the aforementioned method embodiments are implemented, or the steps of the OTA upgrade test method performed on a client as provided in any of the aforementioned method embodiments are implemented, or the steps of the OTA upgrade test method performed on a cloud device as provided in any of the aforementioned method embodiments are implemented. Since the OTA upgrade test method performed on each end has been described in detail above, for any details not fully described in the description of this embodiment, please refer to the relevant descriptions in the aforementioned embodiments, and no further description will be given here.
[0139] 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.
[0140] 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.
[0141] 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.
[0142] The above description is only a specific implementation of the present application, so that those skilled in the art can understand or implement the present application. Various modifications to these embodiments will be apparent to those skilled in the art, and the general principles defined herein can be implemented in other embodiments without departing from the spirit or scope of the present application. Therefore, the present application will not be limited to the embodiments shown herein, but will conform to the widest range consistent with the principles and novel features applied for herein.
Claims
1. An OTA upgrade test method, characterized in that: Applicable to mobile devices, including: Control the client to send an upgrade test request to the cloud device for the target vehicle, so that when the cloud device determines that the target vehicle has software to be upgraded according to the upgrade test request, it returns an upgrade message to the client and sends a software upgrade task to the target vehicle; After determining that the client receives the to-be-upgraded message returned by the cloud device, controlling the target vehicle to be in a target power-on state; After the target vehicle is in the target power-on state, the target vehicle is controlled to execute a software upgrade task, and upgrade progress information of the target vehicle is synchronized and displayed.
2. The method according to claim 1, characterized in that The controlling the target vehicle to be in a target powered-on state includes: monitoring a vehicle status of the target vehicle; When the vehicle is in a power-off state, if the target vehicle is identified to be in a locked state by controlling the client and / or the target vehicle is determined to be in an offline state by the cloud device, the target vehicle is unlocked by controlling the client; After unlocking the target vehicle, the door control motor drives the corresponding door to open by controlling a relay connected to the door control motor in the target vehicle, so that the target vehicle enters a power-on state.
3. The method according to claim 1, characterized in that: After the target vehicle is controlled by the client to be in a target power-on state, the method further includes: Monitoring the vehicle status of the target vehicle; wherein the target vehicle is a Zengcheng vehicle; When the vehicle is in a powered-on state, monitoring the battery power of the target vehicle; If the battery power is less than a preset battery power threshold, querying the upgrade task status corresponding to the target vehicle from the cloud device; wherein the target vehicle reports the upgrade task status to the cloud device starting from attempting to execute the software upgrade task; If the upgrade task status is that the vehicle power battery is insufficient, the target vehicle is controlled to enter a fuel replenishment state.
4. The method according to claim 1, characterized in that: The synchronizing and displaying the upgrade progress information of the target vehicle includes: monitoring the upgrade progress information of the target vehicle, and displaying the monitored upgrade progress information of the target vehicle; or, Monitor the upgrade progress information of the target vehicle; obtain the upgrade progress information of the target vehicle from the cloud device; wherein, during the process of the target vehicle executing the software upgrade task, the target vehicle reports the upgrade progress information to the cloud device; if the monitored upgrade progress information of the target vehicle is different from the acquired upgrade progress information of the target vehicle, the upgrade progress information corresponding to the shortest network delay is selected for display.
5. The method according to claim 1, characterized in that After controlling the target vehicle to perform the software upgrade task, the method further comprises: After monitoring that the target vehicle has completed the software upgrade task, querying the upgrade task status of the target vehicle from the cloud device; wherein the target vehicle reports the upgrade task status to the cloud device during the execution of the software upgrade task; If the upgrade task status is that the target vehicle is performing a software upgrade task, controlling the target vehicle to reconnect to the cloud device; If the upgrade task status is that the target vehicle has completed the software upgrade task, the client is controlled to send the next upgrade test request to the cloud device for the target vehicle so as to perform the next OTA upgrade test.
6. An OTA upgrade test method, characterized in that: Applied to the client, including: Under the control of the mobile device, an upgrade test request is sent to a cloud device for a target vehicle, so that when the cloud device determines that the target vehicle has software to be upgraded according to the upgrade test request, it returns a message to be upgraded and sends a software upgrade task to the target vehicle; After receiving the to-be-upgraded message returned by the cloud device, under the control of the mobile device, the target vehicle is controlled to be in an unlocked state, so that the mobile device controls the target vehicle to enter a target power-on state and executes the software upgrade task; During the process of the target vehicle executing the software upgrade task, the upgrade progress information of the target vehicle is synchronized and displayed from the cloud device.
7. The method according to claim 6, characterized in that Under the control of the mobile device, controlling the target vehicle to be in an unlocked state includes: Under the control of the mobile device, trigger the mobile device to simulate clicking a car lock button; after a preset car lock status information pops up, send a car lock status message to the mobile device; Under the control of the mobile device, the unlock button of the mobile device is triggered to simulate clicking, and an unlock instruction is sent to the target vehicle to unlock the target vehicle.
8. The method according to claim 7, characterized in that In the process of executing the software upgrade task on the target vehicle, synchronously displaying the upgrade progress information of the target vehicle includes: Receive and display the upgrade progress information of the target vehicle sent by the cloud device; wherein, during the process of the target vehicle executing the software upgrade task, the target vehicle reports the upgrade progress information to the cloud device.
9. An OTA upgrade test method, characterized in that: Applied to cloud devices, including: Receiving an upgrade test request; wherein the upgrade test request is issued by the client under the control of the mobile device to the target vehicle; Sending a version detection request to the target vehicle and receiving vehicle software information returned by the target vehicle; When it is determined according to the vehicle software information that the target vehicle has software to be upgraded, returning the upgrade information to the client and sending a software upgrade task to the target vehicle; During the process of the target vehicle executing the software upgrade task, the upgrade progress information of the target vehicle is monitored and synchronized to the mobile device.
10. An OTA upgrade test device, characterized in that: include: at least one communication interface; at least one bus connected to the at least one communication interface; at least one processor coupled to the at least one bus; At least one memory connected to the at least one bus, wherein the processor is configured to: execute the OTA upgrade test program stored in the memory to implement the OTA upgrade test method executed on a mobile device according to any one of claims 1 to 5, or to implement the OTA upgrade test method executed on a client according to any one of claims 6 to 8, or to implement the OTA upgrade test method executed on a cloud device according to claim 9.
