Vehicle software OTA upgrading method and device and vehicle

By recharged battery power in a car, the problem of failure caused by battery power loss during the OTA upgrade process is solved, ensuring the success of software upgrades, the safety and user experience of the vehicle.

CN119088413APending Publication Date: 2024-12-06GUANGZHOU AUTOMOBILE GROUP CO LTD
View PDF 0 Cites 1 Cited by

Patent Information

Application Number
CN202410939349.5
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-07-12
Publication Date
2024-12-06

AI Technical Summary

Technical Problem

During the upgrade of automotive software OTA, the upgrade failed due to battery failure.

Method used

The upgrade management module obtains the controller type and the required upgrade time of the software to be upgraded. If it supports high voltage type and the time length is greater than or equal to the preset time, send a recharge request to the vehicle or power domain controller and use the power battery as the battery Recharge the power to ensure sufficient power during the OTA upgrade process.

Benefits of technology

It effectively avoids the failure of OTA upgrade caused by battery power failure, ensures the successful software upgrade, and improves the safety and user experience of the vehicle.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119088413A_ABST
    Figure CN119088413A_ABST
Patent Text Reader

Abstract

The invention discloses a vehicle software OTA upgrading method and device and a vehicle. The method comprises the steps that in response to a received software OTA upgrading instruction, an upgrading management module in a vehicle obtains the type of a controller where to-be-upgraded software is located and the upgrading duration needed by the to-be-upgraded software; if the type of the controller where the to-be-upgraded software is located is an upper high voltage supporting type and the upgrading duration required by the to-be-upgraded software is greater than or equal to a preset duration, the upgrading management module sends a power supply request to the vehicle control unit or the power domain controller; and the upgrade management module starts to carry out OTA upgrade on the to-be-upgraded software in response to the received first charging state from the vehicle control unit or the power domain controller. Through the mode, the power battery of the vehicle can be used for charging the storage battery, so that the software OTA upgrading failure caused by the power shortage of the storage battery in the software OTA upgrading process is avoided.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of automobile technology, and more specifically, to a vehicle software OTA upgrade method, device and vehicle. Background Art

[0002] At present, there are more and more controllers in cars, and more and more controllers need to be upgraded through OTA technology (Over-the-Air Technology). In related methods, the power required for the software upgrade process can be provided by batteries. However, there is still a problem in related methods that software upgrades fail due to battery power loss. Summary of the invention

[0003] In view of the above problems, the present application proposes a vehicle software OTA upgrade method, device and vehicle to improve the above problems.

[0004] In the first aspect, the present application provides a vehicle software OTA upgrade method, the method comprising: in response to receiving a software OTA upgrade instruction, an upgrade management module in the vehicle obtains the type of controller where the software to be upgraded is located and the upgrade time required for the software to be upgraded; if the type of the controller where the software to be upgraded is located is a type that supports upper high voltage, and the upgrade time required for the software to be upgraded is greater than or equal to a preset time, the upgrade management module sends a power replenishment request to the vehicle controller or the power domain controller, and the power replenishment request is used to trigger the vehicle's power battery to replenish the battery; in response to receiving a first power replenishment state from the vehicle controller or the power domain controller, the upgrade management module starts to perform OTA upgrade on the software to be upgraded, and the first power replenishment state indicates that the battery power has reached a preset power threshold.

[0005] In the second aspect, the present application provides a vehicle software OTA upgrade method, the method comprising: in response to receiving a power replenishment request from a vehicle upgrade management module, the vehicle controller or the power domain controller obtains the remaining power of the power battery; if the remaining power of the power battery is less than a second threshold, the vehicle controller or the power domain controller sends an upper high voltage request, the upper high voltage request is used to start the engine, and replenish the power battery based on the engine so that the remaining power of the power battery is greater than or equal to the second threshold; in response to the remaining power of the power battery being greater than or equal to the second threshold, the engine is turned off, and the power battery is controlled to replenish the battery, and a first power replenishment status is sent to the upgrade management module to trigger the upgrade management module to start OTA upgrade of the software to be upgraded, the first power replenishment status indicating that the power of the battery has reached a preset power threshold.

[0006] In the third aspect, the present application provides a vehicle software OTA upgrade method, the method comprising: in response to receiving a power replenishment request from a vehicle upgrade management module, the vehicle controller or the power domain controller obtains the remaining power of the power battery; if the remaining power of the power battery is greater than or equal to a first threshold, the vehicle controller or the power domain controller sends an upper high voltage request, and the upper high voltage request is used to enable the vehicle's power battery to replenish power for the storage battery; in response to the power battery replenishing power for the storage battery, a first power replenishment status is sent to the upgrade management module to trigger the upgrade management module to start OTA upgrade of the software to be upgraded, and the first power replenishment status indicates that the power of the battery has reached a preset power threshold.

[0007] In a fourth aspect, the present application provides a vehicle software OTA upgrade device, the device comprising: an information acquisition unit, for, in response to receiving a software OTA upgrade instruction, an upgrade management module in the vehicle obtains the type of controller where the software to be upgraded is located and the upgrade time required for the software to be upgraded; a power replenishment request sending unit, for, if the type of the controller where the software to be upgraded is located is a type that supports upper high voltage, and the upgrade time required for the software to be upgraded is greater than or equal to a preset time, the upgrade management module sends a power replenishment request to the vehicle controller or the power domain controller, the power replenishment request is used to trigger the vehicle's power battery to replenish the battery; a software upgrade unit, for, in response to receiving a first power replenishment state from the vehicle controller or the power domain controller, the upgrade management module starts OTA upgrading the software to be upgraded, the first power replenishment state indicating that the battery power reaches a preset power threshold.

[0008] In a fifth aspect, the present application provides a vehicle software OTA upgrade device, the device comprising: a remaining power acquisition unit, for obtaining the remaining power of a power battery by a vehicle controller or a power domain controller in response to receiving a power replenishment request from an upgrade management module of the vehicle; an upper high-voltage request sending unit, for sending an upper high-voltage request by the vehicle controller or the power domain controller if the remaining power of the power battery is less than a second threshold, the upper high-voltage request being used to start the engine and replenish the power battery based on the engine so that the remaining power of the power battery is greater than or equal to the second threshold; a power replenishment status sending unit, for shutting down the engine and controlling the power battery to replenish the battery in response to the remaining power of the power battery being greater than or equal to the second threshold, and sending a first power replenishment status to the upgrade management module to trigger the upgrade management module to start OTA upgrade of the software to be upgraded, the first power replenishment status indicating that the power of the battery has reached a preset power threshold.

[0009] In a sixth aspect, the present application provides a vehicle software OTA upgrade device, the device comprising: a remaining power acquisition unit, for obtaining the remaining power of a power battery by a vehicle controller or a power domain controller in response to receiving a power replenishment request from an upgrade management module of the vehicle; an upper high-voltage request sending unit, for sending an upper high-voltage request by the vehicle controller or the power domain controller if the remaining power of the power battery is greater than or equal to a first threshold, the upper high-voltage request being used to enable the power battery of the vehicle to replenish power for the storage battery; a power replenishment status sending unit, for sending a first power replenishment status to the upgrade management module in response to the power battery replenishing power for the storage battery, so as to trigger the upgrade management module to start OTA upgrade of the software to be upgraded, the first power replenishment status indicating that the power of the storage battery has reached a preset power threshold.

[0010] In a seventh aspect, the present application provides a vehicle comprising a processor and a memory; one or more programs are stored in the memory and configured to be executed by the processor, and the one or more programs are configured to execute the above-mentioned method.

[0011] In an eighth aspect, the present application provides a computer-readable storage medium, in which program code is stored, wherein the above method is executed when the program code is run.

[0012] The present application provides a vehicle software OTA upgrade method, device, vehicle and storage medium. In response to receiving a software OTA upgrade instruction, an upgrade management module in the vehicle obtains the type of controller where the software to be upgraded is located and the upgrade time required for the software to be upgraded. If the type of the controller where the software to be upgraded is located is a type that supports upper high voltage, and the upgrade time required for the software to be upgraded is greater than or equal to a preset time, the upgrade management module sends a power replenishment request to the vehicle controller to trigger the vehicle's power battery to replenish the battery. In response to receiving a first power replenishment state from the vehicle controller indicating that the battery power has been replenished, the upgrade management module starts to perform OTA upgrade on the software to be upgraded. Through the above-mentioned method, the upgrade management module can determine the type of controller where the software to be upgraded is located and the upgrade time required for the controller where the software to be upgraded is located after receiving the software OTA upgrade instruction. If the type of controller where the software to be upgraded is located is a type that supports upper high voltage, and the upgrade time required for the software to be upgraded is greater than or equal to the preset time, the upgrade management module sends a power replenishment request to the vehicle controller or the power domain controller, and in response to receiving the first power replenishment status from the vehicle controller or the power domain controller, starts to perform OTA upgrade on the software to be upgraded, so that the battery can be recharged by the vehicle's power battery, thereby avoiding the failure of the software OTA upgrade due to battery depletion during the software OTA upgrade process. BRIEF DESCRIPTION OF THE DRAWINGS

[0013] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For those skilled in the art, other drawings can be obtained based on these drawings without creative work.

[0014] Figure 1 A flow chart of a vehicle software OTA upgrade method proposed in an embodiment of the present application is shown;

[0015] Figure 2 A flow chart of a vehicle software OTA upgrade method proposed in another embodiment of the present application is shown;

[0016] Figure 3 A schematic diagram showing data transmission between an upgrade management module and other components of a vehicle proposed in the present application is shown;

[0017] Figure 4 A flow chart of a vehicle software OTA upgrade method proposed in another embodiment of the present application is shown;

[0018] Figure 5 A business process diagram proposed in this application is shown;

[0019] Figure 6 Another business process diagram proposed in this application is shown;

[0020] Figure 7 A structural block diagram of a vehicle software OTA upgrade device proposed in an embodiment of the present application is shown;

[0021] Figure 8 A structural block diagram of another vehicle software OTA upgrade device proposed in an embodiment of the present application is shown;

[0022] Fig. 9 A structural block diagram of another vehicle software OTA upgrade device proposed in an embodiment of the present application is shown;

[0023] Fig.10 A structural block diagram of a vehicle proposed in this application is shown. DETAILED DESCRIPTION

[0024] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0025] In an embodiment of the present application, the inventor proposes a vehicle software OTA upgrade method, device and vehicle. In response to receiving a software OTA upgrade instruction, an upgrade management module in the vehicle obtains the type of controller where the software to be upgraded is located and the upgrade time required for the software to be upgraded. If the type of controller where the software to be upgraded is located is a type that supports upper high voltage, and the upgrade time required for the software to be upgraded is greater than or equal to a preset time, the upgrade management module sends a power replenishment request to the vehicle controller to trigger the vehicle's power battery to replenish the battery. In response to receiving a first power replenishment state from the vehicle controller indicating that the battery power has been replenished, the upgrade management module starts to perform OTA upgrade on the software to be upgraded. Through the above-mentioned method, the upgrade management module can determine the type of controller where the software to be upgraded is located and the upgrade time required for the controller where the software to be upgraded is located after receiving the software OTA upgrade instruction. If the type of controller where the software to be upgraded is located is a type that supports upper high voltage, and the upgrade time required for the software to be upgraded is greater than or equal to the preset time, the upgrade management module sends a power replenishment request to the vehicle controller or the power domain controller, and in response to receiving the first power replenishment status from the vehicle controller or the power domain controller, starts to perform OTA upgrade on the software to be upgraded, so that the battery can be recharged by the vehicle's power battery, thereby avoiding the failure of the software OTA upgrade due to battery depletion during the software OTA upgrade process.

[0026] See also Figure 1 , an embodiment of the present application provides a vehicle software OTA upgrade method, the method comprising:

[0027] S110: In response to receiving the software OTA upgrade instruction, the upgrade management module in the vehicle obtains the type of controller where the software to be upgraded is located and the upgrade time required for the software to be upgraded.

[0028] Among them, the software OTA upgrade instruction can be used to instruct the upgrade management module to upgrade the controller software where the software to be upgraded is located. The software OTA upgrade instruction may include the identifier of the controller where the software to be upgraded is located and the size of the software upgrade package. The upgrade management module (OTA module) can be a controller used to perform OTA upgrades on the software to be upgraded in the vehicle.

[0029] The controller where the software to be upgraded is located may be a controller in the vehicle, and the type of the controller where the software to be upgraded is located may be a type that supports upper high voltage or a type that does not support upper high voltage. Whether the controller where the software to be upgraded is located supports upper high voltage can be understood as whether the corresponding controller where the software to be upgraded is located can work normally under high voltage. Among them, the controller that does not support upper high voltage may be a controller related to new energy (such as electricity), such as a vehicle controller, a battery controller, a motor controller, etc.; the controller that supports upper high voltage may be a controller that is not related to new energy, such as an instrument controller, a body controller, etc.

[0030] As a method, the cloud can send a software OTA upgrade instruction to the upgrade management module. In response to receiving the software OTA upgrade instruction, the upgrade management module in the vehicle can determine the type of controller where the software to be upgraded is located based on a preset controller type mapping table where the software to be upgraded is located and the identifier of the controller where the software to be upgraded is located in the software OTA upgrade instruction. And the upgrade management module in the vehicle can determine whether the upgrade time required for the controller where the software to be upgraded is located is long based on the size of the software upgrade package in the software OTA upgrade instruction.

[0031] The controller type mapping table where the software to be upgraded is located can be stored in the upgrade management module. Exemplarily, the controller type mapping table where the software to be upgraded is located can be as shown in Table 1.

[0032] Table 1

[0033] Device identification Device Name Device Type 001 Motor Controller Does not support high voltage type 002 Instrument Controller Support high voltage type ... ... ...

[0034] Optionally, the larger the software upgrade package, the longer the upgrade will take.

[0035] In an embodiment of the present application, after receiving the software OTA upgrade instruction from the cloud, the type of controller where the software to be upgraded is located and the upgrade time required for the software to be upgraded are directly obtained, so that an automatic upgrade service that is not noticeable to the user can be provided, thereby improving the user experience.

[0036] As another method, the cloud can send a software upgrade request to the upgrade management module, and the upgrade management module can respond to receiving the software upgrade request and send a prompt message to the user terminal, which can be used to prompt the user that the engine will be started during the software upgrade process, and request the user to feedback whether the software upgrade is agreed; if the software upgrade agreement is received from the user terminal, the upgrade management module confirms that the software OTA upgrade instruction is received, so that the type of controller where the software to be upgraded is located can be determined based on the pre-set controller type mapping table where the software to be upgraded is located and the identifier of the controller where the software to be upgraded is located in the software OTA upgrade instruction. And the upgrade management module in the vehicle can determine the upgrade time required for the controller where the software to be upgraded is located based on the size of the software upgrade package in the software OTA upgrade instruction.

[0037] The software upgrade request may be used to request the upgrade management module to upgrade the controller software where the software to be upgraded is located. The user terminal may be a terminal device used by the vehicle user, such as a mobile phone, a computer, a tablet, and the like.

[0038] Optionally, after receiving the software upgrade request, the upgrade management module can send a prompt message to the user terminal through T-Box (Telematics-Box, on-board terminal) and TSP (Telematics Service Provider, automotive remote service provider), and receive feedback information from the user terminal. If the feedback information is to agree to the software upgrade, the upgrade management module confirms receipt of the software OTA upgrade instruction, thereby obtaining the type of controller where the software to be upgraded is located and the upgrade time required for the software to be upgraded, so as to prepare for the software upgrade; if the feedback information is to disagree with the software upgrade, the type of controller where the software to be upgraded is located and the upgrade time required for the software to be upgraded are not obtained, and the current upgrade is abandoned.

[0039] Optionally, the prompt information may appear on the display screen of the user terminal in the form of a pop-up window generated by a related application, or may appear on the display screen of the user terminal in the form of a text message.

[0040] Optionally, the user can input feedback information to the user terminal through voice, gesture, pressing relevant controls, typing on the keyboard, etc.

[0041] In the embodiment of the present application, after receiving the software upgrade consent information fed back by the user terminal, the type of controller where the software to be upgraded is located and the upgrade time required for the software to be upgraded are obtained, so that the user can determine whether to start the software upgrade immediately based on the current vehicle status, the user's own vehicle use intention, etc., thereby improving the safety of vehicle use, reducing the loss of vehicle components, and enriching the interaction between the user and the vehicle. For example, it is currently raining heavily and the vehicle is in a flooded state. If the engine is started for upgrading, it may cause damage to the engine. For another example, the user needs to use the vehicle in a few minutes or does not want to upgrade the software at this time.

[0042] Optionally, when the user terminal sends a notification of disagreement with the software upgrade to the upgrade management module, it can also send an appointment time, so that the upgrade management module can obtain the type of controller where the software to be upgraded is located and the upgrade time required for the software to be upgraded when the appointment time arrives, so as to prepare for the software upgrade. The appointment time can be after a specified time, such as 2 hours later, or it can be a specific natural time, such as XX year XX month XX day XX hour XX minute.

[0043] In an embodiment of the present application, by obtaining the type of controller where the software to be upgraded is located and the upgrade time required for the software to be upgraded when the scheduled time arrives, it is possible to avoid missing the software upgrade due to the user being busy, so that the software in the vehicle can be updated in time to provide better service to the user.

[0044] Optionally, if the feedback information is that the software upgrade is not agreed to, and the upgrade management module abandons the current upgrade, the software upgrade module can send a prompt message to the user again after a preset time until it receives feedback from the user terminal indicating that it agrees to the software upgrade, so as to update the software in the vehicle in a timely manner while ensuring vehicle safety and meeting the user's intention to use the vehicle.

[0045] Optionally, if the reminder message for the same software upgrade version of the controller where the same software to be upgraded is located is sent a specified number of times, it may indicate that the user may not want to upgrade the device. To avoid annoying the user, the reminder message may no longer be sent, and the software of the controller where the software to be upgraded is located may not be upgraded to that version.

[0046] S120: If the type of controller where the software to be upgraded is located is a type that supports upper high voltage, and the upgrade time required for the software to be upgraded is greater than or equal to the preset time, the upgrade management module sends a power replenishment request to the vehicle controller or the power domain controller, and the power replenishment request is used to trigger the vehicle's power battery to replenish the battery.

[0047] As a method, if the type of controller where the software to be upgraded is located is a type that supports high voltage, and the upgrade time required for the software to be upgraded is greater than or equal to the preset time, the upgrade management module can confirm whether the first target condition is met; if the first target condition is met, the upgrade management module sends a power replenishment request to the vehicle controller or the power domain controller.

[0048] Among them, the vehicle controller can be a VCU (Vehicle Control Unit) and the power domain controller can be a VBU (Vehicle Brain Unit).

[0049] In an embodiment of the present application, the first target condition may include: the remaining power of the battery is less than or equal to a preset value; and the time for the power battery to recharge the battery is less than or equal to the preset recharging time; and the remaining power of the power battery is greater than or equal to a first threshold; and the vehicle is in an armed state; and the power supply mode of the vehicle is IGOFF; and the hood of the vehicle is in a closed state; and the upgrade management module receives a second recharging state from the vehicle controller, and the second recharging state can indicate that the power battery has failed to recharge the battery.

[0050] When the remaining power of the battery (State of Charge, SOC) is less than or equal to the preset value, it can indicate that the remaining power of the battery is insufficient. If the battery is not recharged, the battery may be depleted during the upgrade process, thereby causing the software upgrade to fail. The preset value can be obtained based on multiple test results, for example, the preset value can be 90%.

[0051] If the duration of the power battery replenishing the battery is less than or equal to the preset replenishing duration, it may indicate that the power battery is insufficient to replenish the battery, so that the remaining power of the battery is still insufficient. If the battery is not replenished by the power battery, the battery may be depleted during the upgrade process, which may lead to software upgrade failure. The preset replenishing duration may be obtained based on multiple test results, for example, the preset replenishing duration may be 1 hour.

[0052] If the remaining power of the power battery is greater than or equal to the first threshold, it can be indicated that the remaining power of the power battery is sufficient, and the battery can be recharged by consuming part of the power while ensuring that other functions of the battery can operate normally. The first threshold can be obtained based on multiple test results. For example, the first threshold corresponding to a hybrid electric vehicle (HEV) can be 45%, and the first threshold corresponding to a plug-in hybrid electric vehicle (PHEV) can be 10%.

[0053] The vehicle is in an armed state, which indicates that the user has locked the vehicle, thereby preventing the user from electric shock.

[0054] The vehicle's power supply mode is IGOFF, which indicates that the user has pressed the ignition off button when getting off the vehicle. Therefore, when the vehicle is not started, the power battery can be used to recharge the storage battery, thereby improving vehicle safety.

[0055] The vehicle's hood is closed to prevent users from getting electric shock. If the hood is open, it means that the user may be repairing the vehicle, and some components of the vehicle will be in a high-voltage state when the power battery is recharging the storage battery, which may cause high-voltage electric shock to the user.

[0056] The upgrade management module receives the second charging status from the vehicle controller, indicating that there is a problem with the relevant components in the vehicle and the storage battery cannot be charged by the power battery.

[0057] Optionally, the upgrade module can determine whether the above first target condition is met based on the feedback information by sending query information to the relevant vehicle controller. For example, the power query information and charging time query information can be sent to the battery management system (BMS), so as to determine the relationship between the remaining power of the battery and the preset value, and the relationship between the time the power battery charges the battery and the preset charging time based on the feedback information.

[0058] In the embodiment of the present application, when the first target condition is met, sending a power replenishment request can improve the safety of the vehicle.

[0059] Optionally, the preset duration can be determined based on the statistical results of the upgrade duration of the software upgrade package. The statistical results of the software upgrade package can be obtained based on big data analysis. For example, the statistical results may be that 20% of the software upgrade packages have an upgrade duration of 20 minutes, 60% of the software upgrade packages have an upgrade duration of 40 minutes, and 20% of the software upgrade packages have an upgrade duration of 1 hour. The preset duration can be the upgrade duration with the largest proportion, that is, 40 minutes.

[0060] Optionally, the preset duration may be determined based on the battery power. Specifically, the preset duration may be a multiple of the upgrade duration that the battery can support when fully charged. For example, if the battery can support an upgrade duration of 1 hour when fully charged, the preset duration may be 1 hour, 2 hours, or 2.5 hours, etc.

[0061] As a method, if the type of controller where the software to be upgraded is located does not support high voltage, or the upgrade time required for the controller where the software to be upgraded is less than the preset time, the upgrade management module can directly perform the software upgrade.

[0062] S130: In response to receiving a first power replenishment state from the vehicle controller or the power domain controller, the upgrade management module starts OTA upgrading the software to be upgraded, wherein the first power replenishment state indicates that the power of the battery reaches a preset power threshold.

[0063] As a method, the upgrade management module can start OTA upgrade of the software to be upgraded in response to receiving the first power replenishment state from the vehicle controller or the power domain controller.

[0064] Optionally, during the OTA upgrade of the software to be upgraded by the upgrade management module, if the second power replenishment state is received from the vehicle controller, it can indicate that from the current moment onwards, only the remaining power of the battery can be relied upon to power the relevant devices in the software upgrade process. If the upgrade management module fails to complete the software upgrade before the remaining power of the battery reaches 0, the battery will be depleted and the software upgrade will fail.

[0065] As a method, the upgrade management module may not perform OTA upgrade on the software to be upgraded in response to receiving a second charging state from the vehicle controller, wherein the second charging state may indicate that the power battery has failed to charge the storage battery.

[0066] Optionally, the upgrade management module may transmit data with the vehicle controller via a gateway module (GWM).

[0067] The present embodiment provides a vehicle software OTA upgrade method. In response to receiving a software OTA upgrade instruction, an upgrade management module in the vehicle obtains the type of controller where the software to be upgraded is located and the upgrade time required for the software to be upgraded. If the type of controller where the software to be upgraded is located is a type that supports upper high voltage, and the upgrade time required for the software to be upgraded is greater than or equal to a preset time, the upgrade management module sends a power replenishment request to the vehicle controller to trigger the vehicle's power battery to replenish the battery. In response to receiving a first power replenishment state from the vehicle controller indicating that the battery power has been replenished, the upgrade management module starts to perform OTA upgrade on the software to be upgraded. Through the above-mentioned method, the upgrade management module can determine the type of controller where the software to be upgraded is located and the upgrade time required for the controller where the software to be upgraded is located after receiving the software OTA upgrade instruction. If the type of controller where the software to be upgraded is located is a type that supports upper high voltage, and the upgrade time required for the software to be upgraded is greater than or equal to the preset time, the upgrade management module sends a power replenishment request to the vehicle controller or the power domain controller, and in response to receiving the first power replenishment status from the vehicle controller or the power domain controller, starts to perform OTA upgrade on the software to be upgraded, so that the battery can be recharged by the vehicle's power battery, thereby avoiding the failure of the software OTA upgrade due to battery depletion during the software OTA upgrade process.

[0068] See also Figure 2 , an embodiment of the present application provides a vehicle software OTA upgrade method, the method comprising:

[0069] S210: In response to receiving a power replenishment request from the upgrade management module of the vehicle, the vehicle controller or the power domain controller obtains the remaining power of the power battery.

[0070] As a method, in response to receiving a power replenishment request from the vehicle's upgrade management module, the vehicle controller can send a power battery power acquisition request to the battery controller to obtain the remaining power of the power battery based on feedback information from the battery controller.

[0071] S220: If the remaining power of the power battery is less than a second threshold, the vehicle controller or the power domain controller sends an upper high-voltage request, which is used to start the engine and replenish the power battery based on the engine so that the remaining power of the power battery is greater than or equal to the second threshold.

[0072] The second threshold value may be obtained based on multiple test results. For example, the second threshold value corresponding to a hybrid electric vehicle (HEV) may be 65%, and the second threshold value corresponding to a plug-in hybrid electric vehicle (PHEV) may be 20%.

[0073] As a way, Figure 3 As shown, if the remaining power of the power battery is less than the second threshold, the vehicle controller or the power domain controller can send a high-voltage request to the battery controller BMS, the motor controller (Instruction Processing Unit, IPU) and other controllers related to high-voltage electricity, so as to start the engine after the high voltage is applied, and let the engine drive the generator to generate electricity, thereby replenishing the power battery based on the generator.

[0074] As a method, if the remaining power of the power battery is greater than or equal to the second threshold, the vehicle controller or the power domain controller can send a high-voltage request to the battery controller, motor controller (Instruction Processing Unit, IPU) and other controllers related to high-voltage electricity, so as to directly control the power battery to replenish the battery after the high voltage is increased.

[0075] Optionally, after applying high voltage, the battery controller can feed back the remaining power of the power battery to the vehicle controller or the power domain controller in real time.

[0076] S230: In response to the remaining power of the power battery being greater than or equal to the second threshold, shutting down the engine, controlling the power battery to recharge the storage battery, and sending a first recharging status to the upgrade management module to trigger the upgrade management module to start OTA upgrading the software to be upgraded, wherein the first recharging status indicates that the power of the storage battery has reached a preset power threshold.

[0077] As a method, in response to the remaining power of the power battery being greater than or equal to the second threshold, the vehicle controller shuts down the engine, controls the power battery to replenish the battery, and sends a first replenishment status to the upgrade management module.

[0078] Optionally, the vehicle controller or the power domain controller may send a first charging status to the upgrade management module when the power battery replenishes the remaining power of the battery to a preset value.

[0079] Optionally, the vehicle controller or the power domain controller may send a first charging status to the upgrade management module when the power battery starts to charge the storage battery.

[0080] As a method, if the vehicle controller or the power domain controller confirms that the second target condition is met, the vehicle controller or the power domain controller sends a high voltage request and sends a second power replenishment status to the upgrade management module. The second power replenishment status can indicate that the power battery has failed to replenish the battery.

[0081] In an embodiment of the present application, the second target condition may include: the remaining power of the power battery is less than the first threshold, the first threshold is less than the second threshold; the vehicle has a high-voltage power-off fault; the DC-DC converter in the vehicle does not work after being enabled; no power replenishment request sent by the upgrade management module is received after a specified time; the vehicle receives a charging wake-up signal; the vehicle is in an unarmed state; the vehicle's power supply mode is not IGOFF; the vehicle's hood is in an open state.

[0082] The vehicle having a high voltage power failure may refer to a failure of a designated component causing the vehicle to be unable to power up to high voltage. The command component is predetermined based on the experience of relevant personnel.

[0083] The DC-DC converter (DCDC) can convert the high voltage of the power battery (such as 48V) into low voltage electricity, and then replenish the battery based on the low voltage electricity (such as 12V). If the DCDC fails, the power battery can stop replenishing the battery.

[0084] In the embodiment of the present application, the safety of the vehicle can be improved by controlling the power battery to stop replenishing the storage battery when the second target condition is met.

[0085] Optionally, the battery recharge can be stopped by disconnecting the power battery relay.

[0086] A vehicle software OTA upgrade method provided in this embodiment enables, through the above-mentioned method, after receiving a power replenishment request, if the power battery is insufficient, that is, the remaining power of the power battery is less than or equal to a second threshold, the vehicle controller can first start the engine to replenish the power battery, and then shut down the engine when the remaining power of the power battery reaches the second threshold, so that the battery can be replenished by the replenished power battery, thereby avoiding the failure of the software OTA upgrade due to the low power of the battery during the software OTA upgrade process, and at the same time avoiding the power battery malfunction due to insufficient remaining power.

[0087] See also Figure 4 , an embodiment of the present application provides a vehicle software OTA upgrade method, the method comprising:

[0088] S310: In response to receiving a power replenishment request from the upgrade management module of the vehicle, the vehicle controller or the power domain controller obtains the remaining power of the power battery.

[0089] S320: If the remaining power of the power battery is greater than or equal to the first threshold, the vehicle controller or the power domain controller sends a high-voltage request, and the high-voltage request is used to enable the power battery of the vehicle to supplement the battery.

[0090] As a method, if the remaining power of the power battery is greater than or equal to the first threshold, the vehicle controller or the power domain controller can send a high-voltage request to the battery controller, motor controller and other controllers related to high-voltage electricity or the power domain controller, so as to directly control the power battery to replenish the battery after the high voltage is increased.

[0091] As a method, if the remaining power of the power battery is less than the first threshold, the vehicle controller or the power domain controller can send a second power replenishment status to the upgrade management module, so that the upgrade management module does not perform software upgrades.

[0092] S330: In response to the power battery replenishing power for the storage battery, a first replenishing power state is sent to the upgrade management module to trigger the upgrade management module to start OTA upgrade of the software to be upgraded, wherein the first replenishing power state indicates that the power of the storage battery reaches a preset power threshold.

[0093] As a method, in response to the power battery replenishing power for the storage battery, the vehicle controller or the power domain controller sends a first replenishment status to the upgrade management module.

[0094] Optionally, the vehicle controller or the power domain controller may send a first charging status to the upgrade management module when the power battery replenishes the remaining power of the battery to a preset value.

[0095] Optionally, the vehicle controller or the power domain controller may send a first charging status to the upgrade management module when the power battery starts to charge the storage battery.

[0096] As a method, if the vehicle controller or the power domain controller confirms that the second target condition is met, the vehicle controller or the power domain controller sends a high voltage request and sends a second power replenishment status to the upgrade management module. The second power replenishment status can indicate that the power battery has failed to replenish the battery.

[0097] In an embodiment of the present application, the second target condition may include: the remaining power of the power battery is less than the first threshold, the first threshold is less than the second threshold; the vehicle has a high-voltage power-off fault; the DC-DC converter in the vehicle does not work after being enabled; no power replenishment request sent by the upgrade management module is received after a specified time; the vehicle receives a charging wake-up signal; the vehicle is in an unarmed state; the vehicle's power supply mode is not IGOFF; the vehicle's hood is in an open state.

[0098] A vehicle software OTA upgrade method provided in this embodiment enables, through the above-mentioned method, after receiving a power replenishment request, if the remaining power of the power battery is less than the first threshold, the vehicle controller can send the second power replenishment status to the upgrade management module so that the upgrade management module does not perform software upgrades; if the remaining power of the power battery is greater than or equal to the first threshold, the power battery can be used to replenish the battery, and the first power replenishment status is sent to the upgrade management module so that the upgrade management module performs software upgrades, thereby avoiding vehicle failures due to insufficient remaining power of the power battery.

[0099] In order to better understand the solutions of all embodiments of the present application, a business process of the vehicle software OTA upgrade method of the present application is introduced below.

[0100] See also Figure 5 , after the upgrade management module receives the feedback information from the user terminal based on step S1, if it is determined based on step S2 that the user does not agree to the software upgrade, step S3 can be executed; if it is determined in step S2 that the user agrees to the software upgrade, steps S4 and S5 can be executed in sequence. If it is determined based on step S5 that the controller where the software to be upgraded is located does not support the upper high voltage type or the time required for the upgrade is less than the preset time, step S6 can be executed; if it is determined based on step S5 that the controller where the software to be upgraded is located supports the upper high voltage type and the time required for the upgrade is greater than or equal to the preset time, step S7 can be executed. After the vehicle controller or the power domain controller obtains the remaining power of the power battery based on step S8, if it is determined based on step S9 that the remaining power of the power battery is less than the second threshold, steps S10 to S12 can be executed; if it is determined based on step S9 that the remaining power of the power battery is less than the second threshold, step S12 can be executed. The upgrade management module can start the software upgrade based on step S13 until the upgrade is completed or the current software upgrade process is exited due to battery depletion. During the software upgrade process, the vehicle controller or the power domain controller can monitor the remaining power of the power battery in real time based on step S14 and step S15, and send a second charging status to the upgrade management module when the remaining power of the power battery is less than the first threshold.

[0101] In order to better understand the solutions of all embodiments of the present application, another business process of the vehicle software OTA upgrade method of the present application is introduced below.

[0102] See also Figure 6, after the upgrade management module receives the feedback information from the user terminal based on step S1, if it is determined based on step S2 that the user does not agree to the software upgrade, step S3 can be executed; if it is determined based on step S2 that the user agrees to the software upgrade, steps S4 and S5 can be executed in sequence. If it is determined based on step S5 that the controller where the software to be upgraded is located does not support the upper high voltage type or the time required for the upgrade is less than the preset time, step S6 can be executed; if it is determined based on step S5 that the controller where the software to be upgraded is located supports the upper high voltage type and the time required for the upgrade is greater than or equal to the preset time, step S7 can be executed. After the vehicle controller or the power domain controller obtains the remaining power of the power battery based on step S8, if it is determined based on step S9 that the remaining power of the power battery is less than the first threshold, step S15 can be executed, so that the software upgrade management module can not perform the software upgrade based on step S16; if it is determined based on step S9 that the remaining power of the power battery is greater than or equal to the first threshold, step S10 can be executed, so that the software upgrade management module can start the software upgrade based on step S11. The upgrade management module can start the software upgrade based on step S13. During the software upgrade process, the vehicle controller or the power domain controller can monitor the remaining power of the power battery in real time based on step S12 and step S13, and send a second charging status to the upgrade management module when the remaining power of the power battery is less than the first threshold.

[0103] See also Figure 7 The present application provides a vehicle software OTA upgrade device 600, the device 600 comprising:

[0104] The information acquisition unit 610 is used for, in response to receiving a software OTA upgrade instruction, the upgrade management module in the vehicle to obtain the type of controller where the software to be upgraded is located and the upgrade time required for the software to be upgraded.

[0105] The power replenishment request sending unit 620 is used to send a power replenishment request to the vehicle controller or the power domain controller if the type of the controller where the software to be upgraded is located is a type that supports upper high voltage and the upgrade time required for the software to be upgraded is greater than or equal to the preset time. The power replenishment request is used to trigger the vehicle's power battery to replenish the battery.

[0106] The software upgrade unit 630 is used to respond to receiving a first power replenishment state from the vehicle controller or the power domain controller, and the upgrade management module starts OTA upgrading the software to be upgraded, wherein the first power replenishment state indicates that the power of the battery reaches a preset power threshold.

[0107] As a method, the information acquisition unit 610 is specifically used to respond to receiving a software upgrade request, and the upgrade management module sends a prompt message to the user terminal, and the prompt message is used to prompt the user that the engine will be started during the software upgrade process, and request the user to feedback whether they agree to the software upgrade; if the user terminal feedbacks the software upgrade agreement, the upgrade management module confirms that the software OTA upgrade instruction has been received.

[0108] As a method, the power replenishment request sending unit 620 is specifically used to confirm whether the first target condition is met by the upgrade management module if the type of the controller where the software to be upgraded is located is a type that supports upper high voltage and the upgrade time required for the controller where the software to be upgraded is located is greater than or equal to the preset time; if the first target condition is met, the upgrade management module sends a power replenishment request to the vehicle controller or the power domain controller.

[0109] Optionally, the first target condition includes: the remaining power of the battery is less than or equal to a preset value; and the time for which the power battery recharges the battery is less than or equal to a preset recharge time; and the remaining power of the power battery is greater than or equal to a first threshold; and the vehicle is in an armed state; and the power supply mode of the vehicle is IGOFF; and the hood of the vehicle is in a closed state; and the upgrade management module receives a second recharge status from the vehicle controller, and the second recharge status indicates that the power battery has failed to recharge the battery.

[0110] See also Figure 8 The present application provides a vehicle software OTA upgrade device 800, the device 800 comprising:

[0111] The remaining power acquisition unit 810 is used to obtain the remaining power of the power battery by the vehicle controller or the power domain controller in response to receiving a power replenishment request from the upgrade management module of the vehicle.

[0112] The upper high-voltage request sending unit 820 is used for the vehicle controller or the power domain controller to send an upper high-voltage request if the remaining power of the power battery is less than a second threshold value. The upper high-voltage request is used to start the engine and replenish the power battery based on the engine so that the remaining power of the power battery is greater than or equal to the second threshold value.

[0113] The power replenishment status sending unit 830 is used to shut down the engine and control the power battery to replenish the battery in response to the remaining power of the power battery being greater than or equal to the second threshold, and to send a first power replenishment status to the upgrade management module to trigger the upgrade management module to start OTA upgrade of the software to be upgraded. The first power replenishment status indicates that the power of the battery has reached a preset power threshold.

[0114] As a method, the charging status sending unit 830 is specifically used to send a lower high voltage request and send a second charging status to the upgrade management module if the vehicle controller confirms that the second target condition is met. The second charging status indicates that the power battery has failed to charge the storage battery.

[0115] Optionally, the second target condition includes: the remaining power of the power battery is less than the first threshold, the first threshold is less than the second threshold; the vehicle has a high-voltage power-off fault; the DC-DC converter in the vehicle does not work after being enabled; no power replenishment request sent by the upgrade management module is received after a specified time; the vehicle receives a charging wake-up signal; the vehicle is in an unarmed state; the power supply mode of the vehicle is not IGOFF; the hood of the vehicle is in an open state.

[0116] See also Fig. 9 The present application provides a vehicle software OTA upgrade device 1000, the device 1000 comprising:

[0117] The remaining power acquisition unit 1010 is used for the vehicle controller or the power domain controller to acquire the remaining power of the power battery in response to receiving a power replenishment request from the upgrade management module of the vehicle.

[0118] The high-voltage request sending unit 1020 is used for the vehicle controller or the power domain controller to send a high-voltage request if the remaining power of the power battery is greater than or equal to the first threshold, and the high-voltage request is used to enable the power battery of the vehicle to supplement the battery.

[0119] The power replenishment status sending unit 1030 is used to shut down the engine and control the power battery to replenish the battery in response to the remaining power of the power battery being greater than or equal to the second threshold, and to send a first power replenishment status to the upgrade management module to trigger the upgrade management module to start OTA upgrade of the software to be upgraded, wherein the first power replenishment status indicates that the power of the battery has reached a preset power threshold.

[0120] As a method, the charging status sending unit 830 is specifically used to send a lower high voltage request and send a second charging status to the upgrade management module if the vehicle controller confirms that the second target condition is met. The second charging status indicates that the power battery has failed to charge the storage battery.

[0121] Optionally, the second target condition includes: the remaining power of the power battery is less than the first threshold, the first threshold is less than the second threshold; the vehicle has a high-voltage power-off fault; the DC-DC converter in the vehicle does not work after being enabled; no power replenishment request sent by the upgrade management module is received after a specified time; the vehicle receives a charging wake-up signal; the vehicle is in an unarmed state; the power supply mode of the vehicle is not IGOFF; the hood of the vehicle is in an open state.

[0122] The following will be combined Fig.10 A vehicle provided in the present application is described.

[0123] See also Fig.10 Based on the above-mentioned vehicle software OTA upgrade method and device, the embodiment of the present application also provides another vehicle 100 that can execute the above-mentioned vehicle software OTA upgrade method. The vehicle 100 includes one or more (only one is shown in the figure) mutually coupled upgrade management modules 102, a vehicle controller 104, a memory 106, and a power domain controller 108. Among them, the memory 106 stores a program that can execute the content of the above-mentioned embodiment, and the upgrade management module 102 and the vehicle controller 104 can execute the program stored in the memory 106.

[0124] Among them, the upgrade management module 102, the vehicle controller 104 or the power domain controller 108 may include one or more processing cores. The upgrade management module 102, the vehicle controller 104 or the power domain controller 108 use various interfaces and lines to connect various parts in the entire vehicle 100, and execute various functions and process data of the vehicle 100 by running or executing instructions, programs, code sets or instruction sets stored in the memory 106, and calling data stored in the memory 106. Optionally, the upgrade management module 102, the vehicle controller 104 or the power domain controller 108 can be implemented in at least one hardware form of digital signal processing (DSP), field programmable gate array (FPGA), and programmable logic array (PLA). The upgrade management module 102, the vehicle controller 104 or the power domain controller 108 can integrate one or a combination of a central processing unit (CPU), a graphics processing unit (GPU), and a modem. The CPU mainly processes the operating system, user interface, and application programs, etc. The GPU is responsible for rendering and drawing display content, and the modem is used to handle wireless communications. It is understandable that the above-mentioned modem may not be integrated into the upgrade management module 102, the vehicle controller 104, or the power domain controller 108, but may be implemented separately through a communication chip.

[0125] The memory 106 may include a random access memory (RAM) or a read-only memory (ROM). The memory 106 may be used to store instructions, programs, codes, code sets or instruction sets. The memory 106 may include a program storage area and a data storage area, wherein the program storage area may store instructions for implementing an operating system, instructions for implementing at least one function (such as a touch function, a sound playback function, an image playback function, etc.), instructions for implementing the following various method embodiments, etc. The data storage area may also store data created by the vehicle 100 during use (such as a phone book, audio and video data, chat record data), etc.

[0126] The embodiment of the present application further provides a computer-readable storage medium. The computer-readable storage medium 1200 stores program codes, which can be called by a processor to execute the method described in the above method embodiment.

[0127] The computer readable storage medium 1200 may be an electronic memory such as a flash memory, an EEPROM (electrically erasable programmable read-only memory), an EPROM, a hard disk, or a ROM. Optionally, the computer readable storage medium 1200 includes a non-transitory computer-readable storage medium. The computer readable storage medium 1200 has storage space for program code 1210 that performs any method step of the above method. These program codes can be read from or written to one or more computer program products. The program code 1210 can be compressed, for example, in an appropriate form.

[0128] To summarize, the present application provides a vehicle software OTA upgrade method, device and vehicle. In response to receiving a software OTA upgrade instruction, the upgrade management module in the vehicle obtains the type of controller where the software to be upgraded is located and the upgrade time required for the software to be upgraded. If the type of controller where the software to be upgraded is located is a type that supports upper high voltage, and the upgrade time required for the software to be upgraded is greater than or equal to a preset time, the upgrade management module sends a power replenishment request to the vehicle controller to trigger the vehicle's power battery to replenish the battery. In response to receiving a first power replenishment state from the vehicle controller indicating that the battery power has been replenished, the upgrade management module starts to perform OTA upgrade on the software to be upgraded. Through the above-mentioned method, the upgrade management module can determine the type of controller where the software to be upgraded is located and the upgrade time required for the controller where the software to be upgraded is located after receiving the software OTA upgrade instruction. If the type of controller where the software to be upgraded is located is a type that supports upper high voltage, and the upgrade time required for the software to be upgraded is greater than or equal to the preset time, the upgrade management module sends a power replenishment request to the vehicle controller or the power domain controller, and in response to receiving the first power replenishment status from the vehicle controller or the power domain controller, starts to perform OTA upgrade on the software to be upgraded, so that the battery can be recharged by the vehicle's power battery, thereby avoiding the failure of the software OTA upgrade due to battery depletion during the software OTA upgrade process.

[0129] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit it. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. However, these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present application.

Claims

1. A vehicle software OTA upgrade method, characterized in that: The method comprises: In response to receiving the software OTA upgrade instruction, the upgrade management module in the vehicle obtains the type of controller where the software to be upgraded is located and the upgrade time required for the software to be upgraded; If the type of the controller where the software to be upgraded is located is a type that supports upper high voltage, and the upgrade time required for the software to be upgraded is greater than or equal to the preset time, the upgrade management module sends a power replenishment request to the vehicle controller or the power domain controller, and the power replenishment request is used to trigger the vehicle's power battery to replenish the battery; In response to receiving a first power replenishment state from the vehicle controller or the power domain controller, the upgrade management module starts OTA upgrading the software to be upgraded, and the first power replenishment state indicates that the power of the battery reaches a preset power threshold.

2. The method according to claim 1, characterized in that Before the step of obtaining the type of controller where the software to be upgraded is located and the upgrade time required for the software to be upgraded in response to receiving the software OTA upgrade instruction, the step further includes: In response to receiving the software upgrade request, the upgrade management module sends a prompt message to the user terminal, wherein the prompt message is used to prompt the user that the engine will be started during the software upgrade process, and to request the user to feedback whether the user agrees to the software upgrade; If the software upgrade consent information fed back by the user terminal is received, the upgrade management module confirms receipt of the software OTA upgrade instruction.

3. The method according to claim 1, characterized in that If the type of the controller where the software to be upgraded is located is a type that supports high voltage, and the upgrade time required for the software to be upgraded is greater than or equal to the preset time, the upgrade management module sends a power replenishment request to the vehicle controller or the power domain controller, including: If the type of the controller where the software to be upgraded is located is a type that supports upper high voltage, and the upgrade time required for the software to be upgraded is greater than or equal to the preset time, the upgrade management module confirms whether the first target condition is met; If the first target condition is met, the upgrade management module sends a power replenishment request to the vehicle controller or the power domain controller.

4. The method according to claim 3, characterized in that The first target condition includes: The remaining power of the battery is less than or equal to a preset value; and The duration for which the power battery replenishes the storage battery is less than or equal to a preset replenishment duration; and The remaining power of the power battery is greater than or equal to a first threshold; and The vehicle is in an armed state; and The power supply mode of the vehicle is IGOFF; and The bonnet of the vehicle is in a closed state; and The upgrade management module receives a second power replenishment status from the vehicle controller or the power domain controller, and the second power replenishment status indicates that the power battery fails to replenish the storage battery.

5. A vehicle software OTA upgrade method, characterized in that: The method comprises: In response to receiving a power replenishment request from the upgrade management module of the vehicle, the vehicle controller or the power domain controller obtains the remaining power of the power battery; If the remaining power of the power battery is less than a second threshold, the vehicle controller or the power domain controller sends an upper high voltage request, the upper high voltage request is used to start the engine, and replenish the power battery based on the engine, so that the remaining power of the power battery is greater than or equal to the second threshold; In response to the remaining power of the power battery being greater than or equal to the second threshold, the engine is turned off, the power battery is controlled to recharge the storage battery, and a first recharging status is sent to the upgrade management module to trigger the upgrade management module to start OTA upgrade of the software to be upgraded, wherein the first recharging status indicates that the power of the storage battery has reached a preset power threshold.

6. The method according to claim 5, characterized in that The method further comprises: If the vehicle controller or the power domain controller confirms that the second target condition is met, the vehicle controller or the power domain controller sends a lower high voltage request and sends a second power replenishment status to the upgrade management module, and the second power replenishment status indicates that the power battery has failed to replenish the battery.

7. The method according to claim 6, characterized in that The second target condition includes: The remaining power of the power battery is less than the first threshold, and the first threshold is less than the second threshold; The vehicle has a high voltage power failure; A DC-DC converter in the vehicle does not operate after being enabled; No power replenishment request sent by the upgrade management module is received after a specified time; The vehicle receives a charging wake-up signal; The vehicle is in an unarmed state; The power supply mode of the vehicle is not IGOFF; The hood of the vehicle is in at least one of the open states.

8. A vehicle software OTA upgrade method, characterized in that: The method comprises: In response to receiving a power replenishment request from the upgrade management module of the vehicle, the vehicle controller or the power domain controller obtains the remaining power of the power battery; If the remaining power of the power battery is greater than or equal to the first threshold, the vehicle controller or the power domain controller sends a high-voltage request, and the high-voltage request is used to enable the power battery of the vehicle to supplement the battery; In response to the power battery replenishing power for the storage battery, a first replenishing power state is sent to the upgrade management module to trigger the upgrade management module to start OTA upgrade of the software to be upgraded, and the first replenishing power state indicates that the power of the storage battery reaches a preset power threshold.

9. The method according to claim 8, characterized in that The method further comprises: If the vehicle controller or the power domain controller confirms that the second target condition is met, the vehicle controller or the power domain controller sends a lower high voltage request and sends a second power replenishment status to the upgrade management module, and the second power replenishment status indicates that the power battery has failed to replenish the battery.

10. The method according to claim 9, characterized in that The second target condition includes: The remaining power of the power battery is less than the first threshold; The vehicle has a high voltage power failure; A DC-DC converter in the vehicle does not operate after being enabled; No power replenishment request sent by the upgrade management module is received after a specified time; The vehicle receives a charging wake-up signal; The vehicle is in an unarmed state; The power supply mode of the vehicle is not IGOFF; The hood of the vehicle is in at least one of the open states.

11. A vehicle software OTA upgrade device, characterized in that: The device comprises: An information acquisition unit, configured to, in response to receiving a software OTA upgrade instruction, enable an upgrade management module in the vehicle to acquire a type of controller where the software to be upgraded is located and an upgrade time required for the software to be upgraded; A power replenishment request sending unit, configured to, if the type of the controller where the software to be upgraded is located is a type that supports upper high voltage, and the upgrade time required for the software to be upgraded is greater than or equal to a preset time, the upgrade management module sends a power replenishment request to the vehicle controller or the power domain controller, and the power replenishment request is used to trigger the vehicle's power battery to replenish the battery; The software upgrade unit is used to respond to receiving a first power replenishment state from the vehicle controller or the power domain controller, and the upgrade management module starts OTA upgrading the software to be upgraded, wherein the first power replenishment state indicates that the power of the battery reaches a preset power threshold.

12. A vehicle software OTA upgrade device, characterized in that: The device comprises: A remaining power acquisition unit, configured to obtain the remaining power of the power battery by the vehicle controller or the power domain controller in response to receiving a power replenishment request from the upgrade management module of the vehicle; an upper high voltage request sending unit, configured to, if the remaining power of the power battery is less than a second threshold, cause the vehicle controller or the power domain controller to send an upper high voltage request, wherein the upper high voltage request is used to start the engine and supplement the power battery based on the engine so that the remaining power of the power battery is greater than or equal to the second threshold; A power replenishment status sending unit is used to shut down the engine and control the power battery to replenish the battery in response to the remaining power of the power battery being greater than or equal to the second threshold, and to send a first power replenishment status to the upgrade management module to trigger the upgrade management module to start OTA upgrade of the software to be upgraded, wherein the first power replenishment status indicates that the power of the battery has reached a preset power threshold.

13. A vehicle software OTA upgrade device, characterized in that: The device comprises: A remaining power acquisition unit, configured to obtain the remaining power of the power battery by the vehicle controller or the power domain controller in response to receiving a power replenishment request from the upgrade management module of the vehicle; an upper high voltage request sending unit, configured to, if the remaining power of the power battery is greater than or equal to a first threshold, cause the vehicle controller or the power domain controller to send an upper high voltage request, wherein the upper high voltage request is used to enable the power battery of the vehicle to supplement the battery; A charging status sending unit is used to send a first charging status to the upgrade management module in response to the power battery charging the storage battery, so as to trigger the upgrade management module to start OTA upgrading the software to be upgraded, and the first charging status indicates that the power of the storage battery reaches a preset power threshold.

14. A vehicle, characterized in that: Including upgrade management module, vehicle controller or power and controller, and memory; One or more programs are stored in the memory and configured to be executed by the upgrade management module or the vehicle controller or the power domain controller, and the one or more programs are configured to execute any of the methods described in claims 1-4 or 5-10.

15. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores program code, wherein when the program code is run, the method according to any one of claims 1 to 10 is executed.

Citation Information

Cited By

  • DCDC converter control method

    CN121375485A