Battery management system fault processing method and device and electronic equipment

Abstract

The embodiment of the invention provides a battery management system fault processing method and device and electronic equipment. The method comprises the following steps: when a fault of a battery management system is output, classifying the fault of the battery management system; the fault response level is adjusted according to the classified battery management system faults; and adopting a corresponding fault processing strategy for the fault of the battery management system after the fault response level is adjusted. According to the embodiment of the invention, the fault response level of the BMS fault can be adaptively adjusted, and different fault processing modes are adopted for the BMS faults of different fault response levels, so that the accuracy of BMS fault detection is improved, the safety of the battery is guaranteed, the service life of the battery is prolonged, and the reliability of the BMS is improved.

Description

Technical Field

[0001] The embodiments of the present invention relate to the technical field of battery management system (BMS) fault handling, and more particularly to a battery management system fault handling method, device, and electronic equipment. Background Art

[0002] In applications such as electric vehicles, reliable BMS fault diagnosis can ensure normal driving and range, reduce breakdowns caused by BMS failures, and improve user experience and satisfaction. BMS fault diagnosis is crucial for ensuring battery safety, extending battery life, improving system reliability, and ensuring user experience.

[0003] Currently, diagnosed BMS faults are handled using a fault classification system. Different fault levels are handled strictly, and once the fault classification is finalized, it remains unchanged. However, battery performance is constantly changing, and if BMS faults are still handled using the previous fault classification system, they will not be able to adapt to the changing battery performance. Summary of the Invention

[0004] In a first aspect, an embodiment of the present invention provides a battery management system fault handling method, comprising:

[0005] When a battery management system fault is output, classify the battery management system fault;

[0006] Adjust the fault response level for classified battery management system faults;

[0007] For battery management system faults after adjusting the fault response level, adopt corresponding fault handling strategies.

[0008] In a possible implementation, when a battery management system fault is output, classifying the battery management system fault includes:

[0009] When a battery management system fault is output, if the battery management system fault is a non-collision fault, a non-thermal runaway fault, and a non-insulation fault, the battery management system fault is classified.

[0010] In a possible implementation, when a battery management system fault is output, classifying the battery management system fault includes:

[0011] When a battery management system fault is output, the battery management system fault is classified according to the fault code of the battery management system fault.

[0012] In a possible implementation, when a battery management system fault is output, classifying the battery management system fault includes:

[0013] When a battery management system fault is output, the battery management system fault is classified according to the fault diagnosis conditions.

[0014] In a possible implementation, the battery management system fault categories include flag type faults and threshold type faults.

[0015] In a possible implementation, adjusting the fault response level for the classified battery management system fault includes:

[0016] If the classified battery management system fault is a flag type fault, and the frequency of occurrence of the flag type fault within the first preset time period is greater than the first preset frequency threshold, the frequency increase flag of the flag type fault is increased by 1 accordingly; if the cumulative count of the frequency increase flag is greater than the first preset count threshold, the fault response level is increased by 1 accordingly; and / or

[0017] If the classified battery management system fault is a flag type fault, and the frequency of occurrence of the flag type fault within the second preset time period is less than the second preset frequency threshold, the frequency reduction flag of the flag type fault is reduced by 1 accordingly; if the cumulative count of the frequency reduction flag is greater than the second preset count threshold, the fault response level is reduced by 1 accordingly.

[0018] In a possible implementation, adjusting the fault response level for the classified battery management system fault includes:

[0019] If the classified battery management system fault is a threshold type fault, and the fault response threshold at the first time point is less than the fault response threshold at the second time point, and the fault response threshold at the first time point is greater than the historical fault threshold, then the fault response threshold increase flag of the threshold type fault is correspondingly increased by 1; if the cumulative count of the fault response threshold increase flag is greater than a third preset count threshold, then the fault response level is correspondingly increased by 1, and the second time point is later than the first time point; and / or

[0020] If the classified battery management system fault is a threshold type fault, and the fault response threshold at the third time point is greater than the fault response threshold at the fourth time point, and the fault response threshold at the third time point is less than the historical fault threshold, then the fault response threshold reduction flag of the threshold type fault is correspondingly reduced by 1; if the cumulative count of the fault response threshold reduction flag is greater than the fourth preset count threshold, then the fault response level is correspondingly reduced by 1, and the fourth time point is later than the third time point.

[0021] In a possible implementation, the fault response level includes six levels;

[0022] The corresponding fault handling strategy is adopted for the battery management system fault after the fault response level is adjusted, including:

[0023] If the fault response level of the battery management system fault after the fault response level is adjusted is level one, a fault code is sent without reducing the power of the battery management system;

[0024] If the fault response level of the battery management system fault after the fault response level is adjusted is level 2, level 3, or level 4, a fault code is sent and the power of the battery management system is reduced at a first preset rate, a second preset rate, a third preset rate, and a first preset ratio, a second preset ratio, and a third preset ratio, respectively;

[0025] If the fault response level of the battery management system fault after the fault response level is adjusted is level five, a fault code is sent and the power of the battery management system is reduced to 0 at a fourth preset rate; or

[0026] If the fault response level of the battery management system fault after the fault response level is adjusted is level six, a fault code is sent and the power of the battery management system is immediately reduced to 0.

[0027] In a second aspect, an embodiment of the present invention provides a battery management system fault handling device, comprising:

[0028] a classification unit, configured to classify the battery management system fault when a battery management system fault output is generated;

[0029] An adjustment unit, used to adjust a fault response level according to a classified battery management system fault;

[0030] The processing unit is used to adopt a corresponding fault processing strategy for the battery management system fault after the fault response level is adjusted.

[0031] In a third aspect, an embodiment of the present invention provides an electronic device, including:

[0032] A memory and a processor, wherein the processor and the memory communicate with each other via a bus; the memory stores program instructions that can be executed by the processor, and the processor calls the program instructions to execute the method described in the first aspect and each step in various possible implementations.

[0033] In a fourth aspect, an embodiment of the present invention provides a storage medium having a computer program stored thereon, which, when executed by a processor, implements the method described in the first aspect and each step in various possible implementations.

[0034] In a fifth aspect, an embodiment of the present invention provides a computer program product comprising instructions, which, when the computer program product is run on a computer, enables the method described in the first aspect to be executed by the computer.

[0035] The embodiments of the present invention provide the following technical effects:

[0036] The embodiments of the present invention can adaptively adjust the fault response level of a BMS fault and adopt different fault handling methods for BMS faults with different fault response levels, thereby improving the accuracy of BMS fault detection, which plays an important role in ensuring battery safety, extending battery life, and improving the reliability of the BMS.

[0037] Of course, any product implementing the present invention does not necessarily need to achieve all of the advantages described above at the same time. BRIEF DESCRIPTION OF THE DRAWINGS

[0038] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the following is a brief introduction to the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0039] Figure 1 A diagram of a system architecture applicable to an embodiment of the present invention;

[0040] Figure 2 A flowchart of a battery management system fault handling method provided by an embodiment of the present invention;

[0041] Figure 3 A flowchart of another method for troubleshooting a battery management system provided by an embodiment of the present invention;

[0042] Figure 4 A schematic block diagram of a battery management system fault handling device provided by an embodiment of the present invention;

[0043] Figure 5 A schematic block diagram of an electronic device provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0044] To make the objectives, technical solutions, and advantages of the embodiments of the present invention more clear, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the accompanying drawings of the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. All other embodiments obtained by ordinary technicians in this field based on the embodiments of the present invention without making any creative efforts shall fall within the scope of protection of the present invention.

[0045] The terms used in the embodiments of the present invention are only for the purpose of describing specific embodiments and are not intended to limit the present invention. The singular forms "a", "an", "the" and "the" used in the embodiments of the present invention and the appended claims are also intended to include plural forms unless the context clearly indicates otherwise.

[0046] It should be understood that the term "and / or" as used herein is merely a description of the relationship between associated objects, indicating that three possible relationships exist. For example, "A and / or B" can represent: A exists alone, A and B exist simultaneously, or B exists alone. Furthermore, the character " / " in this document generally indicates that the associated objects are in an "or" relationship.

[0047] The word "if," as used herein, may be interpreted as "at the time of" or "when" or "in response to determining" or "in response to detecting," depending on the context. Similarly, the phrases "if it is determined" or "if monitoring (stated condition or event)" may be interpreted as "when it is determined" or "in response to determining" or "when detecting (stated condition or event)" or "in response to detecting (stated condition or event)," depending on the context.

[0048] Currently, diagnosed BMS faults are handled using a fault level classification method. Fault levels are defined according to a fault list and written to the BMS. Once the fault level is classified, it remains unchanged. However, battery performance is constantly changing, and so are fault levels. This can cause the fault levels defined in the fault list to no longer reflect the actual BMS fault. Clearly, mainstream BMS fault handling methods are no longer suitable for the reality of constantly changing battery performance and fault levels.

[0049] In view of this, the embodiment of the present invention provides a new idea. In order to facilitate the understanding of the present application, the system architecture based on the embodiment of the present invention is first described. Figure 1 An exemplary system architecture to which embodiments of the present invention may be applied is shown. Figure 1 As shown in , the system architecture may include a terminal device and a battery management system fault processing device located on the server side.

[0050] Terminal devices may include, but are not limited to, smart mobile terminals, smart home devices, wearable devices, and personal computers (PCs). Smart mobile terminals may include mobile phones, tablets, laptops, PDAs (Personal Digital Assistants), and internet-connected cars. Smart home devices may include smart TVs and smart refrigerators. Wearable devices may include smart watches, smart glasses, virtual reality devices, augmented reality devices, and mixed reality devices (i.e., devices that support both virtual reality and augmented reality).

[0051] The battery management system fault processing device can use the battery management system fault processing method provided in the embodiment of the present invention to process the battery management system fault and output whether the battery management system fault has been processed.

[0052] The battery management system fault handling device can be set up in a single server, a server group consisting of multiple servers, or a cloud server. A cloud server, also known as a cloud computing server or cloud host, is a host product in the cloud computing service system to solve the problems of difficult management and weak service scalability in traditional physical hosts and virtual private servers (VPS). Figure 1 In addition to the shown architecture, the battery management system fault processing device can also be set on a computer terminal with strong computing capabilities.

[0053] Figure 2 A flowchart of a battery management system fault handling method provided by an embodiment of the present invention can be Figure 1 The battery management system fault processing device in the system shown is executed. Figure 2 As shown in , the method may include the following steps:

[0054] Step 201: When a battery management system fault is output, classify the battery management system fault.

[0055] Step 202: Adjust the fault response level according to the classified battery management system fault.

[0056] Step 203: adopting a corresponding fault handling strategy for the battery management system fault after adjusting the fault response level.

[0057] The following describes in detail each step of the above process and the effects that can be further produced, in conjunction with embodiments of the present invention. It should be noted that the "first" and "second" definitions involved in the embodiments of the present invention do not have limitations in terms of size, order, or quantity, and are only used to distinguish them in name. For example, "first preset frequency threshold" and "second preset frequency threshold" are used to distinguish two different frequency thresholds.

[0058] First, the above step 201, ie, "classifying the battery management system fault when there is a battery management system fault output" is described in detail in conjunction with an embodiment of the present invention.

[0059] In an embodiment of the present invention, when a BMS fault is output, its fault code, fault response level and parameter status when the BMS fault occurs are recorded, and the above fault information is promptly stored in a non-volatile memory (NVM), and then saved to a BMS fault database. Among them, the above parameter status refers to the fault threshold when a BMS fault occurs. For example, when a cell voltage difference fault occurs, the corresponding fault threshold is 300mV. In other words, when the cell voltage difference is greater than 300mV, for example, when the cell voltage difference is 320mV, a cell voltage difference fault will be output. Accordingly, the current cell voltage difference (320mV) will be stored in the BMS fault database as a new fault threshold. If a cell voltage difference fault occurs again, for example, the cell voltage difference is 330mV, it means that the cell voltage difference (320mV) is more serious than the previous cell voltage difference fault.

[0060] In the embodiment of the present invention, the output BMS faults are classified.

[0061] Specifically, when there is a BMS fault output, if the BMS fault is a non-collision fault, a non-thermal runaway fault, and a non-insulation fault, the BMS fault is classified. It is understandable that collision faults, thermal runaway faults, and insulation faults can be identified based on the fault code. Collision faults, thermal runaway faults, and insulation faults can also be identified based on diagnostic conditions. For example, if the minimum value of the battery cell voltage difference is less than 1.5V and lasts for 500ms, and the battery cell temperature is greater than 85°C and lasts for 2s, it is determined to be a thermal runaway fault. If the insulation impedance value is less than or equal to 500Ω / V (when the high-voltage relay is disconnected), and the time lasts for greater than or equal to 40s, it is determined to be an insulation fault.

[0062] As a possible implementation manner, when a BMS fault is output, the BMS fault is classified according to the fault code of the BMS fault.

[0063] It should be noted that the fault code is the unique identifier of the BMS fault. The fault code can be used to identify the type of BMS fault.

[0064] For example, 1001 represents a VCU communication loss fault, 1002 represents an OBC communication fault, 1003 represents a fast charging communication fault, 1004 represents a daisy chain communication fault, and 1005 represents a current sensor communication fault. The faults represented by 1001 to 1005 above are all communication abnormality or loss faults, and communication abnormality or loss faults belong to communication type faults, and communication type faults belong to flag type faults. 2001 represents a battery cell over-voltage or under-voltage fault, 2002 represents an over-temperature fault, 2003 represents an over-power fault, 2004 represents a battery cell excessive voltage difference fault, and 2005 represents a battery cell excessive temperature difference fault. The faults represented by 2001-2005 above are all threshold type faults.

[0065] That is, the embodiment of the present invention divides BMS faults into flag type faults and threshold type faults.

[0066] As another possible implementation, when there is a BMS fault output, the BMS fault is classified according to the fault diagnosis conditions.

[0067] Exemplarily, the diagnostic condition for a virtual communication unit (VCU) communication loss fault is that the BMS receives a VCU no communication flag flag = 1. In other words, the BMS receives a VCU no communication flag flag = 1, indicating that a VCU communication loss fault has occurred. A VCU communication loss fault is a communication abnormality or loss fault, which is a communication type fault, and a communication type fault is a flag type fault. Exemplarily, the diagnostic condition for a cell overtemperature fault is that the cell temperature is greater than 70°C. The diagnostic condition for a cell temperature difference fault is that the cell temperature difference is greater than 60°C.

[0068] Threshold-type faults are mainly related to the performance of the battery itself, and the diagnostic conditions that determine whether the battery performance is normal are related to the threshold.

[0069] For example, the diagnostic condition for a cell discharge overpower fault is that the current discharge power is greater than the power*factor in the cell parameter table. In other words, when the current discharge power is greater than the power*factor in the cell parameter table, it indicates that a cell discharge overpower fault has occurred.

[0070] The above step 202 , namely “adjusting the fault response level for the classified battery management system fault”, is described in detail below in conjunction with an embodiment of the present invention.

[0071] In an embodiment of the present invention, if the classified BMS fault is a non-collision fault, a non-thermal runaway fault, and a non-insulation fault, the fault response level is adjusted. It should be noted that collision faults, thermal runaway faults, and insulation faults can be identified based on the fault code. For example, the fault code for a collision fault is 3001, the fault code for a thermal runaway fault is 4001, and the fault code for an insulation fault is 5001. Collision faults, thermal runaway faults, and insulation faults can also be identified based on fault diagnosis conditions. For example, if the minimum value of the battery cell voltage difference is less than 1.5V and lasts for 500ms, and the battery cell temperature is greater than 85°C and lasts for 2s, it is determined to be a thermal runaway fault. If the insulation impedance value is less than or equal to 500Ω / V (when the high-voltage relay is disconnected), and the duration of this situation is greater than or equal to 40s, it is determined to be an insulation fault.

[0072] In this embodiment of the present invention, if a classified BMS fault is a flag-type fault and its occurrence frequency increases dramatically within a certain period of time, it indicates that the classified BMS fault is on a development trend. If the occurrence frequency of the classified BMS fault within a first preset time period exceeds a first preset frequency threshold, the frequency increase flag of the classified BMS fault is incremented by 1. If the cumulative count of the frequency increase flag exceeds the first preset count threshold, the fault response level is incremented by 1.

[0073] For example, the first preset time period is set to one driving cycle, the first preset frequency domain threshold is set to three times, and the first preset count threshold is set to ten times. If a classified BMS fault occurs three or more times within a driving cycle, the frequency increase flag for the classified BMS fault is incremented by one. Accordingly, if a classified BMS fault occurs three or more times within a subsequent driving cycle, the frequency increase flag is also incremented by one. When the frequency increase flag accumulates to ten or more times, the fault response level is automatically increased. For example, the fault response level may be incremented by one.

[0074] In this embodiment of the present invention, if a classified BMS fault is a flag-type fault and its occurrence frequency slows over a certain period of time, it indicates that the fault is intermittent and is on a decreasing trend. If the occurrence frequency of the classified BMS fault within a second preset time period is less than a second preset frequency threshold, the frequency reduction flag of the classified BMS fault is decremented by 1 accordingly. If the accumulated count of the frequency reduction flag exceeds the second preset count threshold, the fault response level is decremented by 1 accordingly.

[0075] For example, the second preset time period is set to ten driving cycles, the second preset frequency threshold is set to one, and the second preset count threshold is set to ten. If, within ten driving cycles, the classified BMS fault does not occur or occurs only once, the frequency reduction flag for the classified BMS fault is decremented by one. Accordingly, within the following ten driving cycles, if the classified BMS fault does not occur or occurs only once, the frequency reduction flag is also decremented by one. If the frequency reduction flag accumulates more than ten times, the fault response level is automatically lowered. For example, the fault response level may be decremented by one.

[0076] In an embodiment of the present invention, if a classified BMS fault is a threshold-type fault, the fault response threshold at a first time point is lower than the fault response threshold at a second time point, and the fault response threshold at the first time point is higher than the historical fault threshold, then the fault response threshold-increased flag for the classified BMS fault is incremented by 1, and the fault response threshold at the first time point is stored as the new fault threshold in the BMS fault database. If the classified BMS fault reoccurs and the fault response threshold is higher than the new fault threshold (i.e., the fault response threshold at the first time point), the fault response threshold-increased flag for the classified BMS fault is also incremented by 1. If the cumulative count of the fault response threshold-increased flag exceeds a third preset count threshold, the fault response level is incremented by 1, and the second time point is later than the first time point. In other words, for a classified BMS fault, if the fault response threshold is higher than the historical fault threshold and is on an increasing trend, the fault response threshold-increased flag is incremented by 1. If the cumulative count of the fault response threshold-increased flag exceeds the third preset count threshold, the fault response threshold is increased, and the fault response level is automatically modified and increased. For example, the fault response level can be incremented by 1. For example, the historical fault threshold is 100mV and the fault response threshold is 120mV. Since 120mV is greater than 100mV, a threshold-type fault is determined to have occurred, and 120mV is stored as the new fault threshold in the BMS fault database. The next time the fault response threshold exceeds 120mV, for example, 150mV, a threshold-type fault is determined to have occurred, and 150mV is similarly stored as the new fault threshold in the BMS fault database. Similarly, as the fault threshold increases and maintains an upward trend, the fault response threshold also increases. When the accumulated count of the fault response threshold increase flag exceeds a third preset count threshold, the fault response level is automatically modified and increased.

[0077] The fault response threshold is the real-time physical value when a fault occurs, and the fault threshold is the critical value that can trigger a fault as specified in the fault list in the BMS fault database.

[0078] In an embodiment of the present invention, if a classified BMS fault is a threshold-type fault, the fault response threshold at the third time point is greater than the fault response threshold at the fourth time point, and the fault response threshold at the third time point is less than the historical fault threshold, then the fault response threshold reduction flag for the classified BMS fault is decremented by 1, and the fault response threshold at the third time point is stored as the new fault threshold in the BMS fault database. If the classified BMS fault reoccurs and the fault response threshold is less than the new fault threshold (i.e., the fault response threshold at the third time point), the fault response threshold reduction flag for the classified BMS fault is also decremented by 1. If the cumulative count of the fault response threshold reduction flag exceeds a fourth preset count threshold, the fault response level is decremented by 1, and the fourth time point is later than the third time point. In other words, for a classified BMS fault, if the fault threshold is lower than the historical fault threshold and is showing a weakening trend, the fault response threshold reduction flag is decremented by 1. If the cumulative count of the fault response threshold reduction flag exceeds the fourth preset count threshold, the fault response threshold is reduced, and the fault response level is automatically modified and lowered. For example, the fault response level may be decremented by 1, but cannot be lower than the initially set fault response level.

[0079] The above step 203, i.e., "adopting a corresponding fault handling strategy for the battery management system fault after the fault response level is adjusted," is described in detail below in conjunction with an embodiment of the present invention.

[0080] In the embodiment of the present invention, illustratively, the fault response levels may include six levels.

[0081] In the embodiment of the present invention, different fault handling strategies are adopted for different levels of battery management system faults.

[0082] As a possible implementation, if the fault response level of the BMS fault after the fault response level is adjusted to level 1, a fault code is sent and the BMS power is not reduced. For a level 1 BMS fault, a fault code is sent and the BMS power is not reduced. If the fault response level of the BMS fault after the fault response level is adjusted to level 2, 3, or 4, a fault code is sent and the BMS power is reduced at a first preset rate, a second preset rate, a third preset rate, and a first preset ratio, a second preset ratio, and a third preset ratio, respectively. For level 2, 3, and 4 BMS faults, a fault code is sent and the BMS power is reduced at different rates and ratios. For a level 5 BMS fault, a fault code is sent and the BMS power is reduced to 0 at a certain rate. If the fault response level of the BMS fault after the fault response level is adjusted to level 5, a fault code is sent and the BMS power is reduced to 0 at a fourth preset rate. For a level 6 BMS fault, a fault code is sent and the BMS power is immediately reduced to 0. Alternatively, if the fault response level of the BMS fault after the fault response level is adjusted to level 6, a fault code is sent and the BMS power is immediately reduced to 0.

[0083] As can be seen from the foregoing, the embodiments of the present invention can adaptively adjust the fault response level of a BMS fault and adopt different fault handling methods for BMS faults with different fault response levels, thereby improving the accuracy of BMS fault detection, ensuring battery safety, extending the battery life, and improving the reliability of the BMS.

[0084] Based on the same concept as the above method embodiment, the embodiment of the present invention provides another method for handling battery management system faults. The flow chart of the method is as follows: Figure 3 This method can be used by Figure 1 The battery management system fault processing device in the system shown is executed. Figure 3 As shown in , the method may include the following steps:

[0085] Step 301: Power on and initialize the BMS.

[0086] In the embodiment of the present invention, the BMS is first powered on and initialized.

[0087] Step 302: BMS fault detection and judgment.

[0088] In the embodiment of the present invention, once a BMS fault occurs, the BMS fault is detected and determined.

[0089] Step 303: If the fault diagnosis condition is met, a corresponding fault is set.

[0090] In this embodiment of the present invention, the BMS fault type is determined based on the fault diagnosis conditions. For example, the diagnostic condition for a VCU communication loss fault is that the BMS receives a VCU no communication flag of 1. In other words, receiving a VCU no communication flag of 1 indicates a VCU communication loss fault.

[0091] Step 304 : Determine whether it is a collision, thermal runaway, or insulation failure.

[0092] In the embodiment of the present invention, it is determined whether the corresponding fault set in step 303 is a collision, thermal runaway or insulation fault. If so, step 321 is performed without recording and storing the fault information. If not, step 305 is performed.

[0093] Step 305: record and store the fault information.

[0094] In this embodiment of the present invention, fault information is recorded and stored for the non-crash, non-thermal runaway, and non-insulation faults identified in step 304. This fault information includes the fault code, fault response level, and the battery management system (BMS) parameter status at the time of the fault. Therefore, when a BMS fault is output, the fault code, fault response level, and BMS parameter status at the time of the fault are recorded and promptly stored in the NVM, which is then saved to the BMS fault database.

[0095] For example, 1001 indicates a VCU communication loss fault, 1002 indicates an OBC communication fault, 1003 indicates a fast charge communication fault, 1004 indicates a daisy chain communication fault, and 1005 indicates a current sensor communication fault. 2001 indicates a cell overvoltage or undervoltage fault, 2002 indicates an overtemperature fault, 2003 indicates an overpower fault, 2004 indicates a cell voltage differential fault, and 2005 indicates a cell temperature differential fault.

[0096] Step 306: Classify the BMS fault category.

[0097] In this embodiment of the present invention, the faults represented by 1001 to 1005 in step 305 are all communication abnormality or loss faults, which are communication-related faults, which are classified as flag-related faults. The faults represented by 2001 to 2005 in step 305 are all classified as threshold-related faults.

[0098] In the embodiment of the present invention, if it is classified as a threshold fault, then steps 307 to 313 are performed; if it is classified as a flag bit fault, then steps 314 to 320 are performed.

[0099] Step 307 : Compare the fault response threshold at the first time point with the historical fault threshold.

[0100] In this embodiment of the present invention, the fault response threshold at the first time point is compared with the historical fault threshold to determine whether the fault response threshold has increased or decreased. If the fault response threshold at the first time point is greater than the historical fault threshold, step 308 is performed; if the fault response threshold at the first time point is less than the historical fault threshold, step 309 is performed.

[0101] Step 308: The fault response threshold at the first time point is smaller than the fault response threshold at the second time point, and the fault response threshold at the first time point is larger than the historical fault threshold.

[0102] In this embodiment of the present invention, if the fault response threshold at the first time point is greater than the historical fault threshold, the fault response threshold at the first time point is less than the fault response threshold at the second time point, and the first time point is later than the second time point, then it indicates that the fault response threshold is on an increasing trend. In this case, steps 310 and 311 are performed.

[0103] Step 309 : The fault response threshold at the third time point is greater than the fault response threshold at the fourth time point, and the fault response threshold at the third time point is less than the historical fault threshold.

[0104] In this embodiment of the present invention, if the fault response threshold at the third time point is lower than the historical fault threshold, and the fault response threshold at the third time point is higher than the fault response threshold at the fourth time point, and the fourth time point is later than the third time point, it indicates that the fault response threshold is on a downward trend. In this case, steps 312 and 313 are performed.

[0105] Step 310: The accumulated count of the fault response threshold rising flag is greater than a third preset count threshold.

[0106] In this embodiment of the present invention, if the BMS fault classified in step 306 is a threshold-type fault, the fault response threshold at the first time point is less than the fault response threshold at the second time point, and the fault response threshold at the first time point is greater than the historical fault threshold, then the fault response threshold increase flag of the classified BMS fault is incremented by 1; the fault response threshold at the first time point is stored as the new fault threshold in the BMS fault database. If the classified BMS fault reoccurs the next time, and the fault response threshold is greater than the new fault threshold (i.e., the fault response threshold at the first time point), the fault response threshold increase flag of the classified BMS fault is also incremented by 1. If the accumulated count of the fault response threshold increase flag exceeds a third preset count threshold, the fault response level is automatically increased, i.e., step 311 is performed.

[0107] Step 311: The fault response level is increased by 1 accordingly.

[0108] Step 312: The accumulated count of the fault response threshold reduction flag is greater than a fourth preset count threshold.

[0109] In this embodiment of the present invention, if the classified BMS fault is a threshold-type fault, the fault response threshold at the third time point is greater than the fault response threshold at the fourth time point, and the fault response threshold at the third time point is less than the historical fault threshold, then the fault response threshold reduction flag for the classified BMS fault is decremented by 1 accordingly; the fault response threshold at the third time point is stored as the new fault threshold in the BMS fault database. If the classified BMS fault reoccurs the next time, and the fault response threshold is less than the new fault threshold (i.e., the fault response threshold at the third time point), the fault response threshold reduction flag for the classified BMS fault is also decremented by 1 accordingly. If the accumulated count of the fault response threshold reduction flag exceeds the fourth preset count threshold, the fault response level is automatically lowered, i.e., step 313 is performed.

[0110] In step 313, the fault response level is reduced by 1 accordingly.

[0111] Step 314: determine whether the BMS fault frequency changes.

[0112] In the embodiment of the present invention, if the BMS fault is classified as a flag type fault in step 306 , it is determined that the BMS fault occurrence frequency has changed, and step 315 or step 316 is executed.

[0113] Step 315: The occurrence frequency within the first preset time period is greater than a first preset frequency threshold.

[0114] In the embodiment of the present invention, if the occurrence frequency within the first preset time period is greater than the first preset frequency threshold, step 317 and step 318 are performed.

[0115] Exemplarily, the first preset time period is set to one driving cycle, and the first preset frequency domain threshold is set to three times.

[0116] Step 316: The occurrence frequency within the second preset time period is less than a second preset frequency threshold.

[0117] In the embodiment of the present invention, if the occurrence frequency within the second preset time period is less than the second preset frequency threshold, step 319 and step 320 are performed.

[0118] Exemplarily, the second preset time period is set to ten driving cycles, and the second preset frequency threshold is set to once.

[0119] Step 317: The accumulated count of the frequency increase flag is greater than a first preset count threshold.

[0120] In this embodiment of the present invention, if the classified BMS fault is a flag-type fault and its occurrence frequency increases dramatically within a certain period of time, it indicates that the classified BMS fault is on a growing trend. If the occurrence frequency of the classified BMS fault within a first preset time period exceeds a first preset frequency threshold, the frequency increase flag of the classified BMS fault is incremented by 1. If the cumulative count of the frequency increase flag exceeds the first preset count threshold, the fault response level is automatically modified and increased, i.e., step 318 is performed.

[0121] In step 318, the fault response level is increased by 1 accordingly.

[0122] Step 319: The frequency reduction flag cumulative count is greater than the second preset count threshold.

[0123] In this embodiment of the present invention, if the classified BMS fault is a flag-type fault and its occurrence frequency slows over a certain period of time, it indicates that the fault is intermittent and is on a decreasing trend. If the occurrence frequency of the classified BMS fault within a second preset time period is less than a second preset frequency threshold, the frequency reduction flag of the classified BMS fault is decremented by 1 accordingly. If the accumulated count of the frequency reduction flag exceeds the second preset count threshold, the fault response level is automatically lowered, i.e., step 320 is performed.

[0124] In step 320 , the fault response level is reduced by 1 accordingly.

[0125] Step 321: Do not record or store the fault information.

[0126] According to another embodiment, a battery management system fault processing device is provided. Figure 4 A schematic block diagram of a battery management system fault processing device according to an embodiment is shown. The device can be set at Figure 1 The server side of the architecture shown in Figure 1. Figure 4 As shown, the apparatus 400 may include: a classification unit 401, an adjustment unit 402, and a processing unit 403. The main functions of each component unit are as follows:

[0127] The classification unit 401 is used to classify the battery management system fault when there is a battery management system fault output.

[0128] The adjusting unit 402 is configured to adjust a fault response level according to the classified battery management system fault.

[0129] The processing unit 403 is configured to adopt a corresponding fault handling strategy for the battery management system fault after the fault response level is adjusted.

[0130] As an achievable method, the classification unit 401 is specifically used to classify the battery management system fault when there is a battery management system fault output, if the battery management system fault is a non-collision fault, a non-thermal runaway fault, and a non-insulation fault.

[0131] As an implementable manner, the classification unit 401 is specifically configured to classify the battery management system fault according to the fault code of the battery management system fault when a battery management system fault is output.

[0132] As an implementable manner, the classification unit 401 is specifically configured to classify the battery management system fault according to the fault diagnosis condition when there is a battery management system fault output.

[0133] As an achievable approach, battery management system fault categories include flag type faults and threshold type faults.

[0134] As an achievable manner, the adjustment unit 402 is specifically configured to, if the classified battery management system fault is a flag type fault, and the frequency of occurrence of the flag type fault within a first preset time period is greater than a first preset frequency threshold, then the frequency increase flag of the flag type fault is correspondingly incremented by 1; if the cumulative count of the frequency increase flag is greater than the first preset count threshold, then the fault response level is correspondingly incremented by 1; and / or

[0135] If the classified battery management system fault is a flag type fault, and the frequency of occurrence of the flag type fault within the second preset time period is less than the second preset frequency threshold, the frequency reduction flag of the flag type fault will be reduced by 1 accordingly; if the cumulative count of the frequency reduction flag is greater than the second preset count threshold, the fault response level will be reduced by 1 accordingly.

[0136] As an achievable manner, the adjustment unit 402 is specifically configured to, if the classified battery management system fault is a threshold type fault, and the fault response threshold at the first time point is less than the fault response threshold at the second time point, and the fault response threshold at the first time point is greater than the historical fault threshold, then the fault response threshold increase flag of the threshold type fault is correspondingly incremented by 1; if the cumulative count of the fault response threshold increase flag is greater than a third preset count threshold, then the fault response level is correspondingly incremented by 1, and the second time point is later than the first time point; and / or

[0137] If the classified battery management system fault is a threshold type fault, and the fault response threshold at the third time point is greater than the fault response threshold at the fourth time point, and the fault response threshold at the third time point is less than the historical fault threshold, then the fault response threshold reduction flag of the threshold type fault is correspondingly reduced by 1; if the cumulative count of the fault response threshold reduction flag is greater than the fourth preset count threshold, then the fault response level is correspondingly reduced by 1, and the fourth time point is later than the third time point.

[0138] As an achievable approach, the fault response levels include six levels;

[0139] The fault processing unit 403 is specifically configured to send a fault code without reducing the power of the battery management system if the fault response level of the battery management system fault after the fault response level is adjusted is level one;

[0140] If the fault response level of the battery management system fault after the fault response level is adjusted is level 2, level 3, or level 4, a fault code is sent and the power of the battery management system is reduced at a first preset rate, a second preset rate, a third preset rate, and a first preset ratio, a second preset ratio, and a third preset ratio, respectively;

[0141] If the fault response level of the battery management system fault after the fault response level is adjusted is level five, a fault code is sent and the power of the battery management system is reduced to 0 at a fourth preset rate; or

[0142] If the fault response level of the battery management system fault after the fault response level is adjusted is level six, a fault code is sent and the power of the battery management system is immediately reduced to 0.

[0143] Each embodiment in this specification is described in a progressive manner. The same or similar parts between the embodiments can be referred to each other. Each embodiment focuses on the differences from other embodiments. In particular, for the device embodiment, since it is basically similar to the method embodiment, the description is relatively simple. For the relevant parts, refer to the partial description of the method embodiment. The device embodiment described above is only exemplary, wherein the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the modules can be selected according to actual needs to achieve the purpose of the solution of this embodiment. A person of ordinary skill in the art can understand and implement it without paying any creative work.

[0144] In addition, an embodiment of the present invention further provides a computer-readable storage medium on which a computer program is stored. When the program is executed by a processor, the steps of any one of the methods in the aforementioned method embodiments are implemented.

[0145] And an electronic device comprising:

[0146] one or more processors; and

[0147] A memory associated with the one or more processors, the memory being used to store program instructions, wherein the program instructions, when read and executed by the one or more processors, execute the steps of any one of the method embodiments described above.

[0148] An embodiment of the present invention further provides a computer program product, comprising a computer program, which implements the steps of any one of the methods described in the aforementioned method embodiments when executed by a processor.

[0149] in, Figure 5 The electronic device architecture is shown as an example, and may include a processor 510, a video display adapter 511, a disk drive 512, an input / output interface 513, a network interface 514, and a memory 520. The processor 510, the video display adapter 511, the disk drive 512, the input / output interface 513, the network interface 514, and the memory 520 may be communicatively connected via a communication bus.

[0150] The processor 510 may be implemented as a general-purpose CPU, a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits, and may be used to execute relevant programs to implement the technical solutions provided by the embodiments of the present invention.

[0151] The memory 520 can be implemented in the form of ROM (Read Only Memory), RAM (Random Access Memory), static storage device, dynamic storage device, etc. The memory 520 can store an operating system 521 for controlling the operation of the electronic device 500, and a basic input and output system (BIOS) 522 for controlling the low-level operations of the electronic device 500. In addition, a web browser 523, a data storage management system 524, and a battery management system fault processing device 525, etc. can also be stored. The above-mentioned battery management system fault processing device 525 can be an application program that specifically implements the operations of the aforementioned steps in the embodiment of the present invention. In short, when the technical solution provided by the embodiment of the present invention is implemented by software or firmware, the relevant program code is stored in the memory 520 and is called and executed by the processor 510.

[0152] The input / output interface 513 is used to connect an input / output module to implement information input and output. The input / output module can be configured as a component in the device (not shown in the figure) or can be externally connected to the device to provide corresponding functions. Among them, input devices may include a keyboard, mouse, touch screen, microphone, various sensors, etc., and output devices may include a display, speaker, vibrator, indicator light, etc.

[0153] The network interface 514 is used to connect to a communication module (not shown) to enable communication between the device and other devices. The communication module can communicate via a wired method (such as USB, network cable, etc.) or a wireless method (such as mobile network, WIFI, Bluetooth, etc.).

[0154] The bus comprises a pathway that transmits information between the various components of the device (eg, processor 510, video display adapter 511, disk drive 512, input / output interface 513, network interface 514, and memory 520).

[0155] It should be noted that although the above device only shows a processor 510, a video display adapter 511, a disk drive 512, an input / output interface 513, a network interface 514, a memory 520, a bus, etc., in a specific implementation, the device may also include other components necessary for normal operation. In addition, it will be understood by those skilled in the art that the above device may also include only the components necessary to implement the solution of the present application, and does not necessarily include all the components shown in the figure.

[0156] Through the description of the above embodiments, those skilled in the art can clearly understand that each embodiment can be implemented by means of software plus a necessary general hardware platform, or of course, by hardware. Based on this understanding, the essence of the above technical solution or the part that contributes to the existing technology can be embodied in the form of a software product. The computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, a magnetic disk, an optical disk, etc., and includes a number of instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to execute the methods described in each embodiment or certain parts of the embodiments.

[0157] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the embodiments of the present invention, rather than to limit them. Although the embodiments of the present invention have been described in detail with reference to the above embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the above embodiments, or replace some or all of the technical features therein with equivalents. However, these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present invention.

Claims

1. A method for handling battery management system faults, characterized in that: include: When there is a battery management system fault output, classify the battery management system fault; Adjust the fault response level for the classified battery management system faults; For the battery management system fault after adjusting the fault response level, adopt the corresponding fault handling strategy.

2. The method according to claim 1, characterized in that When there is a battery management system fault output, classifying the battery management system fault includes: When there is a battery management system fault output, if the battery management system fault is a non-collision fault, a non-thermal runaway fault, and a non-insulation fault, the battery management system fault is classified.

3. The method according to claim 2, characterized in that When there is a battery management system fault output, classifying the battery management system fault includes: When a battery management system fault is output, the battery management system fault is classified according to the fault code of the battery management system fault.

4. The method according to claim 2, characterized in that: When there is a battery management system fault output, classifying the battery management system fault includes: When there is a battery management system fault output, the battery management system fault is classified according to the fault diagnosis condition.

5. The method according to claim 3 or 4, characterized in that: The battery management system fault categories include flag type faults and threshold type faults.

6. The method according to claim 5, characterized in that The adjusting of the fault response level for the classified battery management system fault includes: If the classified battery management system fault is a flag type fault, and the frequency of occurrence of the flag type fault within the first preset time period is greater than the first preset frequency threshold, the frequency increase flag of the flag type fault is increased by 1 accordingly; if the cumulative count of the frequency increase flag is greater than the first preset count threshold, the fault response level is increased by 1 accordingly; and / or If the classified battery management system fault is a flag type fault, and the frequency of occurrence of the flag type fault within the second preset time period is less than the second preset frequency threshold, the frequency reduction flag of the flag type fault is reduced by 1 accordingly; if the cumulative count of the frequency reduction flag is greater than the second preset count threshold, the fault response level is reduced by 1 accordingly.

7. The method according to claim 5, characterized in that The adjusting of the fault response level for the classified battery management system fault includes: If the classified battery management system fault is a threshold type fault, and the fault response threshold at the first time point is less than the fault response threshold at the second time point, and the fault response threshold at the first time point is greater than the historical fault threshold, then the fault response threshold increase flag of the threshold type fault is increased by 1 accordingly; if the cumulative count of the fault response threshold increase flag is greater than the third preset count threshold, then the fault response level is increased by 1 accordingly, and the second time point is later than the first time point; and / or If the classified battery management system fault is a threshold type fault, and the fault response threshold at the third time point is greater than the fault response threshold at the fourth time point, and the fault response threshold at the third time point is less than the historical fault threshold, then the fault response threshold reduction flag of the threshold type fault is reduced by 1 accordingly; if the cumulative count of the fault response threshold reduction flag is greater than the fourth preset count threshold, then the fault response level is reduced by 1 accordingly, and the fourth time point is later than the third time point.

8. The method according to any one of claims 1 to 4, characterized in that: The fault response levels include six levels; The corresponding fault handling strategy is adopted for the battery management system fault after the fault response level is adjusted, including: If the fault response level of the battery management system fault after the fault response level is adjusted is level one, a fault code is sent without reducing the power of the battery management system; If the fault response level of the battery management system fault after the fault response level is adjusted is level 2, level 3 or level 4, a fault code is sent and the power of the battery management system is reduced at a first preset rate, a second preset rate, a third preset rate and a first preset ratio, a second preset ratio and a third preset ratio respectively; If the fault response level of the battery management system fault after the fault response level is adjusted is level 5, a fault code is sent and the power of the battery management system is reduced to 0 at a fourth preset rate; or If the fault response level of the battery management system fault after the fault response level is adjusted is level six, a fault code is sent and the power of the battery management system is immediately reduced to 0.

9. A battery management system fault handling device, characterized in that: include: A classification unit, used for classifying the battery management system fault when there is a battery management system fault output; An adjustment unit, used for adjusting a fault response level according to a classified battery management system fault; The processing unit is used to adopt a corresponding fault processing strategy for the battery management system fault after the fault response level is adjusted.

10. An electronic device, characterized in that: include: A memory and a processor, wherein the processor and the memory communicate with each other via a bus; The memory stores program instructions executable by the processor, and the processor can execute the method according to any one of claims 1 to 8 by calling the program instructions.

Images