Root cause diagnosis method, device and electronic equipment for battery thermal runaway events
By receiving vehicle information and matching the fault tree, the signal data is used to diagnose the root cause of the battery thermal runaway event, which solves the problem that the root cause of the battery thermal runaway event cannot be accurately determined in the prior art, and improves vehicle safety.
Patent Information
- Application Number
- CN202411221862.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2024-09-02
- Publication Date
- 2024-11-22
- Estimated Expiration
- 2044-09-02
AI Technical Summary
The prior art cannot accurately determine the root cause of battery thermal runaway events, resulting in low vehicle safety and timely effective protective measures cannot be taken to prevent the recurrence of battery thermal runaway events.
By receiving vehicle information, determine whether the vehicle has a battery thermal runaway event, and match the corresponding target fault tree from the preset fault tree set, use the vehicle signal data and fault tree for root cause diagnosis, and determine the root cause of the battery thermal runaway event. .
Accurate diagnosis of the root causes of battery thermal runaway events has been achieved, timely protective measures have been taken, the safety of the vehicle has been improved, and the recurrence of battery thermal runaway events has been avoided.
Smart Images

Figure CN118722238B_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the technical field of fault diagnosis, and in particular to a root cause diagnosis method, device and electronic equipment for battery thermal runaway events. Background Art
[0002] With the rapid development of the electric vehicle industry, related safety issues have also attracted widespread attention. Among them, battery thermal runaway events, as one of the important failure events of electric vehicles, have also attracted much attention. Battery thermal runaway events refer to the rapid increase in battery temperature during the charging or discharging process due to internal or external factors, exceeding the normal operating temperature range, which can easily cause safety accidents such as battery explosion or fire.
[0003] In the prior art, the battery management system (BMS) is usually used to monitor the battery voltage, current, temperature and other parameters in real time to determine whether a battery thermal runaway event has occurred. However, this method cannot accurately determine the root cause of the battery thermal runaway event, so it is impossible to take effective protective measures in time, and it is also impossible to avoid the recurrence of the battery thermal runaway event, resulting in a low vehicle safety problem. Summary of the invention
[0004] The present application provides a root cause diagnosis method, device and electronic device for a battery thermal runaway event to solve the problem that the prior art cannot accurately determine the root cause of a battery thermal runaway event, resulting in low vehicle safety.
[0005] In a first aspect, the present application provides a root cause diagnosis method for a battery thermal runaway event, the method comprising:
[0006] Receiving vehicle information reported by a target vehicle, wherein the vehicle information includes vehicle identification information and vehicle signal data;
[0007] Determining whether a battery thermal runaway event occurs in the target vehicle according to the vehicle signal data;
[0008] In the case where it is determined that a battery thermal runaway event occurs in the target vehicle, a target fault tree matching the vehicle identification information is matched from a preset fault tree set, wherein the fault tree set includes multiple fault trees corresponding to different vehicle models, and each fault tree includes multiple levels of root cause nodes and logical relationships between the multiple levels of root cause nodes;
[0009] A root cause diagnosis is performed on the battery thermal runaway event according to the vehicle signal data and the target fault tree to obtain a root cause diagnosis result.
[0010] Optionally, performing root cause diagnosis on the battery thermal runaway event according to the vehicle signal data and the target fault tree to obtain a root cause diagnosis result includes:
[0011] Acquiring corresponding vehicle signal data within a target time period from the vehicle signal data, wherein the target time period is determined based on the occurrence time point of the battery thermal runaway event and a preset duration;
[0012] According to the vehicle signal data corresponding to the target time period, a target root cause node satisfying a judgment rule is determined from each root cause node of the target fault tree, wherein each root cause node in the target fault tree has its own corresponding judgment rule;
[0013] The root cause diagnosis result is determined according to the target root cause node.
[0014] Optionally, the target fault tree includes a first-level event node, a plurality of second-level root cause nodes and a plurality of third-level root cause nodes, wherein the logical relationship between the second-level root cause nodes is a logical OR relationship, and the logical relationship between the third-level root cause nodes under the same second-level root cause node is a logical OR relationship;
[0015] The determining the root cause diagnosis result according to the target root cause node includes:
[0016] In the case where the target root cause node belongs to a second-level root cause node, determining the root cause diagnosis result according to the fault root cause corresponding to the target root cause node;
[0017] In the case where the target root cause node belongs to a third-level root cause node, the root cause diagnosis result is determined according to the fault root cause corresponding to the target root cause node and the fault root cause corresponding to the second-level root cause node associated with the target root cause node.
[0018] Optionally, the plurality of second-level root cause nodes include at least two of a battery manufacturing defect root cause node, a cell overheat root cause node, an electrical abuse root cause node, a voltage too low root cause node, a mechanical abuse root cause node, a high temperature root cause node, an insulation degradation root cause node, a short circuit root cause node, an overcharge root cause node, and an over-discharge root cause node;
[0019] The third-level root cause node associated with the battery manufacturing defect root cause node includes at least one of an improper electrode material root cause node, an electrolyte contamination root cause node, and an insufficient quality control root cause node;
[0020] The third-level root cause node associated with the electrical abuse root cause node includes at least one of a battery management system failure root cause node, an electric control system abnormality root cause node, and a cable looseness root cause node;
[0021] The third-level root cause node associated with the mechanical abuse root cause node includes at least one of a collision root cause node and an extrusion root cause node;
[0022] The third-level root cause node associated with the insulation degradation root cause node includes a battery aging root cause node;
[0023] The third-level root cause node associated with the short circuit root cause node includes at least one of an external short circuit root cause node and an internal short circuit root cause node.
[0024] Optionally, after performing root cause diagnosis on the battery thermal runaway event according to the vehicle signal data and the target fault tree to obtain a root cause diagnosis result, the method further includes:
[0025] sending the root cause diagnosis result to a user terminal and an automobile fault prevention and control system associated with the target vehicle, wherein the automobile fault prevention and control system is used to send a remote control instruction to the target vehicle according to the root cause diagnosis result when the target vehicle is in an authorized state; and
[0026] The fault handling result returned by the target vehicle in response to the remote control command is received, the fault handling result is stored, and the fault handling result is fed back to the user terminal, and the user terminal is used to display the root cause diagnosis result and the fault handling result.
[0027] Optionally, after sending the root cause diagnosis result to a user terminal and an automobile fault prevention and control system associated with the target vehicle, the method further includes:
[0028] Determining whether the target vehicle is in an authorized state;
[0029] When the target vehicle is not in an authorized state, an authorization application request is sent to the user terminal, wherein the authorization application request carries an authorization application reason and an authorization application deadline.
[0030] Optionally, before matching a target fault tree matching the vehicle identification information from a preset fault tree set, the method further includes:
[0031] Acquire and compare signal data in a database file corresponding to a first vehicle model with signal data in a database file corresponding to a second vehicle model;
[0032] In a case where the signal data in the database file corresponding to the first vehicle type matches the signal data in the database file corresponding to the second vehicle type, determining the fault tree corresponding to the first vehicle type as the fault tree corresponding to the second vehicle type;
[0033] When the signal data in the database file corresponding to the first vehicle model and the signal data in the database file corresponding to the second vehicle model do not match, the root cause node and the judgment rule of the root cause node in the fault tree corresponding to the first vehicle model are modified to obtain the fault tree corresponding to the second vehicle model.
[0034] Optionally, determining whether a battery thermal runaway event occurs in the target vehicle according to the vehicle signal data includes:
[0035] Obtaining a parsing file that matches the vehicle identification information;
[0036] Parsing the vehicle signal data using the parsing file, and determining whether a target field in the parsed vehicle signal data is a preset value and the duration reaches a preset duration;
[0037] When it is determined that the target field in the parsed vehicle signal data is a preset value and the duration reaches a preset duration, it is determined that the battery thermal runaway event occurs in the target vehicle.
[0038] In a second aspect, the present application also provides a root cause diagnosis device for a battery thermal runaway event, the device comprising:
[0039] A first receiving module, configured to receive vehicle information reported by a target vehicle, wherein the vehicle information includes vehicle identification information and vehicle signal data;
[0040] A first determination module, configured to determine whether a battery thermal runaway event occurs in the target vehicle according to the vehicle signal data;
[0041] A matching module, configured to match a target fault tree matching the vehicle identification information from a preset fault tree set when it is determined that a battery thermal runaway event occurs in the target vehicle, wherein the fault tree set includes a plurality of fault trees corresponding to different vehicle models, and each fault tree includes a plurality of root cause nodes and a logical relationship between the plurality of root cause nodes;
[0042] The diagnosis module is used to perform root cause diagnosis on the battery thermal runaway event according to the vehicle signal data and the target fault tree to obtain a root cause diagnosis result.
[0043] In a third aspect, the present application further provides an electronic device, including a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory communicate with each other via the communication bus;
[0044] Memory, used to store computer programs;
[0045] The processor is used to implement the root cause diagnosis method of the battery thermal runaway event described in the first aspect when executing the program stored in the memory.
[0046] On the other hand, the present application also provides a computer-readable storage medium having a computer program stored thereon, and when the computer program is executed by a processor, the root cause diagnosis method of the battery thermal runaway event described in the first aspect is implemented.
[0047] The above technical solution provided by the present application has the following advantages over the prior art: the method provided by the present application receives vehicle information reported by the target vehicle, wherein the vehicle information includes vehicle identification information and vehicle signal data; determines whether the target vehicle has a battery thermal runaway event according to the vehicle signal data; in the case of determining that the target vehicle has a battery thermal runaway event, matches a target fault tree matching the vehicle identification information from a preset fault tree set, wherein the fault tree set includes multiple fault trees corresponding to different vehicle models, each fault tree includes a multi-level root cause node and a logical relationship between the multi-level root cause nodes; performs root cause diagnosis on the battery thermal runaway event according to the vehicle signal data and the target fault tree, and obtains a root cause diagnosis result. In the above manner, when a battery thermal runaway event occurs in the target vehicle, the target fault tree can be used to perform root cause diagnosis on the battery thermal runaway event, thereby accurately determining the root cause of the battery thermal runaway event in the target vehicle, so as to take effective protective measures in time for protection, and effectively avoid the recurrence of the battery thermal runaway event, so as to achieve the purpose of improving vehicle safety. BRIEF DESCRIPTION OF THE DRAWINGS
[0048] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the invention and, together with the description, serve to explain the principles of the invention.
[0049] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.
[0050] One or more embodiments are exemplarily described by pictures in the corresponding drawings, and these exemplified descriptions do not constitute limitations on the embodiments. Elements with the same reference numerals in the drawings represent similar elements, and unless otherwise stated, the figures in the drawings do not constitute proportional limitations.
[0051] Figure 1 A schematic flow chart of a root cause diagnosis method for a battery thermal runaway event provided in an embodiment of the present application;
[0052] Figure 2 A schematic diagram of the structure of a target fault tree provided in an embodiment of the present application;
[0053] Figure 3 A schematic diagram of the structure of another target fault tree provided in an embodiment of the present application;
[0054] Figure 4 A schematic flow chart of another root cause diagnosis method for a battery thermal runaway event provided in an embodiment of the present application;
[0055] Figure 5 A schematic diagram of a CAN signal parsing and storage process provided in an embodiment of the present application;
[0056] Figure 6 A schematic diagram of a battery thermal runaway fault tree automatic diagnosis process provided in an embodiment of the present application;
[0057] Figure 7 A schematic diagram of a process of remotely controlling a battery thermal runaway fault by a vehicle fault prevention and control system provided in an embodiment of the present application;
[0058] Figure 8 A schematic diagram of the interaction between a car owner user terminal, a car terminal, a cloud management platform and a car fault prevention and control system provided in an embodiment of the present application;
[0059] Fig. 9 A schematic diagram of the structure of a root cause diagnosis device for a battery thermal runaway event provided in an embodiment of the present application;
[0060] Fig.10 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION
[0061] In order to make the purpose, technical solution and advantages of the embodiments of the present application clearer, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of this application.
[0062] The disclosure below provides many different embodiments or examples to implement different structures of the present invention. In order to simplify the disclosure of the present invention, the parts and settings of specific examples are described below. Of course, they are only examples, and the purpose is not to limit the present invention. In addition, the present invention can repeat reference numbers and / or letters in different examples. This repetition is for the purpose of simplification and clarity, and does not itself indicate the relationship between the various embodiments and / or settings discussed.
[0063] In order to solve the problem that the prior art cannot accurately determine the root cause of a battery thermal runaway event, resulting in low vehicle safety, the present application provides a root cause diagnosis method, device and electronic equipment for a battery thermal runaway event, which can accurately determine the root cause of a battery thermal runaway event and improve vehicle safety.
[0064] See also Figure 1 , Figure 1 A schematic diagram of a process flow of a root cause diagnosis method for a battery thermal runaway event provided in an embodiment of the present application. Figure 1 As shown, the root cause diagnosis method of the battery thermal runaway event may include the following steps:
[0065] Step 101: Receive vehicle information reported by a target vehicle, wherein the vehicle information includes vehicle identification information and vehicle signal data.
[0066] It should be noted that the root cause diagnosis method of the battery thermal runaway event provided in the embodiment of the present application is applied to the cloud management platform (Cloud Management Platform, referred to as CMP), which can be connected to the vehicle, the user terminal of the corresponding owner of the vehicle, and the vehicle fault handling system (VFH). Among them, the vehicle can report the information of the vehicle end to the cloud management platform, and the cloud management platform determines whether a battery thermal runaway event has occurred based on the information reported by the vehicle. If a battery thermal runaway event is detected, the root cause diagnosis is performed according to the fault tree, and the root cause diagnosis result is sent to the user terminal corresponding to the vehicle and the vehicle fault prevention and control system. In this way, the owner can view the root cause diagnosis result through the user terminal and take effective protection measures in time. At the same time, the vehicle fault prevention and control system can remotely control the vehicle with the authorization of the owner, such as cutting off the power supply, starting the heat dissipation device, etc., to avoid losses caused by battery thermal runaway events.
[0067] Specifically, the target vehicle may be any vehicle connected to the cloud management platform. The vehicle information may include vehicle identification information and vehicle signal data, wherein the vehicle identification information may include the device number of the vehicle's T-BOX, the vehicle identification number (VIN) code, and other information. The vehicle signal data may include signal data such as battery voltage, battery current, and battery temperature.
[0068] In this step, after the target vehicle is powered on and started, it can report vehicle information to the cloud management platform at a regular interval, such as once every 1 second, once every 5 seconds, etc. In this way, the cloud management platform can receive the vehicle information reported by the target vehicle.
[0069] Step 102: Determine whether a battery thermal runaway event occurs in the target vehicle based on the vehicle signal data.
[0070] In this step, the cloud management platform can determine whether a battery thermal runaway event has occurred in the target vehicle based on the received vehicle signal data. Specifically, the cloud management platform can monitor in real time the specific field in the vehicle signal data used to characterize whether a battery thermal runaway event has occurred. If the value of the field is a value that characterizes the occurrence of a battery thermal runaway event, it is determined that a battery thermal runaway event has occurred in the target vehicle; of course, the specific field in the vehicle signal data used to characterize whether a battery thermal runaway event has occurred can also be monitored in real time. If the value of the field is a value that characterizes the occurrence of a battery thermal runaway event, and the duration of the value reaches a preset duration (such as 5 snapshot adoption cycles, etc.), it is determined that a battery thermal runaway event has occurred in the target vehicle.
[0071] Step 103: When it is determined that a battery thermal runaway event occurs in the target vehicle, a target fault tree matching the vehicle identification information is matched from a preset fault tree set, wherein the fault tree set includes multiple fault trees corresponding to different vehicle models, and each fault tree includes multiple levels of root cause nodes and logical relationships between the multiple levels of root cause nodes.
[0072] Specifically, the cloud management platform pre-builds fault trees corresponding to each vehicle model to form a fault tree set. Each fault tree can include multiple levels of root cause nodes (such as level 2, level 3, level 4, etc.) and logical relationships between multiple levels of root cause nodes (such as logical OR, logical AND, etc.).
[0073] When the cloud management platform determines that a battery thermal runaway event has occurred in a target vehicle, it can determine the model of the target vehicle based on the vehicle identification information, and then match the target fault tree corresponding to the model of the target vehicle from the fault tree set, so as to facilitate the subsequent use of the target fault tree to perform root cause diagnosis of the battery thermal runaway event.
[0074] Step 104: Perform root cause diagnosis on the battery thermal runaway event according to the vehicle signal data and the target fault tree to obtain a root cause diagnosis result.
[0075] It should be noted that the target fault tree may include multiple levels of root cause nodes and logical relationships between multiple levels of root cause nodes, and each root cause node in the target fault tree has a corresponding judgment rule. In this way, when the cloud management platform performs root cause diagnosis on a battery thermal runaway event, it can determine whether the judgment rules corresponding to the root cause nodes in the target fault tree are met based on the vehicle signal data. If the judgment rules corresponding to one or more root cause nodes are met, the final root cause diagnosis result is determined based on the logical relationship between these root cause nodes.
[0076] In this embodiment, when a battery thermal runaway event occurs in a target vehicle, the target fault tree can be used to perform root cause diagnosis of the battery thermal runaway event, thereby accurately determining the root cause of the battery thermal runaway event in the target vehicle, so that effective protective measures can be taken in time to prevent the battery thermal runaway event from happening again, thereby achieving the purpose of improving vehicle safety.
[0077] Furthermore, in the above step 104, root cause diagnosis of the battery thermal runaway event is performed according to the vehicle signal data and the target fault tree to obtain a root cause diagnosis result, including:
[0078] Obtaining corresponding vehicle signal data within a target time period from the vehicle signal data, wherein the target time period is determined based on the occurrence time point of the battery thermal runaway event and a preset duration;
[0079] According to the corresponding vehicle signal data in the target time period, a target root cause node satisfying the judgment rule is determined from each root cause node of the target fault tree, wherein each root cause node in the target fault tree has its own corresponding judgment rule;
[0080] Determine the root cause diagnosis result based on the target root cause node.
[0081] Specifically, the above-mentioned preset duration can be set according to actual conditions, such as 5 minutes, 1 hour, etc., and the embodiments of the present application do not make specific limitations. The time point of occurrence of the above-mentioned battery thermal runaway event refers to the time point when the cloud management platform detects that a battery thermal runaway event occurs in the target vehicle. The above-mentioned target time period can be a time period corresponding to a preset time before the time point of occurrence of the battery thermal runaway event, or it can be a time period corresponding to a preset time after the time point of occurrence of the battery thermal runaway event. As an optional implementation, the time period corresponding to the preset time before the time point of occurrence of the battery thermal runaway event is used as the target time period. For example, assuming that the time point of occurrence of the battery thermal runaway event is 10:00 and the preset duration is 5 minutes, the target time period is 9:55-10:00.
[0082] In one embodiment, when the cloud management platform performs root cause diagnosis on a battery thermal runaway event, it can obtain the corresponding vehicle signal data within a target time period from the vehicle signal data, and then determine the target root cause node that meets the judgment rule from each root cause node of the target fault tree based on the corresponding vehicle signal data within the target time period, and then determine the root cause diagnosis result based on the target root cause node.
[0083] In this way, the root cause of the battery thermal runaway event in the target vehicle can be accurately determined based on the judgment rules corresponding to each root cause node in the target fault tree, so that effective protection measures can be taken in time to prevent the battery thermal runaway event from happening again, thereby improving vehicle safety.
[0084] Furthermore, the above step of determining the root cause diagnosis result according to the target root cause node includes:
[0085] In the case where the target root cause node belongs to a second-level root cause node, determining a root cause diagnosis result according to the fault root cause corresponding to the target root cause node;
[0086] When the target root cause node belongs to the third-level root cause node, the root cause diagnosis result is determined according to the fault root cause corresponding to the target root cause node and the fault root cause corresponding to the second-level root cause node associated with the target root cause node.
[0087] In one embodiment, the target fault tree may include a first-level event node, multiple second-level root cause nodes and multiple third-level root cause nodes, wherein the logical relationship between the second-level root cause nodes is a logical OR relationship, and the logical relationship between the third-level root cause nodes under the same second-level root cause node is a logical OR relationship.
[0088] When the cloud management platform determines the root cause diagnosis result based on the target root cause node, it can first determine whether the target root cause node belongs to the second-level root cause node or the third-level root cause node. If the target root cause node belongs to the second-level root cause node, the root cause diagnosis result can be determined directly based on the fault root cause corresponding to the target root cause node. If the target root cause node belongs to the third-level root cause node, the root cause diagnosis result can be determined based on the fault root cause corresponding to the target root cause node and the fault root cause corresponding to the second-level root cause node that has an associated relationship with the target root cause node.
[0089] For example, assuming that the structure of the target fault tree corresponding to the target vehicle can be as follows Figure 2 As shown, it includes 1 first-level event node (battery thermal runaway event), 4 second-level root cause nodes and 6 third-level root cause nodes, among which the 4 second-level root cause nodes are battery manufacturing defect root cause node, battery cell overheating root cause node, electrical abuse root cause node and low voltage root cause node.
[0090] The judgment rule for the root cause node of battery cell overheating is bms_BalanceSWcellBlock=0;
[0091] The judgment rule for the voltage root cause node is IC_LowBatteryvoltage<2.
[0092] Since the judgment rules of the battery manufacturing defect root cause node and the electrical abuse root cause node are determined by the judgment rules of their associated third-level root cause nodes, they do not need to be configured with judgment rules separately.
[0093] When any one of the cell overheating root cause node and the voltage too low root cause node meets its corresponding judgment rule, a battery thermal runaway event occurs, and the root cause is the root cause corresponding to the second-level root cause node that meets the judgment rule.
[0094] The six third-level root cause nodes are improper electrode material root cause node, electrolyte contamination root cause node, insufficient quality control root cause node, battery management system failure root cause node, electronic control system abnormality root cause node and cable loose root cause node.
[0095] The judgment rule for the root cause node of improper electrode material is bms_cellOutOfBalance=0;
[0096] The judgment rule for the electrolyte contamination root cause node is bms_electrolyteConta=0;
[0097] The judgment rule for the root cause node of insufficient quality control is obc_batteryQuality=0.
[0098] As long as any one of the above three second-level root cause nodes meets the judgment rules, a battery thermal runaway event occurs, and the root cause is the root cause corresponding to the third-level root cause node that meets the judgment rules, as well as the battery manufacturing defect root cause.
[0099] The judgment rule for the battery management system fault root cause node is bms_system=0;
[0100] The judgment rule for the abnormal root cause node of the electronic control system is bms_pPack<12;
[0101] The judgment rule for the cable loose root cause node is obc_batteryConnectStatus=0.
[0102] As long as any one of the above three second-level root cause nodes meets the judgment rules, a battery thermal runaway event occurs, and the root cause is the root cause corresponding to the third-level root cause node that meets the judgment rules, as well as the electrical abuse root cause.
[0103] Through the above method, the root cause of the battery thermal runaway event in the target vehicle can be accurately determined according to the judgment rules corresponding to each root cause node in the target fault tree, so that effective protection measures can be taken in time to prevent the battery thermal runaway event from happening again, thereby achieving the purpose of improving vehicle safety.
[0104] Further, the plurality of second-level root cause nodes include at least two of a battery manufacturing defect root cause node, a cell overheat root cause node, an electrical abuse root cause node, a voltage too low root cause node, a mechanical abuse root cause node, a high temperature root cause node, an insulation degradation root cause node, a short circuit root cause node, an overcharge root cause node, and an over-discharge root cause node;
[0105] Among them, the third-level root cause nodes associated with the battery manufacturing defect root cause nodes include at least one of the improper electrode material root cause node, the electrolyte contamination root cause node and the insufficient quality control root cause node;
[0106] The third-level root cause node associated with the electrical abuse root cause node includes at least one of a battery management system fault root cause node, an electric control system abnormality root cause node, and a cable loose root cause node;
[0107] The third-level root cause node associated with the mechanical abuse root cause node includes at least one of a collision root cause node and a crush root cause node;
[0108] The third-level root cause nodes associated with the insulation degradation root cause node include a battery aging root cause node;
[0109] The third-level root cause node associated with the short circuit root cause node includes at least one of an external short circuit root cause node and an internal short circuit root cause node.
[0110] In one embodiment, the second-level root cause node of the target fault tree can be a combination of any two of the battery manufacturing defect root cause node, the battery cell overheating root cause node, the electrical abuse root cause node, the voltage too low root cause node, the mechanical abuse root cause node, the high temperature root cause node, the insulation degradation root cause node, the short circuit root cause node, the overcharge root cause node and the over-discharge root cause node, any combination of any three, any combination of any four, any combination of any five, any combination of any six, any combination of any seven, any combination of any eight, any combination of any nine, or all of them. Among them, the third-level root cause node associated with the battery manufacturing defect root cause node can be any one of the electrode material improper root cause node, the electrolyte contamination root cause node and the quality control insufficient root cause node, any combination of any two, or all of them. The third-level root cause node associated with the electrical abuse root cause node can be any one of the battery management system fault root cause node, the electronic control system abnormal root cause node and the cable loose root cause node, any combination of any two, or three of them. The third-level root cause node associated with the mechanical abuse root cause node includes any one or a combination of two of the collision root cause node and the extrusion root cause node. The third-level root cause node associated with the short-circuit root cause node includes any one or a combination of two of the external short-circuit root cause node and the internal short-circuit root cause node. It should be noted that the second-level root cause node and the third-level root cause node of the target fault tree can be specifically combined according to the vehicle type of the target vehicle or the vehicle's electrical and electronic architecture (EEA). For different models such as trucks (heavy, medium, etc.), buses, fuel vehicles, and electric vehicles, the battery thermal runaway signals involved will be different, so the root cause nodes of the fault trees corresponding to different models will also be different. The scale and analysis depth of the fault tree finally constructed can reach the level that can be considered as a basic event. By constructing different fault trees for different models, the efficiency and accuracy of fault diagnosis can be improved, and then more accurate maintenance suggestions can be formulated for each model to improve maintenance efficiency.
[0111] As an optional implementation, the structure of the target fault tree corresponding to the target vehicle can be as follows: Figure 3As shown, it includes 1 first-level event (battery thermal runaway event) node, 10 second-level root cause nodes and 11 third-level root cause nodes, among which the 10 second-level root cause nodes are battery manufacturing defect root cause node, battery cell overheating root cause node, electrical abuse root cause node, voltage too low root cause node, mechanical abuse root cause node, high temperature root cause node, insulation degradation root cause node, short circuit root cause node, overcharge root cause node and over discharge root cause node. The 11 third-level root cause nodes are improper electrode material root cause node, electrolyte contamination root cause node, insufficient quality control root cause node, battery management system failure root cause node, electronic control system abnormality root cause node, cable loose root cause node, collision root cause node, extrusion root cause node, battery aging root cause node, external short circuit root cause node and internal short circuit root cause node. The logical relationship between the second-level root cause nodes is a logical OR relationship, and the logical relationship between the third-level root cause nodes under the same second-level root cause node is a logical OR relationship.
[0112] When constructing the target fault tree in the cloud management platform, you can also set judgment rules and maintenance suggestions for each root cause node. The corresponding relationship can be shown in Table 1:
[0113] Table 1
[0114]
[0115] In this way, different fault trees can be designed according to the actual needs of different vehicle models to cover all possible root causes of battery thermal runaway events as much as possible.
[0116] Furthermore, in the above step 104, after performing root cause diagnosis on the battery thermal runaway event according to the vehicle signal data and the target fault tree and obtaining the root cause diagnosis result, the method further includes:
[0117] Sending the root cause diagnosis result to a user terminal and an automobile fault prevention and control system associated with the target vehicle, wherein the automobile fault prevention and control system is used to send a remote control instruction to the target vehicle according to the root cause diagnosis result when the target vehicle is in an authorized state; and
[0118] Receive the fault handling result returned by the target vehicle in response to the remote control command, store the fault handling result, and feed back the fault handling result to the user terminal, which is used to display the root cause diagnosis result and the fault handling result.
[0119] In one embodiment, after the cloud management platform performs root cause diagnosis on the battery thermal runaway event and obtains the root cause diagnosis result, it can also send the root cause diagnosis result to the user terminal and the automobile fault prevention and control system associated with the target vehicle. In this way, the user terminal can display the root cause diagnosis result, which is convenient for the car owner to take corresponding protective measures in time. At the same time, the automobile fault prevention and control system can send remote control instructions to the target vehicle according to the root cause diagnosis result when the target vehicle is in an authorized state, so as to remotely control the target vehicle, such as cutting off the power supply, starting the heat dissipation device, etc. In addition, in an emergency or when the target vehicle is unauthorized, the user can handle it according to the root cause diagnosis result.
[0120] In addition, the cloud management platform can also receive the fault handling results returned by the target vehicle in response to the remote control command, store the fault handling results, and feed back the fault handling results to the user terminal, so that the user terminal can display the fault handling results for the convenience of the car owner to view.
[0121] Furthermore, after the above step of sending the root cause diagnosis result to the user terminal and the automobile fault prevention and control system associated with the target vehicle, the method further includes:
[0122] Determine whether the target vehicle is in an authorized state;
[0123] When the target vehicle is not in the authorized state, an authorization application request is sent to the user terminal, wherein the authorization application request carries the authorization application reason and the authorization application period.
[0124] In one embodiment, in order to meet the requirements of relevant laws and regulations, the cloud management platform needs to obtain the authorization of the owner before sending a remote control instruction to the target vehicle. At this time, the cloud management platform can first determine whether the target vehicle is in an authorized state. If the target vehicle is not in an authorized state, the cloud management platform needs to send an authorization application request to the user terminal, and then receive a response message from the user terminal. If the response message is an authorization agreement, the authorization status of the target vehicle is saved, and the authorization status of the target vehicle is sent to the target vehicle and the automobile fault prevention and control system. In this way, when the target vehicle is in an authorized state, the automobile fault prevention and control system can send a remote control instruction to the target vehicle according to the root cause diagnosis result to achieve remote control of the target vehicle.
[0125] Furthermore, before the above step 103, matching a target fault tree matching the vehicle identification information from a preset fault tree set, the method further includes:
[0126] Acquire and compare signal data in a database file corresponding to a first vehicle model with signal data in a database file corresponding to a second vehicle model;
[0127] In the case where the signal data in the database file corresponding to the first vehicle model matches the signal data in the database file corresponding to the second vehicle model, determining the fault tree corresponding to the first vehicle model as the fault tree corresponding to the second vehicle model;
[0128] When the signal data in the database file corresponding to the first vehicle model and the signal data in the database file corresponding to the second vehicle model do not match, the root cause node and the judgment rule of the root cause node in the fault tree corresponding to the first vehicle model are modified to obtain the fault tree corresponding to the second vehicle model.
[0129] It should be noted that each vehicle model has a corresponding database file, namely, a DBC (short for Database Can) file. When the signal name or signal quantity related to the thermal runaway signal in the DBC file of a certain vehicle model changes, the relevant rule information in the corresponding fault tree will also change in real time; if the signal name and signal quantity related to the thermal runaway signal in the DBC file of the vehicle model do not change, the relevant rule information in the previously set fault tree will continue to be used for diagnosis.
[0130] In one embodiment, when setting a fault tree set, the signal data in the database file corresponding to the first vehicle model and the signal data in the database file corresponding to the second vehicle model may be first obtained and compared. If the signal data in the database file corresponding to the first vehicle model and the signal data in the database file corresponding to the second vehicle model match (i.e., the thermal runaway signals in the DBC files of the two vehicles are consistent), the fault tree corresponding to the first vehicle model may be determined as the fault tree corresponding to the second vehicle model; if the signal data in the database file corresponding to the first vehicle model and the signal data in the database file corresponding to the second vehicle model do not match (i.e., the thermal runaway signals in the DBC files of the two vehicles are inconsistent), the root cause node and the judgment rule of the root cause node in the fault tree corresponding to the first vehicle model may be modified to obtain the fault tree corresponding to the second vehicle model. For example, assuming that a fault tree is currently created with the DBC file of vehicle model A, the fault tree is used for diagnosis when battery thermal runaway occurs in vehicle model A. When vehicle model B needs to perform battery thermal runaway fault diagnosis, the rules set in the fault tree of vehicle model A may be compared to see if they are consistent with the thermal runaway signal rules of vehicle model B. If the rules set in the fault tree of vehicle model A are consistent with the thermal runaway signal rules of vehicle model B, the fault tree of vehicle model A is used to diagnose vehicle model B. In this way, the workload required for setting up the fault tree can be saved, thereby achieving the goal of improving the efficiency of fault tree setting.
[0131] Furthermore, the above step 102, determining whether a battery thermal runaway event occurs in the target vehicle according to the vehicle signal data, includes:
[0132] Obtain a parsed file that matches the vehicle identification information;
[0133] Parsing the vehicle signal data using the parsing file, and determining whether the target field in the parsed vehicle signal data is a preset value and the duration reaches a preset duration;
[0134] When it is determined that the target field in the parsed vehicle signal data is a preset value and the duration reaches a preset duration, it is determined that a battery thermal runaway event occurs in the target vehicle.
[0135] In one embodiment, when determining whether a battery thermal runaway event has occurred in a target vehicle, the cloud management platform may first obtain a parsing file that matches the vehicle identification information, and then use the parsing file to parse the vehicle signal data, and determine whether the target field in the parsed vehicle signal data is a preset value and the duration reaches the preset duration; if the target field is a preset value and the duration reaches the preset duration, it can be determined that a battery thermal runaway event has occurred in the target vehicle.
[0136] As an optional implementation, the judgment rule for the occurrence of a battery thermal runaway event is as follows:
[0137] 1) Signal judgment: BMS_ThrmlRunawaySt ≠ 0x02 ——> BMS_ThrmlRunawaySt = 0x02 (thermal runaway fault);
[0138] 2) Signal duration: 1000ms (5 snapshots in a cycle).
[0139] Through the above method, misjudgment caused by signal interference can be effectively avoided, thereby improving the accuracy of battery thermal runaway event judgment.
[0140] In one embodiment, the root cause diagnosis process of the battery thermal runaway event provided in the embodiment of the present application is as follows: Figure 4 As shown, it may include the following steps:
[0141] Step 401: Receive the CAN signal reported by the vehicle end, where the CAN signal is the vehicle information mentioned above.
[0142] Step 402: Determine whether a battery thermal runaway event occurs.
[0143] It should be noted that the CAN signal reported by the vehicle is collected by the vehicle's own battery management system. The cloud management platform parses the signal value of the target field from the CAN signal according to specific rules and stores it. For example, the judgment rules for the occurrence of thermal runaway events are as follows:
[0144] 1) Signal judgment: BMS_ThrmlRunawaySt ≠ 0x02 ——> BMS_ThrmlRunawaySt = 0x02 (thermal runaway fault);
[0145] 2) Signal duration: 1000ms (such as 5 snapshot cycles, etc.).
[0146] Among them, the system architecture diagram of CAN signal analysis and storage is as follows Figure 5 The names of the various parts and their functions in the system are described in detail as follows:
[0147] Power battery system: mainly detects and collects CAN signals through the Battery Information Collector (BIC) and the Battery Management Unit (BMU), and monitors the battery cell voltage, ambient temperature, air pressure, etc.
[0148] Vehicle Control Unit (VCU): Receives CAN signals and transmits them to the telematics box (T-BOX).
[0149] Input Coupling Unit (ICU): executes VCU commands and issues alarms to alert passengers of danger.
[0150] Telematics processor T-BOX: Remote data terminal. It uploads CAN signals to the cloud management platform via the Message Queuing Telemetry Transport (MQTT) protocol.
[0151] Data analysis service: The cloud management platform analyzes and stores the CAN signals uploaded by the vehicle through the data analysis service, and then provides query and display for the cloud management platform. The specific implementation process is as follows:
[0152] 1) The cloud management platform pushes the original CAN message reported by T-BOX to the distributed publish-subscribe messaging system (Apache Kafka, referred to as Kafka). Kafka finds the corresponding vehicle frame number, vehicle series, model, brand and other information based on the device number of T-BOX;
[0153] 2) The custom CAN parsing service will match the parsing file corresponding to the vehicle model according to the vehicle information, and use it to parse the received CAN original message. After the parsing is completed, it will be pushed to Kafka. During this period, Mysql will store the message information of the vehicle model;
[0154] 3) The data storage service consumes the parsed data pushed to Kafka and stores it in the time series database Influxdb;
[0155] 4) The cloud management platform displays the parsed CAN message information on the WEB page through a unified data query service and application programming interface (API) gateway agent for operators to query and analyze.
[0156] Step 403: Perform automatic diagnosis using the battery thermal runaway fault tree.
[0157] Step 404: Generate a diagnostic report and send the diagnostic report to the vehicle owner user terminal and the thermal runaway fault diagnosis system.
[0158] Before performing fault tree diagnosis, you can build a battery thermal runaway fault tree based on the abnormal fault data reported by the actual vehicle and the fault generation logic. When constructing the structure of the automotive battery thermal runaway fault tree, first define a top-level "top event", which is usually a "battery thermal runaway event". According to known scientific principles and technical specifications, identify various potential causes that may lead to battery thermal runaway events, including direct and indirect causes, and use them as basic events of the intermediate or bottom nodes of the fault tree. Use logic gates at appropriate locations to represent the complex logical relationships between the basic events. By analyzing all intermediate events, bottom events and top events, they are all in an "OR" relationship, so "OR" gates can be used to connect them. The fault tree created based on the "battery thermal runaway" top event can be as follows Figure 3 shown.
[0159] After the battery thermal runaway fault tree is created, matching rules for the third-level fault (bottom event) can be created based on the corresponding signal. For example, when the reported CAN signal meets the matching rule of bms_cellOutOfBalance = 0, the third-level fault of improper electrode material will be triggered, which will in turn trigger the second-level fault (intermediate event) battery manufacturing defect, and finally trigger the battery thermal runaway fault phenomenon (top event). Not all second-level faults have third-level faults. At this time, the matching rules for the second-level fault should be created with the corresponding fault signal. If there is no corresponding matching rule, it will be judged as no fault or unknown state during diagnosis. According to different fault causes, corresponding maintenance suggestions are also given to ensure that after the diagnosis is completed, the battery thermal runaway fault can be prevented and controlled in time according to the maintenance suggestions, thereby improving the efficiency of fault resolution.
[0160] After the fault tree structure is drawn, the corresponding matching rules should be established according to the CAN signals that trigger each bottom event. When setting the matching rules, the default data duration of the CAN signal is 1 hour, but the corresponding data duration can be set according to the time when the thermal runaway occurs. In addition, the basic cycle and evaluation cycle of the matching rules should also be set, so that the fault tree can be successfully established. This is a fault tree created based on the current battery thermal runaway fault analysis. With the continuous development and updating of technology, the causes of battery thermal runaway are far more than this. In the future, the thermal runaway fault diagnosis system will be regularly updated and optimized to adapt to the rapid development of automotive technology and ensure system stability and reliability.
[0161] When a battery thermal runaway event occurs in a vehicle, the cloud management platform will immediately perform automatic diagnosis based on the pre-created battery thermal runaway fault tree, filter and analyze the time point of the fault occurrence, and further accurately match the root cause information. The specific operation steps are as follows:
[0162] Automatically obtain the basic information of the vehicle with thermal runaway; use the time of vehicle thermal runaway as the time of fault occurrence; diagnose and generate diagnostic results based on the fault tree of battery thermal runaway. The cloud management platform determines the probability of each fault event based on the set matching rules. When the vehicle CAN signal data meets the matching rules within the set data duration, the fault event is triggered, and the diagnostic status of each fault event is marked with different colors. After a fault event is triggered, the upper-level target fault event (battery thermal runaway) is further triggered, and the diagnosis of battery thermal runaway is finally completed.
[0163] like Figure 6 As shown, Figure 6 This is the system structure diagram for automatic diagnosis of battery thermal runaway fault tree. The detailed steps are as follows:
[0164] 1) When a battery thermal runaway event occurs, the cloud management platform automatically triggers the fault diagnosis service Kafka;
[0165] 2) The fault diagnosis service Kafka obtains the previously created battery thermal runaway fault tree information from MySQL, and combines it with the basic vehicle information in the equipment center to diagnose the fault based on the time when the battery thermal runaway occurs as the time when the fault occurs;
[0166] 3) Query the rules set in the fault tree, obtain the CAN message information in Influxdb according to the rules and the time when the fault occurred, and determine whether the rules are triggered;
[0167] 4) After the rule is triggered, it is further determined whether the bottom event is triggered, and based on the logical relationship between the bottom events, it is determined whether the intermediate event is triggered. After the intermediate event is triggered, the diagnostic status is updated to "fault", and if it is not triggered, it is updated to "no fault". The same is true for the diagnostic status of the bottom event;
[0168] 6) Loop through steps 4) and 5) until all rules under the fault tree are diagnosed, and store the final diagnosis results in MySQL;
[0169] 7) The cloud management platform obtains the diagnosis results and generates a corresponding diagnosis report.
[0170] After the cloud management platform completes the fault tree diagnosis, it can generate a corresponding diagnostic report based on the diagnostic results, and automatically send the diagnostic report to the car owner's user terminal or the car fault prevention and control system that needs to handle the fault. The diagnostic report may include the following content:
[0171] 1) Basic vehicle information: including vehicle series, model, frame number, vehicle type, vehicle status, vehicle manufacturer and vehicle registration information, etc.
[0172] 2) Fault tree diagnosis results: including fault tree name, creator, diagnosis status, fault tree diagnosis creation time, end time, fault list, fault tree structure diagram and minimum cut set.
[0173] 3) Battery thermal runaway event information: including the time, location, and severity of the thermal runaway.
[0174] 4) Vehicle damage analysis: Analyze and evaluate vehicle battery damage through fault tree diagnosis results.
[0175] 5) Fault cause speculation: Based on the fault tree diagnosis results, the causes of thermal runaway of the battery can be speculated, which may include battery manufacturing defects, high temperature environment, excessive charging and discharging, external short circuit, etc.
[0176] 6) Repair suggestions: Based on the diagnosis results, suggestions for battery repair are given for different causes of failure, including repair parts, repair methods, etc.
[0177] Step 405: Determine whether the vehicle owner authorizes. If the vehicle owner authorizes, execute step 407; if the vehicle owner does not authorize, execute step 406.
[0178] Step 406: Apply for authorization from the vehicle owner and receive authorization from the vehicle owner.
[0179] Step 407: The automobile fault prevention and control system saves the authorization status.
[0180] The vehicle fault prevention and control system will handle the battery thermal runaway according to the maintenance suggestions in the diagnosis results, and will perform certain remote control operations on the vehicle battery during the process. In order to avoid damage to vehicle safety, before performing fault handling, it is necessary to obtain authorization from the owner in accordance with the requirements of relevant laws and regulations, otherwise the fault handling will not be possible. The steps for the owner's authorization are as follows:
[0181] 1) The cloud management platform applies for authorization from the car owner and informs the car owner of the reason and deadline for the application in the form of a text message or application (App) message;
[0182] 2) Car owners can sign the relevant authorization agreement documents at offline sales and service stores, or agree to the authorization through the App;
[0183] 3) The cloud management platform will save the current vehicle authorization status;
[0184] 4) The cloud management platform will synchronize the authorization status and authorization period to the vehicle and the vehicle fault prevention and control system.
[0185] Step 408: The vehicle fault prevention and control system remotely handles the battery thermal runaway fault.
[0186] Step 409: The vehicle returns the fault handling result to the cloud management platform.
[0187] Step 410: Feedback the fault handling result to the vehicle owner user terminal.
[0188] After diagnosing the battery thermal runaway fault tree, the vehicle fault prevention and control system will obtain the corresponding diagnosis report. Within a certain authorization period, according to the maintenance suggestions corresponding to the fault cause in the diagnosis report, the vehicle with battery thermal runaway will be remotely controlled and a temporary treatment plan will be given, such as timely power cut-off and activation of the fire extinguishing system, to control the impact of the accident and reduce vehicle losses to a certain extent. In order to effectively prevent and control battery thermal runaway failures, the vehicle fault prevention and control system will carry out prevention and control from the following aspects:
[0189] 1) Improvement of internal materials and structure:
[0190] A. Optimization of battery cell design: Use more stable electrode materials and electrolytes to reduce the possibility of internal short circuits and thermal reactions.
[0191] B. Thermal isolation and flame retardant design: Flame retardant materials and heat diffusion barriers are added to the battery pack to prevent thermal runaway from spreading to other cells.
[0192] 2) Charging management and monitoring;
[0193] A. Balanced charging: Ensure the consistency of the charging status of each cell in the battery pack to reduce the risk of overcharging of individual cells.
[0194] 3) Physical protection and structural reinforcement:
[0195] A. Enhance mechanical strength: Improve the outer shell strength of the battery pack to prevent internal damage caused by external impact and reduce the causes of thermal runaway.
[0196] like Figure 7 As shown, Figure 7 This is the system structure diagram of the remote control of the automobile fault prevention and control system to handle the battery thermal runaway fault. The specific steps of remote control to handle the battery thermal runaway fault are as follows:
[0197] 1) The cloud management platform applies for authorization from the car owner, and after the car owner agrees to the authorization, the authorization result is synchronized to the vehicle fault prevention and control system and the vehicle end;
[0198] 2) The automobile fault prevention and control system stores the authorization results in MySQL, and the fault processing service Kafka consumes the stored fault diagnosis data and sends remote control commands to the vehicle end through MQTT;
[0199] 3) After receiving the remote control command, the vehicle returns the response information of the fault handling;
[0200] It can be seen that the interaction process between the car owner user terminal, the car terminal, the cloud management platform and the automobile fault prevention and control system can be as follows: Figure 8 The root cause diagnosis method of a battery thermal runaway event provided in the embodiment of the present application can have the following beneficial effects:
[0201] 1. Improve prediction capability: The fault tree diagnosis method can be used to conduct in-depth analysis of battery thermal runaway, thereby improving the prediction capability of battery thermal runaway and avoiding the problem that the existing technology cannot accurately predict and prevent the occurrence of battery thermal runaway.
[0202] 2. Identify the root cause of battery thermal runaway: When thermal runaway occurs in the battery, the root cause of the thermal runaway can be analyzed through the fault tree diagnosis method, thereby providing a basis for subsequent fault handling and prevention. This avoids the problem in the prior art that when thermal runaway occurs in the battery, although the BMS can report the thermal runaway event signal data, it does not further analyze the root cause of the thermal runaway.
[0203] 3. Improve the accuracy of fault diagnosis: Compared with existing fault diagnosis methods, such as model-based fault diagnosis methods and signal processing-based fault diagnosis methods, the fault tree diagnosis method can more accurately locate the fault location and cause, thereby improving the accuracy of fault diagnosis.
[0204] 4. Improve fault resolution efficiency: Combine fault tree diagnosis and VFH system to establish an efficient thermal runaway processing mechanism to handle battery thermal runaway faults as quickly as possible, improve fault resolution efficiency, and enhance car owners’ satisfaction and happiness.
[0205] See also Fig. 9 , Fig. 9 This is a schematic diagram of the structure of a root cause diagnosis device for a battery thermal runaway event provided in an embodiment of the present application. Fig. 9 As shown, the root cause diagnosis device 900 for the battery thermal runaway event includes:
[0206] The first receiving module 901 is used to receive vehicle information reported by the target vehicle, wherein the vehicle information includes vehicle identification information and vehicle signal data;
[0207] A first determination module 902, configured to determine whether a battery thermal runaway event occurs in a target vehicle according to vehicle signal data;
[0208] A matching module 903 is used to match a target fault tree matching the vehicle identification information from a preset fault tree set when it is determined that a battery thermal runaway event occurs in the target vehicle, wherein the fault tree set includes multiple fault trees corresponding to different vehicle models, and each fault tree includes multiple levels of root cause nodes and logical relationships between the multiple levels of root cause nodes;
[0209] The diagnosis module 904 is used to perform root cause diagnosis on the battery thermal runaway event according to the vehicle signal data and the target fault tree to obtain a root cause diagnosis result.
[0210] Furthermore, the diagnosis module 904 includes:
[0211] A first acquisition submodule is used to acquire the vehicle signal data corresponding to a target time period from the vehicle signal data, wherein the target time period is determined based on the occurrence time point of the battery thermal runaway event and a preset duration;
[0212] A first determination submodule is used to determine a target root cause node that meets the judgment rule from each root cause node of the target fault tree according to the corresponding vehicle signal data within the target time period, wherein each root cause node in the target fault tree has its own corresponding judgment rule;
[0213] The second determination submodule is used to determine the root cause diagnosis result according to the target root cause node.
[0214] Further, the target fault tree includes a first-level event node, a plurality of second-level root cause nodes and a plurality of third-level root cause nodes, wherein the logical relationship between the second-level root cause nodes is a logical OR relationship, and the logical relationship between the third-level root cause nodes under the same second-level root cause node is a logical OR relationship;
[0215] The second determination submodule includes:
[0216] A first determining unit is used to determine a root cause diagnosis result according to a fault root cause corresponding to the target root cause node when the target root cause node belongs to a second-level root cause node;
[0217] The second determining unit is used to determine the root cause diagnosis result according to the fault root cause corresponding to the target root cause node and the fault root cause corresponding to the second-level root cause node associated with the target root cause node when the target root cause node belongs to the third-level root cause node.
[0218] Further, the plurality of second-level root cause nodes include at least two of a battery manufacturing defect root cause node, a cell overheat root cause node, an electrical abuse root cause node, a voltage too low root cause node, a mechanical abuse root cause node, a high temperature root cause node, an insulation degradation root cause node, a short circuit root cause node, an overcharge root cause node, and an over-discharge root cause node;
[0219] Among them, the third-level root cause nodes associated with the battery manufacturing defect root cause nodes include at least one of the improper electrode material root cause node, the electrolyte contamination root cause node and the insufficient quality control root cause node;
[0220] The third-level root cause node associated with the electrical abuse root cause node includes at least one of a battery management system fault root cause node, an electric control system abnormality root cause node, and a cable loose root cause node;
[0221] The third-level root cause node associated with the mechanical abuse root cause node includes at least one of a collision root cause node and a crush root cause node;
[0222] The third-level root cause nodes associated with the insulation degradation root cause node include a battery aging root cause node;
[0223] The third-level root cause node associated with the short circuit root cause node includes at least one of an external short circuit root cause node and an internal short circuit root cause node.
[0224] Furthermore, the root cause diagnosis device 900 for the battery thermal runaway event further includes:
[0225] A first sending module is used to send the root cause diagnosis result to a user terminal and an automobile fault prevention and control system associated with the target vehicle, and the automobile fault prevention and control system is used to send a remote control instruction to the target vehicle according to the root cause diagnosis result when the target vehicle is in an authorized state; and
[0226] The second receiving module is used to receive the fault processing result returned by the target vehicle in response to the remote control command, store the fault processing result, and feed back the fault processing result to the user terminal, and the user terminal is used to display the root cause diagnosis result and the fault processing result.
[0227] Furthermore, the root cause diagnosis device 900 for the battery thermal runaway event further includes:
[0228] A judgment module, used to judge whether the target vehicle is in an authorized state;
[0229] The second sending module is used to send an authorization application request to the user terminal when the target vehicle is not in an authorized state, wherein the authorization application request carries an authorization application reason and an authorization application period.
[0230] Furthermore, the root cause diagnosis device 900 for the battery thermal runaway event further includes:
[0231] An acquisition and comparison module, used for acquiring and comparing signal data in a database file corresponding to a first vehicle model and signal data in a database file corresponding to a second vehicle model;
[0232] A second determination module is used to determine the fault tree corresponding to the first vehicle model as the fault tree corresponding to the second vehicle model when the signal data in the database file corresponding to the first vehicle model and the signal data in the database file corresponding to the second vehicle model match;
[0233] The modification module is used to modify the root cause node and the judgment rule of the root cause node in the fault tree corresponding to the first vehicle model when the signal data in the database file corresponding to the first vehicle model and the signal data in the database file corresponding to the second vehicle model do not match, so as to obtain the fault tree corresponding to the second vehicle model. Further, the first determination module 902 includes:
[0234] A second acquisition submodule is used to acquire a parsing file matching the vehicle identification information;
[0235] A judgment submodule is used to parse the vehicle signal data using the parsing file, and to judge whether the target field in the parsed vehicle signal data is a preset value and the duration reaches a preset duration;
[0236] The third determination submodule is used to determine that a battery thermal runaway event occurs in the target vehicle when it is determined that the target field in the parsed vehicle signal data is a preset value and the duration reaches a preset duration.
[0237] It should be noted that the root cause diagnosis device 900 for battery thermal runaway events can implement the root cause diagnosis method for battery thermal runaway events provided by any of the aforementioned method embodiments, and can achieve the same technical effects, which will not be described in detail here.
[0238] like Fig.10 As shown, the embodiment of the present application further provides an electronic device, including a processor 1011, a communication interface 1012, a memory 1013 and a communication bus 1014, wherein the processor 1011, the communication interface 1012, and the memory 1013 communicate with each other through the communication bus 1014.
[0239] Memory 1013, used for storing computer programs;
[0240] In one embodiment of the present application, the processor 1011 is configured to implement the root cause diagnosis method for a battery thermal runaway event provided by any one of the aforementioned method embodiments when executing a program stored in the memory 1013 .
[0241] An embodiment of the present application further provides a computer-readable storage medium having a computer program stored thereon. When the computer program is executed by a processor, the root cause diagnosis method for a battery thermal runaway event provided by any one of the aforementioned method embodiments is implemented.
[0242] The device embodiments described above are merely illustrative, wherein the units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
[0243] Through the description of the above implementation methods, those skilled in the art can clearly understand that each implementation method can be implemented by means of software plus a general hardware platform, and of course, by hardware. Based on this understanding, the above technical solution, in essence, or the part that contributes to the relevant technology, can be embodied in the form of a software product, which can be stored in a computer-readable storage medium, such as ROM / RAM, a disk, an optical disk, etc., including a number of instructions for 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 some parts of the embodiment.
[0244] It should be understood that the terms used herein are only for the purpose of describing specific example embodiments and are not intended to be limiting. Unless the context clearly indicates otherwise, the singular forms "one", "an" and "said" as used herein may also be meant to include plural forms. The terms "include", "comprise", "contain", and "have" are inclusive, and therefore specify the existence of stated features, steps, operations, elements and / or parts, but do not exclude the existence or addition of one or more other features, steps, operations, elements, parts, and / or combinations thereof. The method steps, processes, and operations described herein are not interpreted as necessarily requiring them to be performed in the specific order described or illustrated, unless the execution order is clearly indicated. It should also be understood that additional or alternative steps may be used.
[0245] The foregoing is merely a specific embodiment of the present invention, which enables those skilled in the art to understand or implement the present invention. Various modifications to these embodiments will be apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present invention. Therefore, the present invention will not be limited to the embodiments shown herein, but rather to the widest scope consistent with the principles and novel features claimed herein.
Claims
1. A root cause diagnosis method for a battery thermal runaway event, characterized in that: The method comprises: Receiving vehicle information reported by a target vehicle, wherein the vehicle information includes vehicle identification information and vehicle signal data; Determining whether a battery thermal runaway event occurs in the target vehicle according to the vehicle signal data; In the case where it is determined that a battery thermal runaway event occurs in the target vehicle, a target fault tree matching the vehicle identification information is matched from a preset fault tree set, wherein the fault tree set includes multiple fault trees corresponding to different vehicle models, and each fault tree includes multiple levels of root cause nodes and logical relationships between the multiple levels of root cause nodes; Performing root cause diagnosis on the battery thermal runaway event according to the vehicle signal data and the target fault tree to obtain a root cause diagnosis result; The step of performing root cause diagnosis on the battery thermal runaway event according to the vehicle signal data and the target fault tree to obtain a root cause diagnosis result includes: Acquiring corresponding vehicle signal data within a target time period from the vehicle signal data, wherein the target time period is determined based on the occurrence time point of the battery thermal runaway event and a preset duration; According to the vehicle signal data corresponding to the target time period, a target root cause node satisfying a judgment rule is determined from each root cause node of the target fault tree, wherein each root cause node in the target fault tree has its own corresponding judgment rule; The root cause diagnosis result is determined according to the target root cause node.
2. The root cause diagnosis method of a battery thermal runaway event according to claim 1, characterized in that: The target fault tree includes a first-level event node, a plurality of second-level root cause nodes and a plurality of third-level root cause nodes, wherein the logical relationship between the second-level root cause nodes is a logical OR relationship, and the logical relationship between the third-level root cause nodes under the same second-level root cause node is a logical OR relationship; The determining the root cause diagnosis result according to the target root cause node includes: In the case where the target root cause node belongs to a second-level root cause node, determining the root cause diagnosis result according to the fault root cause corresponding to the target root cause node; In the case where the target root cause node belongs to a third-level root cause node, the root cause diagnosis result is determined according to the fault root cause corresponding to the target root cause node and the fault root cause corresponding to the second-level root cause node associated with the target root cause node.
3. The root cause diagnosis method of battery thermal runaway event according to claim 2, characterized in that: The plurality of second-level root cause nodes include at least two of a battery manufacturing defect root cause node, a cell overheat root cause node, an electrical abuse root cause node, a voltage too low root cause node, a mechanical abuse root cause node, a high temperature root cause node, an insulation degradation root cause node, a short circuit root cause node, an overcharge root cause node, and an over-discharge root cause node; The third-level root cause node associated with the battery manufacturing defect root cause node includes at least one of an improper electrode material root cause node, an electrolyte contamination root cause node, and an insufficient quality control root cause node; The third-level root cause node associated with the electrical abuse root cause node includes at least one of a battery management system failure root cause node, an electric control system abnormality root cause node, and a cable looseness root cause node; The third-level root cause node associated with the mechanical abuse root cause node includes at least one of a collision root cause node and an extrusion root cause node; The third-level root cause node associated with the insulation degradation root cause node includes a battery aging root cause node; The third-level root cause node associated with the short circuit root cause node includes at least one of an external short circuit root cause node and an internal short circuit root cause node.
4. The root cause diagnosis method of a battery thermal runaway event according to claim 1, characterized in that: After performing root cause diagnosis on the battery thermal runaway event according to the vehicle signal data and the target fault tree to obtain a root cause diagnosis result, the method further includes: sending the root cause diagnosis result to a user terminal and an automobile fault prevention and control system associated with the target vehicle, wherein the automobile fault prevention and control system is used to send a remote control instruction to the target vehicle according to the root cause diagnosis result when the target vehicle is in an authorized state; and The fault handling result returned by the target vehicle in response to the remote control command is received, the fault handling result is stored, and the fault handling result is fed back to the user terminal, where the user terminal is used to display the root cause diagnosis result and the fault handling result.
5. The root cause diagnosis method of battery thermal runaway event according to claim 4, characterized in that: After sending the root cause diagnosis result to a user terminal and an automobile fault prevention and control system associated with the target vehicle, the method further includes: Determining whether the target vehicle is in an authorized state; When the target vehicle is not in an authorized state, an authorization application request is sent to the user terminal, wherein the authorization application request carries an authorization application reason and an authorization application deadline.
6. The root cause diagnosis method of battery thermal runaway event according to claim 1, characterized in that: Before matching a target fault tree matching the vehicle identification information from a preset fault tree set, the method further includes: Acquire and compare signal data in a database file corresponding to a first vehicle model with signal data in a database file corresponding to a second vehicle model; In a case where the signal data in the database file corresponding to the first vehicle type matches the signal data in the database file corresponding to the second vehicle type, determining the fault tree corresponding to the first vehicle type as the fault tree corresponding to the second vehicle type; When the signal data in the database file corresponding to the first vehicle model and the signal data in the database file corresponding to the second vehicle model do not match, the root cause node and the judgment rule of the root cause node in the fault tree corresponding to the first vehicle model are modified to obtain the fault tree corresponding to the second vehicle model.
7. The root cause diagnosis method of battery thermal runaway event according to claim 1, characterized in that: The determining, based on the vehicle signal data, whether a battery thermal runaway event occurs in the target vehicle includes: Obtaining a parsing file that matches the vehicle identification information; Parsing the vehicle signal data using the parsing file, and determining whether a target field in the parsed vehicle signal data is a preset value and the duration reaches a preset duration; When it is determined that the target field in the parsed vehicle signal data is a preset value and the duration reaches a preset duration, it is determined that the battery thermal runaway event occurs in the target vehicle.
8. A root cause diagnosis device for battery thermal runaway events, characterized in that: The device comprises: A first receiving module, configured to receive vehicle information reported by a target vehicle, wherein the vehicle information includes vehicle identification information and vehicle signal data; A first determination module, configured to determine whether a battery thermal runaway event occurs in the target vehicle according to the vehicle signal data; A matching module, configured to match a target fault tree matching the vehicle identification information from a preset fault tree set when it is determined that a battery thermal runaway event occurs in the target vehicle, wherein the fault tree set includes a plurality of fault trees corresponding to different vehicle models, and each fault tree includes a plurality of root cause nodes and a logical relationship between the plurality of root cause nodes; A diagnosis module, configured to perform root cause diagnosis on the battery thermal runaway event according to the vehicle signal data and the target fault tree to obtain a root cause diagnosis result; Wherein, the diagnostic module comprises: A first acquisition submodule, configured to acquire vehicle signal data corresponding to a target time period from the vehicle signal data, wherein the target time period is determined based on a time point of occurrence of the battery thermal runaway event and a preset duration; A first determination submodule is used to determine a target root cause node that meets a judgment rule from each root cause node of the target fault tree according to the vehicle signal data corresponding to the target time period, wherein each root cause node in the target fault tree has its own corresponding judgment rule; The second determining submodule is used to determine the root cause diagnosis result according to the target root cause node.
9. An electronic device, characterized in that: It includes a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory communicate with each other through the communication bus; Memory, used to store computer programs; The processor is used to implement the root cause diagnosis method of a battery thermal runaway event as described in any one of claims 1 to 7 when executing a program stored in the memory.
