WO2019128540A1 - Resource management method, mobile terminal and computer readable storage medium - Google Patents

Abstract

A resource management method, comprising: obtaining a target identifier for resource limitation level change; determining a target type for resource limitation level change according to the target identifier, the target type being one of a thread, a process, and an application; and configuring, according to the setting mode corresponding to the target type, a target corresponding to the target identifier as the resource usage priority corresponding to the changed resource limitation level.

Description

Resource management method, mobile terminal and computer readable storage medium

Cross-reference to related applications

This application claims the priority of the Chinese Patent Application filed on Dec. 29, 2017, the Chinese Patent Application No. 201711488929.3, entitled "Resource Management Methods, Devices, Mobile Terminals, and Computer Readable Storage Media", the entire contents of which are incorporated herein by reference. This is incorporated herein by reference.

Technical field

The present application relates to the field of computer technologies, and in particular, to a resource management method, a mobile terminal, and a computer readable storage medium.

Background technique

With the rapid development of the Internet, smart mobile terminals have become the most commonly used electronic devices for many users, such as smart phones and tablet boards. Users can install various applications on the smart mobile terminal for use. When the application runs in the background, it will preempt the CPU (Central Processing Unit), memory, bandwidth and other system resources with the application running in the foreground. This leads to problems such as the application running in the foreground, the slow operation of the system, and the fever of the mobile terminal.

Summary of the invention

According to various embodiments of the present application, a resource management method, a mobile terminal, and a computer readable storage medium are provided.

A resource management method, including:

Obtain the target ID for the resource restriction level change;

Determining, according to the target identifier, a target category for performing a resource restriction level change, the target category including one of a thread, a process, and an application;

The target corresponding to the target identifier is configured as a resource usage priority corresponding to the changed resource restriction level according to a setting manner corresponding to the target type.

A mobile terminal includes a memory and a processor, wherein the memory stores a computer program, when the computer program is executed by the processor, causing the processor to perform an operation of: acquiring a target identifier for performing resource restriction level change Determining, according to the target identifier, a target category for performing a resource restriction level change, the target category including one of a thread, a process, and an application; and corresponding to the target identifier according to a setting manner corresponding to the target category The target is configured as a resource usage priority corresponding to the changed resource restriction level.

A computer readable storage medium having stored thereon a computer program, the computer program being executed by a processor, causing a processor to: acquire a target identifier for performing a resource restriction level change; and determine to perform a resource according to the target identifier Restricting the target type of the level change, the target category includes one of a thread, a process, and an application; configuring the target corresponding to the target identifier to be the changed resource limit according to a setting manner corresponding to the target category The resource usage priority corresponding to the level.

Details of one or more embodiments of the present application are set forth in the accompanying drawings and description below. Other features, objects, and advantages of the invention will be apparent from the description and appended claims.

DRAWINGS

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the embodiments or the description of the prior art will be briefly described below. Obviously, the drawings in the following description are only It is a certain embodiment of the present invention, and other drawings can be obtained from those skilled in the art without any creative work.

1 is a block diagram of a mobile terminal in one embodiment.

2 is a system architecture diagram of a resource management method in an embodiment.

FIG. 3 is a schematic flow chart of a resource management method in an embodiment.

4 is a schematic diagram of a resource group in an embodiment.

FIG. 5 is a schematic diagram of a process of configuring resource usage priorities according to target types in an embodiment.

FIG. 6 is a schematic flowchart of configuring resource usage priority for an application in an embodiment.

FIG. 7 is a schematic diagram of resource limitation from multiple dimensions such as threads, processes, and applications in one embodiment.

FIG. 8 is a schematic flowchart of determining a resource restriction level change target identifier and a changed resource restriction level in one embodiment.

Figure 9 is a block diagram of a resource management device in one embodiment.

Figure 10 is a block diagram of a mobile terminal in another embodiment.

Detailed ways

In order to make the objects, technical solutions, and advantages of the present application more comprehensible, the present application will be further described in detail below with reference to the accompanying drawings and embodiments. It is understood that the specific embodiments described herein are merely illustrative of the application and are not intended to be limiting.

It will be understood that the terms "first", "second" and the like, as used herein, may be used to describe various elements, but these elements are not limited by these terms. These terms are only used to distinguish one element from another. For example, a first client may be referred to as a second client, and similarly, a second client may be referred to as a first client, without departing from the scope of the present application. Both the first client and the second client are clients, but they are not the same client.

1 is a block diagram of a mobile terminal in one embodiment. As shown in FIG. 1, the mobile terminal includes a processor, a memory, a display screen, and an input device connected through a system bus. The memory may include a non-volatile storage medium and a processor. The non-volatile storage medium of the mobile terminal stores an operating system and a computer program, which are executed by the processor to implement a resource management method provided in the embodiments of the present application. The processor is used to provide computing and control capabilities to support the operation of the entire mobile terminal. The internal memory in the mobile terminal provides an environment for the operation of a computer program in a non-volatile storage medium. The display screen of the mobile terminal may be a liquid crystal display or an electronic ink display screen. The input device may be a touch layer covered on the display screen, or may be a button, a trackball or a touchpad provided on the casing of the mobile terminal, or may be An external keyboard, trackpad, or mouse. The mobile terminal can be a mobile phone, a tablet or a personal digital assistant or a wearable device. A person skilled in the art can understand that the structure shown in FIG. 1 is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation of the mobile terminal to which the solution of the present application is applied. The specific mobile terminal may It includes more or fewer components than those shown in the figures, or some components are combined, or have different component arrangements.

2 is a system architecture diagram of a resource management method in an embodiment. As shown in FIG. 2, the system architecture includes a JAVA spatial layer 210, a local framework layer 220, and a kernel space layer 230. The JAVA spatial layer 210 can include a freeze management module 212. The freeze management module 212 can implement a freeze policy for each running application, and freeze the related applications that consume more power in the background or preempt a large amount of system resources. . The resource priority and restriction management module 222 and the platform freeze management module 224 are included in the local framework layer 220. The mobile terminal can maintain different applications in different resource usage priorities and different resource groups in real time through the resource priority and restriction management module 222, and adjust the resource group of the application according to the requirements of the upper layer to achieve optimized performance. Save power. The mobile terminal can allocate the application that can be frozen in the background to the frozen layer corresponding to the preset different levels according to the length of the entry freeze time through the platform freeze management module 224. Optionally, the frozen layer may include three: a CPU limited sleep mode, a CPU freeze sleep mode, and a process deep freeze mode. The CPU restricts the sleep mode to limit the CPU resources occupied by the related processes, so that the related processes occupy less CPU resources, and the free CPU resources are tilted to other unfrozen processes, thereby limiting the occupation of CPU resources. It also limits the occupation of network resources and I/O interface resources by the process; CPU freeze sleep mode refers to prohibiting related processes from using the CPU, while preserving the occupation of memory, when prohibiting the use of CPU resources, the corresponding network resources and I The /O interface resource is also forbidden to use; the process deep freeze mode means that in addition to prohibiting the use of CPU resources, the memory resources occupied by the related processes are further recovered, and the recovered memory can be used by other processes. Optionally, the local framework layer 220 may further include an interface module, where the interface module includes a binder interface developed to the upper layer, and the upper layer framework or the application sends the resource restriction or the frozen instruction to the resource priority and the limit management through the provided binder interface. Module 222 and platform freeze management module 224.

The kernel space layer 230 may include a UID management module 231, a Cgroup module 233, a Binder management module 235, a process memory recovery module 237, and a freeze timeout exit module 239. The UID management module 231 is configured to implement an application-based User Identifier (UID) to manage resources of a third-party application or freeze. Compared with the Process Identifier (PID) for process management and control, it is easier to uniformly manage the resources of a user's application through UID. The Cgroup module 233 is used to provide a complete set of CPU, CPUSET, memory, input/output (I/O) and Net related resource restriction mechanisms. The Binder management module 235 is used to implement the priority control of the background binder communication. The process memory recovery module 237 is configured to implement the process deep freeze mode, so that when a third-party application is in a frozen state for a long time, the file area of the process is mainly released, thereby saving the memory module and speeding up the application next time. The speed at startup. The freeze timeout exit module 239 can be used to resolve an exception generated by the freeze timeout scenario. Through the system architecture described above, the resource management method in various embodiments of the present application can be implemented.

As shown in FIG. 3, in an embodiment, a resource management method is provided, including the following operations:

Operation 310, obtaining a target identifier for performing a resource restriction level change.

A mobile terminal can run one or more applications at the same time. One application can run one or more processes, and one process can run one or more threads. A process is a running activity of a program on a computer on a data set. It is the basic unit for resource allocation and scheduling, and is the basis of the operating system structure. A thread can also be called a Lightweight Process (LWP), which is the smallest unit of a program execution flow. A thread is an entity in a process and is the basic unit that is independently scheduled and dispatched by the system.

The mobile terminal can set different resource restriction levels according to actual needs. The resource restriction level can be used to indicate the extent to which the resource usage is restricted. The higher the resource restriction level, the greater the degree of restriction. Restricted resources may include, but are not limited to, CPU resources, memory resources, I/O resources, network resources, and the like. Different resource restriction levels may correspond to different resource usage priorities. The higher the resource restriction level, the smaller the corresponding resource usage priority, and the lower the resource restriction level, the greater the corresponding resource usage priority. In an embodiment, the resource restriction level set by the mobile terminal may include an unrestricted level, a normal restriction level, a depth restriction level, and a freeze level. An unrestricted level can mean that resources used by an application, a process, or a thread are not limited. For example, an application or a process running in the foreground can correspond to an unrestricted level, thereby ensuring normal operation of a foreground application or a process. The normal restriction level may refer to applications, processes, threads, etc., which may use less resources, such as up to 50% of resources, but are not limited thereto. The depth limit level may refer to applications, processes, or threads that use very few resources, such as up to 20% of resources, but are not limited thereto. The freeze level refers to any behavior that cannot be used by an application, process, or thread to stop an application, process, or thread.

Optionally, the mobile terminal can monitor each application, each process, and each thread, collect the running characteristics of each application, each process, and each thread, and determine resource limits of each application, each process, and each thread according to the running characteristics. grade. The running characteristics may include, but are not limited to, an operating state, a currently executed task, a communication event, a currently occupied resource type and a proportion, etc., wherein the running state may include foreground running and background running, and the communication event refers to communication between processes Such as socket, binder communication, etc.

Optionally, the mobile terminal may collect running characteristics of each application, each process, and each thread at a certain time period, and determine, according to the running characteristics, whether the resource restriction level of the application, the process, or the thread needs to be changed, for example, when the application is from the foreground. When the operation is switched to run in the background, the resource restriction level of the application may be increased, or when the process receives the communication message sent by other processes, the resource restriction level of the process may be lowered, but is not limited thereto. When a resource restriction level change is required, the mobile terminal can obtain a target identifier for making a resource restriction level change, and the target identifier can be used to identify a target for resource restriction level change, which can be an application, a process, a thread, and the like. The target identifier may be composed of one or more of numbers, letters, symbols, and the like.

Operation 320, determining, according to the target identifier, a target type for performing a resource restriction level change, the target category including one of a thread, a process, and an application.

The mobile terminal acquires the target identifier for performing the resource restriction level, and can parse the target identifier, determine the target for which the resource restriction level is changed, and the target type to which the target belongs. The target type can be one of a thread, a process, an application, and the like. Optionally, the target identifiers of different target categories may correspond to different formats. For example, the identifiers of threads, processes, and applications may respectively correspond to different numbers, for example, the thread identifier corresponds to 8 digits, the process identifier corresponds to 9 digits, and the application The identifier corresponds to 10 digits, etc., or the identifier of the process, process, and application carries the corresponding character. For example, the letter of the thread identifier in the first digit is T, the letter of the process identifier in the first digit is P, and the application identifier is in the first One letter is A, etc., but is not limited to this.

In operation 330, the target corresponding to the target identifier is configured as a resource usage priority corresponding to the changed resource restriction level according to a setting manner corresponding to the target type.

After determining the target type of the resource restriction level change, the mobile terminal may obtain a setting manner corresponding to the target type, and configure the target corresponding to the target identifier as the resource use priority corresponding to the changed resource restriction level. Applications, processes, and threads can be assigned to different resource usage priority settings. For example, the target type is a thread, and the mobile terminal may first obtain each thread that runs, and query a target thread that needs to perform a resource restriction level change according to the target identifier, and then configure the target thread to use the resource priority corresponding to the changed resource restriction level. level. The target type is a process, and the mobile terminal optionally obtains each running process, and queries the target process that needs to perform the resource restriction level change according to the target identifier, and then acquires all threads running under the target process, and runs all threads under the target process. The resource usage priority corresponding to the changed resource restriction level is configured to implement the target process as the resource usage priority corresponding to the changed resource restriction level, but is not limited thereto. It can be understood that the application, the process, and the thread can also respectively correspond to other settings, for example, the target type is a process, and the mobile terminal can directly obtain the target process according to the target identifier, and configure the target process to correspond to the changed resource restriction level. Resource usage priority, etc.

In an embodiment, the mobile terminal may add a target corresponding to the target identifier to a resource group corresponding to the changed resource restriction level, and configure a resource usage priority corresponding to the resource group. Optionally, the mobile terminal may divide different resource groups based on a kernel Cgroup (control group) mechanism, and set a resource usage priority of each resource group by using a file node write configuration manner, and is allocated to each resource group. The application, process, or thread manages the time or proportion of resources, etc., where Cgroup is a physical resource that can be used to limit, record, and isolate applications, processes, or threads (such as CPU, The mechanism of memory, I / O and other resources). The mobile terminal can load a Cgroup configuration file, and the configuration file can record the divided resource groups, the resource usage priorities of the resource groups, and the resource scheduling policies corresponding to the resource usage priorities. The resource scheduling policy may include, but is not limited to, an application, a process, a thread, or the like, which is allocated to the resource group, a time when the resource is used, a proportion of the occupied resource, a resource identifier used, and the like. For example, the resource group corresponding to the common restriction level may be configured. An application, a process, a thread, or the like can use 30 seconds of CPU resources in one minute, and an application, a process, or a thread of a resource group corresponding to a common restriction level can use only CPU resources numbered X, but is not limited thereto. When you need to add a new resource group, or modify the resource usage priority and resource scheduling policy of the resource group, you can modify the Cgroup configuration file.

4 is a schematic diagram of a resource group in an embodiment. As shown in FIG. 4, four different resource restriction levels can be set in the mobile terminal, and four resource groups are divided, wherein the first resource group corresponds to an unrestricted level, and the second resource group corresponds to an ordinary limit. Level, the third resource group corresponds to the depth limit level, and the fourth resource group corresponds to the freeze level. The four resource groups may respectively correspond to different resource usage priorities, the resource usage priority of the first resource group may be higher than the second resource group, and the resource usage priority of the second resource group may be higher than the third resource. In the group, the resource usage priority of the third resource group may be higher than the fourth resource group. The first resource group at an unrestricted level does not limit resources such as CPU, memory, I/O, and network used by applications, processes, or threads. The second resource group of the general restriction level limits applications such as CPU, memory, I/O, and network to applications, processes, or threads. The third resource group at the depth limit level limits the use of resources such as CPU, memory, I/O, and network to applications, processes, or threads. The fourth resource group at the freeze level restricts applications such as CPU, memory, I/O, and network from being used by applications, processes, or threads. The mobile terminal can change and adjust the resource restriction levels of applications, processes, and threads according to the running characteristics of each application, process, or thread, and allocate applications, processes, and threads to corresponding resource groups, configurations, and resources. The resource usage priority corresponding to the group manages the resources used by each running application, process, and thread.

In this embodiment, the target identifier for performing the resource restriction level change is obtained, and the target type for performing the resource restriction level change is determined according to the target identifier, and the target category may include one of a thread, a process, and an application, and then according to the target category. The setting method is configured to configure the target corresponding to the target identifier as the resource usage priority corresponding to the changed resource restriction level, and can perform resource limitation from multiple dimensions such as threads, processes, and applications, and implement resource management comprehensively and flexibly. Optimize system performance and save power.

As shown in FIG. 5, in an embodiment, the operation 330 configures the target corresponding to the target identifier as the resource usage priority corresponding to the changed resource restriction level according to the setting manner corresponding to the target category, and includes the following operations:

In operation 502, when the target type is a thread, the thread corresponding to the target identifier is configured as a resource usage priority corresponding to the changed resource restriction level.

The mobile terminal determines the target type according to the target identifier that performs the resource restriction level change. When the target category is a thread, the mobile terminal may acquire all the currently running threads, and query the target thread that needs to perform the resource restriction level change according to the target identifier, and The target thread is added to the resource group corresponding to the changed resource restriction level, and the resource usage priority corresponding to the resource group is configured. After the target thread is assigned to the resource group corresponding to the changed resource restriction level, resources such as CPU, I/O, memory, and network may be used according to a preset resource scheduling policy corresponding to the resource group.

In operation 504, when the target type is a process, each thread included in the process corresponding to the target identifier is configured as a resource usage priority corresponding to the changed resource restriction level.

The mobile terminal determines the target type according to the target identifier that performs the resource restriction level change. When the target category is a process, the mobile terminal may acquire each currently running process, and query the target process that needs to perform the resource restriction level change according to the target identifier. The mobile terminal may add the target process to the resource group corresponding to the changed resource restriction level, and configure the resource usage priority corresponding to the resource group.

Optionally, after acquiring the target process, the mobile terminal may acquire all threads running under the target process, and add all threads running under the target process to the resource group corresponding to the changed resource restriction level, and configure and The resource usage priority corresponding to the resource group. All the threads running under the target process are configured with the resource usage priority corresponding to the changed resource restriction level, so that the target process can be configured to be the resource usage priority corresponding to the changed resource restriction level. After the target process is assigned to the resource group corresponding to the changed resource restriction level, resources such as CPU, I/O, memory, and network may be used according to a preset resource scheduling policy corresponding to the resource group. Further, All threads included in the target process can use resources according to the corresponding resource scheduling policy.

In operation 506, when the target type is an application, each process included in the application corresponding to the target identifier is configured as a resource usage priority corresponding to the changed resource restriction level.

The mobile terminal determines the target category according to the target identifier that changes the resource restriction level. When the target category is an application, the mobile terminal may obtain each application that is currently running, and query the target application that needs to perform the resource restriction level change according to the target identifier. The mobile terminal may add the target application to the resource group corresponding to the changed resource restriction level, and configure the resource usage priority corresponding to the resource group. Optionally, after acquiring the target application, the mobile terminal may acquire all the processes running in the target application, and add all the processes running in the target application to the resource group corresponding to the changed resource restriction level, and configure and The resource usage priority corresponding to the resource group.

As shown in FIG. 6, in one embodiment, the operation configures each process included in the application corresponding to the target identifier as a resource usage priority corresponding to the changed resource restriction level, and includes the following operations:

Operation 602: Acquire user group information of the application according to the target identifier.

When the application is running, the mobile terminal can assign different user groups to the running application, manage the permissions of the application through the user group, and the like. After obtaining the target application for performing the resource level change according to the target identifier, the mobile terminal obtains the user group information of the target application, and obtains each process running under the target application according to the user group information. The user group information may include a user group identifier or the like, wherein the user group identifier may be composed of one or more of numbers, letters, symbols, and the like.

Operation 604, querying a process identifier that has a mapping relationship with the user group information.

The mobile terminal can query the process identifiers that are in a mapping relationship with the user group information according to the user group information of the target application, thereby obtaining each process running under the target application. The kernel space layer of the mobile terminal can collect the user group information to which the process belongs in real time. When the process is created or destroyed, the kernel can allocate and release the user group information to which the process belongs, and the process can also occur during the running process. The case where the user group information is changed. The kernel space layer collects user group information of each process in real time, and can establish a mapping relationship between process information such as process ID and process name and user group information. When the mobile terminal needs to change the resource restriction level of the target application, the process identifier with the mapping relationship may be directly queried according to the user group information of the target application, and the process running under the target application is found by directly traversing all the running processes, and directly searching and The process ID of the user group information with mapping relationship is more convenient and faster.

Operation 606, the process matching the process identifier is configured as a resource usage priority corresponding to the changed resource restriction level.

After the mobile terminal queries the process identifier with the mapping relationship according to the user group information of the target application, all processes running under the target application can be obtained according to the process identifier. The mobile terminal may add all processes running under the target application to the resource group corresponding to the changed resource restriction level, and configure resource usage priorities corresponding to the changed resource restriction level for all processes running under the target application. , so that the purpose of configuring the target application as the resource usage priority corresponding to the changed resource restriction level can be achieved. After the target application is assigned to the resource group corresponding to the changed resource restriction level, the resource scheduling policy corresponding to the resource group may be used to use resources such as CPU, I/O, memory, and network. Further, All processes included in the target application can use resources according to the corresponding resource scheduling policy.

FIG. 7 is a schematic diagram of resource limitation from multiple dimensions such as threads, processes, and applications in one embodiment. As shown in FIG. 7, an application may include one or more processes, and one process may include one or more threads. The mobile terminal configures the resource usage priority of the application, and can implement the resource usage priority of each process included in the application. The mobile terminal configures the resource usage priority of the process, and can implement the resource usage priority of each thread included in the process. The mobile terminal can also separately configure the resource usage priority of a certain thread, and can configure resource usage priorities from multiple dimensions such as applications, processes, and threads, and limit resource usage.

In this embodiment, the mobile terminal can perform resource limitation from multiple dimensions such as threads, processes, and applications, comprehensively and flexibly implement resource management, optimize system performance, and save power consumption.

As shown in FIG. 8, in one embodiment, before the operation 310 obtains the target identifier for the resource restriction level change, the following operations are also included:

Operation 802 collects event data of each application running, each process, and each thread through the kernel space, and packages the event data into a data packet and transmits the data to the user space.

The virtual space of the mobile terminal may include kernel space and user space, the kernel space may be used to store the code and data of the kernel, and the user space may be used to store the code and data of the application. Kernel space has a high privilege level. Processes running in kernel space can have access to all hardware of the mobile terminal. User space has lower permissions. Processes running in user space can only use some resources of the system.

The mobile terminal can collect event data of each application running, each process, and each thread through the kernel space, and the event data may include, but is not limited to, an event type, an event time, an event content, a target identifier to which the event belongs, and the like. Event types may include, but are not limited to, communication events, creation events, exit events, change identification events, task events, and the like. The communication event may include a binder communication event and a socket communication event, wherein the binder is an inter-process communication mechanism that provides a remote procedure call function; the two programs on the network exchange data through a two-way communication connection, the connection One end is called a socket. Creating an event can refer to an event created by a process or thread. An exit event refers to an event that is exited by an application, process, or thread. A change identification event can refer to a process or a thread that changes its own identity, and the like. A task event can refer to a task, such as an application, a process, or a thread.

Optionally, the mobile terminal collects objects for different applications, processes, threads, and the like, and collects event data of different event types. The mobile terminal may pre-determine the type of the collected event and the corresponding collection object identifier. For example, the application or process of collecting the binder communication event may be pre-defined, or the application or process for collecting the socket communication event may be pre-defined. Different event types can respectively correspond to different collection object identifiers.

The mobile terminal collects event data of each application running, each process, and each thread through the kernel space, and can package the event data into a data packet according to the agreed packet format, and transmit the data packet to the user space. Optionally, the kernel space and the user space can communicate by means of an asynchronous netlink, which is a special inter-process communication that enables the user process to communicate with the kernel process. The kernel space transmits the event data to the user space by means of asynchronous communication, which is faster and more convenient than the active query mode of the user space, and can improve the transmission efficiency of the event data.

Operation 804, parsing the data packet through the user space to obtain event data.

Operation 806, analyzing the event data through the user space, determining the target identifier for performing the resource restriction level change, and the changed resource restriction level.

After receiving the data packet transmitted by the kernel space, the user space can parse the data packet to obtain event data. The mobile terminal can analyze the event data through the user space to determine the target identifier that needs to be changed by the resource restriction level. Optionally, the user space may analyze the event type, the event content, and the like in the event data, so as to determine whether the target identifier to which the event belongs needs to be changed by the resource restriction level.

In an embodiment, the mobile terminal analyzes the event data through the user space, and when detecting that the application or the process does not have a communication event such as a binder or a socket within a preset time period, the application or process that does not have a communication event may be improved. The resource restriction level reduces the resource usage priority of the application or process. The mobile terminal may determine that the identifier of the application or process in which the communication event has not occurred within the preset time period is the target identifier, and determine the increased resource restriction level. Optionally, when the user space detects that the application or the process does not have a communication event such as a binder or a socket within a preset time period, the user may first acquire the current resource restriction level of the application or the process in which the communication event does not occur, when no communication event occurs. When the current resource limit level of an application or process is a freeze level, the resource limit level may not be changed. When the current resource restriction level of the application or process that does not have a communication event is not a freeze level, the resource restriction level of the application or process in which the communication event does not occur may be increased, and the resource restriction level of the application or process is changed to the freeze level.

In one embodiment, when the user space detects that a communication event such as a binder or a socket occurs in an application or process, the resource restriction level of the application or process in which the communication event occurs may be reduced, and the resource usage priority of the application or process may be increased. The mobile terminal may determine the identity of the application or process in which the communication event occurred as the target identity and determine the reduced resource restriction level. Optionally, when the user space detects that a communication event such as a binder or a socket occurs in the application or the process, the current resource restriction level of the application or the process in which the communication event occurs may be acquired. The user space can determine, by the event data, whether the application or process has a communication event with an application or process running in the foreground, when the application or process has a communication event with an application or process running in the foreground, and the current resource limit of the application or process is high. When an application or process runs in the foreground, the resource limit level of the application or process can be reduced. Further, the application or process in which the communication event occurs may be configured with the same resource usage priority as the application or process running in the foreground, so that the application or process running in the foreground can be timely responded and the running speed is improved.

In one embodiment, the mobile terminal analyzes the event data through the user space. When detecting that the thread is performing the rendering task, the resource restriction level of the thread that is performing the rendering task may be lowered, and the resource usage priority of the thread is increased. The mobile terminal may determine, by the user space, the thread identifier that is performing the rendering task as the target identifier, and determine the reduced resource restriction level. Optionally, when the user space detects that the thread is performing the rendering task, the resource restriction level of the process running in the foreground may be obtained, and the thread that is performing the rendering task may be changed to the same resource restriction level as the process running in the foreground, and the guarantee is guaranteed. Render tasks are executed quickly, reducing the occurrence of stuck.

In this embodiment, the mobile terminal can collect event data of each application, each process, and each thread through the kernel space, and transmit the collected event data to the user space for analysis, which can provide a clue basis for more resource restriction level changes. It can make the resource restriction level adjustment of threads, processes and applications more accurate, improve resource management effect and system performance.

In one embodiment, a resource management method is provided, including the following operations:

Operation (1), obtain the target identifier for the resource restriction level change.

Optionally, before the operation (1), the method further includes: collecting, by using a kernel space, event data of each application, each process, and each thread, and packaging the event data into a data packet and transmitting the data to the user space; The data packet is obtained, and the event data is obtained; the event data is analyzed through the user space, and the target identifier for changing the resource restriction level is determined, and the changed resource restriction level is determined.

Optionally, the mobile terminal analyzes the event data by using a user space, determines a target identifier for performing a resource restriction level change, and the changed resource restriction level, including: analyzing event data through the user space, when detecting an application or a process. When the communication event does not occur within the preset time period, the resource restriction level of the application or process in which the communication event does not occur is increased; when the communication event occurs when the application or process is detected, the resource restriction level of the application or process in which the communication event occurs is reduced.

Optionally, the mobile terminal analyzes the event data by using a user space, determines a target identifier for performing resource restriction level change, and the changed resource restriction level, including: analyzing event data by using user space, when detecting that the thread is executing When rendering a task, lower the resource limit level of the thread that is executing the rendering task.

Operation (2), determining a target type for performing a resource restriction level change according to the target identifier, the target category including one of a thread, a process, and an application.

In operation (3), the target corresponding to the target identifier is configured as a resource usage priority corresponding to the changed resource restriction level according to a setting manner corresponding to the target type.

Optionally, the operation (3) includes: configuring, when the target category is a thread, a thread corresponding to the target identifier as a resource usage priority corresponding to the changed resource restriction level; when the target category is a process, Each thread included in the process corresponding to the target identifier is configured as a resource usage priority corresponding to the changed resource restriction level; when the target type is an application, each process included in the application corresponding to the target identifier is configured as the changed resource. The resource usage priority corresponding to the restriction level.

Optionally, the mobile terminal configures each process included in the application corresponding to the target identifier as a resource usage priority corresponding to the changed resource restriction level, including: acquiring user group information of the application according to the target identifier; querying and user group information A process ID with a mapping relationship; a process that matches the process ID is configured as a resource usage priority corresponding to the changed resource restriction level.

Optionally, the operation (3) includes: adding a target corresponding to the target identifier to the resource group corresponding to the changed resource restriction level, and configuring a resource usage priority corresponding to the resource group.

In this embodiment, the mobile terminal acquires the target identifier for performing the resource restriction level change, and determines the target type for performing the resource restriction level change according to the target identifier, and the target category may include one of a thread, a process, and an application, and the mobile terminal further The setting method corresponding to the target type configures the target corresponding to the target identifier as the resource usage priority corresponding to the changed resource restriction level, and the mobile terminal can perform resource limitation from multiple dimensions such as threads, processes, and applications, comprehensively, Flexible resource management, optimized system performance, and reduced power consumption.

It should be understood that the operations in the above-described flowcharts are sequentially displayed in accordance with the indication of the arrows, but the operations are not necessarily performed in the order indicated by the arrows. Except as explicitly stated herein, the execution of these operations is not strictly limited, and the operations may be performed in other sequences. Moreover, at least a part of the operations in the above flow diagram may include multiple sub-operations or multiple stages, which are not necessarily performed at the same time, but may be executed at different times, and these sub-operations or stages The order of execution is also not necessarily sequential, but may be performed alternately or alternately with at least a portion of the sub-operations or stages of other operations or other operations.

As shown in FIG. 9 , in one embodiment, a resource management apparatus 900 is provided, including an identifier obtaining module 910, a category determining module 920, and a configuration module 930.

The identifier obtaining module 910 is configured to acquire a target identifier for performing a resource restriction level change.

The category determining module 920 is configured to determine, according to the target identifier, a target category for performing a resource restriction level change, where the target category includes one of a thread, a process, and an application.

The configuration module 930 is configured to configure, according to the setting manner corresponding to the target category, a target corresponding to the target identifier as a resource usage priority corresponding to the changed resource restriction level.

Optionally, the configuration module 930 is further configured to add a target corresponding to the target identifier to the resource group corresponding to the changed resource restriction level, and configure a resource usage priority corresponding to the resource group.

In this embodiment, the target identifier for performing the resource restriction level change is obtained, and the target type for performing the resource restriction level change is determined according to the target identifier, and the target category may include one of a thread, a process, and an application, and then according to the target category. The setting method is configured to configure the target corresponding to the target identifier as the resource usage priority corresponding to the changed resource restriction level, and can perform resource limitation from multiple dimensions such as threads, processes, and applications, and implement resource management comprehensively and flexibly. Optimize system performance and save power.

In one embodiment, the configuration module 930 includes a thread configuration unit, a process configuration unit, and an application configuration unit.

The thread configuration unit is configured to configure, when the target type is a thread, a thread corresponding to the target identifier as a resource usage priority corresponding to the changed resource restriction level.

The process configuration unit is configured to configure, when the target type is a process, each thread included in the process corresponding to the target identifier as a resource usage priority corresponding to the changed resource restriction level.

The application configuration unit is configured to configure, when the target type is an application, each process included in the application corresponding to the target identifier as a resource usage priority corresponding to the changed resource restriction level.

Optionally, the application configuration unit includes a user group acquisition subunit, a query subunit, and a configuration subunit.

The user group acquisition subunit is configured to obtain user group information of the application according to the target identifier.

The query subunit is used to query the process identifier that has a mapping relationship with the user group information.

A configuration sub-unit configured to configure a process that matches the process ID to a resource usage priority corresponding to the changed resource restriction level.

In this embodiment, resources can be restricted from multiple dimensions such as threads, processes, and applications, and resource management can be implemented comprehensively and flexibly, system performance is optimized, and power consumption is saved.

In one embodiment, the resource management device 900 includes an identifier acquisition module 910, a category determination module 920, and a configuration module 930, and an acquisition module, an analysis module, and an analysis module.

The acquisition module is configured to collect event data of each application, each process, and each thread running through the kernel space, and package the event data into a data packet and transmit the data to the user space.

The parsing module is configured to parse the data packet through the user space to obtain event data.

The analysis module is configured to analyze the event data by using a user space, determine a target identifier for performing a resource restriction level change, and a changed resource restriction level.

Optionally, the analyzing module is further configured to analyze the event data by using a user space, and when detecting that the application or the process does not have a communication event within a preset time period, increasing a resource restriction level of the application or process that does not have a communication event occurs. .

Optionally, the analyzing module is further configured to reduce a resource restriction level of the application or process in which the communication event occurs when detecting that the application or process has a communication event.

Optionally, the analysis module is further configured to analyze the event data by using a user space, and when detecting that the thread is performing the rendering task, reduce a resource restriction level of the thread that is performing the rendering task.

In this embodiment, the event data of each application, each process, and each thread can be collected through the kernel space, and the collected event data is transmitted to the user space for analysis, which can provide more clue basis for resource limitation level change, and can be The resource restriction level adjustment of threads, processes, and applications is more accurate, improving resource management effects and system performance.

The embodiment of the present application further provides a mobile terminal. As shown in FIG. 10, for the convenience of description, only the parts related to the embodiments of the present application are shown. For the specific technical details not disclosed, refer to the method part of the embodiment of the present application. The mobile terminal can be any mobile device, a tablet computer, a personal digital assistant (PDA), a point of sale (POS), a car computer, a wearable device, and the like, and the mobile terminal is used as a mobile phone. :

FIG. 10 is a block diagram showing a partial structure of a mobile phone related to a mobile terminal provided by an embodiment of the present application. Referring to FIG. 10, the mobile phone includes: a radio frequency (RF) circuit 1010, a memory 1020, an input unit 1030, a display unit 1040, a sensor 1050, an audio circuit 1060, a wireless fidelity (WiFi) module 1070, and a processor 1080. And power supply 1090 and other components. It will be understood by those skilled in the art that the structure of the handset shown in FIG. 10 does not constitute a limitation to the handset, and may include more or less components than those illustrated, or some components may be combined, or different components may be arranged.

The RF circuit 1010 can be used for receiving and transmitting signals during the transmission and reception of information or during a call. The downlink information of the base station can be received and processed by the processor 1080. The uplink data can also be sent to the base station. Generally, RF circuits include, but are not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a Low Noise Amplifier (LNA), a duplexer, and the like. In addition, RF circuit 1010 can also communicate with the network and other devices via wireless communication. The above wireless communication may use any communication standard or protocol, including but not limited to GSM, GPRS, Code Division Multiple Access (CDMA), W-CDMA, Long Term Evolution (LTE), email, Short Messaging Service (SMS), etc.

The memory 1020 can be used to store software programs and modules, and the processor 1080 executes various functional applications and data processing of the mobile phone by running software programs and modules stored in the memory 1020. The memory 1020 may mainly include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application required for at least one function (such as an application of a sound playing function, an application of an image playing function, etc.); The data storage area can store data (such as audio data, address book, etc.) created according to the use of the mobile phone. Moreover, memory 1020 can include high speed random access memory, and can also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid state storage device.

The input unit 1030 can be configured to receive input numeric or character information and to generate key signal inputs related to user settings and function control of the handset 1000. Specifically, the input unit 1030 may include a touch panel 1032 and other input devices 1034. The touch panel 1032, which may also be referred to as a touch screen, can collect touch operations on or near the user (such as a user using a finger, a stylus, or the like on the touch panel 1032 or near the touch panel 1032. Operation) and drive the corresponding connection device according to a preset program. In one embodiment, the touch panel 1032 can include two portions of a touch detection device and a touch controller. Wherein, the touch detection device detects the touch orientation of the user, and detects a signal brought by the touch operation, and transmits the signal to the touch controller; the touch controller receives the touch information from the touch detection device, converts the touch information into contact coordinates, and sends the touch information. The processor 1080 is provided and can receive commands from the processor 1080 and execute them. In addition, the touch panel 1032 can be implemented in various types such as resistive, capacitive, infrared, and surface acoustic waves. In addition to the touch panel 1032, the input unit 1030 can also include other input devices 1034. Specifically, other input devices 1034 may include, but are not limited to, one or more of a physical keyboard, function keys (such as volume control buttons, switch buttons, etc.).

The display unit 1040 can be used to display information input by the user or information provided to the user as well as various menus of the mobile phone. The display unit 1040 can include a display panel 1042. In one embodiment, the display panel 1042 may be configured in the form of a liquid crystal display (LCD), an organic light-emitting diode (OLED), or the like. In one embodiment, the touch panel 1032 can cover the display panel 1042. When the touch panel 1032 detects a touch operation thereon or nearby, the touch panel 1032 transmits to the processor 1080 to determine the type of the touch event, and then the processor 1080 is The type of touch event provides a corresponding visual output on display panel 1042. Although in FIG. 10, the touch panel 1032 and the display panel 1042 are used as two independent components to implement the input and input functions of the mobile phone, in some embodiments, the touch panel 1032 can be integrated with the display panel 1042. Realize the input and output functions of the phone.

The handset 1000 can also include at least one type of sensor 1050, such as a light sensor, motion sensor, and other sensors. Specifically, the light sensor may include an ambient light sensor and a proximity sensor, wherein the ambient light sensor may adjust the brightness of the display panel 1042 according to the brightness of the ambient light, and the proximity sensor may close the display panel 1042 and/or when the mobile phone moves to the ear. Or backlight. The motion sensor may include an acceleration sensor, and the acceleration sensor can detect the magnitude of the acceleration in each direction, and the magnitude and direction of the gravity can be detected at rest, and can be used to identify the gesture of the mobile phone (such as horizontal and vertical screen switching), and vibration recognition related functions (such as Pedometer, tapping, etc.; in addition, the phone can also be equipped with gyroscopes, barometers, hygrometers, thermometers, infrared sensors and other sensors.

Audio circuitry 1060, speaker 1062, and microphone 1064 can provide an audio interface between the user and the handset. The audio circuit 1060 can transmit the converted electrical data of the received audio data to the speaker 1062, and convert it into a sound signal output by the speaker 1062. On the other hand, the microphone 1064 converts the collected sound signal into an electrical signal, and the audio circuit 1060. After receiving, it is converted into audio data, and then processed by the audio data output processor 1080, transmitted to another mobile phone via the RF circuit 1010, or outputted to the memory 1020 for subsequent processing.

WiFi is a short-range wireless transmission technology. The mobile phone through the WiFi module 1070 can help users to send and receive e-mail, browse the web and access streaming media, etc. It provides users with wireless broadband Internet access. Although FIG. 10 shows the WiFi module 1070, it can be understood that it does not belong to the essential configuration of the mobile phone 1000 and can be omitted as needed.

The processor 1080 is the control center of the handset, which connects various portions of the entire handset using various interfaces and lines, by executing or executing software programs and/or modules stored in the memory 1020, and invoking data stored in the memory 1020, The phone's various functions and processing data, so that the overall monitoring of the phone. In one embodiment, processor 1080 can include one or more processing units. In one embodiment, the processor 1080 can integrate an application processor and a modem, wherein the application processor primarily processes an operating system, a user interface, an application, etc.; the modem primarily processes wireless communications. It will be appreciated that the above described modem may also not be integrated into the processor 1080. For example, the processor 1080 can integrate an application processor and a baseband processor, and the baseband processor and other peripheral chips can form a modem. The mobile phone 1000 also includes a power source 1090 (such as a battery) for powering various components. Preferably, the power source can be logically coupled to the processor 1080 through a power management system to manage functions such as charging, discharging, and power management through the power management system.

In one embodiment, the handset 1000 may also include a camera, a Bluetooth module, and the like.

In the embodiment of the present application, the processor 880 included in the mobile terminal implements the foregoing resource management method when executing a computer program stored in a memory.

In one embodiment, the mobile terminal can include a memory 1020 and a processor 1080. The memory 1020 stores a computer program that, when executed by the processor 1080, causes the processor to perform the following operations:

Obtain the target ID for the resource restriction level change;

Determining a target type for performing a resource restriction level change according to the target identifier, and the target category includes one of a thread, a process, and an application;

The target corresponding to the target identifier is configured as the resource usage priority corresponding to the changed resource restriction level according to the setting manner corresponding to the target type.

In one embodiment, a computer readable storage medium is provided having stored thereon a computer program that, when executed by a processor, implements the resource management method described above.

In one embodiment, a computer program product comprising a computer program, when executed on a computer device, causes the computer device to perform the resource management method described above when executed.

One of ordinary skill in the art can understand that all or part of the process of implementing the above embodiments can be completed by a computer program to instruct related hardware, and the program can be stored in a non-volatile computer readable storage medium. Wherein, the program, when executed, may include the flow of an embodiment of the methods as described above. The storage medium may be a magnetic disk, an optical disk, a read-only memory (ROM), or the like.

Any reference to a memory, storage, database or other medium as used herein may include non-volatile and/or volatile memory. Suitable non-volatile memories can include read only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory. Volatile memory can include random access memory (RAM), which acts as an external cache. By way of illustration and not limitation, RAM is available in a variety of forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), dual data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronization. Link (Synchlink) DRAM (SLDRAM), Memory Bus (Rambus) Direct RAM (RDRAM), Direct Memory Bus Dynamic RAM (DRDRAM), and Memory Bus Dynamic RAM (RDRAM).

The technical features of the above-described embodiments may be arbitrarily combined. For the sake of brevity of description, all possible combinations of the technical features in the above embodiments are not described. However, as long as there is no contradiction between the combinations of these technical features, All should be considered as the scope of this manual.

The above-mentioned embodiments are merely illustrative of several embodiments of the present application, and the description thereof is more specific and detailed, but is not to be construed as limiting the scope of the invention. It should be noted that a number of variations and modifications may be made by those skilled in the art without departing from the spirit and scope of the present application. Therefore, the scope of the invention should be determined by the appended claims.

Claims (21)

A resource management method, including: Obtain the target ID for the resource restriction level change; Determining, according to the target identifier, a target category for performing a resource restriction level change, the target category including one of a thread, a process, and an application; and The target corresponding to the target identifier is configured as a resource usage priority corresponding to the changed resource restriction level according to a setting manner corresponding to the target type. The method according to claim 1, wherein the target corresponding to the target identifier is configured as a resource usage priority corresponding to the changed resource restriction level according to a setting manner corresponding to the target category ,include: When the target category is a thread, configuring a thread corresponding to the target identifier as a resource usage priority corresponding to the changed resource restriction level; When the target type is a process, each thread included in the process corresponding to the target identifier is configured as a resource usage priority corresponding to the changed resource restriction level; and When the target category is an application, each process included in the application corresponding to the target identifier is configured as a resource usage priority corresponding to the changed resource restriction level. The method according to claim 2, wherein the configuring each process included in the application corresponding to the target identifier as a resource usage priority corresponding to the changed resource restriction level comprises: Obtaining user group information of the application according to the target identifier; Querying a process identifier that has a mapping relationship with the user group information; and The process matching the process identifier is configured as a resource usage priority corresponding to the changed resource restriction level. The method according to claim 1, wherein the target corresponding to the target identifier is configured as a resource usage priority corresponding to the changed resource restriction level, and includes: Adding a target corresponding to the target identifier to a resource group corresponding to the changed resource restriction level, and configuring a resource usage priority corresponding to the resource group. The method according to any one of claims 1 to 4, wherein before the obtaining the target identifier for performing the resource restriction level change, the method further comprises: Collecting event data of each application running, each process, and each thread through the kernel space, and packaging the event data into a data packet and transmitting the data to the user space; Parsing the data packet by the user space to obtain the event data; and The event data is analyzed by the user space, and the target identifier for performing the resource restriction level change and the changed resource restriction level are determined. The method according to claim 5, wherein the analyzing the event data by the user space, determining a target identifier for performing a resource restriction level change, and a changed resource restriction level, comprising: Assessing the event data through the user space, and when detecting that the application or process does not have a communication event within a preset time period, increasing a resource restriction level of an application or process that does not have a communication event; and When it is detected that an application or process has a communication event, the resource restriction level of the application or process in which the communication event occurs is reduced. The method according to claim 5, wherein the analyzing the event data by the user space, determining a target identifier for performing a resource restriction level change, and a changed resource restriction level, comprising: The event data is analyzed by the user space, and when it is detected that the thread is performing a rendering task, the resource restriction level of the thread that is performing the rendering task is lowered. A mobile terminal includes a memory and a processor, wherein the memory stores a computer program, and when the computer program is executed by the processor, the processor performs the following operations: Obtain the target ID for the resource restriction level change; Determining, according to the target identifier, a target category for performing a resource restriction level change, the target category including one of a thread, a process, and an application; and The target corresponding to the target identifier is configured as a resource usage priority corresponding to the changed resource restriction level according to a setting manner corresponding to the target type. The mobile terminal according to claim 8, wherein when said computer program is executed by said processor, said processor causes said processor to perform said setting according to said target category, said When the target target corresponding to the target ID is configured as the resource usage priority corresponding to the changed resource restriction level, the following operations are also performed: When the target category is a thread, configuring a thread corresponding to the target identifier as a resource usage priority corresponding to the changed resource restriction level; When the target type is a process, each thread included in the process corresponding to the target identifier is configured as a resource usage priority corresponding to the changed resource restriction level; and When the target category is an application, each process included in the application corresponding to the target identifier is configured as a resource usage priority corresponding to the changed resource restriction level. The mobile terminal according to claim 9, wherein when the computer program is executed by the processor, the processor is configured to execute each process included in the application corresponding to the target identifier as When the resource usage priority corresponding to the changed resource restriction level is also performed, the following operations are also performed: Obtaining user group information of the application according to the target identifier; Querying a process identifier that has a mapping relationship with the user group information; and The process matching the process identifier is configured as a resource usage priority corresponding to the changed resource restriction level. The mobile terminal of claim 8, wherein when the computer program is executed by the processor, causing the processor to configure the target corresponding to the target identifier to be changed When the resource usage priority corresponds to the resource usage level, the following operations are also performed: Adding a target corresponding to the target identifier to a resource group corresponding to the changed resource restriction level, and configuring a resource usage priority corresponding to the resource group. The mobile terminal according to any one of claims 8 to 11, wherein, when said computer program is executed by said processor, said processor is caused to perform said acquisition of a target identifier for performing a resource restriction level change, Also do the following: Collecting event data of each application running, each process, and each thread through the kernel space, and packaging the event data into a data packet and transmitting the data to the user space; Parsing the data packet by the user space to obtain the event data; and The event data is analyzed by the user space, and the target identifier for performing the resource restriction level change and the changed resource restriction level are determined. The mobile terminal according to claim 12, wherein when the computer program is executed by the processor, the processor causes the processor to perform analysis on the event data through the user space, and determines to perform When the target ID of the resource limit level change and the changed resource limit level, the following operations are also performed: Assessing the event data through the user space, and when detecting that the application or process does not have a communication event within a preset time period, increasing a resource restriction level of an application or process that does not have a communication event; and When it is detected that an application or process has a communication event, the resource restriction level of the application or process in which the communication event occurs is reduced. The mobile terminal according to claim 12, wherein when the computer program is executed by the processor, the processor causes the processor to perform analysis on the event data through the user space, and determines to perform When the target ID of the resource limit level change and the changed resource limit level, the following operations are also performed: The event data is analyzed by the user space, and when it is detected that the thread is performing a rendering task, the resource restriction level of the thread that is performing the rendering task is lowered. A computer readable storage medium having stored thereon a computer program, wherein when the computer program is executed by a processor, the processor causes the processor to: Obtain the target ID for the resource restriction level change; Determining, according to the target identifier, a target category for performing a resource restriction level change, the target category including one of a thread, a process, and an application; and The target corresponding to the target identifier is configured as a resource usage priority corresponding to the changed resource restriction level according to a setting manner corresponding to the target type. The computer readable storage medium according to claim 15, wherein when said computer program is executed by said processor, said processor is caused to perform said setting according to said target category When the target corresponding to the target identifier is configured as the resource usage priority corresponding to the changed resource restriction level, the following operations are also performed: When the target category is a thread, configuring a thread corresponding to the target identifier as a resource usage priority corresponding to the changed resource restriction level; When the target type is a process, each thread included in the process corresponding to the target identifier is configured as a resource usage priority corresponding to the changed resource restriction level; and When the target category is an application, each process included in the application corresponding to the target identifier is configured as a resource usage priority corresponding to the changed resource restriction level. A computer readable storage medium according to claim 16, wherein said computer program is executed by said processor such that said processor is executing each of said applications to be included in said application corresponding to said target identification When the process is configured to use the resource usage priority corresponding to the changed resource restriction level, the following operations are also performed: Obtaining user group information of the application according to the target identifier; Querying a process identifier that has a mapping relationship with the user group information; and The process matching the process identifier is configured as a resource usage priority corresponding to the changed resource restriction level. A computer readable storage medium according to claim 15 wherein said computer program is executed by said processor such that said processor is configured to perform a target corresponding to said target identification as When the resource usage priority corresponding to the changed resource restriction level is also performed, the following operations are also performed: Adding a target corresponding to the target identifier to a resource group corresponding to the changed resource restriction level, and configuring a resource usage priority corresponding to the resource group. A computer readable storage medium according to any one of claims 15 to 18, wherein said computer program, when executed by said processor, causes said processor to perform said acquisition for a target of resource restriction level change Before you identify, you also do the following: Collecting event data of each application running, each process, and each thread through the kernel space, and packaging the event data into a data packet and transmitting the data to the user space; Parsing the data packet by the user space to obtain the event data; and The event data is analyzed by the user space, and the target identifier for performing the resource restriction level change and the changed resource restriction level are determined. A computer readable storage medium according to claim 19, wherein said computer program, when executed by said processor, causes said processor to perform said analyzing said event data through said user space To determine the target ID for the resource limit level change and the changed resource limit level, do the following: Assessing the event data through the user space, and when detecting that the application or process does not have a communication event within a preset time period, increasing a resource restriction level of an application or process that does not have a communication event; and When it is detected that an application or process has a communication event, the resource restriction level of the application or process in which the communication event occurs is reduced. A computer readable storage medium according to claim 19, wherein said computer program, when executed by said processor, causes said processor to perform said analyzing said event data through said user space To determine the target ID for the resource limit level change and the changed resource limit level, do the following: The event data is analyzed by the user space, and when it is detected that the thread is performing a rendering task, the resource restriction level of the thread that is performing the rendering task is lowered.

Images