WO2020052493A1 - 应用的冻结方法及装置，存储介质及电子装置 - Google Patents

应用的冻结方法及装置，存储介质及电子装置 Download PDF

Info

Publication number
WO2020052493A1
WO2020052493A1 PCT/CN2019/104550 CN2019104550W WO2020052493A1 WO 2020052493 A1 WO2020052493 A1 WO 2020052493A1 CN 2019104550 W CN2019104550 W CN 2019104550W WO 2020052493 A1 WO2020052493 A1 WO 2020052493A1
Authority
WO
WIPO (PCT)
Prior art keywords
application
frozen
freezing
power consumption
blacklist
Prior art date
Application number
PCT/CN2019/104550
Other languages
English (en)
French (fr)
Inventor
阚勇
何志斌
Original Assignee
中兴通讯股份有限公司
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 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2020052493A1 publication Critical patent/WO2020052493A1/zh

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements 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/44—Arrangements for executing specific programs
    • G06F9/445—Program loading or initiating
    • G06F9/44594—Unloading
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F1/00—Details not covered by groups G06F3/00 - G06F13/00 and G06F21/00
    • G06F1/26—Power supply means, e.g. regulation thereof
    • G06F1/32—Means for saving power
    • G06F1/3203—Power management, i.e. event-based initiation of a power-saving mode
    • G06F1/3234—Power saving characterised by the action undertaken
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F1/00—Details not covered by groups G06F3/00 - G06F13/00 and G06F21/00
    • G06F1/26—Power supply means, e.g. regulation thereof
    • G06F1/32—Means for saving power
    • G06F1/3203—Power management, i.e. event-based initiation of a power-saving mode
    • G06F1/3234—Power saving characterised by the action undertaken
    • G06F1/325—Power saving in peripheral device
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements 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/44—Arrangements for executing specific programs
    • G06F9/445—Program loading or initiating
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements 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/46—Multiprogramming arrangements
    • G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements 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/46—Multiprogramming arrangements
    • G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
    • G06F9/5005—Allocation of resources, e.g. of the central processing unit [CPU] to service a request
    • G06F9/5027—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management

Definitions

  • the present application relates to the field of communications, and in particular, to an application freezing method and device, a storage medium, and an electronic device.
  • the embodiments of the present application provide a method and device for freezing an application, a storage medium, and an electronic device, so as to at least solve how to freeze management of the application in the related art, so as to effectively save power consumption and extend the battery life.
  • the application is frozen and managed with minimal impact on the user without affecting the user's use and improving the user experience.
  • an application freezing method which includes monitoring power consumption behavior of an application running in the background, and freezing an application that meets abnormal power consumption behavior.
  • the method further includes: when it is monitored that the frozen application meets a thawing condition, thawing the frozen application.
  • the abnormal power consumption behavior includes at least one of the following: the continuous occupation time of the central processing unit CPU by the application exceeds a threshold, the lock time of the application exceeds the threshold, and the memory usage of the application exceeds the threshold.
  • the application continuously applies a positioning time exceeding a threshold, and the application's use time of the sensor exceeds the threshold.
  • the thawing condition includes at least one of the following: the application is switched to the foreground, the terminal where the application is located is in a charging state, the freezing time of the application exceeds a threshold, and the wireless fidelity of the terminal where the application is located The WIFI connection is successful, and the application is in a set download / upgrade time period.
  • the method further includes: determining whether the number of freezing times of the application is greater than a preset number of freezing times; and if the determination result is yes, placing the application on the freezing blacklist.
  • the application is frozen.
  • the application located in the frozen blacklist is switched to the foreground, the application is thawed and removed from the frozen blacklist.
  • the defrosting conditions include at least two of the following: the application is switched to the foreground, the terminal where the application is located is in a charging state, the freezing time of the application exceeds a threshold, and the The wireless fidelity WIFI connection is successful, and the application is in a set download / upgrade time period.
  • resources other than the CPU resources occupied by the application are released first, and then the CPU resources occupied by the application are released.
  • an application freezing device including: a freezing module configured to monitor power consumption behavior of an application running in the background, and freezing an application that meets abnormal power consumption behavior.
  • the freezing device further includes a thawing module configured to thaw the frozen application when it is monitored that the frozen application meets a thawing condition.
  • a thawing module configured to thaw the frozen application when it is monitored that the frozen application meets a thawing condition.
  • the freezing device is further configured to determine whether the number of freezing times of the application is greater than a preset number of freezing times; and if the determination result is yes, placing the application on the freezing blacklist.
  • the freezing module is further configured to freeze the application when it is monitored that the application in the frozen blacklist is switched to run in the background.
  • the unfreezing module is further configured to unfreeze and remove the application from the frozen blacklist when it is monitored that the application located in the frozen blacklist is switched to the foreground.
  • the freezing device is further configured to reduce the threshold in the abnormal power consumption behavior when an application in the frozen blacklist is judged to meet the abnormal power consumption behavior, and / or
  • the defrosting conditions include at least two of the following: the application is switched to the foreground, the terminal where the application is located is in a charging state, and the freezing time of the application exceeds a threshold , The wireless fidelity WIFI connection of the terminal where the application is located is successful, and the application is in a set download / upgrade time period.
  • a storage medium stores a computer program, and the computer program is configured to execute the steps in any one of the foregoing method embodiments when running.
  • an electronic device which includes a memory and a processor.
  • the memory stores a computer program
  • the processor is configured to run the computer program to execute any one of the foregoing. Steps in a method embodiment.
  • one or more applications are frozen or thawed under a condition that a preset condition is satisfied, and the freezing and thawing processes can be performed dynamically alternately. So as to effectively save power. Frozen conditions also met.
  • the freezing technology consistent with the embodiments of the present application is mainly a method based on a smart terminal to limit applications to occupy system resources. It mainly includes prohibiting managed applications from occupying central processing unit (CPU) resources, sensors, global positioning system (Global Positioning System (GPS), and memory) and other peripheral resources to achieve management of One or more applications are dynamically frozen or thawed to achieve the effect of effectively saving power consumption and extending battery life.
  • CPU central processing unit
  • GPS Global Positioning System
  • memory global positioning system
  • the freezing strategy in the related technology can be solved, and at the same time, the problem of interfering with the normal use of the application by the user can be solved, so as to save resources such as power consumption without affecting the user's use and improve the user experience.
  • FIG. 1 is a block diagram of a hardware structure of a mobile terminal of an application freezing method according to an embodiment of the present application
  • FIG. 2 is a flowchart of an application freezing method according to an embodiment of the present application.
  • FIG. 3 is a flowchart of an application freeze management method according to another embodiment of the present application.
  • FIG. 4 is a structural block diagram of an application freezing device according to an embodiment of the present application.
  • FIG. 5 is a structural block diagram of a freezing device according to another embodiment of the present application.
  • FIG. 1 is a block diagram of a hardware structure of a mobile terminal in an application freezing method according to an embodiment of the present application.
  • the mobile terminal 10 may include one or more (only one shown in FIG. 1) a processor 102 (the processor 102 may include, but is not limited to, a processing device such as a microprocessor MCU or a programmable logic device FPGA) ) And a memory 104 for storing data, optionally, the above mobile terminal may further include a transmission device 106 and an input-output device 108 for communication functions.
  • a processor 102 may include, but is not limited to, a processing device such as a microprocessor MCU or a programmable logic device FPGA)
  • a memory 104 for storing data
  • the above mobile terminal may further include a transmission device 106 and an input-output device 108 for communication functions.
  • FIG. 1 is only a schematic, and it does not limit the structure of the above mobile terminal.
  • the mobile terminal 10 may further include more or fewer components than those shown in FIG. 1, or have a different configuration from that shown in FIG. 1.
  • the memory 104 may be configured to store a computer program, for example, a software program and module of application software, such as a computer program corresponding to an application freezing method in the embodiment of the present application.
  • the processor 102 runs the computer program stored in the memory 104, thereby Perform various functional applications and data processing, that is, implement the method described above.
  • the memory 104 may include a high-speed random access memory, and may further include a non-volatile memory, such as one or more magnetic storage devices, a flash memory, or other non-volatile solid-state memory.
  • the memory 104 may include memory remotely set with respect to the processor 102, and these remote memories may be connected to the mobile terminal 10 through a network. Examples of the above network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.
  • the transmission device 106 is configured to receive or transmit data via a network.
  • the above-mentioned network optional examples may include a wireless network provided by a communication provider of the mobile terminal 10.
  • the transmission device 106 includes a network adapter (Network Interface Controller, NIC for short), which can be connected to other network equipment through a base station so as to communicate with the Internet.
  • the transmission device 106 may be a radio frequency (RF) module, which is used to communicate with the Internet in a wireless manner.
  • RF radio frequency
  • FIG. 2 is a flowchart of an application freezing method according to an embodiment of the present application. As shown in FIG. It includes the following steps:
  • Step S202 Monitor the power consumption behavior of the applications running in the background, and freeze the applications that meet the abnormal power consumption behavior.
  • the method further includes: thawing the frozen application when it is monitored that the frozen application meets a thawing condition.
  • FIG. 3 is a flowchart of applying a freeze management method according to another embodiment of the present application.
  • the freeze management method includes the following steps:
  • Step S302 The terminal performs power consumption detection on the running application to determine whether there is an abnormal power consumption application
  • Step S304 Determine whether the abnormal power consumption application satisfies a preset freezing condition according to a result of the abnormal power consumption detection.
  • the application is switched from the foreground running state to the background running state when the terminal receives a user opening another application or receives a switching control instruction.
  • step S306 If the preset freeze condition is met, proceed to the next step S306; if it is not met, continue to keep the application running in the background while continuing to perform power consumption detection in accordance with step S302;
  • Step S306 When the preset freezing condition is satisfied, freeze the application that is abnormally power-consuming and runs in the background.
  • the freezing is to restrict or prohibit the application from occupying system resources, including but not limited to CPU resources, and peripheral resources such as sensors, GPS positioning, or memory.
  • peripheral resources such as sensors, GPS positioning, or memory.
  • a business request of the application is to be restricted or prohibited, for example, to apply for or release a service request such as an alarm, wakelock, GPS positioning, and the like.
  • Step S308 Monitor the event of the frozen application on the terminal.
  • the activity event includes a terminal's control instruction for the frozen application, or a message receiving module of the frozen application.
  • the control instruction for the frozen application may include a user re-opening the frozen application to the foreground through an operation.
  • Step S310 Determine whether the frozen application meets a preset thawing condition according to the activity event, and when the preset thawing condition is satisfied, proceed to S3012 to thawing the application. If the preset defrosting conditions are not met, continue to maintain the frozen state of the application and continue monitoring in step S308;
  • Step S312 Unfreeze the frozen application.
  • the thawing restores the application's occupation of system resources, including but not limited to CPU resources, and peripheral resources such as sensors, GPS positioning, or memory.
  • a service request Business request of the application is restored, for example, a service request such as applying for or releasing an alarm, an alarm, a wakelock, a GPS positioning, or the like.
  • step S302 the abnormal power consumption detection in step S302 is continuously performed.
  • the terminal records the freezing situation of each application, including but not limited to: the number of freezing times, the reason for freezing, the freezing time, and so on.
  • the application that enters the frozen state again meets the conditions of knowing the freezing conditions, it will be thawed again.
  • the abnormal power consumption behavior includes at least one of the following: the continuous CPU usage time of the application exceeds the threshold, the lock time of the application exceeds the threshold, the memory usage of the application exceeds the threshold, and the application continues The application positioning time exceeds the threshold, and the application's use time of the sensor exceeds the threshold.
  • the application For example, for the continuous CPU usage time of an application, assuming that the application occupies more than 10 percent of the CPU for 2 minutes (min), or that the application occupies more than half of the CPU within 10 minutes, etc., the application is considered to The continuous occupation time exceeds the threshold, and the abnormal power consumption behavior is satisfied.
  • the main judgment is the time of the kernel lock or frame lock of the application. If the core lock is held for more than 10 minutes in a row or the accumulated lock is held for more than 10 minutes in 20 minutes, then the lock time of the application is deemed to exceed the threshold and satisfy abnormal power consumption behavior.
  • the memory usage of the application it is mainly to determine whether the memory of the background process has increased, or it can also be judged based on the absolute memory usage and the relatively top applications. Assuming that the application's memory usage has increased from 5% to 25%, or the application has stabilized in the top three applications within 10 minutes, etc., it is considered that the application's memory usage exceeds the threshold and meets abnormal power consumption behavior.
  • an application For another example, for an application to continuously apply for positioning time, it is first necessary to determine whether the application is a navigation application. If it is not a navigation application, but the continuous application for positioning information exceeds the threshold, it is assumed that it exceeds 2 minutes, then the application continuously applies the positioning time to exceed the threshold, which meets the abnormal power consumption behavior.
  • time parameters mentioned in the above examples are all listed, not exhaustive. At any time based on the idea of this embodiment, the parameters are only within the protection scope of this embodiment. The user can adjust the above-mentioned time and parameters in real time according to the hardware and software status of the actual terminal, which is not described in detail here.
  • the thawing condition includes at least one of the following: the application is switched to the foreground, the terminal where the application is located is in a charging state, the freezing time of the application exceeds a threshold, and the wireless fidelity of the terminal where the application is located (WireLess Fidelity, WIFI for short) The connection is successful, and the application is in a set download / upgrade time period.
  • the application is placed on the frozen blacklist.
  • the application is frozen.
  • the application located in the frozen blacklist is switched to the foreground, the application is thawed and removed from the frozen blacklist.
  • the applications in the frozen blacklist will directly enter the frozen state without judgment.
  • the application in order to prevent delays in using the application and to prevent repeated power consumption problems of the application, the application can be thawed only when the application in the frozen blacklist is switched to the foreground.
  • the freezing time of the application exceeds a threshold, and the WIFI connection of the terminal where the application is located is not successful, the application cannot be thawed.
  • the defrosting conditions include at least two of the following: the application is switched to the foreground, the terminal where the application is located is in a charging state, the freezing time of the application exceeds a threshold, and the The WIFI connection is successful, and the application is in a set download / upgrade time period.
  • a frozen whitelist can also be set. For an application that has not been frozen for the first time or within a period of time, if it enters a frozen state, the threshold value in the abnormal power consumption behavior may be reduced and adjusted, and the thawing conditions may be relaxed. In this way, the freezing and thawing of the application can be managed more intelligently, so that the power of the terminal can be wasted less.
  • resources other than the CPU resources occupied by the application are released first, and then the CPU resources occupied by the application are released.
  • release other resources including alarm, Binder call, positioning request, broadcast monitoring, and so on. For example: if it applies for alarm, it will put the alarm into the temporary list, or discard the alarm request. If it communicates with the IPC process through Binder when it freezes, it waits for the Binder call to complete.
  • the managed one or more applications can be dynamically frozen or thawed to achieve effective savings.
  • the CPU resources are released and the processes that need to be frozen, including all child threads of this process, are released. Write the freeze flag in Cgroup. After the process enters the FROZEN state, the task is frozen. Does not participate in CPU scheduling.
  • the process of judging applications with high power consumption repeatedly can adjust the number of times of continuous monitoring, the number of times of monitoring in a period of time, and the like.
  • the system finds that the application has repeatedly existed the power consumption behavior of the application at the edge of the abnormal power consumption behavior. For example, the application's continuous use of the CPU is close to the threshold of the application's continuous use of the CPU. For another example, if the application continuous application positioning time is close to the threshold of applying the continuous application positioning time. Although the application has not entered the frozen state, due to multiple occurrences on the edge of abnormal power consumption behavior, the power consumption is also very large. Therefore, if the number of times an application reaches the edge of abnormal power consumption behavior meets a certain threshold within a period of time, the application will also be frozen. For example, suppose that the application corresponding to the abnormal power consumption behavior has a threshold of 20% of the memory usage. If an application has 5 times in 20 minutes, the memory usage of the application reaches 18%, then the application is frozen.
  • an application freezing device is also provided.
  • the device is used to implement the foregoing embodiments and optional implementation manners, and the descriptions will not be repeated.
  • the term "module” may implement a combination of software and / or hardware for a predetermined function.
  • the devices described in the following embodiments are preferably implemented in software, implementation in hardware, or a combination of software and hardware is also possible and conceived.
  • FIG. 4 is a structural block diagram of an application freezing device according to an embodiment of the present application. As shown in FIG. 4, the device includes a freezing module 42.
  • the freezing module 42 is configured to monitor the power consumption behavior of applications running in the background, and freeze the applications that meet the abnormal power consumption behavior.
  • FIG. 5 is a structural block diagram of another application freezing device according to an embodiment of the present application. As shown in FIG. 5, in addition to the modules included in FIG. 4, the freezing device 52 includes a thawing module 52 and a monitoring module 54.
  • the defrost module 52 is configured to defrost the frozen application when it is monitored that the frozen application meets a defrost condition.
  • the monitoring module 54 is configured to monitor a power consumption behavior of an application running in the background and monitor whether the frozen application meets a thawing condition.
  • the freezing device is further configured to determine whether the number of freezing times of the application is greater than a preset number of freezing times; and if the determination result is yes, placing the application on the freezing blacklist.
  • the freezing module 42 is further configured to freeze the application when it is monitored that the application in the frozen blacklist is switched to run in the background.
  • the thawing module 52 is further configured to, when it is monitored that the application in the frozen blacklist is switched to the foreground, unfreeze the application and remove it from the frozen blacklist.
  • the freezing device is further configured to reduce the threshold in the abnormal power consumption behavior when an application in the frozen blacklist is judged to meet the abnormal power consumption behavior, and / or
  • the defrosting conditions include at least two of the following: the application is switched to the foreground, the terminal where the application is located is in a charging state, and the freezing time of the application exceeds a threshold , The WIFI connection of the terminal where the application is located is successful, and the application is in a set download / upgrade time period.
  • the above modules can be implemented by software or hardware. For the latter, they can be implemented in the following ways, but not limited to the above: the above modules are located in the same processor; or the above modules are combined in any combination The forms are located in different processors.
  • An embodiment of the present application further provides a storage medium, in which a computer program is stored, wherein the computer program is configured to execute the steps in any one of the foregoing method embodiments when running.
  • the foregoing storage medium may be configured to store a computer program for performing the following steps:
  • the foregoing storage medium may include, but is not limited to, a U disk, a read-only memory (ROM), a random access memory (Random Access Memory, RAM), A variety of media that can store computer programs, such as mobile hard disks, magnetic disks, or optical disks.
  • ROM read-only memory
  • RAM Random Access Memory
  • An embodiment of the present application further provides an electronic device including a memory and a processor.
  • the memory stores a computer program
  • the processor is configured to run the computer program to perform the steps in any one of the foregoing method embodiments.
  • the electronic device may further include a transmission device and an input-output device, wherein the transmission device is connected to the processor, and the input-output device is connected to the processor.
  • the foregoing processor may be configured to execute the following steps by a computer program:
  • modules or steps of the present application may be implemented by a general-purpose computing device, and they may be concentrated on a single computing device or distributed in a network composed of multiple computing devices.
  • they may be implemented with program code executable by a computing device, so that they may be stored in a storage device and executed by the computing device, and in some cases, may be in a different order than here
  • the steps shown or described are performed either by making them into individual integrated circuit modules or by making multiple modules or steps into a single integrated circuit module. As such, this application is not limited to any particular combination of hardware and software.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Software Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Telephone Function (AREA)

Abstract

本申请实施例提供了一种应用的冻结方法及装置，存储介质及电子设备。可选地，该应用的冻结方法包括：监控在后台运行的应用的耗电行为，并对满足异常耗电行为的应用进行冻结。通过本申请实施例，解决了相关技术中存在的冻结策略十分复杂，同时干扰用户正常使用应用的问题，进而达到了既能节约电量等资源，又不影响用户使用，提高用户体验的效果。

Description

应用的冻结方法及装置,存储介质及电子装置 技术领域
本申请涉及通信领域，具体而言，涉及一种应用的冻结方法及装置，存储介质及电子设备。
背景技术
随着智能终端技术的发展以及在人们的生活和工作中充当着越来越重要的角色，在终端上所安装的应用越来越多，应用的功能也越来越丰富和强大，以满足用户在生活和工作中的各种应用需求。
但是，随着终端支持应用的多样化和功能的强大，在终端使用过程中，往往会发现存在以下情况：终端上安装的应用越多，即使某些应用没有使用，也能感觉到终端的电池消耗越来越快，内存越来越少。这是因为有些应用即使没有使用，这些应用也会在后台频繁的占用CPU等系统资源，导致终端的耗电量较大；终端电池能力、内存等硬件资源在丰富多彩的应用面前就显得捉襟见肘，从而影响用户体验。
发明内容
本申请实施例提供了一种应用的冻结方法及装置，存储介质及电子设备，以至少解决相关技术中如何对应用进行冻结管理、以达到有效节省功耗、延长电池续航时间的效果。同时，在对用户影响最小的情况下对应用进行冻结管理，又不影响用户使用、提高用户体验。
根据本申请的一个实施例，提供了一种应用的冻结方法，包括：监控在后台运行的应用的耗电行为，并对满足异常耗电行为的应用进行冻结。
可选地，在所述应用进行冻结后，还包括：在监控到所述冻结的应用满足解冻条件时，对冻结的所述应用进行解冻。
可选地，所述异常耗电行为至少包括以下之一：所述应用对中央处理 器CPU的持续占用时间超过阈值，所述应用的持锁时间超过阈值，所述应用对内存占用量超过阈值，所述应用连续申请定位时间超过阈值，所述应用对传感器使用时间超过阈值。
可选地，所述解冻条件至少包括以下之一：所述应用切换至前台，所述应用所在的终端处于充电状态，所述应用的冻结时间超过阈值，所述应用所在的终端的无线保真WIFI连接成功，所述应用处于设定的下载/升级时间段。
可选地，所述方法还包括：判断所述应用的冻结次数是否大于预设的冻结次数；在判断结果为是的情况下，将所述应用放入冻结黑名单。
可选地，当监控到位于所述冻结黑名单中的应用切换至后台运行时，冻结所述应用。
可选地，当监控到位于所述冻结黑名单中的所述应用切换至前台时，将所述应用解冻并从所述冻结黑名单中移除。
可选地，当对位于所述冻结黑名单中的应用进行满足异常耗电行为判断时，减小所述异常耗电行为中的所述阈值，和/或当对位于所述冻结黑名单中的应用进行满足解冻条件判断时，解冻条件包括以下至少之二：所述应用切换至前台，所述应用所在的终端处于充电状态，所述应用的冻结时间超过阈值，所述应用所在的终端的无线保真WIFI连接成功，所述应用处于设定的下载/升级时间段。
可选地，当对所述应用进行冻结时，先释放所述应用占有的除CPU资源之外的其它资源，然后释放所述应用占有的CPU资源。
根据本申请的另一个实施例，提供了一种应用的冻结装置，包括：冻结模块，设置为监控在后台运行的应用的耗电行为，并对满足异常耗电行为的应用进行冻结。
可选地，所述冻结装置还包括：解冻模块，设置为在监控到所述冻结的应用满足解冻条件时，对冻结的所述应用进行解冻。
可选地，所述冻结装置还设置为，判断所述应用的冻结次数是否大于 预设的冻结次数；在判断结果为是的情况下，将所述应用放入冻结黑名单。
可选地，所述冻结模块还设置为，当监控到位于所述冻结黑名单中的应用切换至后台运行时，冻结所述应用。
可选地，所述解冻模块还设置为，当监控到位于所述冻结黑名单中的所述应用切换至前台时，将所述应用解冻并从所述冻结黑名单中移除。
可选地，所述冻结装置还设置为，当对位于所述冻结黑名单中的应用进行满足异常耗电行为判断时，减小所述异常耗电行为中的所述阈值，和/或当对位于所述冻结黑名单中的应用进行满足解冻条件判断时，解冻条件包括以下至少之二：所述应用切换至前台，所述应用所在的终端处于充电状态，所述应用的冻结时间超过阈值，所述应用所在的终端的无线保真WIFI连接成功，所述应用处于设定的下载/升级时间段。
根据本申请的又一个实施例，还提供了一种存储介质，所述存储介质中存储有计算机程序，其中，所述计算机程序被设置为运行时执行上述任一项方法实施例中的步骤。
根据本申请的又一个实施例，还提供了一种电子装置，包括存储器和处理器，所述存储器中存储有计算机程序，所述处理器被设置为运行所述计算机程序以执行上述任一项方法实施例中的步骤。
通过本申请实施例，在满足预设条件的情况下，对一个或多个应用进行冻结或解冻，且该冻结、解冻过程可以交替动态进行。从而有效的节省功耗。同时满足的冻结条件。
同时，符合本申请实施例的冻结技术主要是基于智能终端的一种限制应用占用系统资源的方法。它主要包括通过禁止被管理应用占用中央处理器(Central Processing Unit，简称为CPU)资源、传感器Sensor、全球定位系统(Global Positioning System，简称为GPS)、内存等外设资源，达到对被管理的一个或多个应用进行动态地冻结或者解冻，以达到有效节省功耗、延长电池续航时间的效果。
由于通过在后台监控应用的耗电行为，并根据耗电行为进行冻结，而 无需复杂的冻结策略。因此，可以解决相关技术中存在的冻结策略十分复杂，同时干扰用户正常使用应用的问题，达到既能节约电量等资源，又不影响用户使用，提高用户体验的效果。
附图说明
此处所说明的附图用来提供对本申请的进一步理解，构成本申请的一部分，本申请的示意性实施例及其说明用于解释本申请，并不构成对本申请的不当限定。在附图中：
图1是本申请实施例的一种应用的冻结方法的移动终端的硬件结构框图；
图2是根据本申请实施例的一种应用的冻结方法的流程图；
图3是根据本申请另一实施例的应用冻结管理方法的流程图；
图4是根据本申请实施例的一种应用的冻结装置的结构框图；
图5是根据本申请实施例的另一种应用的冻结装置的结构框图。
具体实施方式
下文中将参考附图并结合实施例来详细说明本申请。需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互组合。
需要说明的是，本申请的说明书和权利要求书及上述附图中的术语“第一”、“第二”等是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。
实施例1
本申请实施例一所提供的方法实施例可以在移动终端、计算机终端或者类似的运算装置中执行。以运行在移动终端上为例，图1是本申请实施例的一种应用的冻结方法的移动终端的硬件结构框图。如图1所示，移动终端10可以包括一个或多个(图1中仅示出一个)处理器102(处理器 102可以包括但不限于微处理器MCU或可编程逻辑器件FPGA等的处理装置)和用于存储数据的存储器104，可选地，上述移动终端还可以包括用于通信功能的传输设备106以及输入输出设备108。本领域普通技术人员可以理解，图1所示的结构仅为示意，其并不对上述移动终端的结构造成限定。例如，移动终端10还可包括比图1中所示更多或者更少的组件，或者具有与图1所示不同的配置。
存储器104可设置为存储计算机程序，例如，应用软件的软件程序以及模块，如本申请实施例中的应用的冻结方法对应的计算机程序，处理器102通过运行存储在存储器104内的计算机程序，从而执行各种功能应用以及数据处理，即实现上述的方法。存储器104可包括高速随机存储器，还可包括非易失性存储器，如一个或者多个磁性存储装置、闪存、或者其他非易失性固态存储器。在一些实例中，存储器104可包括相对于处理器102远程设置的存储器，这些远程存储器可以通过网络连接至移动终端10。上述网络的实例包括但不限于互联网、企业内部网、局域网、移动通信网及其组合。
传输装置106设置为经由一个网络接收或者发送数据。上述的网络可选实例可包括移动终端10的通信供应商提供的无线网络。在一个实例中，传输装置106包括一个网络适配器(Network Interface Controller，简称为NIC)，其可通过基站与其他网络设备相连从而可与互联网进行通讯。在一个实例中，传输装置106可以为射频(Radio Frequency，简称为RF)模块，其用于通过无线方式与互联网进行通讯。
在本实施例中提供了一种运行于上述移动终端或网络架构的应用的冻结方法，图2是根据本申请实施例的一种应用的冻结方法的流程图，如图2所示，该流程包括如下步骤：
步骤S202，监控在后台运行的应用的耗电行为，并对满足异常耗电行为的应用进行冻结。
可选地，在所述应用进行冻结后，还包括：在监控到所述冻结的应用 满足解冻条件时，对冻结的所述应用进行解冻。
可选地，图3是根据本申请另一实施例的应用冻结管理方法的流程图，如图3所示，该冻结管理方法包括以下步骤：
步骤S302：终端对处于运行状态下的应用进行耗电检测，确定是否有异常耗电的应用；
步骤S304：根据异常耗电检测的结果，判断该异常耗电的应用是否满足预设的冻结条件。可选的，该应用是终端在接收到用户打开另一应用时、或者接收到切换控制指令时，从前台运行状态被切换到后台运行状态。
若满足预设冻结条件，则进行下一步骤S306；若不满足则继续保持该应用在后台运行，同时继续按照步骤S302进行耗电检测；
步骤S306：在满足预设冻结条件时，将所述异常耗电、且在后台运行的应用进行冻结。所述冻结是要限制或者禁止所述应用对系统资源的占用，包括但不限于CPU资源、以及传感器Sensor、GPS定位、或内存等外设资源。在针对外设资源的可选的应用实施例中，是要限制或禁止所述应用的业务请求(Business request),例如，申请或者释放闹钟Alarm、唤醒锁wakelock、GPS定位等业务请求。
步骤S308：监测终端上针对被冻结应用的活动事件。可选的，所述活动事件包括终端针对被冻结应用的控制指令、或者该被冻结应用的消息接收模块。例如，对被冻结应用的控制指令可以包括用户通过操作将被冻结应用重新打开到前台。
步骤S310：根据所述活动事件，判断被冻结的应用是否满足预设解冻条件，在满足预设解冻条件时进行到S3012对该应用进行解冻。若不满足预设解冻条件，则继续保持该应用的冻结状态，并继续进行步骤S308的监测；
步骤S312：对冻结应用进行解冻。所述解冻即恢复所述应用对系统资源的占用，包括但不限于CPU资源、以及传感器Sensor、GPS定位、或内存等外设资源。在可选的应用实施例中，恢复所述应用的业务请求 Business request,例如，申请或者释放闹钟Alarm、唤醒锁wakelock、GPS定位等业务请求。
最后，对于解冻应用持续进行步骤S302的异常耗电检测。
对于解冻后的应用而言，如果该应用在后台运行时又满足了异常耗电行为话，那么该解冻后的应用就会再次进行冻结。同时对于该应用，终端会对每一次应用的冻结情况进行记录，包括但不限于：冻结次数，冻结原因，冻结时间等等。同时，如果再次进入冻结状态的应用满足了解冻条件的情况下，则再次解冻。
可选地，异常耗电行为至少包括以下之一：所述应用对CPU的持续占用时间超过阈值，所述应用的持锁时间超过阈值，所述应用对内存占用量超过阈值，所述应用连续申请定位时间超过阈值，所述应用对传感器使用时间超过阈值。
例如，对于应用对CPU的持续占用时间而言，假设连续2分钟(min)应用占用CPU达到百分之10以上，或者10min内应用占用CPU的时间超过一半等等，那么视为应用对CPU的持续占用时间超过阈值，满足异常耗电行为。
又如，对于应用的持锁时间而言，主要判断的是应用的持内核锁或框架锁的时间。假如持内核锁的时间连续超过10min或者在20min内累计持锁超过10min的话，那么视为应用的持锁时间超过阈值，满足异常耗电行为。
再如，对所述应用对内存占用量而言，主要是判断在后台进程的内存是否有增加，也可以基于绝对内存占用量、相对占用前几名的应用进行判断。假设应用的内存占用量从5％上升到25％，或者占用内存在10min内稳定在前三名的应用等等，则视为应用对内存占用量超过阈值，满足异常耗电行为。
又如，对应用连续申请定位时间而言，首先需要判断应用是否是导航类的应用。如果不是导航类应用，但连续申请定位信息超过阈值的话，假 设超过2min的话，那么应用连续申请定位时间超过阈值，满足异常耗电行为。
最后，对于应用对传感器使用时间而言，主要是持续申请各类Sensor不释放。假设接近、霍尔等超过5min不释放，认为是传感器使用时间超过阈值，满足异常耗电行为。
需要说明的是，上述举例中所提及的时间，参数均是列举，而非穷举。任何基于本实施例思路的时间，参数仅在本实施例的保护范围之内。用户可以根据实际终端的硬件、软件状态对上述时间、参数进行实时调整，在此并不做过多赘述。
可选地，所述解冻条件至少包括以下之一：所述应用切换至前台，所述应用所在的终端处于充电状态，所述应用的冻结时间超过阈值，所述应用所在的终端的无线保真(WireLess Fidelity，简称为WIFI)连接成功，所述应用处于设定的下载/升级时间段。
可选地，判断所述应用的冻结次数是否大于预设的冻结次数；在判断结果为是的情况下，将所述应用放入冻结黑名单。
例如，如果应用冻结的次数达到了3次，则将该应用放入到冻结黑名单当中。
可选地，当监控到位于所述冻结黑名单中的应用切换至后台运行时，冻结所述应用。
可选地，当监控到位于所述冻结黑名单中的所述应用切换至前台时，将所述应用解冻并从所述冻结黑名单中移除。
具体而言，考虑到位于冻结黑名单中的应用存在异常耗电行为的反复性，因此，对于冻结黑名单的应用会直接进入到冻结状态，而无需进行判断。同时，一方面为了能够不耽误使用应用，同时防止反复存在异常耗电行为的应用的耗电问题，因此，只有在位于所述冻结黑名单中的所述应用切换至前台时，才能够解冻。而其他的解冻条件，例如，所述应用的冻结时间超过阈值，所述应用所在的终端的WIFI连接成功等，则不能够将应 用进行解冻。
需要说明的是，虽然对于切换到前台的位于冻结黑名单中的应用能够从冻结黑名单中移除，但是后续如果该应用切换至后台运行的话，那么仍然存在潜在的反复进入冻结状态的可能性。因此，对于切换到后台的曾经位于冻结黑名单的应用而言，则可以将其设置在潜在冻结黑名单中。一旦该应用又一次进入到冻结状态，则将该应用放入到冻结黑名单当中。
可选地，当对位于所述冻结黑名单中的应用进行满足异常耗电行为判断时，减小所述异常耗电行为中的所述阈值，和/或当对位于所述冻结黑名单中的应用进行满足解冻条件判断时，解冻条件包括以下至少之二：所述应用切换至前台，所述应用所在的终端处于充电状态，所述应用的冻结时间超过阈值，所述应用所在的终端的WIFI连接成功，所述应用处于设定的下载/升级时间段。
具体而言，通过对异常耗电行为中的所述阈值的扩大调整，以及缩紧解冻条件，也可以对进入冻结黑名单的应用进行有效的控制，从而能够防止反复存在异常耗电行为的应用的耗电问题。
此外，需要说明的是，在本实施例中，还能够设置冻结白名单。对于首次或者在一个时间段内没有冻结过的应用，如果进入冻结状态，则可以将异常耗电行为中的所述阈值的缩小调整，同时放宽解冻条件。这样，可以更加智能地管理应用的冻结和解冻，从而可以更少地浪费终端的电量。
可选地，当对所述应用进行冻结时，先释放所述应用占有的除CPU资源之外的其它资源，然后释放所述应用占有的CPU资源。
具体而言，释放其他资源，包括alarm、Binder调用、定位请求、广播监听等等。例如：它有申请alarm，则会对alarm放入临时列表，或者丢弃alarm请求。如果在冻结的时候它通过Binder进行IPC进程通信，则等待Binder调用完成。
通过上述先释放所述应用占有的除CPU资源之外的其它资源，然后释放所述应用占有的CPU资源，能够达到对被管理的一个或多个应用进 行动态地冻结或者解冻，以达到有效节省功耗、延长电池续航时间的效果
具体而言，释放CPU资源，把需要冻结的进程、包括此进程所有的子线程。在Cgroup中写入写freeze标记。进程进入FROZEN状态后，任务就处于冻结状态。不会参与CPU调度。
此外，对反复有高耗电的应用的判断的处理，可以调整连续被监测到的次数、一段时间内被监测到的次数等等。
可选地，在监控在后台运行的应用的耗电行为后，系统发现应用曾经多次存在应用的耗电行为在异常耗电行为的边缘。例如，应用对CPU的持续占用时间接近应用对CPU的持续占用时间的阈值。又如，应用连续申请定位时间濒临应用连续申请定位时间的阈值的话。虽然应用没有进入到冻结状态，但是由于多次存在位于异常耗电行为的边缘，耗电量也是十分大的。因此，如果在一个时间段内，应用达到异常耗电行为的边缘的次数满足一定的阈值，则该应用也将被冻结。举例来说，假设异常耗电行为对应的应用对内存占用量阈值为20％。如果某一个应用，在20min内，曾经存在5次在应用对内存占用量达到18％，则将该应用进行冻结。
通过上述步骤，解决了相关技术中存在的冻结策略十分复杂，同时干扰用户正常使用应用的问题，达到既能节约电量等资源，又不影响用户使用，提高用户体验的效果。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到根据上述实施例的方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本申请实施例的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端设备(可以是手机，计算机，服务器，或者网络设备等)执行本申请各个实施例所述的方法。
实施例2
在本实施例中还提供了一种应用的冻结装置，该装置用于实现上述实施例及可选实施方式，已经进行过说明的不再赘述。如以下所使用的，术语“模块”可以实现预定功能的软件和/或硬件的组合。尽管以下实施例所描述的装置较佳地以软件来实现，但是硬件，或者软件和硬件的组合的实现也是可能并被构想的。
图4是根据本申请实施例的一种应用的冻结装置的结构框图，如图4所示，该装置包括:冻结模块42。
冻结模块42，设置为监控在后台运行的应用的耗电行为，并对满足异常耗电行为的应用进行冻结。
图5是根据本申请实施例的另一种应用的冻结装置的结构框图，如图5所示，除图4中所包括的模块外，还包括：解冻模块52，监控模块54。
解冻模块52，设置为在监控到所述冻结的应用满足解冻条件时，对冻结的所述应用进行解冻。
监控模块54，设置为监控在后台运行的应用的耗电行为以及监控所述冻结的应用是否满足解冻条件。
可选地，所述冻结装置还设置为，判断所述应用的冻结次数是否大于预设的冻结次数；在判断结果为是的情况下，将所述应用放入冻结黑名单。
可选地，所述冻结模块42还设置为，当监控到位于所述冻结黑名单中的应用切换至后台运行时，冻结所述应用。
可选地，所述解冻模块52还设置为，当监控到位于所述冻结黑名单中的所述应用切换至前台时，将所述应用解冻并从所述冻结黑名单中移除。
可选地，所述冻结装置还设置为，当对位于所述冻结黑名单中的应用进行满足异常耗电行为判断时，减小所述异常耗电行为中的所述阈值，和/或当对位于所述冻结黑名单中的应用进行满足解冻条件判断时，解冻条件包括以下至少之二：所述应用切换至前台，所述应用所在的终端处于充电状态，所述应用的冻结时间超过阈值，所述应用所在的终端的WIFI连接成功，所述应用处于设定的下载/升级时间段。
需要说明的是，上述各个模块是可以通过软件或硬件来实现的，对于后者，可以通过以下方式实现，但不限于此：上述模块均位于同一处理器中；或者，上述各个模块以任意组合的形式分别位于不同的处理器中。
实施例3
本申请的实施例还提供了一种存储介质，该存储介质中存储有计算机程序，其中，该计算机程序被设置为运行时执行上述任一项方法实施例中的步骤。
可选地，在本实施例中，上述存储介质可以被设置为存储用于执行以下步骤的计算机程序：
S1，监控在后台运行的应用的耗电行为，并对满足异常耗电行为的应用进行冻结。
可选地，在本实施例中，上述存储介质可以包括但不限于：U盘、只读存储器(Read-Only Memory，简称为ROM)、随机存取存储器(Random Access Memory，简称为RAM)、移动硬盘、磁碟或者光盘等各种可以存储计算机程序的介质。
本申请的实施例还提供了一种电子装置，包括存储器和处理器，该存储器中存储有计算机程序，该处理器被设置为运行计算机程序以执行上述任一项方法实施例中的步骤。
可选地，上述电子装置还可以包括传输设备以及输入输出设备，其中，该传输设备和上述处理器连接，该输入输出设备和上述处理器连接。
可选地，在本实施例中，上述处理器可以被设置为通过计算机程序执行以下步骤：
S1，监控在后台运行的应用的耗电行为，并对满足异常耗电行为的应用进行冻结。
可选地，本实施例中的可选示例可以参考上述实施例及可选实施方式中所描述的示例，本实施例在此不再赘述。
显然，本领域的技术人员应该明白，上述的本申请的各模块或各步骤可以用通用的计算装置来实现，它们可以集中在单个的计算装置上，或者分布在多个计算装置所组成的网络上，可选地，它们可以用计算装置可执行的程序代码来实现，从而，可以将它们存储在存储装置中由计算装置来执行，并且在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤，或者将它们分别制作成各个集成电路模块，或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。这样，本申请不限制于任何特定的硬件和软件结合。
以上所述仅为本申请的可选实施例而已，并不用于限制本申请，对于本领域的技术人员来说，本申请可以有各种更改和变化。凡在本申请的原则之内，所作的任何修改、等同替换、改进等，均应包含在本申请的保护范围之内。

Claims (17)

  1. 一种应用的冻结方法，包括：
    监控在后台运行的应用的耗电行为，并对满足异常耗电行为的应用进行冻结。
  2. 根据权利要求1所述的方法，其中，在所述应用进行冻结后，所述方法还包括：
    在监控到所述冻结的应用满足解冻条件时，对冻结的所述应用进行解冻。
  3. 根据权利要求1所述的方法，其中，所述异常耗电行为至少包括以下之一：
    所述应用对中央处理器CPU的持续占用时间超过阈值，所述应用的持锁时间超过阈值，所述应用对内存占用量超过阈值，所述应用连续申请定位时间超过阈值，所述应用对传感器使用时间超过阈值。
  4. 根据权利要求2所述的方法，其中，所述解冻条件至少包括以下之一：
    所述应用切换至前台，所述应用所在的终端处于充电状态，所述应用的冻结时间超过阈值，所述应用所在的终端的无线保真WIFI连接成功，所述应用处于设定的下载/升级时间段。
  5. 根据权利要求1所述的方法，其中，所述方法还包括：
    判断所述应用的冻结次数是否大于预设的冻结次数；
    在判断结果为是的情况下，将所述应用放入冻结黑名单。
  6. 根据权利要求5所述的方法，其中，还包括：
    当监控到位于所述冻结黑名单中的应用切换至后台运行时，冻结所述应用。
  7. 根据权利要求5所述的方法，其中，所述方法还包括：
    当监控到位于所述冻结黑名单中的所述应用切换至前台时，将所述应用解冻并从所述冻结黑名单中移除。
  8. 根据权利要求5所述的方法，其中，还包括：
    当对位于所述冻结黑名单中的应用进行满足异常耗电行为判断时，减小所述异常耗电行为中的所述阈值，和/或
    当对位于所述冻结黑名单中的应用进行满足解冻条件判断时，解冻条件包括以下至少之二：所述应用切换至前台，所述应用所在的终端处于充电状态，所述应用的冻结时间超过阈值，所述应用所在的终端的无线保真WIFI连接成功，所述应用处于设定的下载/升级时间段。
  9. 根据权利要求1至8任一所述的方法，其中，还包括：
    当对所述应用进行冻结时，先释放所述应用占有的除CPU资源之外的其它资源，然后释放所述应用占有的CPU资源。
  10. 一种应用的冻结装置，包括：
    冻结模块，设置为监控在后台运行的应用的耗电行为，并对满足异常耗电行为的应用进行冻结。
  11. 根据权利要求10所述的装置，其中，所述冻结装置还包括：
    解冻模块，设置为在监控到所述冻结的应用满足解冻条件时，对冻结的所述应用进行解冻。
  12. 根据权利要求9所述的装置，其中，所述冻结装置还设置为， 判断所述应用的冻结次数是否大于预设的冻结次数；在判断结果为是的情况下，将所述应用放入冻结黑名单。
  13. 根据权利要求12所述的装置，其中，所述冻结模块还设置为，当监控到位于所述冻结黑名单中的应用切换至后台运行时，冻结所述应用。
  14. 根据权利要求12所述的装置，其中，所述解冻模块还设置为，当监控到位于所述冻结黑名单中的所述应用切换至前台时，将所述应用解冻并从所述冻结黑名单中移除。
  15. 根据权利要求12所述的装置，其中，所述冻结装置还设置为，当对位于所述冻结黑名单中的应用进行满足异常耗电行为判断时，减小所述异常耗电行为中的所述阈值，和/或当对位于所述冻结黑名单中的应用进行满足解冻条件判断时，解冻条件包括以下至少之二：所述应用切换至前台，所述应用所在的终端处于充电状态，所述应用的冻结时间超过阈值，所述应用所在的终端的无线保真WIFI连接成功，所述应用处于设定的下载/升级时间段。
  16. 一种存储介质，所述存储介质中存储有计算机程序，其中，所述计算机程序被设置为运行时执行所述权利要求1至9任一项中所述的方法。
  17. 一种电子装置，包括存储器和处理器，所述存储器中存储有计算机程序，所述处理器被设置为运行所述计算机程序以执行所述权利要求1至9任一项中所述的方法。
PCT/CN2019/104550 2018-09-14 2019-09-05 应用的冻结方法及装置，存储介质及电子装置 WO2020052493A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201811076379.9A CN110908727A (zh) 2018-09-14 2018-09-14 应用的冻结方法及装置, 存储介质及电子装置
CN201811076379.9 2018-09-14

Publications (1)

Publication Number Publication Date
WO2020052493A1 true WO2020052493A1 (zh) 2020-03-19

Family

ID=69776967

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/104550 WO2020052493A1 (zh) 2018-09-14 2019-09-05 应用的冻结方法及装置，存储介质及电子装置

Country Status (2)

Country Link
CN (1) CN110908727A (zh)
WO (1) WO2020052493A1 (zh)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103324519A (zh) * 2013-06-17 2013-09-25 华为技术有限公司 一种恶意耗电应用的清理方法、装置及用户终端
US20150160976A1 (en) * 2013-12-06 2015-06-11 Samsung Electronics Co., Ltd. Multitasking method and electronic device therefor
CN106020415A (zh) * 2016-05-09 2016-10-12 深圳市万普拉斯科技有限公司 智能设备待机状态下的应用控制方法及装置
CN106292998A (zh) * 2016-07-28 2017-01-04 宇龙计算机通信科技(深圳)有限公司 一种后台运行程序的管理方法以及终端
CN107450704A (zh) * 2016-05-31 2017-12-08 中兴通讯股份有限公司 一种终端异常耗电的控制方法、装置及终端

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106020964A (zh) * 2016-06-30 2016-10-12 宇龙计算机通信科技(深圳)有限公司 一种应用冻结的方法、装置以及终端

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103324519A (zh) * 2013-06-17 2013-09-25 华为技术有限公司 一种恶意耗电应用的清理方法、装置及用户终端
US20150160976A1 (en) * 2013-12-06 2015-06-11 Samsung Electronics Co., Ltd. Multitasking method and electronic device therefor
CN106020415A (zh) * 2016-05-09 2016-10-12 深圳市万普拉斯科技有限公司 智能设备待机状态下的应用控制方法及装置
CN107450704A (zh) * 2016-05-31 2017-12-08 中兴通讯股份有限公司 一种终端异常耗电的控制方法、装置及终端
CN106292998A (zh) * 2016-07-28 2017-01-04 宇龙计算机通信科技(深圳)有限公司 一种后台运行程序的管理方法以及终端

Also Published As

Publication number Publication date
CN110908727A (zh) 2020-03-24

Similar Documents

Publication Publication Date Title
CN107302789B (zh) 一种提高安卓设备电池续航能力的方法及系统
EP3361348B1 (en) Terminal-based wakelock control method and apparatus
CN104699218B (zh) 一种任务管理方法及设备
CN106774786B (zh) 一种功耗控制方法以及装置
CN106648849A (zh) 进程的冷冻方法和移动终端
CN106959874B (zh) 基于操作系统的应用管理方法及应用该方法的电子设备
CN105468426A (zh) 一种应用冻结的方法及终端
CN105183137A (zh) 一种移动终端及其唤醒锁控制方法和控制系统
EP3926467B1 (en) Application control method and apparatus, terminal, and computer-readable storage medium
WO2020052471A1 (zh) 待管理应用检测及控制方法、装置、终端及存储介质
CN106550438B (zh) 限制定期唤醒的方法及系统、移动设备
CN107436672B (zh) 一种应用的处理方法及终端
CN112752332A (zh) 基于NB-IoT通信协议栈的物联网系统休眠控制方法
CN110837456B (zh) 一种控制方法、装置及电子设备
CN103257700A (zh) 一种Android系统的节能方法及装置
CN106406495A (zh) 应用程序的管理方法、应用程序的管理装置和终端
WO2020052493A1 (zh) 应用的冻结方法及装置，存储介质及电子装置
JP5801331B2 (ja) タスク制御装置
WO2020220868A1 (zh) 广播控制方法、终端及计算机可读存储介质
WO2020224417A1 (zh) 终端电耗控制的方法、装置、终端及计算机可读存储介质
WO2020094125A1 (zh) 应用控制方法、装置、终端及计算机可读存储介质
WO2018227355A1 (zh) 一种智能终端的应用程序管理系统及管理方法
WO2020224381A1 (zh) 应用状态控制方法、装置、终端及计算机可读存储介质
CN112540666A (zh) 应用解冻方法、终端设备、计算机设备和计算机可读介质
CN110045812B (zh) 信息处理方法、装置、计算机设备和计算机可读存储介质

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 19859354

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 19859354

Country of ref document: EP

Kind code of ref document: A1