Battery management method and battery management system
By acquiring battery serial numbers and status information, and detecting and comparing threshold ranges, the problem of lack of information system management in battery management methods is solved, enabling flexible battery data correction and remote management.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- HYTERA COMM CORP
- Filing Date
- 2024-10-12
- Publication Date
- 2026-04-14
AI Technical Summary
Existing battery management methods lack information system management, are inflexible, and are extremely costly.
By acquiring the battery serial number and status information sent by the terminal, the system detects whether the data falls within a threshold range, compares the data, and updates the system battery information to avoid invalid data updates, thereby achieving data correction and management.
It effectively avoids invalid data updates caused by instantaneous fluctuations in battery status and information anomalies, enabling flexible acquisition, synchronization, and remote management of battery characteristic information.
Smart Images

Figure CN121862907A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of battery technology, and in particular to battery management methods and battery management systems. Background Technology
[0002] Today, battery safety and its intelligent management are of paramount importance in battery development and design, especially for electronic devices such as walkie-talkies, drones, and telemetry devices that use removable batteries. Because removable batteries can be used with different terminals and different charging docks, their safety monitoring and intelligent management are more complex.
[0003] Currently, battery data is typically acquired through handheld terminals or smart chargers and displayed directly on these devices, but this lacks information system management. Alternatively, large smart charging cabinets can be used to support centralized charging via a smart battery management system gateway, enabling unified collection of battery information and remote battery status management. However, this requires centralized management through the charging cabinet, making the solution inflexible and extremely costly. Summary of the Invention
[0004] The main technical problem addressed by this application is to provide a battery management method and a battery management system, which can solve the problems of existing battery management methods lacking information system management, having inflexible solutions, and incurring huge costs.
[0005] To solve the above-mentioned technical problems, one technical solution adopted in this application is: to provide a battery management method, wherein the battery management method includes: acquiring a battery serial number and battery status information sent by a terminal; wherein the terminal is detachably connected to a battery; if the battery status information is within a first threshold range, comparing the battery status information with the system battery information corresponding to the battery serial number; and when it is determined based on the comparison result that the battery status information is not abnormal, updating the system battery information to the battery status information.
[0006] To solve the above-mentioned technical problems, another technical solution adopted in this application is: to provide a battery management method, wherein the battery management method includes: obtaining the battery serial number and battery status information of the battery; sending the battery serial number and battery status information to a data management terminal, so that when the battery status information is within a first threshold range, the data management terminal compares the battery status information with the system battery information corresponding to the battery serial number, and when it is determined based on the comparison result that there is no abnormality in the battery status information, updates the system battery information to the battery status information.
[0007] To solve the above-mentioned technical problems, another technical solution adopted in this application is: to provide a battery management system, wherein the battery management system includes a data management terminal and a terminal connected in communication, the terminal being connected to a detachable battery; wherein the data management terminal is used to manage the battery using the battery management method described in any of the above claims, and the terminal is used to manage the battery using the battery management method described in any of the above claims.
[0008] The beneficial effects of this application are as follows: Unlike the prior art, the battery management method provided in this application obtains the battery serial number and battery status information sent by the terminal, and detects whether the battery status information is within a first threshold range. When the battery status information is within the first threshold range, the battery status information is compared with the system battery information corresponding to the battery serial number, and the comparison result determines whether there is an anomaly in the battery status information. If there is no anomaly in the battery status information, the system battery information is updated to the battery status information. This effectively avoids invalid data caused by instantaneous fluctuations in battery status and / or information acquisition and reporting anomalies from incorrectly updating data for each terminal, thus effectively correcting the data. Furthermore, the data management terminal is used to perform system data processing, analysis, and statistical management of the battery serial number and battery status information of each battery, so as to flexibly realize the acquisition and synchronization of each battery's characteristic information, data upload and download, and remote monitoring and management of each battery. Attached Figure Description
[0009] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort, wherein:
[0010] Figure 1 This is a flowchart illustrating the first embodiment of the battery management method of this application;
[0011] Figure 2 This is a schematic diagram of an embodiment of a battery management system;
[0012] Figure 3 This is a flowchart illustrating the second embodiment of the battery management method of this application;
[0013] Figure 4 This is a flowchart illustrating the third embodiment of the battery management method of this application;
[0014] Figure 5 This is a flowchart illustrating the fourth embodiment of the battery management method of this application;
[0015] Figure 6This is a flowchart illustrating the fifth embodiment of the battery management method of this application;
[0016] Figure 7 This is a flowchart illustrating the sixth embodiment of the battery management method of this application;
[0017] Figure 8 This is a schematic diagram of one embodiment of the battery management system of this application. Detailed Implementation
[0018] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of them. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.
[0019] The terms "first," "second," and "third" in this application are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Therefore, a feature defined as "first," "second," or "third" may explicitly or implicitly include at least one of that feature. In the description of this application, "multiple" means at least two, such as two, three, etc., unless otherwise explicitly specified. All directional indications (such as up, down, left, right, front, back, etc.) in the embodiments of this application are only used to explain the relative positional relationships and movements between components in a specific orientation (as shown in the figures). If the specific orientation changes, the directional indications also change accordingly. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or device that includes a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units not listed, or may optionally include other steps or units inherent to these processes, methods, products, or devices.
[0020] In this document, the term "implementation" means that a specific feature, structure, or characteristic described in connection with an implementation may be included in at least one implementation of this application. The appearance of this phrase in various places in the specification does not necessarily refer to the same implementation, nor is it a separate or alternative implementation mutually exclusive with other implementations. It will be explicitly and implicitly understood by those skilled in the art that the implementations described herein can be combined with other implementations.
[0021] The present application will now be described in detail with reference to the accompanying drawings and embodiments.
[0022] Please see Figure 1 and Figure 2 ,in, Figure 1 This is a flowchart illustrating the first embodiment of the battery management method of this application. Figure 2 This is a schematic diagram of an embodiment of a battery management system. Specifically, it may include the following steps:
[0023] S11: Obtain the battery serial number and battery status information sent by the terminal.
[0024] Understandably, such as Figure 2 As shown, the battery management method in this embodiment is specifically a data management terminal 101, which can also be understood as a method for the background cloud management system to centrally manage the feature information of the battery 103 that can be detachably installed in the smart terminal 102.
[0025] Optionally, the terminal 102 may specifically include one or more of any reasonable electronic devices that are detachably connected to the battery 103, such as a walkie-talkie, a smart charger 1022, a drone, or a telemetry electronic device. This application does not limit the scope of the application.
[0026] Optionally, the data management terminal 101 can be any reasonable electronic device with data processing function, such as a back-end computer or a cloud management server, or it can be understood as a cloud management system. This application does not limit it in this regard.
[0027] Optionally, the number of terminals 102 may be one or more, and they may belong to one or more types. For example, the terminal 102 may specifically include a walkie-talkie, or at least one walkie-talkie and a smart charger 1022, or at least one drone and a smart charging dock, or any reasonable combination of terminals. This application does not limit this.
[0028] Each terminal 102 is communicatively connected to the data management terminal 101 and detachably connected to a battery 103 for real-time or periodic monitoring of the battery 103's operating status, thereby obtaining the battery serial number and battery status information. Alternatively, the battery 103 may also have a built-in fuel gauge or other suitable detection circuit to self-check its operating status, obtain battery status information, and store the battery serial number and battery status information. When the battery 103 is installed on a terminal 102, the terminal 102 can retrieve the battery serial number and battery status information from the battery 103's storage space.
[0029] It is understood that the terminal 102 may specifically report and send the currently acquired battery serial number and its corresponding at least part of the battery status information to the data management terminal 101 in real time; and / or, each time the device is powered on, and / or each time a charge-discharge cycle is completed, and / or each time a change in battery status information is detected, and / or when the pre-set data reporting cycle expires and / or when any other reasonable preset trigger condition is met, the terminal 102 may report and send the currently acquired battery serial number and its corresponding at least part of the battery status information to the data management terminal 101. This application does not limit this.
[0030] It is worth noting that this battery serial number specifically refers to the software serial number, which is a string of numbers or letters, generally used as an identification code for electronic products. It is commonly used for anti-counterfeiting purposes, and its most significant feature is its uniqueness; that is, each battery 103 has a unique battery serial number. When the battery 103 is installed on different terminals 102, the corresponding battery 103 can be identified by obtaining this serial number, and the battery status information of the battery 103 can be identified and processed using this serial number.
[0031] In addition, the battery status information may include real-time data and non-real-time data. The real-time data may correspond to the data that the terminal 102 detects and acquires in real time, and reports and sends to the data management terminal 101. The non-real-time data may correspond to the data that the terminal 102 detects and acquires in a periodic manner or under preset conditions, and sends to the data management terminal 101.
[0032] Optionally, the battery status information may specifically include one or more of the following: real-time battery temperature, real-time battery charge, real-time battery voltage, timestamp, battery health, battery cycle count, battery full charge capacity, battery charge / discharge status, historical battery over-temperature, battery differential voltage status, battery bulging status, and over-temperature status. The real-time data may specifically include one or more of the following: real-time battery temperature, real-time battery charge, and real-time battery voltage. The non-real-time data, or long-cycle change data, may specifically include one or more of the following: timestamp, battery health, battery cycle count, battery full charge capacity, battery charge / discharge status, historical battery over-temperature, battery differential voltage status, battery bulging status, and over-temperature status. This application does not limit the specific data in this regard.
[0033] Specifically, the data management terminal 101 is used to receive and store the battery serial number and battery status information actively reported and sent by each terminal 102, so as to centrally manage the battery serial number and each battery status information; or, the data management terminal 101 can also actively obtain the battery serial number and battery status information currently detected and stored by each terminal 102.
[0034] It is worth noting that each terminal 102 specifically reports and sends real-time data from the battery serial number and battery status information to the data management terminal 101 in real time; and when a preset trigger condition is met, such as power-on, and / or completion of a charge-discharge cycle, and / or a change in battery status information, and / or expiration of the data reporting cycle, and / or any other reasonable preset trigger condition, it reports and sends non-real-time data from the battery serial number and battery status information to the data management terminal 101.
[0035] Similarly, the data management terminal 101 can also actively acquire real-time data from the battery serial number and battery status information currently detected and stored by each terminal 102; or, when a preset trigger condition is met, such as a set period, and / or device restart and / or other arbitrary reasonable preset trigger conditions, the terminal 102 can acquire the battery serial number and battery status information currently detected and stored by each terminal 102.
[0036] S12: Detect whether the battery status information is within the first threshold range.
[0037] Understandably, in order to facilitate the effective management and interpretation of the operating status and corresponding status information of battery 103, the battery status information can usually be quantified by specific values, and different battery status information has different value ranges. Values exceeding the range will be considered unreasonable, or the currently acquired battery status information will be invalid data.
[0038] For example, the battery status information (which varies depending on the battery) must meet the following requirements: real-time battery charge: 0%–100%; real-time battery voltage: 0V–8.9V; battery health: 0%–100%; battery cycle count: >=0; battery full charge capacity: 0–2000mAh; battery charge / discharge status: charging (e.g., 0), discharging (e.g., 1); highest historical battery temperature: >60 degrees Celsius; battery differential pressure status: no differential pressure (e.g., 0), differential pressure (e.g., 1); battery bulging status: no bulging (e.g., 0), bulging (e.g., 1).
[0039] Specifically, the data management terminal 101 is also used to detect whether the status information of each battery is within the corresponding first threshold range, so as to determine whether the currently acquired status information of each battery is reasonable and whether it is invalid data.
[0040] It is worth noting that the first threshold range can be understood as the preset reasonable and valid threshold range for each battery status information. Different battery status information corresponds to different first threshold ranges. For example, if the currently acquired battery differential pressure is neither 1 nor 0, it will be considered invalid data, while if the battery differential pressure is 1 or 0, it will be considered valid data. Similarly, other battery status information can be treated in the same way to determine whether the currently acquired battery status information is reasonable or invalid data. This will not be elaborated further here.
[0041] If the battery status information is within the first threshold range, then S13 is executed; if the battery status information is not within the first threshold range, then S15 is executed.
[0042] S13: Compare the battery status information with the system battery information corresponding to the battery serial number.
[0043] Understandably, in order to facilitate centralized management of the battery status information of each battery 103, the data management terminal 101 also stores system battery information corresponding to each battery serial number. That is, each system battery information and each battery status information have the same parameter information for the same battery serial number, such as real-time battery temperature, real-time battery voltage, battery cycle count, battery charge and discharge status, etc., and they correspond one-to-one. After receiving the battery serial number and battery status information sent by the terminal 102, it can determine whether to update the currently stored system battery information based on the battery serial number and battery status information.
[0044] Specifically, the currently acquired battery status information is compared one by one with the system battery information currently stored in the data management terminal 101 corresponding to the battery serial number to determine whether the change range between each currently acquired battery status information and its corresponding system battery information is reasonable; and / or, when one battery status information is within the second threshold range, whether the change range between another or several battery status information and its corresponding system battery information is reasonable; and / or, when the change range between one battery status information and its corresponding system battery information is within the second threshold range, whether the change range between another or several battery status information and its corresponding system battery information is reasonable, and / or whether any other reasonable parameter comparison is reasonable.
[0045] S14: Determine whether there are any abnormalities in the battery status information based on the comparison results.
[0046] Understandably, in the actual application of battery 103, the battery status information reported to the data management terminal 101 by the terminal 102 before and after the battery status information usually meets a specific range of change. If the information exceeds the specific range of change, it will be identified as invalid data. Thus, it is possible to determine whether there is an anomaly in the battery status information by comparing the currently acquired battery status information with the system battery information corresponding to the battery serial number.
[0047] For example, when the battery cycle count varies between 1 and 10 cycles, a change in battery health of less than 5%, such as a drop from 100% to 98%, is considered normal data. However, a change exceeding 5%, such as a drop from 100% to 60%, is considered abnormal and invalid, and must be discarded. Similarly, when the battery health change is less than 5%, a change in full charge capacity of less than 5%, such as a drop from 2000mAh to 1900mAh, is considered normal data. Conversely, a change exceeding 5%, such as a drop from 2000mAh to 1300mAh, is considered abnormal and invalid, and must be discarded. This process continues, using preset information comparison rules to determine if any abnormalities exist in the currently acquired battery status information; details are omitted here.
[0048] If the comparison results indicate that the battery status information is abnormal, then S15 is executed; if the comparison results indicate that the battery status information is not abnormal, then S17 is executed.
[0049] S15: Delete the currently acquired battery status information.
[0050] Specifically, when the data management terminal 101 determines that the battery status information is not within the first threshold range, it determines that the currently acquired battery status information is invalid and deletes the battery status information to avoid data update errors; and / or, when it determines that the currently acquired battery status information is abnormal, it directly deletes the battery status information to avoid invalid data causing the data management terminal 101 to update data incorrectly.
[0051] S16: Send the system battery information to the terminal so that the terminal updates the battery storage and display information to the system battery information.
[0052] Furthermore, the data management terminal 101 sends the currently stored system battery information to each terminal, so that each terminal 102 updates the current battery storage and display information to the system battery information, in order to avoid incorrect storage and display of currently acquired invalid data.
[0053] S17: Update the system battery information to battery status information.
[0054] When the data management terminal 101 determines that there is no abnormality in the currently acquired battery status information, it determines that the battery status information currently reported by the terminal 102 is valid and updates the currently stored system battery information to the battery status information.
[0055] Furthermore, in one embodiment, the number of battery status information is at least two, the number of system battery information is at least two, and each battery status information corresponds to one system battery information. Specifically, S13 further includes: sequentially detecting whether the difference between each battery status information and its corresponding system battery information is within the range of a second threshold. The detection order of the at least two battery status information is not particularly required and is not limited here.
[0056] It is worth noting that the battery status information may specifically include one or more of the following: real-time battery temperature, real-time battery capacity, real-time battery voltage, timestamp, battery health, battery cycle count, full charge capacity, battery charge / discharge status, historical battery over-temperature, battery differential voltage status, battery bulging status, and over-temperature status. Furthermore, the battery information in this system corresponding to this battery status information may also specifically include one or more of the following: real-time battery temperature, real-time battery capacity, real-time battery voltage, timestamp, battery health, battery cycle count, full charge capacity, battery charge / discharge status, historical battery over-temperature, battery differential voltage status, battery bulging status, and over-temperature status.
[0057] Furthermore, the range of the second threshold may have different characteristics in different detection procedures, and is determined by the actual application scenario. This application does not limit this range.
[0058] Specifically, if the difference between each battery status information and its corresponding system battery information is within the second threshold range, it is determined that the battery status information is not abnormal; if there is a difference that is not within the second threshold range, it is determined that the battery status information is abnormal. It should be noted that when detecting at least two battery status information in sequence, as long as one difference is detected that is not within the second threshold range, it is not necessary to detect other battery status information, and it can be directly determined that the battery status information is abnormal.
[0059] For ease of understanding, taking the battery status information specifically including battery cycle count and battery health as an example, where the second threshold range for the battery cycle count is 1-10 times and the second threshold range for the battery cycle count is <5%, it can be seen that when the difference between the battery cycle count currently reported by terminal 102 and the battery cycle count currently stored by data management terminal 101, that is, the change range of the battery cycle count, is within 1-10 times; and the difference between the battery health currently reported by terminal 102 and the battery health currently stored by data management terminal 101, that is, the change range of the battery health, is <5%, such as dropping from 100% to 98%, it will be judged as normal data.
[0060] If the change in the number of battery cycles exceeds 1-10 times, such as from 1 to 15 times; and / or the change in the battery health exceeds the range of <5%, such as from 100% to 60%, then the currently acquired battery health data is considered abnormal and invalid, and must be discarded.
[0061] Similarly, when the battery status information specifically includes battery health and battery full charge capacity, and the second threshold range corresponding to the battery health is <5%, and the second threshold range corresponding to the battery full charge capacity is <5%, if the difference between the battery health currently reported by terminal 102 and the battery health currently stored by data management terminal 101, i.e., the change in battery health, is <5%; and the difference between the battery full charge capacity currently reported by terminal 102 and the battery full charge capacity currently stored by data management terminal 101, i.e., the change in battery full charge capacity, is <5%, such as a decrease from 2000mAh to 1900mAh, then it is determined to be normal data.
[0062] If the change in battery health exceeds the range of <5%, such as from 100% to 60%; and / or the change in battery full charge capacity exceeds the range of <5%, such as from 2000mAh to 1300mAh, then the battery full charge capacity data is considered abnormal and invalid, and must be discarded.
[0063] It is understandable that the battery status information may include any other reasonable information, and the second threshold range will be different for different information, which will not be elaborated here.
[0064] The above solution effectively avoids erroneous data updates to each terminal caused by instantaneous fluctuations in battery status and / or abnormal information acquisition and reporting by threshold detection and information comparison of battery status information. This effectively corrects the data and utilizes the data management terminal to perform systematic data processing, analysis, and statistical management of each battery's serial number and battery status information. It flexibly realizes the acquisition and synchronization of each battery's characteristic information, data upload and download, and remote monitoring and management of each battery.
[0065] Please see Figure 3 , Figure 3 This is a flowchart illustrating the second embodiment of the battery management method of this application. The battery management method of this embodiment... Figure 1 A detailed implementation flowchart of the battery management method is shown, which specifically includes the following steps:
[0066] S21: Obtain the battery serial number and battery status information sent by the terminal.
[0067] S22: Detect whether the battery status information is within the first threshold range.
[0068] If the battery status information is within the first threshold range, then execute S23-S24; if the battery status information is not within the first threshold range, then execute S29.
[0069] S23: Compare the battery status information with the system battery information corresponding to the battery serial number.
[0070] Among them, S21, S22 and S23 and Figure 1 S11, S12 and S13 are the same. Please refer to the textual descriptions of S11, S12 and S13 and their related texts for details. They will not be repeated here.
[0071] S24: Based on the comparison results, detect whether there are any abnormalities in the status information of each battery obtained for a set number of consecutive times.
[0072] It is understood that the terminal 102 may specifically include a smart charger 1022 and / or a power-consuming terminal 1021. The smart charger 1022 refers to an electronic device that has one or more of the following reasonable battery processing functions: battery repair, support for battery charging and discharging, general data detection, and battery calibration. The power-consuming terminal 1021 refers to an electronic device that uses the battery 103 to power other reasonable signal processing functions, such as a walkie-talkie, a drone, or a telemetry electronic device. Therefore, there are differences in their performance. When the data management terminal 101 interacts with and manages information with the two, there are also some differences, especially in the information interaction with the smart charger 1022. Because the smart charger 1022 has a battery repair function, it can also be triggered to repair the battery 103 when abnormal status information is detected.
[0073] Specifically, when the comparison result indicates that the battery status information is abnormal, the data management terminal 101 executes the set number of S21-S23 cycles to continuously detect whether there is any abnormality in each currently acquired battery status information based on the comparison result between the battery status information and the system battery information corresponding to the battery serial number.
[0074] If each battery status information obtained after a set number of consecutive comparisons is found to be abnormal, then S29 is executed; if each battery status information obtained after a set number of consecutive comparisons is found to be normal, then S28 is executed.
[0075] If, based on the comparison results, every battery state information obtained for a set number of consecutive tests shows an anomaly, the battery management method in this embodiment further includes:
[0076] S25: Detect whether the terminal is a smart charger.
[0077] The data management terminal 101 determines whether the terminal currently reporting the information is a smart charger based on the currently acquired battery status information, additional feature information, or other arbitrary reasonable annotation information.
[0078] If the terminal is a smart charger, then S26 is executed; if the terminal is not a smart charger, then S27 is executed.
[0079] S26: Send a repair command to the smart charger so that the smart charger can repair the battery.
[0080] Understandably, when the data management terminal 101 determines that each battery status information obtained is abnormal after a set number of consecutive times, such as 2, 3, or 5 consecutive times, and the terminal currently reporting the information is a smart charger, it sends a repair instruction to the smart charger 1022 so that the smart charger 1022 can repair the corresponding battery 103.
[0081] In this device, after repairing the battery 103, the smart charger 1022 is also used to re-acquire the battery serial number and battery status information of the repaired battery 103 and report them to the data management terminal 101, that is, to execute S21-S26 again, so that the battery 103 can be remotely calibrated and repaired through big data analysis.
[0082] S27: Issues a repair reminder.
[0083] Understandably, when the data management terminal 101 determines that the terminal currently reporting information is not a smart charger, that is, it does not have a battery repair function, it issues a repair reminder instruction, such as issuing an audible and visual alarm, or popping up a repair reminder message on the display screen of the data management terminal 101, to remind the user that the battery 103 is in an abnormal state and needs to be repaired.
[0084] S28: Update the system battery information to battery status information.
[0085] When the data management terminal 101 determines that there is no abnormality in the currently acquired battery status information, it determines that the battery status information currently reported by the terminal 102 is valid and updates the currently stored system battery information to the battery status information.
[0086] S29: Delete the currently acquired battery status information.
[0087] Among them, S29 and Figure 1 The same applies to S15 in the previous example; please refer to S15 and its related textual description for details, which will not be repeated here. It should be noted that in this embodiment, if every battery status information obtained for a set number of consecutive times is abnormal, the execution order of steps S25-S27 and step S29 is not important; they can be executed simultaneously or at different times.
[0088] Furthermore, in one embodiment, the above-mentioned S27 may further include: sending a repair reminder instruction to the terminal to trigger the terminal to issue a repair reminder instruction.
[0089] The above solution effectively avoids erroneous data updates to each terminal caused by instantaneous fluctuations in battery status and / or abnormal information acquisition and reporting by threshold detection and information comparison of battery status information. This effectively corrects the data and utilizes the data management terminal to perform systematic data processing, analysis, and statistical management of each battery's serial number and battery status information. It flexibly realizes the acquisition and synchronization of each battery's characteristic information, data upload and download, and remote monitoring and management of each battery.
[0090] Please see Figure 4 , Figure 4This is a flowchart illustrating the third embodiment of the battery management method of this application. The battery management method of this embodiment... Figure 1 A detailed implementation flowchart of the battery management method is shown, which specifically includes the following steps:
[0091] S31: Obtain the battery serial number and battery status information sent by the terminal.
[0092] Among them, S31 and Figure 1 The same applies to S11. Please refer to S11 and its related textual descriptions for details, which will not be repeated here.
[0093] S32: Detect whether the battery status information is battery repair information.
[0094] Understandably, after the smart charger 1022 repairs the battery 103, the battery status information obtained, i.e. the battery repair information, will have a higher processing priority than the general battery status information. Moreover, the repaired battery status information has specific additional information so that it can be identified and differentiated by the data management terminal 101.
[0095] If the currently acquired battery status information is battery repair information, then S33 is executed; if the currently acquired battery status information is not battery repair information, then S35 is executed.
[0096] S33: Update the system battery information to battery repair information.
[0097] Understandably, battery repair information has a higher processing priority than general battery status information, so that when the data management terminal 101 determines that the currently acquired battery status information is battery repair information, the currently stored system battery information is directly updated to battery repair information.
[0098] S34: Send the updated system battery information to the terminal.
[0099] Furthermore, the data management terminal 101 sends the updated system battery information to each terminal 102, so that each terminal 102 updates its current battery storage and display information to the system battery information, thereby avoiding the incorrect storage and display of currently acquired invalid data.
[0100] S35: Detect whether the battery status information is within the first threshold range.
[0101] If the battery status information is within the first threshold range, then execute S36-39 and S310; if the battery status information is not within the first threshold range, then execute S38.
[0102] S36: Compare the battery status information with the system battery information corresponding to the battery serial number.
[0103] S37: Determine whether there are any abnormalities in the battery status information based on the comparison results.
[0104] If the comparison results indicate that the battery status information is abnormal, then execute S38-S39; if the comparison results indicate that the battery status information is not abnormal, then execute S310.
[0105] S38: Delete the currently acquired battery status information.
[0106] S39: Send system battery information to the terminal so that the terminal updates the battery storage and display information to the system battery information.
[0107] S310: Updates the system battery information to battery status information. Among these, S35, S36, S37, S38, S39, and S310 are related to... Figure 1 S12, S13, S14, S15, S16, and S17 are the same. Please refer to the textual descriptions of S12, S13, S14, S15, S16, and S17 for details. They will not be repeated here.
[0108] Please see Figure 5 , Figure 5 This is a flowchart illustrating the fourth embodiment of the battery management method of this application. The battery management method of this embodiment... Figure 1 A detailed implementation flowchart of the battery management method is shown, which specifically includes the following steps:
[0109] S41: Obtain the battery serial number and battery status information sent by the terminal.
[0110] Among them, S41 and Figure 1 The same applies to S11. Please refer to S11 and its related textual descriptions for details, which will not be repeated here.
[0111] S42: Detect whether the battery status information is within the first threshold range.
[0112] S43: Compare the battery status information with the system battery information corresponding to the battery serial number.
[0113] S44: Determine whether there are any abnormalities in the battery status information based on the comparison results.
[0114] S45: Delete the currently acquired battery status information.
[0115] S46: Send system battery information to the terminal so that the terminal updates the battery storage and display information to the system battery information.
[0116] S47: Update the system battery information to battery status information.
[0117] Among them, S41, S42, S43, S44, S45, S469, and S47 and Figure 1 S11, S12, S13, S14, S15, S16 and S17 are the same. For details, please refer to the textual descriptions of S11, S12, S13, S14, S15, S16 and S17 and their related texts. They will not be repeated here.
[0118] In this embodiment, after step S42, if the battery state information is within the first threshold range, the battery management method further includes:
[0119] S48: Detect whether there is any bad status information in the battery status information.
[0120] Understandably, any reasonable information in the battery status information, such as battery health, battery differential pressure, battery bulging, and over-temperature, can typically characterize the specific operating state of battery 103. This allows us to interpret whether the battery currently detachably connected to terminal 102 is operating well. For example, a battery bulging status of 1 indicates that battery 103 is not operating well, but the data is valid; a battery health status >80% indicates that battery 103 is operating well, but the data is valid. Similarly, we can sequentially detect whether there is any malfunctioning status information in the battery status information.
[0121] If there is a bad status information in the battery status information, then execute S49; if there is no bad status information in the battery status information, then execute S43-S47.
[0122] S49: Issue an alarm instruction.
[0123] Understandably, when the data management terminal 101 determines that there is an abnormal status in the battery status information, it will issue an alarm indication, such as issuing an audible and visual alarm, or popping up an alarm message on the display screen of the data management terminal 101, to remind the user that the battery 103 is malfunctioning and needs to be repaired or replaced.
[0124] Furthermore, in one embodiment, the above-mentioned S49 may further include: sending an alarm command to the terminal to trigger the terminal to issue an alarm indication.
[0125] Furthermore, in one embodiment, when the above-mentioned battery status information is abnormal, this embodiment can also perform the step of detecting whether the terminal is a smart charger, as detailed in S25-S27, which will not be repeated here.
[0126] Through the above methods, the data management terminal 101 can effectively acquire battery status and information, upload and synchronize data, monitor, display, and manage battery status, and achieve intelligent safety management of the removable battery 103, thereby improving product competitiveness. Furthermore, by utilizing backend big data analysis, it issues alarms and prompts for batteries 103 with abnormal status and remotely controls the smart charger 1022 to calibrate and repair the battery 103, effectively enhancing the user experience. In addition, by acquiring and detecting data, it can effectively prevent invalid data caused by instantaneous fluctuations in the battery 103 status from incorrectly updating data in each terminal 102, thus effectively correcting the data.
[0127] Please see Figure 6 , Figure 6 This is a flowchart illustrating the fifth embodiment of the battery management method of this application. Specifically, it may include the following steps:
[0128] S51: Obtain the battery serial number and battery status information.
[0129] It is understood that, in this embodiment, as Figure 2 As shown, the battery management method is specifically a method by which the terminal 102 manages the feature information of the battery 103 that is detachably connected to it.
[0130] Optionally, the terminal 102 may be one or more of any reasonable electronic devices with a battery 103 detachably connected, such as a walkie-talkie, a smart charger 1022, a drone, or a telemetry electronic device. This application does not limit the specific device to these devices.
[0131] Specifically, the terminal 102 monitors the operating status of the battery 103 in real time to obtain the battery serial number and battery status information of the battery 103. Alternatively, the battery 103 may also have a built-in fuel gauge or other reasonable detection circuit to self-check its operating status, obtain battery status information, and store the corresponding battery serial number and battery status information. This allows the terminal 102 to retrieve the battery serial number and battery status information from the storage space of the battery 103 when the battery 103 is installed on it.
[0132] S52: Send the battery serial number and battery status information to the data management terminal so that the data management terminal can detect whether the battery status information is within the first threshold range. When the battery status information is within the first threshold range, compare the battery status information with the system battery information corresponding to the battery serial number, and determine whether there is an anomaly in the battery status information based on the comparison result. When there is no anomaly in the battery status information, update the system battery information to the battery status information.
[0133] Furthermore, the terminal 102 can specifically report and send the currently acquired battery serial number and its corresponding at least part of the battery status information to the data management terminal 101 in real time; and / or, each time the device is powered on, and / or each time a charge-discharge cycle is completed, and / or each time a change in battery status information is detected, and / or when the pre-set data reporting cycle expires and / or when any other reasonable preset trigger condition is met, the terminal 102 can report and send the currently acquired battery serial number and its corresponding at least part of the battery status information to the data management terminal 101.
[0134] Optionally, the battery status information may specifically include one or more of the following: real-time battery temperature, real-time battery charge, real-time battery voltage, timestamp, battery health, battery cycle count, battery full charge capacity, battery charge / discharge status, historical battery over-temperature, battery differential voltage status, battery bulging status, and over-temperature status. The real-time data may specifically include one or more of the following: real-time battery temperature, real-time battery charge, and real-time battery voltage. The non-real-time data, or long-cycle change data, may specifically include one or more of the following: timestamp, battery health, battery cycle count, battery full charge capacity, battery charge / discharge status, historical battery over-temperature, battery differential voltage status, battery bulging status, and over-temperature status. This application does not limit the specific data in this regard.
[0135] The data management terminal 101 is used to receive and store the battery serial number and battery status information actively reported and sent by each terminal 102, so as to centrally manage the battery serial number and each battery status information; or, the data management terminal 101 can also actively obtain the battery serial number and battery status information currently detected and stored by each terminal 102.
[0136] It is worth noting that each terminal 102 specifically reports and sends real-time data from the battery serial number and battery status information to the data management terminal 101 in real time; and when a preset trigger condition is met, such as power-on, and / or completion of a charge-discharge cycle, and / or a change in battery status information, and / or expiration of the data reporting cycle, and / or any other reasonable preset trigger condition, it reports and sends non-real-time data from the battery serial number and battery status information to the data management terminal 101.
[0137] Similarly, the data management terminal 101 can also actively acquire real-time data from the battery serial number and battery status information currently detected and stored by each terminal 102; or, when a preset trigger condition is met, such as a set period, and / or device restart and / or other arbitrary reasonable preset trigger conditions, the terminal 102 can acquire the battery serial number and battery status information currently detected and stored by each terminal 102.
[0138] To facilitate the effective management and interpretation of the operating status and corresponding status information of battery 103, the battery status information can usually be quantified by specific values. Different battery status information has different value ranges, and values exceeding these ranges will be considered unreasonable, or the currently acquired battery status information will be considered invalid data.
[0139] For example, the battery status information (which varies depending on the battery type 103) must meet the following requirements: real-time battery charge: 0%–100%; real-time battery voltage: 0V–8.9V; battery health: 0%–100%; battery cycle count: >=0; battery full charge capacity: 0–2000mAh; battery charge / discharge status: charging (e.g., 0), discharging (e.g., 1); highest historical battery temperature: >60 degrees Celsius; battery differential pressure status: no differential pressure (e.g., 0), differential pressure (e.g., 1); and battery bulging status: no bulging (e.g., 0), bulging (e.g., 1).
[0140] Specifically, the data management terminal 101 is also used to detect whether the status information of each battery is within the corresponding first threshold range, so as to determine whether the currently acquired status information of each battery is reasonable and whether it is invalid data.
[0141] It is worth noting that the first threshold range can be understood as the preset reasonable and valid threshold range for each battery status information. Different battery status information corresponds to different first threshold ranges. For example, if the currently acquired battery differential pressure is neither 1 nor 0, it will be considered invalid data, while if the battery differential pressure is 1 or 0, it will be considered valid data. Similarly, other battery status information can be treated in the same way to determine whether the currently acquired battery status information is reasonable or invalid data. This will not be elaborated further here.
[0142] To facilitate centralized management of the battery status information of each battery 103, the data management terminal 101 also stores system battery information corresponding to each battery serial number. That is, each system battery information and each battery status information has the same parameter information for the same battery serial number, such as real-time battery temperature, real-time battery voltage, battery cycle count, battery charge and discharge status, etc., and they correspond one-to-one. After receiving the battery serial number and battery status information sent by the terminal 102, it can determine whether to update the currently stored system battery information based on the battery serial number and battery status information.
[0143] Specifically, when the data management terminal 101 determines that the currently acquired battery status information is within the first threshold range, it compares each currently acquired battery status information with each system battery information currently stored in the data management terminal 101 corresponding to the battery serial number to determine whether the change range between each currently acquired battery status information and its corresponding system battery information is reasonable; and / or, when one battery status information is within the second threshold range, whether the change range between another or several battery status information and its corresponding system battery information is reasonable; and / or, when the change range between one battery status information and its corresponding system battery information is within the second threshold range, whether the change range between another or several battery status information and its corresponding system battery information is reasonable, and / or whether any other reasonable parameter comparison is reasonable.
[0144] Understandably, in the actual application of battery 103, the battery status information reported to the data management terminal 101 by the terminal 102 before and after the battery status information usually meets a specific range of change. If the information exceeds the specific range of change, it will be identified as invalid data. Thus, it is possible to determine whether there is an anomaly in the battery status information by comparing the currently acquired battery status information with the system battery information corresponding to the battery serial number.
[0145] For example, when the battery cycle count varies between 1 and 10 cycles, a change in battery health of less than 5%, such as a drop from 100% to 98%, is considered normal data. However, a change exceeding 5%, such as a drop from 100% to 60%, is considered abnormal and invalid, and must be discarded. Similarly, when the battery health change is less than 5%, a change in full charge capacity of less than 5%, such as a drop from 2000mAh to 1900mAh, is considered normal data. Conversely, a change exceeding 5%, such as a drop from 2000mAh to 1300mAh, is considered abnormal and invalid, and must be discarded. This process continues, using preset information comparison rules to determine if any abnormalities exist in the currently acquired battery status information; details are omitted here.
[0146] When the data management terminal 101 determines that there is no abnormality in the currently acquired battery status information, it determines that the battery status information currently reported by the terminal 102 is valid and updates the currently stored system battery information to the battery status information.
[0147] Furthermore, when the data management terminal 101 determines that the battery status information is not within the first threshold range, it determines the currently acquired battery status information and deletes the battery status information to avoid data update errors.
[0148] Please see Figure 7 , Figure 7 This is a schematic diagram of one embodiment of the battery management system of this application. The battery management method of this embodiment is... Figure 6 A detailed implementation flowchart of the battery management method is shown, which specifically includes the following steps:
[0149] S61: Obtain the battery serial number and battery status information.
[0150] S62: Send the battery serial number and battery status information to the data management terminal so that the data management terminal can detect whether the battery status information is within the first threshold range. When the battery status information is within the first threshold range, compare the battery status information with the system battery information corresponding to the battery serial number, and determine whether there is an anomaly in the battery status information based on the comparison result. When there is no anomaly in the battery status information, update the system battery information to the battery status information.
[0151] Among them, S61 and S62 and Figure 6 S51 and S52 are the same. Please refer to S13 and S14 and their related textual descriptions for details, which will not be repeated here.
[0152] S63: Receive system battery information sent by the data management terminal when it determines that there is an abnormality in the battery status information.
[0153] Understandably, when the data management terminal 101 determines that the currently acquired battery status information is abnormal, it directly deletes the battery status information to avoid invalid data causing the data management terminal 101 to update the data incorrectly, and sends the currently stored system battery information to each terminal 102.
[0154] S64: Update battery storage and display information to system battery information.
[0155] Furthermore, the terminal 102 updates the current battery storage and display information to the system battery information to avoid incorrect storage and display of currently acquired invalid data.
[0156] It is understandable that when the data management terminal 101 receives the battery serial number and battery status information sent by the terminal 102, it can also implement the battery management method described in any of the above embodiments. Please refer to [link / reference] for details. Figures 1-5 The relevant textual content will not be elaborated upon here.
[0157] This application also provides a battery management system; please refer to [link / reference]. Figure 8 , Figure 8 This is a schematic diagram of one embodiment of the battery management system of this application.
[0158] In this embodiment, the battery management system 70 includes a data management terminal 71 and a terminal 72 that are connected in communication. The terminal 72 is used to detachably connect to the battery 701.
[0159] Optionally, the terminal 72 may be one or more of any reasonable electronic devices detachably connected to the battery 701, such as a walkie-talkie, a smart charger 722, a drone, or a telemetry electronic device. This application does not limit the specific device to these devices.
[0160] Optionally, the data management terminal 71 can be any reasonable electronic device with data processing function, such as a back-end computer or a cloud management server, and this application does not limit it.
[0161] Optionally, the number of terminals 72 may be one or more, and they may belong to one or more types. For example, the terminal 72 may specifically include a walkie-talkie, or at least one walkie-talkie and a smart charger 722, or at least one drone and a smart charging dock, or any reasonable combination of terminals. This application does not limit this.
[0162] Optionally, the terminal 72 includes a power terminal 721 and a smart charger 722. The power terminal 721 can be one or more of any reasonable electronic devices connected to a removable battery, such as a walkie-talkie, a drone, or a telemetry electronic device. This application does not limit the specific type of device.
[0163] It is worth noting that the data management terminal 71 can be understood as the back-end cloud management system of the battery 701. It can receive battery serial numbers and battery status information reported by the power-consuming terminals 721 or smart chargers 722, and perform big data analysis, data stabilization, data correction, data display, and anomaly alerts on the battery serial numbers and battery status information. Furthermore, the data management terminal 71 can also distribute corrected and abnormal data to all online power-consuming terminals 721 and smart chargers 722 that are connected to it, enabling remote monitoring and management. The uplink and downlink channels include wired transmission and / or wireless transmission.
[0164] Optionally, the battery status information may specifically include one or more of the following features that reasonably characterize the operating status of the battery 701, such as health status, temperature, charge, deep over-discharge status, differential voltage status, and over-temperature status. This application does not limit this.
[0165] In addition, the power terminal 721 can be understood as a device that can be detachably connected to the battery 701 and communicate directly with the battery 701 to obtain data from the fuel gauge inside the battery 701. It can also receive system battery information sent by the data management terminal 71 and request data from the data management terminal 71 to compare and judge the battery status information obtained from the battery 701 with the system battery information and update the local data.
[0166] In other embodiments, when the battery 701 does not have a detection function, the power terminal 721 can also detect the operating status of the battery 701 in real time and obtain the battery serial number and battery status information of the battery 701.
[0167] The battery 701 has a built-in fuel gauge and stores battery status information and cycle count.
[0168] The smart charger 722 supports charging and discharging of battery 701 and repair of battery 701, and has functions such as general data detection and battery 701 calibration. The smart charger 722 can upload data to the data management terminal 71, receive system battery information issued by the data management terminal 71, and request data from the data management terminal 71. The data reported by the smart charger 722 after calibration and repair has the highest priority.
[0169] It should be noted that the data management terminal 71 described in this embodiment is used to manage the battery 701 using the battery management method described in any of the preceding embodiments. Please refer to [link / reference] for details. Figures 1-5 The relevant textual content will not be elaborated upon here.
[0170] The terminal 72 described in this embodiment is used to manage the battery 701 using the battery management method as described in any of the preceding embodiments. For details, please refer to [link to relevant documentation]. Figures 6-7 The relevant textual content will not be elaborated upon here.
[0171] The beneficial effects of this application are as follows: Unlike the prior art, the battery management method provided in this application obtains the battery serial number and battery status information sent by the terminal, and detects whether the battery status information is within a first threshold range. When the battery status information is within the first threshold range, the battery status information is compared with the system battery information corresponding to the battery serial number, and the comparison result determines whether there is an anomaly in the battery status information. If there is no anomaly in the battery status information, the system battery information is updated to the battery status information. This effectively avoids invalid data updates to each terminal caused by instantaneous fluctuations in battery status and / or information acquisition and reporting anomalies, thus effectively de-jittering and correcting the data. Furthermore, the data management terminal is used to perform system data processing, analysis, and statistical management of the battery serial number and battery status information of each battery, so as to flexibly realize the acquisition and synchronization of each battery's characteristic information, data upload and download, and remote monitoring and management of each battery.
[0172] The above description is merely an embodiment of this application and does not limit the patent scope of this application. Any equivalent structural or procedural transformations made using the content of this application's specification and drawings, or direct or indirect applications in other related technical fields, are similarly included within the patent protection scope of this application.
Claims
1. A battery management method, characterized in that, The battery management method includes: The terminal receives the battery serial number and battery status information sent by the terminal; wherein the terminal is detachably connected to a battery. If the battery status information is within the first threshold range, compare the battery status information with the system battery information corresponding to the battery serial number; If the comparison results determine that there is no abnormality in the battery status information, the system battery information is updated to the battery status information.
2. The battery management method according to claim 1, characterized in that, The battery management method includes: If the comparison results indicate that the battery status information is abnormal, the currently acquired battery status information is deleted. The system battery information is sent to the terminal so that the terminal updates its battery storage and display information to the system battery information.
3. The battery management method according to claim 2, characterized in that, The number of battery status information items is at least two, the number of system battery information items is at least two, each battery status information item corresponds to one system battery information item, and the comparison of the battery status information item with the system battery information item corresponding to the battery serial number includes: Sequentially detect whether the difference between each battery status information and the corresponding system battery information is within the second threshold range; Accordingly, the step of determining that the battery state information does not have any abnormalities based on the comparison results includes: If all the differences are within the second threshold range, it is determined that the battery status information is not abnormal. Accordingly, the step of determining that the battery state information is abnormal based on the comparison results includes: If one of the differences is not within the range of the second threshold, it is determined that the battery status information is abnormal.
4. The battery management method according to claim 2, characterized in that, When it is determined from the comparison results that the battery status information is abnormal, the step of deleting the currently acquired battery status information includes: After determining that the battery status information is abnormal based on the comparison results, the system detects whether each piece of battery status information obtained consecutively for a set number of times is abnormal. If any of the battery status information obtained within the set number of consecutive iterations is abnormal, the currently obtained battery status information is deleted.
5. The battery management method according to claim 4, characterized in that, The battery management method further includes: If no abnormality is found in each of the battery status information acquired a predetermined number of consecutive times, the system battery information is updated to the battery status information acquired last time.
6. The battery management method according to claim 4, characterized in that, If any of the battery status information obtained consecutively within the set number of times is abnormal, the battery management method further includes: Detect whether the terminal is a smart charger; If the terminal is the smart charger, a repair command is sent to the smart charger so that the smart charger can repair the battery.
7. The battery management method according to claim 6, characterized in that, The battery management method further includes: If the terminal is not the smart charger, issue a repair reminder instruction; and / or send an alarm command to the terminal to trigger the terminal to issue a repair reminder instruction.
8. The battery management method according to claim 1, characterized in that, After the step of obtaining the battery serial number and battery status information sent by the terminal, the battery management method further includes: Detect whether the battery status information is battery repair information; If the battery status information is the battery repair information, update the system battery information to the battery repair information; Send the updated system battery information to the terminal; If the battery status information is not the battery repair information, then the step of comparing the battery status information with the system battery information corresponding to the battery serial number is performed if the battery status information is within the first threshold range.
9. The battery management method according to claim 1, characterized in that, After the step of detecting whether the battery status information is within the first threshold range, and before the step of comparing the battery status information with the system battery information corresponding to the battery serial number, the method further includes: Detect whether there is any adverse status information in the battery status information; If the battery status information contains the malfunctioning status information, an alarm indication is issued; and / or, an alarm command is sent to the terminal to trigger the terminal to issue an alarm indication. If the defective status information is not present in the battery status information, then the step of comparing the battery status information with the system battery information corresponding to the battery serial number is performed if the battery status information is within the first threshold range.
10. A battery management method, characterized in that, The battery management method includes: Obtain the battery serial number and battery status information; The battery serial number and the battery status information are sent to the data management terminal, so that when the battery status information is within the first threshold range, the data management terminal compares the battery status information with the system battery information corresponding to the battery serial number, and updates the system battery information to the battery status information when it is determined that the battery status information is not abnormal based on the comparison result.
11. The battery management method according to claim 10, characterized in that, The battery management method further includes: Receive the system battery information sent by the data management terminal when it determines that there is an abnormality in the battery status information; Update the battery storage and display information to the system battery information.
12. A battery management system, characterized in that, The battery management system includes a data management terminal and a terminal connected in communication, wherein the terminal is detachably connected to the battery; The data management terminal is used to manage the battery using the battery management method as described in any one of claims 1-9, and the terminal is used to manage the battery using the battery management method as described in claim 10 or 11.