JP6443813B2 - Task management method and task management device - Google Patents

Description

  This application is the priority of Chinese Patent Application No. 201310665434.9 entitled “TASK MANAGEMENT METHOD AND DEVICE” filed with the Chinese Patent Office on December 10, 2013, which is incorporated herein by reference in its entirety. Is an insistence.

  The present invention relates to the communication field, and in particular, to a task management method and a task management device.

  With the development of communication technology, many devices now support multitasking systems. That is, the device can run multiple application programs simultaneously, and an application program can have one or more threads, each called a task. The multiple tasks typically include a foreground task and a background task. A foreground task is a task that requires user interaction. That is, it is necessary to receive an operation input by the user when executing the foreground task. Background tasks are tasks that do not require user interaction. That is, it is not necessary to receive an operation input by the user when the background task is executed. Since background tasks do not require user interaction, background tasks are generally not user-sensitive tasks, or background tasks are not user related. In other words, some background tasks do not need to be executed. However, background tasks are frequently executed in the background of the system and consume device power constantly. At present, it can be seen that devices can suffer significant power consumption and power loss.

  Embodiments of the present invention provide a task management method and a task management device in order to reduce power consumption and power loss of the device.

According to a first aspect, an embodiment of the present invention provides a task management method, the method comprising:
Determining a first scenario corresponding to the foreground task according to the foreground task;
Exploring at least one background task corresponding to the first scenario when the first scenario corresponding to the foreground task is in the first list, the first list being allowed to be task restricted Exploring at least one background task, including
A step of performing restriction processing on at least one background task corresponding to the first scenario, and the restriction processing includes a step of performing restriction processing, which is processing for reducing system resource use.

In a first possible embodiment of the first aspect, the method comprises:
Searching for a second scenario other than the first scenario corresponding to the foreground task, wherein the second scenario corresponds to at least one background task and the first list includes the second scenario; Exploring a second scenario;
And a restriction process for at least one background task corresponding to the second scenario.

In relation to the first aspect or the first possible embodiment of the first aspect, in the second possible embodiment of the first aspect, according to the foreground task, the first scenario corresponding to the foreground task is After the step of determining, the method
The method further includes determining whether the first scenario is on the first list.

In relation to the first aspect, in the third possible embodiment of the first aspect, prior to performing the restriction process on at least one background task corresponding to the first scenario, the method comprises:
Querying the user identifier of at least one background task;
Ignoring at least one background task if the user identifier of the at least one background task corresponds to a system user;
Performing a restriction process on at least one background task when the user identifier of the at least one background task corresponds to a general user.

In relation to the first aspect, in the fourth possible embodiment of the first aspect, prior to performing the restriction process on at least one background task corresponding to the first scenario, the method comprises:
Starting a timer for at least one background task corresponding to the first scenario;
Stopping the system component used by at least one background task corresponding to the first scenario when the timer exceeds a preset threshold.

In connection with the first aspect, in a fifth possible embodiment of the first aspect, prior to performing the restriction process on at least one background task corresponding to the first scenario, the method comprises:
Querying whether at least one background task uses the system component; and
And stopping the system component when at least one background task uses the system component.

First aspect, first possible embodiment of the first aspect, second possible embodiment of the first aspect, third possible embodiment of the first aspect, first of the first aspect In connection with the four possible implementations, or the fifth possible implementation of the first aspect, in the sixth possible implementation of the first aspect, the process for reducing system resource usage comprises:
Freezing at least one background task;
Stop at least one background task,
Including at least one of: limiting system resources used by at least one background task.

First aspect, first possible embodiment of the first aspect, second possible embodiment of the first aspect, third possible embodiment of the first aspect, first of the first aspect In relation to the four possible embodiments, or the fifth possible embodiment of the first aspect, in the seventh possible embodiment of the first aspect, the first corresponding to the foreground task according to the foreground task The steps to determine the scenario for
Determining a first scenario corresponding to each foreground task according to at least one foreground task.

According to a second aspect, an embodiment of the present invention provides a task management method, the method comprising:
Determining a first scenario corresponding to the foreground task according to the foreground task;
Determining a second scenario other than the first scenario corresponding to the foreground task, wherein the second scenario is a scenario in which task restriction is allowed, and the second scenario is at least one background task Determining a corresponding second scenario;
Searching for at least one background task corresponding to the second scenario;
A step of performing restriction processing on at least one background task corresponding to the second scenario, and the restriction processing includes a step of performing restriction processing, which is processing for reducing system resource use.

In a first possible embodiment of the second aspect, the method comprises
Searching for at least one background task corresponding to the first scenario;
Performing a restriction process on at least one background task corresponding to the first scenario when the user identifier of at least one background task corresponding to the first scenario corresponds to a general user.

In relation to the second aspect, in the second possible embodiment of the second aspect, prior to performing the restriction process on at least one background task corresponding to the second scenario, the method comprises:
Starting a timer for at least one background task corresponding to the second scenario;
Stopping the system component used by at least one background task corresponding to the second scenario when the timer exceeds a preset threshold.

In relation to the second aspect, in the third possible embodiment of the second aspect, prior to performing the restriction process on at least one background task corresponding to the second scenario, the method comprises:
Querying whether at least one background task uses the system component; and
And stopping the system component when at least one background task uses the system component.

In relation to the second aspect, the first possible embodiment of the second aspect, the second possible embodiment of the second aspect, or the third possible embodiment of the second aspect, In a fourth possible embodiment of the two aspects, the process for reducing system resource usage is:
Freezing at least one background task;
Stop at least one background task,
Including at least one of: limiting system resources used by at least one background task.

In relation to the second aspect, the first possible embodiment of the second aspect, the second possible embodiment of the second aspect, or the third possible embodiment of the second aspect, In a fifth possible embodiment of the two aspects, according to the foreground task, determining the first scenario corresponding to the foreground task comprises:
Determining a first scenario corresponding to each foreground task according to at least one foreground task.

According to a third aspect, an embodiment of the present invention provides a task management method, the method includes a determination unit, a first search unit, and a first processing unit,
The determining unit is configured to determine a first scenario corresponding to the foreground task according to the foreground task.
The first search unit corresponds to the foreground task and searches for at least one background task corresponding to the first scenario when the first scenario determined by the determination unit is in the first list. The first list contains scenarios where task limits are allowed,
The first processing unit corresponds to the first scenario, and is configured to perform a limiting process on at least one background task searched by the first searching unit. The limiting process reduces system resource usage. This is the process for making it happen.

In a first possible embodiment of the third aspect, the device comprises
A second search unit corresponding to the foreground task and configured to search for a second scenario other than the first scenario searched by the determination unit, wherein the second scenario is at least one background task A first search list includes a second scenario, a second search unit, and
A second processing unit corresponding to the second scenario and configured to perform a restriction process on at least one background task searched by the second search unit.

In relation to the third aspect or the first possible embodiment of the third aspect, in a second possible embodiment of the third aspect, the device comprises:
A decision unit configured to determine whether the first scenario is on the first list;

In relation to the third aspect, in a third possible embodiment of the third aspect, the device comprises:
A first query unit configured to query a user identifier of at least one background task;
And an ignoring portion configured to ignore at least one background task when the user identifier queried by the first query portion corresponds to a system user and is of at least one background task. ,
The first processing unit is for at least one background task, and when the user identifier inquired by the first inquiry unit corresponds to a general user, the restriction processing for at least one background task is performed. It is configured.

In relation to the third aspect, in a fourth possible embodiment of the third aspect, the device comprises:
A timing portion configured to start a timer for at least one background task corresponding to the first scenario;
A first stop configured to stop a system component used by at least one background task corresponding to the first scenario when the timer exceeds a preset threshold.

In relation to the third aspect, in a fifth possible embodiment of the third aspect, the device comprises:
A second query unit configured to query whether at least one background task uses the system component;
And a second inquiry unit configured to stop the system component when the second inquiry unit confirms that at least one background task uses the system component.

3rd aspect, 1st possible embodiment of the 3rd aspect, 2nd possible embodiment of the 3rd aspect, 3rd possible embodiment of the 3rd aspect, 3rd aspect of the 3rd aspect In connection with the four possible implementations, or the fifth possible implementation of the third aspect, in the sixth possible implementation of the third aspect, the process for reducing system resource usage comprises:
Freezing at least one background task;
Stop at least one background task,
Including at least one of: limiting system resources used by at least one background task.

  3rd aspect, 1st possible embodiment of the 3rd aspect, 2nd possible embodiment of the 3rd aspect, 3rd possible embodiment of the 3rd aspect, 3rd aspect of the 3rd aspect In connection with the four possible embodiments, or the fifth possible embodiment of the third aspect, in the seventh possible embodiment of the third aspect, the determining unit is in accordance with at least one foreground task, It is configured to determine a first scenario corresponding to each foreground task.

According to the second aspect, one embodiment of the present invention provides a task management method, the method comprising: a first determination unit; a second determination unit; a first search unit; a first search unit; Including a processing unit,
The first determination unit is configured to determine a first scenario corresponding to the foreground task according to the foreground task,
The second determination unit corresponds to the foreground task, and is configured to determine a second scenario other than the first scenario determined by the first determination unit. Allowed scenario, the second scenario corresponds to at least one background task,
The first search unit is configured to search for at least one background task corresponding to the second scenario determined by the second determination unit;
The first processing unit is configured to perform restriction processing for at least one background task searched for by the first search unit, corresponding to the second scenario, and the restriction processing reduces system resource usage. This is the process for making it happen.

In a first possible embodiment of the second aspect, the device comprises:
A second search unit configured to search for at least one background task corresponding to the first scenario;
A second configured to perform a restriction process on at least one background task corresponding to the first scenario when a user identifier of at least one background task corresponding to the first scenario corresponds to a general user; And a processing unit.

In relation to the second aspect, in a second possible embodiment of the second aspect, the device comprises:
A timing unit configured to start a timer for at least one background task corresponding to the second scenario;
A first stop configured to stop a system component used by at least one background task corresponding to the second scenario when the timer exceeds a preset threshold.

In relation to the second aspect, in a third possible embodiment of the second aspect, the device comprises:
An inquiry unit configured to inquire whether at least one background task uses the system component;
And a second stopping unit configured to stop the system component when the inquiry unit confirms that at least one background task uses the system component.

In relation to the second aspect, the first possible embodiment of the second aspect, the second possible embodiment of the second aspect, or the third possible embodiment of the second aspect, In a fourth possible embodiment of the two aspects, the process for reducing system resource usage is:
Freezing at least one background task;
Stop at least one background task,
Including at least one of: limiting system resources used by at least one background task.

  In relation to the second aspect, the first possible embodiment of the second aspect, the second possible embodiment of the second aspect, or the third possible embodiment of the second aspect, In a fifth possible implementation of the two aspects, the determining unit is configured to determine a first scenario corresponding to each foreground task according to at least one foreground task.

  In the above technical solution, the first scenario corresponding to the foreground task is determined according to the foreground task, and the first scenario corresponding to the foreground task is in the first list, it corresponds to the first scenario At least one background task is searched, the first list includes scenarios where task restrictions are allowed, and the restriction process is performed on at least one background task corresponding to the first scenario, and the restriction process Is a process for reducing the use of system resources. In this manner, the restriction process is performed on at least one background task corresponding to a scenario in which task restriction is permitted. Compared to the prior art where background tasks are always executed, embodiments of the present invention can reduce device power consumption and power loss.

  To describe the technical solutions in the embodiments of the present invention or in the prior art more clearly, the following briefly describes the accompanying drawings required for describing the embodiments or the prior art. . Apparently, the accompanying drawings in the following description merely show some embodiments of the present invention, and those skilled in the art can further derive other drawings from these accompanying drawings without difficulty.

3 is a schematic flowchart of a task management method according to an embodiment of the present invention; 6 is a schematic flowchart of another task management method according to an embodiment of the present invention; 6 is a schematic flowchart of another task management method according to an embodiment of the present invention; 6 is a schematic flowchart of another task management method according to an embodiment of the present invention; 6 is a schematic flowchart of another task management method according to an embodiment of the present invention; 6 is a schematic flowchart of another task management method according to an embodiment of the present invention; 6 is a schematic flowchart of another task management method according to an embodiment of the present invention; 1 is a schematic diagram of a structure of a task management device according to an embodiment of the present invention. FIG. FIG. 6 is a schematic diagram of another task management device structure according to an embodiment of the present invention; FIG. 6 is a schematic diagram of another task management device structure according to an embodiment of the present invention; FIG. 6 is a schematic diagram of another task management device structure according to an embodiment of the present invention; FIG. 6 is a schematic diagram of another task management device structure according to an embodiment of the present invention; FIG. 6 is a schematic diagram of another task management device structure according to an embodiment of the present invention; FIG. 6 is a schematic diagram of another task management device structure according to an embodiment of the present invention; FIG. 6 is a schematic diagram of another task management device structure according to an embodiment of the present invention; FIG. 6 is a schematic diagram of another task management device structure according to an embodiment of the present invention; FIG. 6 is a schematic diagram of another task management device structure according to an embodiment of the present invention; FIG. 6 is a schematic diagram of another task management device structure according to an embodiment of the present invention; FIG. 6 is a schematic diagram of another task management device structure according to an embodiment of the present invention;

  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. Apparently, the described embodiments are merely a part rather than all of the embodiments of the present invention. All other embodiments obtained by persons of ordinary skill in the art based on the embodiments of the present invention without difficulty will fall within the protection scope of the present invention.

  In the embodiment of the present invention, the first scenario and the second scenario are not limited to two scenarios. The first scenario can indicate one or more scenarios, and the second scenario can also indicate one or more scenarios. For example, the first scenario may be a scenario corresponding to a foreground task, and one or more foreground tasks may occur simultaneously. That is, the first scenario can be one or more scenarios. The second scenario can be any one or more scenarios other than the first scenario. For example, the second scenario can be a scenario corresponding to a task other than the foreground task. In this case, the first and second are only named to distinguish two different scenarios.

  In addition, in an embodiment of the present invention, a scenario can refer to the state of operation of a device implementing the embodiment of the present invention. The operation status of the device may refer to a status in which the device uses system resources. Specifically, system resources can be hardware resources such as CPU resources and memory resources, and system resources can be specifically virtual resources such as network bandwidth resources and operating system resources. This is not limited in the embodiment of the present invention. Scenarios include making a call, sending a short message service message, using a browser, playing a 2D / 3D game, viewing the main user interface, downloading a file, Reading ebooks, playing music, watching videos, navigating websites, browsing photos, taking photos, creating videos, sending emails, etc. It can be.

  In addition, in the embodiment of the present invention, the scenario corresponding to the task can be specifically a scenario in which the task is entered when the task is executed. For example, when a music task is running, this task enters a music scenario and a download scenario. That is, the scenario corresponding to the music task can include a music scenario and a download scenario. In addition, the task corresponding to the scenario can be specifically a task entering the scenario. For example, when a music task is running, this task enters a download scenario. When the browser task is running, this task also enters the download scenario. When a software update task is being executed, this task also enters the download scenario. As such, tasks corresponding to the download scenario can include a music task, a browser task, and a software update task. That is, one scenario corresponds to different tasks.

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

  Referring to FIG. 1, FIG. 1 is a schematic flowchart of a task management method according to an embodiment of the present invention. As shown in FIG. 1, the method includes the following steps.

  101. According to the foreground task, a first scenario corresponding to the foreground task is determined.

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

  102. When the first scenario corresponding to the foreground task is in the first list, search for at least one background task corresponding to the first scenario. The first list includes scenarios where task restrictions are allowed.

  Optionally, the scenario where task restrictions are allowed and included in the first list may be a scenario configured to receive an operation entered by the user. As described above, it is possible to realize a scenario in which task restriction is permitted, which is set according to an operation input by the user and conforms to the user's requirements or habits. For example, the user wants to reduce the power consumption of the device, and the user can set multiple scenarios where task restrictions are allowed in the first list, e.g. browser scenarios as scenarios where task restrictions are allowed Set game scenario, navigation scenario, etc. Thus, step 102 can be performed to reduce power consumption of the device when the first scenario corresponding to the current task is a browser scenario, a game scenario, or a navigation scenario.

  Optionally, task restrictions are allowed and the scenarios included in the first list can also be set automatically according to device performance. For example, when a device has excellent performance, for example, when the device's CPU is running at high speed, the device has a large amount of memory, or the device has enough battery, task limits in the first list Only a few scenarios can be set up that are allowed. For example, when the device has insufficient performance, for example, when the device's CPU is running at low speed, the device has a small amount of memory, or the device does not have enough batteries, in the first list A number of scenarios where task restrictions are allowed can be set. The first list has a large number of scenarios where task limits are allowed, and steps 102 and 103 are performed multiple times, so that multiple devices are used to reduce device power consumption and ensure stable operation of the device. Limit processing can be performed for background tasks.

  Optionally, at least one background task corresponding to the first scenario can also refer to at least one background task in all background tasks corresponding to the first scenario, The corresponding at least one background task can also refer to all background tasks corresponding to the first scenario. In the present embodiment, no limit is set for this.

  103. Limit processing is performed on at least one background task corresponding to the first scenario. The restriction process refers to a process for reducing system resource usage.

  Optionally, the limiting process can be a process to reduce system resources currently used by the task. For example, the amount of system resources used by background task A is A when step 101 is performed, and the system used by background task A after restriction processing is performed for background task A The quantity of resources is B, and A is larger than B. In addition, B can be zero.

  Optionally, the method specifically has a tablet computer, mobile phone, electronic reader, remote control, personal computer (PC), notebook computer, in-car device, web TV, wearable device, or network function. It can be applied to any device having a multitasking system, such as other intelligent devices.

  In the above technical solution, the first scenario corresponding to the foreground task is determined according to the foreground task, and the first scenario corresponding to the foreground task is in the first list, it corresponds to the first scenario At least one background task is searched, the first list includes scenarios where task restrictions are allowed, and the restriction process is performed on at least one background task corresponding to the first scenario, and the restriction process Is a process for reducing the use of system resources. In this manner, the restriction process is performed on at least one background task corresponding to a scenario in which task restriction is permitted. Compared to the prior art where background tasks are always executed, this embodiment of the present invention can reduce the power consumption and power loss of the device.

  Referring to FIG. 2, FIG. 2 is a schematic flowchart of another task management method according to an embodiment of the present invention. As shown in FIG. 2, the method includes the following steps.

  201. According to the foreground task, a first scenario corresponding to the foreground task is determined.

  202. Determine if the first scenario is in the first list. If yes, step 203 is performed. If no, end the process. The first list includes scenarios where task restrictions are allowed.

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

Optionally, step 203 specifically includes at least one background within the background task corresponding to the first scenario that will not affect other tasks or the operating system after undergoing restriction processing. It can also be a step to search for a task, and can also be a step to search for at least one predetermined background task in a background task corresponding to the first scenario, and a background corresponding to the first scenario It may be a step of searching for at least one background task in the task whose user identifier corresponds to a general user. For example, step 203 is
Search for the user identifier of each background task corresponding to the first scenario, and at least one background task corresponding to the first scenario, the background whose user identifier (UID) corresponds to a general user A step of searching for tasks may be included.

  That is, this step corresponds to the first scenario and is used to realize that at least one background task searched in step 203 is a background task whose UID corresponds to a general user. . The UID is a unique identifier of each task and is used to uniquely identify the task. In addition, the UID can correspond to system users and general users. When the background task UID corresponds to a system user, this indicates that the background task is a background task included in the operating system. When the background task UID corresponds to a regular user, this indicates that the background task is not a background task included in the operating system.

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

  Optionally, step 203 may be a step of searching for at least one background task in the background task corresponding to the first scenario whose system resource usage reaches a preset threshold. For example, searching for at least one background task in the background task corresponding to the first scenario whose CPU resource usage reaches 10% of the CPU resource, or the background task corresponding to the first scenario Search for at least one background task whose sleep lock retention period reaches 10 minutes, or the average data download speed within the background task corresponding to the first scenario reaches 10M / min Exploring at least one background task.

  204. Limit processing is performed on at least one background task corresponding to the first scenario. The restriction process refers to a process for reducing system resource usage.

  Optionally, as shown in FIG. 3, the method can further include:

  205. Search for a second scenario other than the first scenario corresponding to the foreground task. The second scenario corresponds to at least one background task, and the first list includes the second scenario.

  206. Limit processing for at least one background task corresponding to the second scenario is performed.

  Optionally, the second scenario can also refer to one or more scenarios. In addition, the second scenario can also refer to all scenarios other than the first scenario, and can also refer to one or a plurality of scenarios other than the first scenario, which is not limited in the present embodiment. .

  In addition, at least one background task corresponding to the second scenario can also refer to at least one background task in all background tasks corresponding to the second scenario, corresponding to the second scenario The at least one background task can also refer to all background tasks corresponding to the second scenario. In the present embodiment, no limit is set for this. In addition, the second scenario may specifically be a predetermined scenario, for example, a scenario set to receive an operation input by the user. As described above, it is possible to realize a scenario in which task restriction is permitted, which is set according to an operation input by the user and conforms to the user's requirements or habits. In addition, step 205 specifically includes at least one background task in the background task corresponding to the second scenario that will not affect other tasks or the operating system after undergoing the restriction process. Can also be a step of searching for at least one predetermined background task in the background task corresponding to the second scenario, and can also be a step of searching for the background task corresponding to the second scenario. And searching for at least one background task whose user identifier corresponds to a general user.

  Optionally, the second scenario may be a scenario that is not in the second list other than the first scenario, and the second list may include scenarios where task restrictions are prohibited. The scenario in which task restriction is prohibited can be a scenario set to receive an operation input by a user. As described above, it is possible to realize a scenario in which task restriction is prohibited, which is set according to an operation input by the user and meets the user's requirements or habits. For example, in the second list, the user may set a scenario that requires the user's attention as a scenario in which task restriction is prohibited, such as a short message service message scenario, a telephone scenario, and a download scenario. it can. Alternatively, a scenario in which task restriction is prohibited can be automatically set according to device performance. For example, when the device has excellent performance, for example, when the device's CPU is running at high speed, the device has a large amount of memory, or the device has enough battery, task limits in the second list There are a number of scenarios that can be prohibited. For example, when the device has insufficient performance, for example, when the device's CPU is running at low speed, the device has a small amount of memory, or the device does not have enough batteries, in the second list There can be very few scenarios where task restrictions are prohibited.

Optionally, prior to step 204, the method includes:
Querying the UID of at least one background task corresponding to the first scenario;
Ignoring at least one background task if the UID of the at least one background task corresponding to the first scenario corresponds to a system user;
Performing a restriction process on the at least one background task when the UID of the at least one background task corresponds to a general user. In other words, step 204 performs a restriction process on at least one background task whose UID corresponds to a general user.

  In this embodiment, since the background task whose UID corresponds to the general user is not an operating system task, other tasks are not affected after the general user restriction process is performed on the background task. Therefore, in step 204, the restriction process is performed only for the background task whose UID corresponds to the general user, thereby reducing the power consumption and power loss of the device without affecting other tasks. Can do.

Optionally, prior to step 204, the method includes:
Starting a timer for at least one background task corresponding to the first scenario;
Stopping a system component used by at least one background task corresponding to the first scenario when the timer exceeds a preset threshold.

  Optionally, system components include, but are not limited to, timers, sleep locks, and broadcast notifications. At the same time, the above steps can save the status value of the system component when the system component is paused, so that after the restriction process is released, the background task will save the saved status of the system component A value can be called. In addition, the system component used by at least one background task corresponding to the first scenario is stopped only when the timer reaches a preset threshold (eg, 10 seconds, 30 seconds, etc.). As a result, frequent stopping of system components used by at least one background task corresponding to the first scenario can be avoided.

Optionally, prior to step 204, the method includes:
Querying whether at least one background task corresponding to the first scenario uses a system component;
Stopping the first scenario when at least one background task corresponding to the first scenario uses the system component.

  In this embodiment, the power consumption and power loss of the device can also be reduced because the system components used by at least one background task corresponding to the first scenario are stopped.

Optionally, processing to reduce system resource usage is:
Freezing at least one background task;
Stop at least one background task,
It can also include at least one of ways to limit system resources used by at least one background task.

  In this case, step 204 includes freezing at least one background task corresponding to the first scenario, or stopping at least one background task corresponding to the first scenario, or to the first scenario. And limiting system resources used by the corresponding at least one background task.

  Optionally, freezing at least one background task corresponding to the first scenario is prohibiting the background task from invoking system resources, e.g., the CPU is at least corresponding to the first scenario It can be a step that prohibits calling one background task. Specifically, the operating system's task scheduler is used to prohibit at least one background task corresponding to the first scenario from participating in any scheduling. Since at least one background task corresponding to the first scenario is prohibited from calling system resources, the power consumption of the device is reduced.

  Optionally, limiting the system resources used by at least one background task corresponding to the first scenario causes the CPU to call at least one background task corresponding to the first scenario within that time And a step of limiting time. For example, at least one background task corresponding to the first scenario so that the CPU can call at least one background task corresponding to the first scenario within the time indicated by the time value of the CPU call A time value is set for In addition, the step of limiting system resources used by at least one background task corresponding to the first scenario further limits the use of system resources by at least one background task corresponding to the first scenario. It can also be a step. For example, limiting network bandwidth usage by at least one background task corresponding to the first scenario, or limiting memory space usage by at least one background task corresponding to the first scenario . In addition, this step can further be a step of using different restriction measures depending on different scenarios corresponding to at least one background task corresponding to the first scenario. The aforementioned steps reduce device power consumption because the use of system resources by at least one background task corresponding to the first scenario is limited.

Optionally, step 201 is
The method may further include determining a first scenario corresponding to the foreground task according to the foreground task when the temperature reaches a preset temperature threshold.

  The temperature may be the temperature of the device that implements the present embodiment, and the device temperature may specifically be the temperature of the device CPU or the temperature of the device modem.

  In this embodiment, it is possible to realize that the limit process is performed on the background task only when the temperature of the device reaches the preset temperature threshold.

Optionally, the method includes
The method may further include a step of releasing restriction processing for at least one background task corresponding to the first scenario. Specifically, when the first scenario is not in the first list, the restriction process is canceled for the background task that has undergone the restriction process.

  Optionally, the method specifically includes multiple computers such as tablet computers, mobile phones, electronic readers, remote controls, PCs, notebook computers, in-car devices, web TVs, wearable devices, or other intelligent devices with network capabilities. It can be applied to any device having a task system.

  In the above technical solution, a plurality of optional implementations are realized based on the first embodiment, and all of these implementations can reduce the power consumption and power loss of the device.

  Referring to FIG. 4, FIG. 4 is a schematic flowchart of another task management method according to an embodiment of the present invention. As shown in FIG. 4, the method includes the following steps.

  401. According to the foreground task, a first scenario corresponding to the foreground task is determined.

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

  402. A second scenario other than the first scenario corresponding to the foreground task is determined. The second scenario is a scenario in which task restriction is permitted, and the second scenario corresponds to at least one background task.

  Optionally, the second scenario can also refer to one or more scenarios. In addition, the second scenario can also refer to all scenarios other than the first scenario, and can also refer to one or a plurality of scenarios other than the first scenario, which is not limited in the present embodiment. . In addition, the second scenario may specifically be a predetermined scenario, for example, a scenario set to receive an operation input by the user. As described above, it is possible to realize a scenario in which task restriction is permitted, which is set according to an operation input by the user and conforms to the user's requirements or habits.

  Optionally, the second scenario may be a scenario that is not in the second list other than the first scenario, and the second list may include scenarios where task restrictions are prohibited.

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

Optionally, at least one background task corresponding to the second scenario can also refer to at least one background task in all background tasks corresponding to the second scenario, The corresponding at least one background task can also refer to all background tasks corresponding to the second scenario. In addition, step 403 specifically includes at least two background tasks within the background task corresponding to the second scenario that will not affect other tasks or the operating system after undergoing restriction processing. Search for at least one predetermined background task in the background task corresponding to the second scenario, or the UID in the background task corresponding to the second scenario is It is also possible to search for at least one background task corresponding to a general user. For example, step 403
Searching for a UID of each background task corresponding to the second scenario, and searching for a background task corresponding to the general user as at least one background task corresponding to the second scenario; , Can be included.

  That is, this step corresponds to the second scenario and is used to realize that at least one background task searched in step 403 is a background task whose UID corresponds to a general user. .

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

  Optionally, step 403 may be a step of searching for at least one background task whose system resource usage reaches a preset threshold in the background task corresponding to the second scenario.

  404. Limit processing for at least one background task corresponding to the second scenario is performed. The restriction process refers to a process for reducing system resource usage.

  Optionally, as shown in FIG. 5, the method can further include:

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

  406. When the UID of at least one background task corresponding to the first scenario corresponds to a general user, a restriction process is performed on at least one background task corresponding to the first scenario.

  For this embodiment of the present embodiment, further refer to the embodiment in which the restriction process is performed on at least one background task corresponding to the first scenario in the first embodiment and the second embodiment. .

Optionally, prior to step 404, the method
Starting a timer for at least one background task corresponding to the second scenario;
Stopping a system component used by at least one background task corresponding to the second scenario when the timer exceeds a preset threshold.

  Optionally, system components include, but are not limited to, timers, sleep locks, and broadcast notifications. At the same time, the above steps can save the status value of the system component when the system component is paused, so that after the restriction process is released, the background task will save the saved status of the system component A value can be called. In addition, the system component used by at least one background task corresponding to the second scenario is stopped only when the timer reaches a preset threshold (eg, 10 seconds, 30 seconds, etc.). Thereby, frequent stopping of the system components used by at least one background task corresponding to the second scenario can be avoided.

Optionally, prior to step 404, the method
Querying whether at least one background task uses the system component; and
And stopping the system component when at least one background task uses the system component.

  In this embodiment, system components used by at least one background task corresponding to the second scenario are stopped, so that power consumption and power loss of the device can be reduced.

Optionally, processing to reduce system resource usage is:
Freezing at least one background task;
Stop at least one background task,
Including at least one of: limiting system resources used by at least one background task.

In this case, step 404 freezes at least one background task corresponding to the second scenario,
Stopping at least one background task corresponding to the second scenario, or limiting system resources used by at least one background task corresponding to the second scenario.

  Optionally, freezing at least one background task corresponding to the second scenario is to prohibit the background task from invoking system resources, e.g., the CPU is at least corresponding to the first scenario It can be a step that prohibits calling one background task. Specifically, the operating system's task scheduler is used to prohibit at least one background task corresponding to the first scenario from participating in any scheduling. Since at least one background task corresponding to the second scenario is prohibited from calling system resources, the power consumption of the device is reduced.

  Optionally, limiting the system resources used by at least one background task corresponding to the second scenario causes the CPU to call at least one background task corresponding to the second scenario within that time It can also be a step of limiting time. For example, at least one time value corresponding to the second scenario so that the CPU can call at least one background task corresponding to the second scenario within the time indicated by the time value of the CPU call Set for background tasks. In addition, the step of limiting system resources used by at least one background task corresponding to the second scenario further limits the use of system resources by at least one background task corresponding to the second scenario It can also be a step. For example, limiting network bandwidth usage by at least one background task corresponding to the second scenario, or limiting memory space usage by at least one background task corresponding to the second scenario . In addition, this step can further be a step of using different restriction measures depending on different scenarios corresponding to at least one background task corresponding to the second scenario. The aforementioned steps limit the use of system resources by at least one background task corresponding to the second scenario, thus reducing the power consumption of the device.

  Optionally, the method specifically includes multiple computers such as tablet computers, mobile phones, electronic readers, remote controls, PCs, notebook computers, in-car devices, web TVs, wearable devices, or other intelligent devices with network capabilities. It can be applied to any device having a task system.

  In the above technical solution, the first scenario corresponding to the foreground task is determined according to the foreground task, the second scenario other than the first scenario corresponding to the foreground task is determined, and the second scenario is a task. A scenario where restrictions are allowed, the second scenario corresponds to at least one background task, and at least one background task corresponding to the second scenario is searched and at least one corresponding to the second scenario Restriction processing is performed for one background task, and the restriction processing is processing for reducing the use of system resources. Therefore, power consumption and power loss of the device can be reduced.

  Referring to FIG. 6, FIG. 6 is a schematic flowchart of a task management method according to an embodiment of the present invention. As shown in FIG. 6, the method includes the following steps.

  601. It is determined whether the currently switched scenario is a scenario included in the white list. If yes, step 602 is performed. If no, end the process. The white list is a pre-configured list that includes at least one scenario where background task restrictions are allowed.

  Optionally, the aforementioned scenario may specifically be a situation of operation of the device performing step 601. The operation status of the device may refer to a status in which the device uses system resources. The system resource can specifically be a hardware resource such as a CPU resource or a memory resource, and the system resource can be a virtual resource such as a network bandwidth resource or an operating system resource. This is not limited in the embodiments of the present invention. Scenarios include making a call, sending a short message service message, using a browser, playing a 2D / 3D game, viewing the main user interface, downloading a file, Reading ebooks, playing music, watching videos, navigating websites, browsing photos, taking photos, creating videos, sending emails, etc. It can be. In addition, the currently switched scenario may be one or more scenarios. In addition, the scenario switching can be specifically a switching that occurs depending on the switching time of the foreground task. For example, when a foreground task is started, it is switched to one or more scenarios. For example, when the task of making a phone call is initiated, the device switches to a phone call scenario, when the music task is initiated, the device switches to a music playback scenario and a music download scenario, and the game task is When 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 restrictions are allowed can also be a scenario that is set up to receive operations entered by the user. As described above, it is possible to realize a scenario in which background task restriction is permitted, which is set according to an operation input by the user and conforms to the user's requirements or habits. For example, the user wants to reduce the power consumption of the device, and the user can set multiple scenarios in the whitelist where background task limits are allowed, eg background task limits are allowed Browser scenario, game scenario, navigation scenario, etc. are set as scenarios. Thus, step 602 can be performed to reduce the power consumption of the device when the current scenario of the device is a browser scenario, a game scenario, or a navigation scenario.

  Optionally, scenarios where background task restrictions are allowed can also be set automatically according to device performance. For example, when the device has excellent performance, for example, when the device's CPU is running at high speed, the device has a large amount of memory, or the device has enough batteries, the background task limits in the whitelist Only a few scenarios can be set up that are allowed. For example, when the device has insufficient performance, for example when the device's CPU is running at low speed, the device has a small amount of memory, or the device does not have enough batteries, A number of scenarios where task restrictions are allowed can be set. The whitelist has a large number of scenarios where background task limits are allowed, and step 602 and step 603 are performed multiple times, so the limit process is performed to reduce device power consumption and ensure stable device operation. Restriction processing can be performed for multiple background tasks that allow

  602. When it is determined that the currently switched scenario is a scenario included in the white list, a background task that permits the restriction process in the currently running background task is searched. The restriction process refers to a process for reducing system resource usage.

  Optionally, the background task that allows the restriction process can be a background task that does not affect other tasks or the operating system (such as the foreground task) after receiving the restriction process. Specifically, the background task that permits the restriction process can also be a predetermined background task, and the background task that permits the restriction process is specifically a background task that satisfies a specific condition. You can also

  Optionally, the restriction process may specifically be an operation used to reduce system resources currently used by the task. For example, the amount of system resources used by background task A is A when step 101 is performed, and the system used by background task A after restriction processing is performed for background task A The quantity of resources is B, and A is larger than B. In addition, B can be zero.

  603. Restriction processing is performed for background tasks that allow restriction processing.

  Optionally, the method specifically includes multiple computers such as tablet computers, mobile phones, electronic readers, remote controls, PCs, notebook computers, in-car devices, web TVs, wearable devices, or other intelligent devices with network capabilities. It can be applied to any device having a task system.

  It should be noted that the scenario of this embodiment can be equal to the scenario of the previous embodiment. In addition, the white list of this embodiment may be the first list of the above-described embodiment.

  In the above technical solution, it is determined whether the currently switched scenario is whitelisted or a scenario, and the whitelist is preconfigured with at least one scenario that allows background task restrictions. When it is determined that the currently switched scenario is included in the whitelist, the background task that allows the restriction process is searched for in the background task that is currently running, and the restriction process is performed by the system. This is a process for reducing resource usage, and a restriction process is performed for a background task that permits the restriction process. In this way, the restriction process is performed on the background task that permits the restriction process. Compared to the prior art where background tasks are always executed, this embodiment of the present invention can reduce the power consumption and power loss of the device.

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

  701. Detect that the device enters a game scenario, browser scenario, or navigation scenario. Game scenarios, browser scenarios, or navigation scenarios are merely examples, and this embodiment includes, but is not limited to, these scenarios can also include, for example, audio playback or video playback scenarios.

  702. Query and determine background tasks that need to be frozen.

  703. Determine whether background tasks that need to be frozen use system components. If yes, step 704 is performed. If “no”, step 705 is performed. Step 703 determines whether a background task that needs to be frozen uses a sleep lock, and / or determines whether a background task that needs to be frozen uses a timer, and / or Or, determining whether a background task that needs to be frozen uses broadcast notifications.

  704. Halt system components. Step 704 pauses the sleep lock if the background task that needs to be frozen uses sleep lock, pauses the timer if the background task that needs to be frozen uses the timer Suspending broadcast notification when a background task that needs to be frozen uses broadcast notification.

  705. Freeze background tasks that need to be frozen.

  The task management method may further include:

  706. Detect that the device switches to the main user interface scenario.

  707. Queries frozen background tasks.

  708. Resume system components for frozen background tasks. Step 708 can include resuming sleep lock, resuming a timer, and resuming broadcast notification.

  709. Unfreeze background tasks that are frozen.

  The apparatus embodiment of the present invention will be described below. The apparatus embodiments of the present invention are used to perform the methods implemented in the first to fifth embodiments of the present invention. For ease of explanation, only the parts related to the embodiment of the present invention will be described below. For specific technical 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. 8, FIG. 8 is a schematic diagram of the structure of a task management device according to an embodiment of the present invention. As shown in FIG. 8, the task management device includes a determination unit 81, a first search unit 82, and a first processing unit 83.

  The determining unit 81 is configured to determine a first scenario corresponding to the foreground task according to the foreground task.

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

  The first search unit 82 corresponds to the foreground task, and searches for at least one background task corresponding to the first scenario when the first scenario determined by the determination unit 81 is in the first list. The first list includes scenarios where task restrictions are allowed.

  Optionally, the scenario where task restrictions are allowed and included in the first list may be a scenario configured to receive an operation entered by the user. As described above, it is possible to realize a scenario in which task restriction is permitted, which is set according to an operation input by the user and conforms to the user's requirements or habits. For example, the user wants to reduce the power consumption of the device, and the user can set multiple scenarios where task restrictions are allowed in the first list, e.g. browser scenarios as scenarios where task restrictions are allowed Set game scenario, navigation scenario, etc. Thus, when the first scenario corresponding to the current task is a browser scenario, a game scenario, or a navigation scenario, the first search unit 82 performs a search operation to reduce the power consumption of the device. be able to.

  Optionally, task restrictions are allowed and the scenarios included in the first list can also be set automatically according to device performance. For example, when a device has excellent performance, for example, when the device's CPU is running at high speed, the device has a large amount of memory, or the device has enough battery, task limits in the first list Only a few scenarios can be set up that are allowed. For example, when the device has insufficient performance, for example, when the device's CPU is running at low speed, the device has a small amount of memory, or the device does not have enough batteries, in the first list A number of scenarios where task restrictions are allowed can be set. In this way, the power consumption of the device can be reduced.

  Optionally, at least one background task corresponding to the first scenario can also refer to at least one background task in all background tasks corresponding to the first scenario, The corresponding at least one background task can also refer to all background tasks corresponding to the first scenario. In the present embodiment, no limit is set for this.

  The first processing unit 83 corresponds to the first scenario, and is configured to perform restriction processing on at least one background task searched by the first search unit 82. The restriction processing uses system resources. This is a process for reducing.

  Optionally, the limiting process can be a process to reduce system resources currently used by the task.

  Optionally, the device is specifically a multi-purpose device such as a tablet computer, mobile phone, electronic reader, remote control, PC, notebook computer, in-car device, web TV, wearable device, or other intelligent device with network capabilities. It can be any device with a task system.

  In the above technical solution, the first scenario corresponding to the foreground task is determined according to the foreground task, and the first scenario corresponding to the foreground task is in the first list, it corresponds to the first scenario At least one background task is searched, the first list includes scenarios where task restrictions are allowed, and the restriction process is performed on at least one background task corresponding to the first scenario, and the restriction process Is a process for reducing the use of system resources. In this manner, the restriction process is performed on at least one background task corresponding to a scenario in which task restriction is permitted. Compared to the prior art where background tasks are always executed, embodiments of the present invention can reduce device power consumption and power loss.

  Referring to FIG. 9, FIG. 9 is a schematic diagram of the structure of a task management device according to an embodiment of the present invention. As shown in FIG. 9, the task management device includes a determination unit 91, a determination unit 92, a first search unit 93, and a first processing unit 94.

  The determining unit 91 is configured to determine a first scenario corresponding to the foreground task according to the foreground task.

  The determination unit 92 is configured to determine whether or not the first scenario determined by the determination unit 91 is in the first list, and the first list includes scenarios in which task restriction is permitted.

  The first search unit 93, when the determination unit 92 determines that the first scenario determined by the determination unit 91 is in the first list, at least one background task corresponding to the first scenario Is configured to search for.

  Optionally, the first search unit 93 specifically does not affect other tasks or the operating system after receiving the restriction process in the background task corresponding to the first scenario. You can also search for one background task, you can also search for at least one predefined background task in the background task that corresponds to the first scenario, and in the background task that corresponds to the first scenario It is also possible to search for at least one background task whose user identifier corresponds to a general user. For example, the user identifier UID of each background task corresponding to the first scenario is searched, the background task whose UID corresponds to the general user is searched, and as at least one background task corresponding to the first scenario used.

  In this way, it is possible to realize that at least one background task corresponding to the first scenario and searched by the first search unit 93 is a background task whose UID corresponds to a general user. it can. The UID is a unique identifier for each task and can be used to uniquely identify the task. In addition, the UID can correspond to system users and general users. When the background task UID corresponds to a system user, this indicates that the background task is a background task included in the operating system. When the background task UID corresponds to a regular user, this indicates that the background task is not a background task included in the operating system.

  Optionally, the device can be further configured to ignore the background task whose UID corresponds to the system user in at least one background task corresponding to the first scenario. That is, no processing is performed for the background task whose UID corresponds to the system user.

  Optionally, the first search unit 93 can also search for at least one background task in the background task corresponding to the first scenario whose system resource usage reaches a preset threshold. For example, at least one background task in the background task corresponding to the first scenario whose CPU resource usage reaches 10% of the CPU resource is searched or in the background task corresponding to the first scenario At least one background task whose sleep lock retention period reaches 10 minutes is searched, or at least one of its average data download speed within the background task corresponding to the first scenario reaches 10M / min Two background tasks are searched.

  The first processing unit 94 corresponds to the first scenario, and is configured to perform restriction processing on at least one background task searched by the first search unit 93. The restriction processing uses system resources. This is a process for reducing.

Optionally, as shown in FIG. 10, the device
A second search unit corresponding to the foreground task and configured to search for a second scenario other than the first scenario searched by the determination unit 91, wherein the second scenario is at least one background A second search unit 95 corresponding to the task, the first list includes the second scenario, and
A second processing unit 96 corresponding to the second scenario and configured to perform a restriction process on at least one background task searched by the second search unit 95.

  Optionally, the second scenario can also refer to one or more scenarios. In addition, the second scenario can also refer to all scenarios other than the first scenario, and can also refer to one or a plurality of scenarios other than the first scenario, which is not limited in the present embodiment. .

  In addition, at least one background task corresponding to the second scenario can also refer to at least one background task in all background tasks corresponding to the second scenario, corresponding to the second scenario The at least one background task can also refer to all background tasks corresponding to the second scenario. In the present embodiment, no limit is set for this. In addition, the second scenario may specifically be a predetermined scenario, for example, a scenario set to receive an operation input by the user. As described above, it is possible to realize a scenario in which task restriction is permitted, which is set according to an operation input by the user and conforms to the user's requirements or habits. In addition, the second search unit 95 specifically has at least one in the background task corresponding to the second scenario that does not affect other tasks or the operating system after receiving the restriction process. You can also search for one background task, you can also search for at least one predefined background task in the background task that corresponds to the second scenario, and in the background task that corresponds to the second scenario It is also possible to search for at least one background task whose user identifier corresponds to a general user.

  Optionally, the second scenario may be a scenario that is not in the second list other than the first scenario, and the second list may include scenarios where task restrictions are prohibited. The scenario in which task restriction is prohibited can be a scenario set to receive an operation input by a user. As described above, it is possible to realize a scenario in which task restriction is prohibited, which is set according to an operation input by the user and meets the user's requirements or habits. For example, in the second list, the user may set a scenario that requires the user's attention as a scenario in which task restriction is prohibited, such as a short message service message scenario, a telephone scenario, and a download scenario. it can. Alternatively, a scenario in which task restriction is prohibited can be automatically set according to device performance. For example, when the device has excellent performance, for example, when the device's CPU is running at high speed, the device has a large amount of memory, or the device has enough battery, task limits in the second list There are a number of scenarios that can be prohibited. For example, when the device has insufficient performance, for example, when the device's CPU is running at low speed, the device has a small amount of memory, or the device does not have enough batteries, in the second list There can be very few scenarios where task restrictions are prohibited.

Optionally, as shown in FIG.
A first query unit 97 configured to query a user identifier of at least one background task;
And an ignoring unit 98 configured to ignore at least one background task when the user identifier queried by the first query unit corresponds to a system user and is of at least one background task. Can include
The first processing unit 94 is for at least one background task, and performs a restriction process on at least one background task when the user identifier inquired by the first inquiry unit 97 corresponds to a general user. It can be constituted as follows.

  In this embodiment, since the background task whose UID corresponds to the general user is not an operating system task, other tasks are not affected after the general user restriction process is performed on the background task. Therefore, the first processing unit 94 can limit only the background task whose UID corresponds to a general user, thereby reducing the power consumption and power loss of the device without affecting other tasks. .

Optionally, as shown in FIG. 12, the device
A timing unit 99 configured to start a timer for at least one background task corresponding to the first scenario;
And a first stop 100 configured to stop a system component used by at least one background task corresponding to the first scenario when the timer exceeds a preset threshold. it can.

  Optionally, system components include, but are not limited to, timers, sleep locks, and broadcast notifications. In addition, the status value of the system component when the system component is paused can be saved in the device, so that after the restriction process is released, the background task can save the status value of the system component. Can be called. In addition, the system component used by at least one background task corresponding to the first scenario is stopped only when the timer reaches a preset threshold (eg, 10 seconds, 30 seconds, etc.). As a result, frequent stopping of system components used by at least one background task corresponding to the first scenario can be avoided.

Optionally, as shown in FIG.
A second query unit 101 configured to query whether at least one background task uses the system component;
The second query unit 101 may further include a second stop unit 102 configured to stop the system component when the at least one background task confirms that the system component is used. .

  In this embodiment, system components used by at least one background task corresponding to the first scenario are stopped, so that power consumption and power loss of the device can be reduced.

Optionally, processing to reduce system resource usage is:
Freezing at least one background task;
Stop at least one background task,
Including at least one of: limiting system resources used by at least one background task.

  As described above, the first processing unit 94 can freeze at least one background task corresponding to the first scenario, or can stop at least one background task corresponding to the first scenario. And can limit system resources used by at least one background task corresponding to the first scenario.

  Optionally, freezing at least one background task corresponding to the first scenario prohibits the background task from invoking system resources, e.g., the CPU at least corresponds to the first scenario. It can be prohibited to call one background task. Specifically, the operating system's task scheduler is used to prohibit at least one background task corresponding to the first scenario from participating in any scheduling. Since at least one background task corresponding to the first scenario is prohibited from calling system resources, the power consumption of the device is reduced.

  Optionally, limiting the system resources used by at least one background task corresponding to the first scenario causes the CPU to call at least one background task corresponding to the first scenario within that time Limiting the time. For example, at least one background task corresponding to the first scenario so that the CPU can call at least one background task corresponding to the first scenario within the time indicated by the time value of the CPU call A time value is set for In addition, limiting the system resources used by at least one background task corresponding to the first scenario is further limited to using system resources by the at least one background task corresponding to the first scenario. Can also be used. For example, restricting at least one background task corresponding to the first scenario, or restricting use of memory space by at least one background task corresponding to the first scenario. In addition, this can also be to use different restriction measures depending on different scenarios corresponding to at least one background task corresponding to the first scenario. The aforementioned steps reduce device power consumption because the use of system resources by at least one background task corresponding to the first scenario is limited.

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

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

  In this embodiment, it is possible to realize that the limit process is performed on the background task only when the temperature of the device reaches the preset temperature threshold.

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

  Optionally, the device is specifically a multi-purpose device such as a tablet computer, mobile phone, electronic reader, remote control, PC, notebook computer, in-car device, web TV, wearable device, or other intelligent device with network capabilities. It can be any device with a task system.

  In the above technical solution, a plurality of optional implementations are realized based on the first embodiment, and all of these implementations can reduce the power consumption and power loss of the device.

  Referring to FIG. 14, FIG. 14 is a schematic diagram of another task management device structure according to an embodiment of the present invention. As shown in FIG. 14, the task management device includes a first determination unit 141, a second determination unit 142, a first search unit 143, and a first processing unit 144.

  The first determination unit 141 is configured to determine a first scenario corresponding to the foreground task according to the foreground task.

  Optionally, the first determination unit 141 can specifically determine the corresponding first scenario according to the current task when the current task is switched. For example, when a current task, a music task is being executed, this task enters a music scenario or a download scenario. Thus, it can be determined that the first scenario corresponding to the foreground task can be a music scenario, a download scenario, or the like. In addition, the foreground task can be one or more foreground tasks. In the case of a plurality of foreground tasks, the first determination unit 141 can be configured to determine a first scenario corresponding to each foreground task according to the plurality of foreground tasks. That is, the first determination unit 141 can be configured to determine a first scenario corresponding to each foreground task according to at least one foreground task.

  The second determination unit 142 corresponds to the foreground task, and is configured to determine a second scenario other than the first scenario determined by the first determination unit 141. The second scenario is a task. A scenario where restrictions are allowed, and the second scenario corresponds to at least one background task.

  Optionally, the second scenario can also refer to one or more scenarios. In addition, the second scenario can also refer to all scenarios other than the first scenario, and can also refer to one or a plurality of scenarios other than the first scenario, which is not limited in the present embodiment. . In addition, the second scenario may specifically be a predetermined scenario, for example, a scenario set to receive an operation input by the user. As described above, it is possible to realize a scenario in which task restriction is permitted, which is set according to an operation input by the user and conforms to the user's requirements or habits.

  Optionally, the second scenario may be a scenario that is not in the second list other than the first scenario, and the second list may include scenarios where task restrictions are prohibited.

  The first search unit 143 is configured to search for at least one background task corresponding to the second scenario determined by the second determination unit 142.

  Optionally, at least one background task corresponding to the second scenario can also refer to at least one background task in all background tasks corresponding to the second scenario, The corresponding at least one background task can also refer to all background tasks corresponding to the second scenario. In addition, the first search unit 143 specifically does not affect other tasks or the operating system in the background task corresponding to the second scenario after receiving the restriction process. You can also search for one background task, you can also search for at least one predefined background task in the background task that corresponds to the second scenario, and in the background task that corresponds to the second scenario You can also search for at least one background task whose UID corresponds to a regular user. For example, the first search unit 143 searches for the UID of each background task corresponding to the second scenario, and the UID corresponds to the general user as at least one background task corresponding to the second scenario. It can be configured to search for background tasks.

  The above-described operation corresponds to the second scenario, and at least one background task searched by the first search unit 143 can realize that the UID is a background task corresponding to a general user. it can.

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

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

  The first processing unit 144 corresponds to the second scenario, and is configured to perform a limiting process on at least one background task searched by the first searching unit 143. The limiting process uses system resources. This is a process for reducing.

Optionally, as shown in Figure 15, the device
A second search unit 145 configured to search for at least one background task corresponding to the first scenario;
A second configured to perform a restriction process on at least one background task corresponding to the first scenario when a user identifier of at least one background task corresponding to the first scenario corresponds to a general user; The processing unit 146 may be further included.

Optionally, as shown in FIG.
A timing unit 147 configured to start a timer for at least one background task corresponding to the second scenario;
A first stop 148 configured to stop a system component used by at least one background task corresponding to the second scenario when the timer exceeds a preset threshold. it can.

  Optionally, system components include, but are not limited to, timers, sleep locks, and broadcast notifications. At the same time, the above steps can save the status value of the system component when the system component is paused, so that after the restriction process is released, the background task will save the saved status of the system component A value can be called. In addition, the system component used by at least one background task corresponding to the second scenario is stopped only when the timer reaches a preset threshold (eg, 10 seconds, 30 seconds, etc.). Thereby, frequent stopping of the system components used by at least one background task corresponding to the second scenario can be avoided.

Optionally, as shown in FIG.
An inquiry unit 149 configured to inquire whether at least one background task uses the system component;
The interrogator may further include a second stop 150 configured to stop the system component when the at least one background task confirms that the system component is used.

  In this embodiment, system components used by at least one background task corresponding to the second scenario are stopped, so that power consumption and power loss of the device can be reduced.

Optionally, processing to reduce system resource usage is:
Freezing at least one background task;
Stop at least one background task,
It can also include at least one of ways to limit system resources used by at least one background task.

  In this case, the first processing unit 144 can freeze at least one background task corresponding to the second scenario, or can stop at least one background task corresponding to the second scenario. The system resources used by at least one background task corresponding to the second scenario can also be limited.

  Optionally, freezing at least one background task corresponding to the second scenario prohibits the background task from calling system resources, e.g., the CPU at least corresponds to the first scenario. It can be prohibited to call one background task. Specifically, the operating system's task scheduler is used to prohibit at least one background task corresponding to the first scenario from participating in any scheduling. Since at least one background task corresponding to the second scenario is prohibited from calling system resources, the power consumption of the device is reduced.

  Optionally, limiting the system resources used by at least one background task corresponding to the second scenario causes the CPU to call at least one background task corresponding to the second scenario within that time You can also limit your time. For example, at least one time value corresponding to the second scenario so that the CPU can call at least one background task corresponding to the second scenario within the time indicated by the time value of the CPU call Set for background tasks. In addition, limiting the system resources used by at least one background task corresponding to the second scenario further limits the use of system resources by at least one background task corresponding to the second scenario It can also be said. For example, limiting the use of network bandwidth by at least one background task corresponding to the second scenario, or limiting the use of memory space by at least one background task corresponding to the second scenario . In addition, this can also be to use different restriction measures depending on different scenarios corresponding to at least one background task corresponding to the second scenario. The aforementioned steps limit the use of system resources by at least one background task corresponding to the second scenario, thus reducing the power consumption of the device.

  Optionally, the device is specifically a multi-purpose device such as a tablet computer, mobile phone, electronic reader, remote control, PC, notebook computer, in-car device, web TV, wearable device, or other intelligent device with network capabilities. It can be any device with a task system.

  In the above technical solution, the first scenario corresponding to the foreground task is determined according to the foreground task, the second scenario other than the first scenario corresponding to the foreground task is determined, and the second scenario is a task. A scenario where restrictions are allowed, the second scenario corresponds to at least one background task, and at least one background task corresponding to the second scenario is searched and at least one corresponding to the second scenario Restriction processing is performed for one background task, and the restriction processing is processing for reducing the use of system resources. Therefore, power consumption and power loss of the device can be reduced.

Referring to FIG. 18, FIG. 18 is a schematic diagram of another task management device structure according to an embodiment of the present invention. As shown in FIG. 18, the task management device includes a memory 181 and a processor 182 connected to the memory 181, and the memory 181 is configured to store a program code.
According to the foreground task, determining the first scenario corresponding to the foreground task, and
When the first scenario corresponding to the foreground task is in the first list, the operation is to search for at least one background task corresponding to the first scenario, and the first list is allowed to be restricted. Searching for at least one background task, including
An operation for performing a restriction process on at least one background task corresponding to the first scenario, and the restriction process is a process for reducing the use of system resources. Is configured to call a program stored in the memory.

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

  Optionally, the scenario where task restrictions are allowed and included in the first list may be a scenario configured to receive an operation entered by the user. As described above, it is possible to realize a scenario in which task restriction is permitted, which is set according to an operation input by the user and conforms to the user's requirements or habits. For example, the user wants to reduce the power consumption of the device, and the user can set multiple scenarios where task restrictions are allowed in the first list, e.g. browser scenarios as scenarios where task restrictions are allowed Set game scenario, navigation scenario, etc. Thus, when the first scenario corresponding to the current task is a browser scenario, a game scenario, or a navigation scenario, the processor 182 can perform a search operation to reduce the power consumption of the device.

  Optionally, task restrictions are allowed and the scenarios included in the first list can also be set automatically according to device performance. For example, when a device has excellent performance, for example, when the device's CPU is running at high speed, the device has a large amount of memory, or the device has enough battery, task limits in the first list Only a few scenarios can be set up that are allowed. For example, when a device has insufficient performance, for example, when the device's CPU is running at low speed, the device has a small amount of memory, or the device does not have enough batteries, Since there are multiple scenarios where task limits are allowed, multiple scenarios where task limits are allowed in the first list may be set.

  Optionally, at least one background task corresponding to the first scenario can also refer to at least one background task in all background tasks corresponding to the first scenario, The corresponding at least one background task can also refer to all background tasks corresponding to the first scenario. In the present embodiment, no limit is set for this.

  Optionally, the restriction process may be a process used to reduce current system resource usage.

In another embodiment, the processor 182
According to the foreground task, determining the first scenario corresponding to the foreground task, and
Determining whether the first scenario is in the first list and, if yes, searching for at least one background task corresponding to the first scenario; and
An operation for performing a restriction process on at least one background task corresponding to the first scenario, the restriction process being a process for reducing the use of system resources, an operation for performing a restriction process,
It can be further configured to perform an operation of terminating the process when the result of the determination is “no”.

Optionally, processor 182 specifically specifies at least one background within the background task corresponding to the first scenario that will not affect other tasks or the operating system after undergoing restriction processing. You can also search for tasks, search for at least one predefined background task in the background task corresponding to the first scenario, and the user in the background task corresponding to the first scenario It is also possible to search for at least one background task whose identifier corresponds to a general user. For example, the operation performed by the processor 182 to search for at least one background task corresponding to the first scenario is:
Search for the user identifier of each background task corresponding to the first scenario, and at least one background task corresponding to the first scenario includes the operation of searching for the background task whose UID corresponds to the general user be able to.

  That is, this action corresponds to the first scenario and is used to realize that at least one background task searched by the processor 182 is a background task whose UID corresponds to a general user. . The UID is a unique identifier of each task and is used to uniquely identify the task. In addition, the UID can correspond to system users and general users. When the background task UID corresponds to a system user, this indicates that the background task is a background task included in the operating system. When the background task UID corresponds to a regular user, this indicates that the background task is not a background task included in the operating system.

  Optionally, the processor 182 may be configured to ignore background tasks whose UID corresponds to the system user in at least one background task corresponding to the first scenario. That is, no processing is performed for the background task whose UID corresponds to the system user.

  Optionally, the processor 182 may search for at least one background task in the background task corresponding to the first scenario whose system resource usage reaches a preset threshold. For example, at least one background task in the background task corresponding to the first scenario whose CPU resource usage reaches 10% of the CPU resource is searched or in the background task corresponding to the first scenario At least one background task whose sleep lock retention period reaches 10 minutes is searched, or at least one of its average data download speed within the background task corresponding to the first scenario reaches 10M / min Two background tasks are searched.

Optionally, the processor 182
An operation to search for a second scenario other than the first scenario corresponding to the foreground task, wherein the second scenario corresponds to at least one background task, and the first list includes the second scenario; An action to search for the second scenario;
It is possible to further perform an operation of performing a restriction process on at least one background task corresponding to the second scenario.

  Optionally, the second scenario can also refer to one or more scenarios. In addition, the second scenario can also refer to all scenarios other than the first scenario, and can also refer to one or a plurality of scenarios other than the first scenario, which is not limited in the present embodiment. .

  In addition, at least one background task corresponding to the second scenario can also refer to at least one background task in all background tasks corresponding to the second scenario, corresponding to the second scenario The at least one background task can also refer to all background tasks corresponding to the second scenario. In the present embodiment, no limit is set for this. In addition, the second scenario may specifically be a predetermined scenario, for example, a scenario set to receive an operation input by the user. As described above, it is possible to realize a scenario in which task restriction is permitted, which is set according to an operation input by the user and conforms to the user's requirements or habits. In addition, the processor 182 specifically has at least one background task in the background task corresponding to the second scenario that will not affect other tasks or the operating system after undergoing restriction processing. And at least one predetermined background task in the background task corresponding to the second scenario, and its user identifier in the background task corresponding to the second scenario Can also search for at least one background task corresponding to a general user.

  Optionally, the second scenario may be a scenario that is not in the second list other than the first scenario, and the second list may include scenarios where task restrictions are prohibited. In addition, the second list can be called a black list. The scenario in which task restriction is prohibited can be a scenario set to receive an operation input by a user. As described above, it is possible to realize a scenario in which task restriction is prohibited, which is set according to an operation input by the user and meets the user's requirements or habits. For example, in the second list, the user may set a scenario that requires the user's attention as a scenario in which task restriction is prohibited, such as a short message service message scenario, a telephone scenario, and a download scenario. it can. Alternatively, a scenario in which task restriction is prohibited can be automatically set according to device performance. For example, when the device has excellent performance, for example, when the device's CPU is running at high speed, the device has a large amount of memory, or the device has enough battery, task limits in the second list There are a number of scenarios that can be prohibited. For example, when the device has insufficient performance, for example, when the device's CPU is running at low speed, the device has a small amount of memory, or the device does not have enough batteries, in the second list There can be very few scenarios where task restrictions are prohibited.

Optionally, prior to the operation in which processor 182 performs a restriction process on at least one background task corresponding to the first scenario, processor 182
Querying the UID of at least one background task corresponding to the first scenario, and
Behavior to ignore at least one background task if at least one background task UID corresponding to the first scenario corresponds to a system user, or at least one background task UID corresponds to a general user In this case, it can be further configured to perform an operation of performing restriction processing on at least one background task. In other words, step 204 performs a restriction process on at least one background task whose UID corresponds to a general user.

  In this embodiment, since the background task whose UID corresponds to the general user is not an operating system task, other tasks are not affected after the general user restriction process is performed on the background task. Therefore, in step 204, the restriction process is performed only for the background task whose UID corresponds to the general user, thereby reducing the power consumption and power loss of the device without affecting other tasks. Can do.

Optionally, prior to the operation in which processor 182 performs a restriction process on at least one background task corresponding to the first scenario, processor 182
An action to start a timer for at least one background task corresponding to the first scenario;
It may be further configured to perform an operation to stop a system component used by at least one background task corresponding to the first scenario when the timer exceeds a preset threshold.

  Optionally, system components include, but are not limited to, timers, sleep locks, and broadcast notifications. At the same time, the above steps can save the status value of the system component when the system component is paused, so that after the restriction process is released, the background task will save the saved status of the system component A value can be called. In addition, the system component used by at least one background task corresponding to the first scenario is stopped only when the timer reaches a preset threshold (eg, 10 seconds, 30 seconds, etc.). As a result, frequent stopping of system components used by at least one background task corresponding to the first scenario can be avoided.

Optionally, prior to the operation in which processor 182 performs a restriction process on at least one background task corresponding to the first scenario, processor 182
An action to query whether at least one background task corresponding to the first scenario uses a system component;
It may be further configured to perform an action to stop the first scenario when at least one background task corresponding to the first scenario uses the system component.

  In this embodiment, system components used by at least one background task corresponding to the first scenario are stopped, so that power consumption and power loss of the device can be reduced.

Optionally, processing to reduce system resource usage is:
Freezing at least one background task;
Stop at least one background task,
It can also include at least one of ways to limit system resources used by at least one background task.

  In this case, the processor 182 can also freeze at least one background task corresponding to the first scenario, can stop at least one background task corresponding to the first scenario, It is also possible to limit the system resources used by at least one background task corresponding to the scenario.

Optionally, the operation performed by processor 182 to determine a first scenario corresponding to the foreground task according to the foreground task is:
When the temperature reaches a preset temperature threshold, an operation may be included that determines a first scenario corresponding to the foreground task according to the foreground task.

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

  In this embodiment, it is possible to realize that the limit process is performed on the background task only when the temperature of the device reaches the preset temperature threshold.

Optionally, the processor 182
It can be further configured to perform an operation of releasing the restriction process for at least one background task corresponding to the first scenario. Specifically, when the first scenario is not in the first list, the restriction process is canceled for the background task that has undergone the restriction process.

  Optionally, the method specifically includes multiple computers such as tablet computers, mobile phones, electronic readers, remote controls, PCs, notebook computers, in-car devices, web TVs, wearable devices, or other intelligent devices with network capabilities. It can be applied to any device having a task system.

  In the above technical solution, the first scenario corresponding to the foreground task is determined according to the foreground task, and the first scenario corresponding to the foreground task is in the first list, it corresponds to the first scenario At least one background task is searched, the first list includes scenarios where task restrictions are allowed, and the restriction process is performed on at least one background task corresponding to the first scenario, and the restriction process Is a process for reducing the use of system resources. In this manner, the restriction process is performed on at least one background task corresponding to a scenario in which task restriction is permitted. Compared to the prior art where background tasks are always executed, this embodiment of the present invention can reduce the power consumption and power loss of the device.

Referring to FIG. 19, FIG. 19 is a schematic diagram of the structure of another task management device according to an embodiment of the present invention. As shown in FIG. 19, the task management device includes a memory 191 and a processor 192 connected to the memory 191. The memory 191 is configured to store a program code.
According to the foreground task, determining the first scenario corresponding to the foreground task, and
An action to determine a second scenario other than the first scenario corresponding to the foreground task, where the second scenario is a scenario in which task restriction is permitted, and the second scenario is at least one background task. An action to determine the corresponding second scenario;
Searching for at least one background task corresponding to the second scenario; and
An operation for performing a restriction process on at least one background task corresponding to the second scenario, and the restriction process is a process for reducing the use of system resources. Is configured to call a program stored in the memory.

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

  Optionally, the second scenario can also refer to one or more scenarios. In addition, the second scenario can also refer to all scenarios other than the first scenario, and can also refer to one or a plurality of scenarios other than the first scenario, which is not limited in the present embodiment. . In addition, the second scenario may specifically be a predetermined scenario, for example, a scenario set to receive an operation input by the user. As described above, it is possible to realize a scenario in which task restriction is permitted, which is set according to an operation input by the user and conforms to the user's requirements or habits.

  Optionally, the second scenario may be a scenario that is not in the second list other than the first scenario, and the second list may include scenarios where task restrictions are prohibited.

Optionally, at least one background task corresponding to the second scenario can also refer to at least one background task in all background tasks corresponding to the second scenario, The corresponding at least one background task can also refer to all background tasks corresponding to the second scenario. In addition, the processor 192 specifically has at least two background tasks within the background task corresponding to the second scenario that will not affect other tasks or the operating system after undergoing restriction processing. You can also search for at least one predetermined background task in the background task corresponding to the second scenario, and its UID in the background task corresponding to the second scenario is It is also possible to search for at least one background task corresponding to a general user. For example, the operation performed by the processor 192 to search for at least one background task corresponding to the second scenario is:
Search for the UID of each background task corresponding to the second scenario, and at least one background task corresponding to the second scenario includes an operation for searching for the background task corresponding to the general user. Can do.

  That is, this step corresponds to the second scenario and is used to realize that at least one background task searched by the processor 192 is a background task whose UID corresponds to a general user. .

Optionally, the processor 192 is
It can be further configured to perform an action in the at least one background task corresponding to the second scenario that ignores the background task whose UID corresponds to the system user. That is, no processing is performed for the background task whose UID corresponds to the system user.

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

Optionally, the processor 192 is
Searching for at least one background task corresponding to the first scenario;
When the UID of at least one background task corresponding to the first scenario corresponds to a general user, it is further configured to perform an operation of performing restriction processing on at least one background task corresponding to the first scenario You can also

  For this embodiment of the present embodiment, further refer to the embodiment in which the restriction process is performed on at least one background task corresponding to the first scenario in the first embodiment and the second embodiment. .

Optionally, prior to the operation of processor 192 performing a restriction process on at least one background task corresponding to the second scenario, processor 192
An action to start a timer for at least one background task corresponding to the second scenario;
It may be further configured to perform an action to stop a system component used by at least one background task corresponding to the second scenario when the timer exceeds a preset threshold.

  Optionally, system components include, but are not limited to, timers, sleep locks, and broadcast notifications. At the same time, the above steps can save the status value of the system component when the system component is paused, so that after the restriction process is released, the background task will save the saved status of the system component A value can be called. In addition, the system component used by at least one background task corresponding to the second scenario is stopped only when the timer reaches a preset threshold (eg, 10 seconds, 30 seconds, etc.). Thereby, frequent stopping of the system components used by at least one background task corresponding to the second scenario can be avoided.

Optionally, prior to the operation of processor 192 performing a restriction process on at least one background task corresponding to the second scenario, processor 192
An action to query whether at least one background task uses a system component, and
If at least one background task uses a system component, it can be further configured to perform the action of stopping the system component.

  In this embodiment, system components used by at least one background task corresponding to the second scenario are stopped, so that power consumption and power loss of the device can be reduced.

Optionally, processing to reduce system resource usage is:
Freezing at least one background task;
Stop at least one background task,
It can also include at least one of ways to limit system resources used by at least one background task.

  In this case, the processor 192 can freeze at least one background task corresponding to the second scenario, can also stop at least one background task corresponding to the second scenario, It is also possible to limit the system resources used by at least one background task corresponding to the scenario.

  Optionally, the method specifically includes multiple computers such as tablet computers, mobile phones, electronic readers, remote controls, PCs, notebook computers, in-car devices, web TVs, wearable devices, or other intelligent devices with network capabilities. It can be applied to any device having a task system.

  In the above technical solution, the first scenario corresponding to the foreground task is determined according to the foreground task, the second scenario other than the first scenario corresponding to the foreground task is determined, and the second scenario is a task. A scenario where restrictions are allowed, the second scenario corresponds to at least one background task, and at least one background task corresponding to the second scenario is searched and at least one corresponding to the second scenario Restriction processing is performed for one background task, and the restriction processing is processing for reducing the use of system resources. Therefore, power consumption and power loss of the device can be reduced.

  Those skilled in the art will appreciate that all or part of each process of the method in each embodiment can be realized by a computer program that instructs the associated hardware. The program can be stored in a computer readable storage medium. When the program runs, each process of the method in each embodiment is performed. The aforementioned storage medium can include a magnetic disk, an optical disk, a read-only memory (abbreviated as ROM), or a random access memory (abbreviated as RAM).

  The foregoing disclosure is merely exemplary embodiments of the present invention and, of course, is not intended to limit the protection scope of the present invention. Accordingly, equivalent modifications made in accordance with the claims of the present invention are intended to be included within the scope of the present invention.

81 Decision part
82 First search part
83 First processing section
91 Decision part
92 Judgment Department
93 First search part
94 First processing section
95 Second search part
96 Second processing section
97 First Inquiry Department
98 Ignore part
99 Timing section
100 First stop
101 Second inquiry section
102 Second stop
141 First decision part
142 Second decision part
143 First search unit
144 First processing part
145 Second search unit
146 Second processing unit
147 Timing section
148 First stop
149 Inquiry Department
150 Second stop
181 memory
182 processor
191 memory
192 processor

Claims (14)

A task management method,
Determining a first scenario corresponding to the foreground task according to the foreground task;
Searching for at least one background task corresponding to the first scenario when the first scenario corresponding to the foreground task is in a first list, wherein the first list is a task Exploring at least one background task, including scenarios where restrictions are allowed;
Performing restriction processing on the at least one background task corresponding to the first scenario, the restriction processing including processing for reducing system resource use, and performing restriction processing;
Determining the first scenario comprises:
Determining, according to the foreground task, the first scenario corresponding to the foreground task when a temperature reaches a preset temperature threshold;
The temperature is a temperature of a device that performs the task management method,
Only when the temperature of the device reaches the preset temperature threshold, the limiting process is performed on the background task ,
Searching for a second scenario other than the first scenario corresponding to the foreground task, wherein the second scenario corresponds to at least one background task, and the first list is the second scenario Exploring a second scenario including:
Performing a restriction process on the at least one background task corresponding to the second scenario;
Further including
The second scenario is a scenario that is not in the second list other than the first scenario, and the second list includes a scenario in which task restriction is prohibited, and the scenario in which the task restriction is prohibited Is automatically set according to the performance of the device,
The task management method , wherein the device performance includes at least one of a performance of the CPU of the device, a memory capacity of the device, and a battery capacity of the device . Before the step of restricting the at least one background task corresponding to the first scenario,
Querying a user identifier of the at least one background task;
Ignoring the at least one background task if the user identifier of the at least one background task corresponds to a system user;
Performing the restriction process on the at least one background task when the user identifier of the at least one background task corresponds to a general user, and
Wherein if at least one of the user identifier of the background task corresponds to the system user, it said at least one background task is a background task in the operating system, the method according to claim 1. Before the step of restricting the at least one background task corresponding to the first scenario,
Querying whether the at least one background task uses a system component;
Wherein when at least one of the background task will use the system components, further comprises the step of stopping the system components, the method according to claim 1. The process for reducing system resource usage includes:
Freezing the at least one background task;
Stopping the at least one background task;
4. The method according to any one of claims 1 to 3 , comprising at least one of: limiting system resources used by the at least one background task. A task management method,
Determining a first scenario corresponding to the foreground task according to the foreground task;
Determining a second scenario other than the first scenario corresponding to the foreground task, wherein the second scenario is a scenario in which task restriction is allowed, and the second scenario is at least one Determining a second scenario corresponding to the background task;
Searching for the at least one background task corresponding to the second scenario;
Performing a restriction process on the at least one background task corresponding to the second scenario, the restriction process including a process for reducing a system resource use, and performing a restriction process;
Determining the first scenario comprises:
Determining, according to the foreground task, the first scenario corresponding to the foreground task when a temperature reaches a preset temperature threshold;
The temperature is a temperature of a device that performs the task management method,
Only when the temperature of the device reaches the preset temperature threshold, the limiting process is performed on the background task ,
The second scenario is a scenario that is not in the second list other than the first scenario, and the second list includes a scenario in which task restriction is prohibited, and the scenario in which the task restriction is prohibited Is automatically set according to the performance of the device,
The task management method , wherein the device performance includes at least one of a performance of the CPU of the device, a memory capacity of the device, and a battery capacity of the device . Searching for at least one background task corresponding to the first scenario;
Performing a restriction process on the at least one background task corresponding to the first scenario when a user identifier of the at least one background task corresponding to the first scenario corresponds to a general user;
Ignoring the at least one background task if a user identifier of the at least one background task corresponding to the first scenario corresponds to a system user;
Further including
6. The method of claim 5 , wherein if the user identifier of the at least one background task corresponds to a system user, the at least one background task is a background task included in an operating system. Before the step of restricting the at least one background task corresponding to the second scenario,
Starting a timer for the at least one background task corresponding to the second scenario;
When the timer exceeds a preset threshold, further comprising the step of stopping the system components used by the at least one background task corresponding to the second scenario, according to claim 5 or 6 Method. Before the step of restricting the at least one background task corresponding to the second scenario,
Querying whether the at least one background task uses a system component;
7. The method of claim 5 or 6 , further comprising stopping the system component when the at least one background task uses the system component. The process for reducing system resource usage includes:
Freezing the at least one background task;
Stopping the at least one background task;
9. A method according to any one of claims 5 to 8 , comprising at least one of: limiting system resources used by the at least one background task. A task management device including a first determination unit, a second determination unit, a first search unit, and a first processing unit,
The first determination unit is configured to determine a first scenario corresponding to the foreground task according to a foreground task,
The second determination unit corresponds to the foreground task and is configured to determine a second scenario other than the first scenario determined by the first determination unit, and the second determination unit The scenario is a scenario in which task restriction is allowed, and the second scenario corresponds to at least one background task,
The first search unit is configured to search for the at least one background task corresponding to the second scenario determined by the second determination unit;
The first processing unit corresponds to the second scenario, and is configured to perform a limiting process on the at least one background task searched by the first searching unit, and the limiting process is This is a process to reduce system resource usage.
The first determination unit includes:
Further configured to determine, according to the foreground task, the first scenario corresponding to the foreground task when a temperature reaches a preset temperature threshold;
The temperature is a temperature of a device managed by the task management device.
The first processing unit includes:
Only when the temperature of the device reaches the preset temperature threshold value, to perform the limit processing for the background task is further configured,
The second scenario is a scenario that is not in the second list other than the first scenario, and the second list includes a scenario in which task restriction is prohibited, and the scenario in which the task restriction is prohibited Is automatically set according to the performance of the device
The device performance includes at least one of the CPU performance of the device, the memory capacity of the device, and the battery capacity of the device.
Task management device. A second search unit configured to search for at least one background task corresponding to the first scenario;
When the user identifier of the at least one background task corresponding to the first scenario corresponds to a general user, the restriction process is performed on the at least one background task corresponding to the first scenario. A second processing unit configured;
A third processing unit configured to ignore the at least one background task when a user identifier of the at least one background task corresponding to the first scenario corresponds to a system user; and Including
11. The device of claim 10 , wherein the at least one background task is a background task included in an operating system if the user identifier of the at least one background task corresponds to a system user. A timing unit configured to start a timer for the at least one background task corresponding to the second scenario;
A first stop configured to stop a system component used by the at least one background task corresponding to the second scenario when the timer exceeds a preset threshold; and The device of claim 10 . An inquiry unit configured to inquire whether the at least one background task uses a system component;
The inquiry unit further comprises said when at least one background task it was confirmed that the use of the system components, second stop portion configured to stop the system components, according to claim 10 Device described in. The process for reducing system resource usage includes:
Freezing the at least one background task;
Stopping the at least one background task;
14. A device according to any one of claims 10 to 13 , comprising at least one of: limiting system resources used by the at least one background task.

Images