CN111045507B - List management and control method, device, mobile terminal and storage medium - Google Patents

List management and control method, device, mobile terminal and storage medium Download PDF

Info

Publication number
CN111045507B
CN111045507B CN201911183642.9A CN201911183642A CN111045507B CN 111045507 B CN111045507 B CN 111045507B CN 201911183642 A CN201911183642 A CN 201911183642A CN 111045507 B CN111045507 B CN 111045507B
Authority
CN
China
Prior art keywords
specified
mobile terminal
application
time
doze mode
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN201911183642.9A
Other languages
Chinese (zh)
Other versions
CN111045507A (en
Inventor
侯健
郑志勇
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Realme Chongqing Mobile Communications Co Ltd
Original Assignee
Realme Chongqing Mobile Communications Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Realme Chongqing Mobile Communications Co Ltd filed Critical Realme Chongqing Mobile Communications Co Ltd
Priority to CN201911183642.9A priority Critical patent/CN111045507B/en
Publication of CN111045507A publication Critical patent/CN111045507A/en
Application granted granted Critical
Publication of CN111045507B publication Critical patent/CN111045507B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F1/00Details not covered by groups G06F3/00 - G06F13/00 and G06F21/00
    • G06F1/26Power supply means, e.g. regulation thereof
    • G06F1/32Means for saving power
    • G06F1/3203Power management, i.e. event-based initiation of a power-saving mode
    • G06F1/3234Power saving characterised by the action undertaken
    • G06F1/3287Power saving characterised by the action undertaken by switching off individual functional units in the computer system
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F1/00Details not covered by groups G06F3/00 - G06F13/00 and G06F21/00
    • G06F1/26Power supply means, e.g. regulation thereof
    • G06F1/32Means for saving power
    • G06F1/3203Power management, i.e. event-based initiation of a power-saving mode
    • G06F1/3234Power saving characterised by the action undertaken
    • G06F1/329Power saving characterised by the action undertaken by task scheduling
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44Arrangements for executing specific programs
    • G06F9/4401Bootstrapping
    • G06F9/4418Suspend and resume; Hibernate and awake

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Software Systems (AREA)
  • Computer Hardware Design (AREA)
  • Computing Systems (AREA)
  • Computer Security & Cryptography (AREA)
  • Telephone Function (AREA)

Abstract

The application discloses a method and a device for managing a name list, a mobile terminal and a storage medium, wherein the method for managing the name list is applied to the mobile terminal and comprises the following steps: when the mobile terminal is monitored to enter a Doze mode, acquiring the current time; if the current time meets a specified time condition, acquiring a specified application in a white list corresponding to the Doze mode, wherein the power consumption of the specified application in the Doze mode is greater than the specified power consumption; removing the specified application from the whitelist. The method can reduce the power consumption of the mobile terminal and improve the cruising ability of the mobile terminal.

Description

List management and control method, device, mobile terminal and storage medium
Technical Field
The present application relates to the field of roster management and control technologies, and in particular, to a roster management and control method, an apparatus, a mobile terminal, and a storage medium.
Background
With the rapid development of mobile terminals, the functions of the mobile terminals are increasing, and the power consumption of the mobile terminals is also increasing. Therefore, the current mobile terminal exits the Doze mode, which is a low power consumption mode, and reduces the power consumption of the mobile terminal by suspending the occupation of the processor and network activities, etc. by the application in the background. When the mobile terminal is in the Doze mode, only the applications in the white list are allowed to wake up the mobile terminal, but some of the applications in the white list may cause large power consumption to the mobile terminal.
Disclosure of Invention
In view of the above problems, the present application provides a method, an apparatus, a mobile terminal and a storage medium for managing titles.
In a first aspect, an embodiment of the present application provides a title management method, which is applied to a mobile terminal, and the method includes: when the mobile terminal is monitored to enter a Doze mode, acquiring the current time; if the current time meets a specified time condition, acquiring a specified application in a white list corresponding to the Doze mode, wherein the power consumption of the specified application in the Doze mode is greater than the specified power consumption; removing the specified application from the whitelist.
In a second aspect, an embodiment of the present application provides a single-card control device, which is applied to a mobile terminal, and the device includes: the mobile terminal comprises a first acquisition module, a second acquisition module and an application removal module, wherein the first acquisition module is used for acquiring the current time when the mobile terminal is monitored to enter a Doze mode; the second obtaining module is used for obtaining the specified application in the white list corresponding to the Doze mode if the current time meets the specified time condition, and the power consumption of the specified application is greater than the specified power consumption; the application removal module is configured to remove the specified application from the whitelist.
In a third aspect, an embodiment of the present application provides a mobile terminal, including: one or more processors; a memory; one or more applications, wherein the one or more applications are stored in the memory and configured to be executed by the one or more processors, the one or more programs configured to perform the rosting method provided by the first aspect above.
In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, where a program code is stored in the computer-readable storage medium, and the program code may be called by a processor to execute the roster management and control method provided in the first aspect.
The scheme that this application provided, through when monitoring that mobile terminal enters into the Doze mode, obtain the current moment, if the current moment satisfies the specified condition, obtain the appointed application in the white list that the Doze mode corresponds, the appointed consumption of using under the Doze mode is greater than appointed consumption, then remove appointed application from the white list, thereby make mobile terminal enter into the Doze mode, can forbid the awakening of appointed application to mobile terminal, thereby reduce the appointed consumption that brings under the Doze mode, and then promote mobile terminal's duration.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.
Fig. 1 shows a flowchart of a roster management method according to an embodiment of the application.
Fig. 2 shows a flowchart of a roster management method according to another embodiment of the present application.
Fig. 3 shows a flowchart of a roster management method according to yet another embodiment of the application.
Fig. 4 shows a flowchart of a roster management method according to yet another embodiment of the application.
Fig. 5 shows a schematic interface diagram according to still another embodiment of the present application.
Fig. 6 shows another interface schematic provided by yet another embodiment of the present application.
Fig. 7 shows a block diagram of a roster control apparatus according to an embodiment of the application.
Fig. 8 is a block diagram of a mobile terminal according to an embodiment of the present application, configured to execute a method for controlling a list according to an embodiment of the present application.
Fig. 9 is a storage unit, according to an embodiment of the present application, configured to store or carry program code for implementing a method for managing a list according to an embodiment of the present application.
Detailed Description
In order to make the technical solutions better understood by those skilled in the art, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application.
With the development of mobile terminals, functions that can be realized by the mobile terminals are increasing, for example, the mobile terminals can realize various functions such as photographing, surfing the internet, video chatting, and the like. The increased functions of the mobile terminal also increase power consumption.
In order to save the system power consumption of the mobile terminal, a Doze mode is introduced into the mobile terminal of the Android system (Android). The Doze mode may be referred to as a Doze mode and functions to cause the mobile terminal to enter a Doze mode in which background, services, broadcasts, etc. of the mobile terminal are delayed accordingly.
The main technical principle of the Doze mode is as follows: when the conditions of the Doze mode are met, the mobile terminal enters the Doze mode; after entering the Doze mode, at intervals, entering a maintenance window (maintence window) window period of a short duration (e.g., 30 seconds), and performing system wake-up, network interaction, and the like; after entering the Doze mode, the system wakes up for a longer and longer interval if the Doze mode is not exited. Therefore, the mobile terminal is in the Doze mode, and the power consumption of the mobile terminal can be saved.
Further, when the system of the mobile terminal is in Doze mode, the system and applications outside the white list are limited as follows: no access to the network, the Wake Locks (Wake Locks) being ignored, the timing service (alarmmmanager) being deferred until the next maintenance window response, the System not performing Wireless Fidelity (WIFI) and Positioning (GPS) scanning, the System not allowing the synchronization adapter to run, the System not allowing the JobScheduler process to run. Applications in the white list can continue to use the network and retain part of the wake-up lock, the Job-like process and the synchronization process are delayed, and the conventional timing service is not triggered.
The inventor finds, through long-term research, that some applications consuming more power exist in a white list corresponding to the Doze mode, and the applications may wake up the system frequently, for example, the white list may include common instant messaging applications such as WeChat, and the system may wake up frequently, which results in higher power consumption of the mobile terminal in the Doze mode.
In view of the above problems, the inventor proposes a method and an apparatus for managing and controlling a list, a mobile terminal, and a storage medium provided in the embodiments of the present application, so that when it is monitored that the mobile terminal enters a Doze mode and when a current time meets a specified time condition, a specified application is removed from a white list corresponding to the Doze mode, thereby reducing power consumption of the specified application in the Doze mode. The specific list management and control method is described in detail in the following embodiments.
Referring to fig. 1, fig. 1 is a schematic flowchart illustrating a method for managing a list according to an embodiment of the present application. The list management and control method is used for removing the designated application from the white list corresponding to the Doze mode when the mobile terminal is monitored to enter the Doze mode and the current time meets the designated time condition, so that the power consumption of the designated application in the Doze mode is reduced. In a specific embodiment, the method for managing the shortlist is applied to the shortlist managing apparatus 400 shown in fig. 7 and the mobile terminal 100 (fig. 8) configured with the shortlist managing apparatus 400. The following will describe a specific flow of the embodiment by taking a mobile terminal as an example, and it is understood that the mobile terminal applied in the embodiment may be a smart phone, a tablet computer, a smart watch, and the like, which is not limited herein. As will be described in detail below with respect to the flow shown in fig. 1, the roster management and control method may specifically include the following steps:
step S110: and when the mobile terminal is monitored to enter the Doze mode, acquiring the current time.
In this embodiment of the application, the mobile terminal may monitor the state of the mobile terminal, so as to control whether to enter the Doze mode according to the detected state, and when the mobile terminal monitors that the state meets the condition of entering the Doze mode, the mobile terminal may be controlled to enter the Doze mode, so as to save the power consumption of the mobile terminal.
In some embodiments, the mobile terminal may detect the state of its battery, the state of the screen, the motion state, and the like. The monitoring method can detect whether the battery is in a charging state, whether the screen is in a bright screen state or a dark screen state, whether the mobile terminal is in a static state and the like.
As a mode, the mobile terminal can determine whether the screen is in a bright screen state or in an off screen state by detecting whether the backlight source is opened in the module of the screen, and when the backlight source is opened, the screen is determined to be in the bright screen state, and when the backlight source is closed, the screen is determined to be in the off screen state. As another mode, when the system installed in the mobile terminal is an Android (Android) system, the screen state may be obtained by an isScreenOn method of PowerManager, that is, by obtaining a value of isScreenOn, if the value of isScreenOn is true, the screen of the mobile terminal is in a bright screen state, and if the value of isScreenOn is false, the screen of the mobile terminal is in a dead screen state. As still another way, the mobile terminal may detect the screen brightness, and may determine that the screen is in a bright screen state if the screen brightness is greater than a specified brightness, and determine that the screen is in an off screen state if the screen brightness is less than or equal to the specified brightness.
In some embodiments, the mobile terminal may obtain the state of the power supply through an interface for power management in the system and determine whether the battery is in a charged state. The mobile terminal may determine whether the mobile terminal is in a motion state through data detected by the acceleration sensor and the gyroscope sensor, and if the acceleration detected by the acceleration sensor and the gyroscope sensor is not 0, the mobile terminal may be determined to be in the motion state, and if the acceleration detected by the acceleration sensor and the gyroscope sensor is 0, the mobile terminal may be determined to be in a stationary state.
In some embodiments, the mobile terminal may determine whether the mobile terminal needs to enter the Doze mode according to whether the battery is in a charged state, whether the screen is in a bright or off state, whether the mobile terminal is in a stationary state, and the like. If the screen of the mobile terminal is not in the screen-off state after the screen of the mobile terminal enters the screen-off state from the bright screen state, and the time length of the mobile terminal in the standing state reaches the specified time length, it can be determined that the mobile terminal needs to enter the Doze mode, and the mobile terminal is controlled to enter the Doze mode. Of course, the specific condition for entering into Doze mode may not be limiting.
In this embodiment of the present application, when the mobile terminal enters the Doze mode, the system time may be read to determine the current time. For example, when the mobile terminal is a mobile terminal installed with an android system, the current time may be obtained through a Date _ Format function and the like, which is not limited herein. It can be understood that, when the mobile terminal enters the Doze mode, the current time is obtained, and whether the mobile terminal meets the specified time condition at this time can be determined according to the current time, so that when the specified time condition is met, corresponding applications are removed from the white list corresponding to the Doze mode, and larger power consumption of the applications in the Doze mode is reduced.
Step S120: and if the current time meets the specified time condition, acquiring the specified application in the white list corresponding to the Doze mode, wherein the power consumption of the specified application in the Doze mode is greater than the specified power consumption.
In the embodiment of the application, after the mobile terminal acquires the current time when entering the Doze mode, whether the current time meets a specified time condition or not can be determined. The specified time condition is used as a judgment basis for determining whether the specified application is removed from the white list corresponding to the Doze mode, and if the current time meets the specified time condition, the specified application is determined to be removed from the white list corresponding to the Doze mode; if the current time does not satisfy the specified time condition, it indicates that it is determined that the specified application does not need to be removed from the white list corresponding to the Doze mode.
In some embodiments, the specified time condition may be a time condition for characterizing that the user does not use the mobile terminal at the current time. For example, the specified time condition may be a time period when the user in the historical statistics does not use the mobile phone at the current time, and the like, and is not limited herein.
In some embodiments, if it is determined that the current time meets the specified time condition, the mobile terminal may obtain the specified application in the white list corresponding to the Doze mode. The designated application may be an application that consumes more power than the designated power consumption in the Doze mode. The power consumption may refer to power consumption, power consumption speed, and the like, and is not limited herein. The specific magnitude of the specified power consumption may not be limited, and may be, for example, 0.1mW (milliwatt)/1 hour or the like.
As an implementation manner, the information of the designated application may be stored in the mobile terminal in advance, and when the mobile terminal needs to acquire the designated application in the white list corresponding to the Doze mode, the designated application in the white list may be determined according to the information of the pre-stored designated application.
As another embodiment, the mobile terminal may obtain power consumption statistical data of each application in the white list in the Doze mode, and then determine, according to the power consumption statistical data, an application whose power consumption is greater than the specified power consumption. The power consumption statistical data may be power consumption data in the Doze mode counted by the mobile terminal, or power consumption statistical data applied in the Doze mode in a white list acquired by the mobile terminal from a server, which is not limited herein.
Step S130: removing the specified application from the whitelist.
In the embodiment of the application, after the mobile terminal determines the designated application in the white list, the designated application can be removed from the white list, so that the mobile terminal cannot be frequently awakened by the designated application after entering the Doze mode, and the power consumption of the mobile terminal is reduced.
In some embodiments, when the mobile terminal monitors that the Doze mode exits, the mobile terminal may add the designated application back to the white list, so that the designated application may run normally without being limited by the Doze mode when the mobile terminal subsequently enters the Doze mode but does not satisfy the designated time condition.
According to the method for managing and controlling the name list, when it is monitored that the mobile terminal enters the Doze mode, the current time is obtained, if the current time meets the specified condition, the specified application in the white list corresponding to the Doze mode is obtained, the power consumption of the specified application in the Doze mode is larger than the specified power consumption, and then the specified application is removed from the white list, so that the mobile terminal cannot be frequently awakened by the specified application after entering the Doze mode, the power consumption of the mobile terminal is reduced, and the cruising ability of the mobile terminal is improved.
Referring to fig. 2, fig. 2 is a schematic flowchart illustrating a method for managing a list according to another embodiment of the present application. The method for managing and controlling the list is applied to the mobile terminal, and will be described in detail with respect to the flow shown in fig. 2, where the method for managing and controlling the list may specifically include the following steps:
step S210: historical usage data for the mobile terminal is obtained, the historical usage data including historical usage status for the mobile terminal.
In the embodiment of the present application, the mobile terminal may record historical usage data of the mobile terminal, the historical usage data may include a usage state of the mobile terminal, corresponding time in different usage states, and the like, and specific historical usage data may not be limited. The usage state may include a state in which the mobile terminal is used and a state in which the mobile terminal is not used. As an embodiment, the mobile terminal may determine that the mobile terminal is in a used state or an unused state according to a duration of the screen being in the screen-off state, a motion state of the mobile terminal, and whether the mobile terminal is operated by a target task. Specifically, when the screen-off duration of the mobile terminal exceeds a specified duration (e.g., 2 hours, 5 hours, etc.), the mobile terminal is stationary and no target task is running, it is determined that the mobile terminal is in an unused state, and otherwise, it may be determined that the mobile terminal is in a used state. The target task may be a task that the user still needs to run when the screen is turned off, for example, a download task, a navigation task, a music task, and the like, which is not limited herein.
In some embodiments, the mobile terminal may specifically record each time point when the usage state of the mobile terminal changes, so as to determine a time period during which the mobile terminal is not used, corresponding to the usage habit of the user, according to the historical usage data.
Step S220: and determining a time period in which the mobile terminal is not used as the designated time period according to the historical use data.
In the embodiment of the application, the mobile terminal may determine the time period in which the mobile terminal is in an unused state according to the historical usage data, and use the determined time period as the specified time period. And the specified time period is used for representing that the user does not use the mobile terminal when the mobile terminal is in the specified time period.
In some embodiments, the mobile terminal may count the time periods in which the mobile terminal is not used in each date according to the historical usage data, and screen out the time periods satisfying the screening condition according to the counted time periods in which the mobile terminal is not used in each date.
As an embodiment, if the length of the time period is small, it may indicate that the user does not use the mobile terminal for a short time, and the user still needs the specific application in the white list, for example, if the time period corresponds to a time period less than 1 hour, the user still needs the specific application (e.g., WeChat, etc.) to run. And determining the time period when the user does not use the mobile phone according to the historical use data of a plurality of dates, if the mobile terminal is in the unused state in one time period only on a few dates, and the mobile terminal is in the used state in other most dates, and if the time period is determined to be the designated time period, the time period is not in accordance with the use habit of the user. Thus, the screening conditions may be that the screening conditions may include: the time length corresponding to the time period is greater than the specified time length, the time period occurrence frequency is greater than the specified frequency, and the like. The specific size of the specified time period may not be limited, and the specified time period may be greater than 30 minutes, for example. The specific size of the designated times may not be limited, and the designated times may be determined according to the number of dates in the historical usage data, for example, the number of dates is 30 days, that is, the historical usage data includes usage data for 30 days, and the designated times may be 20 days, so that the determined time period has a representative value, and the usage habit of the user can be better reflected.
In some embodiments, after determining the time period satisfying the screening condition, the mobile terminal may use the time period satisfying the screening condition as a specified time period, and store the specified time period locally.
Step S230: and when the mobile terminal is monitored to enter the Doze mode, acquiring the current time.
In the embodiment of the present application, step S230 may refer to the contents of the above embodiments, and is not described herein again.
Step S240: and judging whether the current time is in a specified time period, wherein the specified time period is a preset time period in which the mobile terminal is not used.
In the embodiment of the application, the mobile terminal can determine whether the current time meets the specified time condition by determining whether the current time is in the specified time period. It can be understood that, since the specified time period is a time period in which the mobile terminal is not used, if the current time is within the time period, it indicates that the user does not use the mobile terminal, and therefore, the specified application is subsequently removed from the white list corresponding to the Doze mode, and the use requirement of the user is not affected; and if the current time is not within the specified time period, the use requirement of the user can be influenced if the specified application is removed from the white list corresponding to the Doze mode.
In some embodiments, the specified time period may be the specified time period determined in step S210 and step S220. In other embodiments, the specified time period may also be a time period set by the user in the setting interface, for example, the mobile terminal may display the setting interface of the specified time period, prompt the user that the specified time period is a time period in which the mobile terminal is not needed to be used, and then set the specified time period according to the detected setting operation.
Step S250: and if the current time is not in the specified time period, determining that the current time does not meet the specified time condition.
In this embodiment of the application, if the current time is not within the specified time period, it indicates that if the specified application is removed from the white list corresponding to the Doze mode, the usage requirement of the user may be affected, so that when the current time is not within the specified time period, it may be determined that the current time does not satisfy the specified time condition, and the specified application is not subsequently removed from the white list.
Step S260: and not executing the designated application in the white list corresponding to the Doze mode.
Step S270: and if the current time is in the specified time period, determining that the current time meets the specified time condition.
In the embodiment of the application, if the current time is in the specified time period, it indicates that the mobile terminal is not used currently, so that it may be determined that the current time meets the specified condition, and then the specified application is removed from the white list.
Step S280: and acquiring a designated application in a white list corresponding to the Doze mode, wherein the power consumption of the designated application in the Doze mode is greater than the designated power consumption.
Step S290: removing the specified application from the whitelist.
In the embodiment of the present application, step S280 and step S290 may refer to the contents of the foregoing embodiments, and are not described herein again.
According to the method for managing and controlling the name list, historical use data of the mobile terminal are obtained, a time period when the mobile terminal is in an unused state is determined as a designated time period according to the historical use data, when it is monitored that the mobile terminal enters a Doze mode, the current time is obtained, whether the current time is in the designated time period is judged, if the current time is in the designated time period, it is determined that the current time meets a designated time condition, designated applications in a white list corresponding to the Doze mode are obtained, and then the designated applications are removed from the white list, so that the designated applications are removed from the white list under the condition that the use requirements of users are not affected, the mobile terminal cannot be frequently awakened by the designated applications after entering the Doze mode, the power consumption of the mobile terminal is reduced, and the cruising ability of the mobile terminal is improved.
Referring to fig. 3, fig. 3 is a schematic flowchart illustrating a roster management method according to another embodiment of the present application. The method for managing and controlling the list is applied to the mobile terminal, and will be described in detail with respect to the flow shown in fig. 3, where the method for managing and controlling the list may specifically include the following steps:
step S310: the method comprises the steps of obtaining a training data set, wherein the training data set comprises a plurality of historical use moments marked with use states of the mobile terminal.
In the embodiment of the present application, a preset model may be trained in advance, so as to be used for determining whether a current time when the mobile terminal enters the Doze mode meets a specified time condition. It should be noted that the training of the preset model may be performed in advance according to the acquired training data set, and it is not necessary to train the model each time when it is required to determine whether the current time meets the specified time condition by using the preset model each time.
In the embodiment of the application, the historical usage data of the mobile terminal can be obtained, and then the training data set is constructed according to the historical usage data. The training data set comprises a plurality of historical use moments marked with the use states of the mobile terminals.
In some embodiments, the historical usage data may include a usage status of the mobile terminal at a plurality of different recorded historical usage times, wherein the usage status of the mobile terminal includes a status that the mobile terminal is used and a status that the mobile terminal is not used. The recorded multiple historical use moments can be labeled with the use state of the mobile terminal, so as to obtain a training data set. In the training data set, the historical use time is an input sample for training, the use state of the labeled mobile terminal is an output sample for training, and each set of training data may include one input sample and one output sample.
Step S320: and inputting the training data set into a neural network, training the neural network to obtain a trained preset model, wherein the preset model can output the probability of the mobile terminal being used at the input moment according to the input moment.
In the embodiment of the application, the training data set can be input to the neural network for training according to the training data set, so that the preset model is obtained. The neural network may be a deep neural network, which is not limited herein.
The training of the initial model from the training data set is explained below.
Historical use moments in a group of data in the training data set serve as input samples of the neural network, and use states of the mobile terminal marked in the group of data can serve as output samples of the neural network. In the neural network, the neurons in the input layer are fully connected with the neurons in the hidden layer, and the neurons in the hidden layer are fully connected with the neurons in the output layer, so that potential features with different granularities can be effectively extracted. And the number of the hidden layers can be multiple, so that the nonlinear relation can be better fitted, and the trained preset model is more accurate. It is understood that the training process for the preset model may be performed by the mobile terminal, or may not be performed by the mobile terminal. When the training process is not completed by the mobile terminal, the mobile terminal can be used as a direct user or an indirect user, that is, the mobile terminal can send the determined current time when the mobile terminal enters the Doze mode to the server in which the preset model is stored, and obtain the output result of the preset model from the server.
In some embodiments, the trained preset model may determine, according to the input time, a probability that the mobile terminal is used at the time, that is, a probability that the mobile terminal is in a use state. It can be understood that the preset model is trained through a training data set constructed by historical use data, so that the user habits of the mobile terminal in the past can be learned, and therefore, the user can possibly use the mobile terminal at any time. The probability value output by the preset model according to the input time can be understood as the predicted probability that the mobile terminal is used at the time.
In some embodiments, in order to ensure that the preset model can more fully learn the habit of the user and make the output probability more accurate, the training data set may include the same historical use time on a plurality of different dates, and the training data set is labeled with the historical use state, that is, the training of the model is performed through the same historical use time on a plurality of different dates labeled with the historical use state, so that the preset model can more fully learn the use habit of the user.
In some embodiments, the trained preset model may be stored locally at the mobile terminal, or the trained preset model may be stored in a server in communication connection with the mobile terminal, so that the storage space occupied by the mobile terminal may be reduced, and the operating efficiency of the mobile terminal may be improved.
In some embodiments, the preset model may be periodically or aperiodically trained and updated by acquiring new training data.
Step S330: and when the mobile terminal is monitored to enter the Doze mode, acquiring the current time.
In the embodiment of the present application, step S330 may refer to the contents of the foregoing embodiments, and is not described herein again.
Step S340: inputting the current moment into a trained preset model to obtain the probability of the output of the preset model, wherein the preset model is trained in advance to output the probability of the use of the mobile terminal at the input moment according to the input moment.
In the embodiment of the application, when determining whether the current time when entering the Doze mode meets the specified time condition, the mobile terminal may further obtain, through the trained preset model, a probability that the mobile terminal output by the preset model is used at the current time, so as to determine whether the current time meets the specified time condition.
In some embodiments, after obtaining the probability output by the preset model, the mobile terminal may compare the output probability with a specified probability, where the specified probability is used as a criterion for determining whether the mobile terminal will be used by the user at the current time, and if the probability output by the preset model is greater than or equal to the specified probability, the mobile terminal will be likely to be used by the user at the current time, so that subsequently, if the specified application is removed from the white list corresponding to the Doze mode, the usage requirement of the user will be affected; if the probability output by the preset model is smaller than the designated probability, the mobile terminal is probably not used by the user at the current moment, so that the designated application is removed from the white list corresponding to the Doze mode subsequently, and the use requirement of the user is not influenced.
Step S350: and if the probability output by the preset model is greater than or equal to the specified probability, determining that the current moment does not meet the specified time condition.
In this embodiment of the application, if the probability output by the preset model is greater than or equal to the specified probability, it indicates that if the specified application is removed from the white list corresponding to the Doze mode, the usage requirement of the user may be affected, and therefore, when the probability output by the preset model is greater than or equal to the specified probability, it may be determined that the current time does not satisfy the specified time condition, and the specified application is not subsequently removed from the white list.
Step S360: and not executing the designated application in the white list corresponding to the Doze mode.
Step S370: and if the probability output by the preset model is smaller than the specified probability, determining that the current moment meets the specified time condition.
In this embodiment of the application, if the probability output by the preset model is smaller than the specified probability, it indicates that the mobile terminal is not used by the user at the current time at a high probability, and therefore, the specified application is subsequently removed from the white list corresponding to the Doze mode, and the use requirement of the user is not affected, so that it can be determined that the current time meets the specified condition, and the specified application is subsequently removed from the white list.
Step S380: and acquiring a designated application in a white list corresponding to the Doze mode, wherein the power consumption of the designated application is greater than the designated power consumption.
Step S390: removing the specified application from the whitelist.
In the embodiment of the present application, step S380 and step S390 may refer to the contents of the foregoing embodiments, and are not described herein again.
In the embodiment of the application, after the mobile terminal removes the specified application from the white list, the operation on the mobile terminal may be detected, and if it is detected that the mobile terminal is awakened within the specified time period and the operation on the specified application by the user is detected, it indicates that it is wrong to previously determine that the mobile terminal is not used at the current time. Therefore, the preset model can be corrected based on the current time, specifically, the current time can be marked as the state used in the movement, the state is input into the preset model, and the preset model is corrected, so that the probability that the preset model is used at the input time of the output mobile terminal is more accurate, and the use requirement of a user is ensured.
The method for managing and controlling the name list, provided by the embodiment of the application, includes the steps of training to obtain an initial model through historical use time marked with a use state of a mobile terminal, obtaining current time when it is monitored that the mobile terminal enters a Doze mode, inputting the current time into a preset model, obtaining the probability that the mobile terminal output by the preset model is used at the current time, determining that the current time meets a specified time condition if the probability is smaller than a specified probability, obtaining specified applications in a white list corresponding to the Doze mode, and removing the specified applications from the white list, so that the specified applications are removed from the white list under the condition that the use requirements of users are not affected, the mobile terminal cannot be frequently awakened by the specified applications after entering the Doze mode, the power consumption of the mobile terminal is reduced, and the cruising ability of the mobile terminal is improved.
Referring to fig. 4, fig. 4 is a schematic flowchart illustrating a method for managing a list according to another embodiment of the present application. The method for managing and controlling the list is applied to the mobile terminal, and will be described in detail with respect to the flow shown in fig. 4, where the method for managing and controlling the list may specifically include the following steps:
step S410: and determining the application with the power consumption larger than the specified power consumption in the Doze mode in the white list as the specified application according to the power consumption statistical data of each application in the white list in the Doze mode.
In the embodiment of the present application, the mobile terminal may determine the designated application in the white list in advance. Specifically, the mobile terminal may record power consumption statistics data of each application in the white list in the Doze mode. The power consumption statistics may include, but is not limited to, power consumption speed, and the like of each application in the Doze mode.
In some embodiments, the mobile terminal may calculate an average power consumption speed of each application in the Doze mode, and determine whether the average power consumption speed of each application in the Doze mode is greater than a specified power consumption speed, and if the average power consumption speed corresponding to an application is greater than the specified power consumption speed, the power consumption of the application in the Doze mode is greater than the specified power consumption; and if the average power consumption speed corresponding to the application is less than or equal to the specified power consumption speed, the power consumption of the application in the Doze mode is less than or equal to the specified power consumption. Wherein the size of the specified power consumption may not be limiting.
Step S420: storing the application information of the specified application in a removal list.
In this embodiment of the application, after determining that the power consumption in the Doze mode is greater than the specified application with the specified power consumption, the application information of the specified application may be stored in a removal list, so that when the specified application needs to be removed from the white list corresponding to the Doze mode subsequently, the specified application can be removed from the white list according to the stored application information of the specified application.
In some embodiments, before storing the application information of the specific application in the removal list, the mobile terminal may further prompt the user to confirm whether the application information of the specific application is stored in the removal list. Accordingly, step S420 may include: generating prompt information, wherein the prompt information is used for prompting whether the application information of the specified application is stored in a removal list; and when a confirmation instruction is detected, storing the application information of the specified application in a removal list. For example, as shown in fig. 5, after counting and determining the designated applications, the mobile terminal may display a setting interface a1, display the determined designated applications on a setting interface a1, and display text prompt contents to prompt the user whether to add the applications to the removal list. Therefore, the user can determine whether the states of the applications in the white list need to be maintained when the mobile terminal is not used according to the requirements of the user. For example, some users need to keep applications such as WeChat in a white list all the time, so as to obtain information sent by other terminal devices in time, which is convenient for different users' requirements. The application information may be information used for representing an identity of the application, such as a package name and an application identifier of the application, which is not limited herein.
In other embodiments, in addition to the setting manners provided in step S410 and step S420, referring to fig. 6, the mobile terminal may also directly display a removal list setting interface a2, and the user may directly select an application that needs to be removed from the white list when entering the Doze mode, which may also be convenient for different users' needs.
Step S430: and when the mobile terminal is monitored to enter the Doze mode, acquiring the current time.
In the embodiment of the present application, the step S430 may refer to the contents of the foregoing embodiments, and is not described herein again.
Step S440: and if the current moment meets a specified time condition, reading the application information of the specified application from the removal list.
In the embodiment of the application, since the application information of the designated application is pre-stored in the removal list, the application information of the designated application can be directly read from the removal list when the designated application in the white list is acquired.
Step S450: removing application information for the specified application from the whitelist.
In the embodiment of the application, after the application information of the designated application is acquired, when the designated application is removed from the white list, the application information of the designated application can be removed from the white list, so that when the mobile terminal enters the Doze mode, the system is not frequently awakened, and large power consumption is caused.
In some embodiments, when the mobile terminal monitors that the Doze mode exits, the mobile terminal may add the designated application back to the white list, so that the designated application may run normally without being limited by the Doze mode when the mobile terminal subsequently enters the Doze mode but does not satisfy the designated time condition.
In some embodiments, the mobile terminal may further obtain the current time in real time when operating in the Doze mode, continuously determine whether the current time meets a specified time condition, and add the specified application back to the white list when the specified time condition is not met, so as to ensure that the specified application can operate normally without being limited by the Doze mode when the current time does not meet the specified time condition.
Referring to fig. 7, a block diagram of a single control device 400 according to an embodiment of the present disclosure is shown. The apparatus 400 for managing and controlling the list applies the above-mentioned mobile terminal, and the apparatus 400 for managing and controlling the list includes: a first acquisition module 410, a second acquisition module 420, and an application removal module 430. The first obtaining module 410 is configured to obtain a current time when it is monitored that the mobile terminal enters the Doze mode; the second obtaining module 420 is configured to obtain a specified application in a white list corresponding to the Doze mode if the current time meets a specified time condition, where power consumption of the specified application is greater than specified power consumption; the application removal module 430 is configured to remove the specified application from the whitelist.
In some embodiments, the roster management apparatus 400 may further include: a time judgment module, configured to judge whether the current time is within a specified time period before a specified application in a white list corresponding to the Doze mode is acquired if the current time meets a specified time condition, where the specified time period is a preset time period in which the mobile terminal is not used; a first determining module, configured to determine that the current time meets the specified time condition if the current time is within the specified time period; and the second determining module is used for determining that the current time does not meet the specified time condition if the current time is not in the specified time period.
In this embodiment, the apparatus 400 for managing and controlling a list may further include: a usage data obtaining module, configured to obtain historical usage data of the mobile terminal before the current time is determined to be in a specified time period, where the historical usage data includes a historical usage state of the mobile terminal; a time period determining module, configured to determine, according to the historical usage data, a time period in which the mobile terminal is in an unused state as the specified time period.
In some embodiments, the roster management apparatus 400 may further include: a data input module, configured to input a trained preset model to the current time before obtaining a specified application in a white list corresponding to the Doze mode if the current time meets a specified time condition, where the preset model is pre-trained, and output, according to the input time, a probability that the mobile terminal is used at the input time; a third determining module, configured to determine that the current time meets the specified time condition if the probability is smaller than a specified probability; a fourth determining module, configured to determine that the current time does not satisfy the specified time condition if the probability is greater than or equal to the specified probability.
In this embodiment, the apparatus 400 for managing and controlling a list may further include: a training data acquisition module, configured to acquire a training data set before the current time is input into the trained preset model, where the training data set includes a plurality of historical use times labeled with use states of the mobile terminal; and the model training module is used for inputting the training data set into a neural network, training the neural network and obtaining a trained preset model, and the preset model can output the probability of the use of the mobile terminal at the input moment according to the input moment.
In some embodiments, the roster management apparatus 400 may further include: the application determining module is used for determining the application with the power consumption larger than the specified power consumption in the white list in the Doze mode as the specified application according to the power consumption statistical data of each application in the white list in the Doze mode; and the application information storage module is used for storing the application information of the specified application in a removal list.
In this embodiment, the second obtaining module 420 may be specifically configured to: reading the application information of the specified application from the removal list; the application removal module 430 may be specifically configured to: removing application information for the specified application from the whitelist.
In some embodiments, the roster management apparatus 400 may further include: and a prompt module. The prompting module is used for generating prompting information, and the prompting information is used for prompting whether the application information of the specified application is stored in a removal list; the application information storage module may be specifically configured to: and when a confirmation instruction is detected, storing the application information of the specified application in a removal list.
In some embodiments, the roster management apparatus 400 may further include: and applying an adding module. The application adding module is used for adding the specified application to the white list again when the mobile terminal is detected to exit the Doze mode after the specified application is removed from the white list.
It can be clearly understood by those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described apparatuses and modules may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
In the several embodiments provided in the present application, the coupling between the modules may be electrical, mechanical or other type of coupling.
In addition, functional modules in the embodiments of the present application may be integrated into one processing module, or each of the modules may exist alone physically, or two or more modules are integrated into one module. The integrated module can be realized in a hardware mode, and can also be realized in a software functional module mode.
To sum up, the scheme that this application provided, through when monitoring that mobile terminal enters into the Doze mode, obtain the current time, if the current time satisfies the specified condition, obtain the appointed application in the white list that the Doze mode corresponds, the power consumption of appointed application under the Doze mode is greater than the appointed power consumption, then remove the appointed application from the white list, thereby make mobile terminal enter into the Doze mode, can forbid appointed application to mobile terminal's awakening, thereby reduce the power consumption that the appointed application brought under the Doze mode, and then promote mobile terminal's duration.
Referring to fig. 8, a block diagram of a mobile terminal according to an embodiment of the present application is shown. The mobile terminal 100 may be an electronic device capable of running an application, such as a smart phone, a tablet computer, or a smart watch. The mobile terminal 100 in the present application may include one or more of the following components: a processor 110, a memory 120, and one or more applications, wherein the one or more applications may be stored in the memory 120 and configured to be executed by the one or more processors 110, the one or more programs configured to perform a method as described in the aforementioned method embodiments.
Processor 110 may include one or more processing cores. The processor 110 interfaces with various components throughout the mobile terminal 100 using various interfaces and lines, and performs various functions of the mobile terminal 100 and processes data by executing or executing instructions, programs, code sets, or instruction sets stored in the memory 120 and invoking data stored in the memory 120. Alternatively, the processor 110 may be implemented in hardware using at least one of Digital Signal Processing (DSP), Field-Programmable Gate Array (FPGA), and Programmable Logic Array (PLA). The processor 110 may integrate one or more of a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), a modem, and the like. Wherein, the CPU mainly processes an operating system, a user interface, an application program and the like; the GPU is used for rendering and drawing display content; the modem is used to handle wireless communications. It is understood that the modem may not be integrated into the processor 110, but may be implemented by a communication chip.
The Memory 120 may include a Random Access Memory (RAM) or a Read-Only Memory (Read-Only Memory). The memory 120 may be used to store instructions, programs, code sets, or instruction sets. The memory 120 may include a stored program area and a stored data area, wherein the stored program area may store instructions for implementing an operating system, instructions for implementing at least one function (such as a touch function, a sound playing function, an image playing function, etc.), instructions for implementing various method embodiments described below, and the like. The storage data area may also store data created by the terminal 100 in use, such as a phonebook, audio-video data, chat log data, and the like.
Referring to fig. 9, a block diagram of a computer-readable storage medium according to an embodiment of the present application is shown. The computer-readable medium 800 has stored therein a program code that can be called by a processor to execute the method described in the above-described method embodiments.
The computer-readable storage medium 800 may be an electronic memory such as a flash memory, an EEPROM (electrically erasable programmable read only memory), an EPROM, a hard disk, or a ROM. Alternatively, the computer-readable storage medium 800 includes a non-volatile computer-readable storage medium. The computer readable storage medium 800 has storage space for program code 810 to perform any of the method steps of the method described above. The program code can be read from or written to one or more computer program products. The program code 810 may be compressed, for example, in a suitable form.
Finally, it should be noted that: the above embodiments are only used to illustrate the technical solutions of the present application, and not to limit the same; although the present application has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; such modifications and substitutions do not necessarily depart from the spirit and scope of the corresponding technical solutions in the embodiments of the present application.

Claims (10)

1. A business card management method is applied to a mobile terminal, and the method comprises the following steps:
obtaining historical usage data of the mobile terminal, wherein the historical usage data comprises historical usage states of the mobile terminal;
according to the historical use data, counting the time period of the mobile terminal in the unused state in each date;
screening out a time period meeting a screening condition according to the counted time period of the mobile terminal in the unused state in each date, wherein the screening condition comprises that the time length corresponding to the time period is greater than a specified time length and the occurrence frequency of the time period is greater than a specified frequency;
if the screen of the mobile terminal enters the screen-off state from the bright screen state and the time length of the mobile terminal in the standing state reaches the specified time length, determining that the mobile terminal needs to enter the Doze mode, and controlling the mobile terminal to enter the Doze mode;
when the mobile terminal is monitored to enter a Doze mode, acquiring the current time;
judging whether the current time is in a specified time period, wherein the specified time period is a preset time period in which the mobile terminal is not used;
if the current time is in the specified time period, determining that the current time meets the specified time condition;
if the current time is not in the specified time period, determining that the current time does not meet the specified time condition;
if the current time meets a specified time condition, acquiring a specified application in a white list corresponding to the Doze mode, wherein the power consumption of the specified application in the Doze mode is greater than the specified power consumption;
removing the specified application from the whitelist;
when the mobile terminal continues to operate in the Doze mode, acquiring the current time in real time, and continuously determining whether the current time meets the specified time condition;
and when the specified time condition is not met, adding the specified application back to the white list.
2. The method according to claim 1, wherein before the obtaining of the specified application in the white list corresponding to the Doze mode if the current time meets the specified time condition, the method further comprises:
inputting the current moment into a trained preset model to obtain the probability of the output of the preset model, wherein the preset model is trained in advance to output the probability of the use of the mobile terminal at the input moment according to the input moment;
if the probability output by the preset model is smaller than the specified probability, determining that the current moment meets the specified time condition;
and if the probability output by the preset model is greater than or equal to the specified probability, determining that the current moment does not meet the specified time condition.
3. The method of claim 2, wherein prior to said inputting said current time into a trained preset model, said method further comprises:
acquiring a training data set, wherein the training data set comprises a plurality of historical use moments marked with the use states of the mobile terminals;
and inputting the training data set into a neural network, training the neural network to obtain a trained preset model, wherein the preset model can output the probability of the mobile terminal being used at the input moment according to the input moment.
4. The method according to claim 1, wherein before the obtaining of the specified application in the white list corresponding to the Doze mode if the current time meets the specified time condition, the method further comprises:
determining applications in the white list, the power consumption of which is greater than the specified power consumption in the Doze mode, according to the power consumption statistical data of each application in the white list in the Doze mode, and using the applications as the specified applications;
storing the application information of the specified application in a removal list.
5. The method of claim 4, wherein obtaining the specified application in the white list corresponding to the Doze mode comprises:
reading the application information of the specified application from the removal list;
the removing the specified application from the whitelist includes:
removing application information for the specified application from the whitelist.
6. The method of claim 4, wherein prior to said storing application information for the specified application in a removal list, the method further comprises:
generating prompt information, wherein the prompt information is used for prompting whether the application information of the specified application is stored in a removal list;
and when a confirmation instruction is detected, storing the application information of the specified application in a removal list.
7. The method of any of claims 1-6, wherein after said removing said specified application from said whitelist, said method further comprises:
and when the mobile terminal is detected to exit the Doze mode, the designated application is added to the white list again.
8. The title single-card control device is applied to mobile terminals, and comprises: a usage data acquisition module, a time period determination module, a first acquisition module, a time judgment module, a first determination module, a second acquisition module, an application removal module, and an application addition module, wherein,
the usage data acquisition module is used for acquiring historical usage data of the mobile terminal, and the historical usage data comprises historical usage states of the mobile terminal;
the time period determining module is used for counting the time periods of the mobile terminal in the unused state in each date according to the historical use data; screening out a time period meeting a screening condition according to the counted time period of the mobile terminal in the unused state in each date, wherein the screening condition comprises that the time length corresponding to the time period is greater than a specified time length and the occurrence frequency of the time period is greater than a specified frequency;
the first obtaining module is configured to determine that the mobile terminal needs to enter a Doze mode and control the mobile terminal to enter the Doze mode if a duration of the mobile terminal in a stationary state reaches a specified duration after the screen of the mobile terminal enters the Doze state from a bright screen state; when the mobile terminal is monitored to enter a Doze mode, acquiring the current time;
the time judging module is used for judging whether the current time is in a specified time period, wherein the specified time period is a preset time period in which the mobile terminal is not used;
the first determining module is used for determining that the current moment meets the specified time condition if the current moment is in the specified time period;
the second determining module is used for determining that the current moment does not meet the specified time condition if the current moment is not in the specified time period;
the second obtaining module is used for obtaining the specified application in the white list corresponding to the Doze mode if the current time meets the specified time condition, and the power consumption of the specified application is greater than the specified power consumption;
the application removal module is used for removing the specified application from the white list;
the time judgment module is further used for acquiring the current time in real time when the mobile terminal continues to operate in the Doze mode, and continuously determining whether the current time meets the specified time condition;
and the application adding module is used for adding the specified application back to the white list when the specified time condition is not met.
9. A mobile terminal, comprising:
one or more processors;
a memory;
one or more applications, wherein the one or more applications are stored in the memory and configured to be executed by the one or more processors, the one or more programs configured to perform the method of any of claims 1-7.
10. A computer-readable storage medium, having stored thereon program code that can be invoked by a processor to perform the method according to any one of claims 1 to 7.
CN201911183642.9A 2019-11-27 2019-11-27 List management and control method, device, mobile terminal and storage medium Active CN111045507B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201911183642.9A CN111045507B (en) 2019-11-27 2019-11-27 List management and control method, device, mobile terminal and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201911183642.9A CN111045507B (en) 2019-11-27 2019-11-27 List management and control method, device, mobile terminal and storage medium

Publications (2)

Publication Number Publication Date
CN111045507A CN111045507A (en) 2020-04-21
CN111045507B true CN111045507B (en) 2022-04-19

Family

ID=70233800

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201911183642.9A Active CN111045507B (en) 2019-11-27 2019-11-27 List management and control method, device, mobile terminal and storage medium

Country Status (1)

Country Link
CN (1) CN111045507B (en)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113766611B (en) * 2020-06-02 2023-08-11 深圳市万普拉斯科技有限公司 Low-power consumption control optimization method and device, mobile terminal and storage medium
CN116795628B (en) * 2023-05-24 2024-05-14 荣耀终端有限公司 Power consumption processing method of terminal equipment, terminal equipment and readable storage medium

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107885308A (en) * 2016-09-30 2018-04-06 北京小米移动软件有限公司 Electricity saving method and device
CN107885307B (en) * 2016-09-30 2020-09-18 北京小米移动软件有限公司 Equipment control method and device
CN106993102A (en) * 2017-06-01 2017-07-28 深圳天珑无线科技有限公司 Intelligence alignment awakening method, mobile terminal and computer-readable recording medium
CN107450711B (en) * 2017-07-31 2020-08-14 Oppo广东移动通信有限公司 Application processing method and device, storage medium and terminal
CN107632697B (en) * 2017-09-30 2019-10-25 Oppo广东移动通信有限公司 Processing method, device, storage medium and the electronic equipment of application program

Also Published As

Publication number Publication date
CN111045507A (en) 2020-04-21

Similar Documents

Publication Publication Date Title
CN107567083B (en) Method and device for performing power-saving optimization processing
CN107835311B (en) Application management method and device, storage medium and electronic equipment
CN109144232B (en) Process processing method and device, electronic equipment and computer readable storage medium
CN109803359A (en) A kind of method and terminal waking up terminal system
CN108804231B (en) Memory optimization method and device, readable storage medium and mobile terminal
CN111045507B (en) List management and control method, device, mobile terminal and storage medium
CN110032266B (en) Information processing method, information processing device, computer equipment and computer readable storage medium
CN110574355B (en) Alarm clock reminding method and device, storage medium and electronic equipment
CN111050388B (en) Doze mode control method, device, mobile terminal and storage medium
CN107943269A (en) Schedule job control method, device, terminal device and storage medium
CN112148493A (en) Streaming media task management method and device and data server
CN107748697B (en) Application closing method and device, storage medium and electronic equipment
CN113050783B (en) Terminal control method and device, mobile terminal and storage medium
CN113055984B (en) Terminal control method and device, mobile terminal and storage medium
CN107908953A (en) Notifications service control method, device, terminal device and storage medium
CN114416320A (en) Task processing method, device, equipment and storage medium
CN112988030B (en) Terminal control method, device, terminal and storage medium
US20220244985A1 (en) Application management method and device, terminal and readable storage medium
CN111722695B (en) Terminal equipment power consumption optimization method and device
CN107943268A (en) Schedule job control method, device, terminal device and storage medium
CN110046030B (en) Application program processing method and device, electronic equipment and computer readable storage medium
CN113031982A (en) Application program operation prediction method and device and electronic equipment
CN113064660A (en) Device control method, device, electronic device and storage medium
CN112997150A (en) Application program management method and device, storage medium and electronic equipment
CN113985999B (en) Device management method, device, electronic device and storage medium

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant