A task processing method, a battery management system, a battery device and a power utilization equipment

Abstract

The application discloses a task processing method, a battery management system, a battery device and a power utilization equipment, and relates to the technical field of battery management. In the case that system state data meets a preset triggering condition, the method determines an abnormal static task in the static task of the battery management system based on the system state data, and performs suspension processing on the abnormal static task, so that the abnormal data is prevented from spreading. In addition, after the abnormal static task is suspended, the scheme also enables a backup task corresponding to the abnormal static task, which is used to replace the abnormal static task to realize the corresponding function. In this way, the method suspends the abnormal static task when the abnormality occurs, avoids the abnormality of the task from spreading to other tasks, and guarantees the safety and reliability of the system. Moreover, in order to avoid the influence of system restart on work efficiency, the scheme also enables the corresponding backup task, so that the system can continue to normally operate.

Description

Technical Field

[0001] This application relates to the field of battery management technology, and in particular to a task processing method for a battery management system, a battery management system, a battery device, and an electrical device. Background Technology

[0002] In a battery management system, there are some static tasks. The execution flow and parameters of these static tasks are determined before the system runs and remain relatively unchanged during operation. However, these static tasks may encounter abnormal situations during system operation. If appropriate handling measures are not taken in time, the resulting abnormal data will be transmitted between multiple tasks, thereby affecting more tasks and seriously impacting the system's safety and reliability.

[0003] Currently, the common solution for encountering abnormal static tasks is to restart the system, thereby initializing the system and re-executing each task to avoid the anomaly. However, restarting the system will result in the loss of intermediate data that has already been calculated, severely impacting the system's efficiency. Summary of the Invention

[0004] This application provides a task processing method for a battery management system, a battery management system, a battery device, and an electrical device, which can ensure the system's working efficiency while guaranteeing system safety and stability.

[0005] In a first aspect, this application provides a task processing method for a battery management system, including:

[0006] Obtain system status data from the battery management system;

[0007] If the system status data meets the preset triggering conditions, based on the system status data, an abnormal static task is determined in the static tasks of the battery management system.

[0008] The abnormal static task is paused.

[0009] Enable the backup task corresponding to the abnormal static task; the backup task is a task that is pre-set in the battery management system and has the same function as the abnormal static task.

[0010] The task processing method of the battery management system in this embodiment acquires system status data during the execution of static tasks in the battery management system. If the system status data meets preset trigger conditions, it indicates the existence of an abnormal static task in the battery management system. At this point, it is necessary to promptly identify the abnormal static task and take corresponding measures; otherwise, the transmission of abnormal data between different tasks may cause serious security problems for the system. Therefore, this application, based on system status data, identifies abnormal static tasks within the static tasks of the battery management system and suspends these tasks to prevent the spread of abnormal data. Furthermore, after suspending the abnormal static task, this solution also activates a backup task corresponding to the abnormal static task to replace it and implement the corresponding function.

[0011] Thus, this method pauses abnormal static tasks when an anomaly occurs, preventing the anomaly from spreading to other tasks and ensuring system security and reliability. Furthermore, to avoid impacting work efficiency by restarting the system, this solution also activates corresponding backup tasks, ensuring the system can continue to operate normally.

[0012] In one possible implementation, after pausing the abnormal static task, the method further includes:

[0013] The data corresponding to the abnormal static task is moved to the target memory region; the target memory region is isolated from the memory region corresponding to the normal task in the battery management system.

[0014] In this implementation, after pausing the abnormal static task, the data corresponding to the abnormal static task is moved to the target memory area. This isolates the abnormal static task, preventing other tasks from accessing the target memory area. This avoids other tasks continuing to use the data from the abnormal static task, thus preventing the further propagation of abnormal data and impacting system security and stability. Therefore, this solution further prevents data generated by abnormal static tasks from affecting other tasks, thereby ensuring system security and reliability.

[0015] In one possible implementation, after activating the backup task corresponding to the abnormal static task, the method further includes:

[0016] If the backup task fails, and the failure attributes of at least one of the failed static task and the backup task meet the restart conditions, a target task is selected from the failed static task and the backup task; the failure attributes include the failure type and the failure severity.

[0017] Initialize the target task;

[0018] Re-execute the target task.

[0019] This implementation proposes a solution for situations where the backup task malfunctions. Since the backup task is activated to replace the malfunctioning static task, if the system is not restarted when the backup task malfunctions, a task must be selected from the malfunctioning static task and the backup task for initialization and re-execution. This solution uses a restart condition as a criterion. If the malfunction attribute of at least one task among the malfunctioning static task and the backup task meets the restart condition, a target task is selected for initialization and re-execution, thus avoiding the impact of restarting the system on overall system efficiency.

[0020] In one possible implementation, selecting a target task from the abnormal static task and the backup task includes:

[0021] If only one of the abnormal static tasks and the backup tasks has an abnormal attribute that satisfies the restart condition, the task that satisfies the restart condition will be identified as the target task.

[0022] In this implementation, a specific scheme for selecting the target task is provided. If only one of the abnormal static tasks and the backup tasks has an abnormal attribute that meets the restart condition, then the task whose abnormal attribute meets the restart condition can be directly identified as the target task. This method is simple to implement and can quickly identify the target task.

[0023] In one possible implementation, selecting a target task from the abnormal static task and the backup task includes:

[0024] If the abnormal attributes of both the abnormal static task and the backup task meet the restart conditions, determine the degree of impact of the corresponding abnormality on the battery management system in both the abnormal static task and the backup task.

[0025] The task with the smaller impact on the battery management system is identified as the target task.

[0026] This implementation provides another specific solution for selecting the target task. If the exception attributes of both the abnormal static task and the backup task meet the restart conditions, either one can be selected for initialization. To reduce the probability of system anomalies, this solution identifies the task with the smaller impact on the battery management system from the abnormal static task and backup task, and designates this task as the target task. Thus, after initializing and re-executing the target task, the probability of system anomalies is lower, and even if an anomaly occurs, this solution can reduce the impact on the battery management system.

[0027] In one possible implementation, after activating the backup task corresponding to the abnormal static task, the method further includes:

[0028] If the backup task malfunctions, and neither the malfunctioning static task nor the malfunctioning attributes of the backup task meet the restart conditions, the battery management system will be restarted.

[0029] This implementation proposes an alternative solution for when a backup task fails. If a backup task fails and neither the abnormal static task nor the abnormal attributes of the backup task meet the restart conditions, the battery management system is directly restarted, thereby prioritizing system security.

[0030] In one possible implementation, after activating the backup task corresponding to the abnormal static task, the method further includes:

[0031] If the backup task encounters an anomaly, and the anomaly attributes of both the abnormal static task and the backup task do not meet the restart conditions, an anomaly message corresponding to the abnormal static task will be output.

[0032] In this implementation, by outputting the abnormal prompt information corresponding to the abnormal static task, staff can quickly determine the cause of the system abnormality and then take corresponding measures to ensure the system's security and stability.

[0033] In one possible implementation, acquiring system status data from the battery management system includes any one or any combination of the following:

[0034] Based on the sensors of the battery management system, acquire corresponding sensor data;

[0035] Based on the communication bus of the battery management system, fault code information is obtained;

[0036] Based on the battery corresponding to the battery management system, obtain battery power data;

[0037] During the execution of the static task, task data related to the static task is acquired based on the monitoring task.

[0038] In this implementation, hardware data is acquired through sensors, communication buses, and corresponding batteries within the battery management system. During task execution, task data is also acquired based on the monitoring task. This approach enables comprehensive and efficient monitoring of the battery management system, effectively improving its security.

[0039] In one possible implementation, acquiring the system status data from the battery management system includes:

[0040] The system status data is acquired at the key nodes of the static task; the key nodes include any one or any combination of the following: data receiving node, data verification node, data processing node, data storage node, and data transmission node.

[0041] This implementation acquires data only at key nodes of static tasks, enabling efficient monitoring of system anomalies. This is because acquiring and analyzing data at all points in the task execution would result in an excessively large amount of data to process, increasing system resource pressure. Furthermore, some of the acquired data would be invalid and not very useful for monitoring system anomalies. Therefore, this implementation only acquires system status data at key nodes of static tasks, thereby reducing system resource pressure and enabling efficient anomaly monitoring.

[0042] In one possible implementation, after determining the abnormal static task in the static tasks of the battery management system based on the system state data, when the system state data meets the preset triggering conditions, the method further includes:

[0043] Determine the preset key tasks in the battery management system; the preset key tasks are those whose importance indicators meet preset requirements.

[0044] The preset critical tasks are allocated system resources that are isolated from the system resources of other tasks.

[0045] In this implementation, to reduce the probability of anomalies in some preset critical tasks within the battery management system, system resources that are isolated from other tasks are allocated to these preset critical tasks. These preset critical tasks are of high importance to the battery management system and require guaranteed normal and stable operation. Therefore, after identifying abnormal static tasks, this solution allocates independent system resources to these preset critical tasks to isolate them from the abnormal static tasks, thereby preventing abnormal data generated by the abnormal static tasks from affecting the preset critical tasks.

[0046] Secondly, this application provides a battery management system, including:

[0047] Sampling circuit, used to acquire system status data in the battery management system;

[0048] The processor is configured to, based on the system state data, determine an abnormal static task in the static tasks of the battery management system when the system state data meets a preset triggering condition.

[0049] The processor is also used to pause the abnormal static task;

[0050] The processor is also configured to enable a backup task corresponding to the abnormal static task; the backup task is a task pre-set in the battery management system and has the same function as the abnormal static task.

[0051] Thirdly, this application provides a battery device, including the aforementioned battery management system and a corresponding battery.

[0052] Fourthly, this application provides an electrical device including the aforementioned battery device.

[0053] The above description is only an overview of the technical solution of this application. In order to better understand the technical means of this application and to implement it in accordance with the contents of the specification, and to make the above and other objects, features and advantages of this application more obvious and understandable, specific embodiments of this application are given below. Attached Figure Description

[0054] Various other advantages and benefits will become apparent to those skilled in the art upon reading the detailed description of the preferred embodiments below. The accompanying drawings are for illustrative purposes only and are not intended to limit the scope of this application. Furthermore, the same reference numerals denote the same parts throughout the drawings. In the drawings:

[0055] Figure 1 A flowchart illustrating a task processing method for a first battery management system provided in some embodiments of this application;

[0056] Figure 2 A flowchart illustrating a task processing method for a second battery management system provided in some embodiments of this application;

[0057] Figure 3 A flowchart illustrating a task processing method for a third battery management system provided in some embodiments of this application;

[0058] Figure 4 A flowchart illustrating a fourth battery management system task processing method provided in some embodiments of this application;

[0059] Figure 5 A flowchart illustrating a fifth battery management system task processing method provided in some embodiments of this application;

[0060] Figure 6 A flowchart illustrating a sixth battery management system task processing method provided in some embodiments of this application;

[0061] Figure 7 This is a schematic diagram of the structure of a battery management system provided in some embodiments of this application. Detailed Implementation

[0062] The embodiments of the technical solution of this application will now be described in detail with reference to the accompanying drawings. These embodiments are only used to more clearly illustrate the technical solution of this application and are therefore merely examples, and should not be used to limit the scope of protection of this application.

[0063] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application pertains; the terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the application; the terms “comprising” and “having”, and any variations thereof, in the specification, claims, and foregoing description of the drawings are intended to cover non-exclusive inclusion.

[0064] In the description of the embodiments of this application, technical terms such as "first" and "second" are used only to distinguish different objects and should not be construed as indicating or implying relative importance or implicitly specifying the number, specific order, or primary and secondary relationship of the indicated technical features. In the description of the embodiments of this application, "multiple" means two or more, unless otherwise explicitly defined.

[0065] In this document, the term "embodiment" means that a particular feature, structure, or characteristic described in connection with an embodiment may be included in at least one embodiment of this application. The appearance of this phrase in various places throughout the specification does not necessarily refer to the same embodiment, nor is it a separate or alternative embodiment mutually exclusive with other embodiments. It will be explicitly and implicitly understood by those skilled in the art that the embodiments described herein can be combined with other embodiments.

[0066] In the description of the embodiments in this application, the term "and / or" is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, and B existing alone. Additionally, the character " / " in this document generally indicates that the preceding and following related objects have an "or" relationship.

[0067] In the description of the embodiments of this application, the term "multiple" refers to two or more (including two), similarly, "multiple sets" refers to two or more (including two sets), and "multiple pieces" refers to two or more (including two pieces).

[0068] A battery management system (BMS) is an electronic system used to manage and monitor batteries, playing a crucial role in various battery-using devices and scenarios. Therefore, maintaining the normal operation of the BMS and ensuring its safety and efficiency are extremely important.

[0069] In a battery management system, there are some static tasks. These tasks have their execution flow and parameters determined before the system runs, cannot be deleted, and remain relatively fixed during operation. However, during system runtime, these static tasks may encounter abnormal situations. If appropriate handling measures are not taken in a timely manner, the resulting abnormal data will be transmitted between multiple tasks, affecting even more tasks and severely impacting the system's security and reliability.

[0070] Currently, when abnormal static tasks occur, the solution is to directly restart the entire system. However, restarting the system results in the loss of intermediate data that has already been calculated, severely impacting system efficiency. Furthermore, in some cases, a system restart may even cause problems for the entire device.

[0071] It is evident that system restarts should be avoided as much as possible during system operation. However, if an anomaly occurs in a static task, corresponding handling measures must be taken; otherwise, the transmission of abnormal data between multiple tasks could lead to more serious consequences. Therefore, it is necessary to further ensure work efficiency while guaranteeing system security.

[0072] Considering the characteristics of static tasks, each static task has its execution flow and parameters determined before system operation and remain relatively fixed during operation. Therefore, this application proposes designing a backup task with the same function as the static task. This backup task can correspond one-to-one with the static task, and is used to activate the corresponding backup task when a static task encounters an anomaly. In other words, the backup task replaces the abnormal static task, allowing the battery management system to continue execution and ensuring system efficiency. Simultaneously, pausing abnormal static tasks can prevent their abnormal data from affecting other tasks.

[0073] Therefore, based on the above ideas, this application provides a task processing method for a battery management system. Figure 1 This is a flowchart illustrating a task processing method for a first battery management system provided in some embodiments of this application. Figure 1 As shown, the method may include the following steps: S101 to S104.

[0074] S101: Obtain system status data from the battery management system.

[0075] During the operation of a battery management system (BMS), static tasks are executed according to a preset process. These static tasks are relatively fixed and periodically executed, independent of real-time dynamic changes in the battery. During the execution of these static tasks, abnormal situations may occur, leading to anomalous data. If this anomalous data is allowed to propagate between tasks, it could cause the entire system to crash. Therefore, it is necessary to acquire system status data in real time to monitor these static tasks.

[0076] This document does not limit the specific content of the system status data. As an optional embodiment, the system status data may include hardware and software data of the battery management system. For example, hardware data may include sensor data, communication bus data, and battery-related data, etc. Software data (task data) may include resource utilization, task queue length, and processor load corresponding to task execution, etc.

[0077] S102: If the system status data meets the preset triggering conditions, based on the system status data, determine the abnormal static task in the static tasks of the battery management system.

[0078] In this implementation, preset trigger conditions need to be defined in advance, and then the presence of system anomalies is determined based on the preset trigger conditions and real-time acquired system status data. This embodiment does not specifically limit the content of the preset trigger conditions. As some feasible implementation methods, preset trigger conditions may include the battery management system's battery charging exceeding a safety threshold, the appearance of specific serious fault codes on the communication bus, battery power exceeding a critical value, sensor malfunction, and the resource utilization rate of tasks, task queue length, and processor load exceeding thresholds, etc. These situations may cause related static tasks to fail to obtain accurate data, leading to data anomalies.

[0079] When system status data meets preset trigger conditions, an abnormal static task is identified. Therefore, it is necessary to determine the abnormal static task from the static tasks of the battery management system based on the system status data. In practical applications, the corresponding abnormal static task can be determined based on the correspondence between system status data and static tasks, according to the abnormal system status data.

[0080] S103: Pause abnormal static tasks.

[0081] To prevent anomalies from a static task from spreading to other tasks, it needs to be paused. The specific implementation of this pause is not limited here; as an optional implementation, task pause can be achieved by sending an interrupt signal.

[0082] In addition, to further ensure that anomalies in abnormal static tasks are not propagated to other tasks, the corresponding abnormal data can be isolated when an abnormal static task is detected, thereby preventing other tasks from continuing to use the abnormal data.

[0083] S104: Enable the backup task corresponding to the abnormal static task.

[0084] Backup tasks are pre-configured in the battery management system and have the same function as the abnormal static task. For abnormal static tasks, they need to be paused promptly to prevent the anomaly from spreading. After pausing an abnormal static task, to ensure the system can continue operating, the corresponding backup task needs to be activated. Typically, backup tasks correspond one-to-one with static tasks, so when a static task malfunctions, a corresponding backup task can be obtained to replace it.

[0085] As can be seen, when the system status data meets the preset triggering conditions, it indicates the existence of an abnormal static task in the battery management system. At this point, it is necessary to promptly identify the abnormal static task and take corresponding measures; otherwise, the transmission of abnormal data between different tasks may cause serious security problems for the system. In this implementation, based on the system status data, the abnormal static task is identified within the static tasks of the battery management system and suspended, thereby preventing the spread of abnormal data. Furthermore, after suspending the abnormal static task, this solution also activates a backup task corresponding to the abnormal static task to replace it and implement the corresponding function.

[0086] The task processing method of the battery management system in this embodiment acquires system status data during the execution of static tasks in the battery management system. If the system status data meets preset trigger conditions, it indicates the existence of an abnormal static task in the battery management system. At this point, it is necessary to promptly identify the abnormal static task and take corresponding measures; otherwise, the transmission of abnormal data between different tasks may cause serious security problems for the system. Therefore, this application, based on system status data, identifies abnormal static tasks within the static tasks of the battery management system and suspends these tasks to prevent the spread of abnormal data. Furthermore, after suspending the abnormal static task, this solution also activates a backup task corresponding to the abnormal static task to replace it and implement the corresponding function.

[0087] Thus, this method pauses abnormal static tasks when an anomaly occurs, preventing the anomaly from spreading to other tasks and ensuring system security and reliability. Furthermore, to avoid impacting work efficiency by restarting the system, this solution also activates corresponding backup tasks, ensuring the system can continue to operate normally.

[0088] In practice, even when an abnormal static task is paused, other tasks may still access the data generated by the abnormal static task, leading to the propagation of the anomaly. Therefore, to completely avoid the impact of abnormal static tasks on the system, the relevant data needs to be isolated. This application provides a feasible implementation method. Figure 2 This is a flowchart illustrating a second battery management system task processing method provided in some embodiments of this application. Figure 2 As shown, after S103, the method may further include:

[0089] S105: Move the data corresponding to the abnormal static task to the target memory range.

[0090] The target memory region is isolated from the memory regions corresponding to normal tasks in the battery management system. Normal tasks cannot access the target memory region, thus achieving isolation of abnormal static tasks. Therefore, after pausing an abnormal static task, moving the relevant data to the target memory region can achieve data isolation, thereby preventing other tasks from continuing to access this data.

[0091] In this implementation, after pausing the abnormal static task, the data corresponding to the abnormal static task is moved to the target memory area. This isolates the abnormal static task and prevents other tasks from continuing to use its data, which could lead to further propagation of abnormal data and affect the system's security and stability. Therefore, this solution further prevents data generated by abnormal static tasks from affecting other tasks, thus ensuring the system's security and reliability.

[0092] In one possible implementation, after enabling the backup task corresponding to the abnormal static task, the backup task may also encounter an error. In this case, to avoid restarting the system, a task can be re-executed. However, to avoid serious problems caused by re-execution, this application provides a solution. Figure 3 This is a flowchart illustrating a task processing method for a third battery management system provided in some embodiments of this application. For example... Figure 3 As shown, after S104, the method may further include the following steps: S106 to S108.

[0093] S106: If an exception occurs in the standby task, and the exception attribute of at least one of the abnormal static task and the standby task meets the restart condition, select the target task from the abnormal static task and the standby task.

[0094] As mentioned above, the backup task is enabled to replace the abnormal static task. Therefore, if the backup task encounters an error, to avoid directly restarting the system, only one target task can be selected from the abnormal static task and the backup task for re-execution. However, at this time, both the corresponding static task and the backup task have encountered errors, and direct re-execution may cause errors again. Therefore, this implementation analyzes the abnormal attributes of the abnormal static task and the backup task to determine whether it is suitable to re-execute them.

[0095] In this implementation, the restart condition is used as the basis for determining whether the task is suitable for re-execution, and the specific content of the restart condition is not limited; similarly, the specific content of the exception attribute is also not limited, and can be determined according to the actual situation.

[0096] As an optional implementation, the exception attributes can specifically include the exception type and the exception severity; different exception types and severity levels have different impacts on the system. Generally, exception attributes that meet the restart conditions will not have a serious impact on the battery management system. For example, if the exception involves system security, such as unauthorized access, it is considered unsuitable to re-execute the corresponding task. If it is merely a static task consuming excessive hardware resources, then the suitability for re-execution can be determined based on the degree of resource consumption.

[0097] Furthermore, this implementation does not limit the specific method of selecting the target task, which can be set according to the actual situation. In one possible implementation, selecting the target task from the abnormal static task and the backup task may include: if only one task among the abnormal static task and the backup task has an abnormal attribute that satisfies the restart condition, then the task that satisfies the restart condition is determined as the target task.

[0098] In this implementation, a specific scheme for selecting the target task is provided. If only one of the abnormal static tasks and the backup tasks has an abnormal attribute that meets the restart condition, then the task whose abnormal attribute meets the restart condition can be directly identified as the target task. This method is simple to implement and can quickly identify the target task.

[0099] In another possible implementation, a target task is selected from the abnormal static task and the backup task. This includes: if the abnormal attributes of both the abnormal static task and the backup task meet the restart conditions, determining the impact value of the corresponding abnormality on the battery management system from among the abnormal static task and the backup task; and identifying the task with the smaller impact value on the battery management system as the target task. For example, if the abnormality is that the processor load exceeds a threshold, the corresponding impact value can be determined according to the severity of the load overload; the more severe the load overload, the greater the impact value.

[0100] This implementation provides another specific solution for selecting the target task. If the exception attributes of both the abnormal static task and the backup task meet the restart conditions, either one can be chosen for initialization. To reduce the probability of system exceptions, this solution identifies the task with the smaller impact on the battery management system from the abnormal static task and backup task, and designates this task as the target task. Thus, after initializing and re-executing the target task, the probability of system exceptions is lower, and even if exceptions occur, this solution can reduce the impact of the exception on the battery management system.

[0101] S107: Initialize the target task.

[0102] S108: Re-execute the target task.

[0103] After selecting the target task, it needs to be initialized to clear any abnormal data and prevent it from affecting the execution of subsequent tasks. After initializing the target task, it should be re-executed. Due to the judgment of the target task's abnormal attributes mentioned above, serious abnormalities are unlikely to occur after the target task is re-executed, allowing the system to maintain normal operation.

[0104] This implementation proposes a solution for situations where the backup task malfunctions. Since the backup task is activated to replace the malfunctioning static task, if the system is not restarted when the backup task malfunctions, a task must be selected from the malfunctioning static task and the backup task for initialization and re-execution. This solution uses a restart condition as a criterion. If the malfunction attribute of at least one task among the malfunctioning static task and the backup task meets the restart condition, a target task is selected for initialization and re-execution, thus avoiding the impact of restarting the system on overall system efficiency.

[0105] The above embodiment mentions that if a backup task encounters an anomaly, and the anomaly attributes of at least one of the abnormal static task and the backup task meet the restart conditions, a target task can be selected from the abnormal static task and the backup task for re-execution. However, if the anomaly attributes of neither the abnormal static task nor the backup task meet the restart conditions, re-executing both tasks may lead to serious anomalies. In this case, restarting the system can be chosen, although it may reduce work efficiency, it can ensure system security. This embodiment provides a specific implementation method. Figure 4 This is a flowchart illustrating a fourth battery management system task processing method provided in some embodiments of this application. For example... Figure 4 As shown, after S104, the method may further include:

[0106] S109: If an exception occurs in the standby task, and neither the exception static task nor the exception attributes of the standby task meet the restart conditions, restart the battery management system.

[0107] As mentioned above, when a backup task encounters an anomaly, initializing and re-executing the task should be the first priority to avoid excessively impacting system efficiency. However, if neither the abnormal static task nor the backup task's anomaly attributes meet the restart conditions, simply initializing and re-executing the task will not solve the problem and may even lead to serious security issues. In such cases, prioritizing efficiency may result in even more severe consequences.

[0108] This implementation proposes an alternative solution for when a backup task fails. If a backup task fails and neither the abnormal static task nor the abnormal attributes of the backup task meet the restart conditions, the battery management system is directly restarted, thereby prioritizing system security.

[0109] The above embodiments propose that the battery management system can be directly restarted when a backup task malfunctions and neither the abnormal static task nor the abnormal attributes of the backup task meet the restart conditions. However, restarting the system may result in the loss of all intermediate data, making it difficult for staff to analyze the cause of the malfunction later. Therefore, this application provides a possible implementation method. Figure 5 This is a flowchart illustrating a fifth battery management system task processing method provided in some embodiments of this application. Figure 5 As shown, after S104, the method may further include:

[0110] S110: If an exception occurs in the standby task, and neither the exception static task nor the exception attributes of the standby task meet the restart conditions, output the exception message corresponding to the exception static task.

[0111] To address the issue that restarting the system might result in the loss of all intermediate data, making it difficult for staff to analyze the cause of the anomaly, this implementation proposes outputting exception messages for the abnormal static tasks to alert staff to the specific static tasks experiencing the anomaly. By outputting these exception messages, this solution enables staff to quickly identify the cause of the system anomaly and then take appropriate measures to ensure system security and stability.

[0112] As mentioned above, the system status data in a battery management system may include hardware data and software data, etc. To quickly obtain the corresponding data, some feasible implementation methods are provided here. Obtaining system status data from a battery management system includes any one or any combination of the following:

[0113] First, the processor, which is connected to the sensors of the battery management system, can acquire sensor data corresponding to each sensor, and the sensor data can be used to monitor whether there is a sensor malfunction.

[0114] Secondly, fault code information can be obtained based on the communication bus of the battery management system. If a fault code exists, it can be determined that the system status data meets the preset trigger conditions.

[0115] Third, based on the batteries corresponding to the battery management system, battery power data can be obtained. When parameters such as battery charge and power exceed thresholds, the system status data can be determined to meet preset trigger conditions. A battery management system typically includes a dedicated power monitoring circuit connected to each individual cell or battery module in the battery pack. These circuits can measure parameters such as battery voltage, current, and temperature in real time. By measuring the battery's open-circuit voltage and combining it with the battery's characteristic curve (which describes the relationship between battery voltage and remaining power), a preliminary estimate of the battery's power can be made. Furthermore, by integrating the battery's charging and discharging current, the amount of power charged and discharged can be accurately calculated, thus providing a more accurate understanding of the battery's remaining power.

[0116] Fourth, during the execution of static tasks, task data related to the static tasks can be obtained based on the monitoring tasks, such as task queue length, resource utilization, and processor load. Specifically, the relevant hardware resources can be monitored to obtain resource utilization and processor load, and the task queue length can be obtained from the task-related data.

[0117] In this implementation, hardware data is acquired through sensors, communication buses, and corresponding batteries within the battery management system. During task execution, task data is also acquired based on the monitoring task. This approach enables comprehensive and efficient monitoring of the battery management system, effectively improving its security.

[0118] In practical applications, acquiring and analyzing data at every point in the task execution would result in an excessively large amount of data to process, thus increasing the pressure on system resources. Furthermore, some of this acquired data is invalid and not very useful for monitoring system anomalies.

[0119] Therefore, this paper provides a possible implementation for acquiring system status data in a battery management system, which may include acquiring system status data at key nodes of static tasks. Key nodes include any one or any combination of the following: data receiving nodes, data verification nodes, data processing nodes, data storage nodes, and data transmission nodes. Acquiring data at these nodes can effectively achieve system anomaly monitoring.

[0120] Because this implementation method only obtains system status data at key nodes of static tasks, it can avoid obtaining some invalid data, reduce the amount of data that needs to be processed, reduce the system's resource pressure, and efficiently monitor anomalies.

[0121] For battery management systems, there are some critical pre-defined tasks of high importance, such as battery monitoring. Abnormalities in these tasks could lead to serious consequences. Therefore, this paper presents a feasible implementation method. Figure 6 This is a flowchart illustrating a sixth battery management system task processing method provided in some embodiments of this application. For example... Figure 6 As shown, after S102, the method may further include:

[0122] S111: Determine the preset key tasks in the battery management system.

[0123] This application does not limit the specific task types of the preset key tasks, which can be determined according to the actual situation. As some optional implementation methods, these preset key tasks are tasks whose importance indicators meet preset requirements, that is, tasks that have a certain impact on the safe operation of electrical equipment and the normal execution of the battery management system. The corresponding importance indicators can be determined based on the severity of the consequences caused by the task's abnormality. Specifically, these may include battery status monitoring, battery safety management, battery charge and discharge control, battery equalization management, and thermal management tasks, etc.

[0124] S112: Allocate system resources that are isolated from the system resources of other tasks to preset critical tasks.

[0125] In this implementation, to reduce the probability of anomalies in some preset critical tasks within the battery management system, system resources that are isolated from other tasks are allocated to these preset critical tasks. These preset critical tasks are of high importance to the battery management system and require guaranteed normal and stable operation. Therefore, after identifying abnormal static tasks, this solution allocates independent system resources to these preset critical tasks to isolate them from the abnormal static tasks, thereby preventing abnormal data generated by the abnormal static tasks from affecting the preset critical tasks.

[0126] To address the aforementioned technical problems, this application also provides a battery management system. Figure 7 This is a schematic diagram of the structure of a battery management system provided in some embodiments of this application. For example... Figure 7 As shown, the battery management system includes:

[0127] The sampling circuit 701 is used to acquire system status data in the battery management system.

[0128] The processor 702 is used to determine abnormal static tasks in the static tasks of the battery management system based on the system status data when the system status data meets the preset triggering conditions.

[0129] Processor 702 is also used to pause abnormal static tasks;

[0130] The processor 702 is also used to enable a backup task corresponding to the abnormal static task; the backup task is a task that is pre-set in the battery management system and has the same function as the abnormal static task.

[0131] This method pauses abnormal static tasks when an anomaly occurs, preventing the anomaly from spreading to other tasks and ensuring system security and reliability. Furthermore, to avoid impacting work efficiency by restarting the system, this solution also activates corresponding backup tasks, ensuring the system can continue to operate normally.

[0132] The battery management system provided in this application has the same embodiments and beneficial effects as the battery health status determination method provided above, and will not be repeated here.

[0133] To address the aforementioned technical problems, this application also provides a battery device, which includes the battery and battery management system mentioned in the above embodiments. The battery device provided in this application has the same embodiments and beneficial effects as the battery management system described above, and will not be repeated here.

[0134] To address the aforementioned technical problems, this application also provides an electrical device, including the battery device mentioned above. The electrical device provided in this application has the same embodiments and beneficial effects as the battery device described above, and will not be repeated here.

[0135] It should be clarified that this application is not limited to the specific configurations and processes described above and shown in the figures. For the sake of brevity, detailed descriptions of known methods are omitted here. In the above embodiments, several specific steps are described and shown as examples. However, the method process of this application is not limited to the specific steps described and shown. Those skilled in the art can make various changes, modifications, and additions, or change the order of steps, after understanding the spirit of this application.

[0136] The functional blocks shown in the above-described block diagram can be implemented as hardware, software, firmware, or a combination thereof. When implemented in hardware, they can be, for example, electronic circuits, application-specific integrated circuits (ASICs), appropriate firmware, plug-ins, function cards, etc. When implemented in software, the elements of this application are programs or code segments used to perform the required tasks. Programs or code segments can be stored on a machine-readable medium or transmitted over a transmission medium or communication link via data signals carried on a carrier wave. "Machine-readable medium" can include any medium capable of storing or transmitting information. Examples of machine-readable media include electronic circuits, semiconductor memory devices, read-only memory (ROM), flash memory, erasable-ROM (E-ROM), floppy disks, compact disc-ROMs (CD-ROMs), optical disks, hard disks, fiber optic media, radio frequency (RF) links, etc. Code segments can be downloaded via computer networks such as the Internet, intranets, etc.

[0137] It should also be noted that the exemplary embodiments mentioned in this application describe methods or systems based on a series of steps or apparatus. However, this application is not limited to the order of the above steps; that is, the steps can be performed in the order mentioned in the embodiments, or in a different order, or several steps can be performed simultaneously.

[0138] The foregoing flowcharts and / or block diagrams of methods, apparatus (systems) according to embodiments of this application have described various aspects of the present application. It should be understood that each block in the flowcharts and / or block diagrams, and combinations of blocks in the flowcharts and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus to create a machine such that these instructions, executable via the processor of the computer or other programmable data processing apparatus, enable the implementation of the functions / actions specified in one or more blocks of the flowcharts and / or block diagrams. Such a processor can be, but is not limited to, a general-purpose processor, a special-purpose processor, a special application processor, or a field-programmable logic circuit. It is also understood that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can also be implemented by dedicated hardware performing the specified functions or actions, or can be implemented by a combination of dedicated hardware and computer instructions.

[0139] Although this application has been described with reference to preferred embodiments, various modifications can be made thereto and components can be replaced with equivalents without departing from the scope of this application. In particular, the technical features mentioned in the various embodiments can be combined in any manner, provided there is no structural conflict. This application is not limited to the specific embodiments disclosed herein, but includes all technical solutions falling within the scope of the claims.

Claims

1. A task processing method for a battery management system, characterized in that, include: Obtain system status data from the battery management system; If the system status data meets the preset triggering conditions, based on the system status data, an abnormal static task is determined in the static tasks of the battery management system. The abnormal static task is paused. Enable the backup task corresponding to the abnormal static task; the backup task is a task that is pre-set in the battery management system and has the same function as the abnormal static task.

2. The task processing method of the battery management system according to claim 1, characterized in that, After pausing the abnormal static task, the method further includes: The data corresponding to the abnormal static task is moved to the target memory region; the target memory region is isolated from the memory region corresponding to the normal task in the battery management system.

3. The task processing method of the battery management system according to claim 1 or 2, characterized in that, After activating the backup task corresponding to the abnormal static task, the method further includes: If the backup task fails, and the failure attributes of at least one of the failed static task and the backup task meet the restart conditions, a target task is selected from the failed static task and the backup task; the failure attributes include the failure type and the failure severity. Initialize the target task; Re-execute the target task.

4. The task processing method of the battery management system according to claim 3, characterized in that, Among the abnormal static tasks and the backup tasks, the target task is selected, including: If only one of the abnormal static tasks and the backup tasks has an abnormal attribute that satisfies the restart condition, the task that satisfies the restart condition will be identified as the target task.

5. The task processing method of the battery management system according to claim 3, characterized in that, Among the abnormal static tasks and the backup tasks, the target task is selected, including: If the abnormal attributes of both the abnormal static task and the backup task meet the restart condition, determine the degree of impact of the abnormality of the task on the battery management system in both the abnormal static task and the backup task. The task with the smaller impact on the battery management system is identified as the target task.

6. The task processing method of the battery management system according to claim 1 or 2, characterized in that, After activating the backup task corresponding to the abnormal static task, the method further includes: If the backup task malfunctions, and neither the malfunctioning static task nor the malfunctioning attributes of the backup task meet the restart conditions, the battery management system shall be restarted.

7. The task processing method of the battery management system according to claim 6, characterized in that, After activating the backup task corresponding to the abnormal static task, the method further includes: If the backup task encounters an anomaly, and the anomaly attributes of both the abnormal static task and the backup task do not meet the restart conditions, an anomaly message corresponding to the abnormal static task will be output.

8. The task processing method of the battery management system according to claim 1, characterized in that, The acquisition of system status data from the battery management system includes any one or any combination of the following: Based on the sensors of the battery management system, acquire corresponding sensor data; Based on the communication bus of the battery management system, fault code information is obtained; Based on the battery corresponding to the battery management system, obtain battery power data; During the execution of the static task, task data related to the static task is acquired based on the monitoring task.

9. The task processing method of the battery management system according to any one of claims 1 to 8, characterized in that, The acquisition of system status data from the battery management system includes: The system status data is acquired at the key nodes of the static task; the key nodes include any one or any combination of the following: data receiving node, data verification node, data processing node, data storage node, and data transmission node.

10. The task processing method of the battery management system according to any one of claims 1 to 8, characterized in that, When the system status data meets preset triggering conditions, based on the system status data, after identifying the abnormal static task in the static tasks of the battery management system, the method further includes: Determine the preset key tasks in the battery management system; the preset key tasks are those whose importance indicators meet preset requirements. The preset critical tasks are allocated system resources that are isolated from the system resources of other tasks.

11. A battery management system, characterized in that, include: Sampling circuit, used to acquire system status data in the battery management system; The processor is configured to, based on the system state data, determine an abnormal static task in the static tasks of the battery management system when the system state data meets a preset triggering condition. The processor is also used to pause the abnormal static task; The processor is also configured to enable a backup task corresponding to the abnormal static task; the backup task is a task pre-set in the battery management system and has the same function as the abnormal static task.

12. A battery device, characterized in that, Includes the battery management system as described in claim 11 and the corresponding battery.

13. An electrical appliance, characterized in that, Includes the battery device as described in claim 12.

Images