Patent Description:
With development of communications technologies, currently many devices support a multi-task system, that is, a device may run multiple application programs at the same time, and one application program may have one or more threads, each of which is referred to as a task. Multiple tasks usually include a foreground task and a background task. The foreground task refers to a task that requires user interaction, that is, an operation input by a user needs to be received during execution of the foreground task. The background task refers to a task that does not require user interaction, that is, an operation input by a user does not need to be received during execution of the background task. Because the background task does not require user interaction, the background task is generally not a user-sensitive task, or the background task is not of user concern. In other words, some background tasks do not need to be executed. However, the background tasks are continually executed in the background of a system, and continuously consume power of a device. It can be seen that, currently a device may suffer from great power consumption and power loss. <CIT> describes managing processes within suspended states and execution states. <NPL>, describes process lifetimes states for Windows Store apps.

In the following, parts of the description and drawing referring to embodiments, which are not covered by the claims are not presented as embodiments of the invention, but as examples useful for understanding the invention.

To describe the technical solutions in the embodiments of the present invention or in the prior art more clearly, the following briefly introduces the accompanying drawings required for describing the embodiments or the prior art.

The following clearly and completely describes the technical solutions in the embodiments of the present invention with reference to the accompanying drawings in the embodiments of the present invention.

In the embodiments of the present invention, a first scenario and a second scenario are not limited to two scenarios. The first scenario may indicate one or more scenarios, and the second scenario may also indicate one or more scenarios. For example, the first scenario may be a scenario corresponding to a foreground task, and there may be one or more foreground tasks at the same time, that is, the first scenario may be one or more scenarios. The second scenario may be any one or more scenarios except the first scenario; for example, the second scenario may be a scenario corresponding to a task excluding a foreground task. Here, the first and the second are named only for distinguishing two different scenarios.

In addition, in the embodiments of the present invention, a scenario may refer to a status of an action of a device that implements the embodiments of the present invention. The status of the action of the device may refer to a status in which the device uses a system resource. The system resource may be specifically a hardware resource, such as a CPU resource or a memory resource, or the system resource may be specifically a virtual resource, such as a network bandwidth resource or an operating system resource, which is not limited in the embodiments of the present invention. A scenario may be making a call, sending a short message service message, using a browser, playing a 2D/3D game, viewing a main user interface, downloading a file, reading an ebook, playing music, watching a video, navigating through a website, browsing a photo, taking a photo, making a video, sending an email, and the like.

In addition, in the embodiments of the present invention, a scenario corresponding to a task may be specifically a scenario that a task enters when the task is executed. For example, when a music task is being executed, the task enters a music scenario and a download scenario, that is, a scenario corresponding to the music task may include the music scenario and the download scenario. In addition, a task corresponding to a scenario may be specifically a task that enters the scenario. For example, when a music task is being executed, the task enters a download scenario; when a browser task is being executed, the task also enters the download scenario; when a software update task is being executed, the task also enters the download scenario. In this way, the tasks corresponding to the download scenario may include: the music task, the browser task, and the software update task, that is, one scenario corresponds to different tasks.

In addition, in the embodiments of the present invention, a foreground task may refer to a task that requires user interaction, that is, an operation input by a user needs to be received during execution of the foreground task. Alternatively, a foreground task may refer to a task that is displayed on a screen. A background task may refer to a task that does not require user interaction during execution, that is, an operation input by a user does not need to be received during execution of the background task. Alternatively, a background task may refer to a task that is not displayed on a screen. In addition, it can be understood that a task may be a thread in the embodiments of the present invention.

Referring to <FIG> is a schematic flowchart of a task management method, which is not covered by the claims but an example useful for understanding the invention. As shown in <FIG>, the method includes the following steps:
<NUM>. Determine, according to a foreground task, a first scenario corresponding to the foreground task.

Optionally, step <NUM> may be specifically determining, when a current task is switched, a corresponding first scenario according to the current task. For example, when the current task, a music task, is being executed, the task enters a music scenario or a download scenario. In this way, it can be determined that the first scenario corresponding to the foreground task may be the music scenario, the download scenario, or the like. In addition, the foreground task may be one or multiple foreground tasks. In the case of multiple foreground tasks, step <NUM> may include: determining, according to multiple foreground tasks, a first scenario corresponding to each foreground task. That is, step <NUM> may include: determining, according to at least one foreground task, a first scenario corresponding to each foreground task.

When the first scenario corresponding to the foreground task is in a first list, search for at least one background task corresponding to the first scenario, where the first list includes a scenario in which task limitation is allowed.

Optionally, the scenario in which task limitation is allowed and that is included in the first list may be a scenario that is set for receiving an operation input by a user. In this way, the scenario in which task limitation is allowed, and that is set according to the operation input by the user and meets the user's requirements or habits can be implemented. For example, a user likes to reduce power consumption of a device, and the user may set in the first list multiple scenarios in which task limitation is allowed, for example, setting a browser scenario, a game scenario, a navigation scenario, or the like as the scenario in which task limitation is allowed. In this way, when the first scenario corresponding to the current task is the browser scenario, the game scenario, or the navigation scenario, step <NUM> can be performed to reduce power consumption of the device.

Optionally, the scenario in which task limitation is allowed and that is included in the first list may be automatically set according to performance of a device. For example, when the device has better performance, for example, a CPU of the device is running at a high speed, the device has a larger memory, or the device has enough battery, only a few scenarios in which task limitation is allowed may be set in the first list. For example, when the device has poor performance, for example, the CPU of the device is running at a low speed, the device has a smaller memory, or the device does not have enough battery, more scenarios in which task limitation is allowed may be set in the first list. Because the first list has more scenarios in which task limitation is allowed, and step <NUM> and step <NUM> are performed multiple times, limitation processing can be performed on multiple background tasks, so as to reduce power consumption of the device and ensure stable running of the device.

Optionally, the at least one background task corresponding to the first scenario may refer to at least one background task in all background tasks corresponding to the first scenario, or the at least one background task corresponding to the first scenario may refer to all background tasks corresponding to the first scenario. This embodiment sets no limit thereto.

Perform limitation processing on the at least one background task corresponding to the first scenario, where the limitation processing refers to processing for reducing system resource usage.

Optionally, the limitation processing may be processing for reducing a system resource currently used by a task. For example, a quantity of system resources used by a background task A is A when step <NUM> is performed, and after the limitation processing is performed on the background task A, a quantity of system resources used by the background task A is B, where A is greater than B. In addition, B may be zero.

Optionally, the method may be specifically applied to any devices having a multi-task system, such as a tablet computer, a mobile phone, an e-reader, a remote control, a personal computer (Personal Computer, PC), a notebook computer, an in-vehicle device, a web TV, a wearable device, or other intelligent devices having a network function.

In the foregoing technical solutions, a first scenario corresponding to a foreground task is determined according to the foreground task, and when the first scenario corresponding to the foreground task is in a first list, at least one background task corresponding to the first scenario is searched for, where the first list includes a scenario in which task limitation is allowed; and limitation processing is performed on the at least one background task corresponding to the first scenario, where the limitation processing refers to processing for reducing system resource usage. In this way, limitation processing is implemented on at least one background task corresponding to a scenario in which task limitation is allowed. Compared with the prior art in which a background task is always being executed, this can reduce power consumption and power loss of a device.

Referring to <FIG> is a schematic flowchart of another task management method, which is not covered by the claims but an example useful for understanding the invention. As shown in <FIG>, the method includes the following steps:.

Optionally, step <NUM> may be specifically: searching for at least one background task that is in background tasks corresponding to the first scenario and that will not affect other tasks or an operating system after undergoing limitation processing; or searching for at least one pre-determined background task in background tasks corresponding to the first scenario; or searching for at least one background task that is in background tasks corresponding to the first scenario and whose user identifier corresponds to a common user. For example, step <NUM> may include:
searching for a user identifier of each background task corresponding to the first scenario, and searching for a background task whose user identifier (User Identifier, UID) corresponds to a common user as the at least one background task corresponding to the first scenario.

That is, this step is used to implement that the at least one background task that is corresponding to the first scenario and is searched for in step <NUM> is the background task whose UID corresponds to a common user. A UID is an inherent identifier of each task and is used to uniquely identify the task. In addition, a UID may correspond to a system user and a common user. When a UID of a background task corresponds to a system user, it indicates that the background task is a background task included in an operating system. When a UID of a background task corresponds to a common user, it indicates that the background task is not a background task included in an operating system.

Optionally, the method may further include:
ignoring a background task whose UID corresponds to a system user in the at least one background task corresponding to the first scenario. That is, processing is not performed on the background task whose UID corresponds to a system user.

Optionally, step <NUM> may be: searching for at least one background task that is in background tasks corresponding to the first scenario and whose system resource usage reaches a preset threshold. For example, searching for at least one background task that is in the background tasks corresponding to the first scenario and whose CPU resource usage reaches <NUM>% of CPU resources; or searching for at least one background task that is in the background tasks corresponding to the first scenario and whose sleep lock holding duration reaches <NUM> minutes; or searching for at least one background task that is in the background tasks corresponding to the first scenario and whose average data download speed reaches <NUM> per minute.

Optionally, as shown in <FIG>, the method may further include:.

Optionally, the second scenario may refer to one or more scenarios. In addition, the second scenario may refer to all scenarios except the first scenario, or one or more scenarios except the first scenario, which is not limited in this embodiment.

In addition, the at least one background task corresponding to the second scenario may refer to at least one background task in all background tasks corresponding to the second scenario, or the at least one background task corresponding to the second scenario may refer to all background tasks corresponding to the second scenario. This embodiment sets no limit thereto. In addition, the second scenario may be specifically a pre-determined scenario, for example, a scenario that is set for receiving an operation input by a user. In this way, the scenario in which task limitation is allowed, and that is set according to the operation input by the user and meets the user's requirements or habits can be implemented. In addition, step <NUM> may be specifically: searching for at least one background task that is in the background tasks corresponding to the second scenario and will not affect other tasks or an operating system after undergoing limitation processing; or searching for at least one pre-determined background task in the background tasks corresponding to the second scenario; or searching for at least one background task that is in the background tasks corresponding to the second scenario and whose user identifier corresponds to a common user.

Optionally, the second scenario may be a scenario except the first scenario and not in a second list, where the second list may include a scenario in which task limitation is prohibited. The scenario in which task limitation is prohibited may be a scenario that is set for receiving an operation input by a user. In this way, the scenario in which task limitation is prohibited, and that is set according to the operation input by the user and meets the user's requirements or habits can be implemented. For example, the user may set, in the second list, a scenario that requires user attention as the scenario in which task limitation is prohibited, for example, a short message service message scenario, a call scenario, and a download scenario. Alternatively, the scenario in which task limitation is prohibited may be automatically set according to performance of a device. For example, when the device has better performance, for example, a CPU of the device is running at a high speed, the device has a larger memory, or the device has enough battery, more scenarios in which task limitation is prohibited may be set in the second list. For example, when the device has poor performance, for example, the CPU of the device is running at a low speed, the device has a smaller memory, or the device does not have enough battery, only a few scenarios in which task limitation is prohibited may be set in the second list.

Optionally, before step <NUM>, the method may further include:.

In this implementation manner, because the background task whose UID corresponds to a common user is not a task of an operating system, other tasks are not affected after limitation processing is performed on the background task Therefore, limitation processing is performed only on a background task whose UID corresponds to a common user in step <NUM>, which can reduce power consumption and power loss of the device without affecting other tasks.

Optionally, the system component includes but is not limited to a timer, a sleep lock, and broadcast notification. Meanwhile, a status value of the system component when the system component is paused may be saved in the foregoing step, so that the background task can call the saved status value of the system component after the limitation processing is released. In addition, the system component used by the at least one background task corresponding to the first scenario is stopped only when the timer reaches the preset threshold (for example, <NUM>, <NUM>, or the like). This may avoid frequently stopping the system component used by the at least one background task corresponding to the first scenario.

In this implementation manner, because the system component used by the at least one background task corresponding to the first scenario is stopped, power consumption and power loss of the device may also be reduced.

Optionally, the processing for reducing system resource usage may include at least one of the following manners:.

In this case, step <NUM> may be: freezing the at least one background task corresponding to the first scenario, or stopping the at least one background task corresponding to the first scenario, or limiting a system resource used by the at least one background task corresponding to the first scenario.

Optionally, the freezing the at least one background task corresponding to the first scenario may be prohibiting the background task from calling a system resource, for example, prohibiting a CPU from calling the at least one background task corresponding to the first scenario. Specifically, a task scheduler of an operating system is used to prohibit the at least one background task corresponding to the first scenario from participating in any scheduling. Because the at least one background task corresponding to the first scenario is prohibited from calling the system resource, power consumption of the device is reduced.

Optionally, the limiting a system resource used by the at least one background task corresponding to the first scenario may be limiting a time within which the CPU calls the at least one background task corresponding to the first scenario. For example, a time value for CPU calling is set for the at least one background task corresponding to the first scenario, so that the CPU can call the at least one background task corresponding to the first scenario within a time indicated by the time value. In addition, the limiting a system resource used by the at least one background task corresponding to the first scenario may further be limiting use of the system resource by the at least one background task corresponding to the first scenario. For example, limiting use of a network bandwidth by the at least one background task corresponding to the first scenario or limiting use of memory space by the at least one background task corresponding to the first scenario. In addition, it may further be using different limitation measures depending on different scenarios corresponding to the at least one background task corresponding to the first scenario. Because use of the system resource by the at least one background task corresponding to the first scenario is limited in the foregoing step, power consumption of the device is reduced.

Optionally, step <NUM> may further include:
when a temperature reaches a preset temperature threshold, determining, according to the foreground task, a first scenario corresponding to the foreground task.

The temperature may be a temperature of the device that implements this embodiment, where the temperature of the device may specifically refer to a temperature of the CPU of the device or a temperature of a modem of the device.

In this implementation manner, it may be implemented that limitation processing is performed on the background task only when the temperature of the device reaches the preset temperature threshold.

Optionally, the method may further include:
releasing the limitation processing on the at least one background task corresponding to the first scenario. Specifically, when the first scenario is not in the first list, the limitation processing is released for the background task that has undergone the limitation processing.

Optionally, the method may be specifically applied to any devices having a multi-task system, such as a tablet computer, a mobile phone, an e-reader, a remote control, a PC, a notebook computer, an in-vehicle device, a web TV, a wearable device, or other intelligent devices having a network function.

In the foregoing technical solution, multiple optional implementation manners are implemented on the basis of the first embodiment, all of which can reduce power consumption and power loss of a device.

Referring to <FIG> is a schematic flowchart of another task management method, which is not covered by the claims but an example useful for understanding the invention. As shown in <FIG>, the method includes the following steps:
<NUM>. Determine, according to a foreground task, a first scenario corresponding to the foreground task.

Optionally, step <NUM> may specifically be determining, when a current task is switched, a corresponding first scenario according to the current task. For example, when the current task, a music task, is being executed, the task enters a music scenario or a download scenario. In this way, it can be determined that the first scenario corresponding to the foreground task may be the music scenario or the download scenario, or the like. In addition, the foreground task may be one or multiple foreground tasks. In the case of multiple foreground tasks, step <NUM> may include: determining, according to multiple foreground tasks, a first scenario corresponding to each foreground task. That is, step <NUM> may include: determining, according to at least one foreground task, a first scenario corresponding to each foreground task.

Determine a second scenario except the first scenario corresponding to the foreground task, where the second scenario is a scenario in which task limitation is allowed and the second scenario corresponds to at least one background task.

Optionally, the second scenario may refer to one or more scenarios. In addition, the second scenario may refer to all scenarios except the first scenario, or one or more scenarios except the first scenario, which is not limited in this embodiment. In addition, the second scenario may be specifically a pre-determined scenario, for example, a scenario that is set for receiving an operation input by a user. In this way, the scenario in which task limitation is allowed, and that is set according to the operation input by the user and meets the user's requirements or habits can be implemented.

Optionally, the second scenario may be a scenario except the first scenario and not in a second list, where the second list may include a scenario in which task limitation is prohibited.

Search for the at least one background task corresponding to the second scenario.

Optionally, the at least one background task corresponding to the second scenario may refer to at least one background task in all background tasks corresponding to the second scenario, or the at least one background task corresponding to the second scenario may refer to all background tasks corresponding to the second scenario. In addition, step <NUM> may be specifically: searching for at least two background tasks that are in the background tasks corresponding to the second scenario and that will not affect other tasks or an operating system after undergoing limitation processing; or searching for at least one pre-determined background task in the background tasks corresponding to the second scenario; or searching for at least one background task that is in the background tasks corresponding to the second scenario and whose UID corresponds to a common user. For example, step <NUM> may include:
searching for a UID of each background task corresponding to the second scenario, and searching for a background task whose UID corresponds to a common user as the at least one background task corresponding to the second scenario.

That is, this step is used to implement that the at least one background task that is corresponding to the second scenario and is searched for in step <NUM> is the background task whose UID corresponds to a common user.

Optionally, the method may further include:
ignoring a background task whose UID corresponds to a system user in the at least one background task corresponding to the second scenario. That is, processing is not performed on the background task whose UID corresponds to a system user.

Optionally, step <NUM> may be: searching for at least one background task whose system resource usage reaches a preset threshold in the background tasks corresponding to the second scenario.

Perform limitation processing on the at least one background task corresponding to the second scenario, where the limitation processing refers to processing for reducing system resource usage.

For this implementation manner of this embodiment, further refer to the implementation manner in which the limitation processing is performed on the at least one background task corresponding to the first scenario in the first and second embodiments, which is not repeatedly described here.

Optionally, the system component includes but is not limited to a timer, a sleep lock, and broadcast notification. Meanwhile, a status value of the system component when the system component is paused may be saved in the foregoing step, so that the background task can call the saved status value of the system component after the limitation processing is released. In addition, the system component used by the at least one background task corresponding to the second scenario is stopped only when the timer reaches the preset threshold (for example, <NUM>, <NUM>, or the like). This may avoid frequently stopping the system component used by the at least one background task corresponding to the second scenario.

In this implementation manner, because the system component used by the at least one background task corresponding to the second scenario is stopped, power consumption and power loss of the device may be reduced.

Optionally, the processing for reducing system resource usage includes at least one of the following manners:.

In this case, step <NUM> may be: freezing the at least one background task corresponding to the second scenario; stopping the at least one background task corresponding to the second scenario; or limiting a system resource used by the at least one background task corresponding to the second scenario.

Optionally, the freezing the at least one background task corresponding to the second scenario may be prohibiting the background task from calling a system resource, for example, prohibiting a CPU from calling the at least one background task corresponding to the first scenario. Specifically, a task scheduler of an operating system is used to prohibit the at least one background task corresponding to the first scenario from participating in any scheduling. Because the at least one background task corresponding to the second scenario is prohibited from calling the system resource, power consumption of the device is reduced.

Optionally, the limiting a system resource used by the at least one background task corresponding to the second scenario may be limiting a time within which the CPU calls the at least one background task corresponding to the second scenario. For example, a time value for CPU calling is set for the at least one background task corresponding to the second scenario, so that the CPU can call the at least one background task corresponding to the second scenario within a time indicated by the time value. In addition, the limiting a system resource used by the at least one background task corresponding to the second scenario may further be limiting use of the system resource by the at least one background task corresponding to the second scenario. For example, limiting use of a network bandwidth by the at least one background task corresponding to the second scenario or limiting use of memory space by the at least one background task corresponding to the second scenario. In addition, it may further be using different limitation measures depending on different scenarios corresponding to the at least one background task corresponding to the second scenario. Because use of the system resource by the at least one background task corresponding to the second scenario is limited in the foregoing step, power consumption of the device is reduced.

In the foregoing technical solution, a first scenario corresponding to a foreground task is determined according to the foreground task; a second scenario except the first scenario corresponding to the foreground task is determined, where the second scenario is a scenario in which task limitation is allowed and the second scenario corresponds to at least one background task; the at least one background task corresponding to the second scenario is searched for; and limitation processing is performed on the at least one background task corresponding to the second scenario, where the limitation processing refers to processing for reducing system resource usage. Therefore, power consumption and power loss of a device can be reduced.

Referring to <FIG> is a schematic flowchart of a task management method, which is not covered by the claims but an example useful for understanding the invention. As shown in <FIG>, the method includes the following steps:
<NUM>. Determine whether a scenario that is currently switched to is a scenario included in a whitelist. If yes, perform step <NUM>. If no, end the process. The whitelist is a preset list including at least one scenario in which background task limitation is allowed.

Optionally, the foregoing scenario may be specifically a status of an action of a device that implements step <NUM>. The status of the action of the device may refer to a status in which the device uses a system resource. The system resource may be specifically a hardware resource, for example, a CPU resource or a memory resource, or the system resource may be specifically a virtual resource, for example, a network bandwidth resource or an operating system resource. A scenario may be making a call, sending a short message service message, using a browser, playing a 2D/3D game, viewing a main user interface, downloading a file, reading an ebook, playing music, watching a video, navigating through a website, browsing a photo, taking a photo, making a video, sending an email, and the like. In addition, the scenario that is currently switched to may be one or more scenarios. In addition, scenario switching may be specifically switching generated by a switching time of a foreground task. For example, when a foreground task is started, one or more scenarios are switched to. For example, when a task of making a call is started, the device switches to a scenario of making a call; when a music task is started, the device switches to a music playing scenario and a music download scenario; when a game task is started, the device switches to a game scenario and an Internet access scenario. For example, when a foreground task is stopped, the device switches to one or more scenarios. For example, when a game task is stopped, the device switches from a game scenario to a main user interface scenario.

Optionally, the scenario in which background task limitation is allowed may be a scenario that is set for receiving an operation input by a user. In this way, the scenario in which background task limitation is allowed, and that is set according to the operation input by the user and meets the user's requirements or habits can be implemented. For example, a user likes to reduce power consumption of a device, and the user may set in the whitelist multiple scenarios in which background task limitation is allowed, for example, setting a browser scenario, a game scenario, a navigation scenario, or the like as the scenario in which background task limitation is allowed. In this way, when a current scenario of the device is the browser scenario, the game scenario, or the navigation scenario, step <NUM> can be performed to reduce power consumption of the device.

Optionally, the scenario in which background task limitation is allowed may be automatically set according to performance of the device. For example, when the device has better performance, for example, a CPU of the device is running at a high speed, the device has a larger memory, or the device has enough battery, only a few scenarios in which background task limitation is allowed may be set in the whitelist. For example, when the device has poor performance, for example, the CPU of the device is running at a low speed, the device has a smaller memory, or the device does not have enough battery, more scenarios in which background task limitation is allowed may be set in the whitelist. Because the whitelist has more scenarios in which background task limitation is allowed, and step <NUM> and step <NUM> are performed multiple times, limitation processing can be performed on multiple background tasks that allow limitation processing, so as to reduce power consumption of the device and ensure stable running of the device.

When it is determined that the scenario that is currently switched to is the scenario included in the whitelist, search for a background task that allows limitation processing in currently running background tasks, where the limitation processing refers to processing for reducing system resource usage.

Optionally, the background task that allows limitation processing may be specifically a background task that will not affect other tasks (such as a foreground task) or an operating system after undergoing the limitation processing; or the background task that allows limitation processing may be specifically a pre-determined background task; or the background task that allows limitation processing may be specifically a background task that meets a specific condition.

Optionally, the limitation processing may be specifically an operation used to reduce a system resource currently used by a task. For example, a quantity of system resources used by a background task A is A when step <NUM> is performed, and after the limitation processing is performed on the background task A, a quantity of system resources used by the background task A is B, where A is greater than B. In addition, B may be zero.

Perform the limitation processing on the background task that allows limitation processing.

It should be noted that, the scenario in this embodiment may be equivalent to the scenario in the foregoing embodiments. In addition, the whitelist in this embodiment may be the first list in the foregoing embodiments.

In the foregoing technical solution, whether a scenario that is currently switched to is a scenario included in a whitelist is determined, where the whitelist is a preset list including at least one scenario in which background task limitation is allowed; when it is determined that the scenario that is currently switched to is the scenario included in the whitelist, a background task that allows limitation processing is searched for in currently running background tasks, where the limitation processing refers to processing for reducing system resource usage; and the limitation processing is performed on the background task that allows limitation processing. In this way, limitation processing is implemented on a background task that allows limitation processing. Compared with the prior art in which a background task is always being executed, this can reduce power consumption and power loss of a device.

Referring to <FIG> is a schematic diagram of another task management method according to the present invention. As shown in <FIG>, the method includes the following steps:.

The task management method may further include:.

The following describes apparatus embodiments of the present invention. The apparatus embodiments of the present invention are used to execute the methods implemented in the first embodiment to the fifth embodiment of the present invention. For ease of description, the following describes only the part related to the embodiments of the present invention. For specific technology details that are not disclosed, refer to the first embodiment, the second embodiment, the third embodiment, the fourth embodiment, and the fifth embodiment of the present invention.

Referring to <FIG> is a schematic diagram of a structure of a task management device, which is not covered by the claims but an example useful for understanding the invention. As shown in <FIG>, the task management device includes: a determining unit <NUM>, a first search unit <NUM>, and a first processing unit <NUM>.

The determining unit <NUM> is configured to determine, according to a foreground task, a first scenario corresponding to the foreground task.

Optionally, the determining unit <NUM> may specifically determine, when a current task is switched, a corresponding first scenario according to the current task. For example, when the current task, a music task, is being executed, the task enters a music scenario or a download scenario. In this way, it can be determined that the first scenario corresponding to the foreground task may be the music scenario or the download scenario, or the like. In addition, the foreground task may be one or multiple foreground tasks. In the case of multiple foreground tasks, the determining unit <NUM> may be configured to determine, according to multiple foreground tasks, a first scenario corresponding to each foreground task. That is, the determining unit <NUM> may determine, according to at least one foreground task, a first scenario corresponding to each foreground task.

The first search unit <NUM> is configured to search for, when the first scenario that corresponds to the foreground task and is determined by the determining unit <NUM> is in a first list, at least one background task corresponding to the first scenario, where the first list includes a scenario in which task limitation is allowed.

Optionally, the scenario in which task limitation is allowed and that is included in the first list may be a scenario that is set for receiving an operation input by a user. In this way, the scenario in which task limitation is allowed, and that is set according to the operation input by the user and meets the user's requirements or habits can be implemented. For example, a user likes to reduce power consumption of a device, and the user may set in the first list multiple scenarios in which task limitation is allowed, for example, setting a browser scenario, a game scenario, a navigation scenario, or the like as the scenario in which task limitation is allowed. In this way, when the first scenario corresponding to the current task is the browser scenario, the game scenario, or the navigation scenario, the first search unit <NUM> can perform a search action to reduce power consumption of the device.

Optionally, the scenario in which task limitation is allowed and that is included in the first list may be automatically set according to performance of a device. For example, when the device has better performance, for example, a CPU of the device is running at a high speed, the device has a larger memory, or the device has enough battery, only a few scenarios in which task limitation is allowed may be set in the first list. For example, when the device has poor performance, for example, the CPU of the device is running at a low speed, the device has a smaller memory, or the device does not have enough battery, more scenarios in which task limitation is allowed may be set in the first list. In this way, power consumption of the device can be reduced.

The first processing unit <NUM> is configured to perform limitation processing on the at least one background task that corresponds to the first scenario and is searched for by the first search unit <NUM>, where the limitation processing refers to processing for reducing system resource usage.

Optionally, the limitation processing may be processing for reducing a system resource currently used by a task.

Optionally, the device may be specifically any devices having a multi-task system, such as a tablet computer, a mobile phone, an e-reader, a remote control, a PC, a notebook computer, an in-vehicle device, a web TV, a wearable device, or other intelligent devices having a network function.

In the foregoing technical solutions, a first scenario corresponding to a foreground task is determined according to the foreground task, and when the first scenario corresponding to the foreground task is in a first list, at least one background task corresponding to the first scenario is searched for, where the first list includes a scenario in which task limitation is allowed; and limitation processing is performed on the at least one background task corresponding to the first scenario, where the limitation processing refers to processing for reducing system resource usage. In this way, limitation processing is implemented on at least one background task corresponding to a scenario in which task limitation is allowed. Compared with the prior art in which a background task is always being executed, the embodiments of the present invention can reduce power consumption and power loss of a device.

Referring to <FIG> is a schematic diagram of a structure of a task management device, which is not covered by the claims but an example useful for understanding the invention. As shown in <FIG>, the task management device includes: a determining unit <NUM>, a judging unit <NUM>, a first search unit <NUM>, and a first processing unit <NUM>, where:
The determining unit <NUM> is configured to determine, according to a foreground task, a first scenario corresponding to the foreground task.

The judging unit <NUM> is configured to determine whether the first scenario that is determined by the determining unit <NUM> is in a first list, where the first list includes a scenario in which task limitation is allowed.

The first search unit <NUM> is configured to search for, when the judging unit <NUM> determines that the first scenario that is determined by the determining unit <NUM> is in the first list, at least one background task corresponding to the first scenario.

Optionally, the first search unit <NUM> may specifically search for at least one background task that is in background tasks corresponding to the first scenario and that will not affect other tasks or an operating system after undergoing limitation processing; or search for at least one pre-determined background task in background tasks corresponding to the first scenario; or search for at least one background task that is in background tasks corresponding to the first scenario and whose user identifier corresponds to a common user. For example, a user identifier UID of each background task corresponding to the first scenario is searched for, and a background task whose UID corresponds to a common user is searched for and used as the at least one background task corresponding to the first scenario.

In this way, it can be implemented that the at least one background task that is corresponding to the first scenario and is searched for by the first search unit <NUM> is the background task whose UID corresponds to a common user. A UID is an inherent identifier of each task and may be used to uniquely identify the task. In addition, a UID may correspond to a system user and a common user. When a UID of a background task corresponds to a system user, it indicates that the background task is a background task included in an operating system. When a UID of a background task corresponds to a common user, it indicates that the background task is not a background task included in an operating system.

Optionally, the device may be further configured to ignore a background task that is in the at least one background task corresponding to the first scenario and whose UID corresponds to a system user. That is, processing is not performed on the background task whose UID corresponds to a system user.

Optionally, the first search unit <NUM> may search for at least one background task that is in background tasks corresponding to the first scenario and whose system resource usage reaches a preset threshold. For example, at least one background task that is in the background tasks corresponding to the first scenario and whose CPU resource usage reaches <NUM>% of CPU resources is searched for; or at least one background task that is in the background tasks corresponding to the first scenario and whose sleep lock holding duration reaches <NUM> minutes is searched for; or at least one background task that is in the background tasks corresponding to the first scenario and whose average data download speed reaches <NUM> per minute is searched for.

Optionally, as shown in <FIG>, the device may further include:.

In addition, the at least one background task corresponding to the second scenario may refer to at least one background task in all background tasks corresponding to the second scenario, or the at least one background task corresponding to the second scenario may refer to all background tasks corresponding to the second scenario. This embodiment sets no limit thereto. In addition, the second scenario may be specifically a pre-determined scenario, for example, a scenario that is set for receiving an operation input by a user. In this way, the scenario in which task limitation is allowed, and that is set according to the operation input by the user and meets the user's requirements or habits can be implemented. In addition, the second search unit <NUM> may specifically search for at least one background task that is in the background tasks corresponding to the second scenario and will not affect other tasks or an operating system after undergoing limitation processing; or search for at least one pre-determined background task in the background tasks corresponding to the second scenario; or search for at least one background task that is in the background tasks corresponding to the second scenario and whose user identifier corresponds to a common user.

Optionally, the second scenario may be a scenario except the first scenario and not in a second list, where the second list may include a scenario in which task limitation is prohibited. The scenario in which task limitation is prohibited may be a scenario that is set for receiving an operation input by a user. In this way, the scenario in which task limitation is prohibited, and that is set according to the operation input by the user, and meets the user's requirements or habits can be implemented. For example, the user may set, in the second list, a scenario that requires user attention as the scenario in which task limitation is prohibited, for example, a short message service message scenario, a call scenario, and a download scenario. Alternatively, the scenario in which task limitation is prohibited may be automatically set according to performance of a device. For example, when the device has better performance, for example, a CPU of the device is running at a high speed, the device has a larger memory, or the device has enough battery, more scenarios in which task limitation is prohibited may be set in the second list. For example, when the device has poor performance, for example, the CPU of the device is running at a low speed, the device has a smaller memory, or the device does not have enough battery, only a few scenarios in which task limitation is prohibited may be set in the second list.

In this implementation manner, because the background task whose UID corresponds to a common user is not a task of an operating system, other tasks are not affected after limitation processing is performed on these background tasks. Therefore, the first processing unit <NUM> limits only a background task whose UID corresponds to a common user, which can reduce power consumption and power loss of the device without affecting other tasks.

Optionally, the system component includes but is not limited to a timer, a sleep lock, and broadcast notification. In addition, a status value of the system component when the system component is paused may be saved in the device, so that the background task can call the saved status value of the system component after the limitation processing is released. In addition, the system component used by the at least one background task corresponding to the first scenario is stopped only when the timer reaches the preset threshold (for example, <NUM>, <NUM>, or the like). This may avoid frequently stopping the system component used by the at least one background task corresponding to the first scenario.

In this implementation manner, because the system component used by the at least one background task corresponding to the first scenario is stopped, power consumption and power loss of the device may be reduced.

In this way, the first processing unit <NUM> may freeze the at least one background task corresponding to the first scenario, or stop the at least one background task corresponding to the first scenario, or limit a system resource used by the at least one background task corresponding to the first scenario.

According to the present invention, the freezing the at least one background task corresponding to the first scenario may be prohibiting the background task from calling a system resource, for example, prohibiting a CPU from calling the at least one background task corresponding to the first scenario. Specifically, a task scheduler of an operating system is used to prohibit the at least one background task corresponding to the first scenario from participating in any scheduling. Because the at least one background task corresponding to the first scenario is prohibited from calling the system resource, power consumption of the device is reduced.

Optionally, the limiting a system resource used by the at least one background task corresponding to the first scenario may be limiting a time within which the CPU calls the at least one background task corresponding to the first scenario. For example, a time value for CPU calling is set for the at least one background task corresponding to the first scenario, so that the CPU can call the at least one background task corresponding to the first scenario within a time indicated by the time value. In addition, the limiting a system resource used by the at least one background task corresponding to the first scenario may further be limiting use of the system resource by the at least one background task corresponding to the first scenario from using the system resource. For example, limiting the at least one background task corresponding to the first scenario or limiting use of memory space by the at least one background task corresponding to the first scenario. In addition, it may further be using different limitation measures depending on different scenarios corresponding to the at least one background task corresponding to the first scenario. Because use of the system resource by the at least one background task corresponding to the first scenario is limited in the foregoing step, power consumption of the device is reduced.

Optionally, when a temperature reaches a preset temperature threshold, the determining unit <NUM> may be further configured to determine, according to the foreground task, a first scenario corresponding to the foreground task.

The temperature may be a temperature of the device, where the temperature of the device may specifically refer to a temperature of the CPU of the device or a temperature of a modem of the device.

Optionally, the device may be further configured to release the limitation processing on the at least one background task corresponding to the first scenario. Specifically, when the first scenario is not in the first list, the limitation processing is released for the background task that has undergone the limitation processing.

Referring to <FIG> is a schematic diagram of a structure of another task management device, which is not covered by the claims but an example useful for understanding the invention. As shown in <FIG>, the task management device includes: a first determining unit <NUM>, a second determining unit <NUM>, a first search unit <NUM>, and a first processing unit <NUM>.

The first determining unit <NUM> is configured to determine, according to a foreground task, a first scenario corresponding to the foreground task.

Optionally, the first determining unit <NUM> may specifically determine, when a current task is switched, a corresponding first scenario according to the current task. For example, when the current task, a music task, is being executed, the task enters a music scenario or a download scenario. In this way, it can be determined that the first scenario corresponding to the foreground task may be the music scenario or the download scenario, or the like. In addition, the foreground task may be one or multiple foreground tasks. In the case of multiple foreground tasks, the first determining unit <NUM> may be configured to determine, according to multiple foreground tasks, a first scenario corresponding to each foreground task. That is, the first determining unit <NUM> may be configured to determine, according to at least one foreground task, a first scenario corresponding to each foreground task.

The second determining unit <NUM> is configured to determine a second scenario except the first scenario that corresponds to the foreground task and is determined by the first determining unit <NUM>, where the second scenario is a scenario in which task limitation is allowed and the second scenario corresponds to at least one background task.

Optionally, the second scenario may refer to one or more scenarios. In addition, the second scenario may refer to all scenarios except the first scenario, or one or more scenarios except the first scenario, which is not limited in this embodiment. In addition, according to the present invention, the second scenario may be specifically a pre-determined scenario, for example, a scenario that is set for receiving an operation input by a user. In this way, the scenario in which task limitation is allowed, and that is set according to the operation input by the user and meets the user's requirements or habits can be implemented.

The first search unit <NUM> is configured to search for the at least one background task corresponding to the second scenario that is determined by the second determining unit <NUM>.

Optionally, the at least one background task corresponding to the second scenario may refer to at least one background task in all background tasks corresponding to the second scenario, or the at least one background task corresponding to the second scenario may refer to all background tasks corresponding to the second scenario. In addition, the first search unit <NUM> may specifically search for at least two background tasks that are in the background tasks corresponding to the second scenario and that will not affect other tasks or an operating system after undergoing limitation processing; or search for at least one pre-determined background task in the background tasks corresponding to the second scenario; or search for at least one background task that is in the background tasks corresponding to the second scenario and whose UID corresponds to a common user. For example, the first search unit <NUM> may be configured to search for a UID of each background task corresponding to the second scenario, and search for a background task whose UID corresponds to a common user as the at least one background task corresponding to the second scenario.

The foregoing operations can implement that the at least one background task that is corresponding to the second scenario and is searched for by the first search unit <NUM> is the background task whose UID corresponds to a common user.

Optionally, the device may be further configured to ignore a background task whose UID corresponds to a system user in the at least one background task corresponding to the second scenario. That is, processing is not performed on the background task whose UID corresponds to a system user.

Optionally, the first search unit <NUM> may be configured to search for at least one background task whose system resource usage reaches a preset threshold in the background tasks corresponding to the second scenario.

The first processing unit <NUM> is configured to perform limitation processing on the at least one background task that corresponds to the second scenario and is searched for by the first search unit <NUM>, where the limitation processing refers to processing for reducing system resource usage.

According to the present invention, the system component includes but is not limited to a timer, a sleep lock, and broadcast notification. Meanwhile, a status value of the system component when the system component is paused may be saved in the foregoing step, so that the background task can call the saved status value of the system component after the limitation processing is released. In addition, the system component used by the at least one background task corresponding to the second scenario is stopped only when the timer reaches the preset threshold (for example, <NUM>, <NUM>, or the like). This may avoid frequently stopping the system component used by the at least one background task corresponding to the second scenario.

In this case, the first processing unit <NUM> may freeze the at least one background task corresponding to the second scenario, or stop the at least one background task corresponding to the second scenario, or limit a system resource used by the at least one background task corresponding to the second scenario.

Referring to <FIG> is a schematic diagram of a structure of another task management device, which is not covered by the claims but an example useful for understanding the invention. As shown in <FIG>, the task management device includes: a memory <NUM> and a processor <NUM> connected to the memory <NUM>, where the memory <NUM> is configured to store program code, and the processor <NUM> is configured to invoke a program stored in the memory <NUM> to perform the following operations:.

Optionally, the processor <NUM> may specifically determine, when a current task is switched, a corresponding first scenario according to the current task. For example, when the current task, a music task, is being executed, the task enters a music scenario or a download scenario. In this way, it can be determined that the first scenario corresponding to the foreground task may be the music scenario or the download scenario, or the like. In addition, the foreground task may be one or multiple foreground tasks. In the case of multiple foreground tasks, the processor <NUM> may be configured to determine, according to multiple foreground tasks, a first scenario corresponding to each foreground task. That is, the processor <NUM> may determine, according to at least one foreground task, a first scenario corresponding to each foreground task.

Optionally, the scenario in which task limitation is allowed and that is included in the first list may be a scenario that is set for receiving an operation input by a user. In this way, the scenario in which task limitation is allowed, and that is set according to the operation input by the user and meets the user's requirements or habits can be implemented. For example, a user likes to reduce power consumption of a device, and the user may set in the first list multiple scenarios in which task limitation is allowed, for example, setting a browser scenario, a game scenario, a navigation scenario, or the like as the scenario in which task limitation is allowed. In this way, when the first scenario corresponding to the current task is the browser scenario, the game scenario, or the navigation scenario, the processor <NUM> may perform a search operation to reduce power consumption of the device.

Optionally, the scenario in which task limitation is allowed and that is included in the first list may be automatically set according to performance of a device. For example, when the device has better performance, for example, a CPU of the device is running at a high speed, the device has a larger memory, or the device has enough battery, only a few scenarios in which task limitation is allowed may be set in the first list. For example, when the device has poor performance, for example, the CPU of the device is running at a low speed, the device has a smaller memory, or the device does not have enough battery, more scenarios in which task limitation is allowed may be set in the first list because the first list has a large number of scenarios in which task limitation is allowed.

Optionally, the limitation processing may be processing used to reduce current system resource usage.

In another embodiment, the processor <NUM> may be further configured to perform the following operations:.

Optionally, the processor <NUM> may specifically search for at least one background task that is in background tasks corresponding to the first scenario and that will not affect other tasks or an operating system after undergoing limitation processing; or search for at least one pre-determined background task in the background tasks corresponding to the first scenario; or search for at least one background task that is in background tasks corresponding to the first scenario and whose user identifier corresponds to a common user. For example, the operation, performed by the processor <NUM>, of searching for at least one background task corresponding to the first scenario may include:
searching for a user identifier of each background task corresponding to the first scenario, and searching for a background task whose UID corresponds to a common user as the at least one background task corresponding to the first scenario.

That is, this operation is used to implement that the at least one background task that is corresponding to the first scenario and is searched for by the processor <NUM> is the background task whose UID corresponds to a common user. A UID is an inherent identifier of each task and is used to uniquely identify the task. In addition, a UID may correspond to a system user and a common user. When a UID of a background task corresponds to a system user, it indicates that the background task is a background task included in an operating system. When a UID of a background task corresponds to a common user, it indicates that the background task is not a background task included in an operating system.

Optionally, the processor <NUM> may be further configured to:
ignore a background task whose UID corresponds to a system user in the at least one background task corresponding to the first scenario. That is, processing is not performed on the background task whose UID corresponds to a system user.

Optionally, the processor <NUM> may search for at least one background task that is in background tasks corresponding to the first scenario and whose system resource usage reaches a preset threshold. For example, at least one background task that is in the background tasks corresponding to the first scenario and whose CPU resource usage reaches <NUM>% of CPU resources is searched for; or at least one background task that is in the background tasks corresponding to the first scenario and whose sleep lock holding duration reaches <NUM> minutes is searched for; or at least one background task that is in the background tasks corresponding to the first scenario and whose average data download speed reaches <NUM> per minute is searched for.

Optionally, the processor <NUM> may be further configured to perform the following operations:.

In addition, the at least one background task corresponding to the second scenario may refer to at least one background task in all background tasks corresponding to the second scenario, or the at least one background task corresponding to the second scenario may refer to all background tasks corresponding to the second scenario. This embodiment sets no limit thereto. In addition, the second scenario may be specifically a pre-determined scenario, for example, a scenario that is set for receiving an operation input by a user. In this way, the scenario in which task limitation is allowed, and that is set according to the operation input by the user and meets the user's requirements or habits can be implemented. In addition, the processor <NUM> may specifically search for at least one background task that is in the background tasks corresponding to the second scenario and will not affect other tasks or an operating system after undergoing limitation processing; or search for at least one pre-determined background task in the background tasks corresponding to the second scenario; or search for at least one background task that is in the background tasks corresponding to the second scenario and whose user identifier corresponds to a common user.

Optionally, the second scenario may be a scenario except the first scenario and not in a second list, where the second list may include a scenario in which task limitation is prohibited. In addition, the second list may be referred to as a blacklist. The scenario in which task limitation is prohibited may be a scenario that is set for receiving an operation input by a user. In this way, the scenario in which task limitation is prohibited, and that is set according to the operation input by the user and meets the user's requirements or habits can be implemented. For example, the user may set, in the second list, a scenario that requires user attention as the scenario in which task limitation is prohibited, for example, a short message service message scenario, a call scenario, and a download scenario. Alternatively, the scenario in which task limitation is prohibited may be automatically set according to performance of a device. For example, when the device has better performance, for example, a CPU of the device is running at a high speed, the device has a larger memory, or the device has enough battery, more scenarios in which task limitation is prohibited may be set in the second list. For example, when the device has poor performance, for example, the CPU of the device is running at a low speed, the device has a smaller memory, or the device does not have enough battery, only a few scenarios in which task limitation is prohibited may be set in the second list.

Optionally, before the processor <NUM> performs the operation of performing limitation processing on the at least one background task corresponding to the first scenario, the processor <NUM> may be further configured to perform the following operations:.

In this implementation manner, because the background task whose UID corresponds to a common user is not a task of an operating system, other tasks are not affected after limitation processing is performed on these background tasks. Therefore, limitation processing is performed only on a background task whose UID corresponds to a common user in step <NUM>, which can reduce power consumption and power loss of the device without affecting other tasks.

In this case, the processor <NUM> may freeze the at least one background task corresponding to the first scenario, or stop the at least one background task corresponding to the first scenario, or limit a system resource used by the at least one background task corresponding to the first scenario.

Optionally, the operation, performed by the processor <NUM>, of determining, according to a foreground task, a first scenario corresponding to the foreground task may include:
when a temperature reaches a preset temperature threshold, determining, according to the foreground task, a first scenario corresponding to the foreground task.

Optionally, the processor <NUM> may be further configured to perform the following operations:
releasing the limitation processing on the at least one background task corresponding to the first scenario. Specifically, when the first scenario is not in the first list, the limitation processing is released for the background task that has undergone the limitation processing.

In the foregoing technical solutions, a first scenario corresponding to a foreground task is determined according to the foreground task, and when the first scenario corresponding to the foreground task is in a first list, at least one background task corresponding to the first scenario is searched for, where the first list includes a scenario in which task limitation is allowed; and limitation processing is performed on the at least one background task corresponding to the first scenario, where the limitation processing refers to processing for reducing system resource usage. In this way, limitation processing is implemented on at least one background task corresponding to a scenario in which task limitation is allowed. Compared with the prior art in which a background task is always being executed, this embodiment can reduce power consumption and power loss of a device.

Optionally, the processor <NUM> may specifically determine, when a current task is switched, a corresponding first scenario according to the current task. For example, when the current task, a music task, is being executed, the task enters a music scenario or a download scenario. In this way, it can be determined that the first scenario corresponding to the foreground task may be the music scenario, the download scenario, or the like. In addition, the foreground task may be one or multiple foreground tasks. In the case of multiple foreground tasks, the processor <NUM> may be configured to determine, according to multiple foreground tasks, a first scenario corresponding to each foreground task. That is, the processor <NUM> may determine, according to at least one foreground task, a first scenario corresponding to each foreground task.

Optionally, the at least one background task corresponding to the second scenario may refer to at least one background task in all background tasks corresponding to the second scenario, or the at least one background task corresponding to the second scenario may refer to all background tasks corresponding to the second scenario. In addition, the processor <NUM> may specifically search for at least two background tasks that are in the background tasks corresponding to the second scenario and that will not affect other tasks or an operating system after undergoing limitation processing; or search for at least one pre-determined background task in the background tasks corresponding to the second scenario; or search for at least one background task that is in the background tasks corresponding to the second scenario and whose UID corresponds to a common user. For example, the operation, performed by the processor <NUM>, of searching for at least one background task corresponding to the second scenario may include:
searching for a UID of each background task corresponding to the second scenario, and searching for a background task whose UID corresponds to a common user as the at least one background task corresponding to the second scenario.

That is, this step is used to implement that the at least one background task that is corresponding to the second scenario and is searched for by the processor <NUM> is the background task whose UID corresponds to a common user.

Optionally, the processor <NUM> may be further configured to perform the following operations:
ignoring a background task whose UID corresponds to a system user in the at least one background task corresponding to the second scenario. That is, processing is not performed on the background task whose UID corresponds to a system user.

Optionally, the processor <NUM> may search for at least one background task whose system resource usage reaches a preset threshold in the background tasks corresponding to the second scenario.

Optionally, before the processor <NUM> performs the operation of performing limitation processing on the at least one background task corresponding to the second scenario, the processor <NUM> may be further configured to perform the following operations:.

In this case, the processor <NUM> may freeze the at least one background task corresponding to the second scenario; stop the at least one background task corresponding to the second scenario; or limit a system resource used by the at least one background task corresponding to the second scenario.

Claim 1:
A task management method, comprising:
detecting (<NUM>), by the electronic device, that the electronic device enters a game scenario, a browser scenario, a navigation scenario or another audio playing or video playing scenario for which task limitation is allowed, wherein the game scenario, the browser scenario or the navigation scenario is a scenario that is set for receiving an operation input by a user that meets the user's requirements or habits;
querying and determining (<NUM>), by an electronic device, a background task that needs to be frozen, wherein the background task is a task corresponding to the game scenario, the browser scenario, the navigation scenario or another audio playing or video playing scenario;
determining (<NUM>), by the electronic device, whether the background task that needs to be frozen uses a system component, wherein freezing the background task means prohibiting the background task from calling a system resource or reducing usage of the system resource;
when determining the background task that needs to be frozen uses the system component, pausing (<NUM>), by the electronic device, the system component, wherein the system component used by the background task, comprises at least one of: a sleep lock, a timer or a broadcast notification;
freezing (<NUM>), by the electronic device, the background task.