Methods, devices and platform equipment for remote vehicle software upgrades

Abstract

This application discloses a method, apparatus, and device for remotely upgrading vehicle software, relating to the field of automotive technology. The method includes: obtaining a target software version combination and a current software version combination of electronic control units (ECUs) in an electric vehicle; determining a combination of ECUs to be upgraded based on the target software version combination and the current software version combination; and sending a software upgrade package of the ECUs to be upgraded to the vehicle, enabling the vehicle to upgrade according to the software upgrade package. This application's solution achieves unified management of multiple ECUs in a vehicle that support remote upgrades, improving the user experience.

Description

Technical Field

[0001] This application relates to the field of automotive technology, and in particular to a method, apparatus, and platform for remotely upgrading vehicle software. Background Technology

[0002] To enhance user satisfaction and brand loyalty, vehicle manufacturers have developed remote vehicle upgrade capabilities. These capabilities allow for timely and efficient delivery of new features, improving the user experience. However, with the diversification of these capabilities, the number of controllers involved is increasing, leading to more controllers requiring remote upgrades across the entire vehicle and making software version management more complex. Current software management methods involve upgrading each controller individually, failing to achieve unified upgrade management for all controllers. Summary of the Invention

[0003] The purpose of this application is to provide a method, device, and platform for remote upgrading of vehicle software, thereby solving the problem that the prior art cannot uniformly manage the remote upgrading of ECUs.

[0004] To achieve the above objectives, this application provides a method for remotely upgrading vehicle software, including:

[0005] Obtain the target software version combination and the current software version combination of the electronic control unit (ECU) in the electric vehicle;

[0006] Based on the target software version combination and the current software version combination, determine the ECU combination to be upgraded;

[0007] The software upgrade package of the ECU combination to be upgraded is sent to the vehicle, so that the vehicle can be upgraded according to the software upgrade package.

[0008] Optionally, the ECU combination to be upgraded is determined based on the target software version combination and the current software version combination, including:

[0009] Obtain the first version number of the electric vehicle, where the first version number is the version number of the last software upgrade of the electric vehicle;

[0010] If the current software version combination is consistent with the software version combination corresponding to the first version number, the ECU combination to be upgraded is determined according to the target software version combination and the current software version combination.

[0011] If the current software version combination is inconsistent with the software version combination corresponding to the first version number, indicate whether to enter the hard refresh mode.

[0012] Upon receiving a command to enter the hard flashing mode, the ECU combination to be upgraded is determined based on the target software version combination and the current software version combination.

[0013] Optionally, the ECU combination to be upgraded is determined based on the target software version combination and the current software version combination, including:

[0014] The target software version of each ECU on the electric vehicle is compared with the current software version of the corresponding ECU in the current software version combination;

[0015] The ECU whose target software version is inconsistent with the current software version is identified as an element in the ECU combination to be upgraded.

[0016] Optionally, the method further includes:

[0017] Upon receiving an instruction to enter forced refresh mode, a forced refresh approval request is sent to at least one terminal device;

[0018] Upon receiving a command to enter forced flashing mode, the ECU combination to be upgraded is determined based on the target software version combination and the current software version combination, including:

[0019] Upon receiving feedback from each of the terminal devices agreeing to enter the forced flashing mode, the ECU combination to be upgraded is determined based on the target software version combination and the current software version combination.

[0020] Optionally, the method further includes:

[0021] In the event of a software upgrade failure, the software versions of each ECU on the electric vehicle are updated according to the software version combination corresponding to the first version number.

[0022] This application also provides a vehicle software remote upgrade device, including:

[0023] The acquisition module is used to acquire the target software version combination and the current software version combination of the electronic control unit (ECU) in the electric vehicle;

[0024] The determining module is used to determine the ECU combination to be upgraded based on the target software version combination and the current software version combination;

[0025] The sending module is used to send the software upgrade package of the ECU combination to be upgraded to the vehicle, so that the vehicle can be upgraded according to the software upgrade package.

[0026] Optionally, the determining module includes:

[0027] The acquisition submodule is used to acquire the first version number of the electric vehicle, which is the version number of the last software upgrade of the electric vehicle;

[0028] The first determining submodule is used to determine the ECU combination to be upgraded based on the target software version combination and the current software version combination when the current software version combination is consistent with the software version combination corresponding to the first version number.

[0029] The display submodule is used to display whether to enter the hard refresh mode when the current software version combination is inconsistent with the software version combination corresponding to the first version number.

[0030] The second determining submodule is used to determine the ECU combination to be upgraded based on the target software version combination and the current software version combination when a command to enter the hard flash mode is received.

[0031] Optionally, the device further includes:

[0032] The second sending module is used to send a forced refresh approval request to at least one terminal device upon receiving an instruction to enter the forced refresh mode.

[0033] The second determining submodule is specifically used to determine the ECU combination to be upgraded based on the target software version combination and the current software version combination when receiving feedback from each of the terminal devices agreeing to enter the forced flashing mode.

[0034] This application embodiment also provides a vehicle software remote upgrade platform device, including: a processor, a memory, and a program stored in the memory and executable on the processor. When the program is executed by the processor, it implements the vehicle software remote upgrade method as described above.

[0035] This application embodiment also provides a readable storage medium storing a program, which, when executed by a processor, implements the vehicle software remote upgrade method described above.

[0036] The above-mentioned technical solution of this application has at least the following beneficial effects:

[0037] The vehicle software remote upgrade method of this application embodiment first obtains the target software version combination and the current software version combination of the electronic control units (ECUs) in the electric vehicle; second, based on the target software version combination and the current software version combination, determines the ECU combination to be upgraded; finally, the software upgrade package of the ECU combination to be upgraded is sent to the vehicle, enabling the vehicle to upgrade according to the software upgrade package. In this way, unified management of the software versions of ECUs in the vehicle that support remote upgrades is achieved, ensuring that the software version of each ECU is consistent with the software version provided by the software management party (such as the manufacturer or vehicle OEM), thereby improving the user experience. Attached Figure Description

[0038] Figure 1 This is one of the flowcharts illustrating the remote vehicle software upgrade method according to an embodiment of this application;

[0039] Figure 2 This is a second schematic flowchart of the vehicle software remote upgrade method according to an embodiment of this application;

[0040] Figure 3 This is a schematic diagram of the structure of the vehicle software remote upgrade device according to an embodiment of this application;

[0041] Figure 4 This is a schematic diagram of the structure of a vehicle software remote upgrade platform device according to an embodiment of this application. Detailed Implementation

[0042] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0043] The terms "first," "second," etc., used in the specification and claims of this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such use of data can be interchanged where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein. Furthermore, in the specification and claims, "and / or" indicates at least one of the connected objects, and the character " / " generally indicates that the preceding and following objects are in an "or" relationship.

[0044] The following description, in conjunction with the accompanying drawings, details the vehicle software remote upgrade method, apparatus, and platform equipment provided in this application through specific embodiments and application scenarios.

[0045] like Figure 1The diagram shown is one of the flowcharts illustrating a remote vehicle software upgrade method according to an embodiment of this application. The method includes:

[0046] Step 101: Obtain the target software version combination and the current software version combination of the Electronic Control Unit (ECU) in the electric vehicle;

[0047] It should be noted here that this step involves obtaining a collection of software versions for each ECU on the electric vehicle that supports remote upgrades. In other words, the software version combination (including the target software version combination, the current software version combination, etc.) includes the software versions of multiple ECUs.

[0048] Step 102: Determine the ECU combination to be upgraded based on the target software version combination and the current software version combination;

[0049] Similarly, the ECU combination to be upgraded also includes one or more ECUs.

[0050] Step 103: Send the software upgrade package of the ECU combination to be upgraded to the vehicle, so that the vehicle can be upgraded according to the software upgrade package.

[0051] It should be noted that, specifically, after the vehicle's TBOX requests the upgrade package from the remote flashing platform, the remote flashing platform sends the prepared software upgrade package to the vehicle's TBOX. In this way, the TBOX can complete the remote upgrade according to the vehicle's status and user operation commands.

[0052] The vehicle software remote upgrade method of this application embodiment first obtains the target software version combination and the current software version combination of the electronic control units (ECUs) in the electric vehicle; second, based on the target software version combination and the current software version combination, determines the ECU combination to be upgraded; finally, the software upgrade package of the ECU combination to be upgraded is sent to the vehicle, enabling the vehicle to upgrade according to the software upgrade package. In this way, unified management of the software versions of ECUs in the vehicle that support remote upgrades is achieved, ensuring that the software version of each ECU is consistent with the software version of the software manager (such as the manufacturer or vehicle OEM), thereby improving the user experience.

[0053] As an optional implementation, step 102, based on the target software version combination and the current software version combination, determines the ECU combination to be upgraded, including:

[0054] (1) Obtain the first version number of the electric vehicle, wherein the first version number is the version number of the last software upgrade of the electric vehicle;

[0055] In other words, after each remote upgrade, the vehicle software remote upgrade platform will save the version number of this remote upgrade to facilitate subsequent management of the vehicle's software version.

[0056] (2) If the current software version combination is consistent with the software version combination corresponding to the first version number, determine the ECU combination to be upgraded based on the target software version combination and the current software version combination;

[0057] This step specifically involves comparing each software version in the current software version combination with each software version in the software version combination corresponding to the first version number. If they match, it is determined that the software version combination of the vehicle has not changed since the last remote upgrade. For example, no offline upgrade or ECU replacement was performed, and the vehicle status meets the requirements for remote upgrade.

[0058] (3) If the current software version combination is inconsistent with the software version combination corresponding to the first version number, display whether to enter the hard refresh mode;

[0059] Similarly, if the two are inconsistent, it is determined that the software version combination of the vehicle has changed since the last upgrade. For example, an offline upgrade or ECU replacement was performed. In order to ensure that the vehicle status is the same as the status in the vehicle remote upgrade device, so as to facilitate the management of the vehicle software, it is necessary to confirm with the platform administrator whether to enter the forced flashing mode. The forced flashing mode is the forced flashing mode.

[0060] (4) Upon receiving the instruction to enter the hard flashing mode, determine the ECU combination to be upgraded based on the target software version combination and the current software version combination.

[0061] In other words, when entering the forced flashing mode, the ECU to be upgraded is determined based on the target software version combination and the various software versions in the current software version combination, so as to force flashing of vehicles with changed version combinations, so that the version of the whole vehicle software is consistent with the target software version combination after the remote upgrade is completed.

[0062] As a specific implementation, the ECU combination to be upgraded is determined based on the target software version combination and the current software version combination, including:

[0063] The target software version of each ECU on the electric vehicle is compared with the current software version of the corresponding ECU in the current software version combination;

[0064] The ECU whose target software version is inconsistent with the current software version is identified as an element in the ECU combination to be upgraded.

[0065] In other words, by directly comparing the software versions of the corresponding ECUs in the target software version combination and the vehicle's current software version combination, the ECU with the inconsistent software version can be identified as the ECU to be upgraded.

[0066] Furthermore, as an optional implementation, the method also includes:

[0067] Upon receiving an instruction to enter forced refresh mode, a forced refresh approval request is sent to at least one terminal device;

[0068] In other words, after displaying the request to enter the forced refresh mode, if feedback from the platform administrator is received indicating the need to enter forced refresh mode, a forced refresh request is sent to the terminal device bound to the relevant responsible personnel to determine whether to enter forced refresh mode. This ensures the reliability of the upgrade. The forced refresh approval request can be sent sequentially according to the rank of the responsible personnel: first to the highest-ranking responsible personnel, then to the next highest-ranking, and so on until the last responsible personnel are reached; or, first to the responsible personnel with lower privileges, up to the highest-ranking responsible personnel; or, simultaneously to all relevant responsible personnel until feedback is received from all relevant responsible personnel to determine whether to enter forced refresh mode. This application embodiment does not limit the specific method of sending the forced refresh approval request.

[0069] Based on this, upon receiving a command to enter forced flashing mode, the ECU combination to be upgraded is determined according to the target software version combination and the current software version combination, including:

[0070] Upon receiving feedback from each of the terminal devices agreeing to enter the forced flashing mode, the ECU combination to be upgraded is determined based on the target software version combination and the current software version combination.

[0071] Similarly, in this optional implementation, the ECU combination to be upgraded consists of ECUs whose software version numbers are inconsistent with those in the target software version combination and the current software version combination.

[0072] As an optional implementation, the method further includes:

[0073] In the event of a software upgrade failure, the software versions of each ECU on the electric vehicle are updated according to the software version combination corresponding to the first version number.

[0074] In other words, if a software upgrade fails, the ECU's software version can be rolled back to the software version in the software version combination corresponding to the first version number.

[0075] It should be noted that if the software upgrade fails, the ECU software version can also be rolled back to the software version in the current software version combination.

[0076] Below, in conjunction with Figure 2 The specific implementation of the vehicle software remote upgrade method according to the embodiments of this application will be described below:

[0077] It should be noted that the term "major version" refers to a combination of software versions; and the term "remote flashing platform" can refer to the vehicle software remote upgrade platform device in this application embodiment.

[0078] 1) Major version generation

[0079] Each ECU software version number in a major version is a fixed combination and is managed uniformly by the software repository. If the software number of any one or more ECUs in a major version changes, the major version number must also be changed, as shown in Table 1 below.

[0080]

[0081] Table 1

[0082] 2) Create a task

[0083] The remote flashing platform retrieves major versions from the software repository. Each time an upgrade task is created, it needs to determine the target major version (target software version combination) and the base major version (software version combination corresponding to the first version number). The base major version is the current software state of the vehicle. If the upgrade to the target major version fails, the vehicle can be restored to its original state based on the base major version to ensure that the vehicle can be used normally. In short, the target major version is the software state that the vehicle controller should reach after the upgrade task is successful.

[0084] 3) Upgrade package download

[0085] After the task is created but before the upgrade package is downloaded, the remote flashing platform needs to verify the base major version, the target major version, and the vehicle's current component information. Only if the component information is obtained and correct can the remote upgrade process continue. The verification consists of two steps:

[0086] The first step is to verify that the base major version ECU version number matches the vehicle's current ECU version number. For example, if V1.0 is the base major version and all ECUs are S1, then all corresponding ECUs on the vehicle should also be S1; otherwise, the verification will fail. It's important to note that due to the diverse conditions of vehicles in the market, the vehicle's current ECU version number may not fall within the fixed combination range of major versions, resulting in inconsistencies with the base major version ECU version number. This can lead to verification failure and unsuccessful remote upgrades. To improve the upgrade success rate, the platform should not directly determine that the upgrade is impossible. Instead, it should display the problematic ECU part number and software version number to the platform administrators and provide an option to enter the forced flashing mode. If the user does not enter, the verification fails, and the task ends. If the user confirms entry into forced flashing mode, the platform should automatically initiate an approval process with multiple confirmation steps. Only after approval can the task begin.

[0087] The second step is that the remote flashing platform will automatically compare which ECU has changed between the two major versions, and then create an upgrade package for the changed ECU software and download it to the TBOX. For example, if V2.0 is the target major version, and ECU3 has changed compared to V1.0, the flashing platform will only create an upgrade package for ECU3 and then download this upgrade package to the TBOX.

[0088] For the forced flashing mode adopted after the first step of the test fails, the flashing platform will compare the versions of each ECU in the target major version with the current ECU version of the vehicle, and create an upgrade package for the ECUs with inconsistent version numbers together and then download it to TBOX to upgrade.

[0089] 4) Upgrade package update

[0090] After downloading the upgrade package, TBOX will push upgrade reminder information to the user via mobile phone or vehicle screen. TBOX will then complete the remote upgrade based on the vehicle status and user operation instructions.

[0091] Based on the above description, the implementation process of remote vehicle software upgrade in this application embodiment follows the steps below:

[0092] 1) The software repository performs major version creation, that is, the software repository creates a combination of target software versions;

[0093] 2) Remote flashing platform creates tasks, that is, the remote flashing platform creates remote upgrade tasks;

[0094] 3) The remote flashing platform verifies the basic major version and the vehicle end, that is, the remote flashing platform verifies the software version combination corresponding to the first version number with the current software version combination;

[0095] 4) If the verification passes, the remote flashing platform verifies the target major version and the base major version; that is, the remote flashing platform verifies the software version combination corresponding to the first version number and the target software version combination to determine the ECU with inconsistent version numbers. Of course, at this time the base major version is consistent with the vehicle major version, so it can also be understood as the target major version and the vehicle major version being verified.

[0096] 5) If the verification fails, the system will display the failed ECU information and ask whether to enter forced mode. In other words, the remote flashing platform will display the ECU parts and software version number that failed the verification to the platform administrator and provide an option to enter forced flashing mode.

[0097] If the platform administrator confirms the entry into the forced flashing mode, the remote flashing platform will automatically initiate an approval process with multiple confirmation steps. Only after the approval is passed can the task begin. That is, when the platform administrator confirms the entry into the forced flashing mode, a forced flashing approval request will be sent to at least one terminal device, and the forced flashing mode will be confirmed upon receiving consent from each terminal device.

[0098] 7) After entering the hard flashing mode, the target major version is verified, that is, the target major version is verified with the current version of the vehicle to obtain ECUs with inconsistent version numbers.

[0099] 8) Upgrade package creation, that is, creating upgrade packages based on ECUs with different version numbers;

[0100] 9) Upgrade package download, that is, the vehicle downloads the upgrade package from the remote flashing platform;

[0101] 10) Upgrade, that is, the vehicle undergoes a software upgrade.

[0102] The vehicle software remote upgrade method in this application defines the vehicle software version, enabling remote upgrades to be performed on a vehicle-wide basis, facilitating software version management. For situations where the version combination changes after a remote upgrade, such as offline upgrades or ECU replacements, this application provides a forced flashing mode. This allows vehicles with non-standard software versions to complete functional iterations through remote upgrades, standardizes the software status of vehicles in the market, improves the success rate of upgrades, and facilitates timely software problem fixing. It also reduces the number of times users need to visit 4S stores for program updates, thus saving on after-sales maintenance costs to some extent.

[0103] like Figure 3 The diagram shown is a structural schematic of a vehicle software remote upgrade device according to an embodiment of this application. The vehicle software remote upgrade device includes:

[0104] The acquisition module 301 is used to acquire the target software version combination and the current software version combination of the electronic control unit (ECU) on the electric vehicle.

[0105] The determining module 302 is used to determine the ECU combination to be upgraded based on the target software version combination and the current software version combination;

[0106] The sending module 303 is used to send the software upgrade package of the ECU combination to be upgraded to the vehicle, so that the vehicle can be upgraded according to the software upgrade package.

[0107] The vehicle software remote upgrade device of this application embodiment firstly acquires the target software version combination and the current software version combination of the electronic control units (ECUs) in the electric vehicle using an acquisition module 301; secondly, a determining module 302 determines the ECU combination to be upgraded based on the target software version combination and the current software version combination; finally, a sending module 303 sends the prepared software upgrade package of the ECU combination to be upgraded to the vehicle, enabling the vehicle to upgrade according to the software upgrade package. In this way, unified management of the software versions of ECUs in the vehicle that support remote upgrades is achieved, ensuring that the software version of each ECU is consistent with the software version provided by the software management party (such as the manufacturer or vehicle OEM), thereby improving the user experience.

[0108] Optionally, the determining module 302 includes:

[0109] The acquisition submodule is used to acquire the first version number of the electric vehicle, which is the version number of the last software upgrade of the electric vehicle;

[0110] The first determining submodule is used to determine the ECU combination to be upgraded based on the target software version combination and the current software version combination when the current software version combination is consistent with the software version combination corresponding to the first version number.

[0111] The display submodule is used to display whether to enter the hard refresh mode when the current software version combination is inconsistent with the software version combination corresponding to the first version number.

[0112] The second determining submodule is used to determine the ECU combination to be upgraded based on the target software version combination and the current software version combination when a command to enter the hard flash mode is received.

[0113] Optionally, the determining module 302 or the first determining submodule is specifically used for:

[0114] The target software version of each ECU on the electric vehicle is compared with the current software version of the corresponding ECU in the current software version combination;

[0115] The ECU whose target software version is inconsistent with the current software version is identified as an element in the ECU combination to be upgraded.

[0116] Furthermore, the device also includes:

[0117] The second sending module is used to send a forced refresh approval request to at least one terminal device upon receiving an instruction to enter the forced refresh mode.

[0118] The second determining submodule is specifically used to determine the ECU combination to be upgraded based on the target software version combination and the current software version combination when receiving feedback from each of the terminal devices agreeing to enter the forced flashing mode.

[0119] Optionally, the device further includes:

[0120] The update module is used to update the software version of each ECU on the electric vehicle according to the software version combination corresponding to the first version number in the event of a software upgrade failure.

[0121] This application embodiment also provides a vehicle software remote upgrade platform device, including: a processor 400, a memory 420, and a program stored in the memory 420 and executable on the processor 400. When the program is executed by the processor, it implements the various processes of the vehicle software remote upgrade method embodiment described above and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0122] The transceiver 4310 is used to receive and send data under the control of the processor 400.

[0123] Among them, Figure 4 In this context, the bus architecture can include any number of interconnected buses and bridges, specifically linking various circuits of one or more processors represented by processor 400 and memory represented by memory 420. The bus architecture can also link various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further herein. The bus interface provides an interface. Transceiver 410 can be multiple elements, including transmitters and receivers, providing a unit for communicating with various other devices over a transmission medium. For different user equipment, user interface 430 can also be an interface capable of connecting external or internal devices, including but not limited to keypads, displays, speakers, microphones, joysticks, etc.

[0124] The processor 400 is responsible for managing the bus architecture and general processing, while the memory 420 can store the data used by the processor 400 when performing operations.

[0125] This application also provides a readable storage medium storing a program. When executed by a processor, this program implements the various processes of the vehicle software remote upgrade method embodiment described above, and achieves the same technical effect. To avoid repetition, it will not be described again here. The readable storage medium may be a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, etc.

[0126] Finally, it should be noted that in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or terminal apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0127] The above description is the preferred embodiment of this application. It should be noted that for those skilled in the art, several improvements and modifications can be made without departing from the principles described in this application, and these improvements and modifications should also be considered within the scope of protection of this application.

Claims

1. A vehicle software remote upgrading method, characterized in that, The method comprises the following steps: obtaining a target software version combination and a current software version combination of electronic control units (ECUs) on an electric vehicle; determining an ECU combination to be upgraded according to the target software version combination and the current software version combination; sending a software upgrade package of the ECU combination to be upgraded to the vehicle, so that the vehicle is upgraded according to the software upgrade package; wherein the step of determining the ECU combination to be upgraded according to the target software version combination and the current software version combination comprises the following steps: obtaining a first version number of the electric vehicle, the first version number being a version number of the last software upgrade of the electric vehicle; verifying a software version combination corresponding to the first version number and the current software version combination; in the case where the current software version combination is consistent with the software version combination corresponding to the first version number, determining the ECU combination to be upgraded according to the target software version combination and the current software version combination; in the case where the current software version combination is inconsistent with the software version combination corresponding to the first version number, displaying whether to enter a forced flashing mode; wherein the forced flashing mode is a forced flashing mode; in the case where an instruction to enter the forced flashing mode is received, determining the ECU combination to be upgraded according to the target software version combination and the current software version combination; the method further comprises the following steps: in the case where the instruction to enter the forced flashing mode is received, sending a forced flashing approval request to at least one terminal device; the step of determining the ECU combination to be upgraded according to the target software version combination and the current software version combination in the case where the instruction to enter the forced flashing mode is received comprises the following step: in the case where the terminal device feedbacks an instruction to enter the forced flashing mode, determining the ECU combination to be upgraded according to the target software version combination and the current software version combination.

2. The method of claim 1, wherein, the step of determining the ECU combination to be upgraded according to the target software version combination and the current software version combination comprises the following steps: respectively comparing a target software version of each ECU on the electric vehicle with a current software version of a corresponding ECU in the current software version combination; determining an ECU whose target software version is inconsistent with the current software version as an element in the ECU combination to be upgraded.

3. The method of claim 1, wherein, the method further comprises the following step: in the case where the software upgrade fails, updating the software version of each ECU on the electric vehicle according to the software version combination corresponding to the first version number.

4. A vehicle software remote upgrading device, characterized in that, The method comprises the following steps: an obtaining module, configured to obtain a target software version combination and a current software version combination of electronic control units (ECUs) on an electric vehicle; a determining module, configured to determine an ECU combination to be upgraded according to the target software version combination and the current software version combination; a sending module, configured to send a software upgrade package of the ECU combination to be upgraded to the vehicle, so that the vehicle is upgraded according to the software upgrade package; wherein the determining module comprises the following steps: The acquisition sub-module is configured to acquire a first version number of the electric vehicle, the first version number being a version number of a last software upgrade of the electric vehicle, and to verify a software version combination corresponding to the first version number against the current software version combination; The first determination sub-module is configured to, in a case where the current software version combination is consistent with the software version combination corresponding to the first version number, determine a to-be-upgraded ECU combination according to the target software version combination and the current software version combination; The display sub-module is configured to, in a case where the current software version combination is inconsistent with the software version combination corresponding to the first version number, display whether to enter a forced flashing mode, wherein the forced flashing mode is a forced flashing mode; The second determination sub-module is configured to, in a case where an entering forced flashing mode instruction is received, determine a to-be-upgraded ECU combination according to the target software version combination and the current software version combination. The apparatus further includes: The second sending module is configured to, in a case where an entering forced flashing mode instruction is received, send a forced flashing approval request to at least one terminal device. The second determination sub-module is specifically configured to, in a case where each terminal device feeds back an instruction to enter the forced flashing mode, determine a to-be-upgraded ECU combination according to the target software version combination and the current software version combination.

5. A vehicle software remote upgrade platform device, characterized in that, A processor, a memory, and a program stored in the memory and executable on the processor, the program being executed by the processor to implement the whole-vehicle software remote upgrade method according to any one of claims 1 to 3. The readable storage medium stores a program, the program being executed by the processor to implement the whole-vehicle software remote upgrade method according to any one of claims 1 to 3.

6. A readable storage medium characterized by, ​

Images