CN109992399B - Resource management method, resource management device, mobile terminal and computer-readable storage medium - Google Patents
Resource management method, resource management device, mobile terminal and computer-readable storage medium Download PDFInfo
- Publication number
- CN109992399B CN109992399B CN201711488953.7A CN201711488953A CN109992399B CN 109992399 B CN109992399 B CN 109992399B CN 201711488953 A CN201711488953 A CN 201711488953A CN 109992399 B CN109992399 B CN 109992399B
- Authority
- CN
- China
- Prior art keywords
- application
- resource
- background
- running
- foreground
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
- G06F9/5005—Allocation of resources, e.g. of the central processing unit [CPU] to service a request
- G06F9/5011—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resources being hardware resources other than CPUs, Servers and Terminals
- G06F9/5016—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resources being hardware resources other than CPUs, Servers and Terminals the resource being the memory
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
- G06F9/5005—Allocation of resources, e.g. of the central processing unit [CPU] to service a request
- G06F9/5027—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals
- G06F9/5038—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals considering the execution order of a plurality of tasks, e.g. taking priority or time dependency constraints into consideration
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2209/00—Indexing scheme relating to G06F9/00
- G06F2209/50—Indexing scheme relating to G06F9/50
- G06F2209/504—Resource capping
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Telephone Function (AREA)
- Stored Programmes (AREA)
Abstract
The embodiment of the application relates to a resource management method, a resource management device, a mobile terminal and a computer readable storage medium. The method comprises the following steps: acquiring running characteristics of background application, and determining an application scene type of the background application according to the running characteristics, wherein the application scene type comprises a sensible application and an imperceptible application; determining the resource limitation level of the background application according to the application scene type; and performing resource management on the background application according to the resource limit level. The resource management method, the resource management device, the mobile terminal and the computer readable storage medium can dynamically realize resource limitation of different levels for background application, optimize system performance and save power consumption.
Description
Technical Field
The present application relates to the field of computer technologies, and in particular, to a resource management method and apparatus, a mobile terminal, and a computer-readable storage medium.
Background
With the rapid development of the internet, the smart mobile terminal has become the most common electronic device for many users, such as a smart phone, a tablet phone, and the like. A user can install various applications on the intelligent mobile terminal for use, and when the applications run in the background, the applications and the applications running in the foreground can preempt system resources such as a Central Processing Unit (CPU), a memory, a bandwidth and the like, so that problems of unsmooth application running in the foreground, slow system running, heat generation of the mobile terminal and the like occur.
Disclosure of Invention
The embodiment of the application provides a resource management method, a resource management device, a mobile terminal and a computer readable storage medium, which can dynamically realize resource restriction of different levels for background application, optimize system performance and save power consumption.
A method of resource management, comprising:
acquiring running characteristics of background application, and determining an application scene type of the background application according to the running characteristics, wherein the application scene type comprises a sensible application and an imperceptible application;
determining the resource limitation level of the background application according to the application scene type;
and performing resource management on the background application according to the resource limit level.
A resource management apparatus, comprising:
the scene determining module is used for acquiring the running characteristics of the background application and determining the application scene type of the background application according to the running characteristics, wherein the application scene type comprises a perceptible application and an imperceptible application;
the level determining module is used for determining the resource limitation level of the background application according to the application scene type;
and the management module is used for carrying out resource management on the background application according to the resource limit level.
A mobile terminal comprising a memory and a processor, the memory having stored therein a computer program which, when executed by the processor, causes the processor to carry out the method as described above.
A computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out the method as set forth above.
According to the resource management method, the resource management device, the mobile terminal and the computer-readable storage medium, the running characteristics of the background application are obtained, the application scene type of the background application is determined according to the running characteristics, the resource limit level of the background application is determined according to the application scene type, the resource management is performed on the background application according to the resource limit level, the resource limit of different levels can be dynamically realized on the background application according to the application scene type of the background application, the system performance is optimized, and the power consumption is saved.
Drawings
FIG. 1 is a block diagram of a mobile terminal in one embodiment;
FIG. 2 is a system architecture diagram of a resource management method in one embodiment;
FIG. 3 is a flow diagram illustrating a method for resource management in one embodiment;
FIG. 4 is a diagram illustrating different resource restriction levels in one embodiment;
FIG. 5 is a flowchart illustrating a unified resource management process for processes running in a background application according to an embodiment;
FIG. 6 is a flow diagram that illustrates reducing a resource restriction level of a background process that has a dependency relationship with a foreground process, according to an embodiment;
FIG. 7 is a block diagram of a resource management device in one embodiment;
FIG. 8 is a block diagram of a management module in one embodiment;
FIG. 9 is a block diagram of a resource management apparatus in another embodiment;
fig. 10 is a block diagram of a mobile terminal in another embodiment.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the present application is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application.
It will be understood that, as used herein, the terms "first," "second," and the like may be used herein 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.
Fig. 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, among other things, 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, and the computer program is executed by a 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 execution of the computer program in the non-volatile storage medium. The display screen of the mobile terminal can be a liquid crystal display screen or an electronic ink display screen, and the input device can be a touch layer covered on the display screen, a key, a track ball or a touch pad arranged on a shell of the mobile terminal, or an external keyboard, a touch pad or a mouse. The mobile terminal can be a mobile phone, a tablet computer, a personal digital assistant or a wearable device. Those skilled in the art will appreciate that the architecture shown in fig. 1 is only a block diagram of a portion of the architecture associated with the subject application and does not constitute a limitation on the mobile terminal to which the subject application applies, and that a particular mobile terminal may include more or less components than those shown, or may combine certain components, or have a different arrangement of components.
FIG. 2 is a system architecture diagram of a resource management method in one embodiment. As shown in fig. 2, the system architecture includes a JAVA space layer 210, a local framework layer 220, and a Kernel space layer 230. The JAVA space layer 210 may include a freezing management module 212, and the mobile terminal may implement a freezing policy for each running application through the freezing management module 212, and perform a freezing operation on a related application that consumes more power in the background or occupies a large amount of system resources. A resource priority and restriction management module 222 and a platform freeze management module 224 are contained in the local framework layer 220. The mobile terminal can maintain different applications in different resource use priorities and different resource groups in real time through the resource priority and restriction management module 222, and adjust the resource groups of the application program according to the requirements of the upper layer, thereby achieving the effects of optimizing performance and saving power consumption. The mobile terminal can allocate the applications that can be frozen in the background to the freezing layers of different preset layers according to the length of the freezing time through the platform freezing management module 224. Alternatively, the frozen layer may comprise three, respectively: CPU limited sleep mode, CPU frozen sleep mode, process deep frozen mode. The CPU sleep-restricted mode is to restrict CPU resources occupied by related processes, so that the related processes occupy less CPU resources, and the vacant CPU resources are inclined to other processes which are not frozen, so that the occupation of the CPU resources is restricted, and the occupation of network resources and I/O interface resources by the processes is correspondingly restricted; the CPU freezing sleep mode means that related processes are forbidden to use the CPU, the occupation of a memory is reserved, and when CPU resources are forbidden to use, corresponding network resources and I/O interface resources are also forbidden to use; the process deep freezing mode is to further recycle the memory resources occupied by the relevant processes except for forbidding the use of CPU resources, and the recycled memory can be used by other processes. Optionally, the local framework layer 220 may further include an interface module that includes a binder interface that is opened to an upper layer, and a framework or application of the upper layer sends an instruction for resource restriction or freezing to the resource priority and restriction management module 222 and the platform freezing management module 224 through the provided binder interface.
The kernel space layer 230 may include a UID management module 231, a Cgroup module 233, a Binder management module 235, a process memory recycling module 237, and a freeze timeout exit module 239. The UID management module 231 is configured to manage or freeze resources of the third-party application based on a User Identifier (UID) of the application. Compared with the Process control based on the Process Identifier (PID), the unified management of the resources of the application of one user is facilitated through the 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 and control module 235 is used for controlling the priority of background Binder communication. The process memory recycling module 237 is used to implement a deep process freezing mode, so that when a third-party application is in a frozen state for a long time, a file area of a process is mainly released, thereby achieving a memory-saving module and increasing the speed of the application when the application is started next time. The freeze timeout exit module 239 may be used to resolve exceptions resulting from the occurrence of the freeze timeout scenario. Through the system architecture, the resource management method in each embodiment of the application can be realized.
As shown in fig. 3, in one embodiment, there is provided a resource management method, comprising the steps of:
and 310, acquiring the running characteristics of the background application, and determining the application scene type of the background application according to the running characteristics.
One or more application programs can be simultaneously run on the mobile terminal, and the application programs can comprise foreground application running in the foreground and background application running in the background. The mobile terminal can obtain the running characteristics of the background applications and determine the application scene types of the background applications according to the running characteristics. Alternatively, the application scene type may include a perceivable application and an imperceptible application, etc. The perceivable application refers to an application that can be heard, seen, etc. by the user and can be perceived by the user to be running, such as a music application playing music, an application downloading a file, etc., but is not limited thereto, and the application can still be perceived by the user to be running although the application has entered a background running. An imperceptible application refers to an application that is not perceptible to a user as running, such as, but not limited to, entering a social application running in the background, a payment application, and the like. In one embodiment, the imperceptible application may include an imperceptible application that receives process communication and an imperceptible application that receives process communication, where the imperceptible application that receives process communication refers to an imperceptible application in which a process running under the application has communication and the like with other processes, and the imperceptible application that does not have communication with other processes.
The mobile terminal may obtain the running characteristics of each background application currently running in the background, where the running characteristics may include, but are not limited to, a task currently executed by the application, a communication event of each process under the application, a type and a proportion of resources currently occupied by the application, and the like. The mobile terminal can judge the application scene type of the background application according to the running characteristics of the background application, corresponding scene conditions can be preset according to actual requirements for different application scene types, and the application scene type can be determined according to the scene conditions met by the running characteristics. For example, the scene condition corresponding to the application scene type being the perceivable application may include that the task currently executed by the application is a play task or a download task, and the imperceptible application having the application scene type being the receiving process communication may include that the application has a process communication event within a preset time period, and the like, but is not limited thereto.
Optionally, the application scene type of the background application may change with the change of the running feature, for example, when the music application plays music in the background, the application scene type of the music application may be a perceptible application, and when the music application stops playing music, the application scene type of the music application may become an imperceptible application. In one embodiment, the mobile terminal may obtain the running characteristics of each background application at intervals, and determine the application scene type of each background application according to the running characteristics. The mobile terminal can also monitor the tasks executed by each background application, when detecting that the background application starts to execute the tasks or the tasks are completed, the mobile terminal obtains the running characteristics of the background application, and then determines the application scene type and the like of the background application according to the running characteristics.
And 320, determining the resource limitation level of the background application according to the application scene type.
The mobile terminal can set different resource limit levels according to actual requirements, the resource limit levels can be used for representing the limited degree of the application resource, and the higher the resource limit level is, the larger the limited degree can be. The restricted resources may include, but are not limited to, CPU resources, memory resources, I/O resources, network resources, and the like. The background applications have different application scene types and may respectively correspond to different resource restriction levels, optionally, the background application having the application scene type of the perceivable application may have a resource restriction level lower than that of the imperceptible application, and the background application having the application scene type of the imperceptible application receiving the process communication may have a resource restriction level lower than that of the imperceptible application receiving the process communication.
In one embodiment, the resource restriction level set by the mobile terminal may include an unlimited level, a general restricted level, a deep restricted level, and a frozen level. The unlimited level may refer to that resources used by the application are not limited, and the application running in the foreground may correspond to the unlimited level, thereby ensuring normal running of the foreground application. A common level of restriction may refer to, but is not limited to, an application that may use less resources, such as an application that may use only 50% of the resources at the most, etc. The background application with the application scene type of the perceptible application can correspond to the common limiting level, and the resource preemption of the background application is reduced under the condition that the perceptible task of the background application can be normally executed. The depth limit level may refer to, but is not limited to, that the application may use very few resources, such as the application may only use up to 20% of the resources. Background applications of the imperceptible applications of which the application scene types are received process communication can correspond to the depth limit level, and used resources can meet the processing requirements of inter-process communication tasks. The freeze level refers to the inability of the application to use any resources, stopping all behavior of the application. Background application with the application scene type of the non-perceptible application of the process-free communication application can correspond to the freezing level, and power consumption is saved. It will be appreciated that the resource restriction level may be divided in other ways, and is not limited to the above-mentioned ways.
And 330, performing resource management on the background application according to the resource limit level.
Different resource restriction levels can respectively correspond to different resource use priorities, the higher the resource restriction level is, the lower the corresponding resource use priority can be, the fewer resources can be used by the application, the lower the resource restriction level is, the higher the corresponding resource use priority can be, and the more resources can be used by the application. Optionally, after determining the resource restriction level according to the application scene type of the background application, the mobile terminal may configure a resource usage priority corresponding to the resource restriction level for the background application. The resource usage priority configured by the background application with the application scene type for the perceivable application may be higher than the non-perceivable application, and the resource usage priority configured by the non-perceivable application with the application scene type for receiving the process communication may be higher than the non-perceivable application without the process communication.
After the mobile terminal configures the resource use priority according to the resource restriction level of the background application, the resources used by the background application can be managed according to the configured resource use priority. When the application scene type of the background application is changed, the mobile terminal can determine the resource use level again according to the changed application scene type.
FIG. 4 is a diagram illustrating different resource restriction levels, in one embodiment. As shown in fig. 4, four different resource restriction levels can be set in the mobile terminal, which respectively include an unrestricted level, a normal restriction level, a deep restriction level, and a freeze level. The unlimited level does not limit the resources such as CPU, memory, I/O, and network used by the application. Common restriction level restriction applications may use fewer resources such as CPU, memory, I/O, and network. The deep level of restriction limits the applications to use very few resources such as CPU, memory, I/O, and network. The freeze level limits the application from using resources such as CPU, memory, I/O, and network. The mobile terminal can determine the resource restriction level according to the application scene type of the background application, and realize resource restriction of different levels for background applications with different application scene types.
In this embodiment, the running characteristics of the background application are acquired, the application scene type of the background application is determined according to the running characteristics, the resource limitation level of the background application is determined according to the application scene type, the resource management is performed on the background application according to the resource limitation level, the resource limitation of different levels can be dynamically realized on the background application according to the application scene type of the background application, the system performance is optimized, and the power consumption is saved.
As shown in FIG. 5, in one embodiment, step 330 performs resource management on the background application according to the resource restriction level, and includes the following steps:
A process is a running activity of a program in a computer on a data set, is a basic unit for resource allocation and scheduling of a system, and is the basis of an operating system structure. A mobile terminal may typically have multiple processes running thereon, with different processes being available to perform different tasks, respectively. One or more processes can run under one application program, and after the mobile terminal determines the resource restriction level according to the application scene type of the background application, the mobile terminal can perform uniform resource management on each process running under the background application according to the resource restriction level. Optionally, when the application program runs, the mobile terminal may allocate different user groups to the running application program, and may manage the authority of the application program through the user groups. The mobile terminal can acquire user group information of the background application and acquire each process running under the background application according to the user group information, wherein the user group information can comprise user group identification and the like, and the user group identification can be formed by one or more of numbers, letters, symbols and the like.
The mobile terminal can inquire the process identification which has a mapping relation with the user group information according to the user group information of the background application, so that each process running under the background application is obtained. 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 distribute and release the user group information to which the process belongs, and the user group information can be changed in the process of running the process. The kernel space layer collects user group information to which each process belongs in real time, and can establish a mapping relation between process information such as process identification, process names and the like and the user group information. When the mobile terminal needs to adjust the resource restriction level of the background application, the process identification with the mapping relation can be directly inquired according to the user group information of the background application, and compared with the method of traversing all running processes to find the process running under the background application, the method is more convenient and faster to directly search the process identification with the mapping relation with the user group information.
The mobile terminal can divide different resource groups, each resource group can respectively correspond to different resource restriction levels, and is configured with corresponding resource use priority. After the mobile terminal queries the process identification having the mapping relation with the user group information, the background process matched with the process identification can be added into the resource group corresponding to the determined resource restriction level, so that all processes running under the background application are subjected to unified resource management according to the resource restriction level. Optionally, the mobile terminal may divide different resource groups based on a kernel Cgroup (control group) mechanism, and may set a resource usage priority of each resource group in a file node write configuration manner, and manage time or proportion of resource usage by processes in each resource group, where Cgroup is a mechanism provided in the kernel and capable of limiting, recording, and isolating physical resources (e.g., resources such as CPU, memory, I/O, etc.) used by the process groups (processes groups). The mobile terminal can load a Cgroup configuration file, and the configuration file can record the divided resource groups, the resource use priority of each resource group and the resource scheduling strategy corresponding to the resource use priority. The resource scheduling policy may include, but is not limited to, a time for the process to use the resource, a proportion of occupied resource, a resource identifier used, and the like, for example, the process of the resource group corresponding to the configurable general limit level may use 30 seconds of CPU resource within 1 minute, and the process of the resource group corresponding to the general limit level may only use the CPU resource numbered X, and the like. When a new resource group needs to be added or the resource use priority and the resource scheduling policy of the resource group need to be modified, the configuration file of the Cgroup can be modified.
In this embodiment, the process identifier having the mapping relationship may be found according to the user group information of the background application, the background process matched with the process identifier is added to the resource group corresponding to the resource restriction level, uniform resource management may be performed on each process running under the background application according to the resource restriction level, resource restriction at different levels may also be implemented through the setting of the resource group, system performance is optimized, and power consumption is saved.
As shown in fig. 6, in an embodiment, the resource management method further includes the following steps:
The mobile terminal may obtain a foreground process running on the foreground, and optionally, the mobile terminal may obtain all running process lists through a RunningAppProcessInfo class of the activity manager, and obtain a process running in the foreground from the process lists, that is, it may be determined that the process running in the foreground is the foreground process.
And step 604, when a background process with a dependency relationship with a foreground process exists, reducing the resource restriction level of the background process with the dependency relationship.
After acquiring a foreground process running in a foreground, the mobile terminal can detect whether a background process having a dependency relationship with the foreground process exists, wherein the dependency relationship means that one process can be normally executed only by waiting for a message of the other process, and the dependency relationship exists between the two processes. Optionally, the mobile terminal may pre-record a process identifier having a dependency relationship, may obtain a process identifier of a foreground process, and obtain a process identifier having a dependency relationship with the foreground process according to the process identifier of the foreground process. The mobile terminal can detect each process running in the background one by one according to the process identification having the dependency relationship with the foreground process, and determine whether the background process having the dependency relationship with the foreground process exists.
The mobile terminal can reduce the resource restriction level of the background process having the dependency relationship with the foreground process and improve the resource use priority of the background process having the dependency relationship. Optionally, the mobile terminal may adjust the resource restriction level of the background process having the dependency relationship with the foreground process to the same resource restriction as the foreground process, and the like, and may allocate the background process having the dependency relationship to the same resource group as the foreground process, and configure the same resource usage priority as the foreground process. The resource use priority of the background process having the dependency relationship with the process running in the foreground is improved, and the task execution of the background process having the dependency relationship with the process running in the foreground can be accelerated, so that the waiting time of the process running in the foreground is reduced, and the running of the process in the foreground is accelerated.
In one embodiment, the mobile terminal may detect whether a background process in interactive communication with a foreground process exists, and may determine the background process in interactive communication with the foreground process as the background process having a dependency relationship with the foreground process. Optionally, the inter-process interactive communication may include a synchronization mechanism and/or a communication mechanism, and the like, where the synchronization mechanism may refer to two processes coordinating with each other to jointly complete a task, and the communication mechanism refers to propagating or exchanging information between different processes.
In one embodiment, the mobile terminal may detect whether there is a background process having a communication mechanism with the foreground process, and may determine the background process having a communication mechanism with the foreground process as the background process having the dependency relationship. The communication mechanism may include socket, binder, shared memory, etc., wherein, two programs on the network realize the exchange of data through a bidirectional communication connection, one end of this connection is called a socket; the binder is an interprocess communication mechanism and provides a remote procedure call function; shared memory is a very efficient way to allow two unrelated processes to access the same logical memory, and shared memory is a very efficient way to share and transfer data between two running processes, and memory shared between different processes is usually arranged as the same physical memory. Optionally, the mobile terminal may detect whether there is a background process that communicates with the foreground-running process having the socket and/or the binder, and may determine the background process that communicates with the foreground-running process having the socket and/or the binder as the background process having the dependency relationship. The mobile terminal can also detect whether a background process for memory sharing with the process running in the foreground exists or not, and can determine the background process for memory sharing with the process running in the foreground as the background process with the dependency relationship. In one embodiment, the mobile terminal may add a detection mechanism in the binder driver, and detect whether there is a background process having a communication mechanism with the foreground process according to the detection mechanism added in the binder driver.
In one embodiment, the mobile terminal may detect whether there is a background process having a synchronization mechanism with a foreground process, and may determine the background process having the synchronization mechanism with the foreground process as the background process having the dependency relationship. The synchronization mechanism may include a semaphore (semaphore) having a data structure of a value and a pointer to the next process waiting for the semaphore, a mutex lock that may be used to ensure the integrity of shared data, and only one process may access an object having the mutex lock on it at any time. Optionally, the mobile terminal may detect whether a background process having a synchronization mechanism with a foreground process exists through a call of a futex (fast user space mutex) system. The calling of the futex system can be used for realizing a synchronization mechanism among processes, operates in a user space, and is a mixed mechanism of a user mode and a kernel mode, wherein the user mode refers to a non-privileged state.
In one embodiment, when the mobile terminal detects that the lock waiting action occurs in the foreground process, the lock resource waiting by the foreground process can be determined. Lock resources may include thread locks, file handles, signals, etc., where a file handle refers to a sequence number retrieved by an operating system function when reading data from a file, thereby enabling the file to be opened, and the file handle is a unique identification for the opened file. The mobile terminal can traverse all processes running in the background, detect whether a background process waiting for the same resource lock with the foreground process exists, and determine the background process waiting for the same resource lock with the foreground process as the background process with the dependency relationship.
In one embodiment, the mobile terminal may detect whether a background process having a dependency relationship with a foreground process ends the dependency relationship. For example, the mobile terminal may detect whether the background process ends communication with the socket and/or binder of the process running in the foreground, and may determine to end the dependency relationship if the communication ends. The mobile terminal may also detect whether a background process waiting for the same resource as the foreground process completes a task, and if the task is completed, may determine to end the dependency relationship, but is not limited thereto. The mobile terminal can restore the background process which finishes the dependency relationship to the resource limit level before the reduction, and limit the resource use of the background process again.
In this embodiment, the resource restriction level of the background process having a dependency relationship with the foreground process can be reduced, the foreground process can be ensured to be responded in time, the foreground process is prevented from entering a wait state due to the restriction of the resource use of the background process, and the running speed of the foreground is increased while the power consumption is reduced.
In one embodiment, a resource management method is provided, comprising the steps of:
the method comprises the steps of (1) acquiring running characteristics of background application, and determining application scene types of the background application according to the running characteristics, wherein the application scene types comprise a sensible application and an imperceptible application.
And (2) determining the resource limitation level of the background application according to the application scene type.
Optionally, the imperceptible application includes an imperceptible application that receives process communication and an imperceptible application that receives process-free communication; after the step (2), further comprising: and configuring resource use priority corresponding to the resource limit level for the background application, wherein the resource use priority of the application scene type is that the resource use priority of the perceptible application is higher than that of the imperceptible application, and the resource use priority of the application scene type is that the resource use priority of the imperceptible application receiving process communication is higher than that of the imperceptible application receiving no process communication.
And (3) performing resource management on the background application according to the resource limit level.
Optionally, step (3), comprising: acquiring user group information of background application; inquiring process identification having a mapping relation with user group information; and adding the background process matched with the process identification into the resource group corresponding to the resource restriction level.
Optionally, after the step (3), further comprising: acquiring a foreground process running on a foreground; and when a background process with a dependency relationship with a foreground process exists, reducing the resource restriction level of the background process with the dependency relationship.
Optionally, after acquiring a foreground process running in a foreground, the method further includes: when the background process and the foreground process have a synchronization mechanism and/or a communication mechanism, the background process with the synchronization mechanism and/or the communication mechanism is determined as the background process with the dependency relationship.
Optionally, after acquiring a foreground process running in a foreground, the method further includes: when detecting that the foreground process has a lock waiting behavior, determining a waiting lock resource; and if the background process waiting for the resource is available, determining the background process waiting for the resource as the background process with the dependency relationship.
Optionally, after reducing the resource restriction level of the background process with dependency relationship, the method further includes: and when the foreground process finishes the dependency relationship with the background process, restoring the resource limit level of the background process which finishes the dependency relationship before reducing.
In this embodiment, the running characteristics of the background application are acquired, the application scene type of the background application is determined according to the running characteristics, the resource limitation level of the background application is determined according to the application scene type, the resource management is performed on the background application according to the resource limitation level, the resource limitation of different levels can be dynamically realized on the background application according to the application scene type of the background application, the system performance is optimized, and the power consumption is saved.
It should be understood that the steps in the above-described flowchart illustrations are shown in order as indicated by the arrows, but the steps are not necessarily performed in order as indicated by the arrows. The steps are not performed in the exact order shown and described, and may be performed in other orders, unless explicitly stated otherwise. Moreover, at least a portion of the steps in the flow diagrams described above may include multiple sub-steps or multiple stages that are not necessarily performed at the same time, but may be performed at different times, and the order of performing the sub-steps or stages is not necessarily sequential, but may be performed in turn or alternately with other steps or at least a portion of the sub-steps or stages of other steps.
As shown in fig. 7, in one embodiment, a resource management apparatus 700 is provided and includes a scenario determination module 710, a level determination module 720, and a management module 730.
The scene determining module 710 is configured to obtain an operation characteristic of the background application, and determine an application scene type of the background application according to the operation characteristic, where the application scene type includes a perceivable application and an imperceptible application.
And a level determining module 720, configured to determine a resource restriction level of the background application according to the application scene type.
Optionally, the imperceptible application includes an imperceptible application that receives process communications and an imperceptible application that receives process-free communications. The level determining module 720 is further configured to configure a resource usage priority corresponding to the resource restriction level for the background application, where the application scenario type is that the resource usage priority of the perceivable application is higher than that of the imperceptible application, and the application scenario type is that the resource usage priority of the imperceptible application receiving the process communication is higher than that of the imperceptible application without the process communication.
And the management module 730 is configured to perform resource management on the background application according to the resource restriction level.
In this embodiment, the running characteristics of the background application are acquired, the application scene type of the background application is determined according to the running characteristics, the resource limitation level of the background application is determined according to the application scene type, the resource management is performed on the background application according to the resource limitation level, the resource limitation of different levels can be dynamically realized on the background application according to the application scene type of the background application, the system performance is optimized, and the power consumption is saved.
As shown in fig. 8, in one embodiment, the management module 730 includes an obtaining unit 732, a querying unit 734, and an adding unit 736.
The obtaining unit 732 is configured to obtain user group information of the background application.
The query unit 734 is configured to query the process identifier having a mapping relationship with the user group information.
An adding unit 736 configured to add the background process matching the process identifier to the resource group corresponding to the resource restriction level.
In this embodiment, the process identifier having the mapping relationship may be found according to the user group information of the background application, the background process matched with the process identifier is added to the resource group corresponding to the resource restriction level, uniform resource management may be performed on each process running under the background application according to the resource restriction level, resource restriction at different levels may also be implemented through the setting of the resource group, system performance is optimized, and power consumption is saved.
As shown in fig. 9, in an embodiment, the resource management apparatus 700 includes a process obtaining module 740 and a reducing module 750 in addition to the scene determining module 710, the level determining module 720 and the management module 730.
A process obtaining module 740, configured to obtain a foreground process running on a foreground.
The reducing module 750 is configured to reduce, when there is a background process having a dependency relationship with a foreground process, a resource restriction level of the background process having the dependency relationship.
In an embodiment, the resource management apparatus 700 further includes a dependency relationship determination module.
And the dependency relationship determining module is used for determining the background process with the synchronization mechanism and/or the communication mechanism as the background process with the dependency relationship when the background process and the foreground process have the synchronization mechanism and/or the communication mechanism.
In one embodiment, the dependency relationship determining module is further configured to determine a waiting lock resource when detecting that a lock waiting behavior occurs in the foreground process; and if the background process waiting for the resource is available, determining the background process waiting for the resource as the background process with the dependency relationship.
In one embodiment, the reducing module 750 is further configured to restore the resource restriction level of the background process that ended the dependency relationship before the reduction when the foreground process ended the dependency relationship with the background process.
In this embodiment, the resource restriction level of the background process having a dependency relationship with the foreground process can be reduced, the foreground process can be ensured to be responded in time, the foreground process is prevented from entering a wait state due to the restriction of the resource use of the background process, and the running speed of the foreground is increased while the power consumption is reduced.
The embodiment of the application also provides the mobile terminal. As shown in fig. 10, for convenience of explanation, only the parts related to the embodiments of the present application are shown, and details of the technology are not disclosed, please refer to the method part of the embodiments of the present application. The mobile terminal may be any terminal device including a mobile phone, a tablet computer, a Personal Digital Assistant (PDA), a Point of Sales (POS), a vehicle-mounted computer, a wearable device, and the like, taking the mobile terminal as the mobile phone as an example:
fig. 10 is a block diagram of a partial structure of a mobile phone related to a mobile terminal according to an embodiment of the present application. Referring to fig. 10, the cellular phone includes: radio Frequency (RF) circuit 1010, memory 1020, input unit 1030, display unit 1040, sensor 1050, audio circuit 1060, wireless fidelity (WiFi) module 1070, processor 1080, and power source 1090. Those skilled in the art will appreciate that the handset configuration shown in fig. 10 is not intended to be limiting and may include more or fewer components than those shown, or some components may be combined, or a different arrangement of components.
The RF circuit 1010 may be configured to receive and transmit signals during information transmission and reception or during a call, and may receive downlink information of a base station and then process the received downlink information to the processor 1080; the uplink data may also be transmitted to the base station. Typically, the RF circuitry includes, but is 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, the RF circuitry 1010 may also communicate with networks and other devices via wireless communications. The 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 for storing software programs and modules, and the processor 1080 executes various functional applications and data processing of the mobile phone by operating the 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 program required for at least one function (such as an application program for a sound playing function, an application program for an image playing function, and the like), and the like; the data storage area may store data (such as audio data, an address book, etc.) created according to the use of the mobile phone, and the like. Further, the memory 1020 may include high speed random access memory, and may 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 may be used to receive input numeric or character information and generate key signal inputs related to user settings and function control of the cellular phone 1000. Specifically, the input unit 1030 may include a touch panel 1032 and other input devices 1034. Touch panel 1032, which may also be referred to as a touch screen, may collect touch operations by a user (e.g., operations by a user on or near touch panel 1032 using a finger, a stylus, or any other suitable object or accessory) and drive the corresponding connection device according to a predetermined program. In one embodiment, touch panel 1032 can include two portions, a touch detection device and a touch controller. The touch detection device detects the touch direction of a user, detects a signal brought by touch operation and transmits the signal to the touch controller; the touch controller receives touch information from the touch sensing device, converts the touch information into touch point coordinates, sends the touch point coordinates to the processor 1080, and can receive and execute commands sent by the processor 1080. In addition, the touch panel 1032 may be implemented using various types such as resistive, capacitive, infrared, and surface acoustic wave. The input unit 1030 may include other input devices 1034 in addition to the touch panel 1032. In particular, other input devices 1034 may include, but are not limited to, one or more of a physical keyboard, function keys (such as volume control keys, switch keys, etc.), and the like.
The display unit 1040 may be used to display information input by a user or information provided to the user and various menus of the cellular phone. The display unit 1040 may 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 overlay the display panel 1042, and when the touch panel 1032 detects a touch operation thereon or nearby, the touch operation is transmitted to the processor 1080 to determine the type of the touch event, and then the processor 1080 provides a corresponding visual output on the display panel 1042 according to the type of the touch event. Although in fig. 10, the touch panel 1032 and the display panel 1042 are two separate components to implement the input and output functions of the mobile phone, in some embodiments, the touch panel 1032 and the display panel 1042 may be integrated to implement the input and output functions of the mobile phone.
The cell phone 1000 may also include at least one 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 ambient light, and the proximity sensor may turn off the display panel 1042 and/or the backlight when the mobile phone moves to the ear. The motion sensor can comprise an acceleration sensor, the acceleration sensor can detect the magnitude of acceleration in each direction, the magnitude and the direction of gravity can be detected when the mobile phone is static, and the motion sensor can be used for identifying the application of the gesture of the mobile phone (such as horizontal and vertical screen switching), the vibration identification related functions (such as pedometer and knocking) and the like; the mobile phone may be provided with other sensors such as a gyroscope, a barometer, a hygrometer, a thermometer, and an infrared sensor.
WiFi belongs to short-distance wireless transmission technology, and the mobile phone can help the user to send and receive e-mail, browse web pages, access streaming media, etc. through the WiFi module 1070, which provides wireless broadband internet access for the user. Although fig. 10 shows the WiFi module 1070, it is to be understood that it does not belong to the essential constitution of the handset 1000 and may be omitted as needed.
The processor 1080 is a control center of the mobile phone, connects various parts of the whole mobile phone by using various interfaces and lines, and executes various functions of the mobile phone and processes data by operating or executing software programs and/or modules stored in the memory 1020 and calling data stored in the memory 1020, thereby integrally monitoring the mobile phone. In one embodiment, processor 1080 may include one or more processing units. In one embodiment, processor 1080 may integrate an application processor and a modem, wherein the application processor primarily handles operating systems, user interfaces, application programs, and the like; the modem handles primarily wireless communications. It is to be appreciated that the modem can be non-integrated with the processor 1080. For example, the processor 1080 may integrate an application processor and a baseband processor, which may constitute a modem with other peripheral chips, etc. The handset 1000 also includes a power supply 1090 (e.g., a battery) for powering the various components, which may preferably be logically coupled to the processor 1080 via a power management system that may be configured to manage charging, discharging, and power consumption.
In one embodiment, the cell phone 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 above-described resource management method when executing the computer program stored on the memory.
In one embodiment, the mobile terminal can include a memory 1020 and a processor 1080, wherein the memory 1020 stores a computer program that, when executed by the processor 1080, causes the processor to perform the steps of:
acquiring running characteristics of the background application, and determining an application scene type of the background application according to the running characteristics, wherein the application scene type comprises a sensible application and an imperceptible application;
determining the resource limitation level of the background application according to the application scene type;
and performing resource management on the background application according to the resource limitation level.
In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored, which computer program, when being executed by a processor, carries out the above-mentioned resource management method.
In one embodiment, a computer program product is provided that comprises a computer program, which when run on a computer device causes the computer device to perform the above-described resource management method.
It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by a computer program, which can be stored in a non-volatile computer-readable storage medium, and can include the processes of the embodiments of the methods described above when the program is executed. The storage medium may be a magnetic disk, an optical disk, a Read-Only Memory (ROM), or the like.
Any reference to memory, storage, database, or other medium as used herein may include non-volatile and/or volatile memory. Suitable non-volatile memory 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 external cache memory. 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), double data rate SDRAM (DDR SDRAM), Enhanced SDRAM (ESDRAM), synchronous Link (Synchlink) DRAM (SLDRAM), Rambus Direct RAM (RDRAM), direct bus dynamic RAM (DRDRAM), and bus dynamic RAM (RDRAM).
The technical features of the embodiments described above may be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the embodiments described above are not described, but should be considered as being within the scope of the present specification as long as there is no contradiction between the combinations of the technical features.
The above-mentioned embodiments only express several embodiments of the present application, and the description thereof is more specific and detailed, but not construed as limiting the scope of the invention. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the concept of the present application, which falls within the scope of protection of the present application. Therefore, the protection scope of the present patent shall be subject to the appended claims.
Claims (10)
1. A method for resource management, comprising:
acquiring running characteristics of background application, and determining an application scene type of the background application according to the running characteristics, wherein the application scene type comprises a sensible application and an imperceptible application; the perceivable application refers to an application that can be perceived by a user as running; the imperceptible application refers to an application that is imperceptible to a user to be running; the application scene type of the background application is changed along with the change of the running characteristic;
determining the resource limitation level of the background application according to the application scene type;
and performing resource management on the background application according to the resource limit level.
2. The method of claim 1, wherein the unaware applications comprise an unaware application that receives process communication and an unaware application that does not receive process communication;
after the determining the resource restriction level of the background application according to the application scene type, the method further includes:
and configuring a resource use priority corresponding to the resource limit level for the background application, wherein the resource use priority of the application scene type is that the resource use priority of the perceptible application is higher than that of the imperceptible application, and the resource use priority of the application scene type is that the resource use priority of the imperceptible application receiving process communication is higher than that of the imperceptible application without process communication.
3. The method of claim 1, wherein the resource managing the background application according to the resource restriction level comprises:
acquiring user group information of the background application;
inquiring a process identifier having a mapping relation with the user group information;
and adding the background process matched with the process identification into the resource group corresponding to the resource restriction level.
4. The method of claim 3, further comprising:
acquiring a foreground process running on a foreground;
and when a background process with a dependency relationship with the foreground process exists, reducing the resource restriction level of the background process with the dependency relationship.
5. The method of claim 4, wherein after the obtaining a foreground process running in a foreground, the method further comprises:
and when the background process and the foreground process have a synchronization mechanism and/or a communication mechanism, determining the background process with the synchronization mechanism and/or the communication mechanism as the background process with the dependency relationship.
6. The method of claim 4, wherein after the obtaining a foreground process running in a foreground, the method further comprises:
when the foreground process is detected to have a lock waiting behavior, determining a waiting lock resource;
and if the background process waiting for the lock resource exists, determining the background process waiting for the lock resource as the background process with the dependency relationship.
7. The method of any of claims 4 to 6, wherein after the reducing the resource restriction level of the dependent background process, the method further comprises:
and when the foreground process finishes the dependency relationship with the background process, restoring the resource limit level of the background process which finishes the dependency relationship before reducing.
8. A resource management apparatus, comprising:
the scene determining module is used for acquiring the running characteristics of the background application and determining the application scene type of the background application according to the running characteristics, wherein the application scene type comprises a perceptible application and an imperceptible application; the perceivable application refers to an application that can be perceived by a user as running; the imperceptible application refers to an application that is imperceptible to a user to be running; the application scene type of the background application is changed along with the change of the running characteristic;
the level determining module is used for determining the resource limitation level of the background application according to the application scene type;
and the management module is used for carrying out resource management on the background application according to the resource limit level.
9. A mobile terminal comprising a memory and a processor, the memory having stored therein a computer program that, when executed by the processor, causes the processor to carry out the method of any one of claims 1 to 7.
10. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the method according to any one of claims 1 to 7.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201711488953.7A CN109992399B (en) | 2017-12-29 | 2017-12-29 | Resource management method, resource management device, mobile terminal and computer-readable storage medium |
| PCT/CN2018/116944 WO2019128571A1 (en) | 2017-12-29 | 2018-11-22 | Resource management method and device, mobile terminal, as well as computer readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201711488953.7A CN109992399B (en) | 2017-12-29 | 2017-12-29 | Resource management method, resource management device, mobile terminal and computer-readable storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109992399A CN109992399A (en) | 2019-07-09 |
| CN109992399B true CN109992399B (en) | 2021-04-23 |
Family
ID=67063038
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201711488953.7A Active CN109992399B (en) | 2017-12-29 | 2017-12-29 | Resource management method, resource management device, mobile terminal and computer-readable storage medium |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN109992399B (en) |
| WO (1) | WO2019128571A1 (en) |
Families Citing this family (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110554922A (en) * | 2019-09-05 | 2019-12-10 | 北京安云世纪科技有限公司 | System resource allocation method and device |
| CN110806926A (en) * | 2019-09-05 | 2020-02-18 | 华为技术有限公司 | Resource control method and equipment |
| CN112463350A (en) * | 2019-09-09 | 2021-03-09 | 珠海市魅族科技有限公司 | Background application optimization method and device, storage medium and electronic device |
| US12050937B2 (en) | 2021-09-21 | 2024-07-30 | International Business Machines Corporation | Preventing resource exploitation in mobile devices |
| CN117389711B (en) * | 2023-12-11 | 2024-04-09 | 腾讯科技（深圳）有限公司 | Scheduling method and device for terminal resources, terminal and computer readable storage medium |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102932935A (en) * | 2011-08-12 | 2013-02-13 | 中国移动通信集团公司 | Data transmission method and mobile terminal |
| CN106095592A (en) * | 2016-05-31 | 2016-11-09 | 广东欧珀移动通信有限公司 | A kind of prospect application scenarios synchronous method and device, system |
| CN107181700A (en) * | 2017-07-19 | 2017-09-19 | 努比亚技术有限公司 | Control method, mobile terminal and the storage medium of application program for mobile terminal |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20020184369A1 (en) * | 2001-05-31 | 2002-12-05 | Parkinson Steven William | Appointment scheme for redistributing service access |
| CN106293913A (en) * | 2016-08-01 | 2017-01-04 | 宇龙计算机通信科技(深圳)有限公司 | The control method of application program, control device and terminal |
-
2017
- 2017-12-29 CN CN201711488953.7A patent/CN109992399B/en active Active
-
2018
- 2018-11-22 WO PCT/CN2018/116944 patent/WO2019128571A1/en active Application Filing
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102932935A (en) * | 2011-08-12 | 2013-02-13 | 中国移动通信集团公司 | Data transmission method and mobile terminal |
| CN106095592A (en) * | 2016-05-31 | 2016-11-09 | 广东欧珀移动通信有限公司 | A kind of prospect application scenarios synchronous method and device, system |
| CN107181700A (en) * | 2017-07-19 | 2017-09-19 | 努比亚技术有限公司 | Control method, mobile terminal and the storage medium of application program for mobile terminal |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2019128571A1 (en) | 2019-07-04 |
| CN109992399A (en) | 2019-07-09 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109992398B (en) | Resource management method, resource management device, mobile terminal and computer-readable storage medium | |
| CN109992399B (en) | Resource management method, resource management device, mobile terminal and computer-readable storage medium | |
| EP3514684B1 (en) | Memory recovery method and apparatus | |
| CN107526640B (en) | Resource management method, resource management device, mobile terminal and computer-readable storage medium | |
| CN110032267B (en) | Information processing method and device, mobile terminal and computer readable storage medium | |
| CN110032429B (en) | Information processing method and device, mobile terminal and computer readable storage medium | |
| WO2019137173A1 (en) | Resource management method, mobile terminal and computer-readable storage medium | |
| WO2019128546A1 (en) | Application program processing method, electronic device, and computer readable storage medium | |
| CN109992400A (en) | Resource allocation methods, device, mobile terminal and computer readable storage medium | |
| CN110018902B (en) | Memory processing method and device, electronic equipment and computer readable storage medium | |
| WO2019128588A1 (en) | Process processing method and apparatus, electronic device, computer readable storage medium | |
| CN110046032A (en) | Applied program processing method and device, electronic equipment, computer readable storage medium | |
| CN110018885B (en) | Application program freezing method and device, storage medium and terminal | |
| CN109992309B (en) | Application program processing method and device, electronic equipment and computer readable storage medium | |
| CN109992360B (en) | Process processing method and device, electronic equipment and computer readable storage medium | |
| CN110018886B (en) | Application state switching method and device, electronic equipment and readable storage medium | |
| CN110032430B (en) | Application program processing method and device, electronic equipment and computer readable storage medium | |
| CN109375995B (en) | Application freezing method and device, storage medium and electronic equipment | |
| CN109992369B (en) | Application program processing method and device, electronic equipment and computer readable storage medium | |
| WO2019137187A1 (en) | Resource management method and apparatus, mobile terminal and computer-readable storage medium | |
| WO2019128570A1 (en) | Method and apparatus for freezing application, and storage medium and terminal | |
| CN110045811B (en) | Application program processing method and device, electronic equipment and computer readable storage medium | |
| WO2019128562A1 (en) | Application freezing method and apparatus, and terminal and computer-readable storage medium | |
| CN110753909B (en) | Service scheduling method and device, computer equipment and computer readable storage medium | |
| CN109995927B (en) | Information processing method and device, mobile terminal and computer readable storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| CB02 | Change of applicant information |
Address after: Changan town in Guangdong province Dongguan 523860 usha Beach Road No. 18 Applicant after: GUANGDONG OPPO MOBILE TELECOMMUNICATIONS Corp.,Ltd. Address before: Changan town in Guangdong province Dongguan 523860 usha Beach Road No. 18 Applicant before: GUANGDONG OPPO MOBILE TELECOMMUNICATIONS Corp.,Ltd. |
|
| CB02 | Change of applicant information | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |