CN112445606B - Memory recycling method and device - Google Patents

Memory recycling method and device Download PDF

Info

Publication number
CN112445606B
CN112445606B CN201910812574.1A CN201910812574A CN112445606B CN 112445606 B CN112445606 B CN 112445606B CN 201910812574 A CN201910812574 A CN 201910812574A CN 112445606 B CN112445606 B CN 112445606B
Authority
CN
China
Prior art keywords
memory
application
group
waterline
group information
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
Application number
CN201910812574.1A
Other languages
Chinese (zh)
Other versions
CN112445606A (en
Inventor
易见
李昌龙
李家欣
周未来
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to CN201910812574.1A priority Critical patent/CN112445606B/en
Priority to PCT/CN2020/110827 priority patent/WO2021036993A1/en
Publication of CN112445606A publication Critical patent/CN112445606A/en
Application granted granted Critical
Publication of CN112445606B publication Critical patent/CN112445606B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

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]
    • 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]
    • 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/5022—Mechanisms to release resources

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Memory System (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
  • Stored Programmes (AREA)

Abstract

The application provides a memory recycling method and device. The method comprises the following steps: when the fact that an application is started or switched to a foreground interface is monitored, acquiring a memory waterline of the application from a plurality of sets of pre-stored memory waterlines; when the memory recycling condition is met according to the memory waterline of the application and the system memory occupation information, determining an application of the memory to be recycled from the application currently running by the terminal equipment, and transmitting the memory waterline of the application into a kernel space for the kernel to execute memory recycling according to the memory waterline of the application. Therefore, the problems of excessive recovery and insufficient recovery of the memory can be avoided, and the keep-alive rate of the application is improved.

Description

Memory recycling method and device
Technical Field
The present application relates to the field of information technologies, and in particular, to a method and an apparatus for recovering a memory.
Background
In recent years, the demand of mobile Applications (APP) for memory is increasing, and the trend of increasing year by year is shown, and the memory capacity of the terminal device is limited, so that a large amount of application resident memory cannot be accommodated. Therefore, when the memory is insufficient, the system will perform memory reclamation.
In the prior art, the memory reclamation strategy is mainly based on the design of a memory waterline, monitors the system memory occupation information through a kernel process, triggers a memory reclamation mechanism when the monitored memory residual space is lower than a low (low) water level in the memory waterline, and reclaims file pages and anonymous pages of APP with the lowest priority from the memory according to the priority, and writes back to a storage device or compresses data. However, existing memory reclamation strategies sometimes fail to meet the actual needs.
Disclosure of Invention
The application provides a memory recycling method and device, which improve the flexibility of memory recycling and can avoid the problems of excessive memory recycling and insufficient memory recycling.
In a first aspect, the present application provides a memory reclamation method, including:
When the fact that an application is started or switched to a foreground interface is monitored, acquiring a memory waterline of the application from a plurality of sets of pre-stored memory waterlines;
When the memory recycling condition is met according to the memory waterline of the application and the system memory occupation information, determining an application of the memory to be recycled from the application currently running by the terminal equipment, and transmitting the memory waterline of the application into a kernel space for the kernel to execute memory recycling according to the memory waterline of the application.
By the memory recycling method provided by the first aspect, when the fact that an application is started or switched to a foreground interface is monitored, the memory waterline of the application is obtained from a plurality of sets of pre-stored memory waterlines, when the fact that the memory recycling condition is met is judged according to the memory waterline of the application and the system memory occupation information, the application of the memory to be recycled is determined from the application currently running by the terminal equipment, and the memory waterline of the application is transmitted into a kernel space for the kernel to execute memory recycling according to the memory waterline of the application. Therefore, for applications with different memory requirements, memory recovery can be performed according to different memory waterlines, so that the problems of excessive recovery and insufficient recovery of the memory can be avoided, and the keep-alive rate of the application can be improved.
In one possible design, the obtaining the memory waterline of the application from a pre-stored plurality of sets of memory waterlines includes:
searching a target group to which the application belongs from first group information, wherein the first group information comprises a mapping relation between the application in the group and a memory waterline;
determining the memory waterline of the target group as the memory waterline of the application; or alternatively
Determining a target group to which the application belongs according to the memory requirement of the application and second group information, wherein the second group information comprises a mapping relation between a group memory requirement range and a memory waterline;
and determining the memory waterline of the target group as the memory waterline of the application.
In one possible design, the first group information and the second group information are pre-stored.
In one possible design, the determining, according to the memory requirement of the application and the pre-stored second group information, the target group to which the application belongs includes:
And if the memory requirement of the application is within the memory requirement range of a group, determining the group as the target group.
In one possible design, the method further comprises:
Acquiring historical use memory data after each application is operated in a preset time, wherein the historical use memory data is the memory occupied by the application when the application is started, or the historical use memory data is the sum of the memory occupied by the application when the application is started and the memory occupied by a preset time period;
Predicting the memory requirement of each application according to the historical use memory data of each application, wherein the memory requirement is the memory required by starting; or the memory requirement is the sum of the memory required during starting and the expected use stage growth memory;
and acquiring the first group information or the second group information according to the predicted memory requirements of each application.
According to the memory recycling method provided by the embodiment, when the memory is recycled, the sum of the memory required by the APP memory requirement in starting and the expected use stage growth memory is considered, so that the accuracy of memory recycling can be further improved.
In one possible design, the obtaining the first group information according to the predicted memory requirement of each application includes:
And determining the memory waterline corresponding to each application according to the predicted memory requirements of each application and the multiple sets of memory waterlines, wherein all applications corresponding to one set of memory waterline are elements in one group, and at least one application is included in one group, so that the first group information is obtained.
In one possible design, the obtaining the second group information according to the predicted memory requirement of each application includes:
and grouping all the applications according to the predicted memory requirements of each application and the multiple sets of memory waterlines to obtain multiple groups, wherein one set of memory waterline corresponds to one group, and the applications in one memory requirement range belong to the same group to obtain the second group information.
In one possible design, the method further comprises:
and updating the first group information according to the update of the application in the group indicated by the configuration file.
In one possible design, the transferring the memory waterline of the application into the kernel space includes:
In a second aspect, the present application provides a memory reclamation apparatus, including:
The acquisition module is used for acquiring the memory waterline of the application from a plurality of sets of pre-stored memory waterlines when monitoring that the application is started or switched to a foreground interface;
And the processing module is used for determining the application of which the memory is to be recovered from the application currently running by the terminal equipment when the memory recovery condition is met according to the memory waterline of the application and the system memory occupation information, transmitting the memory waterline of the application into the kernel space, and executing the memory recovery by the kernel according to the memory waterline of the application.
In one possible design, the acquisition module is configured to:
searching a target group to which the application belongs from first group information, wherein the first group information comprises a mapping relation between the application in the group and a memory waterline;
determining the memory waterline of the target group as the memory waterline of the application; or alternatively
Determining a target group to which the application belongs according to the memory requirement of the application and second group information, wherein the second group information comprises a mapping relation between a group memory requirement range and a memory waterline;
and determining the memory waterline of the target group as the memory waterline of the application.
In one possible design, the first group information and the second group information are pre-stored.
In one possible design, the acquisition module is configured to:
And if the memory requirement of the application is within the memory requirement range of a group, determining the group as the target group.
In one possible design, the acquisition module is further configured to:
Acquiring historical use memory data after each application is operated in a preset time, wherein the historical use memory data is the memory occupied by the application when the application is started, or the historical use memory data is the sum of the memory occupied by the application when the application is started and the memory occupied by a preset time period;
Predicting the memory requirement of each application according to the historical use memory data of each application, wherein the memory requirement is the memory required by starting; or the memory requirement is the sum of the memory required during starting and the expected use stage growth memory;
and acquiring the first group information or the second group information according to the predicted memory requirements of each application.
In one possible design, the acquisition module is configured to:
And determining the memory waterline corresponding to each application according to the predicted memory requirements of each application and the multiple sets of memory waterlines, wherein all applications corresponding to one set of memory waterline are elements in one group, and at least one application is included in one group, so that the first group information is obtained.
In one possible design, the acquisition module is configured to:
and grouping all the applications according to the predicted memory requirements of each application and the multiple sets of memory waterlines to obtain multiple groups, wherein one set of memory waterline corresponds to one group, and the applications in one memory requirement range belong to the same group to obtain the second group information.
In one possible design, the processing module is further configured to:
and updating the first group information according to the update of the application in the group indicated by the configuration file.
In one possible design, the processing module is to:
And transmitting the memory waterline of the application into a kernel space through a reserved function interface.
The advantages of the memory reclamation device according to the second aspect and the possible designs of the second aspect may be referred to as the advantages of the possible embodiments of the first aspect and the possible embodiments of the first aspect, and are not described herein again.
In a third aspect, the present application provides a terminal device, including: a memory and a processor;
a processor; and
A memory for storing executable instructions of the processor;
Wherein the processor is configured to perform the memory reclamation method of the first aspect and any possible design of the first aspect by executing the executable instructions.
In a fourth aspect, the present application provides a readable storage medium, in which an execution instruction is stored, and when at least one processor of a terminal device executes the execution instruction, the terminal device executes the memory reclamation method in any of the first aspect and any possible designs of the first aspect.
In a fifth aspect, the present application provides a program product comprising execution instructions stored in a readable storage medium. The at least one processor of the terminal device may read the execution instructions from the readable storage medium, the execution instructions being executed by the at least one processor to cause the terminal device to implement the memory reclamation method of the first aspect and any possible design of the first aspect.
In a sixth aspect, the present application provides a chip, where the chip is connected to a memory, or the chip has a memory integrated thereon, and when a software program stored in the memory is executed, the memory reclamation method according to any of the first aspect and any possible design of the first aspect is implemented.
Drawings
FIG. 1 is a schematic diagram of a memory recycling process according to the present application;
FIG. 2 is a flowchart of an embodiment of a memory reclamation method according to the present application;
FIG. 3 is a flowchart of an embodiment of a memory reclamation method according to the present application;
FIG. 4 is a flowchart of an embodiment of a memory reclamation method according to the present application;
FIG. 5 is a flowchart of an embodiment of a memory reclamation method according to the present application;
FIG. 6 is a flowchart of an embodiment of a memory reclamation method according to the present application;
FIG. 7 is a schematic diagram of an embodiment of a memory recycling apparatus according to the present application;
fig. 8 is a schematic structural diagram of a terminal device according to the present application.
Detailed Description
In embodiments of the application, the words "exemplary" or "such as" are used to mean that any embodiment or aspect of the application described as "exemplary" or "such as" is not to be interpreted as preferred or advantageous over other embodiments or aspects. Rather, the use of words such as "exemplary" or "such as" is intended to present related concepts in a concrete fashion.
In embodiments of the present application, the terms "first," "second," and the like are used for descriptive purposes only and are not to be construed as indicating or implying relative importance. "at least one" means one or more, and "a plurality" means two or more.
The memory recycling method of the application can be used for recycling the memory of the terminal equipment, wherein the terminal equipment of the embodiment of the application: which may be a wireless terminal or a wired terminal, which may be a device that provides voice and/or other traffic data connectivity to a user, a handheld device with wireless connectivity, or other processing device connected to a wireless modem. A wireless terminal may communicate with one or more core networks via a Radio Access Network (RAN), which may be mobile terminals such as mobile telephones (or "cellular" telephones) and computers with mobile terminals, for example, portable, pocket, hand-held, computer-built-in, or vehicle-mounted mobile devices that exchange voice and/or data with the radio access network. Such as Personal communication services (Personal Communication Service, PCS) phones, cordless phones, session initiation protocol (Session Initiation Protocol, SIP) phones, wireless local loop (Wireless Local Loop, WLL) stations, personal digital assistants (Personal DIGITAL ASSISTANT, PDA) and the like. A wireless Terminal may also be referred to as a system, subscriber Unit (Subscriber Unit), subscriber Station (Subscriber Station), mobile Station (Mobile Station), remote Terminal (Remote Terminal), access Terminal (ACCESS TERMINAL), user Terminal (User Terminal), user Agent (User Agent), user equipment (User Device or User Equipment), without limitation.
In the related art, by setting a set of memory waterline, when the residual space of the memory is monitored to be lower than the low water level in the memory waterline, the memory recovery is triggered, but in the actual use process, some special applications, such as large-scale game applications, sometimes occur, if the memory recovery is performed according to the memory recovery strategy in the related art, the situation of insufficient memory recovery or excessive memory recovery occurs, and the actual requirements cannot be well met. In order to solve the problem, fig. 1 is a schematic diagram of a memory recycling process provided by the present application, and as shown in fig. 1, the present application executes memory recycling according to a memory waterline of an application currently started or an application currently switched to a foreground interface by running a memory recycling policy in a user mode when determining that a memory recycling condition is satisfied. Specifically, when the user state monitors that an application is started or switched to a foreground interface, a memory waterline of the application is obtained from a plurality of sets of pre-stored memory waterlines, when the memory waterline of the application and system memory occupation information are judged to meet a memory recycling condition, the application of the memory to be recycled is determined from the application currently running by the terminal equipment, the memory waterline of the application is transmitted into a kernel space, and the kernel performs memory recycling according to the memory waterline of the application. Therefore, for the application of different memory demands, the memory recovery can be carried out according to different memory waterlines, so that the problems of excessive recovery and insufficient recovery of the memory can be avoided. Further, since the memory requirement of APP tends to increase with the use time, in the embodiment of the present application, considering that the memory requirement of APP is the sum of the memory required at the start-up and the memory increased in the expected use stage, the accuracy of memory recovery can be further improved, and excessive recovery and insufficient recovery of the memory are avoided.
Fig. 2 is a flowchart of an embodiment of a memory recycling method according to the present application, where, as shown in fig. 2, the method of this embodiment may include:
And S101, acquiring the memory waterline of the application from a plurality of sets of pre-stored memory waterlines when the application is started or switched to a foreground interface.
Specifically, the running state of each application in the terminal equipment system can be monitored in real time in a user mode, when the fact that an application is started or switched to a foreground interface is monitored, the memory waterline of the application is obtained from a plurality of sets of pre-stored memory waterlines, and different applications, due to different memory requirements, can also be different in corresponding memory waterlines. It should be noted that, in the embodiment of the present application, the water line of the memory is divided into three water levels, i.e., high (High), low (Low) and minimum (Min).
As a first implementation manner, the obtaining the memory waterline of the application from the pre-stored sets of memory waterlines may be:
The method comprises the steps of searching a target group to which the application belongs from first group information, wherein the first group information comprises a mapping relation between the application and a memory waterline in the group, and determining the memory waterline of the target group as the memory waterline of the application.
Illustratively, the first group information is as shown in table one below:
List one
Group identification Within-group applications Internal memory waterline
1 APP1、APP2、APP3 Memory waterline I
2 APP4、APP5 Internal memory waterline II
3 APP6、APP7、APP8、APP9 Memory waterline III
…… …… ……
For example, the currently started application is APP1, the target group to which APP1 belongs is found from the first group information shown in table one as group 1, and the memory waterline one of group 1 is regarded as the memory waterline of APP 1. Table one is merely an example, and may not include group identification, but only the mapping relationship between the applications in the group and the memory waterline.
In a first implementation manner, the first group information may be acquired offline, i.e. pre-stored, or may be acquired online, and if the first group information is pre-stored, the first group information may be acquired by:
And acquiring first group information according to the historical use memory data of each application, wherein the historical use memory data is the memory required by the application when the application is started, or the historical use memory data is the sum of the memory required by the application when the application is started and the memory required by using a preset time period.
Specifically, when the historical use memory data is the memory required by the APP during starting, the memory required by each application during starting, that is, the memory occupied by the application during starting operation may be that each application is operated on different terminal devices, the memory data occupied by each application operated on different terminal devices is counted, and then the first group information is obtained according to all the historical use memory data.
When the historical memory data is the sum of the memory required during starting and the memory required during the preset time period, the preset time period can be, for example, half a day, one week, because the existing APP memory requirement tends to show increasing trend along with the use time, and when the owner glows for example, the anonymous page size can be obviously increased every time a game is played, therefore, the memory recovery accuracy can be further improved by considering the APP memory requirement as the sum of the memory required during starting and the memory which is increased in the expected use stage. Specifically, each application may be run on different terminal devices, the memory required by running each application on different terminal devices when starting and the memory required by using a preset time period are counted, the sum of the memory required by starting an application and the memory required by using the preset time period is used as historical use memory data, the historical use memory data of each application is obtained, and then the first group information is obtained according to all the historical use memory data.
As an implementation manner, the first group information may be acquired according to the following manner:
S101a, respectively predicting the memory requirements of each application according to the historical use memory data of each application, wherein the memory requirements are the memories required by starting; or the memory requirement is the sum of the memory required at start-up and the expected usage stage growth memory.
If the historical memory data is the memory required by starting, the predicted memory requirement of each application is the memory required by starting correspondingly. If the historical memory data is the sum of the memory required by starting and the memory required by using the preset time period, the predicted memory requirement of each application is the sum of the memory required by starting and the expected use stage increasing memory correspondingly.
S101b, determining a memory waterline corresponding to each application according to the predicted memory requirements of each application and a plurality of sets of memory waterlines, wherein all applications corresponding to one set of memory waterline are elements in one group, at least one application is included in one group, and a mapping relation between the applications in the group and the memory waterlines is obtained, namely the first group information.
For example, when all applications are grouped according to multiple sets of memory pipelines, for example, applications with memory requirements in a range may be grouped into one group, for example, applications with memory requirements of 0 MB-50 MB may be grouped into one group, applications with memory requirements of 50 MB-100 MB may be grouped into one group, applications with memory requirements of 1 GB-2 GB may be grouped into one group, and so on.
Optionally, after the group division is completed, a group identifier may be set for each group, so as to obtain a mapping relationship among the group identifier, the application in the group and the memory waterline, that is, the first group information.
After the obtained first group information is stored, the first group information can be updated later according to the group identification indicated by the configuration file and the intra-group application or the update of the intra-group application. That is, the applications in the group may be changed, for example, the memory requirement changes after a certain application version is updated, and the corresponding group changes, so that the applications in the group need to be updated.
As a second implementation manner, the obtaining the memory waterline of the application from the pre-stored sets of memory waterlines may be:
and determining a target group to which the application belongs according to the memory requirement of the application and pre-stored second group information, wherein the second group information comprises a mapping relation between a group memory requirement range and a memory waterline, and determining the memory waterline of the target group as the memory waterline of the application.
The determining, according to the memory requirement of the application and the pre-stored second group information, the target group to which the application belongs may specifically be: if the memory requirement of the application is within the memory requirement range of a group, the group is determined as a target group.
Optionally, the second group information may further include a group identifier, and illustratively, the second group information is shown in table two below:
Watch II
Group identification Memory demand range Internal memory waterline
1 0MB～100MB Memory waterline I
2 100MB～200MB Internal memory waterline II
3 1GB～1.5GB Memory waterline III
…… …… ……
For example, the application is currently started as APP3, if the memory requirement of APP3 is 150MB, and 150MB is within the memory requirement range of group 2 of 100 MB-200 MB, group 2 is determined as the target group, and the memory waterline of group 2 is taken as the memory waterline of APP 1.
In a second implementation manner, the second group information may be acquired offline, i.e. pre-stored, or may be acquired online, and if the second group information is pre-stored, the second group information may be acquired by: in a second implementation manner, the method may further include:
and acquiring second group information according to the historical use memory data of each application, wherein the historical use memory data is the memory required by starting, or the historical use memory data is the sum of the memory required by starting and the memory required by using a preset time period.
Specifically, when the historical use memory data is the memory required by the APP during starting, the memory required by each application during starting, that is, the memory occupied by the application during starting operation may be that each application is operated on different terminal devices, the memory data occupied by each application operated on different terminal devices is counted, and then the second group information is obtained according to all the historical use memory data.
When the historical memory data is the sum of the memory required during starting and the memory required during the preset time period, the preset time period can be, for example, half a day, one week, because the existing APP memory requirement tends to show increasing trend along with the use time, and when the owner glows for example, the anonymous page size can be obviously increased every time a game is played, therefore, the memory recovery accuracy can be further improved by considering the APP memory requirement as the sum of the memory required during starting and the memory which is increased in the expected use stage. Specifically, each application may be run on different terminal devices, the memory required by running each application on different terminal devices when starting and the memory required by using a preset time period are counted, the sum of the memory required by starting an application and the memory required by using the preset time period is used as historical use memory data, the historical use memory data of each application is obtained, and then the second group information is obtained according to all the historical use memory data.
As an implementation manner, the second group information may be acquired according to the following manner:
S101a', respectively predicting the memory requirements of each application according to the historical use memory data of each application, wherein the memory requirements are the memories required by starting; or the memory requirement is the sum of the memory required at start-up and the expected usage stage growth memory.
If the historical memory data is the memory required by starting, the predicted memory requirement of each application is the memory required by starting correspondingly. If the historical memory data is the sum of the memory required by starting and the memory required by using the preset time period, the predicted memory requirement of each application is the sum of the memory required by starting and the expected use stage increasing memory correspondingly.
S101b' performs group division on all applications according to the predicted memory requirements of each application and a plurality of sets of memory waterlines to obtain a plurality of groups, one set of memory waterline corresponds to one group, applications in one memory requirement range belong to the same group, and a mapping relation between the memory requirement range and the memory waterline is obtained, namely, the second group information performs group division on all applications according to the predicted memory requirements of each application to obtain a plurality of groups, and applications in one memory requirement range belong to the same group.
For example, when all applications are grouped according to multiple sets of memory waterlines, the applications with memory requirements in a range may be divided into one group, for example, applications with memory requirements of 0 MB-50 MB may be divided into one group, applications with memory requirements of 50 MB-100 MB may be divided into one group, applications with memory requirements of 1 GB-2 GB may be divided into one group, and so on, where the memory requirement range corresponding to each group may be obtained, for example, the memory ranges corresponding to three groups are 0 MB-50 MB, 50 MB-100 MB, and 1 GB-2 GB.
Specifically, after the group division is completed, a memory requirement range corresponding to each group can be obtained, a set of memory waterline and a group identifier are respectively set for each group, and a mapping relationship among the group identifier, the memory requirement range and the memory waterline is obtained, namely second group information.
In the first and second embodiments, if the first group information is obtained online, before S101, the method of this embodiment may further include:
S103, acquiring historical use memory data of each application after running in a preset time.
The historical use memory data is the memory occupied by the application when the application is started, or the historical use memory data is the sum of the memory occupied by the application when the application is started and the memory occupied by the use preset time period.
Specifically, after the user takes the terminal device, each application on the terminal device is operated, the system obtains the historical use memory data of each application after operation, and the preset time can be set according to the user.
S104, respectively predicting the memory requirements of each application according to the historical use memory data of each application, wherein the memory requirements are the memories required by starting; or the memory requirement is the sum of the memory required at start-up and the expected usage stage growth memory.
Specifically, when predicting the memory requirement, the prediction may be performed according to a preset rule, for example, taking an average value of the used memory after each application running, or taking a maximum value, etc.
S105, acquiring first group information or second group information according to the predicted memory requirements of each application.
Specifically, the obtaining the first group information according to the predicted memory requirement of each application may be:
And determining the memory waterline corresponding to each application according to the predicted memory requirements of each application and the multiple sets of memory waterlines, wherein all applications corresponding to one set of memory waterline are elements in one group, and at least one application is included in one group, so that first group information is obtained.
After the obtained first group information is stored, the first group information can be updated later according to the group identification indicated by the configuration file and the intra-group application or the update of the intra-group application. That is, the applications in the group may be changed, for example, the memory requirement changes after a certain application version is updated, and the corresponding group changes, so that the applications in the group need to be updated.
The obtaining of the second group information according to the predicted memory requirement of each application may be:
And grouping all the applications according to the predicted memory requirements of each application and a plurality of sets of memory waterlines to obtain a plurality of groups, wherein one set of memory waterline corresponds to one group, and the applications in one memory requirement range belong to the same group to obtain second group information.
When the first group information or the second group information is acquired in the online acquisition mode, the mapping relation between the application in the group and the memory waterline is acquired and updated according to the use habit of the user, so that the accuracy is higher.
S102, when the memory recycling condition is judged to be met according to the memory waterline of the application and the system memory occupation information, determining the application of the memory to be recycled from the application currently running by the terminal equipment, and transmitting the memory waterline of the application into a kernel space for the kernel to execute memory recycling according to the memory waterline of the application.
Specifically, for example, if the remaining space of the system memory is lower than the low water level in the memory pipeline of the target group, it is determined that the memory reclamation condition is satisfied.
After determining that the memory reclamation condition is met, determining the application to be reclaimed from the applications currently running by the terminal device, for example, determining the application to be reclaimed from the applications currently running according to the priority order of the applications to be reclaimed stored in advance, or according to other existing manners, embodiments of the present application are not limited in this respect. After determining the application of the memory to be recycled, performing system call, namely, transmitting the memory waterline of the application into a kernel space through a reserved function interface, determining a recycling termination condition by the kernel according to the memory waterline of the application, and executing memory recycling.
According to the memory recycling method provided by the embodiment, when the fact that an application is started or switched to a foreground interface is monitored, the memory waterline of the application is obtained from a plurality of sets of pre-stored memory waterlines, when the fact that the memory recycling condition is met is judged according to the memory waterline of the application and the system memory occupation information, the application of the memory to be recycled is determined from the application currently running by the terminal equipment, and the memory waterline of the application is transmitted into a kernel space for the kernel to execute memory recycling according to the memory waterline of the application. Therefore, for applications with different memory requirements, memory recovery can be performed according to different memory waterlines, so that the problems of excessive recovery and insufficient recovery of the memory can be avoided, and the keep-alive rate of the application can be improved.
The technical solution of the method embodiment shown in fig. 2 will be described in detail below using three specific embodiments.
Fig. 3 is a flowchart of an embodiment of a memory recycling method according to the present application, where, as shown in fig. 3, the method of this embodiment may include:
And S201, searching a target group to which the application belongs from prestored first group information when the application is started or switched to a foreground interface, wherein the first group information comprises a group identifier, a mapping relation between the application in the group and a memory waterline, and determining the memory waterline of the target group as the memory waterline of the application.
For example, the currently started application is APP4, the target group to which APP4 belongs is found from the first group information shown in table one to be group 2, and the memory waterline two of group 2 is taken as the memory waterline of APP 2.
Specifically, the first group information may be obtained according to the process of S101a to S101b in the embodiment shown in fig. 2, and the first group information is stored, and the detailed process may be referred to the detailed description of S101a to S101b in the embodiment shown in fig. 2, which is not repeated here.
After the obtained first group information is stored, the first group information can be updated later according to the group identification indicated by the configuration file and the update of the application in the group. That is, the applications within a group may vary.
S202, judging whether the memory recycling condition is met or not according to the memory waterline and the system memory occupation information of the application, if yes, executing S203, and if not, returning to executing S201.
S203, determining an application of which the memory is to be recovered from the application currently running by the terminal equipment, and transmitting the memory waterline of the application into a kernel space through a reserved function interface for the kernel to execute memory recovery according to the memory waterline of the application.
Fig. 4 is a flowchart of an embodiment of a memory reclaiming method according to the present application, as shown in fig. 4, the method of this embodiment may include:
And S301, when the fact that an application is started or switched to a foreground interface is monitored, determining a target group to which the application belongs according to the memory requirement of the application and pre-stored second group information, wherein the second group information comprises a mapping relation of a group identifier, a memory requirement range and a memory waterline, and determining the memory waterline of the target group as the memory waterline of the application.
The determining, according to the memory requirement of the application and the pre-stored second group information, the target group to which the application belongs may specifically be: if the memory requirement of the application is within the memory requirement range of a group, the group is determined as a target group.
For example, as shown in the second group information in the table two, the application is currently started as APP6, if the memory requirement of APP6 is 1.2GB, and 1.2GB is within the memory requirement range of group 3 of 1 GB-1.5 GB, group 3 is determined as the target group, and the memory waterline three of group 3 is taken as the memory waterline of APP 6.
Specifically, the second group information may be obtained according to the process of S101a 'to S101b' in the embodiment shown in fig. 2, and the second group information may be stored, and the detailed process may be referred to the detailed description of S101a 'to S101b' in the embodiment shown in fig. 2, which is not repeated herein.
S302, judging whether the memory recycling condition is met according to the memory waterline and the system memory occupation information of the application, if yes, executing S303, and if not, returning to executing S301.
S303, determining an application of which the memory is to be recovered from applications currently running in the terminal equipment, and transmitting a memory waterline of the application into a kernel space through a reserved function interface for the kernel to execute memory recovery according to the memory waterline of the application.
Fig. 5 is a flowchart of an embodiment of a memory reclamation method according to the present application, which is different from fig. 3 and fig. 4 in that in this embodiment, first group information is obtained online, as shown in fig. 5, the method of this embodiment may include:
S401, acquiring historical use memory data of each application after running in a preset time.
The historical use memory data is the memory occupied by the application when the application is started, or the historical use memory data is the sum of the memory occupied by the application when the application is started and the memory occupied by the use preset time period.
Specifically, after the user takes the terminal device, each application on the terminal device is operated, the system obtains the historical use memory data of each application after operation, and the preset time can be set according to the user.
S402, respectively predicting the memory requirements of each application according to the historical use memory data of each application.
The memory requirement is the memory required during starting; or the memory requirement is the sum of the memory required at start-up and the expected usage stage growth memory.
Specifically, when predicting the memory requirement, the prediction may be performed according to a preset rule, for example, taking an average value of the used memory after each application running, or taking a maximum value, etc.
S403, acquiring first group information according to the predicted memory requirements of each application, wherein the first group information comprises group identification, and the mapping relation between the applications in the group and the memory waterline.
Specifically, the first group information is obtained according to the predicted memory requirement of each application, specifically:
And determining the memory waterline corresponding to each application according to the predicted memory requirements of each application and the multiple sets of memory waterlines, wherein all applications corresponding to one set of memory waterline are elements in one group, and at least one application is included in one group, so that first group information is obtained.
After the obtained first group information is stored, the first group information can be updated later according to the group identification indicated by the configuration file and the intra-group application or the update of the intra-group application. That is, the applications in the group may be changed, for example, the memory requirement changes after a certain application version is updated, and the corresponding group changes, so that the applications in the group need to be updated.
And S404, when the fact that the application is started or switched to the foreground interface is monitored, searching a target group to which the application belongs from the first group information, and determining the memory waterline of the target group as the memory waterline of the application.
And S405, judging whether the memory recycling condition is met according to the memory waterline and the system memory occupation information of the application, if so, executing S403, and if not, returning to executing S404.
S406, determining an application of which the memory is to be recovered from applications currently running in the terminal equipment, and transmitting the memory waterline of the application into a kernel space through a reserved function interface for the kernel to execute memory recovery according to the memory waterline of the application.
Fig. 6 is a flowchart of an embodiment of a memory reclaiming method according to the present application, which is different from fig. 3 and fig. 4 in that in this embodiment, the second group information is obtained online, as shown in fig. 6, and the method of this embodiment may include:
S501, acquiring historical use memory data of each application after running in a preset time.
The historical use memory data is the memory occupied by the application when the application is started, or the historical use memory data is the sum of the memory occupied by the application when the application is started and the memory occupied by the use preset time period.
Specifically, after the user takes the terminal device, each application on the terminal device is operated, the system obtains the historical use memory data of each application after operation, and the preset time can be set according to the user.
S502, respectively predicting the memory requirements of each application according to the historical use memory data of each application.
The memory requirement is the memory required during starting; or the memory requirement is the sum of the memory required at start-up and the expected usage stage growth memory.
Specifically, when predicting the memory requirement, the prediction may be performed according to a preset rule, for example, taking an average value of the used memory after each application running, or taking a maximum value, etc.
S503, acquiring second group information according to the predicted memory requirements of each application, wherein the second group information comprises a group identifier, a memory requirement range and a mapping relation of a memory waterline.
Specifically, the second group information is obtained according to the predicted memory requirement of each application, specifically:
And grouping all the applications according to the predicted memory requirements of each application and a plurality of sets of memory waterlines to obtain a plurality of groups, wherein one set of memory waterline corresponds to one group, and the applications in one memory requirement range belong to the same group to obtain second group information.
And S504, when the fact that the application is started or switched to the foreground interface is monitored, determining a target group to which the application belongs according to the memory requirement of the application and the second group information, and determining the memory waterline of the target group as the memory waterline of the application.
S505, judging whether the memory recycling condition is met according to the memory waterline and the system memory occupation information of the application, if so, executing S503, and if not, returning to executing S504.
S506, determining an application of which the memory is to be recovered from the application currently running by the terminal equipment, and transmitting the memory waterline of the application into a kernel space through a reserved function interface for the kernel to execute memory recovery according to the memory waterline of the application.
Fig. 7 is a schematic structural diagram of an embodiment of a memory reclamation device according to the present application, as shown in fig. 7, the device of this embodiment may include: the system comprises an acquisition module 11 and a processing module 12, wherein the acquisition module 11 is used for acquiring a memory waterline of an application from a plurality of sets of pre-stored memory waterlines when the application is monitored to be started or switched to a foreground interface;
And the processing module 12 is configured to determine an application to be recycled from applications currently running in the terminal device when the memory recycling condition is determined to be met according to the memory waterline of the application and the system memory occupation information, and transmit the memory waterline of the application into the kernel space, so that the kernel performs memory recycling according to the memory waterline of the application.
Further, the obtaining module 11 is configured to:
searching a target group to which the application belongs from first group information, wherein the first group information comprises a mapping relation between the application in the group and a memory waterline;
determining the memory waterline of the target group as the memory waterline of the application; or alternatively
Determining a target group to which the application belongs according to the memory requirement of the application and second group information, wherein the second group information comprises a mapping relation between a group memory requirement range and a memory waterline;
and determining the memory waterline of the target group as the memory waterline of the application.
Optionally, the first group information and the second group information are pre-stored.
Further, the obtaining module 11 is configured to:
And if the memory requirement of the application is within the memory requirement range of a group, determining the group as the target group.
Further, the obtaining module 11 is further configured to:
Acquiring historical use memory data after each application is operated in a preset time, wherein the historical use memory data is the memory occupied by the application when the application is started, or the historical use memory data is the sum of the memory occupied by the application when the application is started and the memory occupied by a preset time period;
Predicting the memory requirement of each application according to the historical use memory data of each application, wherein the memory requirement is the memory required by starting; or the memory requirement is the sum of the memory required during starting and the expected use stage growth memory;
and acquiring the first group information or the second group information according to the predicted memory requirements of each application.
Further, the obtaining module 11 is configured to:
And determining the memory waterline corresponding to each application according to the predicted memory requirements of each application and the multiple sets of memory waterlines, wherein all applications corresponding to one set of memory waterline are elements in one group, and at least one application is included in one group, so that the first group information is obtained.
Further, the obtaining module 11 is configured to:
and grouping all the applications according to the predicted memory requirements of each application and the multiple sets of memory waterlines to obtain multiple groups, wherein one set of memory waterline corresponds to one group, and the applications in one memory requirement range belong to the same group to obtain the second group information.
Further, the processing module 12 is further configured to:
and updating the first group information according to the update of the application in the group indicated by the configuration file.
Further, the processing module 12 is configured to:
And transmitting the memory waterline of the application into a kernel space through a reserved function interface.
The apparatus of this embodiment may be used to implement the technical solution of the method embodiment shown in fig. 2, and its implementation principle is similar, and will not be described here again.
The present application may divide the function modules of the memory reclamation apparatus according to the above method example, for example, each function module may be divided corresponding to each function, or two or more functions may be integrated into one processing module. The integrated modules may be implemented in hardware or in software functional modules. It should be noted that, in the embodiments of the present application, the division of the modules is merely a logic function division, and other division manners may be implemented in practice.
Fig. 8 is a schematic structural diagram of a terminal device according to the present application, where the terminal device 200 includes:
A memory 201 and a processor 202;
A memory 201 for storing a computer program;
the processor 202 is configured to execute the computer program stored in the memory to implement the memory reclamation method in the above-mentioned embodiment. Reference may be made in particular to the relevant description of the embodiments of the method described above.
Alternatively, the memory 201 may be separate or integrated with the processor 202.
When the memory 201 is a device separate from the processor 202, the terminal apparatus 200 may further include:
Bus 203 for connecting memory 201 and processor 202.
Optionally, the present embodiment further includes: a communication interface 204, the communication interface 204 being connectable with the processor 202 via the bus 203. The processor 202 may control the communication interface 203 to implement the above-described functions of receiving and transmitting of the terminal device 200.
The terminal device may be configured to execute each step and/or flow corresponding to the terminal device in the foregoing method embodiment.
The application also provides a readable storage medium, wherein the readable storage medium stores an execution instruction, and when at least one processor of the terminal equipment executes the execution instruction, the terminal equipment executes the memory reclamation method in the embodiment of the method.
The present application also provides a program product comprising execution instructions stored in a readable storage medium. The at least one processor of the terminal device may read the execution instruction from the readable storage medium, where execution of the execution instruction by the at least one processor causes the terminal device to implement the memory reclamation method in the above-described method embodiment.
The application also provides a chip which is connected with the memory or is integrated with the memory, and when the software program stored in the memory is executed, the memory recycling method in the embodiment of the method is realized.
Those of ordinary skill in the art will appreciate that: in the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When loaded and executed on a computer, produces a flow or function in accordance with embodiments of the present application, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus. The computer instructions may be stored in or transmitted from one computer-readable storage medium to another, for example, by wired (e.g., coaxial cable, optical fiber, digital Subscriber Line (DSL)), or wireless (e.g., infrared, wireless, microwave, etc.). The computer readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that contains an integration of one or more available media. The usable medium may be a magnetic medium (e.g., floppy disk, hard disk, tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid state disk Solid STATE DISK (SSD)), etc.

Claims (16)

1. A memory reclamation method, comprising:
When the fact that an application is started or switched to a foreground interface is monitored, acquiring a memory waterline of the application from a plurality of sets of pre-stored memory waterlines;
When judging that the memory recycling condition is met according to the memory waterline of the application and the system memory occupation information, determining an application of the memory to be recycled from the application currently running by the terminal equipment, and transmitting the memory waterline of the application into a kernel space for a kernel to execute memory recycling according to the memory waterline of the application;
The obtaining the memory waterline of the application from the prestored multiple sets of memory waterlines comprises the following steps:
searching a target group to which the application belongs from first group information, wherein the first group information comprises a mapping relation between the application in the group and a memory waterline;
determining the memory waterline of the target group as the memory waterline of the application; or alternatively
Determining a target group to which the application belongs according to the memory requirement of the application and second group information, wherein the second group information comprises a mapping relation between a group memory requirement range and a memory waterline;
determining the memory waterline of the target group as the memory waterline of the application;
the method further comprises the steps of:
Acquiring historical use memory data after each application is operated in a preset time, wherein the historical use memory data is the memory occupied by the application when the application is started, or the historical use memory data is the sum of the memory occupied by the application when the application is started and the memory occupied by a preset time period;
Predicting the memory requirement of each application according to the historical use memory data of each application, wherein the memory requirement is the memory required by starting; or the memory requirement is the sum of the memory required during starting and the expected use stage growth memory;
and acquiring the first group information or the second group information according to the predicted memory requirements of each application.
2. The method of claim 1, wherein the first group information and the second group information are pre-stored.
3. The method of claim 1, wherein the determining the target group to which the application belongs according to the memory requirement of the application and the pre-stored second group information comprises:
And if the memory requirement of the application is within the memory requirement range of a group, determining the group as the target group.
4. The method of claim 1, wherein the obtaining the first group information according to the predicted memory requirements of the respective applications comprises:
And determining the memory waterline corresponding to each application according to the predicted memory requirements of each application and the multiple sets of memory waterlines, wherein all applications corresponding to one set of memory waterline are elements in one group, and at least one application is included in one group, so that the first group information is obtained.
5. The method of claim 1, wherein the obtaining the second group information according to the predicted memory requirements of the respective applications comprises:
and grouping all the applications according to the predicted memory requirements of each application and the multiple sets of memory waterlines to obtain multiple groups, wherein one set of memory waterline corresponds to one group, and the applications in one memory requirement range belong to the same group to obtain the second group information.
6. The method according to claim 1, wherein the method further comprises:
and updating the first group information according to the update of the application in the group indicated by the configuration file.
7. The method of claim 1, wherein the transferring the application's memory waterline into a kernel space comprises:
And transmitting the memory waterline of the application into a kernel space through a reserved function interface.
8. A memory reclamation apparatus, comprising:
The acquisition module is used for acquiring the memory waterline of the application from a plurality of sets of pre-stored memory waterlines when monitoring that the application is started or switched to a foreground interface;
the processing module is used for determining an application of which the memory is to be recovered from the application currently running by the terminal equipment when the memory recovery condition is met according to the memory waterline of the application and the system memory occupation information, and transmitting the memory waterline of the application into a kernel space, and executing memory recovery by the kernel according to the memory waterline of the application;
the acquisition module is used for:
searching a target group to which the application belongs from first group information, wherein the first group information comprises a mapping relation between the application in the group and a memory waterline;
determining the memory waterline of the target group as the memory waterline of the application; or alternatively
Determining a target group to which the application belongs according to the memory requirement of the application and second group information, wherein the second group information comprises a mapping relation between a group memory requirement range and a memory waterline;
determining the memory waterline of the target group as the memory waterline of the application;
The acquisition module is further configured to:
Acquiring historical use memory data after each application is operated in a preset time, wherein the historical use memory data is the memory occupied by the application when the application is started, or the historical use memory data is the sum of the memory occupied by the application when the application is started and the memory occupied by a preset time period;
Predicting the memory requirement of each application according to the historical use memory data of each application, wherein the memory requirement is the memory required by starting; or the memory requirement is the sum of the memory required during starting and the expected use stage growth memory;
and acquiring the first group information or the second group information according to the predicted memory requirements of each application.
9. The apparatus of claim 8, wherein the first group information and the second group information are pre-stored.
10. The apparatus of claim 8, wherein the acquisition module is configured to:
And if the memory requirement of the application is within the memory requirement range of a group, determining the group as the target group.
11. The apparatus of claim 8, wherein the acquisition module is configured to:
And determining the memory waterline corresponding to each application according to the predicted memory requirements of each application and the multiple sets of memory waterlines, wherein all applications corresponding to one set of memory waterline are elements in one group, and at least one application is included in one group, so that the first group information is obtained.
12. The apparatus of claim 8, wherein the acquisition module is configured to:
and grouping all the applications according to the predicted memory requirements of each application and the multiple sets of memory waterlines to obtain multiple groups, wherein one set of memory waterline corresponds to one group, and the applications in one memory requirement range belong to the same group to obtain the second group information.
13. The apparatus of claim 8, wherein the processing module is further configured to:
and updating the first group information according to the update of the application in the group indicated by the configuration file.
14. The apparatus of claim 8, wherein the processing module is to:
And transmitting the memory waterline of the application into a kernel space through a reserved function interface.
15. A terminal device, comprising:
a processor; and
A memory for storing executable instructions of the processor;
Wherein the processor is configured to perform the memory reclamation method of any of claims 1-7 via execution of the executable instructions.
16. A readable storage medium having stored therein execution instructions, characterized in that when executed by at least one processor of a terminal device, the terminal device performs the memory reclamation method according to any of claims 1-7.
CN201910812574.1A 2019-08-30 2019-08-30 Memory recycling method and device Active CN112445606B (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN201910812574.1A CN112445606B (en) 2019-08-30 2019-08-30 Memory recycling method and device
PCT/CN2020/110827 WO2021036993A1 (en) 2019-08-30 2020-08-24 Memory reclaiming method and apparatus

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201910812574.1A CN112445606B (en) 2019-08-30 2019-08-30 Memory recycling method and device

Publications (2)

Publication Number Publication Date
CN112445606A CN112445606A (en) 2021-03-05
CN112445606B true CN112445606B (en) 2024-06-18

Family

ID=74684164

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201910812574.1A Active CN112445606B (en) 2019-08-30 2019-08-30 Memory recycling method and device

Country Status (2)

Country Link
CN (1) CN112445606B (en)
WO (1) WO2021036993A1 (en)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113961427B (en) * 2021-12-20 2022-05-24 荣耀终端有限公司 System memory analysis method and electronic equipment
CN116700944A (en) * 2022-11-03 2023-09-05 荣耀终端有限公司 Memory recycling method and device and electronic equipment

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108205474A (en) * 2017-08-23 2018-06-26 珠海市魅族科技有限公司 EMS memory management process, terminal device, computer installation and readable storage medium storing program for executing

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7852699B2 (en) * 2007-10-04 2010-12-14 Macronix International Co., Ltd. Power saving method and circuit thereof for a semiconductor memory
CN102968335A (en) * 2012-10-25 2013-03-13 东莞宇龙通信科技有限公司 Terminal and terminal memory management method
CN103902359B (en) * 2014-03-31 2018-02-23 深圳创维－Rgb电子有限公司 Based on android system internal memory optimization and application scheduling method thereof and system
CN105701025B (en) * 2015-12-31 2019-07-23 华为技术有限公司 A kind of method for recovering internal storage and device
CN109213539B (en) * 2016-09-27 2021-10-26 华为技术有限公司 Memory recovery method and device
CN109669877B (en) * 2018-12-11 2023-04-04 腾讯科技（深圳）有限公司 Memory management method, device, terminal and storage medium
CN109656722B (en) * 2019-01-04 2021-05-11 Oppo广东移动通信有限公司 Memory optimization method and device, mobile terminal and storage medium

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108205474A (en) * 2017-08-23 2018-06-26 珠海市魅族科技有限公司 EMS memory management process, terminal device, computer installation and readable storage medium storing program for executing

Also Published As

Publication number Publication date
CN112445606A (en) 2021-03-05
WO2021036993A1 (en) 2021-03-04

Similar Documents

Publication Publication Date Title
CN112445606B (en) Memory recycling method and device
CN107071824B (en) A kind of method and device called under network congestion
CN101730304A (en) Apparatus and method for application of multi operating systems in multi modem mobile communication terminal
CN101540799A (en) Mobile terminal software upgrading method
TWI697239B (en) Resource block group division method and user terminal
CN110868339A (en) Node distribution method and device, electronic equipment and readable storage medium
CN105224421A (en) Data backup method and device and electronic equipment
CN106171019A (en) Determine the method for terminal roaming status, device, terminal and server
CN112566187A (en) Bandwidth allocation method, device, computer equipment and computer readable storage medium
CN105824660A (en) Application program updating method and terminal
CN104580757A (en) Phone state sharing method and device
CN111669831B (en) Resource allocation method and device
CN103259869A (en) Concentrated information management method based on distributed data storage
CN112787828A (en) Application flow statistical method and device and mobile electronic device
CN102300198B (en) Realize method and system and the mobile phone remote service centre of mobile phone remote service
CN113115400B (en) Communication method and device
CN111683407B (en) Resource allocation method and device
US20210357252A1 (en) Application management method and apparatus, and device
CN112380411B (en) Sensitive word processing method, device, electronic equipment, system and storage medium
CN110475362B (en) Method and equipment for adjusting transmission resources
CN113542447A (en) Method and device for preventing information leakage, terminal equipment and readable storage medium
CN114173318A (en) Method, device and equipment for identifying to-be-optimized area
CN103685776A (en) Method and device for processing call
CN114501635A (en) Slice resource allocation method, SMF entity, UPF entity and storage medium
CN114554502B (en) Distribution method, device, base station and medium for cell wireless network temporary identifier

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
GR01 Patent grant