Resource management method, system, device and equipment of battery management system

Abstract

The application discloses a resource management method, system and device of a battery management system and equipment, and belongs to the technical field of battery management. The method acquires an operation state of a battery and battery state data of the battery in the operation state; determines a system load of the battery management system according to the operation state and the battery state data; and gradually increases a working frequency of an operating system in the battery management system by a preset step length in a first time period until the working frequency reaches a target working frequency when the system load is greater than or equal to a corresponding load threshold. When the system load is too heavy, the working frequency of the CPU is increased, the processing speed of the task is improved, the task can be executed as soon as possible, and the response speed of the system is improved. Moreover, when the working frequency of the CPU is increased, the working frequency is gradually increased by the preset step length, the stability and reliability of the system are ensured while the response speed is improved, and the performance of the system is improved.

Description

Technical Field

[0001] This application relates to the field of battery management technology, and in particular to a resource management method, system, apparatus and equipment for a battery management system. Background Technology

[0002] For Battery Management Systems (BMS), when the system is heavily loaded, the operating system within the BMS needs to spend more time processing various battery management tasks, which can easily lead to increased task response time. For example, in a vehicle's safety-critical systems, if the response time of a braking-related task is delayed, it may cause the braking system to respond untimely, increasing the risk of a vehicle accident. Therefore, ensuring timely system response is of great importance when the system is heavily loaded. Summary of the Invention

[0003] This application provides a resource management method, system, device, and equipment for a battery management system, which can effectively solve the problem that some tasks cannot be executed in a timely manner due to excessive system load, thereby affecting system performance.

[0004] In a first aspect, embodiments of this application provide a resource management method for a battery management system, comprising:

[0005] Obtain the operating status of the battery corresponding to the battery management system and the battery status data under that operating status;

[0006] The system load of the battery management system is determined based on the operating status and battery status data.

[0007] When the system load is greater than or equal to the corresponding load threshold, the operating frequency of the operating system in the battery management system is gradually increased according to a preset step size within the first time period until the operating frequency reaches the target operating frequency.

[0008] In this embodiment, the operating status of the battery corresponding to the battery management system and the battery status data under that operating status are acquired. Based on the operating status and battery status data, the system load of the battery management system is determined. When the system load is greater than or equal to the corresponding load threshold, the operating frequency of the operating system in the battery management system is gradually increased in a preset step size within a first time period until the operating frequency reaches the target operating frequency. That is, in this embodiment, when the system load is too heavy, increasing the operating frequency of the operating system can improve the processing speed of tasks, thereby enabling tasks to be executed as quickly as possible and improving the system's response speed. Moreover, by gradually increasing the operating frequency of the operating system in a preset step size, the system's stability and reliability are ensured while improving the response speed, thus improving the system's performance.

[0009] In some embodiments, the preset step size includes at least two, the first time period includes at least two sub-time periods, and each preset step size changes sequentially with the sub-time periods.

[0010] During the first time period, the operating frequency of the operating system in the battery management system is gradually increased according to a preset step size until the operating frequency reaches the target operating frequency, including:

[0011] In each sub-time period, the operating frequency of the operating system is increased by a corresponding preset step size until the operating frequency reaches the target operating frequency.

[0012] Therefore, by gradually increasing the operating frequency of the operating system according to a progressive step size, the operating frequency can be increased steadily and rapidly, reducing the impact of a sudden increase in operating frequency on battery management tasks. While ensuring system stability, this further improves the processing speed of battery management tasks.

[0013] In some embodiments, each preset step size changes sequentially with the sub-time period, including: the preset step size corresponding to each sub-time period increases or decreases sequentially according to the time order.

[0014] Therefore, the preset step size can be applied to each sub-time period in different ways to adjust the operating frequency of the operating system and improve the flexibility of the adjustment method.

[0015] In some embodiments, the resource management method of the battery management system further includes:

[0016] When the system load is greater than or equal to the corresponding load threshold, the frequency change of the operating frequency is determined according to the load level of the system load, and the frequency change is positively correlated with the load level.

[0017] Adjust the operating frequency of the operating system according to the frequency change.

[0018] Therefore, the frequency change of the operating frequency is dynamically determined according to the load level of the system load, and then the operating frequency of the operating system is adjusted according to the frequency change. This improves the system's response to battery management tasks and enhances the flexibility of resource management, making it applicable to more scenarios.

[0019] In some embodiments, the resource management method of the battery management system further includes:

[0020] When the system load is less than the corresponding load threshold, determine the load change trend of the system load in the second time period;

[0021] Adjust the operating frequency of the operating system according to the load change trend.

[0022] In this embodiment, when the system load is low, the operating frequency of the operating system is dynamically adjusted according to the changing trend of the system load over a period of time. This makes the adjustment results more accurate and avoids the impact of frequent adjustments on the system stability, thereby improving system performance and ensuring the normal execution of tasks.

[0023] In some embodiments, the resource management method of the battery management system further includes:

[0024] When the system load is greater than or equal to the corresponding load threshold, the task priority of the battery management task is adjusted according to the task parameters of the battery management task in the battery management system.

[0025] The task parameters include at least one of the following: task type and execution cycle.

[0026] Therefore, by dynamically adjusting the priority of battery management tasks based on their task type and execution cycle, high-priority tasks can be executed first, ensuring the timeliness of high-priority task responses and guaranteeing system performance.

[0027] In some embodiments, task parameters include the running cycle;

[0028] Adjust the task priority of the battery management task according to the task parameters in the battery management system, including:

[0029] If the running cycle is less than the cycle threshold, the task priority of the battery management task will be adjusted from the first priority to the second priority, with the second priority being higher than the first priority.

[0030] If the running cycle is greater than or equal to the cycle threshold, the priority of the battery management task will be adjusted from the first priority to the third priority, which is lower than the first priority.

[0031] Therefore, when the battery management task is a periodic task, dynamically adjusting its task priority according to the task's operating cycle can ensure that tasks with shorter cycles are executed in a timely manner, thus guaranteeing system safety.

[0032] In some embodiments, the resource management method of the battery management system further includes:

[0033] When the system load is less than the corresponding load threshold, the target battery management task is determined from each battery management task according to the initial task priority of each battery management task in the battery management system. The initial task priority of the target battery management task is less than the priority threshold.

[0034] The priority offset of the initial task priority is determined based on the level deviation between the initial task priority and the priority of adjacent tasks. The priority offset is greater than the level deviation.

[0035] Based on the priority offset and the initial task priority, the target task priority of the target battery management task is determined, and the target task priority is higher than the initial task priority.

[0036] In this embodiment, when the system load is low, the priority offset is determined based on the initial priority of the task and the level deviation between adjacent priorities. Then, the priority of the task is adjusted according to the priority offset, which appropriately balances the priority of some low-priority tasks, so that they also have a chance to be executed as soon as possible, thereby improving the overall performance of the system.

[0037] In some embodiments, determining the system load of the battery management system based on operating status and battery status data includes:

[0038] Based on the operating status and battery status data, as well as the system load determination model, the system load of the battery management system is determined.

[0039] The system load determination model is trained by taking the actual operating state of the sample battery and the actual battery state data of the sample battery under the actual operating state as input and the actual system load of the battery management system as output.

[0040] This embodiment can pre-train a system load determination model, which can then be used directly. This improves the efficiency of system load determination, enabling faster management of BMS resources and ensuring timely system response.

[0041] In some embodiments, the resource management method of the battery management system further includes:

[0042] Acquire the actual operating status of the sample battery and the actual battery status data of the sample battery under the actual operating status, as well as the actual system load of the battery management system under the actual operating status;

[0043] Based on the actual operating conditions, actual battery data, and actual system load, a relationship fitting is performed to obtain a system load determination model.

[0044] Therefore, through model training, the system load determination model can better adapt to changes in system load and battery operating status, capture these changes, and thus more accurately predict the system load of the BMS, schedule task priorities and operating frequency in advance, and ensure system stability, reliability and timely response.

[0045] Secondly, embodiments of this application provide a battery management system, including:

[0046] The sampling circuit is used to acquire the operating status of the battery corresponding to the battery management system and the battery status data when the battery is in operation.

[0047] The controller is used to determine the system load of the battery management system based on the operating status and battery status data. When the system load is greater than or equal to the corresponding load threshold, the operating frequency of the operating system in the battery management system is gradually increased in a preset step size within the first time period until the operating frequency reaches the target operating frequency.

[0048] In this embodiment, the operating status of the battery corresponding to the battery management system and the battery status data under that operating status are acquired. Based on the operating status and battery status data, the system load of the battery management system is determined. When the system load is greater than or equal to the corresponding load threshold, the operating frequency of the operating system in the battery management system is gradually increased in a preset step size within a first time period until the operating frequency reaches the target operating frequency. That is, in this embodiment, when the system load is too heavy, increasing the operating frequency of the operating system can improve the processing speed of tasks, thereby enabling tasks to be executed as quickly as possible and improving the system's response speed. Moreover, by gradually increasing the operating frequency of the operating system in a preset step size, the system's stability and reliability are ensured while improving the response speed, thus improving the system's performance.

[0049] Thirdly, embodiments of this application provide a battery device, including a battery and a battery management system as described in the second aspect.

[0050] Fourthly, embodiments of this application provide an electrical device including the battery device as described in the third aspect.

[0051] Fifthly, this application provides an electronic device comprising: a processor and a memory storing computer program instructions; wherein the processor, when executing the computer program instructions, implements a resource management method of a battery management system as shown in any embodiment of the first aspect.

[0052] In a sixth aspect, this application provides a computer storage medium storing computer program instructions, which, when executed by a processor, implement the resource management method of the battery management system shown in any embodiment of the first aspect.

[0053] In a seventh aspect, embodiments of this application provide a computer program product in which instructions, when executed by a processor of an electronic device, cause the electronic device to perform the resource management method of the battery management system shown in any embodiment of the first aspect.

[0054] 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

[0055] 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:

[0056] Figure 1 One of the flowcharts illustrating a resource management method for a battery management system provided in some embodiments of this application;

[0057] Figure 2 A second schematic flowchart illustrating a resource management method for a battery management system provided in some embodiments of this application;

[0058] Figure 3 This is a third flowchart illustrating a resource management method for a battery management system provided in some embodiments of this application.

[0059] Figure 4 A fourth schematic flowchart illustrating a resource management method for a battery management system provided in some embodiments of this application;

[0060] Figure 5 Fifth of a flowchart illustrating a resource management method for a battery management system provided in some embodiments of this application;

[0061] Figure 6 This application provides a schematic diagram of the structure of a battery management system according to some embodiments;

[0062] Figure 7 This is a schematic diagram of the structure of an electronic device provided in some embodiments of this application. Detailed Implementation

[0063] 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.

[0064] 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.

[0065] 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.

[0066] 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.

[0067] In the description of the embodiments in this application, the term "and / or" is merely a description of the association 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. The term "multiple" refers to two or more (including two). In addition, the character " / " in this document generally indicates that the preceding and following related objects have an "or" relationship.

[0068] The BMS in this application is used to perform at least one of the following functions for battery cells: state monitoring, state analysis, charge / discharge control, safety protection, information management, thermal management, and high-voltage power distribution. In addition, the BMS in this application can also perform the functions of a controller in an electrical device, such as a vehicle control unit (VCU) or a motor control unit (MCU), etc., and this application does not impose any limitations on this.

[0069] It should be noted that the BMS in this application can be integrated as a controller into the battery device, such as into the battery pack or energy storage box.

[0070] The BMS in this application can also be integrated as a controller into electrical devices, such as in a vehicle or vehicle chassis.

[0071] The BMS in this application can also be integrated into the charging device as a controller, such as into the charging device or the battery swapping device.

[0072] The BMS in this application can also be deployed as control software on a server. The server can be a standalone physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDN (Content Delivery Network), and big data and artificial intelligence platforms, such as vehicle networking cloud, APP backend, etc.

[0073] In a Battery Management System (BMS), if the system load is too heavy, the operating system within the BMS needs to spend more time processing various battery management tasks, resulting in lower task execution efficiency and potentially affecting the execution of some critical tasks. For example, in a vehicle's safety-critical systems, if the response time of a braking-related task is delayed, it may lead to an untimely response from the braking system, increasing the risk of a vehicle accident.

[0074] To address the aforementioned technical problems, this application provides a resource management method for a battery management system, which can improve the processing speed of battery management tasks, thereby shortening the execution time of battery management tasks, enabling other battery management tasks to be executed in a timely manner, and thus improving the performance of the BMS system.

[0075] The resource management method of the battery management system provided in this application will be described in detail below with reference to the accompanying drawings and specific embodiments.

[0076] Figure 1 This illustration shows a flowchart of a resource management method for a battery management system according to an embodiment of this application. It should be noted that this resource management method can be applied to an operating system that conforms to the Automotive Open System Architecture (AUTOSAR) standard. This operating system can be integrated into the BMS, which can be applied to electric vehicles such as pure electric vehicles or plug-in hybrid electric vehicles, or it can be used as a standalone device or apparatus.

[0077] like Figure 1 As shown, the resource management method of the battery management system may include the following steps S110-S130.

[0078] S110. Obtain the operating status of the battery corresponding to the battery management system and the battery status data when the battery is in operation.

[0079] S120. Determine the system load of the battery management system based on the operating status and battery status data.

[0080] S130. When the system load is greater than or equal to the corresponding load threshold, the operating frequency of the operating system in the battery management system is gradually increased according to the preset step size within the first time period until the operating frequency reaches the target operating frequency.

[0081] Therefore, when the system is under heavy load, increasing the operating frequency of the operating system can improve task processing speed, thereby enabling tasks to be executed as quickly as possible and improving system response speed. Moreover, when increasing the operating frequency of the operating system, it is done gradually in preset steps, which improves response speed while ensuring system stability and reliability, thus enhancing system performance.

[0082] The above steps are explained in detail below:

[0083] In S110, the battery can be a single battery cell in the battery energy storage system, or it can be a battery pack containing multiple battery cells in the battery energy storage system. This embodiment does not limit the type of battery; for example, it can include lithium-ion batteries, lead-acid batteries, etc. The aforementioned battery management system is responsible for monitoring and managing the battery energy storage system.

[0084] A battery's operating state can include, for example, charging state, discharging state, and idle state. When a battery is charging, it is in the charging state; when a battery is discharging, it is in the discharging state; when a battery is not connected to a charger or load, it can be considered to be in the idle state, in which the battery voltage will remain relatively stable for a period of time.

[0085] Battery state data can be data characterizing the battery's state, such as, but not limited to, battery voltage, temperature, current, state of charge, and state of health. The system load on the BMS can be assessed based on battery state data under a certain operating condition.

[0086] For example, the operating state of a battery can be determined based on data such as battery voltage, current, and temperature. For instance, when the battery voltage is rising, it can be considered that the battery is in a charging state, and when the battery voltage is falling, it can be considered that the battery is in a discharging state.

[0087] Battery status data can be obtained through sensors. For example, the temperature of a battery cell can be obtained through a temperature sensor, the voltage of a battery cell can be obtained through a voltage sensor, and the current of a battery cell can be obtained through a current sensor.

[0088] It should be understood that sensor accuracy and sampling frequency both affect the load on the BMS system. For example, higher sensor accuracy generates more detailed and accurate data, but this may also mean more data needs to be processed, thus increasing the load on the BMS system. The sampling frequency determines the density of data acquisition; higher frequency sampling generates more data points, requiring more computing resources to process and analyze this data, also increasing the load on the BMS system. Therefore, in some embodiments, the impact of sensor accuracy and sampling frequency on system load can be further considered.

[0089] Furthermore, different types of batteries have different charge / discharge characteristics and data variation patterns, which also affect the load on the BMS system. Therefore, in some embodiments, the battery type can be further considered. This allows for more accurate prediction of the BMS system load and more precise optimization of its performance.

[0090] In S120, the system load here can be the load generated by the BMS system itself, such as the computing, communication, and other loads required for the BMS system to operate. For example, the system load can be characterized by the utilization rate of the Central Processing Unit (CPU) and memory usage.

[0091] In some embodiments, the computational, communication, and other loads required for the operation of the BMS system can be estimated based on the battery's operating status and data such as battery voltage, current, and temperature, providing a basis for subsequent optimization of the BMS system's performance. In some embodiments, the load generated by the operation of the BMS system itself can also be approximated as the sum of the task loads of each battery management task in the BMS system.

[0092] This embodiment does not limit the method for determining the system load. For example, the system load of the BMS can be determined by using a machine learning model or a deep learning model, combined with the battery's operating state and battery state data. This machine learning model or deep learning model can be trained with the actual operating state of the battery and actual battery state data as input, and the actual system load of the BMS as output.

[0093] For example, the system load corresponding to the battery under different operating states and battery state data can be pre-established to obtain a correlation table. Subsequently, the system load corresponding to the current operating state and battery state data can be obtained by looking up the table.

[0094] In S130, the load threshold is used to determine whether the BMS system load is too heavy. For example, the load threshold can be set based on experience, requirements, etc.

[0095] For example, the load threshold can also be dynamically set according to the battery's operating state. For instance, an initial load threshold can be set based on experience and requirements, and then further adjusted according to the battery's operating state. For example, when the battery is charging, the load threshold can be appropriately reduced to ensure timely detection of abnormalities during the charging process. Different BMSs can correspond to different load thresholds.

[0096] For example, when the system load is greater than or equal to the corresponding load threshold, the system load can be considered too heavy, and the resources of the BMS need to be managed to improve the timeliness of the operating system's response to battery management tasks.

[0097] Taking the use of CPU utilization to characterize system load as an example, in some embodiments, the load threshold can be set to 70%. That is, when the CPU utilization is greater than or equal to 70%, the BMS can be considered to be in a high-load state, that is, the BMS system load is too heavy.

[0098] The first time period can be any period starting from when the system load is greater than or equal to the load threshold. For example, if the BMS system load is detected to be greater than the load threshold at 9:00 AM on March 3, 2025, then the first time period can be any period starting from 9:00 AM on March 3. This embodiment does not limit the length of the first time period. For example, to ensure that battery management tasks are executed as promptly as possible and to reduce the impact of delays on battery management tasks, the first time period can be set to be relatively short.

[0099] The preset step size is the adjustment step size of the operating system's operating frequency. That is, in this embodiment, when the system load is too heavy, the operating frequency of the operating system can be increased according to a certain step size, so as to improve the processing speed of the battery management task and thus improve the timeliness of the operating system's response to the battery management task.

[0100] The preset step size here can be fixed, meaning the operating frequency of the operating system can be gradually increased according to a fixed step size. Alternatively, it can be dynamically changed, meaning the operating frequency of the operating system can be gradually increased according to a dynamic step size, thus improving the flexibility and versatility of resource management methods.

[0101] For example, the step size can be set according to experience, requirements, etc. For instance, when the step size is fixed, the fixed step size can be set to 100MHz according to experience, requirements, etc., that is, the operating frequency of the operating system is increased by 100MHz each time.

[0102] For example, the step size can also be dynamically determined by the size of the system load or the rate of increase of the system load. For example, the larger the system load, the larger the step size; or the larger the rate of increase of the system load, the larger the step size.

[0103] The target operating frequency is the maximum operating frequency that the operating system can achieve when the system load is too heavy. The specific value of the target operating frequency is related to the performance of the operating system.

[0104] For example, when a high system load is detected in the BMS, the operating frequency of the operating system can be gradually increased until the target operating frequency is reached. This can prevent the battery management task from malfunctioning due to a sudden change in the operating frequency of the operating system, thus ensuring the stability and reliability of the system.

[0105] For example, the operating frequency of the operating system can be gradually increased by setting a step size based on the difference between the current operating frequency and the target operating frequency, as well as the number of adjustments.

[0106] This can improve the processing speed of battery management tasks, thereby improving the timeliness of the operating system's response to battery management tasks.

[0107] In order to ensure system stability and reliability, during the process of increasing the operating frequency of the operating system, Figure 2 A flowchart of a resource management method for a battery management system is provided as an example. Figure 2 Taking a preset step size comprising at least two sub-time periods as an example, where the first time period comprises at least two sub-time periods, and each preset step size changes sequentially with the sub-time periods. Here, "changing sequentially" means that the step size can be different each time it is adjusted; for example, the step size can increase or decrease sequentially. That is, the preset step size corresponding to each sub-time period increases or decreases sequentially according to the time sequence. Therefore, the preset step size can be applied to each sub-time period in different ways to adjust the operating frequency of the operating system, improving the flexibility of the adjustment method.

[0108] In practical applications, each sub-time period can correspond to a preset step size. The number of sub-time periods and the number of preset step sizes can be the same or different, as long as the preset step size changes according to the time periods.

[0109] For example, when the number of sub-time periods is the same as the number of preset steps, each sub-time period can correspond one-to-one with each preset step in chronological order. Taking a sub-time period with 3 sub-time periods and 3 preset steps as an example, assuming the sub-time periods are t1, t2, and t3 in chronological order, and the 3 preset steps are m1, m2, and m3 in ascending order. When the preset steps increase sequentially in chronological order, the preset step corresponding to sub-time period t1 is m1, the preset step corresponding to sub-time period t2 is m2, and the preset step corresponding to sub-time period t3 is m3. When the preset steps decrease sequentially in chronological order, the preset step corresponding to sub-time period t1 is m3, the preset step corresponding to sub-time period t2 is m2, and the preset step corresponding to sub-time period t3 is m1.

[0110] For example, when the number of sub-time periods is greater than the number of preset step sizes, the preset step sizes corresponding to some adjacent sub-time periods can be the same, and the preset step sizes of each sub-time period still exhibit an overall increasing trend. For instance, there are four sub-time periods, t1-t4, and three preset step sizes, m1-m3. Assuming the preset step sizes increase sequentially, in some embodiments, the preset step size corresponding to sub-time period t1 can be m1, the preset step size corresponding to sub-time period t2 can be m2, the preset step size corresponding to sub-time period t3 can be m2, and the preset step size corresponding to sub-time period t4 can be m3. In other embodiments, the preset step size corresponding to sub-time period t1 can be m1, the preset step size corresponding to sub-time period t2 can be m2, the preset step size corresponding to sub-time period t3 can be m3, and the preset step size corresponding to sub-time period t4 can be m3. Other cases are also possible. In this way, the preset step sizes still exhibit an overall increasing trend.

[0111] For example, when the number of sub-time periods is less than the number of preset step sizes, the same sub-time period can correspond to multiple preset step sizes, and the preset step sizes of each sub-time period still satisfy the characteristic of incremental change. For example, there are 3 sub-time periods, t1-t3, and 4 preset step sizes, m1-m4. Assuming that the preset step sizes increase in chronological order, in some embodiments, the preset step size corresponding to sub-time period t1 can be m1, the preset step size corresponding to sub-time period t2 can be m2, the preset step size corresponding to the first segment of sub-time period t3 can be m3, and the preset step size corresponding to the second segment can be m4. This embodiment does not limit the specific division method of sub-time period t3. In this way, the overall preset step size still shows an incremental trend.

[0112] Taking a sequential increase as an example, the step size gradually increases as the operating frequency increases. Therefore, while ensuring system stability, the processing speed of battery management tasks can be further improved, which in turn can further enhance the timeliness of the operating system's response to battery management tasks.

[0113] Figure 2 Taking a system load greater than or equal to the corresponding load threshold as an example, Figure 2 and Figure 1 The difference is that, Figure 1 S130 in the middle can be further refined into Figure 2 S210 in the middle.

[0114] S210. Increase the operating frequency of the operating system by a corresponding preset step size in each sub-time period until the operating frequency reaches the target operating frequency. For example, when specifically increasing the operating frequency in each sub-time period, the operating frequency can be increased at the beginning of each sub-time period by the corresponding step size, or it can be increased at a certain point between the beginning and end of each sub-time period. To balance system stability and battery management task processing speed, the operating frequency can be increased by the corresponding step size as close as possible to the beginning point.

[0115] Therefore, by gradually increasing the operating frequency of the operating system according to a progressive step size, the operating frequency can be increased steadily and rapidly, reducing the impact of a sudden increase in operating frequency on battery management tasks. While ensuring system stability, this further improves the processing speed of battery management tasks.

[0116] In some embodiments, to improve the flexibility of resource management, the resource management method may further include the following steps:

[0117] When the system load is greater than or equal to the corresponding load threshold, the frequency change of the operating frequency is determined according to the load level of the system load, and the frequency change is positively correlated with the load level.

[0118] Adjust the operating frequency of the operating system according to the frequency change.

[0119] The load level here can characterize the size of the system load; that is, the higher the load level, the higher the system load.

[0120] For example, a mapping relationship between system load size and load level can be established in advance. Subsequently, based on this mapping relationship and the actual size of the system load, its load level can be determined. For example, each load level can correspond to a load range. Based on the actual size of the system load, the load range to which it belongs can be determined, thereby obtaining the corresponding load level.

[0121] The frequency variation of the operating frequency can be dynamically determined based on the system load level. In this embodiment, the load level and the frequency variation can be positively correlated; that is, the higher the load level, the greater the corresponding frequency variation, thereby improving the processing speed of battery management tasks as quickly as possible.

[0122] For example, when CPU utilization exceeds 70%, the load level is relatively low, and a small frequency change can be determined, such as a frequency change of 100MHz. When CPU utilization exceeds 90%, the load level is high, and a larger frequency change can be determined, such as a frequency change of 200MHz. In practical applications, the correspondence between load level and frequency change can be flexibly adjusted according to requirements.

[0123] For example, when the CPU utilization exceeds 70%, the frequency can be increased by 100MHz from the current operating frequency, and when the CPU utilization exceeds 90%, the frequency can be increased by 200MHz from the current operating frequency.

[0124] Therefore, the frequency change of the operating frequency is dynamically determined according to the system load, and the operating frequency of the operating system is adjusted according to the frequency change. This improves the system's responsiveness to battery management tasks and enhances the flexibility of resource management, making it applicable to more scenarios.

[0125] In some embodiments, to accommodate different system loads... Figure 3 An exemplary flowchart of a resource management method is provided. Figure 3 and Figure 1 The difference is that, Figure 3 It also includes S310-S330.

[0126] S310. Determine if the system load is greater than the corresponding load threshold. If yes, execute S130; otherwise, execute S320.

[0127] In this embodiment, the operating frequency of the operating system is adjusted differently depending on the size of the system load, thereby improving the flexibility of the operating frequency adjustment strategy.

[0128] S320. When the system load is less than the corresponding load threshold, determine the load change trend of the system load in the second time period.

[0129] The second time period can be a period of time starting from when the system load is less than the corresponding load threshold, and the duration of the second time period can be set according to requirements. That is, in this embodiment, when the system load is low, the operating frequency of the operating system is not adjusted immediately, but is observed for a period of time to determine the trend of system load change, and then the operating frequency of the operating system is adjusted according to the trend. This can avoid the impact of frequent adjustment of the operating frequency on the stability of the system.

[0130] Load change trend is used to characterize the changes in system load over a second time period, and may include, for example, an upward trend or a downward trend. An upward trend indicates that the system load gradually increases over time, while a downward trend indicates that the system load gradually decreases over time.

[0131] For example, during the second time period, the system load of the BMS can be obtained at certain time intervals, and then a time series diagram of the system load changing over time can be drawn. Based on this time series diagram, the trend of system load change can be determined more intuitively.

[0132] For example, the system load of the BMS can be obtained at certain time intervals, and then the rate of change of the system load can be determined based on the system load at two adjacent time points. Based on the rate of change, the trend of system load change can be clarified, and the speed of system load change can be further determined, so as to adjust the operating frequency of the operating system more accurately.

[0133] S330: Adjust the operating frequency of the operating system according to the load change trend.

[0134] For example, if the load trend is upward, the operating frequency of the operating system can be increased to reduce the impact of system load on system response and improve system performance. If the load trend is downward, the current operating frequency of the operating system can be kept unchanged, or the operating frequency of the operating system can be appropriately reduced to reduce system power consumption.

[0135] In this embodiment, when the system load is low, the operating frequency of the operating system is dynamically adjusted according to the changing trend of the system load over a period of time. This makes the adjustment results more accurate and avoids the impact of frequent adjustments on the system stability, thereby improving system performance and ensuring the normal execution of tasks.

[0136] In some embodiments, when the system load is high, certain tasks may be executed in a timely manner. Figure 4 A flowchart of a resource management method for a battery management system is also provided. Figure 4 and Figure 1 The difference is that, Figure 4 It also includes S410. In practical applications, this embodiment does not limit the execution order of S130 and S410. For example, S130 can be executed first and then S410 can be executed; S410 can be executed first and then S130 can be executed; or S130 and S410 can be executed simultaneously.

[0137] S410. When the system load is greater than or equal to the corresponding load threshold, adjust the task priority of the battery management task according to the task parameters of the battery management task in the battery management system.

[0138] The task parameters here are used to characterize the task characteristics of the battery management task. For example, in some embodiments, the task parameters may include at least one of the following: task type, running cycle, etc. In some embodiments, the task parameters may also include task load, etc.

[0139] Task types may include, but are not limited to, important tasks, urgent tasks, and periodic tasks.

[0140] Important tasks are those that are crucial to system safety and performance, but do not necessarily need to be completed immediately. For example, tasks that have a significant impact on battery safety and performance, such as battery status monitoring and battery overcharge and overvoltage protection, are considered important tasks; while tasks that have a smaller impact on battery safety and performance, such as data logging and data storage, are considered unimportant tasks.

[0141] For example, when the system load is high, the priority of important tasks can be increased to ensure that these important tasks can be executed in a timely manner, thus guaranteeing system stability and performance. Conversely, the priority of non-critical tasks, such as background tasks and data logging tasks, can be decreased to reduce their consumption of system resources.

[0142] Emergency tasks are typically sporadic, prone to serious consequences, and time-sensitive, requiring immediate response once they occur. Examples include fault diagnosis tasks detecting BMS anomalies and battery overcharge protection tasks detecting battery voltage exceeding a threshold.

[0143] For example, when the system load is high, the priority of urgent tasks can be increased and the priority of non-urgent tasks can be decreased to ensure that these tasks can be executed as soon as possible and reduce the impact on the BMS. In some embodiments, when an urgent task requires an immediate response, the priority of the urgent task can be increased to the highest priority, or preemptive scheduling can be performed, that is, the urgent task is allowed to interrupt the currently executing task and execute the urgent task first.

[0144] For some routine data processing tasks, a medium priority can be assigned based on their overall impact on the system and time requirements.

[0145] When a battery management task is a periodic task, its runtime also affects its priority. Generally, the shorter the runtime, the higher the priority. For example, the specific priority of a battery management task can be determined by combining its runtime and execution duration using the RateMonotonic Scheduling (RMS) algorithm.

[0146] In some embodiments, the task priority of battery management tasks can be adjusted in combination with the running cycle and task type, which can make the priority allocation more reasonable and thus improve the overall performance of the system.

[0147] Therefore, by dynamically adjusting the priority of battery management tasks based on their task type and execution cycle, high-priority tasks can be executed first, ensuring the timeliness of high-priority task responses and guaranteeing system performance.

[0148] Taking a task parameter that includes the running cycle as an example, S410 above may include the following steps:

[0149] If the running cycle is less than the cycle threshold, the task priority of the battery management task will be adjusted from the first priority to the second priority, with the second priority being higher than the first priority.

[0150] If the running cycle is greater than or equal to the cycle threshold, the priority of the battery management task will be adjusted from the first priority to the third priority, which is lower than the first priority.

[0151] Generally, the more important a task is, the shorter its execution cycle, allowing for timely detection of system anomalies and ensuring system security. For example, the adjustment range for task priority can be determined based on the difference between the execution cycle and a cycle threshold, thereby increasing or decreasing the priority of battery management tasks accordingly. The cycle threshold can be flexibly set as needed. The adjustment range here refers to the priority difference between the first and second priorities, or the priority difference between the first and third priorities mentioned above.

[0152] Therefore, when the battery management task is a periodic task, dynamically adjusting its task priority according to the task's operating cycle can ensure that tasks with shorter cycles are executed in a timely manner, thus guaranteeing system safety.

[0153] In some embodiments, to allow low-priority tasks to have a chance to execute when the system load is low. Figure 5 A flowchart is provided for a resource management method in a battery management system. Figure 5 and Figure 1 The difference is that, Figure 5 It also includes S510-S540.

[0154] S510. Determine if the system load is greater than the corresponding load threshold. If yes, execute S130; otherwise, execute S520.

[0155] In this embodiment, different resource management strategies are adopted depending on the size of the system load, thereby improving the flexibility of resource adjustment strategies.

[0156] S520. When the system load is less than the corresponding load threshold, determine the target battery management task from each battery management task according to the initial task priority of each battery management task in the battery management system.

[0157] The initial task priority can be the priority set for each battery management task during system initialization, or the priority possessed by each battery management task before executing the scheme of this embodiment. In this embodiment, the target battery management task is a task with a low task priority, that is, the initial task priority of the target battery management task is less than the priority threshold. The priority threshold can be set according to requirements. For example, there are 16 levels of task priority, corresponding to numbers 1-16, with higher numbers representing higher priorities. In some embodiments, the priority threshold can be set to 6. That is, the target battery management task can be a task with a priority less than 6, that is, a task with a priority of 1-5.

[0158] S530. Determine the priority offset of the initial task priority based on the level deviation between the initial task priority and the priority of adjacent tasks.

[0159] Taking an initial task priority of 1 as an example, with an adjacent task priority of 2, the adjacent task priorities can be 1 or 3. The level deviation is the absolute value of the difference between the initial task priority and the adjacent task priority. Still taking an initial task priority of 1 as an example, the level deviation between this initial task priority and the adjacent task priority of 2 is 1.

[0160] Priority offsets are used to adjust the task priority of a target battery management task, giving it a chance to preempt resources and execute. For example, the priority offset can be determined based on the level deviation, and then the task priority of the target battery management task can be adjusted accordingly.

[0161] For example, the priority offset is greater than the level deviation, so that the priority of the target battery management task can be adjusted to be higher than the priority of the adjacent task, thereby preempting resources for the target battery management task and enabling the target battery management task to be executed.

[0162] For example, if the priority deviation is 3, the priority offset can be set to a value greater than 3, such as 5. Assuming the initial priority of the target battery management task is 10 and the priority offset is 5, then when the system load is low, the priority of the target battery management task will be adjusted to 15.

[0163] S540. Determine the target task priority of the target battery management task based on the priority offset and the initial task priority.

[0164] For example, the initial task priority and the priority offset can be summed to obtain the target task priority of the target battery management task, where the target task priority is higher than the initial task priority. This increases the task priority of low-priority tasks.

[0165] In this embodiment, when the system load is low, the priority offset is determined based on the initial priority of the task and the level deviation between adjacent priorities. Then, the priority of the task is adjusted according to the priority offset, which appropriately balances the priority of some low-priority tasks, so that they also have a chance to be executed as soon as possible, thereby improving the overall performance of the system.

[0166] In some embodiments, to determine the system load, S120 may include the following steps:

[0167] Based on the operating status and battery status data, as well as the system load determination model, the system load of the battery management system is determined.

[0168] The system load determination model is trained by taking the actual operating state of the sample battery and the actual battery state data of the sample battery under the actual operating state as input and the actual system load of the battery management system as output.

[0169] The system load determination model here can employ machine learning or deep learning models, such as time series analysis models like the Autoregressive Integrated Moving Average (ARIMA) or Long Short-Term Memory (LSTM) networks. Alternatively, mathematical models, such as linear or nonlinear functions, can be used.

[0170] Taking a machine learning model or deep learning model as an example, exemplarily, actual battery state data of the sample battery under various actual operating conditions can be collected, as well as the task load of each battery management task in the BMS under each actual operating condition. Based on the task load, the actual system load of the BMS can be obtained; for example, the sum of the task loads can be used as the actual system load of the BMS. The model of the sample battery here is the same as the battery model in the above embodiment, thereby improving the training effect of the model.

[0171] For example, the actual battery state data and corresponding actual operating states of the sample batteries under various real-world operating conditions can be input into the system load determination model to obtain the predicted system load output by the system load model. Then, combined with a loss function, the loss function value between the predicted system load and the actual system load is calculated. The parameters of the system load determination model are then updated based on the loss function value until a convergence condition is met, resulting in the trained system load determination model. The convergence condition could be, for example, reaching a preset number of iterations or the loss function value converging.

[0172] For example, for each sampling time, the actual battery state data and actual operating state corresponding to that sampling time can be vectorized to obtain vectors corresponding to the actual battery state data and actual operating state. The vectors are then concatenated, and the concatenated vectors can be combined according to the sampling time to obtain a matrix. This matrix is ​​then input into the system load determination model for training.

[0173] Taking a mathematical model as an example, for each operating state, a fitting function can be obtained by fitting the relationship between the battery state data and the system load corresponding to that operating state. Subsequently, based on the battery's operating state, a suitable fitting function is selected, and the corresponding battery state data is substituted into the fitting function to obtain the corresponding system load.

[0174] After model training is complete, the trained model can be further tested using a test dataset to ensure it can accurately predict system load on unseen data. The process of determining the test dataset is similar to that of determining the training dataset. The model can then be continuously optimized using actual data from the BMS.

[0175] This embodiment can pre-train a system load determination model, which can be used directly in subsequent applications. This can improve the efficiency of system load determination, thereby enabling faster management of BMS resources and ensuring timely system response.

[0176] In some embodiments, to save system overhead and improve the prediction efficiency of system load, the system load determination model can be obtained in the following manner:

[0177] Acquire the actual operating status of the sample battery and the actual battery status data of the sample battery under the actual operating status, as well as the actual system load of the battery management system under the actual operating status;

[0178] Based on the actual operating conditions, actual battery data, and actual system load, a relationship fitting is performed to obtain a system load determination model.

[0179] Therefore, through model training, the system load determination model can better adapt to changes in system load and battery operating status, capture these changes, and thus more accurately predict the system load of the BMS, schedule task priorities and CPU operating frequencies in advance, and ensure system stability, reliability and timely response.

[0180] Based on the same inventive concept, this application also provides a battery management system. The following, in conjunction with... Figure 6 The battery management system provided in the embodiments of this application will be described in detail.

[0181] Figure 6 A schematic diagram of a battery management system provided in one embodiment of this application is shown.

[0182] like Figure 6 As shown, the battery management system may include:

[0183] The sampling circuit 601 is used to acquire the operating status of the battery in the battery management system and the battery status data when the battery is in operation.

[0184] The controller 602 is used to determine the system load of the battery management system based on the operating status and battery status data; when the system load is greater than or equal to the corresponding load threshold, the operating frequency of the operating system in the battery management system is gradually increased in a preset step size within a first time period until the operating frequency reaches the target operating frequency.

[0185] In this embodiment, when the system load is too heavy, increasing the CPU's operating frequency can improve task processing speed, thereby enabling tasks to be executed as quickly as possible and improving system response speed. Furthermore, by gradually increasing the CPU operating frequency according to preset steps, system stability and reliability are maintained while improving response speed, thus enhancing system performance.

[0186] In some embodiments, the preset step size includes at least two, the first time period includes at least two sub-time periods, and each preset step size changes sequentially with the sub-time periods.

[0187] Controller 602 is specifically used for:

[0188] In each sub-time period, the operating frequency of the operating system is increased by a corresponding preset step size until the operating frequency reaches the target operating frequency.

[0189] In some embodiments, each preset step size changes sequentially with the sub-time period, including: the preset step size corresponding to each sub-time period increases or decreases sequentially according to the time order.

[0190] In some embodiments, the controller 602 is further configured to determine the frequency change of the operating frequency according to the load level of the system load when the system load is greater than or equal to the corresponding load threshold, wherein the frequency change is positively correlated with the load level.

[0191] Adjust the operating frequency of the operating system according to the frequency change.

[0192] In some embodiments, the controller 602 is further configured to determine the load change trend of the system load in a second time period when the system load is less than the corresponding load threshold.

[0193] Adjust the operating frequency of the operating system according to the load change trend.

[0194] In some embodiments, the controller 602 is further configured to adjust the task priority of the battery management task according to the task parameters of the battery management task in the battery management system when the system load is greater than or equal to the corresponding load threshold.

[0195] The task parameters include at least one of the following: task type and execution cycle.

[0196] In some embodiments, the controller 602 is specifically used for:

[0197] If the running cycle is less than the cycle threshold, the task priority of the battery management task will be adjusted from the first priority to the second priority, with the second priority being higher than the first priority.

[0198] If the running cycle is greater than or equal to the cycle threshold, the priority of the battery management task will be adjusted from the first priority to the third priority, which is lower than the first priority.

[0199] In some embodiments, the controller 602 is further configured to determine a target battery management task from each battery management task according to the initial task priority of each battery management task in the battery management system when the system load is less than the corresponding load threshold, wherein the initial task priority of the target battery management task is less than the priority threshold.

[0200] The priority offset of the initial task priority is determined based on the level deviation between the initial task priority and the priority of adjacent tasks. The priority offset is greater than the level deviation.

[0201] Based on the priority offset and the initial task priority, the target task priority of the target battery management task is determined, and the target task priority is higher than the initial task priority.

[0202] In some embodiments, the controller 602 is specifically used for:

[0203] Based on the operating status and battery status data, as well as the system load determination model, the system load of the battery management system is determined.

[0204] The system load determination model is trained by taking the actual operating state of the sample battery and the actual battery state data of the sample battery under the actual operating state as input and the actual system load of the battery management system as output.

[0205] In some embodiments, the sampling circuit 601 is further configured to acquire the actual operating state of the sample battery and the actual battery state data of the sample battery in the actual operating state, as well as the actual system load of the battery management system in the actual operating state.

[0206] The controller 602 is also used to fit the relationship based on the actual operating status, actual battery status data and actual system load to obtain a system load determination model.

[0207] Figure 7 A schematic diagram of the structure of an electronic device provided in one embodiment of this application is shown.

[0208] like Figure 7 As shown, the electronic device 700 is capable of implementing the resource management method according to the embodiments of this application.

[0209] The electronic device 700 may include a processor 701 and a memory 702 storing computer program instructions.

[0210] Specifically, the processor 701 may include a central processing unit (CPU), an application-specific integrated circuit (ASIC), or one or more integrated circuits that can be configured to implement the embodiments of this application.

[0211] Memory 702 may include mass storage for data or instructions. For example, and not limitingly, memory 702 may include a hard disk drive (HDD), floppy disk drive, flash memory, optical disk, magneto-optical disk, magnetic tape, or Universal Serial Bus (USB) drive, or a combination of two or more of these. Where appropriate, memory 702 may include removable or non-removable (or fixed) media. Where appropriate, memory 702 may be internal or external to an integrated gateway disaster recovery device. In a particular embodiment, memory 702 is non-volatile solid-state memory. In a particular embodiment, memory 702 may include read-only memory (ROM), random access memory (RAM), disk storage media device, optical storage media device, flash memory device, electrical, optical, or other physical / tangible memory storage device. Thus, generally, memory 702 includes one or more tangible (non-transitory) computer-readable storage media (e.g., memory devices) encoded with software including computer-executable instructions, and when the software is executed (e.g., by one or more processors), it is operable to perform the operations described with reference to the method according to one aspect of this application.

[0212] The processor 701 implements any of the resource management methods described in the above embodiments by reading and executing computer program instructions stored in the memory 702.

[0213] In one example, the electronic device 700 may also include a communication interface 703 and a bus 704. Wherein, as... Figure 7 As shown, the processor 701, memory 702, and communication interface 703 are connected through bus 704 and complete communication with each other.

[0214] The communication interface 703 is mainly used to realize communication between various modules, devices, apparatuses and / or equipment in the embodiments of this application.

[0215] Bus 704 includes hardware, software, or both, that couples components of electronic device 700 together. For example, and not limitingly, the bus may include Accelerated Graphics Port (AGP) or other graphics buses, Enhanced Industry Standard Architecture (EISA) buses, Front Side Bus (FSB), HyperTransport (HT) interconnects, Industry Standard Architecture (ISA) buses, Infinite Bandwidth Interconnects, Low Pin Count (LPC) buses, memory buses, Microchannel Architecture (MCA) buses, Peripheral Component Interconnect (PCI) buses, PCI-Express (PCI-X) buses, Serial Advanced Technology Attachment (SATA) buses, Video Electronics Standards Association Local (VLB) buses, or other suitable buses, or combinations of two or more of these. Where appropriate, bus 704 may include one or more buses. Although specific buses are described and illustrated in embodiments of this application, any suitable bus or interconnect is contemplated herein.

[0216] The electronic device can execute the resource management method of the battery management system in the embodiments of this application, thereby achieving the combination Figures 1 to 5 The described resource management method of the battery management system and Figure 6 The battery management system is described.

[0217] Furthermore, in conjunction with the resource management method of the battery management system in the above embodiments, this application embodiment can provide a computer storage medium for implementation. The computer storage medium stores computer program instructions; when these computer program instructions are executed by a processor, they implement any of the resource management methods of the battery management system in the above embodiments.

[0218] This application also provides a chip, which includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is used to run programs or instructions to implement the various processes of the above method embodiments and achieve the same technical effect. To avoid repetition, it will not be described again here.

[0219] It should be understood that the chip mentioned in the embodiments of this application may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.

[0220] This application also provides a computer program product stored in a readable storage medium. When executed by at least one processor, the program product can implement the various processes of the above method embodiments and achieve the same technical effects. To avoid repetition, it will not be described again here.

[0221] This application also provides a battery device, including a battery and a battery management system as described in the above embodiments.

[0222] This application also provides an electrical device, including the battery device described in the above embodiments.

[0223] 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.

[0224] The functional blocks shown in the above-described structural 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, ROM, flash memory, erasable ROM (EROM), floppy disks, 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.

[0225] 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.

[0226] The aspects of this application have been described above with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It should be understood that each block in the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations 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 produce 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 flowchart illustrations 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.

[0227] 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 resource management method for a battery management system, characterized in that, include: Obtain the operating status of the battery corresponding to the battery management system and the battery status data of the battery in the operating status; The system load of the battery management system is determined based on the operating status and the battery status data. When the system load is greater than or equal to the corresponding load threshold, the operating frequency of the operating system in the battery management system is gradually increased in a preset step size within a first time period until the operating frequency reaches the target operating frequency.

2. The method according to claim 1, characterized in that, The preset step size includes at least two, and the first time period includes at least two sub-time periods, with each preset step size changing sequentially with the sub-time period. The step of gradually increasing the operating frequency of the operating system in the battery management system according to a preset step size within the first time period until the operating frequency reaches the target operating frequency includes: In each of the sub-time periods, the operating frequency of the operating system is increased by a corresponding preset step size until the operating frequency reaches the target operating frequency.

3. The method according to claim 2, characterized in that, Each preset step size changes sequentially with the sub-time period, including: the preset step size corresponding to each sub-time period increases or decreases sequentially according to the time order.

4. The method according to any one of claims 1-3, characterized in that, The method further includes: When the system load is greater than or equal to the corresponding load threshold, the frequency change of the operating frequency is determined according to the load level of the system load, and the frequency change is positively correlated with the load level; The operating frequency of the operating system is adjusted according to the frequency change.

5. The method according to any one of claims 1-4, characterized in that, The method further includes: When the system load is less than the corresponding load threshold, determine the load change trend of the system load in the second time period; The operating frequency of the operating system is adjusted according to the load change trend.

6. The method according to any one of claims 1-5, characterized in that, The method further includes: When the system load is greater than or equal to the corresponding load threshold, the task priority of the battery management task is adjusted according to the task parameters of the battery management task in the battery management system. The task parameters include at least one of the following: task type and running cycle.

7. The method according to claim 6, characterized in that, The task parameters include the running cycle; The step of adjusting the task priority of the battery management task according to the task parameters of the battery management task in the battery management system includes: If the running cycle is less than the cycle threshold, the task priority of the battery management task is adjusted from the first priority to the second priority, where the second priority is higher than the first priority. If the running cycle is greater than or equal to the cycle threshold, the task priority of the battery management task is adjusted from the first priority to the third priority, where the third priority is lower than the first priority.

8. The method according to any one of claims 1-7, characterized in that, The method further includes: When the system load is less than the corresponding load threshold, a target battery management task is determined from each battery management task according to the initial task priority of each battery management task in the battery management system, wherein the initial task priority of the target battery management task is less than the priority threshold. The priority offset of the initial task priority is determined based on the level deviation between the initial task priority and the priorities of adjacent tasks, and the priority offset is greater than the level deviation; The target task priority of the target battery management task is determined based on the priority offset and the initial task priority, wherein the target task priority is higher than the initial task priority.

9. The method according to any one of claims 1-8, characterized in that, The step of determining the system load of the battery management system based on the operating status and the battery status data includes: Based on the operating status and battery status data, as well as the system load determination model, the system load of the battery management system is determined. The system load determination model is trained by taking the actual operating state of the sample battery and the actual battery state data of the sample battery under the actual operating state as input, and taking the actual system load of the battery management system as output.

10. The method according to claim 9, characterized in that, The method further includes: The actual operating state of the sample battery and the actual battery state data of the sample battery under the actual operating state are obtained, as well as the actual system load of the battery management system under the actual operating state; Based on the actual operating state, the actual battery state data, and the actual system load, a relationship fitting is performed to obtain the system load determination model.

11. A battery management system, characterized in that, include: A sampling circuit is used to acquire the operating status of the battery in the battery management system and the battery status data of the battery in the operating status. The controller is used to determine the system load of the battery management system based on the operating status and the battery status data; when the system load is greater than or equal to the corresponding load threshold, the controller gradually increases the operating frequency of the operating system in the battery management system according to a preset step size within a first time period until the operating frequency reaches the target operating frequency.

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

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

Images