Power battery management method and system, vehicle and storage medium

By integrating multiple power battery management software into the domain controller, the problems of complex power battery management software versions and high hardware costs are solved, achieving cost reduction and safety improvement.

CN120621154APending Publication Date: 2025-09-12DEEPAL AUTOMOBILE TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202511039564.0
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2025-07-28
Publication Date
2025-09-12

AI Technical Summary

Technical Problem

In the existing technology, the power battery management software versions of new energy vehicles are complex, resulting in high development, testing and maintenance costs, and high BMS motherboard hardware costs, which limits the room for cost reduction.

Method used

Multiple power battery management software are pre-installed in the domain controller. By obtaining the matching battery configuration parameters of the power battery control unit and the domain controller, the corresponding software is selected to run, reducing hardware requirements and unifying development, testing, and maintenance.

Benefits of technology

It reduces the version management difficulty and hardware cost of power battery management software, improves operational safety and maintenance efficiency, and simplifies version management.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN120621154A_ABST
    Figure CN120621154A_ABST
Patent Text Reader

Abstract

The invention relates to a power battery management method. The method comprises the following steps: acquiring a first battery configuration parameter stored in a power battery control unit of a vehicle and a second battery configuration parameter stored in a domain controller of the vehicle; and when the first battery configuration parameter is consistent with the second battery configuration parameter, running preset power battery management software corresponding to the first battery configuration parameter in a plurality of preset power battery management software preset in the domain controller. The invention further provides a power battery management system, a vehicle and a storage medium. According to the power battery management scheme provided by the invention, the development, test and maintenance cost of the battery management software can be reduced, and the version management difficulty of the battery management software can be reduced. By adopting the power battery management scheme provided by the invention, the hardware cost of the power battery pack can be reduced.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the field of vehicle technology, and in particular to a power battery management method, system, vehicle and storage medium. Background Art

[0002] With the gradual reduction of fossil energy and the increasing severity of environmental problems, the development of new energy has become a general trend, and new energy vehicles have also become the development direction of the vehicle industry.

[0003] In existing technologies, the power battery management software for new energy vehicles is usually pre-installed in the BMS (power battery management system) motherboard, which is directly installed inside the power battery pack to monitor and manage the power battery status and ensure safe and reliable operation of the power battery. However, existing power battery management solutions have the following technical problems: Vehicles with different power battery configurations require different versions of power battery management software to be pre-installed on the BMS motherboard. Even vehicles of the same model with different power battery configurations require different versions of power battery management software to be pre-installed on the BMS motherboard. This increases the number and versions of power battery management software, which in turn increases software development, testing, and maintenance costs, and makes software version management extremely complex. A BMS motherboard is set inside the power battery pack, and the hardware cost of the BMS motherboard is relatively high, which restricts the cost reduction space of the power battery pack and even the entire vehicle. Summary of the Invention

[0004] The object of the present invention is to provide a power battery management method, system, vehicle and storage medium to alleviate or eliminate at least one of the above-mentioned technical problems.

[0005] A power battery management method according to the present invention comprises the following steps: Obtaining a first battery configuration parameter stored in a power battery control unit of a vehicle and a second battery configuration parameter stored in a domain controller of the vehicle; When the first battery configuration parameter is consistent with the second battery configuration parameter, the preset power battery management software corresponding to the first battery configuration parameter among the multiple preset power battery management software preset in the domain controller is run.

[0006] Optionally, after obtaining the first battery configuration parameters stored in the power battery control unit of the vehicle and the second battery configuration parameters stored in the domain controller of the vehicle, the following steps are also included: when the first battery configuration parameters are inconsistent with the second battery configuration parameters, a battery configuration parameter verification fault is reported.

[0007] Optionally, when it is identified that the first battery configuration parameter is inconsistent with the second battery configuration parameter, the method further includes the following steps: prohibiting high voltage from being applied to the vehicle.

[0008] Optionally, after reporting the battery configuration parameter verification failure, the method further includes the following steps: In response to the power battery control unit and the domain controller being powered off and then powered on again, the battery configuration parameter verification fault is cleared.

[0009] Optionally, the method includes the following steps: in response to the power battery control unit and the domain controller being powered on, executing the acquisition of the first battery configuration parameters stored in the power battery control unit of the vehicle and the second battery configuration parameters stored in the domain controller of the vehicle.

[0010] Optionally, the following steps are included: when the second battery configuration parameter is empty, running the default power battery management software pre-installed in the domain controller, and the default power battery management software supports writing the second battery configuration parameter to the domain controller.

[0011] Optionally, the plurality of pre-installed power battery management software correspond one-to-one to a plurality of power battery configurations of the same vehicle model.

[0012] The present invention also proposes a power battery management system, which is characterized by comprising: an acquisition module, configured to acquire a first battery configuration parameter stored in a power battery control unit of a vehicle and a second battery configuration parameter stored in a domain controller of the vehicle; A management module is used to: when the first battery configuration parameter is consistent with the second battery configuration parameter, run the preset power battery management software corresponding to the first battery configuration parameter among the multiple preset power battery management software preset in the domain controller.

[0013] The present invention also provides a vehicle comprising the above-mentioned power battery management system.

[0014] The present invention further provides a storage medium, in which a computer program is stored. When the computer program is executed by a processor, any of the above-mentioned power battery management methods is implemented.

[0015] The power battery management solution proposed in this invention can reduce the development, testing, and maintenance costs of battery management software, and can reduce the difficulty of version management of battery management software. The power battery management solution proposed in this invention helps reduce the hardware cost of power battery packs. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] Figure 1is a flow chart of the power battery management method described in some embodiments; Figure 2 This is a flowchart of the power battery management method described in some examples; Figure 3 Schematic diagram of the power battery management system described in some embodiments.

[0017] In the figure, 10 is a power battery management system, 20 is an acquisition module, and 30 is a management module. DETAILED DESCRIPTION

[0018] The following describes the embodiments of the present invention with reference to the accompanying drawings and preferred embodiments. Those skilled in the art will readily appreciate the other advantages and benefits of the present invention from the disclosure herein. The present invention may also be implemented or applied through various other specific embodiments, and the various details in this specification may be modified or altered based on different viewpoints and applications without departing from the spirit of the present invention. It should be understood that the preferred embodiments are intended only to illustrate the present invention and are not intended to limit the scope of protection of the present invention.

[0019] It should be noted that the illustrations provided in the following embodiments are merely schematic illustrations of the basic concept of the present invention. The illustrations only show components related to the present invention and are not drawn according to the number, shape, and size of components in actual implementation. In actual implementation, the type, quantity, and proportion of each component may be changed arbitrarily, and the component layout may also be more complex.

[0020] like Figure 1 A power battery management method shown includes the following steps: S100: Acquire a first battery configuration parameter stored in a power battery control unit of a vehicle and a second battery configuration parameter stored in a domain controller of the vehicle; S200: When the first battery configuration parameter is consistent with the second battery configuration parameter, running the preset power battery management software corresponding to the first battery configuration parameter among the plurality of preset power battery management software preset in the domain controller.

[0021] By adopting the above-mentioned power battery management method, multiple pre-installed power battery management software can be pre-installed in the domain controller. On the one hand, it can reduce the hardware requirements for the power battery control unit, thereby reducing the hardware cost of the power battery control unit, which helps to reduce the hardware cost of the power battery pack, such as using a high-voltage manager as a power battery control unit; on the other hand, multiple power battery control software can be stored compatibly in the domain controller for unified development, testing, and maintenance, which can reduce the development, testing, and maintenance costs of the battery management software and reduce the difficulty of version management of the battery management software.

[0022] By adopting the above-mentioned power battery management method, the corresponding preset power battery management software is determined according to the matching result of the first battery configuration parameter and the second battery configuration parameter, which can ensure the safety of the power battery pack and the vehicle operation.

[0023] In some embodiments, after obtaining the first battery configuration parameters stored in the vehicle's power battery control unit and the second battery configuration parameters stored in the vehicle's domain controller, the following step is further included: when the first battery configuration parameters are inconsistent with the second battery configuration parameters, reporting a battery configuration parameter verification failure. The above technical solution can provide safety redundancy, prevent software and hardware mismatches, and ensure the safe operation of the power battery pack and vehicle.

[0024] During specific implementation, it can be determined whether the first battery configuration parameters and the second battery configuration parameters are consistent. When the judgment result is consistent, the preset power battery management software corresponding to the first battery configuration parameters among the multiple preset power battery management software preset in the domain controller is run. When the judgment result is inconsistent, a battery configuration parameter verification failure is reported to prevent damage to the power battery pack and the vehicle.

[0025] In some embodiments, when the first battery configuration parameter is inconsistent with the second battery configuration parameter, the further step of: prohibiting high voltage from being applied to the vehicle is included. The above technical solution helps ensure the safe operation of the power battery pack and the vehicle and prevents damage to the power battery pack and the vehicle.

[0026] As a specific example, Figure 2 As shown, the power battery management method includes the following steps: S100: Acquire a first battery configuration parameter stored in a power battery control unit of a vehicle and a second battery configuration parameter stored in a domain controller of the vehicle; S200: When the first battery configuration parameter is consistent with the second battery configuration parameter, running the preset power battery management software corresponding to the first battery configuration parameter among the plurality of preset power battery management software preset in the domain controller; S300: When the first battery configuration parameter is inconsistent with the second battery configuration parameter, a battery configuration parameter verification fault is reported, and the vehicle is prohibited from applying high voltage.

[0027] In some embodiments, after a battery configuration parameter verification fault is reported, the system further includes the following steps: In response to powering off and then on the power battery control unit and domain controller, the battery configuration parameter verification fault is cleared. Using the above technical solution, after a battery configuration parameter verification fault is reported, a cold restart of the power battery control unit and domain controller is performed, and the battery configuration parameter verification fault is cleared, achieving a state reset. This distinguishes between transient interference and actual faults, prevents system lockup caused by transient interference, and supports fault reset after maintenance.

[0028] Furthermore, after clearing the battery configuration parameter verification fault, the first battery configuration parameter stored in the vehicle's power battery control unit and the second battery configuration parameter stored in the vehicle's domain controller are re-acquired; when the first battery configuration parameter is consistent with the second battery configuration parameter, the preset power battery management software corresponding to the first battery configuration parameter among the multiple preset power battery management software preset in the domain controller is run; when the first battery configuration parameter is inconsistent with the second battery configuration parameter, a battery configuration parameter verification fault is reported, and the vehicle is prohibited from applying high voltage.

[0029] Furthermore, in order to help ensure the safe operation of the power battery pack and the vehicle, after reporting a battery configuration parameter verification fault, when the power battery control unit and the domain controller are not recognized to be powered off and then powered on, the battery configuration parameter verification fault will continue to be reported, and the vehicle will be prohibited from applying high voltage.

[0030] It should be noted that the power-off of the power battery control unit and the domain controller is low-voltage power-off, and the power-on of the power battery control unit and the domain controller is low-voltage power-on.

[0031] In some embodiments, a power battery management method includes the following steps: in response to powering on a power battery control unit and a domain controller, obtaining first battery configuration parameters stored in the vehicle's power battery control unit and second battery configuration parameters stored in the vehicle's domain controller. During the power-on initialization process of the power battery control unit and the domain controller, matching the first and second battery configuration parameters helps ensure the safe operation of the power battery pack and the vehicle.

[0032] In some embodiments, the power battery management method includes the following steps: when the second battery configuration parameter is empty, running default power battery management software pre-installed in the domain controller, the default power battery management software supporting writing the second battery configuration parameter to the domain controller. Typically, if the second battery configuration parameter is empty, it means that the relevant battery configuration parameter has not yet been written. The above technical solution solves the initialization problem when the power battery system is used for the first time or when the parameters are lost, ensuring that the vehicle has basic operating capabilities.

[0033] In some embodiments, multiple pre-installed power battery management software programs correspond to multiple power battery configurations for the same vehicle model. Existing domain controllers are capable of supporting and storing pre-installed power battery management software programs for multiple power battery configurations for the same vehicle model. Centrally storing all battery management software programs for the same vehicle model in the domain controller facilitates unified management, updates, and functional upgrades via vehicle-wide OTA, improving maintenance efficiency and user experience.

[0034] As a specific example, the power battery management method includes the following steps: The power battery control unit and domain controller complete low-voltage power-up; The domain controller sends the second battery configuration parameter, and the power battery control unit sends the first battery configuration parameter; During the initialization of the power battery control unit and the domain controller, the power battery control unit determines whether the second battery configuration parameters stored in the domain controller are empty. If empty, it means that the relevant battery configuration parameters have not been written yet, and then runs the default power battery management software, which can support writing the second battery configuration parameters; If it is detected that the second battery configuration parameter is not empty, the power battery control unit determines whether the second battery configuration parameter stored in the domain controller is the same as the first battery configuration parameter. If they are the same, the preset power battery management software corresponding to the first battery configuration parameter and the second battery configuration parameter is run; If the second battery configuration parameter stored in the domain controller is different from the first battery configuration parameter, the domain controller will report a battery configuration parameter verification fault and prohibit the entire vehicle from being powered on at high voltage; the domain controller and the power battery control unit will be simultaneously judged whether they are powered off at low voltage and then powered on at low voltage. If so, the domain controller will clear the battery configuration parameter verification fault. Otherwise, the domain controller will continue to report a battery configuration parameter verification fault and prohibit the vehicle from being powered on at high voltage.

[0035] like Figure 3 As shown, the present invention also proposes a power battery management system 10, comprising: an acquisition module 20 for acquiring a first battery configuration parameter stored in a power battery control unit of the vehicle and a second battery configuration parameter stored in a domain controller of the vehicle; The management module 30 is configured to: when the first battery configuration parameter is consistent with the second battery configuration parameter, run the preset power battery management software corresponding to the first battery configuration parameter among the plurality of preset power battery management software preset in the domain controller.

[0036] In some embodiments, the management module 30 is further configured to: when the first battery configuration parameter is inconsistent with the second battery configuration parameter, report a battery configuration parameter verification failure and prohibit the vehicle from being on high voltage.

[0037] In some embodiments, the management module 30 is further configured to: after reporting a battery configuration parameter verification fault, clear the battery configuration parameter verification fault in response to the power battery control unit and the domain controller being powered off and then powered on again.

[0038] In some embodiments, the management module 30 is further used to: after reporting a battery configuration parameter verification failure, when it is not recognized that the power battery control unit and the domain controller are powered off and then powered on, continue to report the battery configuration parameter verification failure and prohibit the vehicle from applying high voltage.

[0039] In some embodiments, the management module 30 is further used to: in response to power-on of the power battery control unit and the domain controller, execute acquisition of first battery configuration parameters stored in the power battery control unit of the vehicle and second battery configuration parameters stored in the domain controller of the vehicle.

[0040] In some embodiments, the management module 30 is further used to: when the second battery configuration parameter is empty, run the default power battery management software pre-installed in the domain controller, and the default power battery management software supports writing the second battery configuration parameter to the domain controller.

[0041] In a specific implementation, the acquisition module 20 and the management module 30 can be configured in the power battery control unit and the domain controller. For example, the management module 30 is configured in the domain controller, and the acquisition module 20 is configured in the power battery control unit. In another example, both the acquisition module 20 and the management module 30 are configured in the power battery control unit. In another example, both the acquisition module 20 and the management module 30 are configured in the domain controller. In another example, the acquisition module 20 is configured in the domain controller, and the management module 30 is configured in the power battery control unit.

[0042] In specific implementations, multiple pre-installed power battery management software programs are integrated into the domain controller. This can be done as multiple independent software programs, with each program stored as an independent executable in a different partition of the domain controller and isolated through the operating system or virtualization layer. Alternatively, it can be a single modular integrated software package, abstracting the management logic of multiple battery configurations into reusable functional modules, integrating them into a main program, and dynamically calling the corresponding modules through configuration parameters.

[0043] In a specific implementation, the domain controller may be a central integrated domain controller of the vehicle. The power battery control unit may be a high-voltage manager arranged in the power battery pack.

[0044] The core of the present invention is to integrate multiple preset power battery management software into the domain controller, and select a low-cost power battery control unit in the power battery pack to perform the acquisition function, for example, a high-voltage manager with low hardware cost is used as the power battery control unit. The preset power battery management software for different battery configurations of the same vehicle model are all embedded in the domain controller. By writing the second battery configuration parameters into the domain controller and the first battery configuration parameters into the power battery control unit, after the domain controller and the power battery control unit are powered on at low voltage, it is determined whether the first battery configuration parameters and the second battery configuration parameters are configured successfully. If the configuration is successful, the corresponding preset power battery management software is called to run. If the configuration is unsuccessful, a battery configuration parameter verification fault is reported. This fault is a high-level fault and prohibits the entire vehicle from being connected to high voltage.

[0045] The present invention also provides a vehicle including the above-mentioned power battery management system. In specific implementations, the vehicle may be, but is not limited to, a pure electric vehicle (PEV / BEV), a hybrid electric vehicle (HEV), a range-extended electric vehicle (REEV), a plug-in hybrid electric vehicle (PHEV), a new energy vehicle (NEV), a fuel-powered vehicle, etc.

[0046] The present invention further provides a storage medium, in which a computer program is stored. When the computer program is executed by a processor, any of the above-mentioned power battery management methods is implemented.

[0047] The above embodiments are merely preferred embodiments for fully illustrating the present invention, and the scope of protection of the present invention is not limited thereto. Equivalent substitutions or transformations made by those skilled in the art on the basis of the present invention are all within the scope of protection of the present invention. In the description of this specification, the descriptions with reference to the terms "one embodiment", "some embodiments", "example", "specific example" or "some examples" etc. mean that the specific features, structures, materials or characteristics of the embodiment or example are included in at least one embodiment or example of the present invention. In this specification, the schematic representations of the above terms do not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials or characteristics described may be combined in any one or more embodiments or examples in a suitable manner. In addition, those skilled in the art may combine and combine the different embodiments or examples described in this specification.

Claims

1. A power battery management method, characterized in that: The following steps are involved: Obtaining a first battery configuration parameter stored in a power battery control unit of a vehicle and a second battery configuration parameter stored in a domain controller of the vehicle; When the first battery configuration parameter is consistent with the second battery configuration parameter, the preset power battery management software corresponding to the first battery configuration parameter among the multiple preset power battery management software preset in the domain controller is run.

2. The power battery management method according to claim 1, characterized in that: After obtaining the first battery configuration parameter stored in the power battery control unit of the vehicle and the second battery configuration parameter stored in the domain controller of the vehicle, the following steps are also included: when the first battery configuration parameter is inconsistent with the second battery configuration parameter, a battery configuration parameter verification fault is reported.

3. The power battery management method according to claim 2, characterized in that: When it is identified that the first battery configuration parameter is inconsistent with the second battery configuration parameter, the method further includes the following steps: prohibiting high voltage from being applied to the vehicle.

4. The power battery management method according to claim 2, characterized in that: After the battery configuration parameter verification fault is reported, the following step is also included: in response to the power battery control unit and the domain controller being powered off and then powered on again, the battery configuration parameter verification fault is cleared.

5. The power battery management method according to claim 1, characterized in that: The following steps are involved: In response to the power battery control unit and the domain controller being powered on, the acquiring of the first battery configuration parameter stored in the power battery control unit of the vehicle and the second battery configuration parameter stored in the domain controller of the vehicle is performed.

6. The power battery management method according to claim 1, characterized in that: The following steps are involved: When the second battery configuration parameter is empty, the default power battery management software pre-installed in the domain controller is run, and the default power battery management software supports writing the second battery configuration parameter to the domain controller.

7. The power battery management method according to claim 1, characterized in that: The plurality of pre-installed power battery management software correspond one-to-one to a plurality of power battery configurations of the same vehicle model.

8. A power battery management system (10), characterized in that: include: An acquisition module (20) is used to acquire a first battery configuration parameter stored in a power battery control unit of a vehicle and a second battery configuration parameter stored in a domain controller of the vehicle; A management module (30) is used to: when the first battery configuration parameter is consistent with the second battery configuration parameter, run the preset power battery management software corresponding to the first battery configuration parameter among the plurality of preset power battery management software preset in the domain controller.

9. A vehicle, characterized in that: It comprises a power battery management system (10) as claimed in claim 8.

10. A storage medium, characterized in that: The storage medium stores a computer program, which, when executed by a processor, implements the power battery management method according to any one of claims 1 to 7.