A method of determining a state of charge of a battery

CN117007991BActive Publication Date: 2026-10-16HUAWEI TECH CO LTD
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
CN202210457988.9
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2022-04-27
Publication Date
2026-10-16
Estimated Expiration
2042-04-27

AI Technical Summary

Technical Problem

然而,目前缺少对硅负极电池的控制方式

Benefits of technology

[0032] For details on the beneficial effects of any of the second to ninth aspects and their possible designs, please refer to the beneficial effects of the various possible designs in the first aspect above; they will not be repeated here.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN117007991B_ABST
    Figure CN117007991B_ABST
Patent Text Reader

Abstract

The application relates to the field of terminal devices and discloses a battery power state determination method, which is used for realizing mapping based on battery use data, obtaining a mapped target battery power, and thus the stability of the battery can be enhanced, and the battery can be protected. In the method, a battery protection voltage parameter is determined according to battery use data; the battery protection voltage parameter is used for changing an original voltage parameter corresponding to the battery power; a second mapping relationship between an actual battery power and a target battery power is determined according to the battery protection voltage parameter; and the target battery power is determined based on the second mapping relationship and the actual battery power of the battery. Alternatively, a corresponding relationship between an actual battery voltage and the target battery power is determined according to the battery protection voltage parameter; and the target battery power is determined based on the corresponding relationship and the actual battery voltage of the battery.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This application relates to the field of terminal devices, and more particularly to a method for determining the state of a battery. Background Technology

[0002] As terminal devices become increasingly prevalent and important in users' daily lives, the need to increase their battery storage capacity is becoming more urgent. Besides increasing battery space in the device's structure, different battery manufacturing methods can also be used to improve battery storage capacity.

[0003] Currently, most types of terminal devices use graphite as the negative electrode material in their battery manufacturing process, which offers stable performance. Another method uses silicon as the negative electrode material; silicon-based batteries, compared to graphite-based batteries, can have a larger storage capacity under the same conditions. However, there is currently a lack of control methods for silicon-based batteries. Summary of the Invention

[0004] This application provides a method for determining the state of a battery, which maps battery usage data to obtain a target battery level. This allows the target battery level to reflect not only the remaining battery power but also the battery's usage status, thereby enhancing battery stability and protecting the battery.

[0005] In a first aspect, embodiments of this application provide a method for determining the state of a battery. The method includes: determining a battery protection voltage parameter based on battery usage data; the battery usage data reflecting the battery's usage state within a preset time period, and the battery protection voltage parameter used to modify an original voltage parameter corresponding to the battery's state of charge; determining a second mapping relationship between the actual battery state of charge and a target battery state of charge based on the battery protection voltage parameter; and determining the target battery state of charge based on the second mapping relationship and the actual battery state of charge.

[0006] This method maps battery voltage to battery capacity by calculating a mapping between the target battery capacity and the actual battery capacity. Therefore, the mapped target battery capacity reflects not only the actual battery capacity but also the battery voltage. This allows for a lower target battery capacity mapping when the battery voltage is low, providing timely reminders to the user to charge and preventing the battery from remaining in a low-voltage state for extended periods. Thus, through dynamic mapping based on battery voltage and capacity, it is possible to effectively prevent the battery from operating in dangerous voltage ranges for extended periods. For example, silicon anode batteries exhibit unstable performance in low-voltage ranges; therefore, when using silicon anode batteries, the battery shutdown voltage can be increased. Alternatively, if other materials are found to have poor performance in other voltage ranges (such as high-voltage ranges), the battery can be protected and its lifespan extended by reducing the full-charge voltage.

[0007] In one possible design, determining the battery protection voltage parameter based on battery usage data includes: determining the battery protection voltage parameter corresponding to the battery usage data based on a pre-configured first mapping relationship. In this design, the mapping relationship between battery usage data and battery protection voltage parameters can be pre-configured through experiments or deep learning, and then the pre-configured first mapping relationship can be applied to determine the battery protection voltage parameter to adjust the battery voltage, allowing the battery to operate within a wider safe voltage range.

[0008] In one possible design, the pre-configured first mapping relationship can be used to reflect the correspondence between the values ​​of different battery usage data and the values ​​of different battery protection voltage parameters; alternatively, the pre-configured first mapping relationship can also be used to reflect the correspondence between the ranges of different battery usage data and the values ​​or ranges of different battery protection voltage parameters. In this design, the pre-configured first mapping relationship can be a correspondence between values, between values ​​and ranges, or between ranges. By using different mapping methods, various requirements in different application scenarios, such as accuracy requirements, can be adapted.

[0009] In one possible design, determining the second mapping relationship between the actual battery capacity and the target battery capacity based on the battery protection voltage parameter includes: determining the second mapping relationship corresponding to the battery protection voltage parameter based on a first modeling parameter; the first modeling parameter is used to indicate the correspondence between battery voltage and battery capacity. In this design, the mapping between battery voltage and battery capacity can be modeled in advance, and then the first modeling parameter can be applied to determine the correspondence between the original battery voltage and the original battery capacity, as well as the correspondence between the target battery voltage and the target battery capacity. Therefore, the mapping relationship between the actual battery capacity and the target battery capacity can be further determined through these two correspondences, thereby enabling the determination of the mapped target battery capacity.

[0010] In one possible design, the battery usage data includes one or more of the following: fully charged capacity, initial charge level at the start of charging, second charge level at the end of charging, battery usage time, and battery cycle count. In this design, the battery usage data can acquire data related to battery charging, as well as data related to battery usage, thereby allowing analysis of battery usage habits. For example, determining a user's charging habits: if a user habitually uses the battery until it is at a low charge level before charging, since the battery may experience performance instability at low voltage, the shutdown voltage can be increased to achieve a target battery charge level through mapping, preventing the user from using a battery at low voltage for extended periods.

[0011] In one possible design, before determining the battery protection voltage parameters based on battery usage data, the method further includes: receiving and responding to a preset acquisition command, acquiring and statistically analyzing the battery usage data; wherein the preset acquisition command includes, but is not limited to: detecting the terminal device being powered on; or detecting the terminal device being charged; or receiving a user operation command to activate battery optimization. In this design, various methods for acquiring battery usage data can be set according to actual scenario requirements.

[0012] In one possible design, the battery protection voltage parameters include, but are not limited to, at least one of the following parameters: a target shutdown voltage obtained by changing the original shutdown voltage included in the original voltage parameters; and a target full charge voltage obtained by changing the original full charge voltage included in the original voltage parameters. In this design, by adjusting one or a combination of the shutdown voltage and the full charge voltage, the battery operating voltage range can be adjusted, preventing the battery from operating within an unstable voltage range for extended periods.

[0013] In one possible design, the battery protection voltage parameter is indicated by, but not limited to, one of the following forms: an absolute value indicating the change; a relative value indicating the change ratio; or a target value obtained after the change.

[0014] In one possible design, obtaining the actual battery charge includes: continuously collecting battery parameters for determining the actual battery charge, or periodically collecting the battery parameters, or receiving and collecting the battery parameters in response to a request instruction; and determining the actual battery charge based on the battery parameters.

[0015] Secondly, embodiments of this application also provide a method for determining battery state of charge. In this method, a battery protection voltage parameter is determined based on battery usage data; the battery usage data reflects the battery's usage state within a preset time period, and the battery protection voltage parameter is used to change the original voltage of one or more batteries corresponding to the battery state of charge; based on the battery protection voltage parameter, a correspondence between the actual battery voltage and the target battery state of charge is determined; and based on the correspondence and the actual battery voltage, the target battery state of charge is determined.

[0016] This method modifies the mapping relationship between battery voltage and battery capacity, enabling the mapping of battery capacity based on battery voltage. Therefore, the mapped target battery capacity reflects not only the actual battery capacity but also the battery voltage. This allows for mapping a lower target battery capacity when the battery voltage is low, providing timely reminders to the user to charge and preventing the battery from remaining in a low-voltage state for extended periods. Thus, dynamic mapping based on battery voltage and capacity effectively prevents the battery from operating in dangerous voltage ranges for extended periods. For example, silicon anode batteries exhibit unstable performance in low-voltage ranges; therefore, when using silicon anode batteries, the battery shutdown voltage can be increased. Alternatively, if other materials are found to have poor performance in other voltage ranges (such as high-voltage ranges), the battery can be protected and its lifespan extended by reducing the full-charge voltage.

[0017] In one possible design, determining the battery protection voltage parameter based on battery usage data includes: determining the battery protection voltage parameter corresponding to the battery usage data based on a pre-configured first mapping relationship.

[0018] In one possible design, the pre-configured first mapping relationship is used to reflect the correspondence between the values ​​of different battery usage data and the values ​​of different battery protection voltage parameters; or, the pre-configured first mapping relationship is used to reflect the correspondence between the ranges of different battery usage data and the values ​​or ranges of different battery protection voltage parameters.

[0019] In one possible design, determining the correspondence between the actual battery voltage and the target battery capacity based on the battery protection voltage parameters includes: switching a first modeling parameter to a second modeling parameter based on a pre-configured third mapping relationship; the first modeling parameter indicates the original correspondence between battery voltage and battery capacity, and the second modeling parameter indicates the target correspondence between battery voltage and battery capacity. In this design, the pre-configuration of the mapping relationship between the battery protection voltage parameters and the modeling parameters can be achieved through experiments or deep learning. For example, different modeling parameters corresponding to different battery protection voltage parameters can be pre-stored, allowing for switching between different modeling parameters at different battery protection voltage parameters. This results in a suitable correspondence between battery voltage and battery capacity, enabling adjustment of the battery voltage and allowing the battery to operate within a wider range of safe voltage ranges.

[0020] In one possible design, the battery usage data includes, but is not limited to, one or more of the following: full charge capacity, first charge level at the start of charging, second charge level at the end of charging, battery usage time, and battery cycle count.

[0021] In one possible design, before determining the battery protection voltage parameters based on battery usage data, the method further includes: receiving and responding to a preset acquisition command, acquiring and statistically analyzing the battery usage data; wherein the preset acquisition command includes, but is not limited to: detecting the power-on of the terminal device; or detecting the charging of the terminal device; or receiving a user operation command to enable battery optimization.

[0022] In one possible design, the battery protection voltage parameters include at least one of the following parameters: a target shutdown voltage obtained by changing the original shutdown voltage included in the original voltage parameters; and a target full charge voltage obtained by changing the original full charge voltage included in the original voltage parameters.

[0023] In one possible design, the battery protection voltage parameter is indicated by, but not limited to, one of the following forms: an absolute value indicating the change; a relative value indicating the change ratio; or a target value obtained after the change.

[0024] In one possible design, obtaining the actual battery charge includes: continuously collecting battery parameters for determining the actual battery charge, or periodically collecting the battery parameters, or receiving and collecting the battery parameters in response to a request instruction; and determining the actual battery charge based on the battery parameters.

[0025] Thirdly, this application provides a terminal device comprising multiple functional modules. These multiple functional modules interact to implement the methods executed by the terminal device in any of the above aspects and their respective embodiments. The multiple functional modules can be implemented based on software, hardware, or a combination of both, and can be arbitrarily combined or divided based on specific implementations. For example, in embodiments of this application, the multiple functional modules may include a data acquisition module, a processing module, and a transceiver module. The data acquisition module can be used to acquire battery usage data, the processing module can be used to determine the battery power status as described in this application, and the transceiver module can be used to receive the actual battery power obtained by the hardware unit.

[0026] Fourthly, this application provides a terminal device, including at least one processor and at least one memory, wherein the at least one memory stores computer program instructions, and when the terminal device is running, the at least one processor executes any of the above aspects and the methods executed by the terminal device in its various embodiments.

[0027] Fifthly, this application also provides a computer-readable storage medium storing a computer program that, when executed by a computer, causes the computer to perform any of the above-described methods and the methods executed by various possible design terminal devices.

[0028] Sixthly, this application provides a computer program product comprising: a computer program (also referred to as code or instructions) that, when run, causes a computer to perform any of the above aspects and the methods for designing terminal devices thereof.

[0029] Seventhly, embodiments of this application also provide a graphical user interface (GUI) on a terminal device. The terminal device has a display screen, one or more memories, and one or more processors. The one or more processors are used to execute one or more computer programs stored in the one or more memories. The GUI includes a GUI displayed when the terminal device executes any of the above aspects and their possible designs. For example, after determining a mapped target battery level, the terminal device can display the target battery level on the GUI, such as in the upper right corner.

[0030] Eighthly, this application also provides a chip for reading a computer program stored in a memory and executing the methods described above and their possible design terminal devices.

[0031] Ninthly, this application also provides a chip system including a processor for supporting a computer device in implementing the methods executed by any of the above aspects and their respective possible design terminal devices. In one possible design, the chip system further includes a memory for storing programs and data necessary for the computer device. The chip system may be composed of chips or may include chips and other discrete devices.

[0032] For details on the beneficial effects of any of the second to ninth aspects and their possible designs, please refer to the beneficial effects of the various possible designs in the first aspect above; they will not be repeated here. Attached Figure Description

[0033] Figure 1 This is a schematic diagram of the hardware structure of a possible terminal device provided in an embodiment of this application;

[0034] Figure 2 A software architecture block diagram of a terminal device provided in an embodiment of this application;

[0035] Figure 3 A schematic diagram of the hardware structure applicable to a method for determining battery state provided in an embodiment of this application;

[0036] Figure 4 A flowchart illustrating a method for determining battery state provided in an embodiment of this application;

[0037] Figure 5 This is a schematic diagram of the display interface of a terminal device provided in an embodiment of this application;

[0038] Figure 6 Another flowchart illustrating a method for determining battery charge state provided in an embodiment of this application;

[0039] Figure 7 This is a schematic diagram of a battery power state determination device provided in an embodiment of this application. Detailed Implementation

[0040] The embodiments of this application will now be described in detail with reference to the accompanying drawings.

[0041] The technical solutions provided in this application can be applied to the field of terminal devices. Terminal devices typically require batteries to support normal operation; therefore, increasing the battery storage capacity of terminal devices is of significant research importance. On one hand, one could consider allocating more space for the battery within the terminal device to increase its volume and thus its storage capacity. However, given the hardware limitations of terminal devices, this increase in storage capacity is limited. On the other hand, one could also consider improving the battery manufacturing process to achieve a larger storage capacity for the same volume of battery.

[0042] Currently, the batteries used in terminal devices are typically lithium-ion batteries. Lithium-ion batteries are mainly composed of positive electrode materials, negative electrode materials, electrolyte, and a casing. The positive and negative electrode materials are the primary factors affecting the battery's storage capacity and energy. Due to the relatively stable properties of graphite and its insensitivity to low voltage, graphite is generally used as the negative electrode material in mainstream terminal devices on the market.

[0043] In some examples, silicon-based batteries, compared to graphite-based batteries, can have a larger storage capacity under the same conditions when silicon is used as the negative electrode material. For instance, with a graphite-based battery having a storage capacity of 2300 mAh, replacing the negative electrode material with silicon can increase the storage capacity by approximately 140 mAh. However, silicon-based batteries suffer from a low discharge plateau, increased capacity decay at low voltages, and a tendency to expand during charge-discharge cycles, limiting their optimal applications. Current research primarily focuses on employing new preparation methods or adjusting material mixing ratios to improve the performance of silicon-based batteries or reduce the probability of expansion; however, a superior preparation method has yet to be found that enables the widespread application of silicon-based batteries.

[0044] In view of this, embodiments of this application provide a method for determining the state of charge of a battery, used to control batteries such as silicon anode batteries. In implementation of this application, based on collected battery-related usage data, a dynamic mapping between battery voltage data and battery state of charge is achieved, thereby providing a new display method reflecting the battery state of charge (e.g., displayed as battery level). Through this method, the mapped battery state of charge can reflect not only the remaining battery capacity but also the battery voltage state. For example, a lower battery voltage can be mapped to a lower battery level to trigger power-saving modes on the terminal device or remind the user to charge in time; and when the battery voltage is below a voltage threshold, the battery voltage can be mapped to a state of no charge to trigger the terminal device to shut down. This prevents batteries such as silicon anode batteries from being in a low-voltage state for extended periods, which could lead to rapid capacity decay and battery swelling, thereby improving battery stability and extending battery life. It is understood that the methods provided in the embodiments of this application can be applied to silicon anode batteries, or may also be applied to batteries with similar characteristics to silicon anode batteries that may exist in the future, and this application does not limit them.

[0045] It is understood that the terminal device in the embodiments of this application can be such as a mobile phone, tablet computer, laptop computer, ultra-mobile personal computer (UMPC), netbook, smart home device (e.g., smart TV, smart screen, smart speaker, etc.), wearable device (e.g., watch, helmet, headphones, etc.), augmented reality (AR) / virtual reality (VR) device, personal digital assistant (PDA), etc. It is understood that the embodiments of this application do not impose any limitations on the specific type of terminal device.

[0046] The terminal devices to which this application's embodiments can be applied include, but are not limited to, those equipped with... Alternatively, it could be a portable terminal device with another operating system. The aforementioned portable terminal device could also be other portable terminal devices, such as a laptop computer with a touch-sensitive surface (e.g., a touch panel).

[0047] Figure 1A schematic diagram of a possible hardware structure for a terminal device is shown. The terminal device 200 includes components such as a radio frequency (RF) circuit 210, a power supply 220, a processor 230, a memory 240, an input unit 250, a display unit 260, an audio circuit 270, a communication interface 280, and a wireless-fidelity (Wi-Fi) module 290. Those skilled in the art will understand that... Figure 1 The hardware structure of the terminal device 200 shown in the figure does not constitute a limitation on the terminal device 200. The terminal device 200 provided in the embodiments of this application may include more or fewer components than shown, may combine two or more components, or may have different component configurations. Figure 1 The various components shown can be implemented in hardware, software, or a combination of hardware and software, including one or more signal processing and / or application-specific integrated circuits.

[0048] The following is combined Figure 1 The various components of the terminal device 200 are described in detail below:

[0049] The RF circuit 210 can be used for receiving and transmitting data during communication or a call. Specifically, after receiving downlink data from the base station, the RF circuit 210 sends it to the processor 230 for processing; additionally, it sends uplink data to be transmitted to the base station. Typically, the RF circuit 210 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low-noise amplifier (LNA), a duplexer, etc.

[0050] Furthermore, the RF circuit 210 can also communicate with other devices via a wireless communication network. The wireless communication can use any communication standard or protocol, including but not limited to Global System for Mobile Communications (GSM), General Packet Radio Service (GPRS), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), Long Term Evolution (LTE), email, and Short Messaging Service (SMS).

[0051] Wi-Fi technology is a short-range wireless transmission technology. The terminal device 200 can connect to an access point (AP) via the Wi-Fi module 290, thereby enabling access to the data network. The Wi-Fi module 290 can be used for receiving and sending data during communication.

[0052] The terminal device 200 can physically connect to other devices through the communication interface 280. Optionally, the communication interface 280 can be connected to the communication interfaces of other devices via a cable to enable data transmission between the terminal device 200 and other devices.

[0053] The terminal device 200 can also perform communication services and interact with server-side devices or other terminal devices. Therefore, the terminal device 200 needs to have data transmission capabilities, meaning that the terminal device 200 needs to include a communication module. Although Figure 1 The RF circuit 210, the Wi-Fi module 290, and the communication interface 280 are shown, but it is understood that the terminal device 200 contains at least one of the above components or other communication modules (such as a Bluetooth module) for data transmission.

[0054] For example, when the terminal device 200 is a mobile phone, the terminal device 200 may include the RF circuit 210, and may also include the Wi-Fi module 290, or may include a Bluetooth module. Figure 1 (Not shown in the image); when the terminal device 200 is a computer, the terminal device 200 may include the communication interface 280, and may also include the Wi-Fi module 290, or may include a Bluetooth module (not shown in the image); Figure 1 (Not shown in the image); when the terminal device 200 is a tablet computer, the terminal device 200 may include the Wi-Fi module, or may include a Bluetooth module (not shown in the image); Figure 1 (Not shown in the image).

[0055] The memory 240 can be used to store software programs and modules. The processor 230 executes various functional applications and data processing of the terminal device 200 by running the software programs and modules stored in the memory 240. Optionally, the memory 240 may mainly include a program storage area and a data storage area. The program storage area may store the operating system (mainly including the software programs or modules corresponding to the kernel layer, system layer, application framework layer, and application layer).

[0056] Furthermore, the memory 240 may include high-speed random access memory, and may also include non-volatile memory, such as at least one disk storage device, flash memory device, or other volatile solid-state storage device. In this embodiment, information such as computer programs related to implementing the methods provided in this embodiment or pre-stored mapping relationships (e.g., pre-configured first mapping relationship, or pre-stored second mapping relationship, or pre-configured third mapping relationship) may be stored in the memory 240.

[0057] The input unit 250 can be used to receive editing operations on various types of data objects, such as numbers or characters, input by the user, and to generate key signal inputs related to user settings and function control of the terminal device 200. Optionally, the input unit 250 may include a touch panel 251 and other input devices 252.

[0058] The touch panel 251, also known as a touch screen, can collect touch operations performed by the user on or near it (such as operations performed by the user using a finger, stylus, or any suitable object or accessory on or near the touch panel 251), and drive the corresponding connection device according to a pre-set program.

[0059] Optionally, the other input device 252 may include, but is not limited to, one or more of the following: physical keyboard, function keys (such as volume control buttons, power buttons, etc.), trackball, mouse, joystick, etc.

[0060] The display unit 260 can be used to display information input by the user or information provided to the user, as well as various menus of the terminal device 200. The display unit 260 is the display method of the terminal device 200, used to present the interface and realize human-computer interaction. The display unit 260 may include a display panel 261. Optionally, the display panel 261 can be configured using a liquid crystal display (LCD), organic light-emitting diode (OLED), or other similar forms. In this embodiment, the display unit 260 can be used to display the mapped battery power status obtained by the method provided in this application, such as displaying the battery level, so that the user can promptly obtain the battery usage status of the terminal device. Thus, by displaying the battery power status, the user can be promptly reminded to charge the battery or that the terminal device is about to shut down.

[0061] The processor 230 is the control center of the terminal device 200. It connects various components via various interfaces and lines, and executes software programs and / or modules stored in the memory 240, as well as calling data stored in the memory 240, to perform various functions and process data of the terminal device 200, thereby realizing multiple services based on the terminal device 200. In this embodiment, the processor 230 can communicate with the fuel gauge hardware circuit to implement the methods provided in this embodiment. For example, the processor 230 can receive relevant parameters of the power supply 220 (such as a battery) collected by the fuel gauge hardware circuit.

[0062] The terminal device 200 also includes a power supply 220 (such as a battery) for supplying power to various components. Optionally, the power supply 220 can be logically connected to the processor 230 through a power management system, thereby enabling the power management system to manage functions such as charging, discharging, and power consumption.

[0063] like Figure 1 As shown, the terminal device 200 also includes an audio circuit 270, a microphone 271, and a speaker 272, providing an audio interface between the user and the terminal device 200. The audio circuit 270 converts audio data into signals recognizable by the speaker 272 and transmits the signals to the speaker 272, where the speaker 272 converts them into sound signals for output. The microphone 271 collects external sound signals (such as human speech or other sounds) and converts the collected external sound signals into signals recognizable by the audio circuit 270, sending them to the audio circuit 270. The audio circuit 270 can also convert the signals transmitted by the microphone 271 into audio data, outputting the audio data to the RF circuit 210 for transmission to, for example, another terminal device, or outputting the audio data to the memory 240 for further processing.

[0064] Although not shown, the terminal device 200 may also include at least one sensor, a camera, etc., which will not be described in detail here. The at least one sensor may include, but is not limited to, a pressure sensor, a barometric pressure sensor, an accelerometer, a distance sensor, a fingerprint sensor, a touch sensor, a temperature sensor, etc.

[0065] The operating system (OS) involved in this application embodiment is the most basic system software running on the terminal device 200. Taking a mobile phone as an example, the operating system can be HarmonyOS, Android, or iOS. The software system of the terminal device 200 can adopt a layered architecture, event-driven architecture, microkernel architecture, microservice architecture, or cloud architecture. This application embodiment uses an operating system with a layered architecture as an example to illustrate the software architecture of the terminal device 200.

[0066] Figure 2 This is a software architecture block diagram of a terminal device provided in an embodiment of this application. For example... Figure 2 As shown, the software architecture of a terminal device can be a layered architecture. For example, the software can be divided into several layers, each with a clear role and division of labor. Layers communicate with each other through software interfaces. In some embodiments, the operating system is divided into five layers, from top to bottom: the application layer, the application framework layer (framework, FWK), the runtime and system libraries, the kernel layer, and the hardware layer.

[0067] The application layer can include a series of application packages. For example... Figure 2 As shown, the application layer can include camera, settings, skin modules, user interface (UI), third-party applications, etc. Third-party applications can include WLAN, music, call, Bluetooth, video, etc.

[0068] In one possible implementation, the application can be developed using Java, by calling the application programming interface (API) provided by the application framework layer. Developers can then interact with the underlying operating system layers (such as the hardware layer and kernel layer) to develop their own applications. This application framework layer primarily consists of a series of services and management systems within the operating system.

[0069] The application framework layer provides application programming interfaces and a programming framework for applications within the application layer. The application framework layer includes some predefined functions. For example... Figure 2 As shown, the application framework layer may include a shortcut icon management module, a window manager, a content provider, a phone manager, a view system, a notification manager, a resource manager, etc.

[0070] The shortcut icon management module is used to manage the shortcut icons displayed on the terminal device, such as creating shortcut icons, removing shortcut icons, and monitoring whether shortcut icons meet the display conditions.

[0071] The window manager is used to manage windowed applications. It can obtain the screen size, determine if a status bar is present, lock the screen, and capture screenshots. The content provider stores and retrieves data, making this data accessible to applications. This data may include videos, images, audio, made and received phone calls, browsing history and bookmarks, phone books, etc.

[0072] A phone manager is used to provide communication functions for terminal devices. For example, it manages call status (including connection and disconnection).

[0073] A view system includes visual controls, such as controls for displaying text, images, and battery levels. View systems can be used to build applications. A display interface can consist of one or more views. For example, a display interface including a text notification icon could include views for displaying text and views for displaying images.

[0074] The notification manager allows applications to display notifications in the status bar. These notifications can be used to deliver informational messages and can disappear automatically after a short pause, requiring no user interaction. For example, the notification manager can be used to notify users of download completion or message alerts. The notification manager can also display notifications as icons or scrolling text in the top status bar, such as notifications from background applications, or as dialog boxes on the screen. Examples include displaying text messages in the status bar, emitting sounds, vibrating the device, and flashing indicator lights.

[0075] The file explorer provides applications with various resources, such as localized strings, icons, images, layout files, video files, and more.

[0076] The runtime includes the core libraries and the virtual machine. The runtime is responsible for the scheduling and management of the operating system.

[0077] The core library consists of two parts: one part contains the functionalities that the Java language needs to call, and the other part contains the core libraries of the operating system. The application layer and application framework layer run in the virtual machine. The virtual machine executes the Java files of the application layer and application framework layer as binary files. The virtual machine is used to perform functions such as object lifecycle management, stack management, thread management, security and exception management, and garbage collection.

[0078] System libraries can include multiple functional modules. For example: surface manager, 3D graphics processing library (e.g., OpenGL ES), 2D graphics engine (e.g., SGL), media libraries, etc.

[0079] The Surface Manager is used to manage the display subsystem and provides the blending of 2D and 3D layers for multiple applications.

[0080] The 3D graphics processing library is used to implement 3D graphics drawing, image rendering, compositing, and layer processing.

[0081] A 2D graphics engine is a graphics engine for 2D drawing.

[0082] In some embodiments, a 3D graphics processing library can be used to draw 3D motion trajectory images, and a 2D graphics engine can be used to draw 2D motion trajectory images.

[0083] The media library supports playback and recording of various common audio and video formats, as well as still image files. It supports multiple audio and video encoding formats, such as MPEG4, H.264, MP3, AAC, AMR, JPG, and PNG.

[0084] The kernel layer is the layer between hardware and software. The kernel layer includes at least display drivers, camera drivers, audio drivers, and sensor drivers.

[0085] The hardware layer can include various types of sensors, such as accelerometers, gravity sensors, and touch sensors.

[0086] Typically, a terminal device 200 can run multiple applications simultaneously. In a simpler scenario, one application corresponds to one process; in a more complex scenario, one application can correspond to multiple processes. Each process has a unique process ID.

[0087] It should be understood that the hardware structure of a terminal device can be as follows: Figure 1 As shown, the software architecture can be as follows: Figure 2 As shown, the software programs and / or modules corresponding to the software architecture in the terminal device can be stored in the memory 240, and the processor 230 can run the software programs and applications stored in the memory 240 to execute the process of a method for determining battery power status provided in this application embodiment.

[0088] It should be understood that in the embodiments of this application, "at least one" means one or more, and "more than one" means two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone, where A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can represent: a, b, c, a and b, a and c, b and c, or a, b, and c, where a, b, and c can be single or multiple.

[0089] The multiple instances mentioned in the embodiments of this application refer to two or more.

[0090] In addition, it should be understood that in the description of this application, the words "first" and "second" are used only for the purpose of distinguishing descriptions and should not be construed as indicating or implying relative importance or order.

[0091] Furthermore, in the embodiments of this application, the terms "terminal device" and "device" can be used interchangeably, that is, they refer to various devices that can be used to implement the embodiments of this application.

[0092] In combination with the above Figure 1 The text describes the hardware structure of the terminal device, and... Figure 2 The software framework of the terminal device is described below. With reference to several embodiments and accompanying drawings, the working principle of the software and hardware of the terminal device executing the battery power state determination method proposed in the embodiments of this application is illustrated.

[0093] See Figure 3 This is a schematic diagram of the hardware structure applicable to a method for determining battery state provided in an embodiment of this application. The hardware structure may include a battery 301 (e.g., it can be...). Figure 1 The circuit shown includes a power supply 220, a fuel gauge (or a coulomb counter, etc., referred to as a fuel gauge in the following embodiments), a circuit 302, a resistor unit 303, a processor 230, and a charging port 304 (e.g., a power supply 220), a fuel gauge (or a coulomb counter, etc., which will be used as an example in the following embodiments), a fuel gauge circuit 302, a fuel gauge unit 303, a processor 230, and a charging port 304 (e.g., a power supply 220), a fuel gauge circuit 302, a resistor unit 303, a processor 230, and a charging port 304). Figure 1 The communication interface 280 shown in the figure.

[0094] The battery 301 can be used to provide energy to the terminal device 200 to ensure the normal use of the terminal device 200.

[0095] The fuel gauge circuit 302 can be used to sample the voltage across the battery 301, and can also be used to sample the current output by the battery 301 (or the current input to the resistor unit 303); or, depending on the actual scenario, it can also be used to sample other types of battery-related data, such as battery usage data.

[0096] The resistor unit 303 can be used by the fuel meter circuit 302 to sample the current, etc.

[0097] The processor 230 can be used to receive sampled data (such as battery voltage, battery current, etc.) from the fuel gauge circuit 302, and based on the sampled data, it can realize the mapping between voltage and battery power status to determine the battery power status and other processing.

[0098] The charging port 304 can be used to charge the battery 301 to ensure the battery 301 has sufficient power storage.

[0099] based on Figure 3 The hardware structure diagram shown indicates that the processor 230 included in the terminal device 200 can obtain battery usage data from the battery meter circuit 302 by sampling the battery 301 and statistically analyzing the data, and then determine the mapped battery power status based on the battery usage data.

[0100] See Figure 4 This is a flowchart illustrating a method for determining battery state according to an embodiment of this application. The method can be applied to terminal devices and includes at least the following steps:

[0101] Step 401: Determine the battery protection voltage parameters based on the battery usage data; the battery usage data is used to reflect the battery's usage status within a preset time period, and the battery protection voltage parameters are used to change the original voltage parameters corresponding to the battery's charge level.

[0102] The battery usage data may include, but is not limited to, one or a combination of the following information: full charge capacity (FCC), initial charge level at the start of charging (also referred to as "start-charge capacity" in this embodiment), second charge level at the end of charging (also referred to as "end-charge capacity" in this embodiment), battery usage time, and battery (charge-discharge) cycle count. It is understood that the information included in the battery usage data may be multiple sets of data statistically obtained within the preset time period. For example, the FCC, start-charge capacity, and end-charge capacity may be data obtained from multiple charging operations within the preset time period.

[0103] Optionally, the terminal device can collect and statistically analyze the included batteries to obtain battery usage data. Furthermore, the preset time period can be the period from the start of data collection to the implementation of the method provided in this application. The terminal device can continuously collect and statistically analyze the battery usage data, thus continuously implementing the method provided in this application based on historically obtained battery usage data. Additionally, the terminal device can trigger the collection and statistical analysis of battery usage data based on different preset collection commands; these preset collection commands can be configured according to actual scenarios, etc.

[0104] In one optional embodiment, upon detecting and responding to the power-on of the terminal device, the hardware units included in the terminal device begin to operate. In this application, after the processor 230 starts operating, it can initiate the collection of battery usage data. For example, when it detects that the battery 301 is fully charged, FCC data is collected; when it detects that the battery 301 has started charging, the initial charge amount is collected; when it detects that the battery 301 has stopped charging, the stopped charge amount is collected; and, during each charging cycle, the changes in the charge and discharge capacity are accumulated. If a complete charge-discharge cycle is collected, the battery cycle count is updated; and the battery usage time is collected, which can be the usage time after power-on or the usage time after a full charge, etc. This application does not limit the statistical method of battery usage time. It is understood that the processor 230 can use different processes to collect and statistically analyze different information of battery usage data, or some information can be collected using the same process.

[0105] In another alternative embodiment, the processor 230 may also start collecting and collecting battery usage data in response to the detection or charging of the terminal device.

[0106] In another optional embodiment, the terminal device may also receive and respond to a user operation command to enable battery optimization, and initiate the collection and statistics of battery usage data. For example, the battery-related display interface on the terminal device's display panel 261 may include battery optimization controls for updating the battery's state; for example, Figure 5 The display interface of the terminal device shown includes a battery optimization control 510. For example... Figure 5 As shown, if the user enables the battery optimization control 510, the terminal device can initiate the battery power status determination method provided in this embodiment of the application to optimize the battery by updating the battery power status. If the user does not enable the battery optimization control 510 ( Figure 5 (not shown), then the terminal device can determine the battery level of the terminal device by collecting the battery level data.

[0107] Furthermore, in the above embodiments, after the terminal device restarts, the processor 230 can resume collecting and calculating battery usage data. This reduces the pressure on data storage and allows for a more accurate mapping of the target battery level based on the latest battery usage data. It is understood that if the terminal device replaces the battery, the processor 230 can also resume sampling and calculating battery usage data, discarding the battery usage data collected and stored for the original battery.

[0108] Alternatively, the terminal device may also receive battery usage data sent from other devices (e.g., a server). This battery usage data may, for example, be obtained by the other device through other means. It is understood that the method of obtaining the battery usage data is not limited in this embodiment.

[0109] In one optional implementation, the terminal device can determine the battery protection voltage parameters corresponding to the battery usage data based on a pre-configured first mapping relationship. The pre-configured first mapping relationship can be stored in the memory 240.

[0110] Optionally, the pre-configured first mapping relationship can be used to reflect the correspondence between the values ​​of different battery usage data and the values ​​of different battery protection voltage parameters; or it can be used to reflect the correspondence between the ranges of different battery usage data and the values / ranges of different battery protection voltage parameters. In this way, after collecting battery usage data, the terminal device can determine the corresponding battery protection voltage parameter by referring to the first mapping relationship.

[0111] For example, the pre-configured first mapping relationship can be obtained by configuring multiple sets of experimental data, thus yielding a better first mapping relationship. Another example is that the terminal device can also obtain the pre-configured first mapping relationship based on deep learning. For instance, it can pre-obtain the correspondence between multiple sets of battery usage data and battery protection voltage parameters through experiments, and then use these multiple correspondences as training samples for deep learning to obtain the first mapping relationship. It is understood that the battery protection voltage parameters obtained based on the pre-configured first mapping relationship during terminal device use can also be used as training samples to optimize the deep learning model, thereby improving the accuracy of the first mapping relationship. It should be noted that the implementation of this application does not limit the method of obtaining the pre-configured first mapping relationship; for example, the first mapping relationship can also be automatically generated based on the actual business scenario.

[0112] In another optional implementation, the terminal device can also determine the battery protection voltage parameter based on battery usage data and other parameters. For example, other parameters may include application running information of the terminal device.

[0113] In implementation of this application, the battery protection voltage parameter is used to change the original voltage parameter corresponding to the battery capacity, which can be implemented as changing the original shutdown voltage, the original full charge voltage, or the voltage corresponding to other capacities. Optionally, if the battery protection voltage parameter is used to change the target shutdown voltage of the battery, the battery protection voltage parameter may include a target shutdown voltage parameter that changes the original shutdown voltage. Alternatively, if the battery protection voltage parameter is used to change the target full charge voltage of the battery, the battery protection voltage parameter may include a target full charge voltage parameter that changes the original full charge voltage. Yet another option is that if the battery protection voltage parameter is used to change both the target shutdown voltage and the target full charge voltage of the battery, the battery protection voltage parameter may include both the target shutdown voltage parameter and the target full charge voltage parameter.

[0114] The target protection voltage parameters, such as the target shutdown voltage parameter and the target full charge voltage parameter, can have different forms of representation. For example, they can include the following forms:

[0115] (1) Used to indicate the absolute value of the changed value. For example, the target shutdown voltage parameter can be expressed as an increase of 50 millivolts (mV) or +50mV; the target full charge voltage parameter can be expressed as a decrease of 100mV or -100mV.

[0116] (2) Used to indicate relative values ​​of the change ratio. For example, the target shutdown voltage parameter can be expressed as a 1% increase; the target full charge voltage parameter can be expressed as 2%.

[0117] (3) Used to indicate the target value obtained after the change. For example, the target shutdown voltage parameter can be expressed as 3.3V; it can be understood that the target shutdown voltage parameter may be different from the original shutdown voltage parameter, such as 3.2V. The target full charge voltage parameter can be expressed as 4.4V; it can be understood that the target full charge voltage parameter may be different from the original full charge voltage parameter, such as 4.5V.

[0118] Furthermore, the battery protection voltage parameters may include one or more voltage parameters that are numerical values ​​or ranges. For example, the target shutdown voltage parameter may be 3.3V or a range of 3.25V to 3.35V. For instance, when the terminal device periodically collects or collects battery voltage in response to a collection command, if it is determined that the battery voltage falls within the range corresponding to the target shutdown voltage parameter, the terminal device can be triggered to shut down.

[0119] Step 402: Determine the second mapping relationship between the actual battery capacity and the target battery capacity based on the battery protection voltage parameters.

[0120] In one optional implementation, a second mapping relationship corresponding to the battery protection voltage parameter is determined based on a first modeling parameter; the first modeling parameter is used to indicate the correspondence between battery voltage and battery capacity. For example, the first modeling parameter can be expressed as SOC = f(V), where SOC represents the battery capacity and f(V) represents the battery voltage function corresponding to the battery capacity.

[0121] Optionally, taking the battery protection voltage parameter expressed in the aforementioned absolute value form as an example, the second mapping relationship between the actual battery capacity and the target battery capacity can be determined using formulas 1-1 to 7, as follows:

[0122] 100% = SOC 原始满充电量 =f(V 原始满充电压 ) Formula 1-1

[0123] 0% = SOC 原始关机电量 =f(V 原始关机电压 ) Formula 1-2

[0124] SOC 目标满充电量 =f(V 原始满充电压 -△V 降低电压 ) Formula 1-3

[0125] SOC 目标关机电量 =f(V 原始关机电压 -△V 抬升电压 ) Formula 1-4

[0126] Assume the second mapping relationship between the actual battery capacity and the target battery capacity is represented by the following formulas 1-5:

[0127] SOC 目标电池电量 =±kSOC 实际电池电量 ±b Formula 1-5

[0128] Since k and b are constants in formulas 1-5, this application does not limit the signs of k and b. Therefore, the setting of the second mapping relationship can have multiple forms; for example, formulas 1-5 can include four forms. In this embodiment, SOC is used. 目标电池电量 =kSOC 实际电池电量 -b is used as an example. It can be understood that regardless of the form in formulas 1-5, the calculated result of the second mapping relationship is consistent.

[0129] If we combine formulas 1-3 and 1-4 with formula 1-5 respectively, we can obtain the following formulas 1-6 and 1-7:

[0130] SOC 目标满充电量 =kSOC 原始满充电量 -b Formula 1-6

[0131] SOC 目标关机电量 =kSOC 原始关机电量 -b Formula 1-7

[0132] Among them, SOC 目标满充电量 SOC can be obtained through formulas 1-3. 目标关机电量 SOC can be obtained through formulas 1-4. 原始满充电量 100%, SOC 原始关机电量 The value is 0%. Therefore, based on formulas 1-6 and 1-7 above, the values ​​of k and b can be calculated, thus obtaining the second mapping relationship in formula 1-5.

[0133] Alternatively, if the battery protection voltage parameter is expressed in the relative value form described above, then based on Formulas 1-1 and 1-2, Formulas 1-3 and 1-4 can be expressed as Formulas 2-3 and 2-4:

[0134] SOC 目标满充电量 =f(V 原始满充电压 *(1-T1)) Formula 2-3

[0135] SOC 目标关机电量 =f(V 原始关机电压 *(1+T2)) Formula 2-4

[0136] Wherein, T1 represents the relative value of the adjustment to the original full-charge voltage, for example, it can be expressed as a percentage, such as 5%. Then, Formula 2-3 means that the target full-charge voltage is reduced by 5% compared to the original full-charge voltage. Similarly, T2 represents the relative value of the adjustment to the original shutdown voltage, assuming it is 7%. Then, Formula 2-4 means that the target shutdown voltage is increased by 7% compared to the original shutdown voltage.

[0137] Furthermore, the implementation method for determining the second mapping relationship between the actual battery capacity and the target battery capacity in this embodiment can be found in the previous embodiment, and will not be repeated here.

[0138] Alternatively, if the battery protection voltage parameter is expressed in the form of the target value described above, then based on Formulas 1-1 and 1-2, Formulas 1-3 and 1-4 can also be expressed as Formulas 3-3 and 3-4:

[0139] SOC 目标满充电量 =f(V 目标满充电压 ) Formula 3-3

[0140] SOC 目标关机电量 =f(V 目标关机电压 ) Formula 3-4

[0141] It is understood that the implementation method for determining the second mapping relationship between the actual battery power and the target battery power in this embodiment can also refer to the aforementioned embodiments, and will not be repeated here.

[0142] In addition, the first modeling parameter can also be combined with other data information of the battery to reflect the correspondence between battery voltage and battery capacity; for example, other data information may include, but is not limited to: current information and temperature information.

[0143] The first modeling parameter can also be pre-stored in the memory 240. For example, the first modeling parameter can be obtained based on multiple sets of experimental data values ​​and then pre-configured in the terminal device.

[0144] In another optional implementation, the terminal device can also determine a second mapping relationship between the actual battery capacity and the target battery capacity based on the battery protection voltage parameter in combination with other parameters. For example, other parameters may include information such as battery temperature and battery current.

[0145] Step 403: Determine the target battery capacity based on the second mapping relationship and the actual battery capacity of the battery.

[0146] Optionally, the processor 230 can collect the current actual battery level in real time and obtain the mapped target battery level based on the actual battery level and the second mapping relationship shown in formulas 1-5 above. For example, the processor 230 can collect an actual battery level of 30%, and after mapping, obtain a target battery level of 16%. Optionally, if the terminal device has enabled automatic power-saving mode when the battery level is below 20%, it can also automatically activate the power-saving mode. For another example, the processor 230 can collect an actual battery level of 10%, and after mapping, obtain a target battery level of 0%. In this case, if the terminal device's power management system detects that the target battery level is displayed as 0, it can trigger an automatic shutdown process.

[0147] It should be noted that, in the implementation of this application, obtaining the actual battery capacity can be implemented by continuously collecting battery parameters used to determine the actual battery capacity, and then determining the actual battery capacity based on the battery parameters. These battery parameters can be, for example, battery current, battery voltage, etc. Alternatively, it can be implemented by periodically collecting the battery parameters and determining the actual battery capacity in the current cycle based on the battery parameters. Or, it can be implemented by receiving and responding to a request instruction to collect the battery parameters and determining the actual battery capacity based on the battery parameters; for example, if an application or process requests to access the battery capacity, the processor 230 can respond to the application or process to obtain the actual battery capacity.

[0148] Optionally, after determining the mapped target battery level, the processor 230 can transmit the mapped target battery level to the display unit 260 for display, so that the user can obtain the mapped target battery level. Alternatively, if the processor 230 receives a request instruction from another application or process to obtain battery level, it can feed back the mapped target battery level to the other application or process to enable the invocation processing of other applications or processes on the terminal device.

[0149] See Figure 6 This is another flowchart illustrating a method for determining battery state provided in an embodiment of this application. This method can be applied to terminal devices and includes at least the following steps:

[0150] Step 401: Determine the battery protection voltage parameters based on the battery usage data; the battery usage data is used to reflect the battery's usage status within a preset time period, and the battery protection voltage parameters are used to change the original voltage parameters corresponding to the battery's charge level.

[0151] The implementation process of step 401 can be found in the description of the above embodiments, and will not be repeated here.

[0152] Step 402': Determine the correspondence between the actual battery voltage and the target battery capacity based on the battery protection voltage parameters.

[0153] Optionally, based on a pre-configured third mapping relationship, the first modeling parameter is switched to the second modeling parameter; the first modeling parameter is used to indicate the original correspondence between battery voltage and battery capacity, and the second modeling parameter is used to indicate the target correspondence between battery voltage and battery capacity.

[0154] Here, it is assumed that the first modeling parameter can be expressed as SOC = f1(V), where SOC can represent the battery capacity and f1(V) can represent the first battery voltage function corresponding to the battery capacity.

[0155] For example, if a terminal device determines the battery protection voltage parameter based on the collected battery usage data, it can be understood that the correspondence between the original battery voltage and the original battery capacity indicated by the first modeling parameter is no longer applicable. In this application, a second modeling parameter can be determined based on the battery protection voltage parameter. For example, the second modeling parameter can be expressed as SOC = f2(V), where SOC represents the battery capacity and f2(V) represents the second battery voltage function corresponding to the battery capacity.

[0156] Optionally, the battery protection voltage parameters include, but are not limited to, one or a combination of the power-off voltage target parameter and the full-charge voltage target parameter. Taking the power-off voltage target parameter as an example, the processor 230 can retrieve a suitable second modeling parameter from a pre-stored third mapping relationship based on the power-off voltage target parameter. The pre-configured third mapping relationship can be used to reflect the correspondence between different battery protection voltage parameter values ​​and different modeling parameters; or it can be used to reflect the correspondence between different battery protection voltage parameter ranges and different modeling parameters. It should be noted that the terminal device can pre-configure multiple different modeling parameters, for example, pre-store five types of modeling parameters, from the first to the fifth. The battery protection voltage parameters can include one or more parameters that are parameter values ​​or parameter ranges.

[0157] The pre-configured third mapping relationship can be stored in memory 240.

[0158] Step 403': Determine the target battery capacity based on the correspondence and the actual battery voltage of the battery.

[0159] For example, by Figure 3 The fuel gauge circuit 302 shown can collect one or a combination of battery data, such as battery voltage data, current data, and current integral data. Based on the second modeling parameter, it can calculate the target battery capacity. It is understood that the correspondence between battery voltage and battery capacity indicated by the first and second modeling parameters are different. Therefore, when the fuel gauge circuit 302 collects the same battery data, different battery capacities can be obtained.

[0160] The method provided in this application, based on collected battery usage data, allows for the setting of corresponding battery protection voltage parameters according to battery usage conditions to protect the battery. This, in turn, alters the mapping relationship between battery voltage and battery capacity to determine the mapped battery capacity status. This method can achieve the mapping from battery voltage to battery capacity not only by calculating the mapping between the target battery capacity and the actual battery capacity, but also by changing the mapping relationship between battery voltage and battery capacity, thereby enabling the determination of battery capacity based on battery voltage mapping.

[0161] Therefore, the mapped target battery capacity not only reflects the actual battery capacity but also the battery voltage. This allows for mapping a lower target battery capacity when the battery voltage is low, promptly reminding the user to charge and preventing the battery from remaining in a low-voltage state for extended periods. Thus, dynamic mapping based on battery voltage and capacity can effectively prevent the battery from operating in dangerous voltage ranges for extended periods. For example, silicon anode batteries exhibit unstable performance in low-voltage ranges; therefore, when using silicon anode batteries, the battery shutdown voltage can be increased. Alternatively, if other materials are found to have poor performance in other voltage ranges (such as high-voltage ranges), the battery can be protected and its lifespan extended by reducing the full-charge voltage.

[0162] Based on the above embodiments, this application also provides a terminal device, which includes multiple functional modules. These multiple functional modules interact to implement the functions performed by the terminal device in the methods described in the embodiments of this application. The multiple functional modules can be implemented based on software, hardware, or a combination of both, and can be arbitrarily combined or divided based on specific implementations. For example, see [link to relevant documentation]. Figure 7 This is a schematic diagram of a device for determining battery power status according to an embodiment of this application. The device may include: a data acquisition module 701, a processing module 702, and a transceiver module 703. For example, the data acquisition module 701 can be used to acquire battery usage data; the processing module 702 can be used to process battery protection voltage parameters, second mapping relationships, or target battery power as described in the foregoing embodiments; the transceiver module 703 can be used to receive real-time battery power data acquired by other hardware units. The specific functions that each module can achieve can be combined with the foregoing... Figures 4 to 6 The content of the embodiments described herein.

[0163] Based on the above embodiments, this application also provides a terminal device, which includes at least one processor and at least one memory. The at least one memory stores computer program instructions. When the terminal device is running, the at least one processor executes the functions performed by the terminal device in the various methods described in the embodiments of this application. For example, when executing... Figure 4 In the illustrated embodiment, the terminal device performs steps 401 to 403, or executes... Figure 6 Steps 401 to 403' performed by the terminal device in the illustrated embodiment.

[0164] Based on the above embodiments, this application also provides a computer program product, which includes a computer program (also referred to as code or instructions) that, when run, causes a computer to perform the methods described in the embodiments of this application.

[0165] Based on the above embodiments, this application also provides a computer-readable storage medium storing a computer program, which, when executed by a computer, causes the computer to perform the methods described in the embodiments of this application.

[0166] Based on the above embodiments, this application also provides a chip for reading computer programs stored in a memory to implement the methods described in the embodiments of this application.

[0167] Based on the above embodiments, this application provides a chip system including a processor for supporting a computer device in implementing the methods described in the embodiments of this application. In one possible design, the chip system further includes a memory for storing necessary programs and data of the computer device. This chip system may be composed of chips or may include chips and other discrete devices. Those skilled in the art will understand that the embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0168] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to this application. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart illustrations. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0169] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0170] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0171] Obviously, those skilled in the art can make various modifications and variations to this application without departing from the scope of protection of this application. Therefore, if such modifications and variations fall within the scope of the claims of this application and their equivalents, this application also intends to include such modifications and variations.

Claims

1. A method for determining the state of charge of a battery, characterized in that, include: Determine the battery protection voltage parameters based on battery usage data; The battery usage data is used to reflect the battery's usage status within a preset time period, and the battery protection voltage parameter is used to change the original voltage parameter corresponding to the battery's charge level. Based on the battery protection voltage parameters, a second mapping relationship between the actual battery capacity and the target battery capacity is determined; The target battery capacity is determined based on the second mapping relationship and the actual battery capacity.

2. The method according to claim 1, characterized in that, The process of determining the battery protection voltage parameters based on battery usage data includes: Based on a pre-configured first mapping relationship, the battery protection voltage parameters corresponding to the battery usage data are determined.

3. The method according to claim 2, characterized in that, The pre-configured first mapping relationship is used to reflect the correspondence between the values ​​of different battery usage data and the values ​​of different battery protection voltage parameters; or, The pre-configured first mapping relationship is used to reflect the correspondence between the range of different battery usage data and the values ​​or ranges of different battery protection voltage parameters.

4. The method according to claim 1, characterized in that, The step of determining the second mapping relationship between the actual battery capacity and the target battery capacity based on the battery protection voltage parameters includes: Based on the first modeling parameters, a second mapping relationship corresponding to the battery protection voltage parameters is determined; the first modeling parameters are used to indicate the correspondence between battery voltage and battery capacity.

5. The method according to any one of claims 1 to 4, characterized in that, The battery usage data includes one or more of the following: Full charge capacity (FCC), initial charge level at start of charging, second charge level at stop of charging, battery usage time, and battery cycle count.

6. The method according to any one of claims 1 to 5, characterized in that, Before determining the battery protection voltage parameters based on battery usage data, the method further includes: Receive and respond to a preset collection command, collect and statistically analyze the battery usage data; The preset acquisition instructions include: detecting that the terminal device is powered on; or detecting that the terminal device is charging; or receiving a user operation instruction to activate battery optimization.

7. The method according to any one of claims 1 to 6, characterized in that, The battery protection voltage parameter includes at least one of the following parameters: The target shutdown voltage is obtained by changing the original shutdown voltage contained in the original voltage parameters. The target full charge voltage is obtained by modifying the original full charge voltage contained in the original voltage parameters.

8. The method according to any one of claims 1 to 7, characterized in that, The battery protection voltage parameter is indicated by one of the following forms: Used to indicate the absolute value of the changed value; Used to indicate the relative value of the change ratio; Used to indicate the target value obtained after the change.

9. The method according to claim 1, characterized in that, Obtaining the actual battery capacity of the battery includes: Continuously collect battery parameters used to determine the actual battery capacity, or periodically collect the battery parameters, or receive and respond to a request instruction to collect the battery parameters; The actual battery capacity is determined based on the battery parameters.

10. A method for determining the state of charge of a battery, characterized in that, include: Determine the battery protection voltage parameters based on battery usage data; The battery usage data is used to reflect the usage status of the battery within a preset time period, and the battery protection voltage parameter is used to change the original voltage of one or more batteries corresponding to the battery capacity. Based on the battery protection voltage parameters, determine the correspondence between the actual battery voltage and the target battery capacity; Based on the correspondence and the actual battery voltage, the target battery capacity is determined.

11. The method according to claim 10, characterized in that, The process of determining the battery protection voltage parameters based on battery usage data includes: Based on a pre-configured first mapping relationship, the battery protection voltage parameters corresponding to the battery usage data are determined.

12. The method according to claim 11, characterized in that, The pre-configured first mapping relationship is used to reflect the correspondence between the values ​​of different battery usage data and the values ​​of different battery protection voltage parameters; or, The pre-configured first mapping relationship is used to reflect the correspondence between the range of different battery usage data and the values ​​or ranges of different battery protection voltage parameters.

13. The method according to claim 10, characterized in that, The step of determining the correspondence between the actual battery voltage and the target battery capacity based on the battery protection voltage parameters includes: Based on the pre-configured third mapping relationship, the first modeling parameter is switched to the second modeling parameter; the first modeling parameter is used to indicate the original correspondence between battery voltage and battery capacity, and the second modeling parameter is used to indicate the target correspondence between battery voltage and battery capacity.

14. The method according to any one of claims 10 to 13, characterized in that, The battery usage data includes one or more of the following: Full charge capacity (FCC), initial charge level at start of charging, second charge level at stop of charging, battery usage time, and battery cycle count.

15. The method according to any one of claims 10 to 14, characterized in that, Before determining the battery protection voltage parameters based on battery usage data, the method further includes: Receive and respond to a preset collection command, collect and statistically analyze the battery usage data; The preset acquisition instructions include: detecting that the terminal device is powered on; or detecting that the terminal device is charging; or receiving a user operation instruction to activate battery optimization.

16. The method according to any one of claims 10 to 15, characterized in that, The battery protection voltage parameter includes at least one of the following parameters: The target shutdown voltage is obtained by changing the original shutdown voltage contained in the original voltage parameters. The target full charge voltage is obtained by modifying the original full charge voltage contained in the original voltage parameters.

17. The method according to any one of claims 10 to 16, characterized in that, The battery protection voltage parameter is indicated by one of the following forms: Used to indicate the absolute value of the changed value; Used to indicate the relative value of the change ratio; Used to indicate the target value obtained after the change.

18. A terminal device, characterized in that, The device includes at least one processor coupled to at least one memory, the at least one processor being configured to read a computer program stored in the at least one memory to perform the method as claimed in any one of claims 1 to 9, or to perform the method as claimed in any one of claims 10 to 17.

19. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores instructions that, when executed on a computer, cause the computer to perform the method as described in any one of claims 1 to 9, or the method as described in any one of claims 10 to 17.

20. A computer program product containing instructions, characterized in that, When the computer program product is run on a computer, it causes the computer to perform the method as described in any one of claims 1 to 9, or the method as described in any one of claims 10 to 17.

21. A graphical user interface on a terminal device, characterized in that, The terminal device has a display screen, one or more memories, and one or more processors, the one or more processors being configured to execute one or more computer programs stored in the one or more memories, the graphical user interface including a graphical user interface displayed when the terminal device performs the method as described in any one of claims 1 to 9, or a graphical user interface displayed when the terminal device performs the method as described in any one of claims 10 to 17.

Citation Information

Patent Citations

  • Battery electric quantity display method and device of terminal device

    CN108107374A

  • A Li-ion battery protection circuit and its control method

    KR1020150041502A