Vehicle software upgrading method and system, electronic equipment and storage medium

Abstract

The embodiment of the invention provides a vehicle software upgrading method and system, electronic equipment and a storage medium, and the method comprises the steps: receiving a query request from a power conversion end, the query request being sent by the power conversion end in response to a received power conversion request; and in response to the query request, sending an upgradable software version list of the battery management system of the stock battery pack in the battery swap station to the battery swap end, so that the battery swap end checks and updates the battery management system of the target battery pack in the battery swap station according to the software version list and the battery swap request, enabling the battery management system of the target battery pack to be a first software version; and after the target battery pack is installed on the vehicle, receiving an updating request from the battery changing end, and performing software checking and updating on a vehicle control unit of the vehicle according to the updating request. According to the scheme, the problem of software checking update failure of the vehicle control unit caused by frequent battery replacement of the vehicle can be avoided, and the user experience is improved.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of intelligent connected vehicle technology, and in particular, to a vehicle software upgrade method, system, electronic device, and storage medium. Background Art

[0002] New energy vehicles widely use OAT (Over-The-Air) technology to upgrade and manage the vehicle's ECU (Electronic Control Unit), including the vehicle's BMS (Battery Management System).

[0003] In the battery swap scenario, the vehicle needs to update the battery management system software. Since the batteries at the battery swap stations are differentiated by type and capacity, the battery management system software corresponding to the same hardware model batteries often has multiple iterative versions. Therefore, the versions of the battery management system software flashed at different battery swap stations for the same vehicle will change frequently.

[0004] The battery management system software version flashed by the vehicle during the battery replacement process may be incompatible with the BMS software version in the OTA upgrade task, resulting in problems such as vehicle OTA upgrade failure. Summary of the invention

[0005] In view of this, embodiments of the present application provide a vehicle software upgrade method, system, electronic device and storage medium to at least partially solve the above-mentioned problems.

[0006] According to a first aspect of an embodiment of the present application, a vehicle software upgrade method is provided, which is applied to a service end, and includes: receiving a query request from a battery swap end, the query request being sent by the battery swap end in response to a received battery swap request; in response to the query request, sending a list of upgradeable software versions of the battery management system of the existing battery packs in the battery swap station to the battery swap end, so that the battery swap end checks and updates the battery management system of the target battery pack in the battery swap station according to the list of upgradeable software versions and the battery swap request, so that the battery management system of the target battery pack is a first software version; after the target battery pack is installed on the vehicle, receiving an update request from the battery swap end, and performing a software check and update on the vehicle control unit of the vehicle according to the update request.

[0007] According to a second aspect of an embodiment of the present application, a vehicle software upgrade method is provided, which is applied to a battery swapping end, and includes: sending a query request to a server in response to a received battery swapping request; receiving a list of upgradeable software versions of the battery management system of the existing battery packs in the battery swapping station sent by the server according to the query request; checking and updating the battery management system of the target battery pack in the battery swapping station according to the battery swapping request and the list of upgradeable software versions, so that the battery management system of the target battery pack is a first software version; sending an update request to the server according to the capacity of the target battery pack and the first software version, so that the server checks and updates the software of the vehicle control unit of the vehicle according to the update request.

[0008] According to the third aspect of an embodiment of the present application, a vehicle software upgrade system is provided, comprising a battery swap request end, a battery swap end, a server and a vehicle; the battery swap request end is used to send a battery swap request to the battery swap end; the server end is used to execute any of the above-mentioned vehicle software upgrade methods; the battery swap end is used to execute any of the above-mentioned vehicle software upgrade methods.

[0009] According to the fourth aspect of an embodiment of the present application, an electronic device is provided, comprising: a processor, a memory, a communication interface and a communication bus, wherein the processor, the memory and the communication interface communicate with each other through the communication bus; the memory is used to store at least one executable instruction, and the executable instruction enables the processor to perform an operation corresponding to any one of the vehicle software upgrade methods described above.

[0010] According to a fifth aspect of an embodiment of the present application, a computer storage medium is provided, on which a computer program is stored, and when the program is executed by a processor, any of the above-mentioned vehicle software upgrade methods is implemented.

[0011] According to a sixth aspect of an embodiment of the present application, a computer program product is provided, comprising computer instructions, wherein the computer instructions instruct a computer device to perform operations corresponding to any of the above-described vehicle software upgrade methods.

[0012] According to the vehicle software upgrade method provided in each embodiment of the present application, the server receives a query request from the battery swapping end, and in response to the query request, sends a list of upgradeable software of the battery management system of the existing battery pack in the battery swapping station to the battery swapping end, so that the battery management system of the target battery pack in the battery swapping station can be checked and updated based on the list of upgradeable versions provided by the server, so that the battery management system of the target battery pack is the first software version; and the vehicle is swapped based on the target battery pack and the first software version, which can ensure that the software version of the battery management system of the vehicle after frequent battery swaps is consistent with the software version under the whole vehicle baseline in the server, avoiding frequent changes and flashing of software versions during vehicle battery swaps. This can prevent the software version of the battery management system of the vehicle from being inconsistent with the software version in the vehicle baseline, resulting in difficulties in vehicle baseline management. At the same time, it can also ensure that the software version of the battery management system of the vehicle after frequent battery replacement is incompatible with the software version in the software upgrade task released by the server according to the software version of the vehicle baseline, resulting in the problem that the software version of the vehicle cannot be successfully upgraded after frequent battery replacement; after the target battery pack is installed on the vehicle, through the communication between the battery replacement end and the server end, the server end can receive the update request from the battery replacement end, and perform software inspection and update on the vehicle control unit of the vehicle according to the update request, ensuring the normal upgrade and update of the vehicle's software version after the battery replacement is completed, thereby improving the user experience. BRIEF DESCRIPTION OF THE DRAWINGS

[0013] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in the embodiments of the present application. For ordinary technicians in this field, other drawings can also be obtained based on these drawings.

[0014] Figure 1 is a flow chart of a vehicle software upgrade method according to an embodiment of the present application;

[0015] Figure 2 is another flow chart of a vehicle software upgrade method according to an embodiment of the present application;

[0016] Figure 3 is a schematic diagram of a vehicle software upgrade system according to an embodiment of the present application;

[0017] Figure 4 It is a schematic diagram of an electronic device according to an embodiment of the present application. DETAILED DESCRIPTION

[0018] Vehicle software upgrade method

[0019] An embodiment of the present application provides a vehicle software upgrade method, through which it can be ensured that the update of the battery software version during the battery replacement of the vehicle will not affect the software version update during the OTA upgrade.

[0020] Figure 1 1 is a flow chart of a vehicle software upgrade method according to an embodiment of the present application. The vehicle software upgrade method according to this embodiment is applied to a server. In some embodiments, the server may be an OTA operation management system.

[0021] like Figure 1 As shown, the vehicle software upgrade method of this embodiment includes the following steps:

[0022] Step 101: Receive a query request from the battery swap terminal.

[0023] In some embodiments, the server may store the software version data of each vehicle under the vehicle baseline, and these data are synchronously acquired from the vehicle manufacturer's GBOM (Generic Bill of Material) system.

[0024] In some embodiments, a software upgrade task can be issued to the vehicle through the server. Generally, iterative upgrades can be performed based on the vehicle baseline version corresponding to the last software upgrade task of the vehicle, and a new target vehicle baseline version corresponding to the vehicle can be created on the server. The iteratively upgraded software upgrade task corresponding to the new target vehicle baseline version of the vehicle, such as the ECU part module to be upgraded, can be added to the software upgrade task on the server by the operator. Among them, when adding a software upgrade task, the source baseline version and the target baseline version corresponding to the software upgrade task can be selected. The source baseline version can be selected in multiple ways and can be selected across baselines, that is, it can be selected from the previous baseline version. The target baseline version is the newly created target vehicle baseline version, so the software upgrade task can support vehicle cross-baseline upgrades; the validity period of the upgrade task, the preconditions of the upgrade task and other configuration parameters can also be set; the software range list corresponding to the upgrade task can also be selected, such as the software range list of the ECU part module to be upgraded; and the vehicle corresponding to the software upgrade task can also be added. After the software upgrade task is created, the software upgrade task can be released, and an upgrade check and update request is sent to all vehicles added to the software upgrade task, and the vehicle performs a synchronous update of the software upgrade task.

[0025] In some embodiments, if the vehicle has a battery replacement task when it receives a software upgrade task from the service end, and has sent a battery replacement request to the battery replacement end based on the battery replacement reservation end, the service end may receive a query request from the battery replacement end. Among them, the battery replacement request may include at least information such as the battery replacement station, battery model, vehicle information, and the physical identification of the battery management system in the vehicle; the query request may be sent by the battery replacement end in response to the received battery replacement request. For example, the battery replacement end may determine the hardware number of the existing battery pack corresponding to the battery replacement request based on the battery replacement request, and send a query request to the server based on the hardware number of the existing battery pack to query the list of upgradeable software versions of the battery management system corresponding to the hardware number of the existing battery pack;

[0026] Step 102, in response to the query request, sends the list of upgradeable software versions of the battery management system of the existing battery packs in the battery swap station to the battery swap end, so that the battery swap end checks and updates the battery management system of the target battery pack in the battery swap station according to the list of upgradeable software versions and the battery swap request, so that the battery management system of the target battery pack is the first software version.

[0027] In some embodiments, the server can respond to the query request, obtain the data verification information determined by the battery swap end according to the battery swap request, and perform data verification on the data verification information.

[0028] Among them, the data verification information may include at least one of the unique identification of the vehicle, the battery model corresponding to the battery replacement request of the vehicle, the physical identification of the battery management system in the vehicle, the hardware number of the existing battery pack in the battery replacement station, and the identification of the software module to be flashed in the battery management system. Among them, the unique identification of the vehicle can be used to indicate the vehicle corresponding to the identification, the physical identification of the battery management system can indicate the battery management system in the vehicle, the hardware number of the existing battery pack can be used to indicate the existing battery in the battery replacement station, and the identification of the software module to be flashed in the battery management system is used to indicate the software module that the battery management system needs to re-flash when the vehicle is replaced; data verification may include format verification, integrity verification, etc. For example, format verification can be performed by checking whether the format of the data verification information meets expectations, and integrity verification can be performed by checking whether the necessary fields of the data verification information exist.

[0029] In some embodiments, if the data verification passes, after receiving the hardware number of the stock battery at the battery swap station, the server can further obtain the software package data of the battery management system of the vehicle under the whole vehicle baseline. The whole vehicle baseline can include all ECU firmware data of the whole vehicle, that is, the software package data in the vehicle control unit, and the ECU firmware contains the software of the battery management system; the software package data of the battery management system can include the collection of all software package data under the battery management system in the whole vehicle baseline, and the software package data can include part number, version number, function description, software compatibility information, hardware compatibility information, and dependencies with other software or libraries.

[0030] In some embodiments, the server may obtain the battery capacity corresponding to the hardware number of each existing battery pack, and filter the first software package data of the battery management system that matches the battery capacity from the software package data.

[0031] After obtaining the first software package data, the server can filter out software package data from the first software package data that is both hardware-compatible and software-compatible with the battery management system currently used by the vehicle and whose version number is greater than or equal to the version number corresponding to the software package of the battery management system currently used by the vehicle, and determine the filtered software package as the second software package.

[0032] The server can sort the software packages in the second software package in descending order based on the version number, and filter out and combine the part number and version number of each software package according to the part number and version number of each software package in the sorted second software package to obtain an upgradeable software version list. The part number is a hardware number with a preset number of digits, such as 10 digits, which can be used to uniquely identify the software package, and the version number is used to indicate the version of the software package. The larger the version number, the higher the version of the software package.

[0033] In some embodiments, after obtaining the list of upgradeable software versions corresponding to the vehicle, the server can send the vehicle's unique identifier, the list of upgradeable software versions corresponding to the hardware number of each existing battery pack, the vehicle's current battery software version, and the server's calculation status code and description information to the battery swap terminal. Among them, the server's calculation status code is used to indicate the server's calculation success status, failure status, and processing status of the first battery version list, and the description information is used to calculate the explanation information and additional information corresponding to the status code, such as the first battery version list has been sent, unable to connect to the database, the vehicle identification code is invalid, the request is being processed, and it is expected to be completed in 10 minutes.

[0034] Step 103: After the target battery pack is installed on the vehicle, an update request is received from the battery replacement end, and the vehicle control unit of the vehicle is checked and updated for software according to the update request.

[0035] In some embodiments, after the target battery pack is installed on the vehicle, the server receives an update request from the battery swap station, and determines the first capacity and first software version of the target battery pack of the vehicle after the battery swap based on the update request, and performs a software check and update on the vehicle control unit of the vehicle according to the first capacity and first software version of the target battery pack.

[0036] The server can obtain the target battery capacity and target software version of the battery management system in the software upgrade task of the vehicle. If the first capacity is the same as the target battery capacity, and the first software version is the same as the target software version, the software in the software upgrade task of the vehicle except for the target battery pack of the battery management system is checked and updated; if the first capacity is different from the target battery capacity, or the first version is lower than the target software version, the vehicle control unit is checked and updated based on the software update task of the vehicle.

[0037] In this embodiment, a communication mechanism is established between the battery swapping end and the server end, so that the first software version of the target battery pack of the vehicle when the battery is swapped at the battery swapping station is obtained from the upgradeable software version list provided by the server end. Since each data in the upgradeable software version list fed back by the server end is sorted based on the size of the version number, it is ensured that the vehicle will preferentially select the higher version of the software for battery swapping when swapping the battery. At the same time, the embodiment of the present application can also ensure that the target battery pack of the vehicle after each battery swap is compatible with the software version in the server end, so that the frequent battery cycles of the vehicle will not damage the software baseline of the entire vehicle, and avoid the problem of the server end failing to perform software upgrades on the vehicle control unit of the vehicle due to frequent battery swaps, thereby improving the user experience.

[0038] Vehicle software upgrade method

[0039] An embodiment of the present application provides a vehicle software upgrade method, through which the battery software version of the vehicle can be determined by the server when the battery is replaced, thereby avoiding incompatibility issues with the baseline software version of the vehicle in the server due to battery replacement, and avoiding the problem of failure of software upgrade tasks of the vehicle control unit issued by the server due to frequent battery replacement.

[0040] Figure 2 1 is a flow chart of a vehicle software upgrade method according to an embodiment of the present application. The vehicle software upgrade method according to this embodiment is applied to a battery swap terminal. In some embodiments, the battery swap terminal may be a battery swap station or a battery swap operation management system.

[0041] like Figure 2 As shown, the vehicle software upgrade method of this embodiment includes the following steps:

[0042] Step 201: In response to the received battery replacement request, a query request is sent to the server.

[0043] In some embodiments, before the vehicle replaces its battery, the user can send a battery replacement request for the vehicle to the battery replacement cloud management system through an APP (Application) or HMI (Human Machine Interface). The battery replacement request may include at least vehicle information, battery model, battery replacement site, physical identification of the battery in the vehicle and other information.

[0044] In some embodiments, the battery swap terminal can receive a battery swap request for a vehicle, and determine the data verification information of the vehicle based on the battery swap request. The data verification information may include at least one of the vehicle's unique identifier, the battery model of the battery swap request, the physical identifier of the battery management system in the vehicle, the hardware number of the stock battery pack in the battery swap station, and the identifier of the software module to be flashed in the battery management system. Among them, the battery swap station can determine the battery capacity based on the battery model, and query the inventory for the hardware number of the stock battery pack that matches the battery capacity. Based on the data verification information, the battery swap terminal can send a query request to the server to query the list of upgradeable software versions corresponding to the hardware number of each stock battery pack in the battery management system under the vehicle baseline of the vehicle corresponding to the unique identifier.

[0045] Step 202: Receive a list of upgradeable software versions of the battery management system of the existing battery packs in the battery swap station sent by the server in response to a query request.

[0046] In some embodiments, the battery swap station can receive a list of upgradeable software versions of the battery management system of the stock battery packs in the battery swap station sent by the service end according to the query request. Each stock battery pack corresponds to an upgradeable software version list, and each data in each upgradeable version list includes the part number and version number corresponding to each software package, and each data is arranged in order from large to small based on the version number. The part number can uniquely identify the software package, and the version number is used to indicate the version of the software package. The larger the version number, the higher the version of the software package.

[0047] Step 203: According to the battery replacement request and the list of upgradeable software versions, the battery management system of the target battery pack in the battery replacement station is checked and updated so that the battery management system of the target battery pack is the first software version.

[0048] In some embodiments, the battery swap terminal can have a list of upgradeable software versions corresponding to each existing battery, and for each software package in the list of upgradeable software versions, order the part number of the software package in the list from large to small based on the version number of the software package, and query in sequence whether there is a software package corresponding to the part number in the battery swap station. If a software package corresponding to the part number exists in the battery swap station, the query is stopped, and a candidate battery pack corresponding to the part number in the battery swap station is determined based on the queried part number, and the candidate battery pack is determined as the candidate software package corresponding to the battery management system of the existing battery pack.

[0049] After obtaining the candidate software packages corresponding to the battery management system of each stock battery pack, the target battery pack and the first battery version can be determined from the battery management systems of all stock batteries and the candidate software packages corresponding to the battery management system of each stock battery pack. Among them, the battery swap station can determine the target battery pack from all stock battery packs based on a preset selection strategy. As an example, the stock battery pack with the highest battery life, such as the highest battery capacity, can be determined as the target battery pack; or the stock battery pack with the highest battery performance, such as the strongest fast charging capability, can be determined as the target battery pack; or the stock battery pack with the highest version, that is, the latest release, can be determined as the target battery pack; or the stock battery pack with the lowest price can be determined as the target battery pack; or based on a comprehensive analysis of battery life, battery performance, version number size and price, the stock battery pack with the highest cost performance after comprehensive analysis can be determined as the target battery pack. After obtaining the target battery pack, the version number of the candidate software package corresponding to the target battery pack can be determined as the first battery version.

[0050] In some embodiments, the battery swap end can check and update the battery management system of the target battery pack in the battery swap station, that is, perform a battery swap pre-flash operation on the software module to be flashed in the battery swap management system of the target battery pack based on the first battery version, so that the version number of the software package in the battery management system of the target battery pack is the first software version.

[0051] Step 204: Send an update request to the server according to the capacity of the target battery pack and the first software version, so that the server checks and updates the software of the vehicle control unit of the vehicle according to the update request.

[0052] In some embodiments, after the vehicle arrives at the battery swap station, the battery swap station can perform a battery swap on the vehicle based on the target battery pack and the first software version. Because the battery swap management system software module to be flashed for the target battery pack has been pre-flashed based on the first battery version before the vehicle arrives at the station, the target battery pack to which the software module to be flashed in the battery management system has been flashed can be directly used to perform a battery swap on the vehicle. After the vehicle completes the battery swap, an update request can be sent to the server so that the server checks and updates the software of the vehicle control unit of the vehicle according to the update request.

[0053] In this embodiment, through the information exchange between the battery swapping end and the server end, the battery swapping end can determine the first software version of the battery management system of the target battery pack to be replaced according to the list of upgradeable software determined by the server end when replacing the battery of the vehicle. Even if the battery is replaced frequently, the compatibility of the software versions in the battery swapping end and the server end can be maintained, and the maintenance work of the baseline of the entire vehicle on the server end will not be disrupted. At the same time, the problem of failure of the server software upgrade task caused by frequent battery replacement is avoided, thereby improving the user experience.

[0054] Vehicle software upgrade system

[0055] Corresponding to the above vehicle software upgrade method embodiment, Figure 3 A schematic diagram of a vehicle software upgrade system according to an embodiment of the present application is shown. Figure 3 As shown, the vehicle upgrade system supporting battery swapping includes a battery swapping request terminal, a battery swapping terminal, a service terminal and a vehicle.

[0056] The battery swap request end is used to send a battery swap request to the battery swap end.

[0057] In some embodiments, the battery swap request end may be an APP (Application) or HMI (Human Machine Interface), etc. A user may reserve a battery swap request for at least one vehicle through the battery swap request end. The battery swap request may include information such as a battery swap station, battery information, vehicle information, and a physical identifier of the battery management system in the vehicle. At the same time, there is also at least one battery swap request end, and the same battery swap end can handle battery swap requests from multiple battery swap request ends.

[0058] The battery swapping terminal is used to respond to the battery swapping request and send a query request to the server. After receiving the list of upgradeable software versions of the battery management of the existing battery packs in the battery swapping station sent by the server according to the query request, the battery management system of the target battery pack in the battery swapping station is checked and updated based on the battery swapping request and the list of upgradeable versions, and the battery management system of the target battery pack in the battery swapping station is pre-flashed to make the battery management system of the target battery pack a first software version; after the vehicle completes the battery swapping at the battery swapping station, an update request is sent to the server according to the target battery pack after the battery swapping and the first software version of the battery management system of the target battery pack, so that the server checks and updates the software of the vehicle control unit of the vehicle according to the update request.

[0059] The service end is used to respond to the query request of the battery swap end and send the upgradeable software list of the battery management system of the existing battery packs in the battery swap station to the battery swap end, so that the battery swap end can check and update the battery management system of the target battery pack in the battery swap station according to the upgradeable software version list and the battery swap request, so that the battery management system of the target battery pack is the first software version; after the target battery pack is installed on the vehicle, the service end receives the update request from the battery swap end, and checks and updates the software of the vehicle control unit of the vehicle according to the update request.

[0060] It should be noted that the vehicle software upgrade system of this embodiment is used to implement the corresponding vehicle software upgrade method in the aforementioned method embodiment, and has the beneficial effects of the corresponding method embodiment, which will not be repeated here.

[0061] The method of the embodiment of the present application can effectively ensure the consistency of the vehicle battery management system software version between the two systems by opening up the data flow between the battery replacement end and the service end, ensure that the target battery pack after each battery replacement of the vehicle is compatible with the software version in the server end, and realize that frequent battery replacement of the vehicle will not damage the software baseline of the entire vehicle, thereby improving the user experience.

[0062] Electronic devices

[0063] Figure 4 A schematic diagram of the structure of an electronic device according to an embodiment of the present application is shown. The specific embodiment of the present application does not limit the specific implementation of the electronic device.

[0064] like Figure 4 As shown, the electronic device may include: a processor (processor) 402 , a communication interface (Communications Interface) 404 , a memory (memory) 406 , and a communication bus 408 .

[0065] in:

[0066] The processor 402 , the communication interface 404 , and the memory 406 communicate with each other via a communication bus 408 .

[0067] The communication interface 404 is used to communicate with other electronic devices or servers.

[0068] The processor 402 is used to execute the program 410, and specifically can execute the relevant steps in the above-mentioned vehicle software upgrade method embodiment.

[0069] Specifically, the program 410 may include program codes, which include computer operation instructions.

[0070] The processor 402 may be a central processing unit (CPU), or an application-specific integrated circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of the present application. The one or more processors included in the smart device may be processors of the same type, such as one or more CPUs; or processors of different types, such as one or more CPUs and one or more ASICs.

[0071] The memory 406 is used to store the program 410. The memory 406 may include a high-speed RAM memory, and may also include a non-volatile memory (non-volatile memory), such as at least one disk memory.

[0072] The program 410 may be specifically configured to enable the processor 402 to perform the following operations:

[0073] In an optional implementation, the program 410 is also used to enable the processor 402 to implement each step in the program 410. The specific implementation can refer to the corresponding steps and corresponding descriptions of the device in the above vehicle software upgrade method embodiment, which will not be repeated here. Those skilled in the art can clearly understand that for the convenience and simplicity of description, the specific working process of the above described device and module can refer to the corresponding process description in the above method embodiment, which will not be repeated here.

[0074] Computer program product

[0075] An embodiment of the present application also provides a computer program product, including computer instructions, which instruct a computing device to execute operations corresponding to any vehicle software upgrade method in the above-mentioned multiple method embodiments.

[0076] It should be pointed out that, according to the needs of implementation, the various components / steps described in the embodiments of the present application can be split into more components / steps, or two or more components / steps or partial operations of components / steps can be combined into new components / steps to achieve the purpose of the embodiments of the present application.

[0077] Computer readable storage medium

[0078] The present application embodiment also provides a computer-readable storage medium, and the above-mentioned method according to the embodiment of the present application can be implemented in hardware, firmware, or implemented as software or computer code that can be stored in a recording medium (such as a CD ROM, RAM, floppy disk, hard disk or magneto-optical disk), or implemented as a computer code originally stored in a remote recording medium or a non-temporary machine-readable medium downloaded through a network and to be stored in a local recording medium, so that the method described herein can be stored in such software processing on a recording medium using a general-purpose computer, a dedicated processor or programmable or dedicated hardware (such as an ASIC or FPGA). It can be understood that a computer, a processor, a microprocessor controller or programmable hardware includes a storage component (e.g., RAM, ROM, flash memory, etc.) that can store or receive software or computer code, and when the software or computer code is accessed and executed by a computer, a processor or hardware, the vehicle software upgrade method described herein is implemented. In addition, when a general-purpose computer accesses the code for implementing the vehicle software upgrade method shown herein, the execution of the code converts the general-purpose computer into a dedicated computer for executing the vehicle software upgrade method shown herein.

[0079] Those of ordinary skill in the art will appreciate that the units and method steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of the embodiments of the present application.

[0080] The above implementation methods are only used to illustrate the embodiments of the present application, and are not limitations on the embodiments of the present application. Ordinary technicians in the relevant technical field can make various changes and modifications without departing from the spirit and scope of the embodiments of the present application. Therefore, all equivalent technical solutions also belong to the scope of the embodiments of the present application. The scope of patent protection of the embodiments of the present application should be limited by the claims.

Claims

1. A vehicle software upgrade method, applied to a server, characterized in that: The method comprises: Receiving a query request from a battery swap terminal, wherein the query request is sent by the battery swap terminal in response to the received battery swap request; In response to the query request, a list of upgradeable software versions of the battery management system of the stock battery packs in the battery swap station is sent to the battery swap terminal, so that the battery swap terminal checks and updates the battery management system of the target battery pack in the battery swap station according to the list of upgradeable software versions and the battery swap request, so that the battery management system of the target battery pack is the first software version; After the target battery pack is installed on the vehicle, an update request from the battery replacement end is received, and a software check and update of the vehicle control unit of the vehicle is performed according to the update request.

2. The method according to claim 1, characterized in that: The method further comprises: Obtaining software package data of a battery management system of the vehicle under a complete vehicle baseline; For each existing battery pack, the hardware number corresponding to the hardware number is obtained, and the first software package data of the battery management system matching the battery capacity is selected from the software package data; Filtering the first software package data to find software package data that is hardware-compatible and software-compatible with the battery management system currently used by the vehicle and whose version number is greater than or equal to the version number corresponding to the software package of the battery management system currently used by the vehicle, and determining the filtered software package data as the second software package; The second software packages are sorted in descending order based on the version numbers, and the upgradeable software version list is determined according to the part number and version number of each software package in the sorted second software packages; wherein the part number is used to uniquely identify the software package, and the version number is used to indicate the version of the software package, and a larger version number indicates a higher version of the software package.

3. The method according to claim 2, characterized in that Before obtaining the software package data of the battery management system of the vehicle under the whole vehicle baseline, the method further includes: Receiving data verification information determined by the battery swapping terminal according to the battery swapping request; If the data verification information passes the data verification, obtaining the software package data of the battery management system of the vehicle under the whole vehicle baseline; Among them, the data verification information includes data verification information, including the unique identification of the vehicle, the battery model of the battery replacement request, the physical identification of the battery management system in the vehicle, the hardware number of the existing battery pack in the battery replacement station and at least one of the identification of the software module to be flashed in the battery management system.

4. The method according to claim 1, characterized in that The performing software checking and updating on the vehicle control unit of the vehicle according to the update request comprises: Obtaining a target battery capacity and a target software version of a battery management system in a software upgrade task of the vehicle; Check and update the software of the vehicle according to the first capacity of the target battery pack and the first software version If the first capacity is the same as the target battery capacity, and the first software version is the same as the target software version, then the software other than the target battery pack in the software upgrade task of the vehicle is checked and updated.

5. The method according to claim 4, characterized in that The method further comprises: If the first capacity is different from the target battery capacity, or the first version is lower than the target software version, a software check and update is performed on the vehicle based on the software update task of the vehicle.

6. A vehicle software upgrade method, characterized in that: Applied to the battery replacement end, the method includes: In response to the received battery replacement request, sending a query request to the server; Receiving a list of upgradeable software versions of the battery management system of the existing battery packs in the battery swap station sent by the server according to the query request; According to the battery swap request and the list of upgradeable software versions, checking and updating the battery management system of the target battery pack in the battery swap station, so that the battery management system of the target battery pack is the first software version; According to the capacity of the target battery pack and the first software version, an update request is sent to the server, so that the server checks and updates the software of the vehicle control unit of the vehicle according to the update request.

7. The method according to claim 6, characterized in that The step of checking and updating the battery management system of the target battery pack in the battery swap station according to the battery swap request and the upgradeable software version list so that the battery management system of the target battery pack is the first software version includes: For the upgradeable software version list corresponding to the battery management system of each existing battery, the part number of each software package in the upgradeable software version list is queried in descending order based on the version number of the software package. If the part number of the software package exists in the battery swap station, the query is stopped, and the candidate software package corresponding to the battery management system of the existing battery pack is determined according to the currently queried part number; Determine a target battery pack and a first battery version according to all stock battery packs and candidate software packages corresponding to the battery management system of each stock battery pack; The battery management system of the target battery pack is checked and updated based on the first battery version, so that the battery management system of the target battery pack is the first software version.

8. A vehicle software upgrade system, characterized in that: include: Battery swap request end, battery swap end, service end and vehicle; The battery replacement request end is used to send a battery replacement request to the battery replacement end; The server is used to execute the vehicle software upgrade method as described in any one of claims 1 to 5; The battery replacement terminal is used to execute the vehicle software upgrade method as described in any one of claims 6-7.

9. An electronic device, comprising: A processor, a memory, a communication interface and a communication bus, wherein the processor, the memory and the communication interface communicate with each other via the communication bus; The memory is used to store at least one executable instruction, and the executable instruction enables the processor to execute the vehicle software upgrade method as described in any one of claims 1-5 or 6-7.

10. A computer storage medium having a computer program stored thereon, wherein when the program is executed by a processor, the vehicle software upgrade method as described in any one of claims 1-5 or 6-7 is implemented.

Images