Vehicle OTA Upgrade Method, Device, Equipment and Computer Readable Storage Medium

Abstract

The present application relates to the technical field of vehicle control, and discloses a vehicle OTA upgrade method, device, equipment and storage medium. The method includes: obtaining a target vehicle version number of a target vehicle; determining at least one controller version number corresponding to each vehicle version number during the process of upgrading from the current vehicle version number of the target vehicle to the target vehicle version number, and deleting the controller version numbers without upgrade dependency relationships; generating an OTA upgrade task for the target vehicle based on the remaining controller version numbers and sending the OTA upgrade task to the target vehicle for OTA upgrade. By applying the technical solution of the present application, cross-version upgrade of vehicle OTA can be achieved, the entire upgrade process and upgrade time are shortened, and the upgrade experience of users is improved.

Description

Technical Field

[0001] This application relates to the technical field of vehicle control, and particularly to a vehicle OTA upgrade method, device, equipment and computer-readable storage medium. Background Art

[0002] Traditional vehicle OTA upgrades usually upgrade the vehicle according to the vehicle version path pre-configured on the OTA platform. However, in the existing vehicle OTA upgrade process, each version is upgraded in sequence, which results in too long OTA upgrade process and upgrade time, affecting the user's upgrade experience. Summary of the Invention

[0003] In view of the above problems, this application provides a vehicle OTA upgrade method, device, equipment and computer-readable storage medium, which is used to solve the problems of too long upgrade process and upgrade time existing in the prior art.

[0004] According to one aspect of the embodiments of this application, a vehicle OTA upgrade method is provided, and the method includes:

[0005] Obtain the target vehicle version number of the target vehicle;

[0006] Determine at least one controller version number corresponding to each vehicle version number in the process of upgrading from the current vehicle version number of the target vehicle to the target vehicle version number, and delete the controller version numbers without upgrade dependencies;

[0007] Generate an OTA upgrade task for the target vehicle based on the remaining controller version numbers and send it to the target vehicle for OTA upgrade.

[0008] In an alternative manner, the step of obtaining the target vehicle version number of the target vehicle includes:

[0009] Determine the target vehicle version number of the target vehicle according to the VIN code of the target vehicle.

[0010] In an alternative manner, the step of determining at least one controller version number corresponding to each vehicle version number in the process of upgrading from the current vehicle version number of the target vehicle to the target vehicle version number includes:

[0011] Judge whether there is a target upgrade path from the current vehicle version number to the target vehicle version number;

[0012] If so, determine at least one controller version number corresponding to the vehicle version numbers included in the target upgrade path as the controller version numbers in the process of upgrading from the current vehicle version number to the target vehicle version number.

[0013] In an alternative manner, the step of determining at least one controller version number corresponding to each vehicle version number during the process of upgrading from the current vehicle version number of the target vehicle to the target vehicle version number further includes:

[0014] If not, obtain the maximum upgrade path corresponding to the current vehicle version number, and determine at least one controller version number corresponding to the vehicle version numbers included in the maximum upgrade path;

[0015] Use the vehicle version numbers included in the maximum upgrade path as the current vehicle version number, and return to execute the step of obtaining the maximum upgrade path corresponding to the current vehicle version number until each maximum upgrade path during the process of upgrading from the current vehicle version number to the target vehicle version number is obtained;

[0016] Respectively determine the at least one controller version number corresponding to the vehicle version numbers included in each maximum upgrade path as the controller version numbers during the process of upgrading from the current vehicle version number to the target vehicle version number.

[0017] In an alternative manner, at least one upgrade version number of a controller is included in all the controller version numbers; the step of deleting the controller version numbers without upgrade dependencies includes:

[0018] When there are multiple upgrade version numbers in the upgrade version number corresponding to any controller, determine whether there is a dependent version number among the multiple upgrade version numbers of the controller;

[0019] If so, delete the dependent version number corresponding to the controller until the dependent version number corresponding to each controller is deleted.

[0020] In an alternative manner, the step of generating an OTA upgrade task for the target vehicle based on the remaining controller version numbers includes:

[0021] Classify and sort the remaining controller version numbers in ascending order based on the controller type and the controller version number to obtain a target queue;

[0022] Generate an OTA upgrade task for the target vehicle according to the target queue.

[0023] According to another aspect of the embodiments of the present application, there is provided a vehicle OTA upgrade device, including:

[0024] An acquisition module, configured to acquire the target vehicle version number of the target vehicle;

[0025] A processing module, configured to determine at least one controller version number corresponding to each vehicle version number during the process of upgrading from the current vehicle version number of the target vehicle to the target vehicle version number, and delete the controller version numbers without upgrade dependency relationships;

[0026] An upgrade module, configured to generate an OTA upgrade task for the target vehicle based on the remaining controller version numbers and send it to the target vehicle for OTA upgrade.

[0027] In an alternative manner, the obtaining module is configured to:

[0028] Determine the target vehicle version number of the target vehicle according to the VIN code of the target vehicle.

[0029] According to another aspect of the embodiments of the present application, there is provided a vehicle OTA upgrade device, including:

[0030] A controller;

[0031] A memory, configured to store one or more programs, which when executed by the controller, cause the controller to implement the vehicle OTA upgrade method of the present invention.

[0032] According to yet another aspect of the embodiments of the present invention, there is provided a storage medium, in which at least one executable instruction is stored, and when the executable instruction runs on a vehicle OTA upgrade device / equipment, it causes the vehicle OTA upgrade device / equipment to execute the operations of the vehicle OTA upgrade method of the present invention.

[0033] In the embodiments of the present application, by obtaining the target vehicle version number of the target vehicle; determining at least one controller version number corresponding to each vehicle version number during the process of upgrading from the current vehicle version number of the target vehicle to the target vehicle version number, and deleting the controller version numbers without upgrade dependency relationships; generating an OTA upgrade task for the target vehicle based on the remaining controller version numbers and sending it to the target vehicle for OTA upgrade, it is possible to achieve cross-version OTA upgrade of the vehicle, shorten the entire upgrade process and upgrade time, and improve the user's upgrade experience.

[0034] The above description is only an overview of the technical solutions of the embodiments of the present application. In order to be able to understand the technical means of the embodiments of the present application more clearly, it can be implemented according to the content of the specification. And in order to make the above and other purposes, features and advantages of the embodiments of the present application more obvious and understandable, the following specifically illustrates the embodiments of the present application. Description of the Drawings

[0035] The drawings are only used to illustrate the embodiments and are not considered to be a limitation of the present application. And throughout the drawings, the same reference numerals are used to represent the same components. In the drawings:

[0036] Figure 1 Shows a schematic flowchart of the first embodiment of the vehicle OTA upgrade method provided by the present application;

[0037] Figure 2 Shows a schematic flowchart of the second embodiment of the vehicle OTA upgrade method provided by the present application;

[0038] Figure 3 Shows a schematic flowchart of the third embodiment of the vehicle OTA upgrade method provided by the present application;

[0039] Figure 4 Shows a schematic flowchart of the fourth embodiment of the vehicle OTA upgrade method provided by the present application;

[0040] Figure 5 Shows the overall flowchart of the vehicle OTA upgrade method;

[0041] Figure 6 Shows a schematic structural diagram of an embodiment of the vehicle OTA upgrade device provided by the present application;

[0042] Figure 7 Shows a schematic structural diagram of an embodiment of the vehicle OTA upgrade equipment provided by the present application. Detailed Description of the Specific Embodiment

[0043] Here, the exemplary embodiments will be described in detail, and the examples are shown in the drawings. When the following description refers to the drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present application. On the contrary, they are merely examples of devices and methods consistent with some aspects of the present application as detailed in the appended claims.

[0044] The block diagrams shown in the drawings are only functional entities and do not necessarily correspond to physically independent entities. That is, these functional entities can be implemented in software form, or implemented in one or more hardware modules or integrated circuits, or implemented in different networks and / or processor devices and / or microcontroller devices.

[0045] The flowcharts shown in the drawings are only exemplary descriptions, not necessarily including all contents and operations / steps, nor necessarily executed in the described order. For example, some operations / steps can be decomposed, and some operations / steps can be combined or partially combined, so the actual execution order may change according to the actual situation.

[0046] As used in this application, "a plurality of" means two or more. " / or" describes the relationship between associated objects and indicates three possible relationships. For example, A / or B can represent: A exists alone, both A and B exist simultaneously, and B exists alone. The character " / " generally indicates an "or" relationship between the associated objects before and after.

[0047] Traditional vehicle OTA upgrades usually upgrade the vehicle according to the vehicle version path pre-configured on the OTA platform. However, in the existing vehicle OTA upgrade process, each version is upgraded sequentially, which results in a long OTA upgrade process and upgrade time for the vehicle, affecting the user's upgrade experience.

[0048] Figure 1 The flowchart of the first embodiment of the vehicle OTA upgrade method provided by this application is shown, and this method is executed by the OTA cloud device. Please refer to Figure 1 As shown, this method includes the following steps:

[0049] Step S110: Obtain the target vehicle version number of the target vehicle.

[0050] Among them, the target vehicle is the vehicle that needs to be OTA upgraded in this embodiment. The target vehicle version number (taskVersion) is the vehicle version number of the target task, that is, the latest issued vehicle version number that the user is expected to upgrade. For example, the target vehicle version number is vehicle version 3.0.

[0051] Specifically, the OTA cloud device obtains the target vehicle version number of the target vehicle.

[0052] Step S120: Determine at least one controller version number corresponding to each vehicle version number during the process of upgrading from the current vehicle version number of the target vehicle to the target vehicle version number, and delete the controller version numbers without upgrade dependencies.

[0053] Among them, the current vehicle version number (currentVersion) is the current vehicle version number of the target vehicle at the vehicle end. For example, the current vehicle version number is vehicle version 1.0.

[0054] Among them, each vehicle version number includes at least one controller (ECU) version number. For example, vehicle version 1.0 includes controller version numbers A-1.0, B-1.0, and C-1.0.

[0055] Among them, all the controller version numbers form EcuVersionCache, that is, to complete the entire upgrade (in this example, from vehicle version 1.0 to vehicle version 3.0), the ECU upgrade list cache corresponding to the vehicle version path (1.0 -> 2.0, 2.0 -> 3.0).

[0056] Among them, if during the process of upgrading from A-1.0 to A-3.0, it is necessary to first upgrade from A-1.0 to A-2.0 and then from A-2.0 to A-3.0, it indicates that there is an upgrade dependency relationship between A-2.0 and A-3.0; if during the process of upgrading from A-1.0 to A-3.0, it is possible to directly upgrade from A-1.0 to A-3.0, it indicates that there is no upgrade dependency relationship between A-2.0 and A-3.0, and the controller version number A-2.0 can be deleted.

[0057] Specifically, the OTA cloud device determines at least one controller version number corresponding to each vehicle version number during the process of upgrading from the current vehicle version number of the target vehicle to the target vehicle version number, and deletes the controller version numbers without upgrade dependency relationships.

[0058] Step S130: Based on the remaining controller version numbers, generate an OTA upgrade task for the target vehicle and send it to the target vehicle for OTA upgrade.

[0059] Among them, the OTA upgrade task includes the remaining controller version numbers and the corresponding software download addresses.

[0060] Specifically, the OTA cloud device uses the remaining controller version numbers to generate an OTA upgrade task for the target vehicle and sends the OTA upgrade task to the vehicle end of the target vehicle so that the vehicle end can perform the upgrade according to the OTA upgrade task.

[0061] The technical solution of this embodiment can realize cross-version OTA upgrade of the vehicle by obtaining the target vehicle version number of the target vehicle, determining at least one controller version number corresponding to each vehicle version number during the process of upgrading from the current vehicle version number of the target vehicle to the target vehicle version number, deleting the controller version numbers without upgrade dependency relationships, and generating an OTA upgrade task for the target vehicle based on the remaining controller version numbers and sending it to the target vehicle for OTA upgrade, shortening the entire upgrade process and upgrade time, and improving the user's upgrade experience.

[0062] Figure 2 The flowchart of the second embodiment of the vehicle OTA upgrade method provided by the present application is shown, and this method is executed by the OTA cloud device. Please refer to Figure 2 As shown, this method includes the following steps:

[0063] Step S210: Determine the target vehicle version number of the target vehicle according to the VIN code of the target vehicle.

[0064] Specifically, the OTA cloud device determines the target vehicle version number of the target vehicle according to the VIN code of the target vehicle.

[0065] Among them, one vehicle corresponds to one VIN code, and through the VIN code, the tasks sorted by time within the validity period of the vehicle in the vehicle task list can be queried. When the task ID of the target vehicle is returned, the target vehicle version number of the target vehicle is determined according to the task ID.

[0066] Step S220: Determine at least one controller version number corresponding to each vehicle version number during the process of upgrading from the current vehicle version number of the target vehicle to the target vehicle version number, and delete the controller version numbers without upgrade dependency relationships.

[0067] Step S230: Based on the remaining controller version numbers, generate an OTA upgrade task for the target vehicle and send it to the target vehicle for OTA upgrade.

[0068] The technical solution of this embodiment further determines the target vehicle version number according to the vehicle VIN code, can realize cross-version OTA upgrade of the vehicle, shortens the entire upgrade process and upgrade time, and improves the user's upgrade experience.

[0069] Figure 3 The flowchart of the third embodiment of the vehicle OTA upgrade method provided by this application is shown, and this method is executed by the OTA cloud device. Please refer to Figure 3 As shown, this method includes the following steps:

[0070] Step S310: Obtain the target vehicle version number of the target vehicle.

[0071] Step S320: Determine whether there is a target upgrade path from the current vehicle version number to the target vehicle version number.

[0072] Among them, the target upgrade path is the upgrade path that directly upgrades to the target vehicle version number. For example, the current vehicle version number 1.0 includes: A-1.0 and B-1.0, and the target vehicle version number includes: A-2.0 and B-2.0; at this time, the target upgrade path is: A-1.0 → A-2.0, B-1.0 → B-2.0.

[0073] Specifically, the OTA cloud device determines whether there is a target upgrade path from the current vehicle version number to the target vehicle version number, and obtains a judgment result.

[0074] Step S330A: If so, determine at least one controller version number corresponding to the vehicle version numbers included in the target upgrade path as the controller version numbers during the process of upgrading from the current vehicle version number to the target vehicle version number.

[0075] Among them, one target upgrade path corresponds to one vehicle version number, such as vehicle version 2.0. One vehicle version number corresponds to at least one controller, and each controller corresponds to a controller version number. For example, vehicle version 2.0 includes controller A and controller B. The controller version number corresponding to controller A is A-2.0, and the controller version number corresponding to controller B is B-2.0.

[0076] Specifically, when the judgment result is yes, the OTA cloud device determines at least one controller version number corresponding to the vehicle version number included in the target upgrade path as the controller version number during the upgrade from the current vehicle version number to the target vehicle version number.

[0077] Step S340: Delete the controller version numbers without upgrade dependencies.

[0078] Step S350: Generate an OTA upgrade task for the target vehicle based on the remaining controller version numbers and send it to the target vehicle for OTA upgrade.

[0079] Preferably, it further includes:

[0080] Step S330B: If not, obtain the maximum upgrade path corresponding to the current vehicle version number, and determine at least one controller version number corresponding to the vehicle version number included in the maximum upgrade path.

[0081] Among them, the maximum upgrade path is reachableVersion, that is, the version that the current version can be upgraded to the maximum extent under the upgrade path. For example, if the target vehicle is vehicle version 1.0, the maximum reachable vehicle version is 2.0.

[0082] Specifically, when the judgment result is no, the OTA cloud device obtains the maximum upgrade path corresponding to the current vehicle version number and determines at least one controller version number corresponding to the vehicle version number included in the maximum upgrade path.

[0083] Step S331B: Use the vehicle version number included in the maximum upgrade path as the current vehicle version number, and return to execute the step of obtaining the maximum upgrade path corresponding to the current vehicle version number until each maximum upgrade path during the upgrade from the current vehicle version number to the target vehicle version number is obtained.

[0084] Among them, when there is a maximum upgrade path, the number of maximum upgrade paths is at least one. After determining a maximum upgrade path, if the target vehicle version number is not reached, the vehicle version numbers included in the maximum upgrade path are used as the current vehicle version number, and the step of obtaining the maximum upgrade path corresponding to the current vehicle version number is returned for execution until each maximum upgrade path in the process of upgrading from the current vehicle version number to the target vehicle version number is obtained. For example, if the current vehicle version number is 1.0 and the target vehicle version number is 3.0, there are two maximum upgrade paths reachableVersion1 and reachableVersion2 in the upgrade process; reachableVersion1 is: vehicle version 1.0 → vehicle version 2.0; reachableVersion2 is: vehicle version 2.0 → vehicle version 3.0.

[0085] Specifically, the OTA cloud device uses the vehicle version numbers included in the maximum upgrade path as the current vehicle version number, and returns to execute the step of obtaining the maximum upgrade path corresponding to the current vehicle version number until each maximum upgrade path in the process of upgrading from the current vehicle version number to the target vehicle version number is obtained.

[0086] Step S332B: Determine at least one controller version number corresponding to the vehicle version number included in each maximum upgrade path as the controller version number in the process of upgrading the current vehicle version number to the target vehicle version number.

[0087] Among them, one maximum upgrade path corresponds to one vehicle version number, one vehicle version number corresponds to at least one controller, and each controller corresponds to one controller version number.

[0088] Specifically, the OTA cloud device determines at least one controller version number corresponding to the vehicle version number included in each maximum upgrade path as the controller version number in the process of upgrading the current vehicle version number to the target vehicle version number.

[0089] The technical solution of this embodiment further determines the controller version number required for the upgrade according to the upgrade path in the process of upgrading the current vehicle version number to the target vehicle version number, so as to realize the cross-version upgrade of vehicle OTA through one upgrade process, shorten the entire upgrade process and upgrade time, and improve the user's upgrade experience.

[0090] Figure 4 The flowchart of the fourth embodiment of the vehicle OTA upgrade method provided by the present application is shown. This method is executed by the OTA cloud device. Please refer to Figure 4 As shown, this method includes the following steps:

[0091] Step S410: Obtain the target vehicle version number of the target vehicle.

[0092] Step S420: Determine at least one controller version number corresponding to each vehicle version number during the process of upgrading from the current vehicle version number of the target vehicle to the target vehicle version number.

[0093] Step S430: When there are multiple upgrade version numbers in the upgrade version numbers corresponding to any controller, determine whether there is a dependent version number among the multiple upgrade version numbers of the controller.

[0094] Among them, if a controller needs to be upgraded, there is at least one upgrade version number corresponding to the controller. For example, the upgrade version numbers corresponding to Controller A (the current controller version is A-1.0) are A-2.0 and A-3.0.

[0095] Among them, the dependent version number is: the version number that must be experienced during the process of upgrading from a lower version number to a higher version number. For example, during the process of upgrading from A-1.0 to A-3.0, it must be upgraded from A-1.0 to A-2.0, and then from A-2.0 to A-3.0, then A-2.0 is the dependent version number.

[0096] Specifically, when there are multiple upgrade version numbers in the upgrade version numbers corresponding to any controller, the OTA cloud device determines whether there is a dependent version number among the multiple upgrade version numbers of the controller to obtain a judgment result.

[0097] Step S440: If so, delete the dependent version number corresponding to the controller until the dependent version number corresponding to each controller is deleted.

[0098] Specifically, when the judgment result is yes, the OTA cloud device deletes the dependent version number corresponding to the controller, and repeats the steps of S430 to judge each controller until the dependent version number corresponding to each controller is deleted.

[0099] It should be noted that when the judgment result is no, the OTA cloud device does not delete the controller version number corresponding to the controller.

[0100] Step S450: Generate an OTA upgrade task for the target vehicle based on the remaining controller version numbers and send it to the target vehicle for OTA upgrade.

[0101] The technical solution of this embodiment further trims and integrates the vehicle controller version. While realizing the OTA cross-version upgrade of the vehicle, it also shortens the entire upgrade process and upgrade time, and improves the user's upgrade experience.

[0102] Based on the technology of any of the above embodiments, the step of generating the OTA upgrade task for the target vehicle based on the remaining controller version numbers includes:

[0103] Based on the controller type and the controller version number, classify and sort the remaining controller version numbers in ascending order to obtain a target queue.

[0104] Among them, one controller type corresponds to one controller, such as controller A, controller B, and controller C. The target queue is grouped according to the controller type and arranged in ascending order according to the controller version number. For example, at this time, the controller version numbers include A-2.0, B-2.0, A-3.0, B-3.0, then the target queue is: {A-2.0, A-3.0, B-2.0, B-3.0}.

[0105] Generate the OTA upgrade task for the target vehicle according to the target queue.

[0106] Specifically, the OTA cloud device classifies and sorts the remaining controller version numbers based on the controller type and the controller version number to obtain a target queue, and generates the OTA upgrade task for the target vehicle according to the target queue.

[0107] It should be noted that as Figure 5 shown, the OTA cloud device queries the latest task taskVersion that the vehicle can upgrade through the VIN code uploaded by the vehicle end; queries whether there is a path from the current vehicle version currentVersion of the vehicle to taskVersion, and if so, directly sends down the upgrade task. If not, find the maximum upgradable path reachableVersion1 that can be reached currently, and the maximum upgradable path reachableVersion2 reachable by reachableVersion1, and so on, until the final taskVersion. Query the upgrade version corresponding to each controller of the target vehicle version, retain the dependent version and the target version in EcuVersionCache. If the target version of the controller has no dependency requirements, the intermediate versions can be directly skipped and upgraded to the final target version; finally, generate the OTA upgrade task for the vehicle based on the remaining controller version numbers and send it to the vehicle for OTA upgrade.

[0108] Figure 6 shows a schematic structural diagram of an embodiment of a vehicle OTA upgrade device provided by the present application. Please refer to Figure 6 shown, the device 500 includes: an acquisition module 510, a processing module 520, and an upgrade module 530.

[0109] An acquisition module 510, configured to acquire a target vehicle version number of a target vehicle;

[0110] A processing module 520, configured to determine at least one controller version number corresponding to each vehicle version number during the process of upgrading from the current vehicle version number of the target vehicle to the target vehicle version number, and delete the controller version numbers without upgrade dependencies;

[0111] An upgrade module 530, configured to generate an OTA upgrade task for the target vehicle based on the remaining controller version numbers and send the OTA upgrade task to the target vehicle for OTA upgrade.

[0112] In an optional manner, the acquisition module 510 is configured to:

[0113] Determine the target vehicle version number of the target vehicle according to the VIN code of the target vehicle.

[0114] In an optional manner, the step of determining at least one controller version number corresponding to each vehicle version number during the process of upgrading from the current vehicle version number of the target vehicle to the target vehicle version number in the processing module 520 includes:

[0115] Judge whether there is a target upgrade path for upgrading from the current vehicle version number to the target vehicle version number;

[0116] If so, determine at least one controller version number corresponding to the vehicle version numbers included in the target upgrade path as the controller version numbers during the process of upgrading from the current vehicle version number to the target vehicle version number.

[0117] In an optional manner, the step of determining at least one controller version number corresponding to each vehicle version number during the process of upgrading from the current vehicle version number of the target vehicle to the target vehicle version number in the processing module 520 further includes:

[0118] If not, obtain the maximum upgradeable path corresponding to the current vehicle version number, and determine at least one controller version number corresponding to the vehicle version numbers included in the maximum upgradeable path;

[0119] Use the vehicle version numbers included in the maximum upgradeable path as the current vehicle version number, and return to execute the step of obtaining the maximum upgradeable path corresponding to the current vehicle version number until each maximum upgradeable path during the process of upgrading from the current vehicle version number to the target vehicle version number is obtained;

[0120] Determine at least one controller version number corresponding to the vehicle version number included in each maximum upgradable path as the controller version number during the process of upgrading the current vehicle version number to the target vehicle version number.

[0121] In an alternative manner, at least one upgraded version number of a controller is included in all the controller version numbers; the step of deleting the controller version numbers without upgrade dependencies in the processing module 520 includes:

[0122] When there are multiple upgraded version numbers in the upgraded version number corresponding to any controller, determine whether there is a dependent version number among the multiple upgraded version numbers of the controller;

[0123] If so, delete the dependent version number corresponding to the controller until the dependent version number corresponding to each controller is deleted.

[0124] In an alternative manner, the step of generating the OTA upgrade task for the target vehicle based on the remaining controller version numbers in the upgrade module 530 includes:

[0125] Classify and sort the remaining controller version numbers in ascending order based on the controller type and the controller version number to obtain a target queue;

[0126] Generate the OTA upgrade task for the target vehicle according to the target queue.

[0127] The technical solution of this embodiment can achieve cross-version OTA upgrade of the vehicle, shorten the entire upgrade process and upgrade time, and improve the user's upgrade experience.

[0128] It should be noted that the vehicle OTA upgrade device provided in the above embodiment and the vehicle OTA upgrade method provided in the foregoing embodiment belong to the same concept. The specific manners in which each module and unit perform operations have been described in detail in the method embodiment and will not be elaborated here.

[0129] Figure 7 The structural schematic diagram of the embodiment of the vehicle OTA upgrade device of the present application is shown, and the structural schematic diagram of the computer system suitable for implementing the vehicle OTA upgrade device of the embodiment of the present application is shown. The specific implementation of the vehicle OTA upgrade device in the specific embodiment of the present application is not limited.

[0130] Please refer to Figure 7 As shown, the vehicle OTA upgrade device includes: a controller; a memory for storing one or more programs, which when executed by the controller, execute the above-mentioned vehicle OTA upgrade method.

[0131] Please continue to refer to Figure 7As shown, the computer system 600 of the vehicle OTA upgrade device includes a Central Processing Unit (CPU) 601, which can perform various appropriate actions and processes according to the program stored in the Read-Only Memory (ROM) 602 or the program loaded from the storage section 608 into the Random Access Memory (RAM) 603, such as executing the methods in the above embodiments. In the RAM 603, various programs and data required for system operation are also stored. The CPU 601, ROM 602, and RAM 603 are connected to each other via a bus 604. An Input / Output (I / O) interface 605 is also connected to the bus 604.

[0132] The following components are connected to the I / O interface 605: an input section 606 including a keyboard, a mouse, etc.; an output section 607 including, for example, a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), etc. and a speaker, etc.; a storage section 608 including a hard disk, etc.; and a communication section 609 including a network interface card such as a LAN (Local Area Network) card, a modem, etc. The communication section 609 performs communication processing via a network such as the Internet. A drive 610 is also connected to the I / O interface 605 as needed. A removable medium 611, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 610 as needed so that the computer program read from it can be installed into the storage section 608 as needed.

[0133] Specifically, according to the embodiments of the present application, the process described above with reference to the flowchart can be implemented as a computer software program. For example, the embodiments of the present application include a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes a computer program for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from the network through the communication section 609, and / or installed from the removable medium 611. When the computer program is executed by the Central Processing Unit (CPU) 601, various functions defined in the system of the present application are executed.

[0134] Another aspect of the present application also provides a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the vehicle OTA upgrade method described above is implemented. The computer-readable storage medium may be included in the vehicle OTA upgrade device described in the above embodiments, or may exist separately without being assembled into the electronic device.

[0135] On the other hand, the present application also provides a computer program product or a computer program, which includes at least one executable instruction. When the executable instruction runs on a vehicle OTA upgrade device / equipment, the vehicle OTA upgrade device / equipment is caused to execute the vehicle OTA upgrade method as described above.

[0136] The executable instruction can specifically be used to cause the vehicle OTA upgrade device / equipment to perform the following operations:

[0137] Obtain the target vehicle version number of the target vehicle;

[0138] Determine at least one controller version number corresponding to each vehicle version number during the process of upgrading from the current vehicle version number of the target vehicle to the target vehicle version number, and delete the controller version numbers without upgrade dependencies;

[0139] Generate an OTA upgrade task for the target vehicle based on the remaining controller version numbers and send it to the target vehicle for OTA upgrade.

[0140] In an optional manner, the step of obtaining the target vehicle version number of the target vehicle includes:

[0141] Determine the target vehicle version number of the target vehicle according to the VIN code of the target vehicle.

[0142] In an optional manner, the step of determining at least one controller version number corresponding to each vehicle version number during the process of upgrading from the current vehicle version number of the target vehicle to the target vehicle version number includes:

[0143] Judge whether there is a target upgrade path from the current vehicle version number to the target vehicle version number;

[0144] If so, determine at least one controller version number corresponding to the vehicle version numbers included in the target upgrade path as the controller version numbers during the process of upgrading from the current vehicle version number to the target vehicle version number.

[0145] In an optional manner, the step of determining at least one controller version number corresponding to each vehicle version number during the process of upgrading from the current vehicle version number of the target vehicle to the target vehicle version number further includes:

[0146] If not, obtain the maximum upgradeable path corresponding to the current vehicle version number and determine at least one controller version number corresponding to the vehicle version numbers included in the maximum upgradeable path;

[0147] Take the vehicle version number included in the maximum upgrade path as the current vehicle version number, and return to execute the step of obtaining the maximum upgrade path corresponding to the current vehicle version number until each maximum upgrade path in the process of upgrading from the current vehicle version number to the target vehicle version number is obtained;

[0148] Respectively determine at least one controller version number corresponding to the vehicle version number included in each maximum upgrade path as the controller version number in the process of upgrading from the current vehicle version number to the target vehicle version number.

[0149] In an alternative manner, at least one upgraded version number of a controller is included in all the controller version numbers; the step of deleting the controller version numbers without upgrade dependencies includes:

[0150] When there are multiple upgraded version numbers in the upgraded version number corresponding to any controller, determine whether there is a dependent version number among the multiple upgraded version numbers of the controller;

[0151] If so, delete the dependent version number corresponding to the controller until the dependent version number corresponding to each controller is deleted.

[0152] In an alternative manner, the step of generating the OTA upgrade task for the target vehicle based on the remaining controller version numbers includes:

[0153] Classify and sort the remaining controller version numbers in ascending order based on the controller type and the controller version number to obtain a target queue;

[0154] Generate the OTA upgrade task for the target vehicle according to the target queue.

[0155] The technical solution of this embodiment can achieve cross-version OTA upgrade of the vehicle, shorten the entire upgrade process and upgrade time, and improve the user's upgrade experience.

[0156] It should be noted that the computer-readable medium shown in the embodiments of the present application can be a computer-readable signal medium, a computer-readable storage medium, or any combination of the two. A computer-readable storage medium can be, for example, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the above. More specific examples of the computer-readable storage medium may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM), a flash memory, an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present application, the computer-readable storage medium can be any tangible medium that contains or stores a program, and this program can be used by or in combination with an instruction execution system, apparatus, or device. In the present application, a computer-readable signal medium can include a data signal propagated in a baseband or as part of a carrier wave, which carries a computer-readable computer program. Such a propagated data signal can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. The computer-readable signal medium can also be any computer-readable medium other than the computer-readable storage medium, and this computer-readable medium can send, propagate, or transmit a program for use by or in combination with an instruction execution system, apparatus, or device. The computer program contained on the computer-readable medium can be transmitted by any appropriate medium, including but not limited to: wireless, wired, etc., or any suitable combination of the above.

[0157] The flowcharts and block diagrams in the accompanying drawings illustrate the possible architectures, functions, and operations of systems, methods, and computer program products according to various embodiments of the present application. Among them, each block in the flowchart or block diagram can represent a module, a program segment, or a part of code, and the above module, program segment, or part of code contains one or more executable instructions for implementing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the blocks may occur in an order different from that marked in the accompanying drawings. For example, two consecutive blocks shown may actually be executed substantially in parallel, and they may sometimes be executed in the reverse order, depending on the functions involved. It should also be noted that each block in the block diagram or flowchart, as well as the combination of blocks in the block diagram or flowchart, can be implemented by a dedicated hardware-based system for performing the specified functions or operations, or can be implemented by a combination of dedicated hardware and computer instructions.

[0158] The units involved in the embodiments described in this application can be implemented in software or in hardware, and the described units can also be provided in a processor. Among them, the names of these units do not, in some cases, constitute a limitation on the units themselves.

[0159] According to one aspect of the embodiments of the present application, there is also provided a computer system, including a central processing unit (CPU), which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) or a program loaded from a storage section into a random access memory (RAM), such as executing the methods in the above embodiments. In the RAM, various programs and data required for system operations are also stored. The CPU, ROM, and RAM are connected to each other via a bus. An input / output (I / O) interface is also connected to the bus.

[0160] The following components are connected to the I / O interface: an input section including a keyboard, a mouse, etc.; an output section including a cathode ray tube (CRT), a liquid crystal display (LCD), etc. and a speaker; a storage section including a hard disk, etc.; and a communication section including a network interface card such as a LAN (Local Area Network) card, a modem, etc. The communication section performs communication processing via a network such as the Internet. A drive is also connected to the I / O interface as required. A removable medium, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive as required, so that a computer program read from it can be installed into the storage section as required.

[0161] The above content is only a preferred exemplary embodiment of the present application and is not used to limit the implementation of the present application. Those of ordinary skill in the art can make corresponding adaptations or modifications very conveniently according to the main concept and spirit of the present application. Therefore, the protection scope of the present application should be subject to the protection scope required by the claims.

Claims

1. A vehicle OTA upgrade method, characterized in that, the method includes: Obtain the target vehicle version number of the target vehicle; Determine at least one controller version number corresponding to each vehicle version number during the process of upgrading from the current vehicle version number of the target vehicle to the target vehicle version number, and delete the controller version numbers without upgrade dependencies; Generate an OTA upgrade task for the target vehicle based on the remaining controller version numbers and send it to the target vehicle for OTA upgrade; Each vehicle version number corresponds to at least one controller version number. The step of generating the OTA upgrade task for the target vehicle based on the remaining controller version numbers includes: Classify the remaining controller version numbers based on the at least one controller version number and the controller type to obtain a classification result; Arrange the controller version numbers in the classification result in ascending order to obtain a target queue, and the target queue includes at least one upgrade controller version number of at least one controller type; Generate an OTA upgrade task for the target vehicle according to the target queue.

2. The method according to claim 1, characterized in that, the step of obtaining the target vehicle version number of the target vehicle includes: Determine the target vehicle version number of the target vehicle according to the VIN code of the target vehicle.

3. The method according to claim 1, characterized in that, the step of determining at least one controller version number corresponding to each vehicle version number during the process of upgrading from the current vehicle version number of the target vehicle to the target vehicle version number includes: Judge whether there is a target upgrade path from the current vehicle version number to the target vehicle version number; If so, determine at least one controller version number corresponding to the vehicle version numbers included in the target upgrade path as the controller version numbers during the process of upgrading from the current vehicle version number to the target vehicle version number.

4. The method according to claim 3, characterized in that, the step of determining at least one controller version number corresponding to each vehicle version number during the process of upgrading from the current vehicle version number of the target vehicle to the target vehicle version number further includes: If not, obtain the maximum upgradeable path corresponding to the current vehicle version number. The maximum upgradeable path is the maximum version that the current version can be upgraded to, and determine at least one controller version number corresponding to the vehicle version numbers included in the maximum upgradeable path; Use the vehicle version numbers included in the maximum upgradeable path as the current vehicle version number. After determining a maximum upgradeable path, if the target vehicle version number is not reached, use the vehicle version numbers included in the maximum upgradeable path as the current vehicle version number, and return to execute the step of obtaining the maximum upgradeable path corresponding to the current vehicle version number until each maximum upgradeable path during the process of upgrading from the current vehicle version number to the target vehicle version number is obtained. Respectively determine at least one controller version number corresponding to the vehicle version number included in each maximum upgradable path as the controller version number during the process of upgrading the current vehicle version number to the target vehicle version number.

5. A vehicle OTA upgrade device, characterized in that, the device includes: an acquisition module, configured to acquire the target vehicle version number of the target vehicle; a processing module, configured to determine at least one controller version number corresponding to each vehicle version number during the process of upgrading the current vehicle version number of the target vehicle to the target vehicle version number, and delete the controller version numbers without upgrade dependency relationships; an upgrade module, configured to generate an OTA upgrade task for the target vehicle based on the remaining controller version numbers and send the OTA upgrade task to the target vehicle for OTA upgrade; each vehicle version number corresponds to at least one controller version number, and the step of generating the OTA upgrade task for the target vehicle based on the remaining controller version numbers includes: classifying the remaining controller version numbers based on the at least one controller version number and the controller type to obtain a classification result; sorting the controller version numbers in the classification result in ascending order to obtain a target queue, where the target queue includes at least one upgrade controller version number of at least one controller type; generating the OTA upgrade task for the target vehicle according to the target queue.

6. The device according to claim 5, characterized in that, the acquisition module is configured to: determine the target vehicle version number of the target vehicle according to the VIN code of the target vehicle.

7. A vehicle OTA upgrade device, characterized in that, includes: a controller; a memory, configured to store one or more programs, and when the one or more programs are executed by the controller, enable the controller to implement the vehicle OTA upgrade method according to any one of claims 1 to 4.

8. A computer-readable storage medium, characterized in that, at least one executable instruction is stored in the storage medium, and when the executable instruction runs on the vehicle OTA upgrade device / equipment, enables the vehicle OTA upgrade device / equipment to perform the operations of the vehicle OTA upgrade method according to any one of claims 1-4.

Images