Battery protection method and terminal device

Abstract

The present application provides a battery protection method and a terminal device. The method comprises: acquiring a usage parameter of a battery when the terminal device is in use; on the basis of the usage parameter, determining a usage state of the battery; when the usage state of the battery is a first usage state, the value of a protection parameter of the battery remaining unchanged, and when the usage state of the battery is a second usage state, increasing the value of the protection parameter, the protection parameter comprising one or more of a charging starting parameter and a shutdown parameter; and on the basis of the value of the protection parameter, performing an operation related to protection of the battery, so that the terminal device can perform personalized protection on the battery according to usage habits of different users, thereby prolonging the service life of the battery as much as possible and reducing the safety risk of the battery.

Description

Methods and terminal devices for protecting batteries

[0001] This application claims priority to Chinese Patent Application No. 202410918641.9, filed on July 8, 2024, entitled "Method and Terminal Device for Protecting a Battery", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of battery technology for terminal devices, and more particularly to a method for protecting batteries and a terminal device. Background Technology

[0003] With the development of battery technology, the demand for battery protection is also increasing. Taking silicon anode batteries as an example, under the same conditions, silicon anode batteries have a larger storage capacity than graphite anode batteries. For instance, a 2300mAh ordinary graphite anode battery, after replacing its anode material with silicon, can increase its capacity by approximately 140mAh, a capacity gain of 6.1%. Furthermore, silicon anode batteries can achieve lower discharge voltages. Therefore, in recent years, to improve the battery capacity of terminal devices, graphite anode batteries have been gradually replaced by silicon anode batteries. However, if silicon anode batteries are frequently subjected to low voltage, due to their electrochemical characteristics, they are prone to swelling and bulging, leading to a decrease in maximum capacity, affecting battery life, and also posing battery safety risks.

[0004] Therefore, there is a need for a method to protect batteries in order to extend the battery life of terminal devices as much as possible and reduce the safety risks of batteries in terminal devices. Summary of the Invention

[0005] This application provides a method and terminal device for protecting batteries. The method protects batteries according to their usage status, thereby achieving personalized protection for batteries of different terminal devices or different user terminal devices, extending the battery life of terminal devices as much as possible, and reducing the safety risks of batteries in terminal devices.

[0006] Firstly, this application provides a method for protecting the battery of a terminal device. The terminal device can be a battery-powered electronic device, such as a mobile phone, tablet computer, wearable device, in-vehicle device, augmented reality (AR) / virtual reality (VR) device, laptop computer, ultra-mobile personal computer (UMPC), netbook, personal digital assistant (PDA), etc. It can also be a smart home device, smart city device, automobile, etc., equipped with battery-powered electronic devices, or a battery-powered electric vehicle, electric car, etc. The method includes: acquiring battery usage parameters when the terminal device is in use; determining the battery's usage state based on the value of the usage parameters; when the battery's usage state is a first usage state, the value of the battery protection parameter remains unchanged; when the battery's usage state is a second usage state, the value of the protection parameter is increased. The protection parameter includes one or more of charging parameters and power-off parameters; and performing operations related to battery protection based on the value of the protection parameter. This enables the terminal device to provide personalized battery protection for different users' usage habits, effectively extending battery life and reducing battery safety risks.

[0007] In one possible implementation, the above-mentioned usage parameters include one or any combination of the following: voltage, temperature, and charge, to determine the battery's usage status by any or any combination of the battery's voltage, temperature, and charge during use, and to determine the protection parameter values ​​and protect the battery accordingly.

[0008] In one possible implementation, obtaining the battery usage parameters when the terminal device is in use includes: obtaining the battery usage parameters when the terminal device starts charging. Determining the battery usage state based on the usage parameters includes: determining the battery usage state based on the interval to which the previously obtained usage parameter values ​​belong and the cumulative number of charges corresponding to that interval; the first usage state is the battery state when the value determined by the interval to which the usage parameter values ​​belong and the cumulative number of charges corresponding to that interval falls within a first threshold range, the first threshold range corresponding to the current value of the protection parameter; the second usage state is the battery state when the value determined by the interval to which the usage parameter values ​​belong and the cumulative number of charges corresponding to that interval falls within a second threshold range, the second threshold range being higher than the first threshold range, i.e., the lower limit of the second threshold range is greater than or equal to the upper limit of the first threshold range (as shown in Table 2).

[0009] In one possible implementation, when the terminal device begins charging, it acquires the battery's usage parameters, including: acquiring the battery's usage parameters when the value of the battery's usage parameters is lower than the previously determined starting charging parameter value. Compared to acquiring the terminal's usage parameters and determining protection parameters for each charge, this method extends battery life while reducing the processing load on the terminal device, improving its processing speed, and enhancing the user experience.

[0010] In one possible implementation, the range to which the values ​​of the aforementioned usage parameters belong is determined by the values ​​of the aforementioned usage parameters obtained in each iteration and the type of the aforementioned usage parameters. For example, when the usage parameters include voltage and temperature, then the types of usage parameters include voltage and temperature, and correspondingly, a value range for voltage and a value range for temperature are preset. When determining the range, it can be first determined whether the range to which the value of the usage parameter belongs is a value range for voltage or a value range for temperature, and then it can be determined which specific range within the voltage or temperature value range it belongs to. When the usage parameters include charge and temperature, or voltage, charge and temperature, the method for determining the range is similar. This method can further improve the battery protection performance by obtaining the values ​​of multiple types of usage parameters or multiple usage parameters.

[0011] In one possible implementation, the value determined by the interval to which the value of the aforementioned usage parameter belongs and the cumulative number of charging cycles corresponding to that interval is based on the formula Y = α × C. β The cumulative usage score Y for this interval is obtained, where α and β are the weights of this interval, and C is the cumulative number of charging times for this interval.

[0012] In one possible implementation, the aforementioned usage parameter is current. Obtaining the battery usage parameter when the terminal device is in use includes: when the terminal device is continuously discharging, and the discharge reaches a preset duration, obtaining the battery current value. Determining the battery's usage state based on this usage parameter includes: determining the battery's usage state based on the battery current value, thereby providing more ways to protect the battery.

[0013] In one possible implementation, the aforementioned usage parameter is current. Obtaining the battery usage parameters during terminal device use includes: when the terminal device is continuously discharging, obtaining the battery current value after the discharge has reached a preset duration. Determining the battery's usage status based on the intervals to which the previously obtained usage parameter values ​​belong and the corresponding cumulative number of charges within those intervals includes: determining the battery's usage status based on the intervals to which the previously obtained usage parameter values ​​belong and the corresponding cumulative number of charges, as well as based on the current value, thereby further refining and improving battery protection.

[0014] In one possible implementation, the above-mentioned operation related to battery protection is performed based on the value of the protection parameter, including: during the discharge process of the terminal device, when the voltage or charge value of the battery is greater than the value of the charging parameter, in response to the user's operation of opening a preset interface, displaying information related to battery safety, so that the user can perceive the battery's usage status, thereby helping to cultivate better usage habits and further extend battery life and reduce safety risks.

[0015] In one possible implementation, the above-mentioned display of battery safety-related information includes: displaying the value of the above-mentioned starting charge parameter or a value related to the above-mentioned starting charge parameter to prompt the user to charge the terminal device before the battery power drops to the value of the starting charge parameter, thereby achieving shallow charging, effectively extending battery life and reducing safety risks.

[0016] In one possible implementation, the aforementioned display of battery safety-related information further includes: displaying one or more of the battery's overuse count and maximum capacity value. The overuse count is determined by the number of times the battery is charged when the value of the aforementioned usage parameter is lower than the value of the aforementioned initial charge parameter. The maximum capacity value is negatively correlated with the value of the aforementioned protection parameter. By displaying the battery's overuse count and maximum capacity value, users' awareness of battery protection can be improved, encouraging them to more actively implement shallow charging and discharging, thereby further extending battery life and reducing safety risks.

[0017] In one possible implementation, based on the current value of the protection parameters, the above-mentioned operations related to battery protection are performed, including: prompting the user to charge when the battery voltage or charge drops to the value of the charging start parameter; and shutting down the device when the battery voltage or charge drops to the value of the shutdown parameter. This method provides forced protection for the battery when the user is unable to perform shallow charging and discharging, thereby extending battery life and reducing safety risks.

[0018] In a second aspect, this application provides a terminal device, including: a processor and a memory, the memory being used to store computer program code, and when the memory runs the computer program code, the terminal device executes the method described in any of the first aspects above.

[0019] Thirdly, this application provides a computer-readable storage medium storing a computer program that, when run on a computer, causes the computer to perform the method described in any of the first aspects above. Attached Figure Description

[0020] To more clearly illustrate the technical solutions of the embodiments of this application, the drawings used in the embodiments will be briefly introduced below. Obviously, the 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.

[0021] Figures 1A, 1B, and 1C are schematic diagrams showing the battery charge level in a battery protection method;

[0022] Figure 2 is a schematic diagram showing the relationship between battery voltage and charge.

[0023] Figure 3A is a schematic flowchart of a battery protection method provided in an embodiment of this application;

[0024] Figure 3B is a schematic diagram of the usage state of the battery protection method provided in the embodiments of this application;

[0025] Figure 3C is a schematic diagram showing the relationship between protection parameters, current battery voltage / charge, and terminal device operation in the battery protection method provided in the embodiments of this application.

[0026] Figure 3D is a schematic diagram of a method for protecting the battery provided in this application, in which the user is prompted to charge.

[0027] Figures 4A1 and 4A2 are schematic diagrams of a user opening a preset interface in the battery protection method provided in the embodiments of this application;

[0028] Figures 4B1 and 4B2 are schematic diagrams of another operation in which the user opens a preset interface in the battery protection method provided in the embodiments of this application;

[0029] Figures 4C1 and 4C2 are schematic diagrams of two other operations in the battery protection method provided in the embodiments of this application, in which the user opens a preset interface;

[0030] Figure 4D1 is a schematic diagram of a preset interface shown in the battery protection method provided in the embodiment of this application;

[0031] Figure 4D2 is a schematic diagram of another preset interface shown in the battery protection method provided in the embodiments of this application;

[0032] Figure 5 is a flowchart illustrating another method for protecting a battery provided in an embodiment of this application;

[0033] Figure 6 is a structural schematic diagram of a terminal device 100 provided in an embodiment of this application;

[0034] Figure 7 is a schematic diagram of a battery protection system in a terminal device provided in an embodiment of this application;

[0035] Figure 8 is a schematic diagram of the software structure of a terminal device and its relationship with the hardware layer provided in an embodiment of this application. Detailed Implementation

[0036] To better understand the technical solution of this application, the embodiments of this application will be described in detail below with reference to the accompanying drawings.

[0037] For terminal devices with displays, one way to protect the battery is to display the battery level (i.e., the current remaining battery percentage) on the screen. The battery level displayed on the screen (i.e., the level that the user can perceive) is the State of Charge (SOC) value. As shown in Figure 1A, the phone's battery level is currently 80%, and the filled portion of the battery icon is displayed in green, indicating to the user that the battery is fully charged and does not need to be charged or that charging should be stopped. Or, as shown in Figure 1B, the phone's battery level is currently 20%, and the filled portion of the battery icon is displayed in yellow, indicating to the user that the terminal device needs to be charged. Or, as shown in Figure 1C, the phone's battery level is currently 10%, and the filled portion of the battery icon is displayed in red, indicating to the user that the terminal device urgently needs to be charged.

[0038] In this method, the terminal device tracks and detects battery parameters such as voltage and current, estimates battery capacity, and reports the battery capacity to the display screen. Specifically, as shown in Figure 2, the terminal device presets a usable battery voltage range, such as 2.5V-4.3V, and the corresponding user-perceived capacity range is 0-100%. Furthermore, the terminal device sets charging and discharging rules. For example, when the battery capacity is 80%, according to the preset rules, the battery voltage is considered 4.3V, and the battery is safe to use; the battery icon is displayed green. When the battery capacity is 20%, according to the preset rules, the battery voltage is considered 3.0V, and the battery poses a safety risk; the battery icon is displayed yellow. When the battery capacity is 10%, according to the preset rules, the battery voltage is considered 2.8V, and the battery poses a higher safety risk; the battery icon is displayed red. When the battery capacity is 0%, according to the preset rules, the battery voltage is considered 2.5V, which may damage the battery, and the device is shut down.

[0039] However, as the terminal device is used, the battery degrades, and the actual correspondence between battery charge and battery voltage deviates from the preset correspondence; that is, the voltage corresponding to the same amount of charge becomes higher. As shown in Figure 2, the preset correspondence, or initially, is that 100% battery charge corresponds to a battery voltage of 4.5V, 80% to 4.3V, 20% to 3V, and 10% to 2.5V. After a period of use, when the terminal device's battery charge is 100%, the actual battery voltage becomes 4.7V; when the charge is 80%, the actual battery voltage becomes 4.36V; when the charge is 20%, the actual battery voltage becomes 3.3V; and when the charge is 10%, the actual battery voltage becomes 2.58V.

[0040] However, the terminal device still follows preset rules and relationships, prompting the user to charge or shut down when the battery voltage reaches a preset value. For example, if the battery voltage is 3V, the preset relationship assumes the battery level is 20% and prompts the user to charge the terminal device, when the actual battery level is only 18%. This causes the user to frequently charge the battery when it is only 18%, resulting in the battery being discharged too low. This can easily damage the active materials on the battery electrodes, causing the battery to lose its responsiveness and shorten its lifespan.

[0041] To extend battery life as much as possible and reduce battery safety risks, this application provides another method for protecting the battery. As shown in Figure 3A, the method includes:

[0042] Step 31. Obtain one or more of the following: battery usage parameters when the terminal device starts charging or battery usage parameters when the terminal device is discharging.

[0043] In this embodiment, the battery usage parameters at the start of charging of the terminal device may include any one or any combination of voltage, capacity, and temperature. The battery usage parameters during discharging of the terminal device may include current, etc. The terminal device can read the battery current value after continuous discharging for a certain period of time to determine the battery's usage status.

[0044] Step 32. Determine the battery's usage status based on the value of this usage parameter.

[0045] For example, the status parameters can be determined first based on the values ​​of the usage parameters, and then the usage status can be determined from the status parameters.

[0046] When the value of the determined state parameter does not exceed the preset value compared with the current value of the state parameter, the battery usage state is determined to be the first usage state; when the value of the determined state parameter exceeds the preset value compared with the current value of the state parameter, the battery usage state is determined to be the second usage state.

[0047] Another feasible approach is to pre-set multiple threshold ranges based on the battery's usage parameters and state parameters during the experiment. When the threshold range to which the determined state parameter value belongs is the same as the threshold range to which the current state parameter value belongs, the battery's usage state is determined to be the first usage state; when the threshold range to which the determined state parameter value belongs is different from the threshold range to which the current state parameter value belongs, the battery's usage state is determined to be the second usage state. As shown in Figure 3B, n threshold ranges 1-n are pre-set. Assuming the current state parameter value belongs to threshold range m, when the determined state parameter value also belongs to threshold range m, the battery's usage state is determined to be the first usage state; when the determined state parameter value belongs to threshold range m+1, the battery's usage state is determined to be the second usage state.

[0048] Furthermore, the terminal device can pre-set the correspondence between threshold ranges and protection parameters. As shown in Figure 3B, different threshold ranges correspond to different levels of protection parameter values. In Figure 3B, 1 to n are the threshold range numbers, and 1 to N are the level or sequence numbers of the protection parameter values. The values ​​of the threshold ranges 1 to n increase sequentially, and the values ​​of the protection parameters 1 to N also increase sequentially accordingly. For example, when the protection parameter is a charging parameter, values ​​1 to N represent different charging parameter values, which increase sequentially. When the protection parameter is a shutdown parameter, values ​​1 to N represent different shutdown parameter values, which increase sequentially. When the protection parameter includes both charging and shutdown parameters, each value from 1 to N includes both the charging parameter value and the shutdown parameter value. The charging parameter value and the shutdown parameter value from 1 to N can increase sequentially, or in other words, the charging parameter value from 1 to N increases sequentially, and the shutdown parameter value from 1 to N also increases sequentially; that is, different charging parameter values ​​correspond to different shutdown parameter values. Optionally, when the protection parameters include charging parameters and shutdown parameters, the overall trend of the values ​​of the charging parameters and shutdown parameters from 1 to N is increasing, but there are cases where the values ​​within adjacent levels or numbers remain unchanged. In other words, there are cases where different charging parameter values ​​correspond to the same shutdown parameter value, or the same charging parameter value corresponds to different shutdown parameter values, etc. For example, the charging parameter value in value M+1 is greater than the charging parameter value in value M, but the shutdown parameter value in value M+1 is equal to the shutdown parameter value in value M, or the charging parameter value in value M+1 is equal to the charging parameter value in value M, but the shutdown parameter value in value M+1 is greater than the shutdown parameter value in value M, and so on. When the values ​​of adjacent levels or numbers of protection parameters remain unchanged, at least one protection parameter value in adjacent levels or numbers increases.

[0049] Step 33. When the battery is in the first usage state, the value of the battery protection parameter remains unchanged. This protection parameter includes one or more of the charging start parameter and the power off parameter. When the battery is in the second usage state, the value of this protection parameter is increased.

[0050] In this method, if the current protection parameter value is M, it means that the protection parameter value determined based on the battery usage parameters during the last charging of the terminal device was M, and the currently obtained battery usage parameter value is used to determine the new current protection parameter value.

[0051] The method in this embodiment can be executed periodically, that is, after each execution of step 34, step 31 is executed at the start of the next charge. Here, it is assumed that the value of the state parameter determined by the battery usage parameters obtained during the previous charge belongs to the threshold range m. If, in step 33, the value of the state parameter determined by the currently obtained battery usage parameters belongs to the threshold range m, then the current battery usage state is the first usage state, and the corresponding protection parameter value is value M. In other words, the new current protection parameter value is the same as the previously determined protection parameter value, or the protection parameter value remains unchanged. The value of the state parameter determined by the currently obtained battery usage parameters can be determined by combining the usage parameter values ​​from previous terminal device charging. This state parameter or the value represented by the threshold range can be expressed as a usage score or cumulative usage score for the terminal device battery, etc., and is not limited here.

[0052] If the value of the state parameter determined by the currently acquired battery usage parameters falls within the threshold range m+1, then the current battery usage state is the second usage state, and the corresponding protection parameter value M+1 is greater than the current protection parameter value M. Therefore, the protection parameter value is increased to the value M+1 to obtain the new current protection parameter value.

[0053] The starting charge parameter and the power-off parameter can both be voltage, or both be battery capacity, or the starting charge parameter can be battery capacity and the power-off parameter can be voltage, or the starting charge parameter can be voltage and the power-off parameter can be battery capacity. The values ​​of the starting charge parameter and the power-off parameter can be the user-perceived SOC value, or the battery voltage value or the amount of remaining charge (actual remaining battery capacity) corresponding to the SOC value.

[0054] Step 34. Based on the value of the protection parameter, perform operations related to battery protection.

[0055] When the battery is in the first usage state, the battery has a first state parameter, and the threshold range corresponding to the first usage state of the battery can be obtained based on the first state parameter.

[0056] For example, the terminal device can compare the real-time usage parameters of the battery with the current protection parameters, and perform corresponding battery protection operations based on the comparison results.

[0057] As shown in Figure 3C, when the protection parameters include the initial charging parameter, and the current battery voltage / charge value drops to the initial charging parameter value, the user can be prompted to charge. The prompting method can be as shown in Figure 3D: displaying charging information on the screen, providing a voice prompt, using vibration, or a combination of display and vibration, etc. When the protection parameters include both the initial charging parameter and the power-off parameter, and the current battery voltage / charge value is lower than the initial charging parameter but higher than the power-off parameter value, the user can continue to be prompted to charge, or the prompts can be intermittent, such as every one or two minutes, or the interval can be progressively shortened, such as three minutes for the first time, two minutes for the second, one minute for the third, etc. When the protection parameters include the power-off parameter, and the current battery voltage / charge value drops to the power-off parameter value, the electronic device (i.e., the terminal device) is powered off.

[0058] This method determines the battery's usage status and, based on that status, determines one or more of the battery's initial charging and shutdown parameters. It then protects the battery based on these parameters, allowing the terminal device to adjust the battery's voltage range according to its operating conditions. This is equivalent to protecting the terminal device's battery based on the user's usage habits, replacing the general protection strategy of previous methods with a one-person-one-device-one-protection approach. This allows the terminal device to provide personalized battery protection for different users, extending battery life and reducing battery safety risks. For example, for user A, who has a habit of shallow charging and discharging, and user B, who has a habit of overcharging and over-discharging, under the same usage time, user B's terminal device may have higher initial charging or shutdown parameters than user A's, effectively extending battery life and reducing battery safety risks.

[0059] As shown in Figure 3C, when the current voltage / charge value of the battery is greater than the starting charge parameter value, the electronic device can display battery safety-related information in response to the user opening a preset interface. Optionally, when the current voltage / charge value of the battery is equal to or less than the starting charge parameter value, and greater than the power-off parameter value, the electronic device can display battery safety-related information in response to the user opening a preset interface.

[0060] As shown in Figure 4A1, the user opens the preset interface by clicking the settings icon on the phone's main screen. The device then responds by opening the settings interface. This settings interface displays the "Battery Safety" option, which links to the "Battery Safety" interface, as shown in Figure 4A2. The user then clicks the "Battery Safety" option. This "Battery Safety" interface is an example of a preset interface, not a limitation. For example, the preset interface could also be described as a "Battery Health" interface, etc.

[0061] Another way for users to open the preset interface is as shown in Figure 4B1: pull down from the top of the terminal device's display screen. In response, the terminal device displays an icon linking to the "Battery Safety" interface, as shown in Figure 4B2. Then, as shown in Figure 4A2, the user clicks the "Battery Safety" icon.

[0062] Optionally, the user can open the preset interface by making a set gesture on the display screen or operation interface of the terminal device, such as drawing a clockwise circle on the phone screen as shown in Figure 4C1, or drawing an S-shape on the phone screen as shown in Figure 4C2, etc.

[0063] After the terminal device responds to the user's above operation, the preset interface displayed can be shown as Figure 4D1. The "Battery Safety" interface prompts the user to charge when the battery level is 28%. 28% battery level can be the value of the starting charge parameter, or it can be calculated from the starting charge parameter value. For example, if the starting charge parameter value is a charge quantity value, this charge quantity value can be converted to the 28% battery level displayed on the preset interface. The preset interface displayed by the terminal device in response to the user's above operation can also be shown as Figure 4D2, described as the "Battery Health" interface. This interface displays the battery's "maximum capacity" value, the number of times the battery has been overused, and the recommended charging time when the battery level reaches ×%. The "maximum capacity" is the battery capacity relative to a new battery (or the battery's initial capacity), and its value is the percentage of the battery's current capacity compared to its capacity before use (i.e., the initial capacity). As usage time and battery cycle count increase, the battery capacity will gradually decrease. Therefore, the battery's maximum capacity value will also gradually decrease. Furthermore, overuse of the battery will accelerate the reduction of battery capacity, causing the maximum capacity of the battery to decay faster. Excessive battery usage count refers to the number of times the battery is charged when its voltage or charge level is below the initial charging parameter. For example, if the current initial charging parameter is 3.0V (equivalent to 20% charge), and the user charges the terminal device when the current battery voltage is 2.8V or the charge level is 18%, this charge will be counted as an excessive usage count. By displaying the excessive usage count, maximum capacity, and recommended initial charging value (i.e., the initial charging parameter value or a value converted from the initial charging parameter) on a preset interface, the terminal device helps cultivate good user habits, thereby further extending battery life and reducing battery safety risks.

[0064] Optionally, the default interface may not display "maximum capacity" or excessive usage count, which can also effectively reduce the number of times the user overuses the battery, thereby further extending battery life and reducing battery safety risks.

[0065] The solution provided in the above embodiments focuses on the battery's usage parameters such as charge / voltage at the start of each charging cycle to assess the battery's discharge state. It's not intended to predict user habits, but rather to cumulatively record the damage caused by user behavior to the battery, preventing over-discharge. Furthermore, even if user habits change, the user's cumulative usage score continuously accumulates, and when the score reaches a certain level, the battery's discharge cutoff voltage (shutdown voltage / charge) and start-up charging voltage / charge are increased to protect the battery, thus adapting to the irreversible damage and fundamentally solving the risk of over-discharge.

[0066] Figure 5 is a flowchart illustrating another battery protection method provided in an embodiment of this application. As shown in Figure 5, after the terminal device is powered on and put into use, the following steps are performed:

[0067] Step 51. Obtain the current battery usage parameters and the current charging parameters.

[0068] Step 52. If the current battery usage parameters are equal to or less than the starting charging parameters, proceed to step 53; otherwise, proceed to step 58.

[0069] In some implementations, when the battery's usage parameters are equal to or less than the initial charging parameters, the terminal device can display a pop-up window suggesting that charging is urgently needed.

[0070] Step 53. If the user starts charging the battery, proceed to step 54; otherwise, proceed to step 57.

[0071] Step 54. Record and store the battery's usage parameters at this time (i.e., when charging begins or starts). These parameters include voltage and charge.

[0072] This step records and stores the battery's usage parameters at the start of charging when the battery level is below the initial charging parameter value. For example, if the initial charging parameter value is 5% battery level, and charging begins when the battery level is 8%, the battery's behavior data at that time will not be recorded and stored; however, if the initial charging parameter value rises to 10% battery level, and charging begins when the battery level is 8%, then the battery's behavior data at that time will be recorded and stored.

[0073] Optionally, the terminal device can also persistently store the battery's usage parameters (charge, voltage, temperature, etc.) at the start of each charge (including charging when the battery level is greater than the initial charging parameter), and count the number of charges occurring in each condition interval (i.e., the aforementioned preset interval) to further improve the battery protection performance of the terminal device. In this case, the trigger condition for recording and storing the usage parameters in this step is user charging. That is, regardless of whether the user is charging when the battery usage parameters are lower than, equal to, or higher than the initial charging parameter, as long as charging starts, the terminal device will record and store the battery's usage parameters at this time, and then execute steps 55 and 56.

[0074] Step 55. Obtain the status parameters based on the stored usage parameters.

[0075] In this step, since the trigger condition for storing usage parameters is the user's charging behavior when the battery usage parameters are equal to or less than the initial charging parameters, this reflects the user's behavioral habits to some extent. Therefore, the stored usage parameters can also be called behavioral data. The terminal device can calculate the corresponding status parameter values ​​based on the stored usage parameters and their weights. The value of the status parameter can be regarded as the user's battery usage behavior score (i.e., cumulative usage score), and the threshold range to which the status parameter value belongs can be regarded as the user's behavior level.

[0076] For example, if the usage parameters stored in step 54 are voltage and power, the terminal device first determines which range the voltage and power values ​​belong to, and then increments the corresponding number by 1. The range of the usage parameters can be preset.

[0077] Table 1

[0078] For example, as shown in Table 1, the preset battery levels are 0%–1%, 1%–2%, 2%–3%, and 3%–4%, and the preset voltage levels are 0–2.8V, 4.0–4.45V, and 4.45–4.65V. The number of times each level corresponds to is the number of times the battery has been charged (i.e., charged when the battery level is lower than the initial charging parameter value) up to the current step 54. For example, 2 times for 0%–1% means charging twice when the battery level is 0%–1%, and 20 times for 1%–2% means charging 20 times when the battery level is 1%–2%. The same applies to the other levels. α and β are the weights. α and β differ for different levels; as shown in Table 1, the lower the battery level, the larger α and β are.

[0079] If the battery level stored in step 54 falls within the range of "3% to 4% battery level", the corresponding count for that range is incremented by 1, resulting in a new current charging count of 13. Similarly, if the voltage value stored in step 54 falls within the range of "4.45 to 4.65V", the corresponding count for that range is incremented by 1, resulting in a new current charging count of 2. Then, according to the formula Y = α × C... β Obtain the current state parameters of the battery. Specifically, first calculate the score for each interval, then add the scores of each interval to obtain the current cumulative score: Y1 (score for 0%–1% battery capacity) + Y2 (score for 1%–2% battery capacity) + Y3 (score for 2%–3% battery capacity) + Y4 (score for 3%–4% battery capacity) + Y5 (score for 0–2.8V voltage) + Y6 (score for 4.0–4.45V voltage) + Y7 (score for 4.45–4.65V voltage) = 1.1 × 2 1.3 +1.1×20 1.1 +0.6×3 1.1 +0.6×(12+1) 0.8 +1.1×2 1.3 +1.1×50 1.3 +1.1×(1+1) 1.4 =217.05.

[0080] Step 56. Determine the protection parameters based on the status parameters. For example, the terminal device can determine the protection parameters corresponding to the status parameters obtained in step 55 based on a preset mapping table between the threshold range of status parameters and protection parameters.

[0081] Table 2 Mapping Relationship Table

[0082] For example, as shown in Table 2, assuming the current state parameter is 217.05, the corresponding threshold range is 150–300. The larger the value of the state parameter, the less beneficial the user's behavior is to battery protection. As the threshold range increases, the value of the protection parameter tends to increase as well.

[0083] If the threshold range of the currently obtained state parameter 217.05 is greater than the threshold range of the previously obtained state parameter, meaning the battery's usage state is the second usage state, then a new value for the current protection parameter is obtained, corresponding to the protection parameter values ​​for the threshold range 150-300: recommended starting charging voltage 3.2V, recommended starting charging amount 11%, and shutdown voltage 2.9V. If the threshold range of the currently obtained state parameter 217.05 is the same as the threshold range of the previously obtained state parameter, meaning the battery's usage state is the first usage state, then the value of the current protection parameter remains unchanged. For example, the cumulative score from the previous usage = 1.1 × 2 1.3+1.1×20 1.1 +0.6×3 1.1 +0.6×12 0.8 +1.1×2 1.3 +1.1×50 1.3 +1.1×1 1.4 =214.957, which also falls within the threshold range of 150 to 300. Therefore, the current protection parameter value remains unchanged.

[0084] If a new value for the current protection parameter is determined, the current protection parameter value is updated to the new protection parameter value. For example, the recommended starting voltage is updated to 3.2V, the recommended starting charge is updated to 11%, and the shutdown voltage is updated to 2.9V.

[0085] Step 57. The terminal device prompts the user to charge. When the battery's usage parameters drop to the shutdown parameters, such as when the battery voltage drops to the shutdown voltage, or when the battery level drops to the level corresponding to the shutdown voltage, the terminal device shuts down.

[0086] Step 58. Detect user clicks on preset interfaces.

[0087] In some implementations, the terminal device can also recognize the user's intention to open a preset interface by recognizing the user's voice.

[0088] In some implementations, the operation of the terminal device sensing the user's intention to open a preset interface can be performed when the battery usage parameters are equal to or less than the starting charging parameters, or when the battery is charging.

[0089] Step 59. The terminal device responds to the user's click on the preset interface, displays the current cumulative number of battery over-discharges (e.g., the number of charging times recorded in step 54), and protection parameters such as the battery initial charge level recommended to the user for charging the terminal device.

[0090] The method provided in this embodiment can also be a software process, including a low battery charging scenario (steps 54 to 56), a low battery not charging scenario (step 57), and a scenario of actively viewing battery information (steps 58 and 59).

[0091] The method provided in this embodiment stores battery usage parameters, such as voltage and charge level, when the battery is charging at the edge of its usable range. It then identifies user over-discharge behavior, enabling the terminal device to categorize user discharge behavior into different levels based on user habits, usage history, and the number of charge / discharge cycles. Different user levels are mapped to different protection parameters, such as initial charging parameters and shutdown parameters, allowing for adaptive adjustment of battery protection parameters. When battery usage parameters drop to the shutdown parameter, the terminal device shuts down. Based on user behavior data, a personalized approach is implemented for each device, effectively extending battery life and reducing battery safety risks. Furthermore, when the user accesses the terminal device's preset interface manually or via voice, they can see data such as the number of over-discharge cycles, protection parameters, including the initial charge level / voltage / temperature and the corresponding number of cycles, as well as suggested initial charge levels. When battery usage parameters, such as charge level / voltage, drop to the initial charging parameter, the terminal device automatically pops up a reminder, providing a smart battery health reminder solution for user awareness of battery protection.

[0092] Another battery protection method provided in this application differs from the previous embodiment in that the preset range of the terminal device also includes a temperature range. For example, as shown in Table 3, the preset range of the terminal device includes not only the battery's charge and voltage ranges, but also the battery's temperature range and its corresponding weights α and β.

[0093] Table 3

[0094] Accordingly, the terminal device records and stores the battery's voltage and charge at the start of charging, as well as the battery's temperature at that time. The state parameter value is calculated based on the voltage and charge values, and further calculated based on the temperature value. For example, assuming the currently stored battery temperature is 26°C, the current battery voltage is 4.5V, and the charge is 3%, then the number of times recorded in the temperature range of 25°C to 40°C, the voltage range of 4.45V to 4.65V, and the charge range of 3% to 4% are incremented by 1. The state parameter value = Y1 (score for the 0% to 1% charge range) + Y2 (score for the 1% to 2% charge range). Y1 (value) + Y2 (score for 2%–3% battery capacity) + Y3 (score for 3%–4% battery capacity) + Y4 (score for 0–2.8V voltage) + Y5 (score for 4.0–4.45V voltage) + Y6 (score for 4.45–4.65V voltage) + Y7 (score for 4.45–4.65V voltage) + Y8 (score for -20°C–0°C temperature) + Y9 (score for 0°C–25°C temperature) + Y10 (score for 25°C–40°C temperature) = 1.1 × 2 1.3 +1.1×20 1.1 +0.6×3 1.1 +0.6×(12+1)0.8 +1.1×2 1.3 +1.1×50 1.3 +1.1×(1+1) 1.4 +0.2×0 1 +0×10 0.8 +0.1×(6+1) 0.9 =217.05+0.58=217.63.

[0095] The value of the status parameter is determined by the interval to which the usage parameter value belongs and the corresponding cumulative number of charging cycles. For example, if the status parameter obtained during the nth charging cycle is 217.63, corresponding to a threshold range of 150-300 (i.e., the first threshold range), and the status parameter obtained during the (n+1)th charging cycle is 230, still within the first threshold range, then the battery usage state during the (n+1)th charging cycle is the first usage state, and the value of the protection parameter remains unchanged. As another example, if the status parameter obtained during the nth charging cycle is 340, corresponding to a threshold range of 300-350 (i.e., the first threshold range), and the status parameter obtained during the (n+1)th charging cycle is 360, corresponding to a threshold range of 350-500, which is higher than the first threshold range of 300-350, i.e., it falls within the second threshold range, then the battery usage state during the (n+1)th charging cycle is the second usage state, and the value of the protection parameter is increased.

[0096] In some implementations, the terminal device may also obtain the status parameters based solely on any one of the following usage parameters: voltage, battery level, and temperature. Accordingly, when the terminal device begins charging, it may store only the battery voltage value, or only the battery level value, or even the battery temperature value.

[0097] In some implementations, the terminal device's preset mapping table also includes the corresponding power level when the device is off.

[0098] In the above embodiments, the values ​​of the state parameters can also be obtained through formulas. We obtain . Where n is the total number of intervals using parameters, γ i C represents the weight of the i-th interval using parameters. i The number of times to charge for the i-th interval using parameters.

[0099] In some implementations, the battery's usage status is determined based on the current value. This can be similar to the above embodiments, where the battery's status parameters are calculated based on the current value, and the battery's usage status is determined based on the status parameters.

[0100] Figure 6 is a schematic diagram of the structure of a terminal device 100 provided in an embodiment of this application. As shown in Figure 6, the terminal device 100 includes a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, a fuel gauge 143, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker, a receiver, a microphone, a headphone jack, a sensor module 180, buttons 190, a motor 191, an indicator 192, a camera 193, a display screen 194, and a subscriber identification module (SIM) card interface 195, etc.

[0101] The sensor module 180 includes a pressure sensor, a gyroscope sensor, a barometric pressure sensor, a magnetic sensor, an accelerometer, a distance sensor, a proximity sensor, a fingerprint sensor, a temperature sensor, a touch sensor, an ambient light sensor, and a bone conduction sensor. The temperature sensor can be used to obtain the temperature of the battery 142. The touch sensor, also known as a "touch panel," is used to detect touch operations applied to or near it, and transmits the detected touch operations to the application processor to determine the type of touch event. The touch sensor can also provide visual output related to touch operations through the display screen 194. The touch sensor can also form a touchscreen (i.e., a "touchscreen") with the display screen 194. Optionally, the touch sensor is located on the surface of the terminal device 100 at a different position than the display screen 194. In this embodiment, the terminal device 100 can use the touch sensor to detect user actions such as clicking and swiping on the display screen 194, and accordingly provide the user with information prompts regarding battery usage and / or status and / or safety.

[0102] Processor 110 may include one or more processing units, such as application processors (APs), modem processors, graphics processing units (GPUs), image signal processors (ISPs), controllers, video codecs, digital signal processors (DSPs), baseband processors, and / or neural network processing units (NPUs). Different processing units may be independent devices or integrated into one or more processors. The controller can generate operation control signals based on instruction opcodes and timing signals to control the operation of each module or component. Terminal device 100 implements display functions through GPUs, display screens 194, and application processors. The GPU is a microprocessor for image processing, connected to the display screen 194 and the application processor. The GPU performs mathematical and geometric calculations and is used for graphics rendering. Processor 110 may include one or more GPUs, which execute program instructions to generate or modify display information. Display screen 194, also called a display screen or screen, is used to display images, videos, etc. Display screen 194 includes a display panel. The display panel may be an OLED display panel. Optionally, the terminal device 100 may include one or N displays 194, where N is a positive integer greater than 1.

[0103] The processor 110 may further include memory for storing instructions and data. Optionally, the memory in the processor 110 is a cache memory. This memory can store instructions or data that the processor 110 has just used or that are used repeatedly. If the processor 110 needs to use the instruction or data again, it can directly retrieve it from memory, avoiding repeated access, reducing the processor 110's waiting time, and improving system efficiency.

[0104] Internal memory 121 may include one or more random access memory (RAM) and one or more non-volatile memory (NVM). The RAM may include static random-access memory (SRAM), dynamic random-access memory (DRAM), synchronous dynamic random-access memory (SDRAM), double data rate synchronous dynamic random-access memory (DDR SDRAM, such as fifth-generation DDR SDRAM, generally referred to as DDR5 SDRAM), etc. The NVM may include disk storage devices and flash memory. Flash memory can be classified according to its operating principle, including NOR FLASH, NAND FLASH, 3D NAND FLASH, etc.; according to the level of the storage cell, including single-level cell (SLC), multi-level cell (MLC), triple-level cell (TLC), quad-level cell (QLC), etc.; and according to the storage specification, including universal flash memory (UFS) and embedded multimedia card (eMMC), etc.

[0105] Random access memory (RAM) can be directly read and written by the processor 110. It can be used to store executable programs (such as machine instructions) of the operating system or other running programs, as well as user and application data. Non-volatile memory can store executable programs and user and application data, and executable programs and data can also be pre-loaded into RAM for direct read and write by the processor 110.

[0106] In this embodiment, the code implementing the battery protection method provided in this embodiment can be stored in non-volatile memory. During runtime, the terminal device 100 can load the executable code stored in the non-volatile memory into random access memory.

[0107] The external memory interface 120 can be used to connect to external non-volatile memory to expand the storage capacity of the terminal device 100. The external non-volatile memory communicates with the processor 110 through the external memory interface 120 to realize data storage function.

[0108] The charging management module 140 receives charging input from the charger. The charger can be a wireless charger or a wired charger. When the charger is a wired charger, it can charge the terminal device 100 via the USB interface 130. While charging the battery 142, the charging management module 140 can also supply power to the terminal device 100 via the power management module 141. The power management module 141 is connected to the battery 142, the charging management module 140, and the processor 110, and is used to receive input from the battery 142 and / or the charging management module 140 to supply power to the processor 110, internal memory 121, display screen 194, camera 193, and wireless communication module 160, etc. Optionally, the power management module 141 and the charging management module 140 are housed in the same device. The fuel gauge 143 is connected to the battery 142 and the processor 110 and is used to monitor at least one of the voltage, temperature, charge, and current of the battery 142, so that the processor 110 can protect the battery 142 accordingly. Optionally, the fuel gauge 143 is replaced by a coulomb counter.

[0109] The audio module 170 is used to convert digital audio information into analog audio signals for output, and also to convert analog audio input into digital audio signals. The speaker, also called a "loudspeaker," is used to convert audio electrical signals into sound signals. The terminal device 100 can play sound through the speaker. The receiver, also called a "handpiece," is used to convert audio electrical signals into sound signals. When the terminal device 100 plays sound, the user can listen to the voice by bringing the receiver close to their ear. The headphone jack is used to connect wired or wireless headphones. The terminal device 100 can implement audio functions through the audio module 170, speaker, receiver, microphone, headphone jack, and application processor. For example, it can provide sound or voice prompts to the user about charging.

[0110] It is understood that the components illustrated in the terminal device 100 diagram can be implemented in hardware, software, or a combination of both. Furthermore, the structure of the terminal device 100 illustrated in this embodiment does not constitute a specific limitation on the terminal device of this application. The terminal device of this application may include more or fewer components than illustrated, or combine certain components, or split certain components, or have different component arrangements. For example, when the terminal device of this application is a laptop computer, the mobile communication module 150, receiver, motor 191, SIM card interface 195, pressure sensor, gyroscope sensor, and barometric pressure sensor shown in Figure 6 can be omitted. Similarly, when the terminal device of this application is an electrical appliance such as a reading pen or electric hair clipper, the mobile communication module 150, wireless communication module 160, display screen 194, external memory interface, and sensor module 180 can be omitted. Furthermore, when the terminal device of this application is an electric vehicle, it further includes a power drive component, frame, wheels, etc.

[0111] The battery protection system in the terminal device provided in this application embodiment is shown in Figure 7, and includes a physical unit and a software module.

[0112] The physical unit includes a battery, a fuel gauge, or a coulomb meter. The fuel gauge or coulomb meter is used to acquire the battery's voltage, current, and capacity data.

[0113] The software modules include a UI display module, a smart notification module, a data recording and storage module, a user processing module, and a battery management and control module. The data recording and storage module reads and records user charging and discharging data obtained from a fuel gauge or coulomb counter. The user processing module calculates the degree of damage to the battery caused by user behavior (reflected through cumulative scores) based on the data stored in the data recording and storage module, classifies users into different levels, and determines the current battery protection parameters. The smart notification module prompts the user to charge in a timely manner based on the values ​​determined by the user processing module, including generating prompt messages and sending them to the UI display module for display. The UI display module displays battery data on the user interface, such as the number of charging cycles, the value of the initial charging parameter, and prompts for charging. The battery management and control module controls battery usage based on the usable range determined by the user processing module; for example, when the current battery usage parameter value is lower than the shutdown parameter value determined by the user processing module, it controls the battery to stop working, shutting down the terminal device. Optionally, the software modules further include a settings application for users to access a preset interface and view battery safety-related information.

[0114] For example, at the start of each charge, the data recording and storage module persistently stores the current power level, voltage, and temperature, and counts the number of occurrences for each condition interval. The user processing module performs mathematical processing on the number of occurrences under different conditions based on the battery lifecycle to obtain a user behavior score, classifies user behavior into different levels, corresponds to different battery discharge strategies, and determines battery protection parameters based on the user level: the battery's shutdown voltage / shutdown power level, and the recommended starting charge level / voltage to avoid additional damage to the battery.

[0115] When the battery voltage / charge drops to the shutdown voltage / charge level, the battery management control module shuts down the terminal device to prevent over-discharge. When the battery voltage / charge reaches the recommended initial charging level / voltage, the user intelligent notification module automatically and intelligently prompts the user to charge, guiding the user to proactively avoid prolonged periods in a low-voltage state. By intelligently identifying the user's deep discharge behavior, the system intelligently and accurately manages the battery's usable voltage range, shifting from a general strategy to a personalized approach for each user and device.

[0116] Figure 8 is a schematic diagram of the software structure of a terminal device and its relationship with the hardware layer provided in an embodiment of this application.

[0117] As shown in Figure 8, in this embodiment of the application, the hardware layer includes a battery, a temperature sensor, and a fuel gauge / coulomb counter.

[0118] The software architecture is a layered architecture of the Android system, which includes, from top to bottom, the application layer, the application framework layer, the native layer, and the hardware abstraction layer (HAL). The layers communicate with each other through software interfaces.

[0119] The application layer may include a series of application packages. These application packages may include applications such as camera, gallery, calendar, map, navigation, WLAN, Bluetooth, music, video, and SMS. In this embodiment, the application layer includes a user processing module, a smart notification module, a UI display module, and a settings application.

[0120] The application framework layer provides an application programming interface (API) and programming framework for applications in the application layer. The application framework layer includes some predefined functions. In this embodiment, the application framework layer includes a data recording and storage module, a power management module, and a sensor service. The power management module obtains the values ​​of the battery protection parameters from the user processing module and sends them to the battery management control module. The sensor service obtains the battery temperature through a temperature sensor and sends it to the data recording and storage module for recording and storage.

[0121] The local layer can also be called the local framework layer, local algorithm layer, or local service layer, etc.

[0122] The Hardware Abstraction Layer (HAL) is an abstract interface for the device kernel driver, used to provide application programming interfaces for accessing the underlying device to higher-level API frameworks. In this embodiment, the HAL includes a battery management control module. The battery management control module protects the battery, such as by shutting it down, based on protection parameters obtained from the power management module.

[0123] This embodiment provides a systematic solution to battery protection problems, encompassing power device management, charging software framework, and intelligent service prompts.

[0124] The solution provided in the above embodiments is particularly suitable for protecting terminal devices such as mobile phones that are powered by batteries that are not resistant to low voltage (such as silicon anode batteries). Through software means, combined with the user's usage habits and the battery's own properties, the usable voltage of the battery is dynamically adjusted. Under the premise of ensuring that the battery provides sufficient power and the user can use the mobile phone functions normally, the battery aging and swelling are slowed down, the battery life is extended, and battery safety and user experience are taken into account at the same time.

[0125] It should be understood that the embodiments described in this application are only some embodiments, and not all embodiments. Based on the embodiments in this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0126] The terminology used in the embodiments of this application is for the purpose of describing particular embodiments only and is not intended to be limiting of this application. The singular forms “a,” “the,” and “the” used in the embodiments of this application and the appended claims are also intended to include the plural forms unless the context clearly indicates otherwise.

[0127] It should be understood that the term "and / or" used in this article is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. Additionally, the character " / " in this article generally indicates that the preceding and following related objects have an "or" relationship.

[0128] In a specific implementation, the present invention also provides a computer storage medium, wherein the computer storage medium may store a program, which, when executed, may include some or all of the steps in the various embodiments of the simulation scene generation method provided by the present invention. The storage medium may be a magnetic disk, optical disk, read-only memory (ROM), or random access memory (RAM), etc.

[0129] In a specific implementation, the present invention also provides a computer program product, wherein the computer program product includes executable instructions, which, when executed on a computer, cause the computer to perform some or all of the steps in various embodiments of the simulation scene generation method provided by the present invention.

[0130] Those skilled in the art will clearly understand that the techniques in the embodiments of the present invention can be implemented using software plus necessary general-purpose hardware platforms. Based on this understanding, the technical solutions in the embodiments of the present invention, or the parts that contribute to the prior art, can be embodied in the form of a software product. This computer software product can be stored in a storage medium, such as ROM / RAM, magnetic disk, optical disk, etc., and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute the methods described in various embodiments or certain parts of the embodiments of the present invention.

[0131] The same or similar parts between the various embodiments in this specification can be referred to mutually. In particular, the device embodiments and terminal embodiments are basically similar to the method embodiments, so the description is relatively simple, and the relevant parts can be referred to the description in the method embodiments.

Claims

1. A method for protecting a battery, characterized in that, Applied to terminal devices, including: Obtain the battery usage parameters when the terminal device is in use; Based on the aforementioned usage parameters, determine the battery's usage status; When the battery is in the first usage state, the value of the battery protection parameter remains unchanged. When the battery is in the second usage state, the value of the protection parameter is increased. The protection parameter includes one or more of the charging start parameter and the power off parameter. Based on the value of the protection parameter, perform operations related to protecting the battery.

2. The method according to claim 1, characterized in that, The usage parameters include one or any combination of the following: voltage, temperature, and power.

3. The method according to claim 1, characterized in that, The step of obtaining the battery usage parameters of the terminal device during use includes: When the terminal device starts charging, it acquires the battery's usage parameters. Determining the battery's usage status based on the usage parameters includes: The battery's usage state is determined based on the interval to which the previously obtained usage parameter values ​​belong and the cumulative number of charges corresponding to the intervals. The first usage state is the battery's state when the value determined by the interval to which the usage parameter values ​​belong and the cumulative number of charges corresponding to the intervals falls within a first threshold range, where the first threshold range corresponds to the current value of the protection parameter. The second usage state is the battery's state when the value determined by the interval to which the usage parameter values ​​belong and the cumulative number of charges corresponding to the intervals falls within a second threshold range, where the second threshold range is higher than the first threshold range.

4. The method according to claim 3, characterized in that, When the terminal device starts charging, it acquires the battery's usage parameters, including: When the value of the battery's usage parameters is lower than the value of the previously determined starting charging parameters, and the terminal device starts charging, the battery's usage parameters are obtained.

5. The method according to claim 3 or 4, characterized in that, The range to which the values ​​of the usage parameters obtained in each iteration belong is determined by the values ​​of the usage parameters obtained in each iteration and the type of the usage parameters.

6. The method according to any one of claims 3 to 5, characterized in that, The value determined by the interval to which the value of the usage parameter belongs and the cumulative number of charging times corresponding to the interval is based on the formula Y = α × C. β The obtained cumulative score Y for the interval is given by Y, where α and β are the weights of the interval, and C is the cumulative number of charging times for the interval.

7. The method according to any one of claims 1 to 6, characterized in that, The step of performing operations related to protecting the battery based on the value of the protection parameter includes: During the discharge process of the terminal device, when the voltage or charge value of the battery is greater than the value of the charging parameter, in response to the user's operation of opening a preset interface, information related to the safety of the battery is displayed.

8. The method according to claim 7, characterized in that, The information displayed is related to the safety of the battery, including: Display the value of the starting charge parameter or a value related to the starting charge parameter.

9. The method according to claim 7 or 8, characterized in that, The display of information related to the safety of the battery also includes: The display shows one or more of the battery's overuse count and the battery's maximum capacity value. The overuse count is determined by the number of times the battery is charged when the value of the usage parameter is lower than the value of the initial charge parameter. The battery's maximum capacity value is negatively correlated with the value of the protection parameter.

10. The method according to any one of claims 1 to 9, characterized in that, The step of performing battery protection-related operations based on the current value of the protection parameter includes: When the voltage or charge of the battery drops to the value of the charging parameter, the user is prompted to charge. The device shuts down when the battery voltage or charge drops to the value of the shutdown parameter.

11. A terminal device, characterized in that, include: A processor and a memory, the memory being used to store computer program code, wherein when the memory runs the computer program code, the terminal device performs the method as described in any one of claims 1 to 10.

12. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when run on a computer, causes the computer to perform the method described in any one of claims 1 to 10.

Images