WO2019128545A1

WO2019128545A1 - Process handling method, and electronic device and computer-readable storage medium

Info

Publication number: WO2019128545A1
Application number: PCT/CN2018/116526
Authority: WO
Inventors: 方攀; 陈岩
Original assignee: Oppo广东移动通信有限公司
Priority date: 2017-12-29
Filing date: 2018-11-20
Publication date: 2019-07-04
Also published as: CN109992394A; CN109992394B

Abstract

A process handling method, comprising: acquiring process information of a daemon process running in the background; detecting whether the process information includes a pre-set keyword; and when the keyword is included, carrying out resource restriction on the daemon process.

Description

Process processing method, electronic device, 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. 201711484424.X, entitled "Process Processing Method and Apparatus, Electronic Apparatus, Computer Readable Storage Medium", The entire contents are incorporated herein by reference.

Technical field

The present application relates to the field of data processing, and in particular, to a process processing method, an electronic device, and a computer readable storage medium.

Background technique

With the development of mobile communication technologies, mobile operating systems provide a method for resource limitation of application processes. In a traditional operating system, a process of a foreground application (that is, a foreground process) is usually not resource-restricted, and a process (ie, a background process) of an application running in the background that is not related to the foreground application is occupied by resources. Limits to provide more resources for the foreground application process to improve the operational efficiency of the foreground application.

However, in the traditional method, there are always some hidden processes, such as the application installation process, which makes the system difficult to detect and limit, which causes these hidden background processes to occupy more resources, which affects the operating efficiency of the foreground application.

Summary of the invention

The embodiment of the present application provides a process processing method, an electronic device, and a computer readable storage medium.

A process processing method, the method comprising:

Get the process information of the daemon running in the background;

Detecting whether the process information includes a preset keyword;

When the keyword is included, resource restrictions are imposed on the daemon.

A computer readable storage medium having stored thereon a computer program, the computer program being executed by a processor, causing the processor to: acquire process information of a daemon running in the background; and detect the process information Whether the preset keyword is included; when the keyword is included, the resource is restricted to the daemon.

An electronic device comprising a memory, a processor, and a computer program stored on the memory and operable on the processor, the processor executing the computer program, causing the processor to perform the following operations: fetching in the background Process information of the daemon process; detecting whether the process information includes a preset keyword; when the keyword is included, performing resource limitation on the daemon process.

DRAWINGS

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

FIG. 1 is a schematic diagram showing the internal structure of an electronic device in an embodiment.

2 is a partial block diagram of a system in an electronic device in an embodiment.

3 is a flow chart of a process processing method in an embodiment.

4 is a flow chart of a process processing method in another embodiment.

Figure 5 is a block diagram showing the structure of a process processing apparatus in an embodiment.

Figure 6 is a block diagram showing the structure of a process processing apparatus in another embodiment.

Figure 7 is a block diagram showing a portion of the structure of a handset in an 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, the first keyword may be referred to as a second keyword without departing from the scope of the present application, and similarly, the second keyword may be referred to as a first keyword. Both the first keyword and the second keyword are keywords, but they are not the same keyword.

In one embodiment, as shown in FIG. 1, an internal structure diagram of an electronic device is provided. The electronic device includes a processor, memory, and display screen connected by a system bus. The processor is used to provide computing and control capabilities to support the operation of the entire electronic device. The memory is used to store data, programs, and/or instruction codes, etc., and the memory stores at least one computer program, which can be executed by the processor to implement the process processing method applicable to the electronic device provided in the embodiments of the present application. The memory may include a non-volatile storage medium such as a magnetic disk, an optical disk, a read-only memory (ROM), or a random storage memory (Random-Access-Memory, RAM). For example, in one embodiment, the memory includes a non-volatile storage medium and an internal memory. Non-volatile storage media stores operating systems, databases, and computer programs. The database stores data related to a process processing method provided by the above various embodiments, such as information such as the name of each process or application. The computer program can be executed by a processor for implementing a process processing method provided by various embodiments of the present application. The internal memory provides a cached operating environment for operating systems, databases, and computer programs in non-volatile storage media. The display screen can be a touch screen, such as a capacitive screen or an electronic screen, for displaying interface information of an application corresponding to the foreground process, and can also be used for detecting a touch operation acting on the display screen, and generating corresponding instructions, such as performing front and back Application switching instructions, etc.

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 on the electronic device to which the solution of the present application is applied. The specific electronic device may be It includes more or fewer components than those shown in the figures, or some components are combined, or have different component arrangements. For example, the electronic device further includes a network interface connected through a system bus, and the network interface may be an Ethernet card or a wireless network card, etc., for communicating with an external electronic device, for example, for communicating with a server. For example, there is no display connected through the system bus on the electronic device, or an external display device can be connected.

In one embodiment, as shown in FIG. 2, a partial architectural diagram of an electronic device is provided. The architecture of the electronic device includes a JAVA spatial layer 210, a local framework layer 220, and a kernel space layer 230. The JAVA spatial layer 210 may include a freeze management application 212. The electronic device may implement a freeze policy for each application through the freeze management application 212, and perform freezing and thawing management operations on the related applications of the background power consumption. The resource priority and restriction management module 222 and the platform freeze management module 224 are included in the local framework layer 220. The electronic device can maintain different applications in different priorities and different resource organizations through the resource priority and limit management module 222, and adjust the resource group of the application according to the requirements of the upper layer to achieve optimized performance and save power. effect. The electronic device can allocate the tasks that can be frozen in the background to the frozen layer corresponding to the preset different levels according to the length of the entering freeze time through the platform freeze management module 224. Optionally, the frozen layer can include three, respectively: the CPU Limit sleep mode, CPU freeze sleep mode, 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; 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. The kernel space layer 230 includes a UID management module 231, a Cgroup module 232, a Binder management module 233, a process memory recovery module 234, and a freeze timeout exit module 235. 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 232 is used to provide a complete set of Central Processing Unit (CPU), CPUSET, memory, input/output (I/O), and Net related resource restriction mechanisms. The Binder management module 233 is used to implement the priority control of the background binder communication. The interface module of the local framework layer 220 includes a binder interface developed to the upper layer, and the upper layer framework or application sends a resource restriction or frozen instruction to the resource priority and restriction management module 222 and the platform freeze management module 224 through the provided binder interface. . The process memory recovery module 234 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 235 is configured to resolve an exception generated by the freeze timeout scenario. Through the above architecture, the process processing method in various embodiments of the present application can be implemented.

In an embodiment, as shown in FIG. 3, a process processing method is provided. The embodiment is applied to the electronic device shown in FIG. 1 as an example for description. The method includes:

In operation 302, the process information of the daemon running in the background is obtained.

There are multiple processes in the electronic device. The process is a basic operation of a program on a certain data set in a computer. It is the basic unit for resource allocation and scheduling, and is the basis of the operating system structure. The operation of an application (APP) is usually reflected by the operation of multiple related processes. The process involved in the foreground application runtime is the foreground process, and the process involved in the background application runtime is the background process. The electronic device can obtain the foreground process when the foreground application is running. Each process can be executed as a task. The task formed by the foreground process is the foreground task, and the task formed by the background process is the background task.

In the process running in the background, there is a class of processes as daemons (Daemon processes). The daemon is a server program that runs all the time. It usually runs in the background of the system. There is no control terminal and no interaction with the foreground. The daemon is generally used as a system service. It is a long-running process. It usually runs after the system is started. It ends when it is closed.

The electronic device may acquire process information of the daemon running in the background according to a preset frequency or according to the detected user operation instruction. The process information includes basic information such as the User Identifier (UID), Process Identifier (PID), and process name of the process.

In an embodiment, the electronic device may update the process running in the foreground and the process running in the background according to the running state of the electronic device. Optionally, the foreground process pool of the corresponding foreground process and the background process of the background process may be set. Pool. Add the process information of the foreground process to the foreground process pool, add the process information of the background process to the background process pool, and update the foreground process pool and the background process pool when detecting that the process running in the background changes. Process ID. For example, when it is detected that the process B changes from the background process to the foreground process, the process information of the process B can be moved from the background process pool to the foreground process pool.

In an embodiment, the electronic device may set a corresponding foreground mark or background mark for each process, determine a process with a foreground mark as a foreground process, determine a process with a background mark as a background process, and obtain a background mark. Process information for the daemon.

In operation 304, it is detected whether the preset keyword is included in the process information.

The electronic device presets at least one keyword, which is one or more of a preset number of digits, letters or other characters. This keyword is information common to the process information of the daemon that can be resource limited. The electronic device may detect one or more field information preset in the process information to determine whether the detected field information includes the corresponding keyword. For example, it can detect whether the process name and the one or more fields such as UID contain corresponding keywords.

Operation 306, when the keyword is included, resource limits are imposed on the daemon.

Optionally, when the preset information is included in the incoming information, the resource is restricted to the corresponding daemon. The resources include CPU resources, CPUSET resources, memory resources, I/O resources, and Net related resources. The electronic device may limit one or more of the above resources to prevent the daemon process from occupying more resources and affecting the processing efficiency of the foreground process.

In one embodiment, resource limits are imposed on the daemon, including: limiting CPU resources and I/O resources occupied by the daemon.

Optionally, since such a daemon process generally occupies more CPU resources and I/O resources, the electronic device can further improve the CPU that can be used by the foreground application by limiting CPU resources and I/O resources of such resources. Resources and I/O resources improve the processing efficiency of the foreground application.

In the process processing method provided by the embodiment, the electronic device can improve the detection efficiency of detecting the relatively hidden daemon process by detecting the keyword of the daemon process, and include the corresponding key in the detected process information. The word daemon performs resource restrictions to prevent it from occupying more resources, so that more resources are tilted toward the foreground application, and the processing efficiency of the foreground application is improved through the process.

In one embodiment, the keyword includes a first keyword and a second keyword; operation 304 includes: detecting whether the process name in the process information includes the first keyword; and detecting whether the user identity UID in the process information includes the second Keyword; operation 306 includes: resource limiting the daemon process when the first keyword and the second keyword are included.

The keywords that the electronic device needs to retrieve include two types, a first keyword and a second keyword. The first keyword and the second keyword are respectively composed of one or more of different numbers, letters or other characters of a preset length. The first keyword is a keyword that detects the process name, and the second keyword is a keyword that detects the UID.

The electronic device can obtain the process name and the UID in the process information, and detect whether the process name includes the first keyword and whether the second keyword is included in the UID. Optionally, the electronic device can perform detection of the first keyword and the second keyword at the same time, and the detection order of the two is not necessarily limited. When it is detected that the process name includes the first keyword, and the UID includes the second keyword, the electronic device may perform resource limitation on the daemon.

In this embodiment, the electronic device further improves the accuracy of detecting the daemon process that can perform resource limitation by performing keyword detection in the process name and the UID.

In an embodiment, before the resource restriction is performed on the daemon, the method further includes: acquiring an application category of the foreground application, and performing resource limitation on the daemon when the application category is a game application.

Optionally, the electronic device can detect an operating state of the front-end application of the local device, and when the current running application is in the running state of the game, perform a resource limiting operation on the daemon. The electronic device can record application categories to which different applications belong, and the application categories may include game applications, social applications, map navigation applications, online shopping payment applications, call communication applications, browser applications, and the like. The electronic device can obtain the application category of the application running in the foreground, and the application running in the foreground is the foreground application. When it is detected that the foreground application is a game application, the electronic device can perform a resource restriction operation on the daemon.

In this embodiment, since the application of the game class is in the process of running, it usually needs to occupy a large resource to maintain smooth running, and when there is a daemon hidden in the background, it also occupies certain resources and affects the game. The running efficiency of the application, therefore, when detecting that the foreground application is a game application, the electronic device can limit the resources of the detected daemon, which can further improve the operating efficiency of the game application.

In one embodiment, resource limits are imposed on the daemon, including: reducing the priority of the daemon; and limiting resources to the daemon based on the reduced priority.

Optionally, for each process running in the front background, the electronic device is set to correspond to different priorities, and different priorities correspond to different resource limitation levels. The higher the priority, the lower the limit on the resources available to it. Generally, the foreground process is set to the highest priority and is relatively higher than the priority of the background process. The same process, when running in the foreground and running in the background, does not have the same priority. And the same background process, the priority in different states is not necessarily the same. For example, when the same background process is different at different times or when the foreground process is different, the priority of the background process is not necessarily the same.

For the queried daemon, the electronic device can adjust its priority to lower the priority of the daemon, and limit the resource to the daemon according to the reduced priority to increase the resource limit on the daemon. The extent that more resources are tilted toward the foreground application.

For example, the electronic device can set priority 1 to priority 5 according to the priority, and the priority is 5 levels, and the higher the priority, the lower the limit on the resources that can be used. When the priority of the daemon A is 3, and the process information of the daemon A includes the above keywords, the electronic device adjusts the priority of the daemon A from the priority 3 to the priority 4 or preferentially. Level 5, etc., to retain more available resources for the foreground application to further improve the operational efficiency of the foreground application.

In one embodiment, the daemon process performs resource limitation, including: calculating a limit on the daemon process according to the local resource utilization rate; and limiting the resource to the daemon process according to the degree of restriction.

Optionally, the local resource utilization includes utilization of one or more resources of the CPU resource, the I/O resource, the memory resource, and the like. The resource utilization reflects the idle state of the resources of the electronic device, and the lower the resource utilization, the more idle resources are corresponding. The electronic device can calculate the limit on the daemon process according to the current resource utilization rate, so that when the resource utilization rate is larger, the restriction on the daemon process is higher, and the resource utilization rate is smaller, the daemon process is restricted. The degree is correspondingly smaller.

For example, taking a resource as an example of memory, m may be any suitable empirical value when the number of available I/O resources currently limited to the daemon is m or unlimited. When the current resource utilization rate of the electronic device is a%, the electronic device may limit the number of I/O resources of the daemon to n, and when the current resource utilization rate of the electronic device is b%, the electronic device may The number of I/O resources for this daemon is limited to k. Wherein b and k are both smaller than m, and when a is smaller than b, n is greater than k.

In an embodiment, the electronic device may reduce the priority of the daemon according to the local resource utilization, and limit the resource to the daemon by the degree of resource limitation corresponding to the different priorities. The lower the resource utilization rate, the smaller the priority of the daemon process, and the higher the resource utilization rate, the greater the decrease in the priority of the daemon process.

The electronic device calculates the degree of restriction on the daemon process according to the local resource utilization rate, and limits the daemon process according to the degree of the restriction, so that the degree of limitation on the daemon process when the local resource utilization is large is large. Larger, when the utilization of local resources is low, the electronic device has a relatively small restriction on the daemon process, so that the degree of restriction on the daemon is balanced with the local resource utilization, and the processing efficiency of the foreground application is not affected. In large cases, the electronic device does not impose too many restrictions on the daemon process, and also avoids the processing efficiency of the daemon process is too low.

In an embodiment, before the resource restriction on the daemon, the method further includes: detecting whether the daemon is dependent on the foreground process; and when the daemon is dependent on the foreground process, adjusting the priority of the daemon to match the foreground process; When the daemon is not dependent on the foreground process, the resource limit is enforced on the daemon.

In an embodiment, the electronic device performs the dependency detection operation on the daemon, and may perform detection in any process before the foregoing operation 306. For example, the dependency relationship may be detected first, when there is no dependency relationship, Perform keyword detection. When there is no dependency and contains the above keywords, the daemon is executed to perform resource limitation.

Dependency indicates that a process needs to utilize data from one or more processes in order to successfully implement the relationship to the execution of that process. The two processes that have dependencies are the dependent process and the dependent process, and the electronic device detects the background running daemon that will be depended by the foreground process as the background process that is depended by the foreground process. The electronic device may set a corresponding dependency flag to the detected background process that is depended by the foreground process, and obtain a background process with the dependency mark from the background process pool, and determine the background process as a background that is depended by the foreground process. process.

For the daemon, when dependent on the foreground process, the electronic device can determine that the daemon process is a background process that is depended by the foreground process, and the priority of the daemon process that is dependent on the foreground process is adjusted to match the priority of the foreground process. . The foreground process is the process running in the foreground.

Optionally, for the queried daemon that is queried by the foreground process, the electronic device may adjust its priority so that the adjusted priority matches the priority of the foreground process. The electronic device can set different matching priorities of the daemon processes that are dependent on the foreground process and the foreground priority. According to the matching relationship, the electronic device can obtain a corresponding priority for the daemon process that is dependent on the foreground process, and adjust the priority of the daemon process that is dependent on the foreground process to the priority, and reduce the guard against the foreground process. The degree of resource throttling of a process matches the extent to which resources that can be used by daemons that are dependent on the foreground process match the limits of the foreground process.

In one embodiment, the priority that matches the priority of the foreground process may be the same priority as the foreground process. That is, the electronic device can adjust the priority of the daemon process that is depended by the foreground process to the same priority as the foreground process, so that the degree of limitation on the resources that can be used by the daemon process that is dependent on the foreground process is related to the foreground process. The limits are the same.

By detecting the dependency of the daemon, the electronic device adjusts the priority of the daemon that the foreground process depends on to the priority of the foreground process. Because the foreground process has the highest priority, the limit of the available resources is the lowest, and the background process has the lower priority to prevent the background process from occupying too many resources and affecting the foreground application. However, in the background process, there is a situation that is depended on by the foreground process. When the dependent background process is executed efficiently, it also affects the foreground process. The application adjusts the priority of the dependent daemon to the priority matching the foreground priority, thereby reducing the limit of the resources that the dependent daemon can use, thereby improving the dependent daemon. Processing efficiency. Since the processing efficiency of the dependent daemon is improved, the processing efficiency of the foreground process depending on the dependent daemon is also improved.

In one embodiment, as shown in FIG. 4, another process processing method is provided, the method comprising:

Operation 402: Obtain process information of a daemon running in the background.

Optionally, the process information includes the process name and UID described above. The electronic device scans all processes running locally to get the process name and UID of the daemon running in the background. Optionally, the electronic device can acquire the process name and the UID of the multiple daemons at the same time, and obtain the process of the next round of the daemon process after completing the detection of one of the daemons in a preset order. Information is detected and detected, wherein the number of processes included in each round may be one or more and may not be the same.

In one embodiment, the electronic device may send a detection adjustment instruction to the daemon process to the resource priority and restriction management module 222 through the Binder interface through the freeze management application 210 in FIG. 2, and the resource priority and restriction management module 222 passes The received detection instruction acquires the process information of the daemon.

Operation 404, detecting whether the process name in the process information includes the first keyword; and detecting whether the user identity UID in the process information includes the second keyword.

In one embodiment, the first keyword may be "dex2oat." The second keyword may be a keyword of "2999", and the electronic device may detect whether the process name includes "dex2oat" and whether the UID is preceded by a UID starting with "2999", wherein "2999" may be included after A plurality of consecutive 9, such as "299999", "2999999" or "29999999".

Operation 406, when the first keyword and the second keyword are included, and the foreground application is a game application, the resource limitation is performed on the daemon, and the CPU resources and I/O resources occupied by the daemon are restricted.

In an embodiment, when the first keyword of the daemon includes "dex2oat", and the first 4 digits of the UID are "2999", or contains more consecutive "9", the electronic device may determine that the daemon is Apply the installation process and mark the identified application installation process. At the same time, the electronic device can detect whether the foreground application is a game application, and when it is a game application, limit the occupied CPU resources and I/O resources of the daemon. For example, if the CPU of the electronic device is an 8-core or a 6-core CPU, the CPU that can be occupied by the daemon can be limited to only one core, so as to provide more CPU resources for the game application running in the foreground. When the current application uses 30 or 20 I/O interfaces, the electronic device can limit it to occupy only 3 I/O interfaces to provide more I/O resources for use by game applications running in the foreground. .

In one embodiment, the electronic device may send a resource limit instruction to the detected daemon to the resource priority and limit management module 222 via the Binder interface. Optionally, the resource limit instruction may be a priority adjustment instruction to the daemon. After receiving the priority adjustment instruction, the resource priority and limit management module 222 lowers the priority of the corresponding daemon process, increases the resource limit thereof, and prevents the foreground application from being stuck.

In an embodiment, before limiting the resources of the daemon, the method further includes: detecting whether the daemon is dependent on the foreground process, and when the daemon is not dependent on the foreground process, the electronic device may use CPU resources occupied by the daemon. I/O resources are restricted.

In one embodiment, when there is socket communication, binder communication, memory sharing, or lock waiting between the daemon and the foreground process, the electronic device can determine that there is a communication mechanism between the background process and the foreground process.

You can detect whether there is a background process that has communication mechanism with the foreground process by any one or several of the following methods:

(1) detecting whether there is a background process having at least one of socket and binder communication with the foreground process;

(2) detecting whether there is a background process for memory sharing with the foreground process;

(3) Check if there is a background process waiting for the foreground process to wait on the lock resource.

The electronic device can set a detection mechanism for the Binder communication between the foreground process and the background process in the Binder driver, and call the detection mechanism set in the Binder driver to detect the background process in which the Binder communication exists with the foreground process, and the detection will be detected. The background process is determined to be a background process that is dependent on the foreground process.

In one embodiment, the electronic device can detect individual lock resources, including thread locks, file handles, signals, and the like. For each lock resource, it can be detected whether a lock wait occurs, that is, the lock resource waits. When it is detected that a lock wait is generated, it may be further detected whether the behavior of the occurrence of the wait occurs on the foreground process. If so, all the background processes waiting for the lock resource are traversed, and the detected background processes waiting on the lock resource are all determined to be background processes that are depended by the foreground process.

In one embodiment, the electronic device may set a lock resource monitoring module and a priority adjustment module in a kernel space of the operating system, and embed the lock resource monitoring module into the kernel's native waiting interface. Through the lock resource monitoring module, detecting thread locks, file handles, signals, etc. lock various lock resources, whether a wait occurs, whether the waiting behavior occurs on the foreground process, and if it occurs on the foreground task, it will detect The message is sent to the priority adjustment module. The electronic device traverses all the background threads waiting for the lock resource by the priority adjustment, and determines these background processes as the background processes that are depended by the foreground process. And the priority adjustment module adjusts the priority of the corresponding daemon to the matching priority.

In an embodiment, before the operation 304, the method further includes: when there is a synchronization mechanism between the background process and the foreground process, determining that the daemon having the synchronization mechanism is a background process that is dependent on the foreground process.

The electronic device can also detect the background process in the background process set by calling the futex system call, whether there is a background process having a synchronization mechanism with the foreground process, and determine the background process with the synchronization mechanism as the background process that is depended by the foreground process.

In concurrent programming, access to public variables must be restricted by each process. This constraint is called synchronization. In the operating system, the user mode synchronization mechanism can be implemented by calling the futex system call. Among them, the user state refers to the non-privileged state. Synchronization mechanisms include semaphores, mutex locks, and more. When a background process that detects any kind of synchronization mechanism with the foreground process is detected by the futex system call, the detected background process may be determined as a background process that is dependent on the foreground process.

The electronic device determines, by the detection of at least one of a communication mechanism and a synchronization mechanism between the foreground process and the background process, the detected background process having at least one of a communication mechanism and a synchronization mechanism with the foreground process as being forwarded The background process that the process depends on can improve the efficiency of detecting the daemons that are dependent on the foreground process.

In the above process processing method, when the current application is a game application, since the normal game application needs to occupy a large CPU resource and I/O resources, the smoothness of the game operation can be guaranteed, and in the background process, there is an application installation. Process, the application installation process usually occupies large CPU resources and I/O resources during the running process, and such application installation process has greater concealment, making the electronic device difficult to detect, through the daemon process. The process name and the UID are detected. When the process name includes a first keyword that is common to the application installation process, and the UID includes a second keyword that is common to the application installation process, the electronic device may use the CPU occupied by the daemon. Restrictions on resources and I/O resources prevent the daemon from consuming CPU resources and I/O resources, improving the processing efficiency of game applications running in the foreground.

It should be understood that although the operations in the flowcharts of FIGS. 3 and 4 are sequentially displayed as indicated by the arrows, these 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 some of the operations in FIGS. 3 and 4 may include multiple sub-operations or multiple stages, which are not necessarily performed at the same time, but may be performed at different times, or The order of execution of the stages 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.

In one embodiment, as shown in FIG. 5, a process processing apparatus is provided. The apparatus includes a process acquisition module 502, a keyword detection module 504, and a process processing module 506. The process obtaining module 502 is configured to: process the process information of the daemon running in the background; the keyword detection module 504 is configured to detect whether the process information includes a preset keyword; and the process processing module 506 is configured to: when the keyword is included, Resource restrictions on the daemon.

In an embodiment, the keyword includes a first keyword and a second keyword; the keyword detection module 504 is configured to detect whether the process name in the process information includes the first keyword; and detect whether the user identity identifier UID in the process information is The second keyword is included; the process processing module 506 is configured to perform resource limitation on the daemon when the first keyword and the second keyword are included.

In one embodiment, the process processing module 506 is further configured to obtain an application category of the foreground application, and when the application category is a game application, resource limitation is performed on the daemon.

In one embodiment, the process processing module 506 is further configured to reduce the priority of the daemon process; resource limiting the daemon process according to the reduced priority.

In one embodiment, the process processing module 506 is further configured to calculate a limit on the daemon process according to the local resource utilization rate; and limit the resource to the daemon process according to the degree of restriction.

In one embodiment, the process processing module 506 is further configured to limit CPU resources and I/O resources occupied by the daemon.

In one embodiment, as shown in FIG. 6, another process processing apparatus is provided, the apparatus further comprising:

The dependency detection module 508 is configured to detect whether the daemon process is dependent on the foreground process.

The process processing module 506 is further configured to: when the daemon process is dependent on the foreground process, adjust the priority of the daemon to match the foreground process; when the daemon is not dependent on the foreground process, and the process information includes the keyword, execute Resource restrictions on the daemon.

The above-mentioned process processing device can improve the detection efficiency of detecting the relatively hidden daemon process by detecting the keyword of the daemon process, and perform resources for the daemon process including the corresponding keyword in the detected process information. Restrictions prevent them from occupying more resources, so that more resources are tilted toward the foreground application, and the processing efficiency of the foreground application is improved through the process.

The division of each module in the above process processing device is for illustrative purposes only. In other embodiments, the process processing device may be divided into different modules as needed to complete all or part of the functions of the process processing device.

For the specific definition of the process processing device, reference may be made to the limitation of the process processing method in the above, and details are not described herein again. Each of the above-described process processing devices may be implemented in whole or in part by software, hardware, and combinations thereof. Each of the above modules may be embedded in or independent of the processor in the electronic device, or may be stored in a memory in the electronic device in a software format, so that the processor calls to perform operations corresponding to the above modules.

The implementation of each module in the process processing apparatus provided in the embodiments of the present application may be in the form of a computer program. The computer program can run on an electronic device such as a terminal or a server. The program modules of the computer program can be stored on a memory of the electronic device. When the computer program is executed by the processor, the operation of the process processing method described in the embodiment of the present application is implemented.

In one embodiment, an electronic device is provided, including a memory, a processor, and a computer program stored on the memory and operable on the processor, the processor performing the process processing provided by the foregoing embodiments when executing the computer program The operation of the method.

In one embodiment, there is also provided a computer readable storage medium having stored thereon a computer program for performing process processing as described in various embodiments of the present application when executed by a processor The operation of the method.

In one embodiment, a computer program product comprising instructions, when executed on a computer, causes the computer to perform the process processing methods described in the various embodiments of the present application.

The embodiment of the present application also provides a computer device. As shown in FIG. 7 , for the convenience of description, only the parts related to the embodiments of the present application are shown. If the specific technical details are not disclosed, please refer to the method part of the embodiment of the present application. The computer device may be any terminal device including a mobile phone, a tablet computer, a PDA (Personal Digital Assistant), a POS (Point of Sales), a vehicle-mounted computer, a wearable device, and the like, taking a computer device as a mobile phone as an example. :

FIG. 7 is a block diagram showing a part of a structure of a mobile phone related to a computer device according to an embodiment of the present application. Referring to FIG. 7, the mobile phone includes: a radio frequency (RF) circuit 710, a memory 720, an input unit 730, a display unit 740, a sensor 750, an audio circuit 760, a wireless fidelity (WiFi) module 770, and a processor 780. And power supply 790 and other components. It will be understood by those skilled in the art that the structure of the mobile phone shown in FIG. 7 does not constitute a limitation to the mobile phone, and may include more or less components than those illustrated, or a combination of certain components, or different component arrangements.

The RF circuit 710 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 780. 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 circuitry 710 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 Global System of Mobile communication (GSM), General Packet Radio Service (GPRS), Code Division Multiple Access (Code Division). Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), Long Term Evolution (LTE), e-mail, Short Messaging Service (SMS), and the like.

The memory 720 can be used to store software programs and modules, and the processor 780 executes various functional applications and data processing of the mobile phone by running software programs and modules stored in the memory 720. The memory 720 can mainly include a program storage area and a data storage area, wherein the program storage area can 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 720 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 730 can be configured to receive input numeric or character information and to generate key signal inputs related to user settings and function controls of the handset 700. Specifically, the input unit 730 may include a touch panel 731 and other input devices 732. The touch panel 731, also referred to as a touch screen, can collect touch operations on or near the user (such as the user using a finger, a stylus, or the like on the touch panel 731 or near the touch panel 731. Operation) and drive the corresponding connection device according to a preset program. In one embodiment, the touch panel 731 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 780 is provided and can receive commands from the processor 780 and execute them. In addition, the touch panel 731 can be implemented in various types such as resistive, capacitive, infrared, and surface acoustic waves. In addition to the touch panel 731, the input unit 730 may also include other input devices 732. In particular, other input devices 732 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 740 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 740 can include a display panel 741. In one embodiment, the display panel 741 can 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 731 can cover the display panel 741. When the touch panel 731 detects a touch operation on or near it, the touch panel 731 transmits to the processor 780 to determine the type of the touch event, and then the processor 780 is The type of touch event provides a corresponding visual output on display panel 741. Although the touch panel 731 and the display panel 741 are used as two independent components to implement the input and input functions of the mobile phone in FIG. 7, in some embodiments, the touch panel 731 can be integrated with the display panel 741. Realize the input and output functions of the phone.

The handset 700 can also include at least one type of sensor 750, 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 741 according to the brightness of the ambient light, and the proximity sensor may close the display panel 741 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 760, speaker 761, and microphone 762 can provide an audio interface between the user and the handset. The audio circuit 760 can transmit the converted electrical data of the received audio data to the speaker 761 for conversion to the sound signal output by the speaker 761; on the other hand, the microphone 762 converts the collected sound signal into an electrical signal by the audio circuit 760. After receiving, it is converted into audio data, and then processed by the audio data output processor 780, transmitted to another mobile phone via the RF circuit 710, or outputted to the memory 720 for subsequent processing.

WiFi is a short-range wireless transmission technology, and the mobile phone can help users to send and receive emails, browse web pages, and access streaming media through the WiFi module 770, which provides users with wireless broadband Internet access. Although FIG. 7 shows the WiFi module 770, it can be understood that it does not belong to the essential configuration of the mobile phone 700 and can be omitted as needed.

The processor 780 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 720, and invoking data stored in the memory 720, The phone's various functions and processing data, so that the overall monitoring of the phone. In one embodiment, processor 780 can include one or more processing units. In one embodiment, the processor 780 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 780. For example, the processor 780 can integrate an application processor and a baseband processor, and the baseband processor and other peripheral chips can form a modem. The handset 700 also includes a power source 790 (such as a battery) that supplies power to the various components. Preferably, the power source can be logically coupled to the processor 780 via a power management system to manage functions such as charging, discharging, and power management through the power management system.

In one embodiment, the handset 700 can also include a camera, a Bluetooth module, and the like.

In the embodiment of the present application, the processor included in the mobile phone implements the process processing method described above when executing a computer program stored in the memory.

Any reference to a memory, storage, database or other medium 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 above 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 claims. 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

A process processing method, the method comprising:

Get the process information of the daemon running in the background;

Detecting whether the process information includes a preset keyword; and

When the keyword is included, resource restrictions are imposed on the daemon.
The method of claim 1, wherein the keyword comprises a first keyword and a second keyword;

The detecting whether the process information includes a preset keyword includes:

Detecting whether the process name in the process information includes a first keyword;

Detecting whether the user identity UID in the process information includes a second keyword; and

When the keyword is included, the resource limitation of the daemon process includes:

When the first keyword and the second keyword are included, resource limitation is performed on the daemon process.
The method according to claim 1, wherein before the resource limiting the daemon process, the method further comprises:

Obtaining an application category of the foreground application, and when the application category is a game application, performing resource limitation on the daemon.
The method according to claim 1, wherein the resource limiting the daemon process comprises:

Lowering the priority of the daemon; and

The daemon is resource limited according to the lowered priority.
The method according to claim 1, wherein the daemon process performs resource limitation, including:

Calculating the degree of restriction on the daemon process based on local resource utilization; and

Restricting resources of the daemon process according to the degree of limitation.
The method according to claim 1, wherein the resource limiting the daemon process comprises:

Limit the CPU resources and I/O resources occupied by the daemon process.
The method according to any one of claims 1 to 6, further comprising: before the resource limiting the daemon process, further comprising:

Detecting whether the daemon process is dependent on the foreground process;

When the daemon process is dependent on the foreground process, the priority of the daemon is adjusted to match the foreground process; and

The resource restriction on the daemon process is performed when the daemon process is not dependent on the foreground process.
The method according to claim 7, wherein the detecting whether the application to be processed is dependent on the foreground application comprises:

Detecting whether at least one of a communication mechanism and a synchronization mechanism exists between the to-be-processed application and the foreground application; and

The to-be-processed application is dependent on the foreground application when there is at least one of a communication mechanism and a synchronization mechanism between the to-be-processed application and the foreground application.
The method according to claim 8, wherein when the socket application, the binder communication, the memory sharing or the lock wait exists between the to-be-processed application and the foreground application, the to-be-processed application and the foreground application There is a communication mechanism between them.
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:

Get the process information of the daemon running in the background;

Detecting whether the process information includes a preset keyword; and

When the keyword is included, resource restrictions are imposed on the daemon.
A computer readable storage medium according to claim 10, wherein said keyword comprises a first keyword and a second keyword; said computer program being executed by said processor such that said processor is When performing the detecting whether the process information includes a preset keyword, the following operations are also performed:

Detecting whether the process name in the process information includes a first keyword;

Detecting whether the user identity UID in the process information includes a second keyword; and

When the keyword is included, the resource limitation of the daemon process includes:

When the first keyword and the second keyword are included, resource limitation is performed on the daemon process.
The computer readable storage medium of claim 10, wherein the computer program is executed by the processor such that the processor further performs before performing the resource restriction on the daemon process The following operations:

Obtaining an application category of the foreground application, and when the application category is a game application, performing resource limitation on the daemon.
A computer readable storage medium according to claim 10, wherein said computer program is executed by said processor such that said processor further executes when said performing resource restriction on said daemon process The following operations:

Lowering the priority of the daemon; and

The daemon is resource limited according to the lowered priority.
The computer readable storage medium of claim 10, wherein when the computer program is executed by the processor, causing the processor to perform the following operations when performing the resource limitation by the daemon:

Calculating the degree of restriction on the daemon process based on local resource utilization; and

Restricting resources of the daemon process according to the degree of limitation.
A computer readable storage medium according to claim 10, wherein said computer program is executed by said processor such that said processor further executes when said performing resource restriction on said daemon process The following operations:

Limit the CPU resources and I/O resources occupied by the daemon process.
The computer readable storage medium according to any one of claims 10 to 15, wherein the computer program is executed by the processor, causing the processor to perform the pairing of the daemon Before the resource is restricted, the following actions are also performed:

Detecting whether the daemon process is dependent on the foreground process;

When the daemon process is dependent on the foreground process, the priority of the daemon is adjusted to match the foreground process; and

The resource restriction on the daemon process is performed when the daemon process is not dependent on the foreground process.
The computer readable storage medium of claim 16, wherein when the computer program is executed by the processor, causing the processor to perform a process of detecting whether an application to be processed is dependent on a foreground application, Do the following:

Detecting whether at least one of a communication mechanism and a synchronization mechanism exists between the to-be-processed application and the foreground application; and

The to-be-processed application is dependent on the foreground application when there is at least one of a communication mechanism and a synchronization mechanism between the to-be-processed application and the foreground application.
The computer readable storage medium according to claim 17, wherein when there is socket communication, binder communication, memory sharing or lock waiting between the to-be-processed application and the foreground application, the to-be-processed application and There is a communication mechanism between the foreground applications.
An electronic device comprising a memory, a processor, and a computer program stored on the memory and operable on the processor, wherein when the processor executes the computer program, the processor causes the processor to:

Get the process information of the daemon running in the background;

Detecting whether the process information includes a preset keyword; and

When the keyword is included, resource restrictions are imposed on the daemon.
The electronic device of claim 19, wherein the keyword comprises a first keyword and a second keyword; when the computer program is executed by the processor, causing the processor to perform the When detecting whether the process information includes a preset keyword, the following operations are also performed:

Detecting whether the process name in the process information includes a first keyword;

Detecting whether the user identity UID in the process information includes a second keyword; and

When the keyword is included, the resource limitation of the daemon process includes:

When the first keyword and the second keyword are included, resource limitation is performed on the daemon process.
The electronic device according to claim 19, wherein when said computer program is executed by said processor, said processor further performs the following operations before performing said resource limitation on said daemon:

Obtaining an application category of the foreground application, and when the application category is a game application, performing resource limitation on the daemon.
The electronic device according to claim 19, wherein when the computer program is executed by the processor, the processor further performs the following operations when performing the resource limitation on the daemon process:

Lowering the priority of the daemon; and

The daemon is resource limited according to the lowered priority.
The electronic device according to claim 19, wherein when said computer program is executed by said processor, said processor further performs the following operations when said processor performs resource limitation by said daemon:

Calculating the degree of restriction on the daemon process based on local resource utilization; and

Restricting resources of the daemon process according to the degree of limitation.
The electronic device according to claim 19, wherein when the computer program is executed by the processor, the processor further performs the following operations when performing the resource limitation on the daemon process:

Limit the CPU resources and I/O resources occupied by the daemon process.
An electronic device according to any one of claims 19 to 24, wherein said computer program is executed by said processor such that said processor performs resource limiting of said daemon process prior to said , also do the following:

Detecting whether the daemon process is dependent on the foreground process;

When the daemon process is dependent on the foreground process, the priority of the daemon is adjusted to match the foreground process; and

The resource restriction on the daemon process is performed when the daemon process is not dependent on the foreground process.
The electronic device according to claim 25, wherein when said computer program is executed by said processor, said processor further performs the following operations when said detecting whether said application to be processed is dependent by a foreground application :

Detecting whether at least one of a communication mechanism and a synchronization mechanism exists between the to-be-processed application and the foreground application; and

The to-be-processed application is dependent on the foreground application when there is at least one of a communication mechanism and a synchronization mechanism between the to-be-processed application and the foreground application.
The electronic device according to claim 26, wherein when there is socket communication, binder communication, memory sharing or lock waiting between the to-be-processed application and the foreground application, the to-be-processed application and the foreground There is a communication mechanism between applications.