WO2017070894A1 - 基于终端的唤醒锁控制方法、装置及终端 - Google Patents
基于终端的唤醒锁控制方法、装置及终端 Download PDFInfo
- Publication number
- WO2017070894A1 WO2017070894A1 PCT/CN2015/093204 CN2015093204W WO2017070894A1 WO 2017070894 A1 WO2017070894 A1 WO 2017070894A1 CN 2015093204 W CN2015093204 W CN 2015093204W WO 2017070894 A1 WO2017070894 A1 WO 2017070894A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- application
- wakelock
- preset
- identifier
- service
- Prior art date
Links
Images
Classifications
-
- 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/329—Power saving characterised by the action undertaken by task scheduling
-
- 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/3206—Monitoring of events, devices or parameters that trigger a change in power modality
- G06F1/3228—Monitoring task completion, e.g. by use of idle timers, stop commands or wait commands
-
- 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
-
- 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/3206—Monitoring of events, devices or parameters that trigger a change in power modality
-
- 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
- G06F1/3265—Power saving in display device
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/60—Protecting data
- G06F21/62—Protecting access to data via a platform, e.g. using keys or access control rules
- G06F21/629—Protecting access to data via a platform, e.g. using keys or access control rules to features or functions of an application
-
- 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
-
- 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/4401—Bootstrapping
- G06F9/4418—Suspend and resume; Hibernate and awake
-
- 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/48—Program initiating; Program switching, e.g. by interrupt
- G06F9/4806—Task transfer initiation or dispatching
- G06F9/4843—Task transfer initiation or dispatching by program, e.g. task dispatcher, supervisor, operating system
- G06F9/485—Task life-cycle, e.g. stopping, restarting, resuming execution
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
- H04W52/02—Power saving arrangements
- H04W52/0209—Power saving arrangements in terminal devices
- H04W52/0261—Power saving arrangements in terminal devices managing power supply demand, e.g. depending on battery level
- H04W52/0264—Power saving arrangements in terminal devices managing power supply demand, e.g. depending on battery level by selectively disabling software applications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
- H04W52/02—Power saving arrangements
- H04W52/0209—Power saving arrangements in terminal devices
- H04W52/0251—Power saving arrangements in terminal devices using monitoring of local events, e.g. events related to user activity
-
- 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
-
- 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
- Y02D30/00—Reducing energy consumption in communication networks
- Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks
Definitions
- the present invention relates to the field of terminal technologies, and in particular, to a terminal-based wake-lock control device, device, and terminal.
- Android is a widely used operating system on the terminal. Usually, users will set up multiple applications (Application, APP) on the terminal. In order to ensure that the application set on the terminal is working properly, Android provides a WakeLock mechanism. The application set on the terminal can apply for a wake lock to the Android system, and the Android system allocates a wake lock for the application and the service it calls. As long as the number of held wake locks is greater than 0, the Android system cannot enter the sleep state, that is, The Android system can only enter the sleep state when any of the applications set on the terminal and the services it calls do not hold the wake lock.
- the Android system In order to prevent the Android system from going to sleep, there are many applications and the services they call have unreasonable holding of the wake lock. For example, the game application still holds the wake lock, e-book application when running in the background for a long time. The called update service holds the wakelock and so on for a long time. Because the application and the service it calls for a long time unreasonably hold the wake-up lock, the standby current of the screen is increased from ten mA to tens of milliamps or even more than 100 mA, which will increase the terminal power consumption. More system resources are used.
- the embodiment of the present invention provides a terminal-based wake-up lock control method, device, and terminal, which are used to solve the problem that the application program existing in the prior art and the service invoked by the terminal are irrationally held by the wake-up lock for a long time. Consumption, excessive use of system resources.
- an embodiment of the present invention provides a terminal-based wakelock control method, including:
- the wake-up lock held by the second application and the service it invokes is forcibly released.
- the preset screening condition includes The preset duration, the preset application scenario list, and the blacklist determine whether the first application meets the preset screening conditions, specifically:
- the first application that determines that the background running time exceeds the preset duration and the application scenario is not saved in the preset application scenario list and is not saved in the blacklist does not meet the preset screening condition.
- the method further includes:
- the application scenario is saved in the preset application scenario list, or the first application saved in the blacklist meets the preset screening condition.
- the second application is forcibly released Before the program and the services it invokes hold the wakelock, it also includes:
- the second application is set to a proxy lock state.
- the method further includes:
- the wakelock application request for carrying the identifier of the second application is received, the wakelock application request is recorded in the feature information including the identifier of the second application, and the wakelock application request is not executed;
- the wakelock change request for carrying the identifier of the second application is received, the wakelock change request is recorded in the feature information including the identifier of the second application, and the wakelock change request is not executed;
- the wakelock deletion request carrying the identifier of the second application is received, the feature information including the identifier of the second application is deleted, and the wakelock deletion request is not executed.
- the method further includes:
- the forced recovery condition includes: running in the foreground or being invoked, determining whether the second application is in compliance with the mandatory recovery Conditions, including:
- the method further includes:
- an embodiment of the present invention provides a terminal-based wake-up lock control apparatus, including:
- An obtaining module configured to acquire a first application running in the background
- a first determining module configured to determine whether the first application meets a preset screening condition
- a selection module configured to select a first application that does not meet the preset screening condition, to obtain a second application
- a release module is configured to force release of the wake lock held by the second application and the service it invokes.
- the preset screening condition includes a preset duration, a preset application scenario list, and a blacklist, where the first determining module is configured to determine Whether the first application meets the preset screening conditions, specifically for:
- the first application that determines that the background running time exceeds the preset duration and the application scenario is not saved in the preset application scenario list and is not saved in the blacklist does not meet the preset screening condition.
- the method further includes:
- the determining module is configured to determine that the background running time is less than the preset duration, the application scenario is saved in the preset application scenario list, or the first application saved in the blacklist meets the preset screening condition.
- the method further includes:
- a saving module configured to save feature information of the wakelock held by the second application and the service called by the release module before the release module forcibly releases the wakelock held by the second application and the service it invokes
- the feature information includes an identifier corresponding to the second application
- a setting module configured to set the second application to a proxy lock state after the release module forcibly releases the wake lock held by the second application and the service called by the release module.
- the processing module is further configured to:
- the wakelock application request for carrying the identifier of the second application is received, the wakelock application request is recorded in the feature information including the identifier of the second application, and the wakelock application request is not executed;
- the wakelock change request for carrying the identifier of the second application is received, the wakelock change request is recorded in the feature information including the identifier of the second application, and the wakelock change request is not executed;
- the wakelock deletion request carrying the identifier of the second application is received, the feature information including the identifier of the second application is deleted, and the wakelock deletion request is not executed.
- the method further includes:
- a second determining module configured to determine whether the second application meets a mandatory recovery condition
- a recovery module if it is determined that the second application meets the mandatory recovery condition, forcibly recovering the wakeup of the second application and the service it invokes according to the feature information including the identifier of the second application lock;
- the cancel module is configured to cancel the proxy lock status of the second application.
- the forced recovery condition includes a foreground running or being invoked
- the second determining module is configured to determine Whether the second application meets the mandatory recovery condition, specifically for:
- the seventh possible implementation of the second aspect is further configured to:
- an embodiment of the present invention provides a terminal, including:
- a first processor configured to acquire a first application running in the background
- a second processor configured to determine whether the first application meets a preset screening condition, select a first application that does not meet the preset screening condition, obtain a second application, and force release the second application The wakeup lock held by the service it invokes.
- the preset screening condition includes a preset duration, a preset application scenario list, and a blacklist, where the second processor is configured to determine Whether the first application meets the preset screening conditions, specifically for:
- the first application that determines that the background running time exceeds the preset duration and the application scenario is not saved in the preset application scenario list and is not saved in the blacklist does not meet the preset screening condition.
- the second processor is further configured to:
- the application scenario is saved in the preset application scenario list, or the first application saved in the blacklist meets the preset screening condition.
- the second processor Also used for:
- the feature information includes a second corresponding The identity of the application.
- the second application After the release of the wake lock held by the second application and the service it invokes, the second application is set to the agent lock state.
- the second processor is further configured to:
- the wakelock application request for carrying the identifier of the second application is received, the wakelock application request is recorded in the feature information including the identifier of the second application, and the wakelock application request is not executed;
- the wakelock change request for carrying the identifier of the second application is received, the wakelock change request is recorded in the feature information including the identifier of the second application, and the wakelock change request is not executed;
- the wakelock deletion request carrying the identifier of the second application is received, the feature information including the identifier of the second application is deleted, and the wakelock deletion request is not executed.
- the second processor is further configured to:
- the forced recovery condition includes a foreground running or being invoked
- the second processor is configured to determine Whether the second application meets the mandatory recovery condition, specifically for:
- the second processor is further configured to:
- the embodiment of the present invention provides a terminal-based wake-up lock control method, apparatus, and terminal, and obtains a first application running in the background; determining whether the first application meets a preset screening condition; The first application that meets the preset screening condition obtains the second application; forcibly releases the wake lock held by the second application and the service it invokes.
- FIG. 1 is a flowchart of a terminal-based wakelock control method according to an embodiment of the present invention
- FIG. 3 is a flowchart of another terminal-based wakelock control method in an embodiment of the present invention.
- FIG. 4 is a flowchart of still another method for controlling a wake-up lock based on a terminal in an embodiment of the present invention
- FIG. 5 is a flowchart of a terminal-based wakelock control apparatus according to an embodiment of the present invention.
- FIG. 6 is a schematic structural diagram of a terminal according to an embodiment of the present invention.
- the embodiment of the present invention provides a wake-up lock based on the terminal.
- the control method, the method can be applied to the terminal, and the process is as shown in FIG. 1 , which specifically includes the following steps:
- the wake-up locks held belong to the case where the wake-up locks are properly held. These wake-up locks cannot be forcibly released. Therefore, this embodiment is directed to an application running in the background, and the application running in the background is defined as the first application.
- the first application can be one or more.
- S12 Determine whether the first application meets the preset screening condition.
- the preset screening condition is preset according to actual needs. After obtaining the first application running in the background on the terminal, it can be determined whether the first application meets the preset screening condition.
- S13 Select a first application that does not meet the preset screening condition, and obtain a second application.
- the first application may have a preset filter condition, or may not meet the preset filter condition, and select the first application that does not meet the preset filter condition as the second application.
- the application set on the terminal will call many services during the running process, and the application and the services it calls may hold the wake lock.
- the second application and the wakeup lock held by the server it invokes are unreasonably holding the wake lock, so Force release of the wake-up lock held by the second application and the service it invokes.
- the preset filtering conditions are set in various manners.
- the following includes an example of a preset duration, a preset application scenario list, and a blacklist.
- the S12 determines whether the first application meets the preset screening condition.
- the implementation process, as shown in Figure 2, specifically includes the following steps:
- S121 Count the background running time of the first application, and determine whether the background running time of the first application exceeds a preset duration.
- the background running time of the first application is the duration of the first application running from the foreground running to the background running. If the first application runs in the background for a long time, then it may be considered to force release of the first application and the service it calls. Some wake locks. Therefore, for the first application running in the background, the background running time can be counted, and then it is determined whether the background running time of the first application exceeds the preset duration.
- the preset duration can be set according to actual needs, for example, it can be set to 3 minutes, 5 minutes, 10 minutes, and so on.
- S122 Determine an application scenario of the first application according to the interface invoked by the first application, and compare the application scenario of the first application with the preset application scenario list.
- the first application may call the interface of the Android system during the foreground running or the background running, and may determine the application scenario of the first application according to the interface invoked by the first application, such as audio playing, downloading, etc., and some application scenarios are very important.
- the interrupt will affect the user experience. Therefore, you can obtain important application scenarios and get a list of preset application scenarios.
- the application scenario of the first application is compared with the preset application scenario list, and the application scenario of the first application is determined to be saved in the preset application scenario list.
- Some of the applications set on the terminal are very important. Forcibly releasing the wakelocks they hold will have a serious user experience. Therefore, you can get these important applications in advance and get blacklists.
- the applications in the blacklist are not. Allows the release of the held wakelock lock.
- the first application is compared with the blacklist to determine whether the first application is saved in the blacklist.
- S121 may be executed first, then S122 may be executed, S123 may be executed, S121 may be executed first, S123 may be executed, S122 may be executed, or S121 may be notified. S122 and S123.
- S124 The first application that determines that the background running time exceeds the preset duration, the application scenario is not saved in the preset application scenario list, and is not saved in the blacklist does not meet the preset screening condition.
- the application scenario is saved in the preset application scenario list, or the first application saved in the blacklist meets the preset screening condition.
- the first application that is not in compliance with the preset filter condition (that is, the second application) and the wake lock held by the service called by it may be forced to release, and the first application that retains the preset filter condition and the service hold of the call thereof Wake lock.
- the embodiment of the present invention further provides another terminal-based wake-up lock control method.
- the process of the method is as shown in FIG. 3.
- the method On the basis of the method shown in FIG. 1, the method further includes:
- S15 Save feature information of the wakelock held by the second application and the service invoked by the service, and the feature information includes an identifier corresponding to the second application.
- the feature information of the wake lock held by the second application and the service called by the second application and the called application may be saved before the release of the wake lock held by the second application and the service called by the second application, and the feature information includes the second application
- the identifier is used to indicate that the feature information is related to the second application, and the feature information of the wake-up locks may include binding information, tag information, tag information, and the like.
- the second application can also be set to the agent lock state. Since the second application is in the agent lock state, if the request for the second application and the service request, the change, and the deletion of the wake lock are received, only the corresponding feature information is changed, and the corresponding request is not specifically executed, for example:
- the wakelock application request carrying the identifier of the second application is received, the wakelock application request is recorded in the feature information including the identifier of the second application, and the wakelock request request is not executed;
- the wakelock change request carrying the identifier of the second application is received, the wakelock change request is recorded in the feature information including the identifier of the second application, and the wakelock change request is not executed;
- the wakelock deletion request carrying the identifier of the second application is received, the feature information including the identifier of the second application is deleted, and the wakelock deletion request is not executed.
- the embodiment of the present invention further provides a terminal-based wake-up lock control method.
- the process of the method is shown in FIG. 4 .
- the method further includes:
- the forced recovery condition can be set according to actual needs.
- the second application may be included according to the second application.
- the identified feature information forces recovery of the wakelock held by the second application and the service it invokes, and cancels the agent lock state of the second application.
- the setting of the forced recovery condition may be performed in multiple manners.
- the following describes the implementation process of determining whether the second application meets the mandatory recovery condition in the foregoing S17 by using the foreground running or being invoked as an example, specifically: monitoring the second application. Whether the program is converted to run in the foreground or whether the second application is called; if it is monitored that the second application is converted to run in the foreground or the second application is called, it is determined that the second application meets the mandatory recovery condition; If the application is not converted to run in the foreground and the second application is not called, then it is determined that the second application does not meet the mandatory recovery condition.
- the embodiment of the present application further provides a terminal-based wake-lock control device, which corresponds to the terminal-based wake-lock control method shown in FIG. 1 , and the structure of the device is as shown in FIG. 5 , including :
- the obtaining module 51 is configured to acquire a first application running in the background
- the first determining module 52 is configured to determine whether the first application meets the preset screening condition
- the selecting module 53 is configured to select a first application that does not meet the preset screening condition, and obtain a second application.
- the release module 54 is configured to forcibly release the wake lock held by the second application and the service it invokes.
- the preset screening condition includes a preset duration, a preset application scenario list, and a blacklist
- the first determining module 52 is configured to determine whether the first application meets the preset screening condition, specifically for:
- the first application that determines that the background running time exceeds the preset duration and the application scenario is not saved in the preset application scenario list and is not saved in the blacklist does not meet the preset screening criteria.
- the foregoing apparatus further includes:
- the determining module is configured to determine that the background running time is less than the preset duration, the application scenario is saved in the preset application scenario list, or the first application saved in the blacklist meets the preset screening condition.
- the foregoing apparatus further includes:
- a saving module configured to save feature information of the wakelock held by the second application and the service called by the release module before the release module forcibly releases the wakeup lock held by the second application and the service invoked by the service, and the feature information includes the corresponding The identity of the second application;
- a setting module configured to set the second application to a proxy lock state after the release module forcibly releases the wakeup lock held by the second application and the service invoked by the second application.
- the foregoing apparatus further includes a processing module, configured to:
- the wakelock application request carrying the identifier of the second application is received, the wakelock application request is recorded in the feature information including the identifier of the second application, and the wakelock request request is not executed;
- the wakelock change request carrying the identifier of the second application is received, the wakelock change request is recorded in the feature information including the identifier of the second application, and the wakelock change request is not executed;
- the wakelock deletion request carrying the identifier of the second application is received, the feature information including the identifier of the second application is deleted, and the wakelock deletion request is not executed.
- the foregoing apparatus further includes:
- a second determining module configured to determine whether the second application meets a mandatory recovery condition
- a recovery module configured to: if the second application is determined to meet the mandatory recovery condition, forcibly restore the wake lock held by the second application and the service invoked by the second application according to the feature information of the identifier of the second application;
- the cancel module is used to cancel the proxy lock status of the second application.
- the forced recovery condition includes the foreground running or being invoked
- the second determining module is configured to determine whether the second application meets the mandatory recovery condition, specifically for:
- the second determining module is further configured to:
- the embodiment of the present application further provides a terminal, which corresponds to the terminal-based wakelock control method of FIG. 1.
- the structure of the device is as shown in FIG. 6, and includes:
- the first processor 61 is configured to acquire a first application running in the background
- the second processor 62 is configured to determine whether the first application meets the preset screening condition, select the first application that does not meet the preset screening condition, and obtain the second application; forcibly release the second application and the service that is called Hold the wake lock.
- the preset filter condition includes a preset duration, a preset application scenario list, and a blacklist
- the second processor 62 is configured to determine whether the first application meets the preset screening condition, specifically for:
- the first application that determines that the background running time exceeds the preset duration and the application scenario is not saved in the preset application scenario list and is not saved in the blacklist does not meet the preset screening criteria.
- the second processor 62 is further configured to:
- the second processor 62 is further configured to:
- the second application After the release of the wake lock held by the second application and the service it invokes, the second application is set to the agent lock state.
- the second processor 62 is further configured to:
- the wakelock application request carrying the identifier of the second application is received, the wakelock application request is recorded in the feature information including the identifier of the second application, and the wakelock request request is not executed;
- the wakelock change request carrying the identifier of the second application is received, the wakelock change request is recorded in the feature information including the identifier of the second application, and the wakelock change request is not executed;
- the wakelock deletion request carrying the identifier of the second application is received, the feature information including the identifier of the second application is deleted, and the wakelock deletion request is not executed.
- the second processor 62 is further configured to:
- the forced recovery condition includes the foreground running or being invoked
- the second processor 62 is configured to determine whether the second application meets the mandatory recovery condition, specifically for:
- the second processor 62 is further configured to:
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Computer Security & Cryptography (AREA)
- Computer Hardware Design (AREA)
- Health & Medical Sciences (AREA)
- General Health & Medical Sciences (AREA)
- Bioethics (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Stored Programmes (AREA)
- Telephone Function (AREA)
- Power Sources (AREA)
- Telephonic Communication Services (AREA)
Abstract
Description
Claims (24)
- 一种基于终端的唤醒锁控制方法,其特征在于,包括:获取后台运行的第一应用程序;判断所述第一应用程序是否符合预设筛选条件;选取不符合所述预设筛选条件的第一应用程序,得到第二应用程序;强制释放所述第二应用程序及其调用的服务持有的唤醒锁。
- 如权利要求1所述的方法,其特征在于,所述预设筛选条件包括预设时长、预设应用场景名单和黑名单,判断所述第一应用程序是否符合预设筛选条件,具体包括:统计所述第一应用程序的后台运行时长,判断所述第一应用程序的后台运行时长是否超过所述预设时长;根据所述第一应用程序调用的接口确定所述第一应用程序的应用场景,将所述第一应用程序的应用场景与所述预设应用场景名单进行比对;以及,将所述第一应用程序与所述黑名单比对;确定后台运行时长超过预设时长、应用场景未保存在所述预设应用场景名单中且未保存在所述黑名单中的第一应用程序不符合所述预设筛选条件。
- 如权利要求2所述的方法,其特征在于,还包括:确定后台运行时长小于预设时长、应用场景保存在所述预设应用场景名单中或者保存在所述黑名单中的第一应用程序符合所述预设筛选条件。
- 如权利要求1-3任一所述的方法,其特征在于,强制释放所述第二应用程序及其调用的服务持有的唤醒锁之前,还包括:保存所述第二应用程序及其调用的服务持有的唤醒锁的特征信息,所述特征信息包括对应第二应用程序的标识;强制释放所述第二应用程序及其调用的服务持有的唤醒锁之后,还包括:将所述第二应用程序设置为代理锁状态。
- 如权利要求4所述的方法,其特征在于,还包括:若接收到携带所述第二应用程序的标识的唤醒锁申请请求,则在包括所述第二应用程序的标识的特征信息中记录所述唤醒锁申请请求,不执行所述唤醒锁申请请求;若接收到携带所述第二应用程序的标识的唤醒锁变更请求,则在包括所述第二应用程序的标识的特征信息中记录所述唤醒锁变更请求,不执行所述唤醒锁变更请求;若接收到携带所述第二应用程序的标识的唤醒锁删除请求,则删除包括所述第二应用程序的标识的特征信息,不执行所述唤醒锁删除请求。
- 如权利要求了4所述的方法,其特征在于,还包括:判断所述第二应用程序是否符合强制恢复条件;若确定所述第二应用程序符合强制恢复条件,则根据包括所述第二应用程序的标识的特征信息,强制恢复所述第二应用程序及其调用的服务持有的唤醒锁;取消所述第二应用程序的代理锁状态。
- 如权利要求6所述的方法,其特征在于,所述强制恢复条件包括前台运行或者被调用,判断所述第二应用程序是否符合强制恢复条件,具体包括:监控所述第二应用程序是否转换为前台运行或者所述第二应用程序是否被调用;若监控到所述第二应用程序转换为前台运行或者所述第二应用程序被调用,则确定所述第二应用程序符合所述强制恢复条件。
- 如权利要求7所述的方法,其特征在于,还包括:若监控到所述第二应用程序未转换为前台运行且所述第二应用程序未被调用,则确定所述第二应用程序不符合所述强制恢复条件。
- 一种基于终端的唤醒锁控制装置,其特征在于,包括:获取模块,用于获取后台运行的第一应用程序;第一判断模块,用于判断所述第一应用程序是否符合预设筛选条件;选取模块,用于选取不符合所述预设筛选条件的第一应用程序,得到第二应用程序;释放模块,用于强制释放所述第二应用程序及其调用的服务持有的唤醒锁。
- 如权利要求9所述的装置,其特征在于,所述预设筛选条件包括预设时长、预设应用场景名单和黑名单,所述第一判断模块,用于判断所述第一应用程序是否符合预设筛选条件,具体用于:统计所述第一应用程序的后台运行时长,判断所述第一应用程序的后台运行时长是否超过所述预设时长;根据所述第一应用程序调用的接口确定所述第一应用程序的应用场景,将所述第一应用程序的应用场景与所述预设应用场景名单进行比对;以及,将所述第一应用程序与所述黑名单比对;确定后台运行时长超过预设时长、应用场景未保存在所述预设应用场景名单中且未保存在所述黑名单中的第一应用程序不符合所述预设筛选条件。
- 如权利要求10所述的装置,其特征在于,还包括:确定模块,用于确定后台运行时长小于预设时长、应用场景保存在所述预设应用场景名单中或者保存在所述黑名单中的第一应用程序符合所述预设筛选条件。
- 如权利要求9-11任一所述的装置,其特征在于,还包括:保存模块,用于在所述释放模块强制释放所述第二应用程序及其调用的服务持有的唤醒锁之前,保存所述第二应用程序及其调用的服务持有的唤醒锁的特征信息,所述特征信息包括对应第二应用程序的标识;以及,设置模块,用于在所述释放模块强制释放所述第二应用程序及其调用的服务持有的唤醒锁之后,将所述第二应用程序设置为代理锁状态。
- 如权利要求12所述的装置,其特征在于,还包括处理模块,用于:若接收到携带所述第二应用程序的标识的唤醒锁申请请求,则在包括所述第二应用程序的标识的特征信息中记录所述唤醒锁申请请求,不执行所述唤醒锁申请请求;若接收到携带所述第二应用程序的标识的唤醒锁变更请求,则在包括所述第二应用程序的标识的特征信息中记录所述唤醒锁变更请求,不执行所述唤醒锁变更请求;若接收到携带所述第二应用程序的标识的唤醒锁删除请求,则删除包括所述第二应用程序的标识的特征信息,不执行所述唤醒锁删除请求。
- 如权利要求了12所述的装置,其特征在于,还包括:第二判断模块,用于判断所述第二应用程序是否符合强制恢复条件;恢复模块,用于若确定所述第二应用程序符合强制恢复条件,则根据包括所述第二应用程序的标识的特征信息,强制恢复所述第二应用程序及其调用的服务持有的唤醒锁;取消模块,用于取消所述第二应用程序的代理锁状态。
- 如权利要求14所述的装置,其特征在于,所述强制恢复条件包括前台运行或者被调用,所述第二判断模块,用于判断所述第二应用程序是否符合强制恢复条件,具体用于:监控所述第二应用程序是否转换为前台运行或者所述第二应用程序是否被调用;若监控到所述第二应用程序转换为前台运行或者所述第二应用程序被调用,则确定所述第二应用程序符合所述强制恢复条件。
- 如权利要求15所述的装置,其特征在于,所述第二判断模块,还用于:若监控到所述第二应用程序未转换为前台运行且所述第二应用程序未被调 用,则确定所述第二应用程序不符合所述强制恢复条件。
- 一种终端,其特征在于,包括:第一处理器,用于获取后台运行的第一应用程序;第二处理器,用于判断所述第一应用程序是否符合预设筛选条件;选取不符合所述预设筛选条件的第一应用程序,得到第二应用程序;强制释放所述第二应用程序及其调用的服务持有的唤醒锁。
- 如权利要求17所述的终端,其特征在于,所述预设筛选条件包括预设时长、预设应用场景名单和黑名单,所述第二处理器,用于判断所述第一应用程序是否符合预设筛选条件,具体用于:统计所述第一应用程序的后台运行时长,判断所述第一应用程序的后台运行时长是否超过所述预设时长;根据所述第一应用程序调用的接口确定所述第一应用程序的应用场景,将所述第一应用程序的应用场景与所述预设应用场景名单进行比对;以及,将所述第一应用程序与所述黑名单比对;确定后台运行时长超过预设时长、应用场景未保存在所述预设应用场景名单中且未保存在所述黑名单中的第一应用程序不符合所述预设筛选条件。
- 如权利要求18所述的终端,其特征在于,所述第二处理器,还用于:确定后台运行时长小于预设时长、应用场景保存在所述预设应用场景名单中或者保存在所述黑名单中的第一应用程序符合所述预设筛选条件。
- 如权利要求17-19任一所述的终端,其特征在于,所述第二处理器,还用于:在强制释放所述第二应用程序及其调用的服务持有的唤醒锁之前,保存所述第二应用程序及其调用的服务持有的唤醒锁的特征信息,所述特征信息包括对应第二应用程序的标识;以及,在强制释放所述第二应用程序及其调用的服务持有的唤醒锁之后,将所述第二应用程序设置为代理锁状态。
- 如权利要求20所述的终端,其特征在于,所述第二处理器,还用于:若接收到携带所述第二应用程序的标识的唤醒锁申请请求,则在包括所述第二应用程序的标识的特征信息中记录所述唤醒锁申请请求,不执行所述唤醒锁申请请求;若接收到携带所述第二应用程序的标识的唤醒锁变更请求,则在包括所述第二应用程序的标识的特征信息中记录所述唤醒锁变更请求,不执行所述唤醒锁变更请求;若接收到携带所述第二应用程序的标识的唤醒锁删除请求,则删除包括所述第二应用程序的标识的特征信息,不执行所述唤醒锁删除请求。
- 如权利要求了20所述的终端,其特征在于,所述第二处理器,还用于:判断所述第二应用程序是否符合强制恢复条件;若确定所述第二应用程序符合强制恢复条件,则根据包括所述第二应用程序的标识的特征信息,强制恢复所述第二应用程序及其调用的服务持有的唤醒锁;取消所述第二应用程序的代理锁状态。
- 如权利要求22所述的终端,其特征在于,所述强制恢复条件包括前台运行或者被调用,所述第二处理器,用于判断所述第二应用程序是否符合强制恢复条件,具体用于:监控所述第二应用程序是否转换为前台运行或者所述第二应用程序是否被调用;若监控到所述第二应用程序转换为前台运行或者所述第二应用程序被调用,则确定所述第二应用程序符合所述强制恢复条件。
- 如权利要求23所述的终端,其特征在于,所述第二处理器,还用于:若监控到所述第二应用程序未转换为前台运行且所述第二应用程序未被调用,则确定所述第二应用程序不符合所述强制恢复条件。
Priority Applications (6)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2018522123A JP6639665B2 (ja) | 2015-10-29 | 2015-10-29 | 端末ベースのウェイクロック制御の方法、装置及び端末 |
EP15906958.2A EP3361348B1 (en) | 2015-10-29 | 2015-10-29 | Terminal-based wakelock control method and apparatus |
PCT/CN2015/093204 WO2017070894A1 (zh) | 2015-10-29 | 2015-10-29 | 基于终端的唤醒锁控制方法、装置及终端 |
KR1020187014739A KR102098581B1 (ko) | 2015-10-29 | 2015-10-29 | 단말기 기반 웨이크록(wakelock)의 제어 방법, 장치, 및 단말기 |
US15/772,349 US10788881B2 (en) | 2015-10-29 | 2015-10-29 | Terminal-based wakelock control method and apparatus and terminal |
CN201580042100.3A CN106662907B (zh) | 2015-10-29 | 2015-10-29 | 基于终端的唤醒锁控制方法、装置及终端 |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/CN2015/093204 WO2017070894A1 (zh) | 2015-10-29 | 2015-10-29 | 基于终端的唤醒锁控制方法、装置及终端 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2017070894A1 true WO2017070894A1 (zh) | 2017-05-04 |
Family
ID=58629671
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2015/093204 WO2017070894A1 (zh) | 2015-10-29 | 2015-10-29 | 基于终端的唤醒锁控制方法、装置及终端 |
Country Status (6)
Country | Link |
---|---|
US (1) | US10788881B2 (zh) |
EP (1) | EP3361348B1 (zh) |
JP (1) | JP6639665B2 (zh) |
KR (1) | KR102098581B1 (zh) |
CN (1) | CN106662907B (zh) |
WO (1) | WO2017070894A1 (zh) |
Cited By (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN109765983A (zh) * | 2017-11-01 | 2019-05-17 | 中国电信股份有限公司 | 运行程序管理方法、装置和移动终端 |
CN110086835A (zh) * | 2018-01-24 | 2019-08-02 | 腾讯科技(深圳)有限公司 | 应用程序管控方法、终端、服务器及系统 |
CN110572866A (zh) * | 2019-07-26 | 2019-12-13 | 华为技术有限公司 | 一种唤醒锁的管理方法及电子设备 |
EP3671451A4 (en) * | 2017-08-16 | 2021-07-28 | JRD Communication (Shenzhen) Ltd | PROCESS FOR AUTOMATICALLY RELEASING A RESOURCE OCCUPIED BY A BACKGROUND PROCESS OF A TERMINAL, INFORMATION MEDIA AND TERMINAL |
Families Citing this family (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN107291212A (zh) * | 2017-06-16 | 2017-10-24 | 深圳天珑无线科技有限公司 | 电源锁处理方法及装置 |
CN108121570B (zh) * | 2017-12-21 | 2021-01-19 | 深圳市沃特沃德股份有限公司 | 车载系统休眠的方法与装置 |
CN109189196A (zh) * | 2018-08-01 | 2019-01-11 | 北京珠穆朗玛移动通信有限公司 | 终端设备的管理方法、终端设备及装置 |
CN109379337B (zh) * | 2018-09-18 | 2021-01-26 | 四川长虹电器股份有限公司 | 一种安卓平台下应用进程的保活方法 |
CN111352660A (zh) * | 2018-12-20 | 2020-06-30 | 成都鼎桥通信技术有限公司 | 持有唤醒锁应用的识别方法与装置 |
CN110086932B (zh) * | 2019-04-24 | 2021-05-25 | 努比亚技术有限公司 | 一种进程启动控制方法、穿戴式设备及存储介质 |
CN110837290A (zh) * | 2019-09-30 | 2020-02-25 | 华为终端有限公司 | 一种内核锁的管理方法及终端设备 |
CN112035242B (zh) * | 2020-11-06 | 2021-03-09 | 南京研利科技有限公司 | 播放推送消息的方法、计算设备和计算机可读存储介质 |
CN112506629B (zh) * | 2020-11-27 | 2023-08-22 | 努比亚技术有限公司 | 一种系统调度优化方法、终端及计算机可读存储介质 |
Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN103402027A (zh) * | 2013-07-29 | 2013-11-20 | 广东欧珀移动通信有限公司 | 一种移动终端和使移动终端进入睡眠状态的方法 |
CN103885565A (zh) * | 2012-12-21 | 2014-06-25 | 希姆通信息技术(上海)有限公司 | 智能设备的休眠方法及系统 |
CN104038635A (zh) * | 2014-06-25 | 2014-09-10 | 深圳市中兴移动通信有限公司 | 一种移动终端及其异常待机的提示方法 |
CN104156053A (zh) * | 2014-07-29 | 2014-11-19 | 深圳市中兴移动通信有限公司 | 一种异常耗电的控制方法、装置和移动终端 |
CN104298549A (zh) * | 2014-09-30 | 2015-01-21 | 北京金山安全软件有限公司 | 移动终端中应用程序的清理方法、装置和移动终端 |
US20150208352A1 (en) * | 2014-01-22 | 2015-07-23 | Seven Networks, Inc. | Method for power saving in mobile devices by optimizing wakelocks |
Family Cites Families (18)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20110040989A1 (en) * | 2009-06-22 | 2011-02-17 | David Keyes Keyes | Systems and methods for managing power consumption of mobile computing devices |
US20120209923A1 (en) * | 2011-02-12 | 2012-08-16 | Three Laws Mobility, Inc. | Systems and methods for regulating access to resources at application run time |
US20120291102A1 (en) * | 2011-05-09 | 2012-11-15 | Google Inc. | Permission-based administrative controls |
US8769676B1 (en) * | 2011-12-22 | 2014-07-01 | Symantec Corporation | Techniques for identifying suspicious applications using requested permissions |
US10013511B2 (en) * | 2012-04-09 | 2018-07-03 | Purdue Research Foundation | System and method for energy usage accounting in software applications |
KR101324604B1 (ko) * | 2012-05-25 | 2013-11-01 | 전자부품연구원 | 다중 대기 상태 운용 방법 및 이를 적용한 방송수신장치 |
CN104166542B (zh) * | 2013-05-17 | 2018-01-05 | 腾讯科技(深圳)有限公司 | 检测应用耗电的方法和装置 |
CN103324519A (zh) | 2013-06-17 | 2013-09-25 | 华为技术有限公司 | 一种恶意耗电应用的清理方法、装置及用户终端 |
US9501382B2 (en) * | 2013-06-25 | 2016-11-22 | Purdue Research Foundation | Systems and methods of detecting power bugs |
US9229522B1 (en) * | 2013-08-27 | 2016-01-05 | Symantec Corporation | Mobile battery performance by identifying apps that disproportionally run background tasks that prevent mobile devices from sleeping |
US9965014B2 (en) * | 2013-09-27 | 2018-05-08 | Intel Corporation | Techniques for tracing wakelock usage |
US10423514B1 (en) * | 2013-10-28 | 2019-09-24 | Symantec Corporation | Automated classification of mobile app battery consumption using simulation |
CN104731302B (zh) * | 2013-12-20 | 2018-01-12 | 北京猎豹移动科技有限公司 | 一种移动终端省电操作的方法及系统 |
US9841802B2 (en) * | 2014-02-20 | 2017-12-12 | Qualcomm Incorporated | Wake lock management through application monitoring |
US9769756B1 (en) * | 2014-03-26 | 2017-09-19 | Amazon Technologies, Inc. | Wake-up quotas and statistics generation |
US9648564B1 (en) * | 2014-03-26 | 2017-05-09 | Amazon Technologies, Inc. | Wake-up management for mobile devices |
KR102217336B1 (ko) * | 2014-04-22 | 2021-02-19 | 엘지전자 주식회사 | 이동단말기 제어방법 |
WO2016053984A1 (en) * | 2014-09-29 | 2016-04-07 | Lebon-Schnider Francois | Methods and systems for regulating communications at a mobile communications device |
-
2015
- 2015-10-29 CN CN201580042100.3A patent/CN106662907B/zh active Active
- 2015-10-29 EP EP15906958.2A patent/EP3361348B1/en active Active
- 2015-10-29 WO PCT/CN2015/093204 patent/WO2017070894A1/zh active Application Filing
- 2015-10-29 JP JP2018522123A patent/JP6639665B2/ja active Active
- 2015-10-29 US US15/772,349 patent/US10788881B2/en active Active
- 2015-10-29 KR KR1020187014739A patent/KR102098581B1/ko active IP Right Grant
Patent Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN103885565A (zh) * | 2012-12-21 | 2014-06-25 | 希姆通信息技术(上海)有限公司 | 智能设备的休眠方法及系统 |
CN103402027A (zh) * | 2013-07-29 | 2013-11-20 | 广东欧珀移动通信有限公司 | 一种移动终端和使移动终端进入睡眠状态的方法 |
US20150208352A1 (en) * | 2014-01-22 | 2015-07-23 | Seven Networks, Inc. | Method for power saving in mobile devices by optimizing wakelocks |
CN104038635A (zh) * | 2014-06-25 | 2014-09-10 | 深圳市中兴移动通信有限公司 | 一种移动终端及其异常待机的提示方法 |
CN104156053A (zh) * | 2014-07-29 | 2014-11-19 | 深圳市中兴移动通信有限公司 | 一种异常耗电的控制方法、装置和移动终端 |
CN104298549A (zh) * | 2014-09-30 | 2015-01-21 | 北京金山安全软件有限公司 | 移动终端中应用程序的清理方法、装置和移动终端 |
Non-Patent Citations (1)
Title |
---|
See also references of EP3361348A4 * |
Cited By (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP3671451A4 (en) * | 2017-08-16 | 2021-07-28 | JRD Communication (Shenzhen) Ltd | PROCESS FOR AUTOMATICALLY RELEASING A RESOURCE OCCUPIED BY A BACKGROUND PROCESS OF A TERMINAL, INFORMATION MEDIA AND TERMINAL |
US11138041B2 (en) | 2017-08-16 | 2021-10-05 | JRD Communication (Shenzhen) Ltd. | Method for automatically releasing resource occupied by process in background of terminal, storage medium and terminal |
CN109765983A (zh) * | 2017-11-01 | 2019-05-17 | 中国电信股份有限公司 | 运行程序管理方法、装置和移动终端 |
CN110086835A (zh) * | 2018-01-24 | 2019-08-02 | 腾讯科技(深圳)有限公司 | 应用程序管控方法、终端、服务器及系统 |
CN110086835B (zh) * | 2018-01-24 | 2021-08-03 | 腾讯科技(深圳)有限公司 | 应用程序管控方法、终端、服务器及系统 |
CN110572866A (zh) * | 2019-07-26 | 2019-12-13 | 华为技术有限公司 | 一种唤醒锁的管理方法及电子设备 |
Also Published As
Publication number | Publication date |
---|---|
KR20180074762A (ko) | 2018-07-03 |
JP2019505031A (ja) | 2019-02-21 |
EP3361348A4 (en) | 2018-11-07 |
CN106662907B (zh) | 2019-10-22 |
JP6639665B2 (ja) | 2020-02-05 |
US10788881B2 (en) | 2020-09-29 |
EP3361348B1 (en) | 2021-12-01 |
KR102098581B1 (ko) | 2020-04-08 |
US20180321733A1 (en) | 2018-11-08 |
EP3361348A1 (en) | 2018-08-15 |
CN106662907A (zh) | 2017-05-10 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2017070894A1 (zh) | 基于终端的唤醒锁控制方法、装置及终端 | |
US10838838B2 (en) | Method and apparatus for dealing with abnormality of application program and storage medium | |
CN105677477B (zh) | 一种优化应用程序资源的方法、装置及电子设备 | |
JP5694602B2 (ja) | ワイヤレスローカルエリアネットワークへのデータのオフロード | |
WO2015184885A1 (zh) | 关闭移动终端后台应用的方法、装置及移动终端 | |
WO2014117653A1 (zh) | 内存清理方法、装置和终端设备 | |
WO2017156676A1 (zh) | 一种针对应用的处理方法、装置及智能终端 | |
CA2974820A1 (en) | System and method for introducing functionality to an application for use with a network service | |
EP3209005B1 (en) | Task processing device, intelligent apparatus, task processing method and baseband processor | |
WO2010015175A1 (zh) | 一种即时通讯系统窗口的创建方法、设备和系统 | |
CN103246568A (zh) | 一种通过手机设置应用优先级的方法和装置 | |
CN112383585A (zh) | 消息处理系统、方法及电子设备 | |
CN106951314B (zh) | 面向Android系统后台服务自动唤醒的切断方法 | |
WO2022095862A1 (zh) | 调整线程优先级的方法、终端及计算机可读存储介质 | |
WO2020237545A1 (zh) | 相机启动方法及相关装置 | |
CN109885340B (zh) | 一种应用程序冷启动加速方法、装置、电子设备 | |
US20160255614A1 (en) | Network Device, Terminal Device, and Voice Service Control Method | |
CN113542256A (zh) | 客户端中登录凭证的更新方法、装置、设备及存储介质 | |
CN107765834B (zh) | 应用管理方法、装置、存储介质及电子设备 | |
CN112015525A (zh) | 任务进程阻塞管理方法 | |
CN102263797A (zh) | 一种会话控制的方法及装置 | |
TW200813819A (en) | Computer micro-jobs | |
CN106776057B (zh) | 事件处理方法及装置 | |
CN108009009A (zh) | 电子设备的处理器、软件执行方法及存储器 | |
CN107783825A (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: 15906958 Country of ref document: EP Kind code of ref document: A1 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2018522123 Country of ref document: JP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 15772349 Country of ref document: US |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2015906958 Country of ref document: EP |
|
ENP | Entry into the national phase |
Ref document number: 20187014739 Country of ref document: KR Kind code of ref document: A |