Method for predicting battery life, electronic equipment and readable storage medium

Through user behavior analysis and application of power consumption analysis models, combined with the equipment environment and battery attributes, the battery life of electronic equipment is predicted, which solves the problem of inaccurate prediction of battery life in the existing technology, and improves the accuracy and user experience of prediction.

CN119026718APending Publication Date: 2024-11-26HONOR DEVICE CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202310606436.4
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2023-05-25
Publication Date
2024-11-26

AI Technical Summary

Technical Problem

The prior art cannot accurately predict the battery life of electronic equipment batteries, and the actual use time of the battery cannot be reflected by the remaining power indication.

Method used

Through the user behavior analysis model and the application power consumption analysis model, combined with user usage habits, equipment environment factors and battery attribute information, the battery life is predicted and the battery life is displayed.

Benefits of technology

It improves the accuracy of battery life prediction, provides more reliable battery usage suggestions, and meets users' needs for battery life.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119026718A_ABST
    Figure CN119026718A_ABST
Patent Text Reader

Abstract

The invention discloses a method for predicting battery life, electronic equipment and a readable storage medium, and belongs to the technical field of terminals. The method comprises the steps that on the basis of behavior analysis index information, a target operation object sequence is determined through a user behavior analysis model, the target operation object sequence is used for representing application programs possibly operated by a user in sequence in a period of time in the future, and the user behavior analysis model can predict operation behaviors of the user. According to the target operation object sequence and the battery attribute information, the current physical environment index value and the residual total electric quantity of the electronic equipment, the battery endurance duration of the electronic equipment is determined, and the physical environment index value comprises the value of at least one equipment environment factor influencing the power consumption of the electronic equipment. And the battery life duration is displayed. By comprehensively considering the use habit of the user on the application program and the equipment environment factors influencing the power consumption, the accuracy of predicting the endurance time of the battery can be improved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of terminal technology, and in particular to a method for predicting battery life, an electronic device, and a readable storage medium. Background Art

[0002] With the rapid popularization of electronic devices such as mobile phones and personal computers, the battery life of electronic devices has gradually become a focus of users. In order to provide users with more reliable battery usage suggestions, it is usually necessary to predict the battery life.

[0003] In the related art, electronic devices generally only have a remaining power indication function, which can indicate the remaining power of the electronic device battery and display it on the interface of the electronic device in a graphical manner. However, the remaining power of the battery and the battery life are usually not linearly related, so the battery life cannot be predicted by indicating the remaining power of the battery. Summary of the invention

[0004] The present application provides a method for predicting battery life, an electronic device, and a readable storage medium, which can solve the problem that the battery life cannot be accurately predicted in the related art. The technical solution is as follows:

[0005] In a first aspect, a method for predicting battery life is provided, the method comprising:

[0006] Based on the behavior analysis index information, a target operation object sequence is determined through a user behavior analysis model, wherein the target operation object sequence is used to characterize the application programs that the user may sequentially operate in a future period of time, and the user behavior analysis model can predict the operation behavior of the user;

[0007] Determining the battery life of the electronic device according to the target operation object sequence, the battery property information of the electronic device, the current physical environment index value and the remaining total power, wherein the physical environment index value includes the value of at least one device environment factor that affects the power consumption of the electronic device;

[0008] Displays stated battery life.

[0009] In this way, when predicting battery life, the user's usage habits of the application and the device environment factors that affect power consumption are comprehensively considered, thereby improving the accuracy of the battery life prediction.

[0010] As an example of the present application, the number of the current physical environment indicator values ​​is multiple;

[0011] The determining the battery life of the electronic device according to the target operation object sequence, the battery property information of the electronic device, the current physical environment indicator value and the remaining total power includes:

[0012] Determine a current physical environment impact coefficient based on multiple current physical environment indicator values;

[0013] Based on the current physical environment impact coefficient and the battery property information of the electronic device, a target power consumption data set is determined by applying a power consumption analysis model, wherein the target power consumption data set is used to characterize the power consumption of each application in the electronic device within a unit time under the current device environment, and the application power consumption analysis model can determine the power consumption of each application within the unit time under different device environments;

[0014] The battery life is determined based on the target operation object sequence, the remaining total power and the target power consumption data set.

[0015] In this way, by determining a target operation object sequence for characterizing the power consumption of each application in the electronic device in the current device environment per unit time, and combining the target operation object sequence and the remaining total power, the battery life can be determined, thereby improving the accuracy of the prediction.

[0016] As an example of the present application, the application power consumption analysis model includes multiple mapping relationships, each of the multiple mapping relationships includes a correspondence between primary physical indication information, a range of physical environment impact coefficients, and secondary physical indication information, wherein different primary physical indication information corresponds to different battery attribute information, and different secondary physical indication information corresponds to different power consumption data sets;

[0017] The determining of a target power consumption data set by applying a power consumption analysis model based on the current physical environment impact coefficient and the battery attribute information of the electronic device includes:

[0018] Determining a target physical environment impact coefficient range in which the current physical environment impact coefficient is located from a plurality of physical environment impact coefficient ranges;

[0019] Determine target primary physical indication information corresponding to the battery attribute information of the electronic device;

[0020] The application power consumption analysis model is used to determine the secondary physical indication information corresponding to the target physical environment impact coefficient range and the target primary physical indication information from the multiple mapping relationships, and the target power consumption data set is the power consumption data set corresponding to the determined secondary physical indication information.

[0021] In this way, by determining the target physical environment impact coefficient range of the current physical environment impact coefficient, the target power consumption data set under the current device environment is determined according to multiple mapping relationships in the application power consumption analysis module, so that the power consumption of each application in the target operation object sequence under the current device environment can be determined based on the target power consumption data set, thereby predicting the battery life.

[0022] As an example of the present application, the target operation object sequence includes at least one application, and the at least one application is arranged in sequence according to a possible operation order;

[0023] The determining the battery life based on the target operation object sequence, the remaining total power and the target power consumption data set includes:

[0024] Based on the target power consumption data set, respectively determine the power consumption of each application in the target operation object sequence within the unit time under the current device environment;

[0025] Determine at least one reference application from the target operation object sequence according to the time sequence of operations and the power consumption of each application in the target operation object sequence within the unit time, wherein the total power consumption of the at least one reference application is greater than or equal to the remaining total power, and the difference between the total power consumption of the at least one reference application and the remaining total power is minimal;

[0026] counting the number of the at least one reference application;

[0027] The battery life is determined by multiplying the number of the at least one reference application by the unit time.

[0028] In this way, by finding the minimum number of reference applications that make the remaining total power zero from the target operation object sequence, it is possible to determine how many unit time periods it will take for the remaining total power of the electronic device to be consumed, and thus determine the battery life.

[0029] As an example of the present application, the behavior analysis index information includes the current feature cycle and the current time point; the user behavior analysis model includes a user personalized behavior sequence corresponding to each feature cycle in multiple feature cycles, each feature cycle includes multiple unit time periods, each user personalized behavior sequence includes multiple applications, each application corresponds to a unit time period, and the user personalized behavior sequence corresponding to any cycle feature is used to characterize the application used by the user in each of the unit time periods in sequence under any feature cycle;

[0030] The step of determining a target operation object sequence based on the behavior analysis index information through a user behavior analysis model includes:

[0031] Obtaining the user personalized behavior sequence corresponding to the current feature period from the user personalized behavior sequences of the multiple feature periods by using the user behavior analysis model;

[0032] From the user personalized behavior sequence corresponding to the current feature period, the application programs corresponding to each unit time period after the current time point are determined, and the determined application programs constitute the target operation object sequence.

[0033] In this way, by determining the user's personalized behavior sequence under the current feature cycle, and then predicting the applications that the user may use in sequence from the user's personalized behavior sequence under the current feature cycle according to the current time point, the target operation object sequence can be determined, which facilitates the subsequent prediction of battery life based on the determined user usage habits.

[0034] As an example of the present application, the method further includes:

[0035] Acquire a plurality of application history usage data, each of the plurality of application history usage data being used to characterize a history usage record of an application program, wherein the history usage record of an application program includes a characteristic period in which the application program is used;

[0036] The plurality of application history usage data are grouped based on the characteristic period to obtain a plurality of groups of application history usage data, wherein one group corresponds to one characteristic period;

[0037] Based on each set of application history usage data in the multiple sets of application history usage data, a user personalized behavior sequence corresponding to each characteristic period is determined.

[0038] In this way, by building a user behavior analysis model based on the accumulated user operation behavior data, the applications that users may use in each unit time under different characteristic periods are analyzed, and the user personalized behavior sequences corresponding to different characteristic periods are output. In this way, the applications that users may use in sequence in the future can be predicted based on the real-time collected reporting data and the user behavior operation sequence, and then the battery life can be predicted based on the power consumption of these applications.

[0039] As an example of the present application, the historical usage record of the one application further includes time information when the one application is used;

[0040] The determining, based on each set of application history usage data in the plurality of sets of application history usage data, a user personalized behavior sequence corresponding to each characteristic period includes:

[0041] For any set of application history usage data among the multiple sets of application history usage data, counting the usage frequency of each application used in each unit time period in the characteristic period corresponding to the any set according to each time information in the any set of application history usage data;

[0042] Based on the usage frequency of each application used in each unit time period in the feature period corresponding to any group, a user personalized behavior sequence corresponding to one feature period is determined.

[0043] In this way, based on the data set under each characteristic period, the applications that users are accustomed to using in each unit time period are statistically analyzed to determine the users' habitual operation objects in each unit time period, and further determine the users' personalized behavior sequences under each characteristic period.

[0044] As an example of the present application, determining a user personalized behavior sequence corresponding to a feature period based on the usage frequency of each application used in each unit time period in any group of corresponding feature periods includes:

[0045] For any one of the unit time periods, if the number of applications with the highest frequency of use in the any one of the unit time periods is one, determining the application with the highest frequency of use as the operation object in the any one of the unit time periods;

[0046] If there are multiple applications with the highest usage frequency in any one unit time period, the operation object determined in the previous unit time period is determined as the operation object in the any one unit time period.

[0047] In this way, by determining the application with the highest usage frequency within a unit time, and thus determining the operation object within the unit time period, the effectiveness and accuracy of the analysis can be improved.

[0048] As an example of the present application, the method further includes:

[0049] Acquire multiple key data feature sets corresponding to each of the application programs, each of the multiple key data feature sets including application information of an application program, and corresponding battery attribute information, physical environment index value, and power consumption within the unit time when the application program is used;

[0050] Determining the physical environment impact coefficient corresponding to each key data feature set according to the physical environment indicator value in each key data feature set;

[0051] Determining, from a plurality of physical environment impact coefficient ranges, a physical environment impact coefficient range in which a physical environment impact coefficient corresponding to each key data feature set is located;

[0052] Based on the multiple key data feature sets and the range of physical environment impact coefficients corresponding to each key data feature set, counting the power consumption of each application program in a unit time under different device environments;

[0053] The multiple mapping relationships are established based on the power consumption of each application program within a unit time under different device environments.

[0054] In this way, by analyzing a massive set of key data features, the power consumption of each application per unit time in various device environments can be determined, and a mapping relationship between the device environment and the power consumption of the application can be established. This will facilitate the subsequent prediction of battery life. The power consumption of each application can be determined based on the real-time device environment, and then the possible power consumption of the battery in the future can be determined in combination with the applications that the user is predicted to operate, so that the battery life can be accurately predicted.

[0055] As an example of the present application, before determining the target operation object sequence through the user behavior analysis model based on the behavior analysis index information, the method further includes:

[0056] Displaying a first interface, wherein the first interface includes a battery life prediction switch;

[0057] Receiving an operation of turning on the battery life prediction switch;

[0058] The step of determining a target operation object sequence based on the behavior analysis index information through a user behavior analysis model includes:

[0059] In response to the start operation, acquiring the behavior analysis index information;

[0060] Based on the behavior analysis index information, the target operation object sequence is determined through the user behavior analysis model.

[0061] In this way, by displaying the first interface to the user, the user can interact with the electronic device based on the first interface when the user needs to determine the battery life, so that the electronic device automatically makes predictions, thereby improving the user experience.

[0062] In a second aspect, a device for predicting battery life is provided, the device for predicting battery life has the function of implementing the method for predicting battery life in the first aspect. The device for predicting battery life includes at least one module, and the at least one module is used to implement the method for predicting battery life provided in the first aspect.

[0063] In a third aspect, an electronic device is provided, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the computer program, the method for predicting battery life as described in the first aspect above is implemented.

[0064] In a fourth aspect, a computer-readable storage medium is provided, wherein instructions are stored in the computer-readable storage medium, and when the computer-readable storage medium is executed on a computer, the computer executes the method for predicting battery life described in the first aspect.

[0065] In a fifth aspect, a computer program product comprising instructions is provided, which, when executed on a computer, enables the computer to execute the method for predicting battery life described in the first aspect.

[0066] The technical effects obtained by the above-mentioned second, third, fourth and fifth aspects are similar to the technical effects obtained by the corresponding technical means in the above-mentioned first aspect, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0067] Figure 1 is a schematic diagram showing an application scenario according to an exemplary embodiment;

[0068] Figure 2 is a schematic diagram of an application scenario according to another exemplary embodiment;

[0069] Figure 3 is a schematic diagram of a framework of a software system according to an exemplary embodiment;

[0070] Figure 4 is a schematic diagram of a data analysis framework according to an exemplary embodiment;

[0071] Figure 5 is a flowchart of a method for constructing a user behavior analysis model according to an exemplary embodiment;

[0072] Figure 6 is a schematic diagram showing operation behavior data of each user in a characteristic period according to an exemplary embodiment;

[0073] Figure 7is a schematic diagram showing a user personalized behavior sequence according to an exemplary embodiment;

[0074] Figure 8 is a flowchart of a method for constructing an application power consumption analysis model according to an exemplary embodiment;

[0075] Fig. 9 is a schematic diagram of a data analysis framework according to another exemplary embodiment;

[0076] Fig.10 is a schematic diagram of a data analysis framework according to another exemplary embodiment;

[0077] Fig.11 is a schematic diagram showing a collection of application power consumption data according to an exemplary embodiment;

[0078] Fig.12 is a schematic diagram showing a collection of application power consumption data according to another exemplary embodiment;

[0079] Fig.13 is a schematic diagram showing a method flow for determining battery life according to an exemplary embodiment;

[0080] Fig.14 is a schematic diagram of an architecture of a method for determining battery life according to an exemplary embodiment;

[0081] Fig.15 is a schematic diagram showing a user personalized behavior sequence in a current feature period according to an exemplary embodiment;

[0082] Fig.16 is a schematic diagram showing a target operation object sequence according to an exemplary embodiment;

[0083] Fig.17 is a schematic diagram showing a target power consumption data set according to an exemplary embodiment;

[0084] Fig.18 is a schematic structural diagram of a device for predicting battery life according to an exemplary embodiment;

[0085] Fig.19 The diagram is a schematic structural diagram of an electronic device according to an exemplary embodiment. DETAILED DESCRIPTION

[0086] In order to make the objectives, technical solutions and advantages of the present application clearer, the implementation methods of the present application will be further described in detail below in conjunction with the accompanying drawings.

[0087] It should be understood that the "multiple" mentioned in this application refers to two or more. In the description of this application, unless otherwise specified, " / " means or, for example, A / B can mean A or B; "and / or" in this article is only a description of the association relationship of associated objects, indicating that there can be three relationships, for example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone. In addition, in order to facilitate the clear description of the technical solution of this application, the words "first" and "second" are used to distinguish between the same items or similar items with basically the same functions and effects. Those skilled in the art can understand that the words "first" and "second" do not limit the quantity and execution order, and the words "first" and "second" do not limit them to be different.

[0088] References to "one embodiment" or "some embodiments" etc. described in the specification of this application mean that one or more embodiments of the present application include specific features, structures or characteristics described in conjunction with the embodiment. Therefore, the statements "in one embodiment", "in some embodiments", "in some other embodiments", "in some other embodiments", etc. that appear in different places in this specification do not necessarily refer to the same embodiment, but mean "one or more but not all embodiments", unless otherwise specifically emphasized in other ways. The terms "including", "comprising", "having" and their variations all mean "including but not limited to", unless otherwise specifically emphasized in other ways.

[0089] First, the application scenarios involved in the embodiments of the present application are introduced.

[0090] As an example of the present application, when a user wants to check the battery life of an electronic device, the user can trigger the electronic device to display a battery management interface through the path of "Settings-Battery", such as the battery management interface Figure 1 As shown in S1 in (a) of FIG. 1 , the battery management interface S1 includes an “intelligent battery life evaluation” option 10 . Thus, the user can trigger the switch control of the “intelligent battery life evaluation” option 10 to the on state, such as Figure 1 In response to the user turning on the switch control of the "intelligent battery life evaluation" option 10, the electronic device begins to evaluate the battery life of the electronic device, that is, predicting how long the battery of the electronic device can continue to be used. Figure 1 As shown in Figure (c), the electronic device can display the prediction result 11 below the "Intelligent Battery Life Evaluation" option, such as the displayed prediction result 11 being "expected to continue using for 17 hours and 55 minutes."

[0091] In one example, when the switch control of the "intelligent battery life evaluation" option 10 is turned on, the electronic device can update the prediction result after a certain period of time (such as 10 minutes). Figure 2 After 10 minutes, the electronic device predicts the battery life again, and then updates the prediction result 11 in the battery management interface S1 to the latest prediction result, for example, the prediction result 11 is updated to "expected to continue using for 17 hours and 44 minutes".

[0092] Of course, if the user does not need to continue to view the prediction results, the user can trigger the switch control of the "Smart Endurance Evaluation" option 10 to the off state, that is, trigger it to the Figure 1 The state shown in Figure (a) in the figure, in this case, the electronic device no longer displays the prediction result 11.

[0093] That is, in order to provide users with reasonable battery usage suggestions, the embodiment of the present application provides a method for predicting battery life, which can accurately predict how long the battery of the electronic device can continue to be used based on factors such as the user's usage habits, the current device environment characteristics of the electronic device, and battery properties when the user checks the battery life of the electronic device, and display the prediction results, so that the user can reasonably plan the use of the electronic device according to the prediction results. The specific implementation can be seen below.

[0094] Before the method provided in the embodiment of the present application is introduced in detail, the software system of the electronic device is first described. The software system of the electronic device can adopt a layered architecture, an event-driven architecture, a micro-core architecture, a micro-service architecture, or a cloud architecture. The embodiment of the present application takes the Android system with a layered architecture as an example to exemplify the software system of the electronic device.

[0095] Figure 3 is a block diagram of a software system of an electronic device provided in an embodiment of the present application. Figure 3 The layered architecture divides the software into several layers, each with clear roles and division of labor. The layers communicate with each other through software interfaces. In some embodiments, the Android system is divided into four layers, from top to bottom, namely, the application layer, the application framework layer, the Android runtime (Android runtime) and the system layer, and the kernel layer.

[0096] The application layer can include a series of application packages. Figure 3 As shown, the application package may include camera, gallery, calendar, call, map, navigation, WLAN, Bluetooth, music, video, short message and other applications.

[0097] The application framework layer provides an application programming interface (API) and a programming framework for the applications in the application layer. The application framework layer includes some predefined functions. As an example of the present application, the application framework layer includes a data acquisition module, a user behavior analysis module, an application power consumption analysis module, and a battery life prediction module.

[0098] The data collection module is used to collect user operation behavior data and application power consumption data. In one example, the data collection module can be added by embedding points in the application manager, where the application manager is a system component used to manage applications in electronic devices, and can know when the application is started and when it exits. User operation behavior data is a record of the user's use of applications, which can be used to characterize when the user used which application and how long it was used. Application power consumption data includes data such as application power consumption, application information of power-consuming applications, physical environment indicator values, and battery attribute information. The application information of power-consuming applications is used to indicate which application is consuming power, such as application information can be application ID, etc. The physical environment indicator value includes the value of at least one device environment factor that affects the power consumption of the electronic device, such as the physical environment indicator value can include screen brightness, volume, device temperature, network status, etc. The battery attribute information includes information related to the characteristics and status of the battery, such as battery attribute information can include battery model, battery capacity, life, internal discharge rate, internal resistance and other indicators. In one example, the data collection module includes a user behavior collection module and a power consumption collection module, the user behavior collection module is used to collect user operation behavior data, and the power consumption collection module is used to collect application power consumption data.

[0099] The user behavior analysis module is used to analyze the user's operation behavior.

[0100] The application power consumption analysis module is used to analyze the power consumption of each application under the current device status.

[0101] The battery life prediction module is used to predict battery life.

[0102] In addition, if Figure 3 As shown, the application framework layer may also include a display module, a battery management module, a sensor module, an audio module, a communication module, etc. Among them, the display module can be used to control the interface display and monitor the user's touch events, such as displaying the first interface and the controls in the first interface, monitoring the user's touch events on the controls, etc. The battery management module can be used to manage the battery of the electronic device. The sensor module can be used to detect the screen brightness, the device temperature of the electronic device, etc. The audio module can be used to control the volume of the electronic device. The communication module can be used to control and manage the communication network of the electronic device.

[0103] Android Runtime includes core libraries and virtual machines. Android runtime is responsible for scheduling and management of the Android system. The core library consists of two parts: one is the function that the Java language needs to call, and the other is the Android core library. The application layer and the application framework layer run in the virtual machine. The virtual machine executes the Java files of the application layer and the application framework layer as binary files. The virtual machine is used to perform object life cycle management, stack management, thread management, security and exception management, and garbage collection.

[0104] The system library can include multiple functional modules, such as: surface manager, media library, etc. The surface manager is used to manage the display subsystem and provide fusion of 2D and 3D layers for multiple applications. The media library supports playback and recording of multiple common audio and video formats, as well as static image files, etc. The media library can support multiple audio and video encoding formats, such as: MPEG4, H.264, MP3, AAC, AMR, JPG, PNG, etc.

[0105] The kernel layer is the layer between hardware and software. The kernel layer contains at least display driver, camera driver, audio driver, and sensor driver.

[0106] In the above Figure 3 Based on the electronic device shown, the method for predicting battery life provided by the embodiment of the present application is introduced below. The method for predicting battery life provided by the embodiment of the present application is based on big data analysis. That is, before predicting the battery life, the electronic device can analyze the relationship between various types of data reported by users and power consumption based on big data, and establish a big data analysis and prediction model, so that when the battery life prediction is needed in the future, it can be accurately predicted based on various types of data collected in real time through the established model. Please refer to Figure 4 , the models that need to be pre-established involved in the embodiments of the present application mainly include a user behavior analysis model, an application power consumption analysis model, and a battery life prediction model. The user behavior analysis model is used to analyze the user's habits of using the application in the electronic device, and the application power consumption analysis model is used to analyze the power consumption of the application in a certain device environment. After that, the battery life prediction model can predict the battery life based on the analysis results of the user behavior analysis model and the application power consumption analysis model. Next, the establishment methods of the user behavior analysis model and the application power consumption analysis model are introduced respectively:

[0107] Please refer to Figure 5 , Figure 5is a flowchart of a method for establishing a user behavior analysis model according to an exemplary embodiment. As an example but not a limitation, the method can be Figure 3 The electronic device shown in the figure is executed, and the electronic device is implemented by multiple modules interacting with each other. Specifically, the method may include some or all of the following contents:

[0108] Step 501: The data collection module obtains a plurality of application history usage data, each of the plurality of application history usage data is used to represent a history usage record of an application program.

[0109] As an example of the present application, the historical usage record of an application may include the characteristic period in which the application is used. The characteristic period may be, but is not limited to, working days, holidays, etc. A characteristic period usually includes multiple unit time periods, and the duration of each unit time period is the unit duration. For example, if the unit duration is 1 minute, the multiple unit time periods included in a characteristic period are [00:00, 00:01], [00:01, 00:02], [00:02, 00:03], ..., [24:58, 24:59]. In addition, the historical usage record of an application may also include the time information when the application is used, that is, at what point in time the application is used.

[0110] In one example, the data collection module can obtain multiple application history usage data based on the daily accumulated user operation behavior data. The accumulated user operation behavior data refers to the data collected and recorded by the data collection module when the user uses the application in the electronic device on a daily basis. For example, the user operation behavior data of an application may include but is not limited to the application usage time, the characteristic cycle when it is used, the application category, the time information when it is used, and other data. The application categories include but are not limited to playback applications, operation applications, and standby. Playback applications may refer to applications for playing videos and audios, such as multimedia applications; operation applications may refer to applications for chatting or office work, such as instant messaging applications.

[0111] In implementation, since the application manager can perceive the usage of the application when the user is using the application in the electronic device, based on this, the data collection module can periodically collect the application usage records through the application manager. For example, the data collection period is T0, and the collected usage records are used to characterize which application is used at what time of the week and how long the user used it. In this way, as the electronic device is used over time, the data collection module can accumulate a large amount of user operation behavior data, and then, based on the accumulated user operation behavior data, multiple application history usage data can be obtained.

[0112] In one example, the specific implementation of obtaining multiple application history usage data based on the recorded user operation behavior data may include: filtering out user operation behavior data with a usage time shorter than a preset time from the recorded user operation behavior data based on the usage time of each application in each user operation behavior data, and determining the filtered user operation behavior data as multiple application history usage data. The preset time can be set according to demand, for example, the preset time can be 10 seconds.

[0113] When an application is used for a short time, the user may not use the application. For example, the user may just quickly slide across the interface of an application. In this case, the use of this type of application can be ignored, that is, the user operation behavior data corresponding to the application has no reference significance. Therefore, when conducting big data analysis, such user operation behavior data can be deleted, and then the remaining user operation behavior data can be used as application history usage data.

[0114] It should be noted that the above specific implementation method of obtaining multiple application history usage data based on the recorded user operation behavior data is only exemplary. In another example, the recorded user operation behavior data can also be directly determined as multiple application history usage data; or, some information in the recorded user operation behavior data can also be filtered, such as filtering to application category information, and then the filtered user operation behavior data is determined as application history usage data.

[0115] It should also be noted that the data collection period T0 represents the minimum granularity of data collection, which can determine the minimum time unit of the user behavior analysis model. Setting a reasonable data collection period can affect the accuracy and efficiency of the model analysis. As an example but not a limitation, the data collection period T0 can be a unit time length, such as 1 minute.

[0116] Step 502: The data collection module groups the multiple application history usage data based on the characteristic period, and obtains multiple groups of application history usage data, wherein one group corresponds to one characteristic period.

[0117] As mentioned above, the characteristic period can be a working day, a holiday, etc. For ease of description and understanding, the characteristic period is denoted as E n , where n = 1, 2, 3, ..., N.

[0118] In order to improve the efficiency of subsequent analysis, the data collection module can group multiple application history usage data in different dimensions and types according to data characteristics, so as to use the grouped application history usage data for subsequent data modeling. As an example of the present application, the data collection module groups the multiple application history usage data based on the characteristic period as the dimension, so that after grouping, the characteristic period of each application history usage data in each group of application history usage data is the same.

[0119] For example, please refer to Figure 6 , in the characteristic period E1, the historical usage data of each application are as follows Figure 6 As shown, one row represents the historical usage data of an application when the characteristic period is E1, and a cell in each row represents a unit time period, or in other words, a data collection period. The character in each cell represents the user's operation object in this time period. For example, when the character in the cell is "a", it means that the user's operation object in this unit time period is application a. For example, please refer to Figure 6 In the first row, during the unit time period from t to t+T0, the electronic device is in standby mode, during the unit time period from t+T0 to t+2T0, the user uses application a in the electronic device, during the unit time period from t+2T0 to t+3T0, the user continues to use application a, and so on.

[0120] It should be noted that, when T0 is set reasonably, the user's operation object in a unit time period is usually only one. Of course, in some cases, the user's operation object in a unit time period may also include multiple. Figure 6 Some cells shown in include multiple characters, for example, a cell includes a and b. In this case, the method provided in the embodiment of the present application can still be used to establish a model.

[0121] It should be noted that the embodiment of the present application takes the characteristic period as a dimension for grouping as an example. In another example, classification can also be performed based on other characteristics as a dimension, for example, classification can also be performed based on the application type as a dimension, such as classification according to standby, playback type application, operation type application, etc., and the embodiment of the present application does not limit this.

[0122] Step 503: The data collection module sends multiple groups of application history usage data to the user behavior analysis module.

[0123] As an example but not limitation, the data collection module can send multiple sets of application history usage data to the user behavior analysis module, and the user behavior analysis module will model based on the multiple sets of application history usage data, that is, the user behavior analysis module will establish a user behavior analysis model.

[0124] Step 504: The user behavior analysis module counts the usage frequency of each application program used in each unit time period in each corresponding characteristic period based on each time information in each group of application history usage data.

[0125] As an example of the present application, the time granularity of user behavior analysis can be consistent with the time granularity of data collection, that is, the frequency of use of each program used in each unit time period in each characteristic cycle can be analyzed with unit time length as the granularity, so as to determine the operation object (that is, the operated application) in each unit time period in each characteristic cycle.

[0126] In implementation, after grouping multiple application history usage data, the user personalized behavior sequence corresponding to the characteristic period corresponding to each group of application history usage data can be determined based on each group of application history usage data. The user personalized behavior sequence includes multiple applications, and each application corresponds to a unit time period, indicating that the user used this application during this unit time, so the user personalized behavior sequence can be used to characterize the applications that the user may use in sequence in the corresponding characteristic period. For example, please refer to Figure 7 , Figure 7 It is a user personalized behavior sequence corresponding to a characteristic period shown according to an exemplary embodiment. It is not difficult to understand that in this characteristic period, starting from time t, the user uses application a, application a, application a, application b, application f, etc. in each unit time period. That is, the user behavior analysis module can analyze the user's habit of using applications corresponding to each characteristic period based on the application history usage data corresponding to each characteristic period.

[0127] To this end, for any set of application history usage data among the multiple sets of application history usage data, the usage frequency of each application used in each unit time period in any set of corresponding feature period is counted based on the various time information in any set of application history usage data, so that the user's personalized behavior sequence under the characteristic period corresponding to any set can be determined based on the counted usage frequency.

[0128] For any unit time period in each unit time period, the usage frequency of each application used in the unit time period can be determined by the following formula (1):

[0129]

[0130] Among them, P i Indicates the usage frequency of application i used in the unit time period, N irepresents the total number of times application i is used in the unit time period, and N represents the total number of times all applications used in the unit time period.

[0131] Step 505: The user behavior analysis module determines the user personalized behavior sequence corresponding to each characteristic period based on the usage frequency of each application used in each unit time period in each group of corresponding characteristic periods.

[0132] As an example of the present application, for a feature period corresponding to any one of multiple groups, an implementation method for determining a user personalized behavior sequence corresponding to the feature period based on the usage frequency of each application used in each unit time period in the feature period is to determine the user's habitual operation objects in each unit time period in the period feature, and then determine the sequence composed of the user's operation objects in each determined unit time period as the user personalized behavior sequence corresponding to the period feature.

[0133] In one example, for any unit time period in the characteristic period, the user behavior analysis module can determine the maximum usage frequency of each application used in the any unit time period, as shown in formula (2). Then, based on the determined maximum usage frequency, the operation object in the any unit time period is determined, that is, the application habitually used by the user in the any unit time period is determined.

[0134] Op [t~t+T0] =max[P1,P2,P3,...](2)

[0135] Among them, Op [t~t+T0] It is the maximum frequency of use within a unit time period.

[0136] It is not difficult to understand that in one possible case, Op [t~t+T0] The number of is one, in another possible case, Op [t~t+T0] The number is multiple. According to Op [t~t+T0] The specific implementation of determining the operation object within any unit time period according to the determined maximum usage frequency may include the following two cases:

[0137] In the first case, for any unit time period in each unit time period, if the number of applications with the highest usage frequency in any unit time period is one, the application with the highest usage frequency is determined as the operation object in any unit time period.

[0138] That is, in Op [t~t+T0]In the case of only one, the application with the highest frequency of use can be directly determined as the user's operation object in the unit time period, indicating that the user usually uses the application with the highest frequency of use in this unit time period. For example, in the unit time period t~t+T0, if the application corresponding to the highest frequency of use is application a, then in the user behavior analysis, it is determined that the operation object in the unit time period t~t+T0 is application a, that is, Figure 7 As shown, for the user personalized behavior sequence, it is determined that the element corresponding to the unit time period t to t+T0 is application a.

[0139] In the second case, if there are multiple applications with the highest usage frequency in any unit time period, the operation object determined in the previous unit time period is determined as the operation object in any unit time period.

[0140] That is, in Op [t~t+T0] If it is not unique, the operation object determined in the previous unit time period of the unit time period can be determined as the operation object in the unit time period. For example, if the user used application a in the previous unit time period, it is very likely that the user will continue to use application a in the current unit time period, so application a can continue to be determined as the operation object in the current unit time period.

[0141] It should be noted that in Op [t~t+T0] In the non-unique case, the above implementation method is exemplary. In another example, an application can be selected from multiple applications corresponding to the maximum usage frequency according to a preset selection rule, and the selected application can be determined as the user's operation object within the unit time period. The embodiment of the present application is not limited to this.

[0142] According to the above method, the operation object in each unit time period in a characteristic cycle can be determined, and then the user personalized behavior sequence corresponding to this characteristic cycle can be determined. For example, the user personalized behavior sequence determined under the characteristic cycle E1 (such as working days) is as follows Figure 7 As shown, in the unit time period t~t+T0 (such as 14:00~14:01), the predicted user operation behavior is "operating application a"; in the unit time period t+2T0~t+3T0 (such as 14:02~14:03), the predicted user operation behavior is "operating application a".

[0143] It is worth noting that the prediction of user personalized behavior sequence changes dynamically over time, that is, as the statistical time gradually increases and the accumulated data gradually increases, in this case, the probability of the same maximum usage frequency will become smaller and smaller, and the accuracy of the statistical results will gradually increase.

[0144] In this way, the user personalized behavior sequence corresponding to each feature period can be determined. In this way, the user behavior analysis module can determine a user behavior analysis model, which includes the corresponding relationship between each feature period in all determined feature periods and the user personalized behavior sequence.

[0145] It should be noted that steps 504 to 505 are an optional implementation method for determining the user personalized behavior sequence corresponding to each characteristic period based on each set of application history usage data in multiple sets of application history usage data, that is, the above-mentioned determination of the user behavior analysis model based on multiple sets of application history usage data is only exemplary. In another example, the user behavior analysis module can also establish a user behavior analysis model based on multiple application history usage data using other statistical predictive analysis or machine learning methods, which is not limited in this embodiment of the present application.

[0146] In the embodiment of the present application, based on the accumulated user operation behavior data, a user behavior analysis model is established to analyze the applications that the user may use in each unit time under different characteristic periods, and output the user personalized behavior sequence corresponding to the different characteristic periods. In this way, the application programs that the user may use in sequence in the future can be predicted based on the real-time collected reporting data and the user behavior operation sequence, and then the battery life can be predicted based on the power consumption of these applications.

[0147] Among them, since the power consumption of applications is affected by the device environment, that is, the power consumption of applications is different in different device environments. Therefore, in order to determine the power consumption of each application that the user may use in the real-time device environment, the electronic device also establishes an application power consumption analysis model, so that when predicting the battery life in the future, the power consumption of each application that the user may use can be determined by the application power consumption analysis model based on the real-time device environment.

[0148] As an example of this application, please refer to Figure 8 , Figure 8 is a schematic diagram showing a method for establishing an application power consumption analysis model according to an exemplary embodiment. The method may include the following contents:

[0149] Step 801: The data acquisition module obtains multiple key data feature sets corresponding to each application in the electronic device, each key data feature set includes application information of an application, as well as corresponding battery attribute information, physical environment indicator values ​​and power consumption per unit time when used.

[0150] The device environment factors that affect the power consumption of applications generally include two aspects: one is battery attribute information, such as battery model, battery capacity, life, internal discharge rate, internal resistance, etc., and the other is physical environment indicators, such as screen brightness, volume, device temperature, network status, etc. The network status can include connected or disconnected, as well as network strength, etc. Therefore, in the process of establishing an application power consumption analysis model, a large amount of power consumption per unit time of each application in different device environments can be obtained, and then analysis and model construction can be carried out based on these big data.

[0151] In one example, some of the key data feature sets in the multiple key data feature sets can be recorded by the electronic device itself. The key feature data set recorded by itself refers to the power consumption of the application in different device environments recorded by the data collection module when the user uses the application in the electronic device. Please refer to Fig. 9 That is, the data collection module can not only record the use records of the application through the user behavior collection module, but also collect data related to the power consumption of the application through the power consumption collection module, such as recording the power consumption of the application in a unit time, and determining the physical environment index value and battery attribute information when the power is consumed. Then, the recorded power consumption, physical environment index value and battery attribute information are stored with the application information of the power-consuming application as a key feature data set. In this way, as time goes by, the data collection module can record a large number of key data feature sets. During the model analysis and construction process, the electronic device can obtain the key feature data set recorded by itself and obtain other key data feature sets from other data sources (such as a designated service platform, or user import, etc.), thereby obtaining the multiple key data feature sets.

[0152] In one example, the data acquisition module can determine the power consumption of each application per unit time through the battery management module, obtain the screen brightness and device temperature through the sensor module, determine the volume of the electronic device through the audio module, and determine the network status through the communication module. In addition, the battery management module records the battery attribute information, and the data acquisition module obtains the battery attribute information from the battery management module.

[0153] Step 802: The data collection module sends a plurality of key data feature sets to the application power consumption analysis module.

[0154] As an example but not limitation, the data collection module can send multiple key data feature sets to the application power consumption analysis module, and the application power consumption analysis module performs modeling based on the multiple key data feature sets, that is, the application power consumption analysis module establishes an application power consumption analysis model.

[0155] Step 803: Apply the power consumption analysis module to determine the physical environment impact coefficient corresponding to each key data feature set according to the physical environment indicator value in each key data feature set.

[0156] In one example, for any one of the key data feature sets in each key data feature set, the power consumption analysis module can be used to perform data standardization on each physical environment indicator value in the key data feature set, so that each physical environment indicator value is in the [0,100] range after standardization. Thereafter, each standardized physical environment indicator value is weightedly calculated to obtain the physical environment impact coefficient corresponding to the key data feature set.

[0157] For example, the application power consumption analysis module may determine the physical environment impact coefficient based on the standardized physical environment indicator values ​​through the following formula (3):

[0158] inf_coe=(α×inf1+β×inf2+...+γ×inf n )%(3)

[0159] Among them, inf_coe is the physical environment impact coefficient, which is in the range of [0,1]; inf1, inf2, ..., inf n They represent the standardized values ​​of various physical environment indicators respectively; α, β, ..., γ are preset constants.

[0160] In this way, the physical environment impact coefficient corresponding to each key data feature set in the multiple key data feature sets can be determined.

[0161] Step 804: Using the power consumption analysis module, determine the physical environment impact coefficient range in which each key data feature set corresponds to a physical environment impact coefficient from multiple physical environment impact coefficient ranges.

[0162] In one example, multiple physical environment impact coefficient ranges can be set according to requirements. For example, multiple physical environment impact coefficient ranges may include [0, 0.25), [0.25, 0.5), [0.5, 0.75), [0.75, 1).

[0163] For any one of the multiple key data feature sets, after the power consumption analysis module is applied to determine the physical environment impact coefficient corresponding to the key data feature set, the physical environment impact coefficient corresponding to the key data feature set is determined from multiple physical environment impact coefficient ranges to which physical environment impact coefficient range the physical environment impact coefficient corresponding to the key data feature set belongs. For example, if the physical environment impact coefficient corresponding to the key data feature set is 0.18, it can be determined that the physical environment impact coefficient corresponding to the key data feature set belongs to the physical environment impact coefficient range [0,0.25).

[0164] Step 805: The application power consumption analysis module counts the power consumption of each application program per unit time in different device environments based on multiple key data feature sets and the range of physical environment impact coefficients corresponding to each key data feature set.

[0165] According to the previous records, the characteristics of the device environment are determined by the battery attribute information and the physical environment index value. Fig.10 As shown, the application power consumption analysis module can be further divided into an environment analysis module and a power consumption statistics module. When counting the power consumption of each application in different device environments within a unit time, for any application, the environment analysis module can obtain the key data feature set recorded by the application in the same device environment from multiple key data feature sets according to the battery attribute information in each key data feature set and the range of the physical environment impact coefficient corresponding to each key data feature set, and then the power consumption statistics module extracts the power consumption information from each key data feature set obtained by the environment analysis module to obtain multiple power consumptions, and then the average power consumption of the application in the same device environment can be determined, and the determined average power consumption is determined as the power consumption of the application in the device environment within a unit time. Afterwards, based on the power consumption of each application in each device environment within a unit time, a power consumption data set in each device environment can be established, and a power consumption data set corresponding to a device environment is used to characterize the power consumption of each application in the device environment within a unit time.

[0166] Step 806: The application power consumption analysis module establishes a plurality of mapping relationships based on the power consumption of each application program within a unit time under different device environments.

[0167] Among them, each mapping relationship among the multiple mapping relationships includes the correspondence between the first-level physical indication information, the physical environment impact coefficient range, and the second-level physical indication information, wherein different first-level physical indication information corresponds to different battery attribute information, and different second-level physical indication information corresponds to different power consumption data sets.

[0168] In one example, the first-level physical indication information is recorded as ENV_L1_n (n=1,2,3,...). When n is different, it represents different first-level physical indication information, and different first-level physical indication information corresponds to different battery attribute information. Different battery attribute information refers to different battery attribute sizes, but the dimension of the attribute is the same. For example, the battery attribute information corresponding to ENV_L1_1 includes battery model L1, battery capacity M1, life K1, internal discharge rate E1, and internal resistance S1; the battery attribute information corresponding to ENV_L1_1 includes battery model L2, battery capacity M2, life K2, internal discharge rate E2, and internal resistance S2; the battery attribute information corresponding to ENV_L1_3 includes battery model L3, battery capacity M3, life K3, internal discharge rate E3, and internal resistance S3, etc.

[0169] In one example, the secondary physical indication information is recorded as ENV_L2_n (n=1, 2, 3, ...). When n is different, it represents different secondary physical indication information, and different secondary physical indication information corresponds to different power consumption data sets. For example, the power consumption data set corresponding to ENV_L2_1 is as follows: Fig.11 As shown, the power consumption data set corresponding to ENV_L2_2 is as follows Fig.12 As shown, etc.

[0170] In implementation, for each power consumption data set, a mapping relationship between each power consumption data set and the primary physical indication information and the secondary physical indication information can be established according to the battery attribute information and the physical environment indicator value corresponding to each power consumption data set, so that multiple mapping relationships can be established, and then an application power consumption analysis model is established, and the application power consumption analysis model includes the multiple mapping relationships. Exemplarily, the multiple mapping relationships are shown in Table 1.

[0171] Table 1

[0172]

[0173] The application power consumption analysis model can be used to determine the power consumption of each application per unit time in various device environments. For example, when the first-level physical indicator information corresponding to the battery attribute information is ENV_L1_1, and the physical environment impact coefficient corresponding to the physical environment indicator value is in the range of [0,0.25), the second-level physical indicator information can be determined to be ENV_L2_1, so that the power consumption of each application per unit time in the device environment corresponding to the battery attribute information and the physical environment indicator value can be determined. Fig.11 The power consumption data set shown is recorded.

[0174] In an embodiment of the present application, by analyzing a massive set of key data features, the power consumption of each application in a unit time under various device environments is determined, and a mapping relationship between the device environment and the power consumption of the application is established. This facilitates the subsequent prediction of battery life. The power consumption of each application can be determined based on the real-time device environment, and then the possible power consumption of the battery in the future can be determined in combination with the predicted applications that the user may operate, so that the battery life can be accurately predicted.

[0175] Based on the above embodiments, the electronic device can predict the battery life according to the current device environment and other information through the battery life prediction model, combined with the above user behavior analysis model and application power consumption analysis model. Fig.13 , Fig.13 is a flowchart of a method for predicting battery life according to an exemplary embodiment. As an example but not a limitation, the method can be performed by the above Figure 3 The electronic device shown is executed, and the electronic device is implemented by multiple modules interacting with each other. The method may include part or all of the following contents:

[0176] Step 1301: The display module displays a first interface, which includes a battery life prediction switch.

[0177] As an example and not limitation, the first interface may be Figure 1 In S1 of Figure (a), the battery life prediction switch is a switch control corresponding to option 10 of “Intelligent battery life evaluation”.

[0178] Step 1302: The display module receives a turn-on operation of a battery life prediction switch.

[0179] For example, Figure 1 As shown in Figure (b), when the user wants the electronic device to predict the battery life, the switch control corresponding to the "Intelligent Battery Life Evaluation" option 10 can be triggered to the on state, and accordingly, the electronic device receives the on operation of the battery life prediction switch.

[0180] Step 1303: In response to the start-up operation, the display module notifies the user behavior analysis module and the application power consumption analysis module to perform data analysis.

[0181] That is, when the user triggers the electronic device to predict the battery life, the display module notifies the user behavior analysis module and the application power consumption analysis module, so that the user behavior analysis module performs user behavior analysis through the following steps 1304 to 1305, and the application power consumption analysis module performs power consumption analysis through the following steps 1307 to 1310.

[0182] It should be noted that the above steps 1301 to 1303 are an optional example. In another example, the triggering condition for the display module to notify the user behavior analysis module and the application power consumption analysis module to perform data analysis may also include other situations. For example, when the battery life prediction switch is turned on, the electronic device can update the predicted results after a certain period of time. For this reason, the display module notifies the user behavior analysis module and the application power consumption analysis module to perform data analysis so as to predict the battery life again through subsequent steps. For specific application scenarios, please refer to Figure 2 The embodiments shown will not be described in detail here.

[0183] Step 1304: The user behavior analysis module obtains behavior analysis index information.

[0184] As an example of the present application, the behavior analysis index information may include the current feature period and the current time point, for example, the current feature period is Monday and the current time point is 14:00.

[0185] Step 1305: The user behavior analysis module determines the target operation object sequence through the user behavior analysis model based on the behavior analysis index information.

[0186] Since the user analysis model can predict the programs that the user may use sequentially in the future, based on the behavior analysis index information, the user behavior analysis model can determine the target operation object sequence starting from the current time point in the current feature period. The target operation object sequence includes at least one application, and the at least one application is arranged in sequence according to the order of operation.

[0187] According to the above records, the user behavior analysis model includes a personalized user behavior sequence corresponding to each of the multiple feature cycles, each feature cycle includes multiple unit time periods, each personalized user behavior sequence includes multiple applications, and each application corresponds to a unit time period. Therefore, according to the current feature cycle, the personalized user behavior sequence corresponding to the current feature cycle can be determined from the personalized user behavior sequences corresponding to the multiple cycle features, and then the subsequence consisting of the applications corresponding to each unit time period after the current time point in the personalized user behavior sequence is determined as the target operation object sequence.

[0188] For example, the current feature period is Monday, and the current time is 14:00. The user personalized behavior sequence corresponding to the current feature period is determined from the user personalized behavior sequences corresponding to the multiple period features, as follows: Fig.15As shown in the figure. The applications corresponding to each unit time period after 14:00 are application a, application a, application t, application a, application a, application n, application m, application a, application b, application m, application c, application d, ... At this point, the target operation object sequence can be determined as follows: Fig.16 As shown, that is, from the current time point in the future, the application programs that the user may use in sequence in a unit time period are a, a, t, a, a, n, m, a, b, m, c, d, ...

[0189] Step 1306: The user behavior analysis module sends the target operation object sequence to the battery life prediction module.

[0190] Please refer to Fig.14 ,After determining the target operation object sequence based on the behavior analysis index information through the user behavior analysis model, the target operation object sequence is sent to the battery life prediction model so as to subsequently perform the battery life prediction through the battery life prediction model.

[0191] Step 1307: The application power consumption analysis module determines the current physical environment impact coefficient based on multiple current physical environment indicator values.

[0192] Exemplarily, the current physical environment indicators include screen brightness, volume, device temperature, and network status, and the values ​​of the current physical environment indicators are T1, V1, C1, and Q1, respectively. Thus, the current physical environment impact coefficient can be determined according to the multiple current physical environment indicator values ​​through the above formula (3).

[0193] Step 1308: Using the power consumption analysis module, determine the target physical environment impact coefficient range in which the current physical environment impact coefficient is located from multiple physical environment impact coefficient ranges.

[0194] Step 1309: Use the power consumption analysis module to determine the target primary physical indication information corresponding to the battery attribute information of the electronic device.

[0195] As an example of the present application, the power consumption analysis module can determine the battery attribute information of the electronic device from the battery management module. Afterwards, the first-level physical indication information corresponding to the battery attribute information (hereinafter referred to as the target and physical indication information) can be determined based on the correspondence between the battery attribute information and the first-level physical indication information.

[0196] It should be noted that the application power consumption analysis module can record the battery attribute information of the electronic device. In this way, when the battery life evaluation is needed again in the future, the battery attribute information can be directly obtained, avoiding the need to obtain it from the battery power consumption module every time.

[0197] Step 1310: The power consumption analysis module applies a power consumption analysis model to determine the secondary physical indication information corresponding to the target physical environment impact coefficient range and the target primary physical indication information from multiple mapping relationships, and the target power consumption data set is the power consumption data set corresponding to the determined secondary physical indication information.

[0198] The target power consumption data set is used to represent the power consumption per unit time of each application in the electronic device under the current device environment.

[0199] According to the above records, the application power consumption analysis model can determine the power consumption of each application program per unit time in different device environments. As an example of this application, Figure 8 As recorded in the illustrated embodiment, the application power consumption analysis model includes a plurality of mapping relationships, and each mapping relationship includes a correspondence between primary physical indication information, a physical environment impact coefficient range, and secondary physical indication information. In this way, the secondary physical indication information corresponding to the target physical environment impact coefficient range and the target primary physical indication information can be determined from the plurality of mapping relationships. For example, if the target physical environment impact coefficient range is [0.5, 0.75), and the target primary physical indication information is ENV_L1_1, then according to the plurality of mapping relationships shown in Table 1, it can be determined that the secondary physical indication information corresponding to the target physical environment impact coefficient range and the target primary physical indication information is ENV_L2_3. Afterwards, the power consumption data set corresponding to ENV_L2_3 is obtained by applying the power consumption analysis model, and the target power consumption data set is obtained. For example, the target power consumption data set is as follows: Fig.17 shown.

[0200] It should be noted that steps 1306 to 1310 are an optional implementation method for determining a target power consumption data set by applying a power consumption analysis model based on the current physical environment impact coefficient and the battery property information of the electronic device.

[0201] Step 1311: The application power consumption analysis module sends a target power consumption data set to the battery life prediction module.

[0202] Please continue to refer to Fig.14 By applying the power consumption analysis model, after determining the target power consumption data set based on the current physical environment indicator value, the target power consumption data set is sent to the battery life prediction model. In this way, the battery life prediction model can be used to predict the battery life based on the target operation object sequence and the target power consumption data set. The specific implementation can be seen in the following steps.

[0203] Step 1312: The battery life prediction module determines the power consumption per unit time of each application in the target operation object sequence under the current device environment based on the target power consumption data set.

[0204] Since the target power consumption data set is used to characterize the power consumption of each application in the electronic device in the current device environment per unit time, the power consumption of each application in the target operation object sequence in the current device environment per unit time can be determined based on the power consumption data set.

[0205] For example, if the determined target power consumption data set is as follows Fig.17 As shown, in the target operation object sequence Fig.16 In the case shown, it is possible to determine that the power consumption of each application in the target operation object sequence, that is, application a, application a, application t, application a, application a, application n, application m, application a, application b, application m, application c, application d, etc. in the current device environment per unit time is Qa3, Qa3, Qt3, Qa3, Qa3, Qn3, Qm3, Qa3, Qb3, Qm3, Qc3, Qd3, etc.

[0206] Step 1313: The battery life prediction module determines at least one reference application from the target operation object sequence according to the chronological order of operations and the power consumption of each application in the target operation object sequence per unit time, the total power consumption of at least one reference application is greater than or equal to the remaining total power, and the difference between the total power consumption of at least one reference application and the remaining total power is minimal.

[0207] As an example of the present application, according to the chronological order of operations, the first i applications satisfying the following formula (4) are determined from the target operation object sequence as at least one reference application:

[0208]

[0209] Among them, Q0 represents the remaining total power, Q i j represents the power consumption per unit time of the i-th application in the target operation object sequence under the current device environment, for example, j is 3.

[0210] Step 1314: The battery life prediction module counts the number of at least one reference application.

[0211] That is, the minimum i in the above formula (4) is determined. For example, if the power consumption of only two application programs a can satisfy the above formula (4), then the number of at least one reference application program can be determined to be 2.

[0212] Step 1315: The battery life prediction module determines the battery life as a result of multiplying the number of at least one reference application by the unit time.

[0213] For example, if the number of at least one reference application is z and the unit duration is T0, then the battery life duration Min=z×T0 can be determined.

[0214] Of course, the implementation method of determining the battery life based on the number of at least one reference application and the unit duration is only exemplary. In another example, the battery life can also be determined based on the number of at least one reference application and the unit duration by other methods, such as multiplying the unit duration by a preset coefficient, and multiplying the multiplied result by the number of at least one reference application to obtain the battery life, which is not limited in the embodiments of the present application.

[0215] It should be noted that the above steps 1312 to 1315 are an optional implementation method for determining the battery life based on the target operation object sequence, the remaining total power and the target power consumption data set.

[0216] It should be noted that steps 1305 to 1315 are an optional implementation method for determining the battery life of the electronic device based on the target operation object sequence, the battery property information of the electronic device, the current physical environment indicator value and the remaining total power.

[0217] Step 1316: The battery life prediction module sends the determined battery life to the display module.

[0218] Step 1317: The display module displays the determined battery life in the first interface.

[0219] For example Figure 1 In Figure (c), after the battery life is determined, the battery life is displayed below "Intelligent Battery Life Evaluation". In this way, the user can use the electronic device in a planned way according to the displayed battery life. For example, when the battery life is short, the user can turn on the low power mode.

[0220] In an embodiment of the present application, based on the behavior analysis index information, a target operation object sequence is determined through a user behavior analysis model, and the target operation behavior sequence is used to characterize the applications that the user may operate in sequence in the future, that is, the user behavior analysis module is used to predict the user's use of applications in the electronic device in the future. Afterwards, the battery life of the electronic device is determined based on the determined target operation object sequence, combined with the electronic device's own battery attribute information, the current physical environment index value, and the remaining total power, wherein the physical environment index value includes the value of at least one device environment factor that affects the power consumption of the electronic device. That is, when predicting the battery life, the user's application usage habits and the device environment factors that affect power consumption are comprehensively considered, thereby improving the accuracy of the battery life prediction.

[0221] Please refer to Fig.18 , Fig.18 1 is a schematic diagram of a structure of a device for predicting battery life according to an exemplary embodiment. The device is configured in the above electronic device. The device may include a first determination module 1810, a second determination module 1820 and an interface display module 1830:

[0222] A first determination module 1810 is used to determine a target operation object sequence through a user behavior analysis model based on the behavior analysis index information, wherein the target operation object sequence is used to represent the application programs that the user may sequentially operate in a future period of time, and the user behavior analysis model can predict the operation behavior of the user;

[0223] A second determining module 1820 is configured to determine the battery life of the electronic device according to the target operation object sequence, the battery property information of the electronic device, the current physical environment index value, and the remaining total power, wherein the physical environment index value includes a value of at least one device environment factor that affects the power consumption of the electronic device;

[0224] The interface display module 1830 is used to display the battery life.

[0225] In one example, the first determination module is used to execute the operations of steps 1304 to 1306 above; the second determination module is used to execute the operations of steps 1307 to 1316 above; and the interface display module is used to execute the operations of steps 1301 to 1303 above, and the operation of step 1317 above.

[0226] Optionally, the first determining module is further configured to execute the above Figure 5 Some or all of the operations in the illustrated embodiments.

[0227] Optionally, the second determining module is further configured to execute the above Figure 8Some or all of the operations in the illustrated embodiments.

[0228] In an embodiment of the present application, based on the behavior analysis index information, a target operation object sequence is determined through a user behavior analysis model, and the target operation behavior sequence is used to characterize the applications that the user may operate in sequence in the future, that is, the user behavior analysis module is used to predict the user's use of applications in the electronic device in the future. Afterwards, the battery life of the electronic device is determined based on the determined target operation object sequence, combined with the electronic device's own battery attribute information, the current physical environment index value, and the remaining total power, wherein the physical environment index value includes the value of at least one device environment factor that affects the power consumption of the electronic device. That is, when predicting the battery life, the user's application usage habits and the device environment factors that affect power consumption are comprehensively considered, thereby improving the accuracy of the battery life prediction.

[0229] It should be noted that the device for predicting battery life provided in the above embodiment only uses the division of the above-mentioned functional modules as an example when predicting the battery life. In actual applications, the above-mentioned functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.

[0230] The functional units and modules in the above embodiments may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit, and the above integrated units may be implemented in the form of hardware or in the form of software functional units. In addition, the specific names of the functional units and modules are only for the convenience of distinguishing each other, and are not used to limit the protection scope of the embodiments of the present application.

[0231] The device for predicting battery life provided in the above embodiments and the method embodiment for predicting battery life belong to the same concept. The specific working process of the units and modules in the above embodiments and the technical effects brought about can be found in the method embodiment part and will not be repeated here.

[0232] Next, the electronic devices involved in the embodiments of the present application are described. The electronic devices may be mobile phones, sports cameras (GoPro), digital cameras, tablet computers, desktop computers, laptop computers, handheld computers, notebook computers, vehicle-mounted devices, ultra-mobile personal computers (UMPC), netbooks, cellular phones, personal digital assistants (PDA), augmented reality (AR) and virtual reality (VR) devices, etc., which are not limited in the embodiments of the present application.

[0233] Fig.19 is a schematic diagram of the structure of an electronic device provided in an embodiment of the present application. Fig.19 The electronic device 100 may include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, an earphone interface 170D, a sensor module 180, a button 190, a motor 191, an indicator 192, a camera 193, a display screen 194, and a subscriber identification module (SIM) card interface 195, etc. Among them, the sensor module 180 may include a pressure sensor 180A, a gyroscope sensor 180B, an air pressure sensor 180C, a magnetic sensor 180D, an acceleration sensor 180E, a distance sensor 180F, a proximity light sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, an ambient light sensor 180L, a bone conduction sensor 180M, etc.

[0234] It is to be understood that the structure illustrated in the embodiment of the present application does not constitute a specific limitation on the electronic device 100. In other embodiments of the present application, the electronic device 100 may include more or fewer components than shown in the figure, or combine some components, or split some components, or arrange the components differently. The components shown in the figure may be implemented in hardware, software, or a combination of software and hardware.

[0235] The processor 110 may include one or more processing units, for example, the processor 110 may include an application processor (AP), a modem processor, a graphics processor (GPU), an image signal processor (ISP), a controller, a memory, a video codec, a digital signal processor (DSP), a baseband processor, and / or a neural-network processing unit (NPU), etc. Different processing units may be independent devices or integrated into one or more processors.

[0236] The controller may be the nerve center and command center of the electronic device 100. The controller may generate an operation control signal according to the instruction operation code and the timing signal to complete the control of fetching and executing instructions.

[0237] The processor 110 may also be provided with a memory for storing instructions and data. In some embodiments, the memory in the processor 110 is a cache memory. The memory may store instructions or data that the processor 110 has just used or cyclically used. If the processor 110 needs to use the instruction or data again, it may be directly called from the memory. This avoids repeated access, reduces the waiting time of the processor 110, and thus improves the efficiency of the system.

[0238] In some embodiments, the processor 110 may include one or more interfaces, such as an inter-integrated circuit (I2C) interface, an inter-integrated circuit sound (I2S) interface, a pulse code modulation (PCM) interface, a universal asynchronous receiver / transmitter (UART) interface, a mobile industry processor interface (MIPI), a general-purpose input / output (GPIO) interface, a subscriber identity module (SIM) interface, and / or a universal serial bus (USB) interface, etc.

[0239] It is understandable that the interface connection relationship between the modules illustrated in the embodiment of the present application is only a schematic illustration and does not constitute a structural limitation on the electronic device 100. In other embodiments of the present application, the electronic device 100 may also adopt different interface connection methods in the above embodiments, or a combination of multiple interface connection methods.

[0240] The charging management module 140 is used to receive charging input from a charger. The charger may be a wireless charger or a wired charger. In some wired charging embodiments, the charging management module 140 may receive charging input from a wired charger through the USB interface 130. In some wireless charging embodiments, the charging management module 140 may receive wireless charging input through a wireless charging coil of the electronic device 100. While the charging management module 140 is charging the battery 142, it may also power the electronic device 100 through the power management module 141.

[0241] The power management module 141 is used to connect the battery 142, the charging management module 140 and the processor 110. The power management module 141 receives input from the battery 142 and / or the charging management module 140, and provides power to the processor 110, the internal memory 121, the external memory, the display screen 194, the camera 193 and the wireless communication module 160. The power management module 141 can also be used to monitor parameters such as battery capacity, battery cycle number, battery health status (leakage, impedance), etc. In some other embodiments, the power management module 141 can also be set in the processor 110. In other embodiments, the power management module 141 and the charging management module 140 can also be set in the same device.

[0242] The wireless communication function of the electronic device 100 can be implemented through the antenna 1, the antenna 2, the mobile communication module 150, the wireless communication module 160, the modem processor and the baseband processor.

[0243] Antenna 1 and antenna 2 are used to transmit and receive electromagnetic wave signals. Each antenna in the electronic device 100 can be used to cover a single or multiple communication frequency bands. Different antennas can also be reused to improve the utilization of the antennas. For example, antenna 1 can be reused as a diversity antenna for a wireless local area network. In some other embodiments, the antenna can be used in combination with a tuning switch.

[0244] The mobile communication module 150 can provide solutions for wireless communications including 2G / 3G / 4G / 5G, etc., applied to the electronic device 100. The mobile communication module 150 may include at least one filter, a switch, a power amplifier, a low noise amplifier (LNA), etc. The mobile communication module 150 can receive electromagnetic waves from the antenna 1, and filter, amplify, and process the received electromagnetic waves, and transmit them to the modulation and demodulation processor for demodulation. The mobile communication module 150 can also amplify the signal modulated by the modulation and demodulation processor, and convert it into electromagnetic waves for radiation through the antenna 1. In some embodiments, at least some of the functional modules of the mobile communication module 150 can be set in the processor 110. In some embodiments, at least some of the functional modules of the mobile communication module 150 can be set in the same device as at least some of the modules of the processor 110.

[0245] The modem processor may include a modulator and a demodulator. Among them, the modulator is used to modulate the low-frequency baseband signal to be sent into a medium-high frequency signal. The demodulator is used to demodulate 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. After the low-frequency baseband signal is processed by the baseband processor, it is passed to the application processor. The application processor outputs a sound signal through an audio device (not limited to a speaker 170A, a receiver 170B, etc.), or displays an image or video through a display screen 194. In some embodiments, the modem processor may be an independent device. In other embodiments, the modem processor may be independent of the processor 110 and be set in the same device as the mobile communication module 150 or other functional modules.

[0246] The wireless communication module 160 can provide wireless communication solutions including wireless local area networks (WLAN) (such as wireless fidelity (Wi-Fi) networks), bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), infrared (IR), etc., which are applied to the electronic device 100. The wireless communication module 160 can be one or more devices integrating at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via the antenna 2, modulates the frequency of the electromagnetic wave signal and performs filtering, and sends the processed signal to the processor 110. The wireless communication module 160 can also receive the signal to be sent from the processor 110, modulate the frequency of it, amplify it, and convert it into electromagnetic waves for radiation through the antenna 2.

[0247] In some embodiments, the antenna 1 of the electronic device 100 is coupled to the mobile communication module 150, and the antenna 2 is coupled to the wireless communication module 160, so that the electronic device 100 can communicate with the network and other devices through wireless communication technology. The wireless communication technology may include global system for mobile communications (GSM), general packet radio service (GPRS), code division multiple access (CDMA), wideband code division multiple access (WCDMA), time-division code division multiple access (TD-SCDMA), long term evolution (LTE), BT, GNSS, WLAN, NFC, FM, and / or IR technology, etc. GNSS may include the global positioning system (GPS), the global navigation satellite system (GLONASS), the Beidou navigation satellite system (BDS), the quasi-zenith satellite system (QZSS) and / or the satellite based augmentation system (SBAS).

[0248] The electronic device 100 implements the display function through a GPU, a display screen 194, and an application processor. The GPU is a microprocessor for image processing, which connects the display screen 194 and the application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. The processor 110 may include one or more GPUs that execute program instructions to generate or change display information.

[0249] The display screen 194 is used to display images, videos, etc. The display screen 194 includes a display panel. The display panel can be a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light emitting diode or an active-matrix organic light emitting diode (AMOLED), a flexible light-emitting diode (FLED), Miniled, MicroLed, Micro-oLed, a quantum dot light-emitting diode (QLED), etc. In some embodiments, the electronic device 100 may include 1 or N display screens 194, where N is an integer greater than 1.

[0250] The electronic device 100 can realize the shooting function through ISP, camera 193, video codec, GPU, display screen 194 and application processor.

[0251] The digital signal processor is used to process digital signals, and can process not only digital image signals but also other digital signals. For example, when the electronic device 100 is selecting a frequency point, the digital signal processor is used to perform Fourier transform on the frequency point energy.

[0252] Video codecs are used to compress or decompress digital videos. The electronic device 100 may support one or more video codecs. Thus, the electronic device 100 may play or record videos in various coding formats, such as Moving Picture Experts Group (MPEG) 1, MPEG2, MPEG3, MPEG4, etc.

[0253] NPU is a neural network (NN) computing processor. By drawing on the structure of biological neural networks, such as the transmission mode between neurons in the human brain, it can quickly process input information and can also continuously self-learn. Through NPU, applications such as intelligent cognition of electronic device 100 can be realized, such as image recognition, face recognition, voice recognition, text understanding, etc.

[0254] The external memory interface 120 can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the electronic device 100. The external memory card communicates with the processor 110 through the external memory interface 120 to implement a data storage function, such as storing music, video and other files in the external memory card.

[0255] The internal memory 121 can be used to store computer executable program codes, which include instructions. The processor 110 executes various functional applications and data processing of the electronic device 100 by running the instructions stored in the internal memory 121. The internal memory 121 may include a program storage area and a data storage area. Among them, the program storage area may store an operating system, an application required for at least one function (such as a sound playback function, an image playback function, etc.), etc. The data storage area may store data created by the electronic device 100 during use (such as audio data, a phone book, etc.), etc. In addition, the internal memory 121 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, a universal flash storage (UFS), etc.

[0256] The electronic device 100 can implement audio functions, such as music playback, recording, etc., through the audio module 170, the speaker 170A, the receiver 170B, the microphone 170C, the headphone interface 170D and the application processor.

[0257] The ambient light sensor 180L is used to sense the ambient light brightness. The electronic device 100 can adaptively adjust the brightness of the display screen 194 according to the perceived ambient light brightness. The ambient light sensor 180L can also be used to automatically adjust the white balance when taking pictures. The ambient light sensor 180L can also cooperate with the proximity light sensor 180G to detect whether the electronic device 100 is in a pocket to prevent accidental touches.

[0258] The fingerprint sensor 180H is used to collect fingerprints. The electronic device 100 can use the collected fingerprint characteristics to implement fingerprint unlocking, access application locks, fingerprint photography, fingerprint call answering, etc.

[0259] The temperature sensor 180J is used to detect temperature. In some embodiments, the electronic device 100 uses the temperature detected by the temperature sensor 180J to execute a temperature processing strategy. For example, when the temperature reported by the temperature sensor 180J exceeds a threshold, the electronic device 100 reduces the performance of the processor located near the temperature sensor 180J to reduce power consumption and implement thermal protection. In other embodiments, when the temperature is lower than another threshold, the electronic device 100 heats the battery 142 to avoid abnormal shutdown of the electronic device 100 due to low temperature. In other embodiments, when the temperature is lower than another threshold, the electronic device 100 boosts the output voltage of the battery 142 to avoid abnormal shutdown caused by low temperature.

[0260] The touch sensor 180K is also called a "touch panel". The touch sensor 180K can be set on the display screen 194, and the touch sensor 180K and the display screen 194 form a touch screen, also called a "touch screen". The touch sensor 180K is used to detect touch operations acting on or near it. The touch sensor 180K can pass the detected touch operation to the application processor to determine the type of touch event. Visual output related to the touch operation can be provided through the display screen 194. In other embodiments, the touch sensor 180K can also be set on the surface of the electronic device 100, which is different from the position of the display screen 194.

[0261] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network or other programmable device. The computer instructions may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from a website site, computer, server or data center by wired (such as: coaxial cable, optical fiber, data subscriber line (Digital Subscriber Line, DSL)) or wireless (such as: infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center. The computer-readable storage medium may be any available medium that a computer can access, or a data storage device such as a server or data center that includes one or more available media integrations. The available medium may be a magnetic medium (such as a floppy disk, a hard disk, a magnetic tape), an optical medium (such as a digital versatile disc (DVD)), or a semiconductor medium (such as a solid state disk (SSD)).

[0262] The above are optional embodiments provided for the present application and are not intended to limit the present application. Any modifications, equivalent substitutions, improvements, etc. made within the technical scope disclosed in the present application shall be included in the protection scope of the present application.

Claims

1. A method for predicting battery life, characterized in that: Applied to electronic equipment, the method comprises: Based on the behavior analysis index information, a target operation object sequence is determined through a user behavior analysis model, wherein the target operation object sequence is used to characterize the application programs that the user may sequentially operate in a future period of time, and the user behavior analysis model can predict the operation behavior of the user; Determining the battery life of the electronic device according to the target operation object sequence, the battery property information of the electronic device, the current physical environment index value and the remaining total power, wherein the physical environment index value includes the value of at least one device environment factor that affects the power consumption of the electronic device; Displays stated battery life.

2. The method according to claim 1, characterized in that The number of the current physical environment indicator values ​​is multiple; The determining the battery life of the electronic device according to the target operation object sequence, the battery property information of the electronic device, the current physical environment indicator value and the remaining total power includes: Determine a current physical environment impact coefficient based on multiple current physical environment indicator values; Based on the current physical environment impact coefficient and the battery property information of the electronic device, a target power consumption data set is determined by applying a power consumption analysis model, wherein the target power consumption data set is used to characterize the power consumption of each application in the electronic device within a unit time under the current device environment, and the application power consumption analysis model can determine the power consumption of each application within the unit time under different device environments; The battery life is determined based on the target operation object sequence, the remaining total power and the target power consumption data set.

3. The method according to claim 2, characterized in that The application power consumption analysis model includes a plurality of mapping relationships, each of the plurality of mapping relationships includes a correspondence between primary physical indication information, a range of physical environment impact coefficients, and secondary physical indication information, wherein different primary physical indication information corresponds to different battery attribute information, and different secondary physical indication information corresponds to different power consumption data sets; The determining of a target power consumption data set by applying a power consumption analysis model based on the current physical environment impact coefficient and the battery attribute information of the electronic device includes: Determining a target physical environment impact coefficient range in which the current physical environment impact coefficient is located from a plurality of physical environment impact coefficient ranges; Determine target primary physical indication information corresponding to the battery attribute information of the electronic device; The application power consumption analysis model is used to determine the secondary physical indication information corresponding to the target physical environment impact coefficient range and the target primary physical indication information from the multiple mapping relationships, and the target power consumption data set is the power consumption data set corresponding to the determined secondary physical indication information.

4. The method according to claim 2 or 3, characterized in that The target operation object sequence includes at least one application, and the at least one application is arranged in sequence according to a possible operation order; The determining the battery life based on the target operation object sequence, the remaining total power and the target power consumption data set includes: Based on the target power consumption data set, respectively determine the power consumption of each application in the target operation object sequence within the unit time under the current device environment; Determine at least one reference application from the target operation object sequence according to the time sequence of operations and the power consumption of each application in the target operation object sequence within the unit time, wherein the total power consumption of the at least one reference application is greater than or equal to the remaining total power, and the difference between the total power consumption of the at least one reference application and the remaining total power is minimal; counting the number of the at least one reference application; The battery life is determined by multiplying the number of the at least one reference application by the unit time.

5. The method according to any one of claims 1 to 4, characterized in that The behavior analysis index information includes the current feature cycle and the current time point; the user behavior analysis model includes a user personalized behavior sequence corresponding to each feature cycle in multiple feature cycles, each feature cycle includes multiple unit time periods, each user personalized behavior sequence includes multiple applications, each application corresponds to a unit time period, and the user personalized behavior sequence corresponding to any cycle feature is used to characterize the applications used by the user in each unit time period in sequence under any feature cycle; The step of determining a target operation object sequence based on the behavior analysis index information through a user behavior analysis model includes: Obtaining the user personalized behavior sequence corresponding to the current feature period from the user personalized behavior sequences of the multiple feature periods by using the user behavior analysis model; From the user personalized behavior sequence corresponding to the current feature period, the application programs corresponding to each unit time period after the current time point are determined, and the determined application programs constitute the target operation object sequence.

6. The method according to claim 5, characterized in that The method further comprises: Acquire a plurality of application history usage data, each of the plurality of application history usage data being used to characterize a history usage record of an application program, wherein the history usage record of an application program includes a characteristic period in which the application program is used; The plurality of application history usage data are grouped based on the characteristic period to obtain a plurality of groups of application history usage data, wherein one group corresponds to one characteristic period; Based on each set of application history usage data in the multiple sets of application history usage data, a user personalized behavior sequence corresponding to each characteristic period is determined.

7. The method according to claim 6, characterized in that The historical usage record of the application further includes time information when the application is used; The determining, based on each set of application history usage data in the plurality of sets of application history usage data, a user personalized behavior sequence corresponding to each characteristic period includes: For any set of application history usage data among the multiple sets of application history usage data, counting the usage frequency of each application used in each unit time period in the characteristic period corresponding to the any set according to each time information in the any set of application history usage data; Based on the usage frequency of each application used in each unit time period in the feature period corresponding to any group, a user personalized behavior sequence corresponding to one feature period is determined.

8. The method according to claim 7, characterized in that The determining of a user personalized behavior sequence corresponding to a feature period based on the usage frequency of each application used in each unit time period in any group of corresponding feature periods includes: For any one of the unit time periods, if the number of applications with the highest frequency of use in the any one of the unit time periods is one, determining the application with the highest frequency of use as the operation object in the any one of the unit time periods; If there are multiple applications with the highest usage frequency in any one unit time period, the operation object determined in the previous unit time period is determined as the operation object in the any one unit time period.

9. The method according to claim 3, characterized in that The method further comprises: Acquire multiple key data feature sets corresponding to each of the application programs, each of the multiple key data feature sets including application information of an application program, and corresponding battery attribute information, physical environment index value, and power consumption within the unit time when the application program is used; Determining the physical environment impact coefficient corresponding to each key data feature set according to the physical environment indicator value in each key data feature set; Determining, from a plurality of physical environment impact coefficient ranges, a physical environment impact coefficient range in which a physical environment impact coefficient corresponding to each key data feature set is located; Based on the multiple key data feature sets and the range of physical environment impact coefficients corresponding to each key data feature set, counting the power consumption of each application program in a unit time under different device environments; The multiple mapping relationships are established based on the power consumption of each application program within a unit time under different device environments.

10. The method according to any one of claims 1 to 9, characterized in that Before determining the target operation object sequence through the user behavior analysis model based on the behavior analysis index information, the method further includes: Displaying a first interface, wherein the first interface includes a battery life prediction switch; Receiving an operation of turning on the battery life prediction switch; The step of determining a target operation object sequence based on the behavior analysis index information through a user behavior analysis model includes: In response to the start operation, acquiring the behavior analysis index information; Based on the behavior analysis index information, the target operation object sequence is determined through the user behavior analysis model.

11. An electronic device, characterized in that: The electronic device comprises a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the method according to any one of claims 1 to 10 when executing the computer program.

12. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores instructions, which, when executed on a computer, enable the computer to execute the method according to any one of claims 1 to 10.