CN116723268B

CN116723268B - Terminal battery abnormality management and control method and mobile terminal

Info

Publication number: CN116723268B
Application number: CN202310979067.3A
Authority: CN
Inventors: 魏国帅
Original assignee: Honor Device Co Ltd
Current assignee: Honor Device Co Ltd
Priority date: 2023-08-04
Filing date: 2023-08-04
Publication date: 2024-04-02
Anticipated expiration: 2043-08-04
Also published as: CN116723268A

Abstract

The application discloses a terminal battery abnormality management and control method and a mobile terminal, relates to the technical field of terminals, and is applied to the mobile terminal, wherein the mobile terminal comprises a battery. Comprising the following steps: the mobile terminal acquires a first configuration update file, wherein the first configuration update file is used for updating parameters of target applications in the mobile terminal and representing whether the battery of the mobile terminal is abnormal or not. Under the condition that the preset condition is met, when the battery of the mobile terminal is in a charging state, the mobile terminal stops charging when detecting that the charging electric quantity of the battery of the mobile terminal reaches a preset charging electric quantity threshold value. The preset condition comprises that the first configuration update file indicates that the battery of the mobile terminal is abnormal. In the scheme, the mobile terminal can conduct charging limit control on the risk battery with abnormality, and potential safety hazards brought to a user by the risk battery with abnormality are reduced.

Description

Terminal battery abnormality management and control method and mobile terminal

Technical Field

The embodiment of the application relates to the technical field of terminals, in particular to a terminal battery abnormality management and control method and a mobile terminal.

Background

After the mobile phone is subjected to falling, collision, extrusion and the like to cause the defect of the battery pole piece, the risk of short circuit spontaneous combustion of the battery is greatly increased. If the user continues to unconsciously use the terminal with the risk battery, a terminal failure problem or a terminal damage accident caused by the risk battery may occur, thereby bringing potential safety hazard to the user.

Disclosure of Invention

The embodiment of the application provides a terminal battery abnormality management and control method and a mobile terminal, when the mobile terminal determines that a battery is an abnormal risk battery, the mobile terminal can timely conduct battery limit management and control operation, and when a user knows that the battery is abnormal, potential safety hazards brought to the user by the abnormal risk battery are reduced through limit processing in the battery charging process, and the safety of the user using the mobile terminal is improved.

In order to achieve the above purpose, the embodiments of the present application adopt the following technical solutions.

In a first aspect, a method for managing and controlling abnormality of a battery of a terminal is provided, and the method is applied to a mobile terminal, wherein the mobile terminal comprises a battery, and includes:

the mobile terminal obtains a first configuration update file. The first configuration update file is used for updating parameters of target applications in the mobile terminal and representing whether the battery of the mobile terminal is abnormal or not.

Under the condition that the preset condition is met, when the battery of the mobile terminal is in a charging state, the mobile terminal stops charging when detecting that the charging electric quantity of the battery of the mobile terminal reaches a preset charging electric quantity threshold value.

The preset conditions comprise: the first configuration update file indicates that there is an abnormality in the battery of the mobile terminal.

In the application, after the mobile terminal obtains the first configuration update file, when it is determined that the first configuration update file indicates that the battery of the mobile terminal is different, the mobile terminal performs a power limiting control operation on the risk battery. Specifically, when the mobile terminal is in a charging state, and when detecting that the charging capacity of the battery of the mobile terminal meets a preset charging capacity threshold, the mobile terminal stops charging. The mobile terminal automatically triggers the power limiting control of the abnormal battery in the charging process, so that accidents possibly caused by short circuit of the battery in the charging process can be effectively avoided.

In a possible implementation manner of the first aspect, the preset condition further includes: the battery of the mobile terminal is not replaced.

In the present application, there is a delay between the occurrence of an abnormality in the battery of the mobile terminal and the acquisition of the configuration update file issued by the server, during which the user may have replaced the abnormal battery of the mobile terminal. Therefore, before the battery is charged and limited, the mobile terminal can further confirm whether the battery is replaced, and if the battery is not replaced, the abnormal battery is charged and limited, so that the charging and limited operation is more effective.

In a possible implementation manner of the first aspect, the mobile terminal obtains a first configuration update file, including:

the mobile terminal receives a first configuration update file from a server; or,

under the condition that the mobile terminal detects that a charging interruption event is generated, acquiring a first configuration update file from a first storage space of the mobile terminal; or,

under the condition that a system of the mobile terminal is restarted, the mobile terminal acquires a first configuration update file from a second storage space of the mobile terminal; or,

the first configuration update file is specifically used for acquiring the first configuration update file from the second storage space of the mobile terminal under the condition that the service of the target application of the mobile terminal is restarted under the condition that the parameter of the target application of the mobile terminal is updated.

Wherein the second storage space is a permanent storage space (backup area). The first storage space may be a local storage space of the application, and contents in the local storage space of the application may be cleared or overridden and replaced along with parameter updating of the application or restarting of the system.

In the application, the manner of acquiring the first configuration update file by the mobile terminal is different for different scenes. For example, the mobile terminal may directly receive the first configuration update file issued by the server. When the mobile terminal detects that the charging interrupt event is generated, a first configuration update file can be acquired from a local storage space of the application. When the parameter of the application is updated or the system is restarted, the mobile terminal can acquire the first configuration update file from the backup area because the local storage space of the application may be cleared of data. The mobile terminal acquires the first configuration update file in different modes aiming at different scenes, so that in either case, the mobile terminal can judge the battery abnormality based on the acquired first configuration update file and conduct charging limit control when the battery abnormality is determined.

In a possible implementation manner of the first aspect, if the first configuration update file includes the first identifier, when the battery of the mobile terminal is in a charging state, the mobile terminal stops the charging operation when detecting that the charging power of the battery reaches a preset charging power threshold, including:

if the first configuration update file comprises a first identifier and the mobile terminal does not replace the battery, stopping the charging operation when the mobile terminal detects that the charging electric quantity of the battery reaches a preset charging electric quantity threshold value.

In the application, before the battery charging limit power control operation is executed, the mobile terminal can further confirm whether the battery is replaced or not, and meaningless limit power operation on a new battery is avoided.

In another possible implementation manner of the first aspect, after the obtaining the first configuration update file, the method further includes:

the mobile terminal obtains a second version number of a second configuration update file; the second configuration update file is a configuration update file stored in the second storage space;

and if the first version number of the first configuration update file is greater than the second version number of the second configuration update file, the mobile terminal replaces the configuration update file stored in the second storage space with the first configuration update file.

In the application, after receiving the first configuration update file, the mobile terminal can compare the version of the first configuration update file with the version of the second configuration update file in the backup area, and under the condition that the version of the first configuration update file is larger than the version of the second configuration update file, the configuration update file stored in the backup area is replaced by the first configuration update file, so that the purpose of backing up the first configuration update file in the backup area is realized, and the problem of clearing the configuration update file in the first storage space caused by the parameter update of the application or the restart/system restart of the application service performed by the mobile terminal based on the configuration update file is avoided. In addition, under the condition that the version of the first configuration update file is not larger than that of the second configuration update file, the first configuration update file is not stored in the backup area, and the space occupation of repeated files in the backup area is reduced.

In another possible implementation manner of the first aspect, the first configuration update file includes a first battery serial number, and after the obtaining the first configuration update file, the method further includes:

the mobile terminal obtains battery parameters of a current battery of the mobile terminal, wherein the battery parameters comprise a first battery serial number and/or full charge and discharge times.

And the mobile terminal judges whether the battery of the mobile terminal is replaced according to the battery parameters.

Under the condition that the battery parameter comprises a first battery serial number, if the first battery serial number is different from a second battery serial number included in the second storage space, the battery of the mobile terminal is determined to be replaced; if the first battery serial number is the same as the second battery serial number, the battery of the mobile terminal is not replaced. Under the condition that the battery parameters comprise the full charge and discharge times, if the full charge and discharge times are smaller than a preset first threshold value, determining that the battery of the mobile terminal is replaced; and if the number of times of full charge amplification is greater than a preset first threshold value, determining that the battery of the mobile terminal is not replaced.

In this application, before acquiring the battery parameter, the mobile terminal may first determine whether the second storage space includes the second battery serial number.

If the second storage space comprises a second battery serial number, the mobile terminal judges whether the battery is replaced or not based on the first battery serial number and the second battery serial number; if the second storage space does not comprise the second battery serial number, the mobile terminal judges whether the battery is replaced or not based on the current full charge and discharge times of the battery and a preset first threshold value.

Or, in the present application, the mobile terminal determines how to perform the determination of whether to replace the battery based on the acquired battery parameters. If the acquired battery parameters comprise the second battery serial number, the mobile terminal judges whether the battery is replaced or not based on the first battery serial number and the second battery serial number; if the acquired parameters do not include the second battery serial number, the mobile terminal judges whether the battery is replaced or not based on the number of full-charge and discharge of the current battery and a preset first threshold value.

Or, in the present application, if the second storage space includes the second battery serial number, or if the acquired battery parameter includes the second battery serial number, the mobile terminal may also determine whether to replace the battery based on the battery serial number and the number of times of full charge and discharge of the battery. If the first battery serial number is different from the second battery serial number and the number of times of full charge and discharge is smaller than a preset first threshold value, determining that the battery of the mobile terminal is replaced; if the first battery serial number is the same as the second battery serial number included in the first configuration update file and the number of full-charge amplification is greater than a preset first threshold, determining that the battery of the mobile terminal is not replaced.

In the application, the mobile terminal can determine whether to replace the battery according to the serial number of the battery or the number of times of full charge and discharge of the battery, and the charging limit control operation of the battery is not executed under the condition of replacing the battery; only in the case where it is determined that the battery is not replaced, the battery charging limit control operation is performed, so that the battery at risk of abnormality can be effectively charged limit controlled. Avoiding meaningless charging limit control operation on the new battery and avoiding error experience of timely using the new battery and still displaying reminding information for reminding the user that the battery is abnormal. Meanwhile, the waste of resources for the mobile terminal to execute the charging limit control operation is avoided.

In another possible implementation manner of the first aspect, before the mobile terminal detects that the charge level of the battery reaches the preset charge level threshold, the method further includes:

the mobile terminal obtains the full charge and discharge times of the battery, and determines that the full charge and discharge times of the battery meet the execution times; the execution times are the sum of the full charge discharge times of the battery and the preset delay times.

In the application, the mobile terminal may perform the power limiting control operation when the number of times of full charge and discharge of the battery satisfies the preset number of times according to a comparison determination of the number of times of full charge and discharge of the battery and the delay number of times before performing the power limiting control operation. Thus, the charging limit control operation of the battery is executed for a period of time, and the battery abnormality caused by the mobile terminal is prevented from causing bad use experience to the user due to the fact that the mobile terminal updates the application version according to the configuration update file.

In another possible implementation manner of the first aspect, in a case that the first configuration update file includes the first identifier, the first configuration update file is used to indicate that a battery of the mobile terminal is abnormal; if the first configuration update file does not comprise the first identifier, the first configuration update file is used for indicating that the battery of the mobile terminal is not abnormal; or,

the method comprises the steps that under the condition that a first identifier included in a first configuration update file is a first value, the first configuration update file is used for indicating that a battery of the mobile terminal is abnormal; and under the condition that the first identifier included in the first configuration update file is a second value, the first configuration update file is used for indicating that the battery of the mobile terminal is not abnormal.

In the application, the mobile terminal can characterize that the battery is abnormal by setting a first identifier in the configuration update file; alternatively, the presence of an anomaly in the battery is characterized by setting a first flag in the configuration update file to a first value. After receiving the configuration update file, the mobile terminal can effectively and conveniently determine whether the battery indicated in the configuration update file is abnormal, and is convenient for controlling the charging limit of the subsequent abnormal battery.

In another possible implementation manner of the first aspect, the first configuration update file includes a second identifier, and the second identifier is used to characterize a risk level of the battery; the risk level of the battery comprises a plurality of levels, and different levels correspond to different preset charging electric quantity thresholds; the more serious the battery abnormality represented by the risk level is, the smaller the preset charge quantity threshold value is.

In the application, the mobile terminal can execute the power limiting control operation of charging the corresponding battery according to different risk grades of the battery, namely, execute the power limiting operation corresponding to the charging power thresholds corresponding to different grades, execute the corresponding operation according to the severity degree of the battery abnormality, and further reduce the risk of accidents possibly caused by short circuit of the battery in the abnormal battery charging process.

In another possible implementation manner of the first aspect, in a case that a preset condition is met, the method further includes:

the mobile terminal outputs prompt information; the prompt information is used for prompting the user that the battery is abnormal.

In this application, mobile terminal can also remind the user that there is the abnormality in battery through output prompt message for the user can in time perceive the actual conditions of battery, carries out the potential safety hazard that changes battery or other operations and avoids unusual battery to cause.

In another possible implementation manner of the first aspect, the first configuration update file includes a second identifier, and the second identifier is used to characterize a risk level of the battery; the risk level of the battery comprises a plurality of levels, and different levels correspond to different preset charging electric quantity thresholds; the more serious the battery abnormality of the risk level characterization is, the higher the reminding level of the prompt information is.

The mobile terminal may also be used to prompt the user to replace the battery by means of strobing, outputting a prompting audio signal, or the like. The prompt information with medium prompt level can be used for prompting the user that the battery needs to be replaced. The prompt information with lower prompt level can be used for prompting the user that the battery is abnormal, etc.

In the application, the mobile terminal can execute the power limiting control operation of charging the corresponding battery according to different risk grades of the battery, namely, the mobile terminal outputs prompt information with different degrees corresponding to different grades, and the prompt information has different degrees of reminding to the user, so that the aim of reminding the user that the battery is abnormal or the battery needs to be replaced can be effectively achieved.

In another possible implementation manner of the first aspect, in a case where a battery of the mobile terminal is replaced, the method further includes:

The mobile terminal deletes all parameters except the version number in the configuration update file of the second storage space.

In the application, the second storage space is the backup area, and the mobile terminal deletes all parameters except the version number in the configuration update file of the backup area, so that the parameters in the configuration update file of the backup area take effect once, and the meaningless limit control operation on the new battery is prevented from being triggered and executed because the configuration update file comprises the parameters such as the first identifier, the application parameter to be updated and the like.

In a second aspect, a method for managing and controlling abnormality of a terminal battery is provided, and the method further includes:

the mobile terminal acquires a first configuration update file; the first configuration update file is used for updating parameters of the mobile terminal and representing whether the battery of the mobile terminal is abnormal or not;

the mobile terminal judges whether the second storage space comprises a second battery serial number or not; the second storage space is a permanent storage space;

if the second storage space comprises a second battery serial number, and the second battery serial number is consistent with the first battery serial number of the current battery, the mobile terminal marks a third mark as a first value; a third identifier is used for representing whether the battery is replaced or not;

if the second battery serial number is inconsistent with the first battery serial number, the mobile terminal marks the third mark as a second value;

If the second storage space does not comprise the second battery serial number, the mobile terminal acquires the full charge and discharge times of the current battery;

if the number of times of full charge and discharge of the current battery is not less than a preset first threshold value, the mobile terminal marks a third mark as a first value;

if the number of times of full charge and discharge of the current battery is smaller than a preset first threshold value, the mobile terminal marks the third mark as a second value.

If the third identifier is a first value, the mobile terminal acquires a first version number of the first configuration update file and a second version number of the second configuration update file; the second configuration update file is a configuration update file stored in the second storage space;

if the first version number is greater than the second version number, the mobile terminal updates the configuration update file stored in the second storage space into a first configuration update file;

if the first version number is not greater than the second version number, the mobile terminal will delete all parameters of the configuration update file stored in the second storage space except the version number.

If the first configuration update file indicates that the battery is abnormal, and the number of times of full charge and discharge of the battery meets the number of times of execution, when the battery of the mobile terminal is in a charging state, the mobile terminal stops charging when detecting that the charging electric quantity of the battery reaches a preset charging electric quantity threshold value.

In the method, the mobile terminal acquires the first configuration update file, performs the charging limit control operation of the battery with abnormality from the dimension of whether the version of the first configuration update file is higher than the version dimension of the historical configuration update file of the backup area, the dimension of whether to replace the battery and the dimension of delaying the charging limit control operation, can effectively avoid accidents possibly caused by short circuit of the risk battery in the charging process, simultaneously avoids the problem that the application version update of the mobile terminal cannot clear the first configuration update file, and does not perform meaningless charging limit control operation on the replaced battery, further avoids the error impression caused by the application version update to the user, and optimizes the use experience of the user from different dimensions.

In a third aspect, a method for managing and controlling abnormality of a terminal battery is provided, and the method is applied to a server, and includes:

the server acquires battery state information of a plurality of mobile terminals. Wherein the battery status information includes a battery serial number and a battery capacity.

The server determines a target battery with abnormality based on battery state information of each mobile terminal; and the server generates a configuration update file of the mobile terminal corresponding to the target battery. The configuration update file is used for updating parameters of the mobile terminal and whether the battery of the mobile terminal is abnormal or not. And the server sends the configuration update file to the mobile terminal corresponding to the target battery.

In a possible implementation manner of the third aspect, the method further includes:

the server determines the risk level of the target battery based on the battery state information of the target battery; the server adds the risk level of the target battery to the corresponding configuration update file.

In a fourth aspect, a mobile terminal is provided that includes a memory, a display screen, a communication module, and one or more processors; the memory, the display screen and the communication module are coupled with the processor; the memory has stored therein computer program code comprising computer instructions which, when executed by the processor, cause the mobile terminal to perform the method according to any of the first aspects described above.

In a fifth aspect, a server is provided, the server comprising a processing center and a database;

the processing center is used for acquiring battery state information of a plurality of mobile terminals; the battery status information includes a battery serial number and a battery capacity; determining a target battery with abnormality based on battery state information of each mobile terminal; generating a configuration update file of the mobile terminal corresponding to the target battery; the configuration update file is used for updating parameters of the mobile terminal and judging whether the battery of the mobile terminal is abnormal or not;

And the database is used for sending the configuration update file to the mobile terminal corresponding to the target battery.

In a possible implementation manner of the fifth aspect, the database is a lightweight cloud database, and the database is configured to send the configuration update file to the mobile terminal corresponding to the target battery in a cloud pushing manner.

In a sixth aspect, there is provided a terminal battery abnormality management system including the mobile terminal as provided in the fourth aspect and the server as provided in the fifth aspect.

In a seventh aspect, there is provided a computer readable storage medium having instructions stored therein that, when run on a mobile terminal, enable the mobile terminal to perform the method of any one of the first and second aspects above; when running on a server, to enable the server to perform the method according to any one of the third aspects above

In an eighth aspect, there is provided a computer program product comprising instructions which, when run on a mobile terminal, enable the mobile terminal to perform the method of any one of the first and second aspects above; which when run on a server, enables a mobile terminal to perform the method of any of the third aspects above.

In a ninth aspect, embodiments of the present application provide a chip comprising a processor for invoking a computer program in a memory to perform a method as in any of the first, second, and third aspects.

It may be appreciated that, the advantages achieved by the mobile terminal according to the fourth aspect, the server according to the fifth aspect, the terminal battery abnormality management system according to the sixth aspect, the computer readable storage medium according to the seventh aspect, the computer program product according to the eighth aspect, and the chip according to the ninth aspect may refer to the advantages of any one of the first aspect and any one of the possible designs thereof, the second aspect and any one of the possible designs thereof, and the third aspect and any one of the possible designs thereof, which are not repeated herein.

Drawings

Fig. 1 is a schematic view of a scenario in which a server interacts with a plurality of mobile terminals according to an embodiment of the present application;

fig. 2 is a schematic structural diagram of a mobile terminal according to an embodiment of the present application;

fig. 3 is a schematic architecture diagram of a mobile terminal according to an embodiment of the present application;

fig. 4 is a flow chart of a method for managing and controlling abnormality of a terminal battery according to an embodiment of the present application;

Fig. 5 is a schematic diagram of a display interface of a mobile terminal according to an embodiment of the present application;

fig. 6 is a flowchart illustrating another method for managing and controlling abnormal terminal battery according to an embodiment of the present application;

fig. 7 is a flowchart illustrating another method for managing and controlling abnormal terminal battery according to an embodiment of the present application;

fig. 8 is a flowchart of another method for managing and controlling abnormal terminal battery according to an embodiment of the present application;

fig. 9 is a flowchart of another method for managing and controlling abnormal terminal battery according to an embodiment of the present application;

fig. 10 is a schematic structural diagram of another mobile terminal according to an embodiment of the present application;

fig. 11 is a schematic structural diagram of a chip system according to an embodiment of the present application.

Detailed Description

In the description of the embodiments of the present application, the terminology used in the embodiments below is for the purpose of describing particular embodiments only and is not intended to be limiting of the present application. As used in the specification of this application and the appended claims, the singular forms "a," "an," "the," and "the" are intended to include, for example, "one or more" such forms of expression, unless the context clearly indicates to the contrary. It should also be understood that in the various embodiments herein below, "at least one", "one or more" means one or more than two (including two). The term "and/or" is used to describe an association relationship of associated objects, meaning that there may be three relationships; for example, a and/or B may represent: a alone, a and B together, and B alone, wherein A, B may be singular or plural. The character "/" generally indicates that the context-dependent object is an "or" relationship.

Reference in the specification to "one embodiment" or "some embodiments" or the like means that a particular feature, structure, or characteristic described in connection with the embodiment is included in one or more embodiments of the application. Thus, appearances of the phrases "in one embodiment," "in some embodiments," "in other embodiments," and the like in the specification are not necessarily all referring to the same embodiment, but mean "one or more but not all embodiments" unless expressly specified otherwise. The terms "comprising," "including," "having," and variations thereof mean "including but not limited to," unless expressly specified otherwise. The term "coupled" includes both direct and indirect connections, unless stated otherwise. The terms "first," "second," and the like are used for descriptive purposes only and are not to be construed as indicating or implying relative importance or implicitly indicating the number of technical features indicated.

In the embodiments of the present application, words such as "exemplary" or "such as" are used to mean serving as examples, illustrations, or descriptions. Any embodiment or design described herein as "exemplary" or "for example" should not be construed as preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary" or "such as" is intended to present related concepts in a concrete fashion.

The battery is a power source of the mobile terminal and can provide stable power for a long time for the mobile terminal such as a mobile phone. The mobile terminal may cause defects in the battery pole piece due to dropping, collision, extrusion, etc. Illustratively, the situation that the battery pole piece is defective includes that large-area bulges appear on the surface of the pole piece, the pole piece is dropped, and the like, and the risk that the battery is in short circuit and spontaneous combustion is increased due to the defect of the battery pole piece.

The existing mobile terminal is usually a non-detachable rechargeable battery, and when the mobile terminal falls, collides, extrudes and the like to possibly cause the defect of a battery pole piece, a user cannot check the specific situation of the battery in time. Even if the battery pole piece is defective, the user can not perceive the mobile terminal with increased risk of spontaneous combustion due to the short circuit of the battery. The battery with the risk of short-circuit spontaneous combustion is extremely likely to cause the excessive temperature or other abnormal performance of the mobile terminal in the normal use process of the mobile terminal or in the charging process of the battery of the mobile terminal, and the mobile terminal is possibly damaged or even fire is generated due to the short-circuit spontaneous combustion of the battery in severe cases, so that great potential safety hazards are brought to users.

The embodiment of the application provides a terminal battery abnormality management and control method, when a mobile terminal meets a power limiting management and control condition, a configuration update file is obtained, and if the configuration update file comprises a first identifier for representing that a battery has risks, the mobile terminal executes power limiting management and control operation on the risk battery. Specifically, when the mobile terminal is in a charging state and the charging electric quantity meets a preset charging electric quantity threshold value, the mobile terminal stops the charging operation and outputs reminding information for reminding a user that the battery is at risk. Therefore, a user can know the specific situation of the risk battery in time, and the mobile terminal automatically triggers the charging limit control, so that accidents possibly caused by short circuit of the risk battery in the charging process can be effectively avoided.

The method for managing and controlling the abnormality of the terminal battery, provided by the embodiment of the invention, can be applied to a scene shown in fig. 1. By way of example, fig. 1 includes a server and a plurality of mobile terminals. The server comprises a processing center and a database.

The processing center can acquire battery state information of a plurality of mobile terminals to carry out statistical analysis so as to determine the mobile terminals with abnormal batteries of the mobile terminals. The plurality of mobile terminals can be the same batch of mobile terminals produced by the same manufacturer; alternatively, the plurality of mobile terminals may be mobile terminals of the same brand; or, the plurality of mobile terminals can also be mobile terminals with positions in a preset area; alternatively, the plurality of mobile terminals may be random or designated plurality of mobile terminals. The processing center obtains battery state information of each mobile terminal, wherein the battery state information can include information such as a battery Serial Number (SN), an actual capacity of the battery, an actual discharge period of the battery, an actual output voltage and an actual output current of the battery. Wherein the processing center can determine the actual resistance of the battery based on the actual output voltage and the actual output current of the battery.

The processing center can analyze the battery abnormality of each mobile terminal according to the battery state information of each mobile terminal, and if one or more battery state information abnormalities exist in a certain mobile terminal, the battery of the mobile terminal is considered to be abnormal. For example, the processing center may determine whether there is an abnormality in the battery of the mobile terminal according to one parameter in the battery state information of the mobile terminal. If the actual capacity of the battery is smaller than the rated capacity of the battery, for example, the battery is considered to be abnormal; or if the actual resistance of the battery is smaller than the rated resistance of the battery, the battery can be considered to be abnormal; alternatively, if the actual discharge cycle of the battery is smaller than the rated discharge cycle of the battery, it can be considered that there is an abnormality in the battery, or the like. Also exemplary, the processing center may determine whether there is an abnormality in the battery of the mobile terminal based on a plurality of parameters of the battery state information of the mobile terminal. For example, if the actual battery capacity is smaller than the rated battery capacity and the actual battery resistance is smaller than the rated battery resistance, it can be considered that there is an abnormality in the battery, and so on.

Optionally, the battery status information further includes parameter information for characterizing whether the mobile terminal is dropped, or the like. The processing center may also determine whether the battery of the mobile terminal is abnormal according to whether the mobile terminal is dropped, or the like. For example, the mobile terminal may obtain, through a sensor of the mobile terminal, information about whether the mobile terminal falls, etc., and report the information to a processing center, where the processing center is configured to perform abnormal analysis of a battery of the mobile terminal. For example, the mobile terminal can detect whether the mobile terminal falls down or not in a short time through a gyroscope sensor and acceleration built in the mobile terminal, and report the actions to a processing center. Thus, when the mobile terminal falls, the processing center can determine that the battery is possibly affected to generate abnormality.

Optionally, the processing center may also detect, through a preset algorithm, whether an abnormality of pole piece missing exists in the battery of the mobile terminal. Wherein, the data required in detection can originate from the mobile terminal.

Optionally, the processing center may also define different levels corresponding to the battery risk according to different severity levels of battery abnormality. For example, if the battery has one abnormal battery state information, the risk level of the battery is regarded as three levels; if the battery has two abnormal battery state information, the risk level of the battery is regarded as a second level; and if at least two battery state information of the battery are abnormal, the risk level of the battery is regarded as one level. The level of risk is greater than the level two and the level of risk is greater than the level three.

Alternatively, the risk level of the processing center determining the battery may also be determined based on the importance level of the battery status information. For example, the importance level of the battery state information is preset, and if the battery state information with the importance level being the first level is abnormal, the risk level of the battery abnormality is considered to be the first level; if the battery state information with the importance level being the second level is abnormal, the battery abnormal risk level is considered to be the second level, and the like. For example, the importance level of the battery capacity is a level, and if the actual battery capacity is smaller than the rated battery capacity and the actual battery capacity is smaller than the preset lower capacity limit, the risk level of the battery is regarded as a level. For example, the importance level of the battery discharge cycle is one level, and if the actual discharge cycle of the battery is smaller than the rated discharge cycle of the battery and the actual discharge cycle of the battery is smaller than the preset lower limit of the discharge cycle, the risk level of the battery is regarded as one level, and so on.

Alternatively, the information about whether the battery is abnormal, the risk level of the battery having the abnormality, and the like may be determined by human judgment. Since the occurrence of an abnormality of the battery belongs to a small probability event, for such a scene where the amount of abnormal data is small, it is possible for the worker to determine whether the battery is abnormal based on battery state information of the battery or the like. Accordingly, the staff may also determine the risk level of the battery based on the case of abnormality of the battery. The battery state information of the battery can be reported to the server by the mobile terminal, and staff can view the information in the server.

After performing the abnormality analysis on the battery of each mobile terminal, the processing center may generate a first identifier (or referred to as a power limit control identifier) for indicating whether the battery of each mobile terminal is abnormal according to whether the battery of each mobile terminal is abnormal. Optionally, in the event of an abnormality in the battery, the processing center may also generate a second identification (or referred to as a risk level identification) that characterizes the risk level of the battery.

For example, the processing center may generate a first identification that, when at a first value, characterizes the battery as having an anomaly; and when the first mark is a second value, the battery is characterized as not having abnormality.

In another implementation, the processing center may generate a first identifier that characterizes that the battery of the mobile terminal is abnormal, that is, if the first identifier is present, the battery is considered to be abnormal; if the first identifier is not available, the battery is considered to be free of abnormality.

In this embodiment, the processing center analyzes the battery based on the battery serial number SN, where the battery serial number SN has a binding relationship with the serial number of the mobile terminal in which it is located.

The database in the server stores configuration update files of each mobile terminal, and the database can send the configuration update files to each mobile terminal to update/upgrade the configuration of the terminal application or the terminal system. The configuration update file may be, for example, a JSON file updated for a configuration corresponding to a system or application. Based on this, the processing center determines the mobile terminal corresponding to the abnormal battery serial number SN from the battery serial number SN. And adding the first identifier and/or the second identifier in the configuration update file of the corresponding mobile terminal. The database issues the configuration update file to the corresponding mobile terminal.

In some embodiments, when the configuration update file characterizes that the battery is abnormal, the mobile terminal is triggered to execute corresponding battery limit control operation. The configuration update file may include a first identifier in the configuration update file, where the first identifier is used to indicate whether the battery has an abnormality, and the value of the first identifier is a first value (a value corresponding to the abnormality of the battery), or the configuration update file includes the first identifier used to indicate that the battery has an abnormality.

In some embodiments, the database of the server may be a lightweight cloud database. The database stores parameters related to the higher update frequency in the configuration update file. Illustratively, the parameters include application level parameters or system level parameters. When such parameters are updated, the database may issue a configuration update file after updating the parameters to the mobile terminal. The mobile terminal receives the configuration update file to update the application or the system. The database transmits configuration update files or updated parameters to a plurality of mobile terminals in a lightweight cloud pushing mode, so that efficient transmission of lightweight data is realized.

The mobile terminal only needs to replace and cover the configuration update file, so that the update of corresponding parameters can be realized, the system update and upgrade of the whole mobile terminal are not needed, and the cloud pushing configuration update file mode also reduces the operation amount of application update or parameter update of the mobile terminal.

Optionally, in some embodiments, the database may push the configuration update file only to the mobile terminal with an abnormal battery, or the designated mobile terminal, so as to implement fixed-point pushing of the mobile terminal, and avoid transmission of a meaningless configuration update file of the mobile terminal without an abnormal battery.

The mobile terminal in the embodiment of the present application may be a portable computer (such as a mobile phone), a tablet computer, a notebook computer, a personal computer (personal computer, PC), a wearable mobile terminal (such as a smart watch), an augmented reality (augmented reality, AR) \virtual reality (VR) device, and the following embodiments do not limit the specific form of the mobile terminal in particular.

Referring to fig. 2, a block diagram of a mobile terminal (e.g., mobile terminal 100) is provided in an embodiment of the present application. Among other things, the mobile terminal 100 may include a processor 310, an external memory interface 320, an internal memory 321, a universal serial bus (universal serial bus, USB) interface 330, a charge management module 340, a power management module 341, a battery 342, an antenna 1, a communication module 360, an audio module 370, a sensor module 380, a display 390, and the like. Wherein the sensor module 380 may include a temperature sensor or the like.

The structure illustrated in the embodiment of the present invention does not constitute a limitation of the mobile terminal 100. More or fewer components than shown may be included, or certain components may be combined, or certain components may be split, or different arrangements of components. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

Processor 310 may include one or more processing units. For example, the processor 310 may include an application processor (application processor, AP), a modem processor, a graphics processor (graphics processing unit, GPU), an image signal processor (image signal processor, ISP), a controller, a memory, a video codec, a digital signal processor (digital signal processor, DSP), a baseband processor, and/or a neural network processor (neural-network processing unit, NPU), etc. Wherein the different processing units may be separate devices or may be integrated in one or more processors.

The controller may be a decision maker that directs the various components of the mobile terminal 100 to coordinate their operations in accordance with instructions. Is the neural and command center of the mobile terminal 100. The controller generates an operation control signal according to the instruction operation code and the time sequence signal to finish the control of instruction fetching and instruction execution.

A memory may also be provided in the processor 310 for storing instructions and data. In some embodiments, memory in the processor 310 is a cache memory that holds instructions or data that the processor 310 has just used or recycled. If the processor 310 needs to reuse the instruction or data, it may be called directly from the memory. Repeated accesses are avoided and the latency of the processor 310 is reduced, thereby improving the efficiency of the system.

In some embodiments, the processor 310 may include an interface. The interfaces may include an integrated circuit (inter-integrated circuit, I2C) interface, an integrated circuit built-in audio (inter-integrated circuit sound, I2S) interface, a pulse code modulation (pulse code modulation, PCM) interface, a universal asynchronous receiver transmitter (universal asynchronous receiver/transmitter, UART) interface, a mobile industry processor interface (mobile industry processor interface, MIPI), a general-purpose input/output (GPIO) interface, a SIM interface, and/or a USB interface, among others.

The interface connection relationship between the modules illustrated in the embodiment of the present invention is only schematically illustrated, and does not limit the structure of the mobile terminal 100. The mobile terminal 100 may employ different interfacing means, or a combination of interfacing means in the embodiments of the present invention.

The charge management module 340 is configured to receive a charge input from a charger. The charger can be a wireless charger or a wired charger. In some wired charging embodiments, the charge management module 340 may receive a charging input of a wired charger through the USB interface 330. In some wireless charging embodiments, the charge management module 340 may receive wireless charging input through a wireless charging coil of the mobile terminal 100. The charging management module 340 may also supply power to the mobile terminal 100 through the power management module 341 while charging the battery 342.

The power management module 341 is configured to connect the battery 342, the charge management module 340 and the processor 310. The power management module 341 receives input from the battery 342 and/or the charge management module 340 to power the processor 310, the internal memory 321, the external memory interface 320, the display 390, the communication module 360, and the like. The power management module 341 may also be configured to monitor battery parameters such as battery capacity, battery cycle times, battery health (leakage, impedance), etc.

In some embodiments, the power management module of the mobile terminal may report the monitored parameters of the battery to the processor, and the processor may report the parameters of the battery to the server through the communication module to form battery status information; therefore, the server can analyze the battery abnormality of the mobile terminal according to the battery state information reported by the mobile terminal.

In some embodiments, the power management module 341 may also be disposed in the processor 310. In some embodiments, the power management module 341 and the charge management module 340 may also be provided in the same device.

The wireless communication function of the mobile terminal 100 can be implemented by the antenna 1, the communication module 360, a modem, a baseband processor, and the like.

The antenna 1 is used for transmitting and receiving electromagnetic wave signals. Each antenna in the mobile terminal 100 may be configured to cover a single or multiple communication bands. Different antennas may also be multiplexed to improve the utilization of the antennas. For example: the cellular network antennas may be multiplexed into wireless local area network diversity antennas. In some embodiments, the antenna may be used in conjunction with a tuning switch.

The modem may include a modulator and a demodulator. The modulator is used for modulating the low-frequency baseband signal to be transmitted into a medium-high frequency signal. The demodulator is used for demodulating the received electromagnetic wave signal into a low-frequency baseband signal. The demodulator then transmits the demodulated low frequency baseband signal to the baseband processor for processing. The low frequency baseband signal is processed by the baseband processor and then transferred to the application processor. The application processor outputs sound signals through an audio device or displays images or video through the display 390. In some embodiments, the modem may be a stand-alone device. In some embodiments, the modem may be provided in the same device as the other functional modules, independent of the processor 310.

The communication module 360 may provide a communication processing module that is applied to the mobile terminal 100 and includes solutions of wireless communication such as wireless local area network (wireless local area networks, WLAN) (e.g., wireless fidelity (wireless fidelity, wi-Fi) network), bluetooth (BT), global navigation satellite system (global navigation satellite system, GNSS), frequency modulation (frequency modulation, FM), near field wireless communication technology (near field communication, NFC), infrared technology (IR), and the like. The communication module 360 may be one or more devices integrating at least one communication processing module. The communication module 360 receives electromagnetic waves via the antenna 1, modulates the electromagnetic wave signals and filters the signals, and transmits the processed signals to the processor 310. The communication module 360 may also receive a signal to be transmitted from the processor 310, frequency modulate it, amplify it, and convert it to electromagnetic waves for radiation via the antenna 1.

In some embodiments, the antenna 1 and the communication module 360 of the mobile terminal 100 are coupled such that the mobile terminal 100 may communicate with a network and other devices through wireless communication techniques. The wireless communication techniques may include the Global System for Mobile communications (global system for mobile communications, GSM), general packet radio service (general packet radio service, GPRS), code division multiple access (code division multiple access, CDMA), wideband code division multiple access (wideband code division multiple access, WCDMA), time division code division multiple access (time-division code division multiple access, TD-SCDMA), long term evolution (long term evolution, LTE), BT, GNSS, WLAN, NFC, FM, and/or IR techniques, among others. The GNSS may include a global satellite positioning system (satellite based augmentation systems, SBAS), a global navigation satellite system (global navigation satellite system, GLONASS), a beidou satellite navigation system (BeiDou navigation satellite system, BDS), a Quasi zenith satellite system (Quasi-Zenith satellite system, QZSS) and/or a satellite based augmentation system (satellite based augmentation systems, SBAS).

In some embodiments, the mobile terminal communicates with the server through a communication module. By way of example, the communication means of the mobile terminal with the server may include Wi-Fi, GNSS, cellular network, and the like.

The mobile terminal 100 implements display functions through a GPU, a display screen 390, and an application processor, etc. The GPU is a microprocessor for image processing, connected to the display 390 and the application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. Processor 310 may include one or more GPUs that execute program instructions to generate or change display information.

The display 390 is used to display images, videos, and the like. The display 390 includes a display panel. The display panel may employ a liquid crystal display (liquid crystal display, LCD), an organic light-emitting diode (OLED), an active-matrix organic light emitting diode (AMOLED), a flexible light-emitting diode (flex), a mini, a Micro-OLED, a quantum dot light-emitting diode (quantum dot light emitting diodes, QLED), or the like. In some embodiments, the mobile terminal 100 may include 1 or N displays 390, N being a positive integer greater than 1.

In this embodiment, the display 390 may display a reminder message for reminding the user that there is an abnormality in the current battery. Optionally, the reminding information can also be used for reminding the user to timely replace the abnormal battery, and the like.

The external memory interface 320 may be used to connect an external memory card, such as a Micro SD card, to enable expansion of the memory capabilities of the mobile terminal 100. The external memory card communicates with the processor 310 through an external memory interface 320 to implement data storage functions. For example, files such as music, video, etc. are stored in an external memory card.

The internal memory 321 may be used to store computer executable program code comprising instructions. The processor 310 executes various functional applications of the mobile terminal 100 and data processing by executing instructions stored in the internal memory 321. The memory 321 may include a stored program area and a stored data area. The storage program area may store an application program (such as a sound playing function, an image playing function, etc.) required for at least one function of the operating system, etc. The storage data area may store data (e.g., audio data, phonebook, etc.) created during use of the mobile terminal 100, and the like. In addition, the memory 321 may include high-speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, other volatile solid-state storage device, universal flash memory (universal flash storage, UFS), and the like.

The mobile terminal 100 may implement audio functions through the audio module 370, as well as speakers, a receiver, a microphone, an earphone interface, an application processor, and the like, which are included in the audio module. Such as music playing, recording, etc.

The audio module 370 is used to convert digital audio information into an analog audio signal output and also to convert an analog audio input into a digital audio signal. The audio module 370 may also be used to encode and decode audio signals. In some embodiments, the audio module 370 may be disposed in the processor 310, or some of the functional modules of the audio module 370 may be disposed in the processor 310.

The sensor module 380 includes a temperature sensor, a gyroscope sensor, an acceleration sensor, and the like.

Wherein a temperature sensor may be used to detect temperature. Alternatively, in some embodiments, the mobile terminal 100 may detect the temperature of the mobile terminal through a temperature sensor. For example, in the charging process of the mobile terminal, if the mobile terminal determines that the battery is abnormal, the mobile terminal can detect the temperature in time and perform more timely reaction while performing power limiting control. For example, when the temperature of the mobile terminal is not considered, the mobile terminal determines that the configuration update file includes a first identifier (or when the first identifier is a first value) indicating that the battery is abnormal, and in the process of charging the mobile terminal, the mobile terminal stops the charging operation after determining that the charging electric quantity reaches a preset threshold value. After considering the temperature of the mobile device, the mobile terminal determines that the configuration update file comprises a first identifier representing that the battery is abnormal, and in the process of charging the mobile terminal, if the temperature of the mobile terminal reaches a temperature threshold or the charging electric quantity reaches a preset threshold, the mobile terminal executes the operation of stopping charging. And the mobile terminal is subjected to limit management from the temperature and charging lighting of the mobile terminal, so that the risk possibly brought by abnormal batteries is effectively reduced.

The gyro sensor may be used to determine a motion gesture of the mobile terminal 100. In some embodiments, the angular velocity of the mobile terminal 100 about three axes (i.e., x, y, and z axes) may be determined by a gyroscopic sensor. The acceleration sensor may detect the magnitude of acceleration of the mobile terminal 100 in various directions (typically three axes). The magnitude and direction of gravity may be detected when the mobile terminal 100 is stationary.

In some embodiments, a gyro sensor and an acceleration sensor may be used to detect whether a fall, a drop, etc. of the mobile terminal 100 occurs. If the mobile terminal 100 falls, etc., it is considered that the battery of the mobile terminal 100 may have pole piece falling or other abnormal problems.

The software system of the mobile terminal 100 may employ a layered architecture, an event driven architecture, a micro-core architecture, a micro-service architecture, or a cloud architecture. In the embodiment of the invention, an Android system with a layered architecture is taken as an example, and the software structure of the mobile terminal 100 is illustrated.

Fig. 3 is a software structural block diagram of the mobile terminal 100 according to the embodiment of the present invention. The layered architecture divides the software into several layers, each with distinct roles and branches. The layers communicate with each other through a software interface. In some embodiments, the Android system includes an application layer, a hardware abstraction layer (hardware abstraction layer, HAL), and a kernel layer (kernel).

The hardware abstraction layer HAL and the application program layer transmit data or instructions through interface description languages (interface description language, HIDL).

The application layer may include a series of application packages. As shown in fig. 3, the application package may include a housekeeping application. The manager application is used for management of system files or applications of the mobile terminal. Illustratively, the housekeeping application may expose the operating conditions of the system, such as memory usage of the system, performance scores of the system, and so forth; the housekeeping application may also manage the storage space of the system, e.g., scan, clean up, etc., garbage/duplicate files in the storage space. The manager application can also carry out authority management on each application in the mobile terminal, statistics and display the use condition of each application in the mobile terminal and the like. Illustratively, the display interface of the manager application may statistically display the time of day of each application, the amount of memory occupied by each application, and so on.

Optionally, the application layer may also include applications for cameras, gallery, calendar, phone, map, navigation, WLAN, bluetooth, music, video, short messages, etc.

In some embodiments, the configuration update file may be a configuration update file of the system, i.e., included in the configuration update file are parameters to be updated at the system level. After receiving the configuration update file, the mobile terminal covers the configuration update file to replace the existing configuration update file in the system, so as to realize the parameter update operation of the system level.

In still other embodiments, the configuration update file may also be a configuration update file of an application, that is, the configuration update file includes parameters to be updated at an application level, for example, the parameters are parameters to be updated of a housekeeping application. And after the mobile terminal receives the configuration update file, the configuration update file is covered and replaced with the configuration update file stored in the manager application, so that the parameter update operation of the manager application is realized.

The configuration update file stored in the database of the server is identical to the configuration update file stored in the manager application in format and has the same function.

Since the system types or system versions of the respective mobile terminals are different and the versions of the applications are mostly the same, the cost of the parameter update at the application level is lower than the cost of the parameter update at the system level. Based on this, the terminal battery abnormality management and control method provided in the embodiment is deployed in an application layer, and the method is described by taking a manager application as an example.

In some embodiments, the configuration update file is illustrated as a configuration update file for a housekeeping application. Referring to fig. 3, the housekeeping application includes a power limiting control module, an algorithm library and other business modules.

The power limiting management and control module is used for receiving the configuration update file of the database cloud pushing and carrying out corresponding parameter update.

The electricity limiting management and control module is also used for identifying whether the configuration update file characterizes battery abnormality. For example, when the configuration update file includes a first identifier for characterizing battery abnormality; or when the first identifier in the configuration update file is a first value, executing the power limiting control operation. And executing the electricity limiting control operation based on the electricity limiting control strategy corresponding to the second identifier under the condition that the configuration update file is determined to comprise the second identifier.

The algorithm library provides a limit control strategy that performs a limit control operation. For example, the method comprises the step of limiting control strategies corresponding to different risk levels.

Other business modules may implement functions other than power-limited management operations, such as application management functions, system management functions, and the like.

The kernel layer is a layer between hardware and software.

In this embodiment, the core layer includes a system-on-chip and a battery chip. The system-level chip is used for controlling the battery chip to execute corresponding power limiting control operation according to the power limiting control instruction issued by the power limiting control module. For example, after receiving the instruction of limiting the power control, the system-level chip obtains the charge quantity of the battery when the battery is in a charging state. When the charging electric quantity meets a preset charging electric quantity threshold value, the battery chip is controlled to stop charging operation, and the electricity limiting control is realized. The system-on-chip may also obtain battery parameters from the battery chip. The battery parameters may include, for example, a battery serial number, an operating state of the battery, a number of full-charge discharges of the battery, an actual capacity of the battery, a discharge period of the battery, and the like. The system-on-chip may report battery parameters to a power limit control module of a housekeeping application. The electricity limiting management and control module can report the battery parameters to the server through the communication module to form battery state information.

Optionally, in some embodiments, the kernel layer may also include display drivers, audio drivers, sensor drivers, power drivers, and the like.

Referring to fig. 3, in this embodiment, the lightweight cloud database sends the configuration update file to the mobile terminal in a fixed point in a cloud pushing manner. And the power limiting management and control module of the manager application of the mobile terminal updates the related parameters according to the configuration update file. If the configuration update file comprises a first identification (or when the first identification is a first value) for representing that the battery is abnormal, the electricity limiting control module determines an electricity limiting control strategy through an algorithm library and sends an electricity limiting control instruction carrying the electricity limiting control strategy to a system-in-chip of a kernel layer through an HIDL interface. When the battery is in a charging state, the system-level chip controls the battery chip to execute corresponding power limiting control operation according to a power limiting control strategy, so that the control operation on the abnormal battery in the charging process of the mobile terminal is realized.

Optionally, the manager application of the mobile terminal may also output information on the display interface. The reminding information can be used for reminding the user of the abnormality of the battery or reminding the user of timely battery replacement and the like.

In some embodiments, a method for managing and controlling abnormal battery of a terminal provided in the embodiments of the present application is described with reference to fig. 4, where the method includes:

s201, the mobile terminal acquires the configuration update file.

The mobile terminal obtains the configuration update file in order to determine whether the configuration update file characterizes the battery as having an abnormality. For example, whether the battery is abnormal may be determined by whether the first identification is included in the configuration update file; alternatively, whether the first identifier in the configuration update file is a first value determines whether the battery is abnormal. Based on a scene in which it is necessary to determine whether the battery is abnormal, a limit control condition is determined.

In some embodiments, if the server determines that the battery of the mobile terminal is abnormal, the server issues a configuration update file to the mobile terminal including a first identifier that characterizes the battery abnormality. Based on the scene, the mobile terminal acquires the configuration update file and then acquires the configuration update file issued by the server.

In some embodiments, the mobile terminal may store the configuration update file in a local storage space (first storage space) of the housekeeping application when receiving the configuration update file issued by the server.

Alternatively, in some embodiments, the configuration update file in the local storage space of the housekeeping application may be purged due to the version update/parameter update of the housekeeping application, and the mobile terminal may store the configuration update file to the backup area (second storage space) after storing the configuration update file to the local storage space of the housekeeping application.

In some embodiments, the abnormal battery needs to be controlled by limiting electricity during charging, so when the mobile terminal charges the battery, it is required to determine whether the battery is the battery with the abnormality. Based on this scenario, when the mobile terminal generates a charging interrupt event, the mobile terminal is in a charging state, and the mobile terminal obtains the configuration update file from the local storage space of the housekeeper application.

The power supply driver can report the charging interruption event to a system-level chip of the mobile terminal through the battery chip, so that the mobile terminal can realize the purpose of detecting the charging interruption event.

In some embodiments, the mobile terminal performs operations such as system restart or manager application service restart, which may also be due to an abnormality in the battery, so that further determination needs to be performed. Based on this scenario, the mobile terminal obtains the configuration update file from the backup area. This is because the operations such as system restart or manager application service restart may remove the configuration update file stored in the local storage space of the manager application, and thus, the mobile terminal may directly obtain the configuration update file from the backup area in this scenario.

In some embodiments, in the case where the mobile terminal performs a parameter update of a manager application of the mobile terminal, the parameter update of the target application may clear a configuration update file stored in a local storage space of the manager application, so that the mobile terminal obtains the configuration update file in such a scenario, and may also obtain the configuration update file from the backup area.

In some embodiments, meeting the electronic control condition may further include the temperature of the mobile terminal reaching a preset temperature threshold, and the temperature of the mobile terminal being too high may also affect the battery. Based on the scene, if the mobile terminal detects that the temperature of the mobile terminal reaches the preset temperature threshold value through the temperature sensor, the mobile terminal can acquire a configuration update file from a local storage space or a backup area of a housekeeping application. When the temperature of the mobile terminal reaches a preset temperature threshold and the configuration update file comprises a first identifier for representing battery abnormality, triggering to execute the power limiting control operation, so that potential safety hazards caused by overhigh temperature to battery charging are avoided.

In some embodiments, the configuration update file may also include application parameters to be updated, and the like. After receiving the configuration update file issued by the server, the mobile terminal can perform corresponding parameter update based on the application parameters to be updated.

S202, the mobile terminal judges whether the configuration update file represents battery abnormality.

In one implementation, if the configuration update file includes the first identifier, the configuration update file characterizes that the battery is abnormal, and the mobile terminal needs to perform charging limit control of the battery, then S203 is executed. If the configuration update file does not include the first identifier, the configuration update file characterizes that the battery is not abnormal, meaning that the battery of the mobile terminal is a non-abnormal battery, and charging limit control of the battery is not needed, S204 is executed.

Alternatively, in another implementation, the mobile terminal may determine whether the battery is abnormal by configuring a value of the first identifier included in the update file. For example, when the first flag is a first value, the battery abnormality is characterized. Illustratively, the first value may be 1. When the first flag is at the second value, which may be, for example, 0, the battery is characterized as normal. In some embodiments, if the first identifier in the configuration update file is a first value, meaning that there is an anomaly in the battery; if the first flag in the configuration update file is the second value, which means that the battery is not an abnormal battery, the mobile terminal does not need to perform the power limiting control operation, and S204 is performed.

And S203, when the mobile terminal is in a charging state, if the detected battery charging quantity meets a preset charging quantity threshold value, stopping the charging operation.

In some embodiments, the configuration update file characterizes battery anomalies, meaning that the battery of the mobile terminal is a risk battery of anomalies through statistical analysis by the server. The risk battery with abnormality has low accident probability when not being charged; there is a risk that the battery may be easily damaged due to short-circuiting when the battery is charged.

In this embodiment, the configuration update file characterizes the battery abnormality, and the mobile terminal determines that the current battery is the battery having the abnormality. When the battery is detected to be in a charged state, the execution of the power limiting control operation of the battery is triggered. Specifically, when it is detected that the charge amount of the battery reaches a preset charge amount threshold, the charging operation of the battery is stopped.

When the mobile terminal is plugged into the charger, the power supply drive can generate a charging interruption event, the power supply drive can report the charging interruption event to a system-level chip of the mobile terminal through the battery chip, the system-level chip reports the charging interruption event to the electricity limiting control module, and the electricity limiting control module continuously judges whether the charging electric quantity reaches a preset charging electric quantity threshold value or not after receiving the charging interruption event. When the electricity limiting control module detects that the charging electric quantity reaches a preset charging electric quantity threshold value, a charging stopping instruction is generated; the electricity limiting management and control module sends a charging stopping instruction to the system-level chip, and the system-level chip sends the charging stopping instruction to the battery chip, so that the battery chip responds to the charging stopping instruction to stop the charging operation of the battery.

S204, the mobile terminal does not execute the power limiting control operation.

In some embodiments, the mobile terminal need not perform the power limiting control operation this time, but there may already be a historical power limiting control strategy in the battery chip of the mobile terminal. That is, the backup area of the mobile terminal may further include a history configuration update file indicating an abnormality of the battery, and the mobile terminal may further clear the history configuration update file in the backup area in order to avoid meaningless triggering of the power limiting operation of the new battery by the history configuration update file. From the module level, the mobile terminal can also send instructions for clearing the limit control strategy to the battery chip through the system-in-chip.

In some embodiments, if the first identifier is included in the configuration update file, or if the first identifier is a first value, the mobile terminal may further determine whether the user replaces the battery, that is, in this case, after performing S202, it further includes:

s205, the mobile terminal judges whether to replace the battery.

In some embodiments, battery parameters such as a battery serial number may also be included in the configuration update file. The mobile terminal can acquire the first serial number of the current battery through the battery chip, compares the first serial number of the battery with the second serial number of the battery in the stored configuration update file of the backup area, and if the first serial number of the battery is consistent with the second serial number of the battery, the mobile terminal is indicated that the battery is not replaced; if the batteries are inconsistent, the battery of the mobile terminal with the abnormality is replaced.

If the mobile terminal does not replace the battery, the mobile terminal performs S203.

In some embodiments, the mobile terminal does not replace the battery, meaning that the current battery of the mobile terminal remains the server-determined risk battery for the presence of anomalies. In this case, the mobile terminal needs to perform a power limiting management operation on the battery. That is, when the battery is in a charged state, the mobile terminal continuously determines whether the charged electric quantity reaches a preset charged electric quantity threshold. When the charging electric quantity reaches a preset charging electric quantity threshold value, the mobile terminal sends a charging stopping instruction to the battery chip through the system-level chip, and the battery chip responds to the charging stopping instruction to stop the charging operation of the battery.

If the mobile terminal has replaced the battery, the mobile terminal performs S204.

The mobile terminal has changed the battery, means that the current battery of the mobile terminal is not the risk battery with the abnormality determined by the server, the changed battery is generally a new battery, and the occurrence probability of the abnormality is very small. In this case, the mobile terminal does not perform the limit electric control operation.

S206, the mobile terminal outputs prompt information.

In some embodiments, when the mobile terminal determines that the configuration update file characterizes the battery as abnormal and the mobile terminal does not replace the battery, the mobile terminal may also send a prompt message on the display interface to remind the user that the battery is abnormal or that the battery needs to be replaced. Referring to fig. 5, a housekeeper application of the mobile terminal outputs a prompt 501 at a current display interface (lock screen interface) of the mobile terminal. The prompt 501 includes prompt content for prompting the user to go to the service center to replace the battery. In this embodiment, the mobile terminal outputs the reminding information, so that the user can sense that the battery is abnormal and further perform battery maintenance or replacement processing, thereby avoiding accidents caused by abnormal battery caused by lack of sensing of the battery abnormality by the user.

In the embodiment of the present application, after the mobile terminal obtains the configuration update file, when a preset condition is satisfied, for example, when the configuration update file characterizes that the battery is abnormal or when the configuration update file characterizes that the battery is abnormal and the battery is not replaced, the mobile terminal performs a power limiting management and control operation on the risk battery. Specifically, when the charging power meets a preset charging power threshold while the mobile terminal is in a charging state, the mobile terminal stops the charging operation. Therefore, the mobile terminal automatically triggers the charging electricity limiting control, and accidents possibly caused by short circuit of the risk battery in the charging process can be effectively avoided.

In some embodiments, in the event of an abnormality in the battery, a second identification may also be included in the configuration update file. Wherein the second identifier is used to characterize a risk level of the abnormal battery, the risk level referring to a severity of the battery abnormality. As described in the above embodiments, the risk level may be determined by the server processing center from the battery state information of the battery; the risk level may also be set manually according to the actual condition of the battery. For example, the risk level of the battery may include a first level, a second level, and a third level, where the first level is set to be higher than the second level, and the second level is set to be higher than the third level. The second identifier may have a plurality of different values for characterizing different risk levels. If the second mark is the first value, the characterization risk level is the first level; when the second mark is a second value, the characterization risk level is a second level; and when the second mark is a third value, the characterization risk level is three-level. Therein, the first value may be 0, the second value may be 1, and the third finger may be 2, as examples.

In step S203, the mobile terminal may specifically execute the power limiting control operation corresponding to the risk level according to the risk level represented by the second identifier.

For example, according to the second identifier, the mobile terminal may perform the case that the charging operation is stopped when the detected charging amount of the battery meets the preset threshold value, where the case may include:

if the second identifier represents that the risk level is one level, which means that the risk level of the battery with abnormality is extremely high, in this case, the power limiting control policy corresponding to the risk level of the first level may include that the mobile terminal executes the charging stopping operation when detecting that the charging capacity of the battery reaches the first charging capacity threshold.

The first charge amount threshold may be understood as a minimum upper limit value of the charge amount in the electric power limiting control. For example, the first charge level threshold may be 30%, 40% of the actual total capacity of the battery.

That is, if the second identifier represents that the risk level is at the first level, the mobile terminal stops the charging operation after the battery charge level reaches 30% when the mobile terminal is in the charging state.

In some embodiments, there may be a case where the charging power of the mobile terminal is greater than or equal to the first charging power threshold value when the mobile terminal starts charging. In this case, the mobile terminal does not directly perform the charging operation, that is, the mobile terminal is in a state of not being charged even if the user inserts the mobile terminal into the charging power source. In this way, the potential safety hazard possibly caused by the battery with extremely high risk in the charging process is avoided to a great extent.

Further, S206 the prompting message output by the mobile terminal on the display screen is the first prompting message. Here, the first reminding information is used for reminding the user to replace the abnormal battery as soon as possible.

In some embodiments, if the second identifier characterizes that the risk level is two, which means that there is a higher risk level of the abnormal battery, in this case, the power limiting control policy corresponding to the risk level of two may include that the mobile terminal performs the charging stopping operation when detecting that the charging power of the battery reaches the second charging power threshold.

The second charge level threshold is greater than the first charge level threshold. For example, the second charge level threshold may be 50%, 60% of the actual total capacity of the battery. The second charge level threshold is greater than the first charge level threshold.

That is, if the second identifier represents that the risk level is two, the mobile terminal stops the charging operation after the battery charge level reaches 50% when the mobile terminal is in the charging state.

In some embodiments, similarly, there may be a case where the charging power of the mobile terminal is already greater than or equal to the second charging power threshold value when the mobile terminal starts charging. In this case, the mobile terminal does not directly perform the charging operation, that is, the mobile terminal is in a state of not being charged even if the user inserts the mobile terminal into the charging power source. In this way, potential safety hazards possibly caused by batteries with higher risk degree in the charging process are avoided to a great extent.

Further, S206 the prompting message output by the mobile terminal on the display screen is the second prompting message. Here, the second reminding information is used for reminding the user that the battery has abnormality and needs to be replaced. It should be noted that, the degree of urgency of the user prompted by the first reminding information to update the battery is higher than that of the second reminding information.

In some embodiments, if the second identifier characterizes that the risk level is three, which means that the risk level of the battery with abnormality is low, in this case, the power limiting control policy corresponding to the risk level of three may include that the mobile terminal performs the charging stopping operation when detecting that the charging power of the battery reaches the third charging power threshold.

The third charge capacity threshold is greater than the second charge capacity threshold. For example, the third charge level threshold may be 70%, 80% of the actual total capacity of the battery. The third charge level threshold is greater than the second charge level threshold.

That is, if the second identifier represents that the risk level is three, the mobile terminal stops the charging operation after the battery charge level reaches 70% when the mobile terminal is in the charging state.

In some embodiments, similarly, there may be a case where the charging power of the mobile terminal is already greater than or equal to the third charging power threshold value when the mobile terminal starts charging. In this case, the mobile terminal does not directly perform the charging operation, that is, the mobile terminal is in a state of not being charged even if the user inserts the mobile terminal into the charging power source. In this way, the potential safety hazard possibly caused by the battery with lower risk degree in the charging process is avoided to a great extent.

Further, the prompt information output by the mobile terminal on the display screen in S206 is a third prompt information. Here, the third reminding information is used for reminding the user that the battery is abnormal.

It should be noted that the risk level is not limited to three levels, and may include two levels, four levels, five levels, and the like according to actual situations. Accordingly, different electronic limiting management strategies corresponding to different risk levels can be set. The power limiting control strategy comprises charging power thresholds corresponding to different levels and reminding information required to be output by the mobile terminal under the different levels. The higher the risk level is, the higher the severity of the battery risk is, the smaller the corresponding charging electric quantity threshold value is, and the higher the reminding level of the output reminding information is.

In some embodiments, if the configuration update file is a configuration update file of the application, that is, the configuration update file includes parameters to be updated of the application. After the mobile terminal receives the configuration update file, the configuration update file may be stored and parameter updates of the application may be performed based on the stored configuration update file. When the parameters of the application are updated, the updated application version will cover the old application version, and the stored configuration update file will be cleared by the cover. That is, the configuration update file received by the mobile terminal may be deleted, so that the mobile terminal cannot perform the corresponding battery charging limit control operation based on the first identifier in the configuration update file. For such a scenario, the present embodiment provides a method for managing and controlling abnormality of a terminal battery, referring to fig. 6, including:

S301, the mobile terminal acquires a first configuration update file.

In the embodiment referring to S201, the description of this embodiment is omitted.

S302, the mobile terminal judges whether the first version number is larger than the second version number, and if so, S303 is executed; if not, S304 is performed.

The first version number is a version number of the first configuration update file. The second version number is a version number of a second configuration update file, which may be a configuration update file stored in the backup area.

And the mobile terminal judges the first version number of the first configuration update file and the second version of the second configuration update file, if the first version number is larger than the second version number, the mobile terminal indicates that the parameters in the configuration update file change, the version of the first configuration update file is newer than the version of the second configuration update file, and S303 is executed. If the first version number is not greater than the second version number, in practical cases, the version of the first configuration update file is not greater than the version of the second configuration update file, including that the version of the first configuration update file is identical to the version of the second configuration update file, in this case, it is indicated that no update change occurs in parameters in the configuration update file, and S304 is executed.

S303, the mobile terminal replaces the configuration update file stored in the backup area with the first configuration update file.

Generally, after receiving a configuration update file issued by a server, a mobile terminal stores the configuration update file in a local storage space of a housekeeper application, and after performing an application version update operation based on the configuration update file, the update operation causes the configuration update file in the storage space of the housekeeper to be cleared. This may affect the mobile terminal to perform battery charging limit management operations based on the configuration update file.

In some embodiments, if the mobile terminal is a first configuration update file obtained from the server or the first storage space, the first configuration update file needs to be backed up to the backup area; if the mobile terminal is the first configuration update file obtained from the backup area, the mobile terminal may directly execute the step of S304 without executing the steps of S302 and S303.

Based on the above, the mobile terminal backs up the configuration update file to the permanent backup area on the basis of storing the configuration update file in the local storage space of the housekeeper application, so that the effect of limiting power control operation of reading the configuration update file from the backup area to charge the battery can be achieved even if the application version is updated based on the configuration update file.

In some embodiments, the backup area is a permanent backup area of the mobile terminal. Illustratively, the permanent backup area may be a system image path of the mobile terminal; or may be a memory space of a designated register of the mobile terminal.

In this embodiment, the version of the first configuration update file is greater than that of the second configuration update file, which indicates that the parameters of the configuration update file change, and the configuration update file of the backup area needs to be replaced accordingly. Therefore, the mobile terminal stores the first configuration update file into the backup area, and timely update of the configuration update file of the backup area is realized.

S304, the mobile terminal judges whether the first configuration update file represents battery abnormality. If yes, then S305 is performed; if not, S306 is performed.

And storing the first configuration update file in the backup area at the mobile terminal, and judging whether the first configuration update file comprises the first identification or not by the mobile terminal.

Alternatively, in some embodiments, if the version of the first configuration update file is not greater than the version of the second configuration update file, i.e., the version of the first configuration update file is consistent with the version of the second configuration update file. In this case, the configuration update file of the backup area does not need to be updated, and the mobile terminal directly performs the operation of judging whether the first configuration update file characterizes the battery abnormality without performing the operation of storing the first configuration update file to the backup area.

In this embodiment, referring to S202, if the first configuration update file characterizes the battery as abnormal, meaning that the battery of the mobile terminal is a risk battery with abnormality, the mobile terminal needs to perform charging limit control of the battery, S305 is performed. If the first configuration update file characterizes the battery as non-abnormal, meaning that the battery of the mobile terminal is a non-abnormal battery, no charge limit control of the battery is required, S306 is performed.

And S305, when the mobile terminal is in a charging state, if the detected charging quantity of the battery meets the preset charging quantity threshold value, stopping the charging operation.

In some embodiments, the first configuration update file characterizes a battery anomaly, and triggers performance of a battery limit management operation upon detection of the battery being in a state of charge. The embodiment given in S203 may be referred to, and this embodiment will not be described in detail.

S306, the mobile terminal does not execute the power limiting control operation.

The embodiment given in S204 is not described in detail.

S307, the mobile terminal outputs prompt information.

The embodiment given in S206 is not described in detail.

In this embodiment, the mobile terminal may store the configuration update file received from the server in time in the permanent backup area, so as to avoid the problem of clearing the configuration update file in the local storage space of the housekeeping application when updating the application version based on the configuration update file. The permanent backup area comprises a history configuration update file, the mobile terminal can compare the version of the first configuration update file with the version of the second configuration update file of the backup area after receiving the first configuration update file, and the first configuration update file is stored in the backup area under the condition that the version of the first configuration update file is larger than the version of the second configuration update file; and under the condition that the version of the first configuration update file is not larger than that of the second configuration update file, the first configuration update file is not stored in the backup area, so that the occupation of the repeated files in the backup area is reduced.

In some embodiments, the server may acquire battery state information of the mobile terminal to perform battery risk analysis, and when determining that the battery is abnormal, add a first identifier for characterizing the battery abnormality in a configuration update file of the mobile terminal corresponding to the battery. However, in the scenario that the server identifies a battery abnormality and the server sends a configuration update file to the mobile terminal, the user may replace the battery, that is, the information of "battery abnormality" of the battery a becomes invalid after replacing the battery B, the embodiment provides a method for managing and controlling the battery abnormality of the terminal, referring to fig. 7, including:

s401, the mobile terminal acquires the configuration update file.

In this embodiment, the configuration update file includes an identifier of the abnormal battery, which may be a serial number, referred to as a first battery serial number, for example.

S402, the mobile terminal judges whether the backup area has a second battery serial number. If yes, executing S403; if not, S408 is performed.

The second battery serial number is the serial number of the battery included in the configuration update file of the backup area.

In some embodiments, the mobile terminal may first determine whether the backup area has the second battery serial number. The mobile terminal may determine whether the backup area has a configuration update file, if so, determine whether the backup area has a second battery serial number corresponding to the battery from the configuration update file of the backup area, and execute S403; and if the backup area is not provided with the update file, confirming that the backup area does not have the second battery serial number corresponding to the battery. The absence of the configuration update file in the backup area means that the mobile terminal may receive the configuration update file regarding the battery abnormality for the first time, in which case S408 is performed.

S403, the mobile terminal judges whether the first battery serial number is consistent with the second battery serial number. If so, executing S404; if not, S409 is performed.

In some embodiments, the first battery serial number is a serial number of a current battery acquired by the mobile terminal through the battery chip. And under the condition that the mobile terminal determines that the backup area has the configuration update file and the backup area has the second battery serial number, the mobile terminal judges whether the first battery serial number is consistent with the second battery serial number. If the first battery serial number is consistent with the second battery serial number, it is indicated that the mobile terminal does not perform the operation of replacing the battery during the period from the server identifying the battery abnormality of the mobile terminal to the server issuing the configuration update file, and S404 is executed; if the first battery serial number is inconsistent with the second battery serial number, it indicates that the mobile terminal has performed a battery replacement operation during the period from when the server identifies that the battery of the mobile terminal is abnormal to when the server issues the configuration update file, and S409 is executed.

Optionally, in order that the mobile terminal may provide the other scenario with valid information for characterizing the non-replaced battery, the mobile terminal may set a third identification, and after determining the non-replaced battery, S404 is performed.

S404, the mobile terminal sets the third mark to be a first value.

Wherein the third identifier is used to characterize whether to replace the battery. When the third mark is the first value, the battery is not replaced; and when the third mark is a second value, the third mark represents that the battery is replaced.

When the mobile terminal determines that the first battery serial number is consistent with the second battery serial number, i.e., the mobile terminal does not replace the battery, the third flag is set to the first value. Wherein, the first value may be 0, for example.

S405, the mobile terminal judges whether the configuration update file represents battery abnormality. If yes, then execute S406; if not, S410 is performed.

And determining that the battery is not replaced at the mobile terminal, and judging whether the configuration update file represents battery abnormality or not by the mobile terminal. If yes, meaning that the battery of the mobile terminal is a risk battery with abnormality, the mobile terminal needs to perform charging limit control of the battery, and S406 is executed. If the configuration update file characterizes the battery as non-abnormal, meaning that the battery of the mobile terminal is a non-abnormal battery, the charging limit control of the battery is not required, S410 is performed.

And S406, when the mobile terminal is in a charging state, if the detected battery charging quantity meets the preset charging quantity threshold value, stopping the charging operation.

The embodiment given in S203 is not described in detail.

S407, the mobile terminal outputs prompt information.

The embodiment given in S206 is not described in detail.

S408, the mobile terminal judges whether the number of times of full charge and discharge of the battery is smaller than a preset first threshold. If yes, executing S409; if greater than or equal to, S405 is performed.

If the backup area does not have the second battery serial number, the mobile terminal may also determine whether to replace the battery through other information.

In this embodiment, the mobile terminal may obtain the number of full-charge discharging times of the battery, where the number of full-charge discharging times of the battery refers to the number of complete cycles of full charge and full charge. If the number of times is smaller than the preset first threshold, which indicates that the battery of the mobile terminal is used for a short time, and the number of times of full charge and discharge is small, it may be that the mobile terminal has replaced the battery, and S409 is performed. If the number of times is greater than or equal to the preset threshold, it indicates that the battery of the mobile terminal has a longer service life, and the number of times of full charge and discharge has satisfied the preset first threshold, and the mobile terminal does not replace the battery, and S405 is executed. Illustratively, the preset first threshold may be 10, 20, etc., the preset first threshold being a natural number greater than 0. Illustratively, if the number of full-charge discharges of the battery is less than 20, then the battery is deemed not to be replaced.

Optionally, if the number of times is greater than or equal to the preset first threshold, the mobile terminal may further determine whether the number of times is greater than or equal to the preset second threshold, which indicates that the battery of the mobile terminal has a longer service life, and the mobile terminal does not replace the battery. Wherein the preset second threshold is greater than the preset first threshold, and the preset second threshold may be 30, 40, etc., and the preset second threshold is a natural number greater than 0.

Alternatively, in another implementation, the mobile terminal may directly perform S408 to determine whether to replace the battery after performing S401.

Optionally, in order that the mobile terminal may provide the other scenario with valid information for characterizing the replaced battery, the mobile terminal may set a third identification, and after determining that the battery has been replaced, S409 is performed.

S409, the mobile terminal sets the third identifier to a second value.

The third flag is set to the second value when the mobile terminal determines that the first battery serial number is inconsistent with the second battery serial number, i.e., the mobile terminal has replaced the battery. Wherein, for example, the second value may be 1.

Or if the number of times of full charge and discharge of the battery is smaller than the preset first threshold, which means that the battery of the mobile terminal is used for a short time, the number of times of full charge and discharge is smaller, it may be that the mobile terminal has replaced the battery, and the third identifier is set to a second value.

Optionally, in some embodiments, the mobile terminal may clear the configuration update file of the permanent backup area after determining that the battery is replaced, so as to avoid triggering performance of meaningless power limiting management operation on the new battery due to inclusion of the first identifier in the configuration update file.

S410, the mobile terminal does not execute the power limiting control operation.

In some embodiments, the first configuration update file does not include the first identifier, the mobile terminal determines that the current battery is not abnormal, and the mobile terminal does not need to perform the power limiting control operation. Or if the third identification value is the second value, the mobile terminal replaces the battery, and the current battery is determined to be abnormal, so that the mobile terminal does not need to execute the power limiting control operation.

In this embodiment, the mobile terminal may determine whether to replace the battery according to the battery serial number or the number of times of full charge and discharge of the battery, and does not perform the charging limit control operation of the battery in the case of replacing the battery; only in the case where it is determined that the battery is not replaced, the battery charging limit control operation is performed, so that the battery at risk of abnormality can be effectively charged limit controlled. Avoiding meaningless charging limit control operation on the new battery and avoiding error experience of timely using the new battery and still displaying reminding information for reminding the user that the battery is abnormal. Meanwhile, the waste of resources for the mobile terminal to execute the charging limit control operation is avoided.

In some embodiments, the mobile terminal performs the power limiting control operation immediately after updating based on the configuration update file, which may cause a risk to the user that the battery is intuitively caused by the application version (parameter) update operation, and may cause the user to be dissatisfied with the application version update operation. For such a scenario, the present embodiment provides a method for managing and controlling abnormality of a terminal battery, referring to fig. 8, including:

s501, the mobile terminal acquires a first configuration update file.

S502, the mobile terminal judges whether the first configuration update file represents battery abnormality. If yes, then execution S503; if not, S505 is performed.

In the present embodiment, referring to S202, if the first configuration update file includes the first identifier, which means that the battery of the mobile terminal is a risk battery with abnormality, the mobile terminal needs to perform charging limit control of the battery, S503 is performed. If the first identifier is not included in the first configuration update file, which means that the battery of the mobile terminal is a non-abnormal battery, the charging limit control of the battery is not required, S505 is performed.

S503, the mobile terminal judges whether the number of times of full charge and discharge of the battery meets the number of times of execution. If yes, executing S504; if not, S505 is performed.

The mobile terminal can acquire the current full charge and discharge times of the battery, wherein the current full charge and discharge times of the battery refer to the accumulated times of complete cycles of full charge and complete charge. The mobile terminal may determine a number of delays, for example, a number of delays of 2. The execution count is the sum of the accumulated count and the delay count. For example, the number of full charge discharge of the battery is 10, the number of delay is 2, and the number of execution is 12. If the mobile terminal determines that the number of times of full charge and discharge of the battery reaches the execution number of times 12, executing S504; if the mobile terminal determines that the number of battery full-charge discharging times does not reach the execution number 12, S505 is executed.

In this embodiment, the mobile terminal may clear the execution count when stopping the execution of the power limiting control operation, so that the determination of the execution count is performed when it is determined that the power limiting control operation needs to be performed next time.

S504, when the mobile terminal is in a charging state, if the battery charging quantity is detected to meet a preset charging quantity threshold value, stopping the charging operation.

The embodiment given in S203 is not described in detail.

S505, the mobile terminal does not execute the power limiting control operation.

In some embodiments, the first configuration update file characterizes a battery anomaly, the mobile terminal determines that the current battery is not abnormal, and the mobile terminal does not need to perform a power limit control operation.

In some embodiments, if the mobile terminal determines that the number of battery full-discharge times does not reach the execution number, the power limiting control operation is not executed temporarily.

S506, the mobile terminal outputs prompt information.

The embodiment given in S206 is not described in detail.

In this embodiment, the mobile terminal may perform the power limiting control operation when the number of times of battery full charge and discharge satisfies the number of times of execution according to a comparison judgment of the number of times of battery full charge and discharge and the number of delays before performing the power limiting control operation. Thus, the charging limit control operation of the battery is executed for a period of time, and the battery abnormality caused by the mobile terminal is prevented from causing bad use experience to the user due to the fact that the mobile terminal updates the application version according to the configuration update file.

Further embodiments of the power limiting management operations for three different scenarios are given in the embodiments provided in fig. 6-8 above, and in conjunction with the content of fig. 6-8, in some embodiments, fig. 9 provides a method for managing terminal battery anomalies in three scenarios considered by the mobile terminal, including:

s601, the mobile terminal acquires a first configuration update file.

S602, the mobile terminal judges whether the backup area has a second battery serial number. If yes, executing S603; if not, S605 is executed.

A step of judging whether the backup area has the second battery serial number in the embodiment of reference S402. If the backup area has the second battery serial number, executing S603; if the backup area does not have the second battery serial number, S605 is executed.

S603, the mobile terminal judges whether the first battery serial number is consistent with the second battery serial number. If so, executing S604; if not, S606 is performed.

A step of judging whether the first battery serial number is identical to the second battery serial number in the embodiment of reference S402. If so, executing S604; if not, S606 is performed.

S604, the mobile terminal sets the third mark to be a first value.

In the embodiment referring to S404, the description of this embodiment is omitted.

S605, the mobile terminal judges whether the number of times of full charge and discharge of the battery is smaller than a preset first threshold value. If yes, executing S606; if greater than or equal to, S607 is performed.

The step of judging whether the number of full discharge times of the battery is smaller than the preset first threshold value in the embodiment of reference S408. If the number of full charge and discharge times of the battery is less than the preset first threshold, executing S606; if the number of full discharge times of the battery is not less than the preset first threshold, S607 is performed.

S606, the mobile terminal sets the third mark to be a second value.

In the embodiment referring to S409, the description of this embodiment is omitted.

S607, the mobile terminal judges whether the third mark is the first value. If yes, executing S608; if not, S610 is performed.

When the mobile terminal determines that the third identifier is the first value, determining that the battery is not replaced, and executing S608; if the third flag is not the first value, it is determined that the battery is replaced, and S610 is performed.

S608, the mobile terminal judges whether the first version number is larger than the second version number, and if so, S609 is executed; if not, S611 is performed.

A step of determining whether the first version number of the first configuration update file is greater than the second version number of the second configuration update file in the embodiment of reference S302. If the first configuration update file version is greater than the second configuration update file version, S609 is performed; if the first profile version is not greater than the second profile version, S611 is performed.

It should be noted that, in some embodiments, if the mobile terminal performs operations such as system restart or manager application service restart, the mobile terminal performs the operations. In this scenario, the configuration update file in the current storage space of the housekeeping application has been cleared, and the mobile terminal is the first configuration update file obtained from the backup area. The first configuration update file is the configuration update file of the backup area, and is obtained from the backup area, so that the first configuration update file is actually the configuration update file of the backup area, and the comparison operation and the backup operation of the version numbers (S608 and S609) do not need to be performed, and after the mobile terminal performs S607, S610 or S611 can be correspondingly performed, so that the computing resources of the mobile terminal can be saved.

S609, the mobile terminal replaces the configuration update file stored in the backup area with the first configuration update file.

The step of storing the first configuration update file to the backup area in the embodiment of reference S303.

S610, the mobile terminal clears the target parameters in the configuration update file of the backup area.

If the third identifier is the second value, that is, the mobile terminal updates the battery, the mobile terminal clears all parameters except the version number in the configuration update file of the backup area. The configuration update file includes a plurality of parameters such as a version number, battery status information (battery identifier, first identifier, second identifier), application parameters of the housekeeper application, and the like. The version numbers can be reserved for comparison of different configuration update file version numbers; clearing other parameters in the configuration update file can ensure that the parameters in the configuration update file take effect once, and meaningless limit control operation on the new battery is prevented from being performed due to triggering of the failed parameters in the configuration update file.

In this embodiment, S615 is performed after the mobile terminal clears all parameters except the version number in the configuration update file of the backup area, that is, when the mobile terminal determines that the battery is updated.

S611, the mobile terminal judges whether the first configuration update file represents battery abnormality. If yes, then S612 is performed; if not, S615 is performed.

Reference is made to the step of determining that the first configuration update file characterizes the battery abnormality in the S202 embodiment. If the first configuration update file characterizes the battery abnormality, S612 is performed. If the first configuration update file characterizes the battery as non-abnormal, S615 is performed.

S612, the mobile terminal judges whether the number of times of full charge and discharge of the battery meets the number of times of execution. If yes, executing S613; if not, S615 is performed.

A step of judging whether the number of times of full charge and discharge of the battery satisfies the number of times of execution in the embodiment with reference to S503. If yes, executing S613; if not, S615 is performed.

And S613, when the mobile terminal is in a charging state, if the battery charging quantity is detected to meet the preset charging quantity threshold value, stopping the charging operation.

The embodiment given in S203 is not described in detail.

S614, the mobile terminal outputs prompt information.

The embodiment given in S206 is not described in detail.

S615, the mobile terminal does not execute the power limiting control operation.

The embodiment given in S204 is not described in detail.

In this embodiment, when the mobile terminal meets the power limiting control condition, the mobile terminal obtains the first configuration update file. The method comprises the steps of carrying out charging limit control operation of a battery with abnormality from the dimension of whether the version of a first configuration update file is higher than the version of a historical configuration update file of a backup area, the dimension of whether to replace the battery and the dimension of delaying the charging limit control operation, effectively avoiding accidents possibly caused by short circuit of a risk battery in the charging process, avoiding the problem that the first configuration update file cannot be cleared when the mobile terminal carries out application version update, and carrying out meaningless charging limit control operation on the replaced battery, further avoiding causing error impression of battery abnormality caused by application version update to a user, and optimizing the use experience of the user from different dimensions.

In the embodiment of the present application, the mobile terminal may perform any one of the methods in fig. 6 to 8, may perform at least two methods, or may further perform three methods. In a scenario where at least two methods are performed, the present embodiment does not limit the execution logic sequence of the mobile terminal to the embodiments presented in fig. 6-8. For example, the mobile terminal may perform the power limit control operation in order of judging whether the mobile terminal replaces the battery, whether the configuration update file has been backed up in the backup area, and whether the number of executions is satisfied; alternatively, the mobile terminal may perform the power limiting control operation in order of determining whether the configuration update file has been backed up in the backup area, whether the mobile terminal replaces the battery, whether the number of executions is satisfied, etc., and fig. 9 is merely an example, and the present embodiment does not limit the actual execution logic sequence.

Fig. 10 shows a possible structural diagram of the mobile terminal involved in the above embodiment. The mobile terminal 1000 shown in fig. 10 includes a processor 1001, a display 1002, a storage module 1003, and a communication module 1004.

The processor 1001 may be a central processing unit (central processing unit, CPU), a digital signal processor (digital signal processor, DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (field programmable gate array, FPGA) or other programmable logic device, a transistor logic device, a hardware component, or any combination thereof. The processor may include an application processor and a baseband processor. Which may implement or perform the various exemplary logic blocks, modules, and circuits described in connection with this disclosure. The processor may also be a combination that performs the function of a computation, e.g., a combination comprising one or more microprocessors, a combination of a DSP and a microprocessor, and the like. The memory module 1003 may be a memory.

For example, the processor 1001 may be the processor 310 shown in fig. 2; the display 1002 may be the display 390 shown in fig. 2; the storage module 1003 may be an internal memory 321 as shown in fig. 2; the communication module 1004 may be the communication module 360 shown in fig. 2. The mobile terminal provided in the embodiment of the present application may be the mobile terminal 100 shown in fig. 2.

Embodiments of the present application also provide a system-on-a-chip (SoC) including at least one processor 701 and at least one interface circuit 702, as shown in fig. 11. The processor 701 and the interface circuit 702 may be interconnected by wires. For example, the interface circuit 702 may be used to receive signals from other devices, such as a memory of a mobile terminal. For another example, the interface circuit 702 may be used to send signals to other devices, such as the processor 701 or a camera of a mobile terminal. The interface circuit 702 may, for example, read instructions stored in a memory and send the instructions to the processor 701. The instructions, when executed by the processor 701, may cause the mobile terminal to perform the various steps of the embodiments described above. Of course, the chip system may also include other discrete devices, which are not specifically limited in this embodiment of the present application.

Embodiments of the present application also provide a computer readable storage medium, where the computer readable storage medium includes computer instructions, which when executed on the mobile terminal, cause the mobile terminal to perform the functions or steps performed by the mobile terminal 100 in the method embodiments described above; when executed on a server, cause the server to perform the functions or steps performed by the server in the method embodiments described above.

Embodiments of the present application also provide a computer program product which, when run on a computer, causes the computer to perform the various functions or steps performed by the mobile terminal 100 in the method embodiments described above. For example, the computer may be the mobile terminal 100 described above; the computer program product, when run on a computer, causes the computer to perform the functions or steps performed by the server in the method embodiments described above.

It will be apparent to those skilled in the art from this description that, for convenience and brevity of description, only the above-described division of the functional modules is illustrated, and in practical application, the above-described functional allocation may be performed by different functional modules according to needs, i.e. the internal structure of the apparatus is divided into different functional modules to perform all or part of the functions described above.

In the several embodiments provided in this application, it should be understood that the disclosed apparatus and method may be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the modules or units is merely a logical functional division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another apparatus, or some features may be omitted, or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and the parts displayed as units may be one physical unit or a plurality of physical units, may be located in one place, or may be distributed in a plurality of different places. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in each embodiment of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in software functional units.

The integrated units, if implemented in the form of software functional units and sold or used as stand-alone products, may be stored in a readable storage medium. Based on such understanding, the technical solution of the embodiments of the present application may be essentially or a part contributing to the prior art or all or part of the technical solution may be embodied in the form of a software product stored in a storage medium, including several instructions for causing a device (may be a single-chip microcomputer, a chip or the like) or a processor (processor) to perform all or part of the steps of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read Only Memory (ROM), a random access memory (random access memory, RAM), a magnetic disk, or an optical disk, or other various media capable of storing program codes.

The foregoing is merely a specific embodiment of the present application, but the scope of the present application is not limited thereto, and any changes or substitutions within the technical scope of the present disclosure should be covered in the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. The abnormal terminal battery control method is characterized by being applied to a mobile terminal, wherein the mobile terminal comprises a battery; the method comprises the following steps:

the mobile terminal acquires a first configuration update file; the first configuration update file is used for updating application parameters of the mobile terminal, and the first configuration update file characterizes whether the battery of the mobile terminal is abnormal or not; the battery indicated by the first configuration update file has a binding relation with the mobile terminal, and the first configuration update file is a file which is sent to the mobile terminal in a cloud pushing mode when a server determines that the battery of the mobile terminal is abnormal or determines that the application parameters of the mobile terminal need to be updated;

under the condition that a preset condition is met, when the battery of the mobile terminal is in a charging state, the mobile terminal stops charging when detecting that the charging electric quantity of the battery of the mobile terminal reaches a preset charging electric quantity threshold value;

wherein, the preset conditions include: the first configuration update file indicates that a battery of the mobile terminal is abnormal.

2. The method of claim 1, wherein the preset conditions further comprise: the battery of the mobile terminal is not replaced.

3. The method of claim 1, wherein the mobile terminal obtaining the first configuration update file comprises:

the mobile terminal receives the first configuration update file from the server; or,

the mobile terminal acquires the first configuration update file from a first storage space of the mobile terminal under the condition that the mobile terminal detects that a charging interruption event is generated; or,

the mobile terminal acquires the first configuration update file from a second storage space of the mobile terminal under the condition that a system of the mobile terminal is restarted; or,

the first configuration update file is specifically configured to obtain the first configuration update file from the second storage space of the mobile terminal when the mobile terminal restarts the service of the target application under the condition that the parameter of the target application of the mobile terminal is updated;

wherein the second storage space is a permanent storage space.

4. A method according to claim 3, wherein after the obtaining the first configuration update file, the method further comprises:

the mobile terminal acquires a second version number of a second configuration update file; the second configuration update file is a configuration update file stored in the second storage space;

And under the condition that the first version number of the first configuration update file is larger than the second version number, the mobile terminal replaces the configuration update file stored in the second storage space with the first configuration update file.

5. The method of any of claims 1-4, wherein the first configuration update file comprises a first battery serial number, the method further comprising, after the obtaining the first configuration update file:

the mobile terminal acquires battery parameters of a current battery of the mobile terminal; the battery parameters comprise a first battery serial number and/or a full charge discharge number;

the mobile terminal judges whether the battery of the mobile terminal is replaced according to the battery parameters;

wherein, if the battery parameter includes the first battery serial number, if the first battery serial number is different from a second battery serial number included in a second storage space, determining that the battery of the mobile terminal is replaced; if the first battery serial number is the same as the second battery serial number, determining that the battery of the mobile terminal is not replaced;

under the condition that the battery parameters comprise the full charge and discharge times, if the full charge and discharge times are smaller than a preset first threshold value, determining that the battery of the mobile terminal is replaced; and if the number of times of full charge amplification is greater than the preset first threshold value, determining that the battery of the mobile terminal is not replaced.

6. The method according to any one of claims 1-4, wherein before the mobile terminal stops the charging operation upon detecting that the charge level of the battery reaches a preset charge level threshold, the method further comprises:

7. The method according to any of claims 1-4, wherein in case the first configuration update file comprises a first identification, the first configuration update file is used to indicate that there is an abnormality in the battery of the mobile terminal; if the first configuration update file does not include the first identifier, the first configuration update file is used for indicating that the battery of the mobile terminal is not abnormal; or,

the method comprises the steps that under the condition that a first identifier included in a first configuration update file is a first value, the first configuration update file is used for indicating that a battery of the mobile terminal is abnormal; and in the case that the first identifier included in the first configuration update file is a second value, the first configuration update file is used for indicating that the battery of the mobile terminal is not abnormal.

8. The method according to any of claims 1-4, wherein the first configuration update file comprises a second identification characterizing a risk level of a battery of the mobile terminal; the risk level of the battery comprises a plurality of levels, and different levels correspond to different preset charging electric quantity thresholds; the more serious the battery abnormality represented by the risk level is, the smaller the preset charge quantity threshold value is.

9. The method according to any one of claims 1-4, wherein, in case the preset condition is met, the method further comprises:

the mobile terminal outputs prompt information; the prompt information is used for prompting a user that the battery is abnormal.

10. The method of claim 9, wherein the first configuration update file includes a second identification characterizing a risk level of a battery of the mobile terminal; the risk level of the battery comprises a plurality of levels, and different levels correspond to different preset charging electric quantity thresholds; the serious the battery abnormal condition represented by the risk level is, the higher the reminding level of the prompt information is.

11. A method according to claim 3, characterized in that in case the battery of the mobile terminal is replaced, the method further comprises:

And deleting parameters except the version number in the configuration update file of the second storage space by the mobile terminal.

12. A method for managing and controlling abnormality of a terminal battery, which is applied to a server, the method comprising:

the server acquires battery state information of a plurality of mobile terminals; the battery state information comprises a battery serial number and a battery capacity;

the server determines a target battery with abnormality based on battery state information of each mobile terminal;

the server generates a configuration update file of the mobile terminal corresponding to the target battery; the configuration update file is used for updating application parameters of the mobile terminal and representing whether the battery of the mobile terminal is abnormal or not;

and the server sends the configuration update file to the mobile terminal corresponding to the target battery.

13. The method according to claim 12, wherein the method further comprises:

the server determines the risk level of the target battery based on the battery state information of the target battery;

and the server adds the risk level of the target battery to a corresponding configuration update file.

14. A mobile terminal comprising a memory, a display screen, a communication module, and one or more processors; the memory, the display screen, the communication module are coupled with the processor; the memory has stored therein computer program code comprising computer instructions which, when executed by the processor, cause the mobile terminal to perform the method of any of claims 1-11.

15. A server, wherein the server comprises a processing center and a database;

the processing center is used for acquiring battery state information of a plurality of mobile terminals; the battery state information comprises a battery serial number and a battery capacity; determining a target battery with abnormality based on battery state information of each mobile terminal; acquiring a configuration update file of the mobile terminal corresponding to the target battery; the configuration update file is used for updating parameters of the mobile terminal and whether the battery of the mobile terminal is abnormal or not;

the database is used for sending the configuration update file to the mobile terminal corresponding to the target battery.

16. The server of claim 15, wherein the database is a lightweight cloud database,

the database is used for sending the configuration update file to the mobile terminal corresponding to the target battery in a cloud pushing mode.

17. A terminal abnormality battery management system, characterized in that the system comprises a mobile terminal according to claim 14 and a server according to claim 15 or 16.

18. A computer readable storage medium comprising computer instructions which, when run on a mobile terminal, cause the mobile terminal to perform the method of any of claims 1-11; the computer instructions, when run on the server, cause the server to perform the method of claim 12 or 13.