CN108196938B - Memory calling method, mobile terminal and computer readable storage medium - Google Patents
Memory calling method, mobile terminal and computer readable storage medium Download PDFInfo
- Publication number
- CN108196938B CN108196938B CN201711446055.5A CN201711446055A CN108196938B CN 108196938 B CN108196938 B CN 108196938B CN 201711446055 A CN201711446055 A CN 201711446055A CN 108196938 B CN108196938 B CN 108196938B
- Authority
- CN
- China
- Prior art keywords
- memory
- memory data
- data block
- mobile terminal
- server
- 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/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F12/00—Accessing, addressing or allocating within memory systems or architectures
- G06F12/02—Addressing or allocation; Relocation
- G06F12/0223—User address space allocation, e.g. contiguous or non contiguous base addressing
- G06F12/023—Free address space management
- G06F12/0253—Garbage collection, i.e. reclamation of unreferenced 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/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
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Telephone Function (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
The invention discloses a memory calling method, which comprises the following steps: regularly acquiring memory data blocks corresponding to all the method functions from a server; storing all the acquired memory data blocks to a disk space of the mobile terminal; when a method function needs to be called, judging whether a memory data block corresponding to the method function in a memory is recycled; when the memory data block is recovered, searching the memory data block corresponding to the method function from the disk space of the mobile terminal; and writing the memory data block into a memory to run the method function. The embodiment of the invention also discloses a mobile terminal and a computer readable storage medium. This can reduce the operation frequency of memory collection and generation.
Description
Technical Field
The present invention relates to the technical field of memory optimization, and in particular, to a memory calling method, a mobile terminal, and a computer-readable storage medium.
Background
The applications in the android operating system are all realized by Java, based on a JVM virtual machine, a memory recovery mechanism of the JVM virtual machine is timing recovery, and a memory recovery task of the JVM virtual machine scans the memory and recovers useless memory. When the application is used frequently, the memory space occupied by the application is large, at the moment, the memory recovery is also frequent, the CPU occupancy rate is high, and the use smoothness of the application is influenced. And some applications can generate larger memory space when executing certain operations, and memory recovery occurs within a certain time after the memory space is used up, but when the applications execute the operations again, the memory data is generated again, namely, the applications need to apply for new memory repeatedly, the response speed is slower, and the system efficiency is lower. Moreover, when the memory recovery and generation actions are frequent, the system power consumption is also influenced to a certain extent.
Disclosure of Invention
The invention mainly aims to provide a memory calling method and a corresponding mobile terminal, and aims to solve the problem of how to reduce the action frequency of memory recovery and generation.
In order to achieve the above object, the present invention provides a memory calling method applied to a mobile terminal, including:
regularly acquiring memory data blocks corresponding to all the method functions from a server;
storing all the acquired memory data blocks to a disk space of the mobile terminal;
when a method function needs to be called, judging whether a memory data block corresponding to the method function in a memory is recycled;
when the memory data block is recovered, searching the memory data block corresponding to the method function from the disk space of the mobile terminal; and
and writing the memory data block into a memory to run the method function.
Optionally, before the step of obtaining the memory data blocks corresponding to all the method functions from the server at regular time, the method further includes the steps of:
monitoring various method functions operated in the mobile terminal, and recording information of each method function;
acquiring a memory change time threshold value set by the server;
and sending the memory data block with the recorded memory change times smaller than or equal to the memory change time threshold value to the server for statistics.
Optionally, the information of each method function includes a method function name, a parameter value combination, a memory change time, and a specific memory data block; in the step of obtaining the memory data blocks corresponding to all the method functions from the server at regular time, the obtained content also includes the name of the method function, a combination of parameter values, the number of memory changes and a specific memory data block.
Optionally, the process of counting the memory data blocks by the server includes:
collecting the memory data blocks uploaded by all mobile terminals in communication connection with the server;
combining corresponding memory data blocks under the condition that the name, the parameter value and the memory change times of the method function uploaded by each mobile terminal are the same;
analyzing whether memory change of each mobile terminal aiming at the memory data block is repeated or not so as to merge memory change times of the memory data block;
and judging whether the combined memory change times is greater than the memory change time threshold value or not so as to determine whether the memory data block should be stored or deleted.
Optionally, when the memory change times after the memory data blocks are merged are less than or equal to the memory change time threshold, the server stores the memory data blocks, the corresponding method function names, the parameter values and the merged memory change times;
and when the memory change times after the memory data blocks are combined are larger than the memory change time threshold, the server deletes the memory data blocks and the related records.
Optionally, for the memory data block with the change frequency of 0, when the memory is recovered after the corresponding method function is completed, performing countdown marking on the memory data block, and within the time range of the countdown marking, not recovering the memory data block until the time range is passed, and then recovering the memory data block.
Optionally, in the step of searching the memory data block corresponding to the method function from the disk space of the mobile terminal, the memory data block required for operating the method function is searched from the disk space according to the information of the method name, the parameter value combination, and the memory change frequency.
Optionally, the method further comprises the step of:
and when the memory data block counted in the server changes, the mobile terminal receives a push notification sent by the server, acquires the changed memory data block, and updates the memory data block into the disk space.
In addition, to achieve the above object, the present invention further provides a mobile terminal, including: the memory calling method comprises a memory, a processor, a screen and a memory calling program which is stored on the memory and can run on the processor, wherein when the memory calling program is executed by the processor, the steps of the memory calling method are realized.
Further, to achieve the above object, the present invention also provides a computer readable storage medium, where a memory calling program is stored, and when the memory calling program is executed by a processor, the steps of the memory calling method are implemented.
The memory calling method, the mobile terminal and the computer readable storage medium can realize memory optimization according to the memory change frequency. The mobile terminal monitoring system and all method functions called in the application running process analyze the memory data blocks and the memory change times generated in the running process and upload the memory data blocks to the server, and the server counts the memory data blocks uploaded by all the mobile terminals and then sends the memory data blocks to the mobile terminals at regular time. For the memory data blocks which cannot be changed, a countdown mark is added during memory recovery, real recovery is not carried out within a certain time range, and the memory data blocks are copied to the disk space of the mobile terminal, so that the generation frequency of repeated memory data blocks is reduced. For the memory data blocks with low memory change times, in the operation process of the method function, the corresponding memory data blocks are copied from the disk space to the memory area, and the memory data blocks required to be used are directly positioned along with the operation of the method function, so that the generation times of the memory data blocks are reduced. According to the scheme, the memory generation and recovery times are reduced by combining a memory pre-generation technology according to the analysis and the record of the change times and the content of the memory data block, so that the running speed and the smoothness of a system and an application are improved, and the power consumption of the mobile terminal can be reduced.
Drawings
Fig. 1 is a schematic diagram of a hardware structure of a mobile terminal implementing various embodiments of the present invention;
FIG. 2 is a diagram of a wireless communication system for the mobile terminal shown in FIG. 1;
FIG. 3 is a diagram of an application environment architecture in which various embodiments of the present invention may be implemented;
fig. 4 is a flowchart of a memory calling method according to a first embodiment of the present invention;
fig. 5 is a flowchart of a memory calling method according to a second embodiment of the present invention;
fig. 6 is a block diagram of a mobile terminal according to a third embodiment of the present invention;
fig. 7 is a block diagram of a memory call system according to a fourth embodiment of the present invention;
fig. 8 is a block diagram illustrating a memory call system according to a fifth embodiment of the present invention.
The implementation, functional features and advantages of the objects of the present invention will be further explained with reference to the accompanying drawings.
Detailed Description
It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.
In the following description, suffixes such as "module", "component", or "unit" used to denote elements are used only for facilitating the explanation of the present invention, and have no specific meaning in itself. Thus, "module", "component" or "unit" may be used mixedly.
The terminal may be implemented in various forms. For example, the terminal described in the present invention may include a mobile terminal such as a mobile phone, a tablet computer, a notebook computer, a palmtop computer, a Personal Digital Assistant (PDA), a Portable Media Player (PMP), a navigation device, a wearable device, a smart band, a pedometer, and the like, and a fixed terminal such as a Digital TV, a desktop computer, and the like.
The following description will be given by way of example of a mobile terminal, and it will be understood by those skilled in the art that the construction according to the embodiment of the present invention can be applied to a fixed type terminal, in addition to elements particularly used for mobile purposes.
Referring to fig. 1, which is a schematic diagram of a hardware structure of a mobile terminal for implementing various embodiments of the present invention, the mobile terminal 100 may include: RF (Radio Frequency) unit 101, WiFi module 102, audio output unit 103, a/V (audio/video) input unit 104, sensor 105, display unit 106, user input unit 107, interface unit 108, memory 109, processor 110, and power supply 111. Those skilled in the art will appreciate that the mobile terminal architecture shown in fig. 1 is not intended to be limiting of mobile terminals, which may include more or fewer components than those shown, or some components may be combined, or a different arrangement of components.
The following describes each component of the mobile terminal in detail with reference to fig. 1:
the radio frequency unit 101 may be configured to receive and transmit signals during information transmission and reception or during a call, and specifically, receive downlink information of a base station and then process the downlink information to the processor 110; in addition, the uplink data is transmitted to the base station. Typically, radio frequency unit 101 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, and the like. In addition, the radio frequency unit 101 can also communicate with a network and other devices through wireless communication. The wireless communication may use any communication standard or protocol, including but not limited to GSM (Global System for Mobile communications), GPRS (General Packet Radio Service), CDMA2000(Code Division Multiple Access 2000), WCDMA (Wideband Code Division Multiple Access), TD-SCDMA (Time Division-Synchronous Code Division Multiple Access), FDD-LTE (Frequency Division duplex Long Term Evolution), and TDD-LTE (Time Division duplex Long Term Evolution).
WiFi belongs to short-distance wireless transmission technology, and the mobile terminal can help a user to receive and send e-mails, browse webpages, access streaming media and the like through the WiFi module 102, and provides wireless broadband internet access for the user. Although fig. 1 shows the WiFi module 102, it is understood that it does not belong to the essential constitution of the mobile terminal, and may be omitted entirely as needed within the scope not changing the essence of the invention.
The audio output unit 103 may convert audio data received by the radio frequency unit 101 or the WiFi module 102 or stored in the memory 109 into an audio signal and output as sound when the mobile terminal 100 is in a call signal reception mode, a call mode, a recording mode, a voice recognition mode, a broadcast reception mode, or the like. Also, the audio output unit 103 may also provide audio output related to a specific function performed by the mobile terminal 100 (e.g., a call signal reception sound, a message reception sound, etc.). The audio output unit 103 may include a speaker, a buzzer, and the like.
The a/V input unit 104 is used to receive audio or video signals. The a/V input Unit 104 may include a Graphics Processing Unit (GPU) 1041 and a microphone 1042, the Graphics processor 1041 Processing image data of still pictures or video obtained by an image capturing device (e.g., a camera) in a video capturing mode or an image capturing mode. The processed image frames may be displayed on the display unit 106. The image frames processed by the graphic processor 1041 may be stored in the memory 109 (or other storage medium) or transmitted via the radio frequency unit 101 or the WiFi module 102. The microphone 1042 may receive sounds (audio data) via the microphone 1042 in a phone call mode, a recording mode, a voice recognition mode, or the like, and may be capable of processing such sounds into audio data. The processed audio (voice) data may be converted into a format output transmittable to a mobile communication base station via the radio frequency unit 101 in case of a phone call mode. The microphone 1042 may implement various types of noise cancellation (or suppression) algorithms to cancel (or suppress) noise or interference generated in the course of receiving and transmitting audio signals.
The mobile terminal 100 also includes at least one sensor 105, such as a light sensor, a motion sensor, and other sensors. Specifically, the light sensor includes an ambient light sensor that can adjust the brightness of the display panel 1061 according to the brightness of ambient light, and a proximity sensor that can turn off the display panel 1061 and/or a backlight when the mobile terminal 100 is moved to the ear. As one of the motion sensors, the accelerometer sensor can detect the magnitude of acceleration in each direction (generally, three axes), can detect the magnitude and direction of gravity when stationary, and can be used for applications of recognizing the posture of a mobile phone (such as horizontal and vertical screen switching, related games, magnetometer posture calibration), vibration recognition related functions (such as pedometer and tapping), and the like; as for other sensors such as a fingerprint sensor, a pressure sensor, an iris sensor, a molecular sensor, a gyroscope, a barometer, a hygrometer, a thermometer, and an infrared sensor, which can be configured on the mobile phone, further description is omitted here.
The display unit 106 is used to display information input by a user or information provided to the user. The Display unit 106 may include a Display panel 1061, and the Display panel 1061 may be configured in the form of a Liquid Crystal Display (LCD), an Organic Light-Emitting Diode (OLED), or the like.
The user input unit 107 may be used to receive input numeric or character information and generate key signal inputs related to user settings and function control of the mobile terminal. Specifically, the user input unit 107 may include a touch panel 1071 and other input devices 1072. The touch panel 1071, also referred to as a touch screen, may collect a touch operation performed by a user on or near the touch panel 1071 (e.g., an operation performed by the user on or near the touch panel 1071 using a finger, a stylus, or any other suitable object or accessory), and drive a corresponding connection device according to a predetermined program. The touch panel 1071 may include two parts of 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 110, and can receive and execute commands sent by the processor 110. In addition, the touch panel 1071 may be implemented in various types, such as a resistive type, a capacitive type, an infrared ray, and a surface acoustic wave. In addition to the touch panel 1071, the user input unit 107 may include other input devices 1072. In particular, other input devices 1072 may include, but are not limited to, one or more of a physical keyboard, function keys (e.g., volume control keys, switch keys, etc.), a trackball, a mouse, a joystick, and the like, and are not limited to these specific examples.
Further, the touch panel 1071 may cover the display panel 1061, and when the touch panel 1071 detects a touch operation thereon or nearby, the touch panel 1071 transmits the touch operation to the processor 110 to determine the type of the touch event, and then the processor 110 provides a corresponding visual output on the display panel 1061 according to the type of the touch event. Although the touch panel 1071 and the display panel 1061 are shown in fig. 1 as two separate components to implement the input and output functions of the mobile terminal, in some embodiments, the touch panel 1071 and the display panel 1061 may be integrated to implement the input and output functions of the mobile terminal, and is not limited herein.
The interface unit 108 serves as an interface through which at least one external device is connected to the mobile terminal 100. For example, the external device may include a wired or wireless headset port, an external power supply (or battery charger) port, a wired or wireless data port, a memory card port, a port for connecting a device having an identification module, an audio input/output (I/O) port, a video I/O port, an earphone port, and the like. The interface unit 108 may be used to receive input (e.g., data information, power, etc.) from external devices and transmit the received input to one or more elements within the mobile terminal 100 or may be used to transmit data between the mobile terminal 100 and external devices.
The memory 109 may be used to store software programs as well as various data. The memory 109 may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required by at least one function (such as a sound playing function, an image playing function, etc.), and the like; the storage data area may store data (such as audio data, a phonebook, etc.) created according to the use of the cellular phone, and the like. Further, the memory 109 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 processor 110 is a control center of the mobile terminal, connects various parts of the entire mobile terminal using various interfaces and lines, and performs various functions of the mobile terminal and processes data by operating or executing software programs and/or modules stored in the memory 109 and calling data stored in the memory 109, thereby performing overall monitoring of the mobile terminal. Processor 110 may include one or more processing units; preferably, the processor 110 may integrate an application processor, which mainly handles operating systems, user interfaces, application programs, etc., and a modem processor, which mainly handles wireless communications. It will be appreciated that the modem processor described above may not be integrated into the processor 110.
The mobile terminal 100 may further include a power supply 111 (e.g., a battery) for supplying power to various components, and preferably, the power supply 111 may be logically connected to the processor 110 via a power management system, so as to manage charging, discharging, and power consumption management functions via the power management system.
Although not shown in fig. 1, the mobile terminal 100 may further include a bluetooth module or the like, which is not described in detail herein.
In order to facilitate understanding of the embodiments of the present invention, a communication network system on which the mobile terminal of the present invention is based is described below.
Referring to fig. 2, fig. 2 is an architecture diagram of a communication Network system according to an embodiment of the present invention, where the communication Network system is an LTE system of a universal mobile telecommunications technology, and the LTE system includes a UE (User Equipment) 201, an E-UTRAN (Evolved UMTS Terrestrial Radio Access Network) 202, an EPC (Evolved Packet Core) 203, and an IP service 204 of an operator, which are in communication connection in sequence.
Specifically, the UE201 may be the terminal 100 described above, and is not described herein again.
The E-UTRAN202 includes eNodeB2021 and other eNodeBs 2022, among others. Among them, the eNodeB2021 may be connected with other eNodeB2022 through backhaul (e.g., X2 interface), the eNodeB2021 is connected to the EPC203, and the eNodeB2021 may provide the UE201 access to the EPC 203.
The EPC203 may include an MME (Mobility Management Entity) 2031, an HSS (Home Subscriber Server) 2032, other MMEs 2033, an SGW (Serving gateway) 2034, a PGW (PDN gateway) 2035, and a PCRF (Policy and Charging Rules Function) 2036, and the like. The MME2031 is a control node that handles signaling between the UE201 and the EPC203, and provides bearer and connection management. HSS2032 is used to provide registers to manage functions such as home location register (not shown) and holds subscriber specific information about service characteristics, data rates, etc. All user data may be sent through SGW2034, PGW2035 may provide IP address assignment for UE201 and other functions, and PCRF2036 is a policy and charging control policy decision point for traffic data flow and IP bearer resources, which selects and provides available policy and charging control decisions for a policy and charging enforcement function (not shown).
The IP services 204 may include the internet, intranets, IMS (IP Multimedia Subsystem), or other IP services, among others.
Although the LTE system is described as an example, it should be understood by those skilled in the art that the present invention is not limited to the LTE system, but may also be applied to other wireless communication systems, such as GSM, CDMA2000, WCDMA, TD-SCDMA, and future new network systems.
Based on the above mobile terminal hardware structure and communication network system, the present invention provides various embodiments of the method.
Referring to fig. 3, fig. 3 is a diagram illustrating an application environment architecture for implementing various embodiments of the present invention. The present invention is applicable in an application environment including, but not limited to, a server 2, a mobile terminal 4, and a network 6.
In this embodiment, the server 2 is a JVM virtual machine. The mobile terminal 4 may be a mobile device of a mobile phone, a smart phone, a notebook computer, a digital broadcast receiver, a PDA (personal digital assistant), a PAD (tablet computer), a PMP (portable multimedia player), a navigation device, a vehicle-mounted device, or the like.
The network 6 may be a wireless or wired network such as an Intranet (Intranet), the Internet (Internet), a Global System of Mobile communication (GSM), Wideband Code Division Multiple Access (WCDMA), a 4G network, a 5G network, Bluetooth (Bluetooth), Wi-Fi, and the like. The server 2 is respectively connected with one or more mobile terminals 4 through the network 6 in a communication way so as to carry out data transmission and interaction.
The memory calling method provided by the invention is used for realizing memory optimization according to the memory change frequency and reducing the action frequency of memory recovery and generation.
Example one
As shown in fig. 4, a first embodiment of the present invention provides a memory calling method, including the following steps:
and S400, regularly acquiring the memory data blocks corresponding to all the method functions from the server 2.
Specifically, the acquired content includes a method function name, a parameter value combination, memory change times, and a specific memory data block. Various method functions are called during the operation of the system and the application of the mobile terminal 4. Each method function carries parameters, and each parameter has a specific value. During the operation of a method function, various memory data blocks are generated. Therefore, the memory change frequency in the operation process of the method function is recorded and analyzed by taking the method function and the specific parameter thereof as a unit, so that the memory data blocks respectively corresponding to each change frequency can be obtained, and the memory data blocks corresponding to all the method functions are distinguished. For example, there is a method function a, which carries a parameter B. The value combination for parameter B included 1 and 3 in all the running records. Assuming that no matter what value the parameter B is, the memory data block a and the memory data block B are generated in the operation process, and the memory data block a and the memory data block B are not changed each time, the memory data block a and the memory data block B are the memory data blocks with the change frequency of 0 following the method function a. Assuming that when the value of the parameter B is 1, the generated memory data blocks have c and d; when the value of the parameter B is 3, the generated memory data blocks have c and e. Then, for the method function a when the value of the parameter B is 1, the memory data blocks c and d with the change times of 1; and for the method function A with the parameter B of 3, the memory data blocks c and e with the change times of 1. The mobile terminal 4 acquires various memory data blocks corresponding to all the method functions counted by the server 2 from the server 2 at regular time.
When the memory data block counted in the server 2 changes, the changed memory data block is updated to the mobile terminal 4 in time through a push notification mechanism, so as to ensure that the memory data block in the mobile terminal 4 is the latest. And the mobile terminal 4 receives the push notification sent by the server 2, acquires the changed memory data block, and updates the memory data block to the disk space.
S402, storing all the acquired memory data blocks to the disk space of the mobile terminal 4.
Specifically, after the memory data blocks corresponding to all the method functions are obtained from the server 2, the memory data blocks are stored in the disk space of the mobile terminal 4 for direct use when the method functions need to be run subsequently. Because the disk space of the mobile terminal 4 is large, more memory data blocks can be stored, thereby facilitating the mobile terminal 4 to run various method functions.
S404, when the method function needs to be called, whether the memory data block corresponding to the method function in the memory is recycled is judged.
Specifically, when a certain method function needs to be called in the running process of the system or application of the mobile terminal 4, the mobile terminal 4 first determines whether a memory data block corresponding to the method function in the memory has been recovered by the server 2. If not, the memory data block in the memory can be directly used to run the method function.
It should be noted that, for the memory data block with the change number of 0, when the memory is recycled after the corresponding method function is completed, the memory data block is not really recycled, but a countdown flag is performed, and within a time range (for example, 30 minutes) of the countdown flag, the memory data block is not recycled until the time range is passed (after 30 minutes). Thus, within the timeframe of the countdown flag (within 30 minutes), if the method function is run again, there is no need to generate these repeated memory data blocks again.
S406, when it is recovered, searching the memory data block corresponding to the method function from the disk space of the mobile terminal 4.
Specifically, since all the method functions and the corresponding memory data blocks are obtained from the server 2 at a fixed time and stored in the disk space, the memory data blocks required for running the method functions can be searched from the disk space according to information such as method names, parameter value combinations, memory change times, and the like.
S408, writing the memory data block into a memory to run the method function.
Specifically, when the method function runs, if the memory data block is recovered, the memory data block with the change frequency of 0 corresponding to the method function is automatically written into the memory from the disk space, and the memory data block is prevented from being generated again, so that the running speed of the method function is increased.
For the memory data block with low change times, for example, when the parameter value of the method function a is 1, the memory data block with the change times of 2 is also automatically written into the memory in the running process. Along with the operation of the method function, which memory data block is needed can be quickly judged according to the parameter value and the change times of the method function, so that the memory data block can be directly used after being obtained from the disk space without completely generating all the memory data blocks of the method function again.
Example two
As shown in fig. 5, a second embodiment of the invention provides a memory calling method. In the second embodiment, steps S506 to S514 of the memory calling method are similar to steps S400 to S408 of the first embodiment, except that the method further includes steps S500 to S504.
The method comprises the following steps:
s500, monitoring various method functions running in the mobile terminal 4, and recording information of each method function.
Specifically, the information includes a method function name, a parameter value combination, a memory change number, and a specific memory data block. Various method functions are called during the operation of the system and the application of the mobile terminal 4. Each method function carries parameters, and each parameter has a specific value. During the operation of a method function, various memory data blocks are generated. Therefore, the memory change frequency in the operation process of the method function is recorded and analyzed by taking the method function and the specific parameter thereof as a unit, so that the memory data blocks respectively corresponding to each change frequency can be obtained, and the memory data blocks corresponding to all the method functions are distinguished. For example, there is a method function a, which carries a parameter B. The value combination for parameter B included 1 and 3 in all the running records. Assuming that no matter what value the parameter B is, the memory data block a and the memory data block B are generated in the operation process, and the memory data block a and the memory data block B are not changed each time, the memory data block a and the memory data block B are the memory data blocks with the change frequency of 0 following the method function a. Assuming that when the value of the parameter B is 1, the generated memory data blocks have c and d; when the value of the parameter B is 3, the generated memory data blocks have c and e. Then, for the method function a when the value of the parameter B is 1, the memory data blocks c and d with the change times of 1; and for the method function A with the parameter B of 3, the memory data blocks c and e with the change times of 1. And so on.
The mobile terminal 4 monitors various method functions called in the system and application running process, records parameter value combinations and memory change times in the running process, and records various corresponding memory data blocks under different method function names, parameter values and memory change times.
And S502, acquiring a memory change time threshold value set by the server 2.
Specifically, the server 2 may set a memory change time threshold, for example, 10 times, which indicates that all memory data blocks whose memory change times are less than or equal to the memory change time threshold need to be uploaded to the server 2 when the mobile terminal 4 monitors the operation of the method function. And the mobile terminal 4 acquires the memory change time threshold from the server 2.
S504, sending the memory data block whose memory change time is less than or equal to the memory change time threshold to the server 2 for statistics.
Specifically, according to the memory change time threshold received from the server 2, the mobile terminal 4 selects a memory data block with a memory change time less than or equal to the memory change time threshold (less than or equal to 10 times) from all the recorded memory data blocks, and sends the memory data block to the server 2.
And the server 2 collects the memory data blocks uploaded by all the mobile terminals 4 in communication connection with the server, and then performs merging and filtering again according to the threshold of the memory change times. The merging and filtering includes merging the corresponding memory data blocks under the condition that the function names, the parameter values and the memory change times uploaded by each mobile terminal 4 are the same, analyzing whether memory changes of each mobile terminal 4 aiming at the memory data blocks are repeated or not so as to merge the memory change times of the memory data blocks, and judging whether the merged memory change times are larger than the memory change time threshold or not so as to determine whether the memory data blocks should be stored or deleted. That is to say, when the memory change times after the memory data blocks are merged is less than or equal to the memory change time threshold, the server 2 stores the memory data blocks, the corresponding method function names, the parameter values and the merged memory change times; and when the memory change times after the memory data blocks are merged are larger than the memory change time threshold, the server 2 deletes the memory data blocks and the related records.
For example, the method function a uploaded by the first mobile terminal 4 has a memory data block a with a memory change frequency of 10 times, and the second mobile terminal 4 also uploads the memory data block a with a memory change frequency of 10 times, but the server 2 analyzes the memory change frequency corresponding to the memory data block a uploaded by the first mobile terminal 4 and the second mobile terminal 4, and finds that only 5 times of memory changes are repeated, so that the memory change frequency corresponding to the memory data block a after the two are combined becomes 15 times, which is greater than the threshold of the memory change frequency, and the memory data block a is deleted by the server 2.
S506, periodically obtaining the memory data blocks corresponding to all the method functions from the server 2.
Specifically, the acquired content includes a method function name, a parameter value combination, a memory change number (which refers to the merged memory change number), and a specific memory data block. The mobile terminal 4 acquires various memory data blocks corresponding to all the method functions counted by the server 2 from the server 2 at regular time. When the memory data block counted in the server 2 changes, the changed memory data block is updated to the mobile terminal 4 in time through a push notification mechanism, so as to ensure that the memory data block in the mobile terminal 4 is the latest. And the mobile terminal 4 receives the push notification sent by the server 2, acquires the changed memory data block, and updates the memory data block to the disk space.
S508, storing all the acquired memory data blocks to the disk space of the mobile terminal 4.
Specifically, after the memory data blocks corresponding to all the method functions are obtained from the server 2, the memory data blocks are stored in the disk space of the mobile terminal 4 for direct use when the method functions need to be run subsequently. Because the disk space of the mobile terminal 4 is large, more memory data blocks can be stored, thereby facilitating the mobile terminal 4 to run various method functions.
S510, when the method function needs to be called, whether the memory data block corresponding to the method function in the memory is recycled is judged.
Specifically, when a certain method function needs to be called in the running process of the system or application of the mobile terminal 4, the mobile terminal 4 first determines whether a memory data block corresponding to the method function in the memory has been recovered by the server 2. If not, the memory data block in the memory can be directly used to run the method function.
It should be noted that, for the memory data block with the change number of 0, when the memory is recycled after the corresponding method function is completed, the memory data block is not really recycled, but a countdown flag is performed, and within a time range (for example, 30 minutes) of the countdown flag, the memory data block is not recycled until the time range is passed (after 30 minutes). Thus, within the timeframe of the countdown flag (within 30 minutes), if the method function is run again, there is no need to generate these repeated memory data blocks again.
S512, when it has been recovered, searching the memory data block corresponding to the method function from the disk space of the mobile terminal 4.
Specifically, since all the method functions and the corresponding memory data blocks are obtained from the server 2 at a fixed time and stored in the disk space, the memory data blocks required for running the method functions can be searched from the disk space according to information such as method names, parameter value combinations, memory change times, and the like.
S514, writing the memory data block into a memory to run the method function.
Specifically, when the method function runs, if the memory data block is recovered, the memory data block with the change frequency of 0 corresponding to the method function is automatically written into the memory from the disk space, and the memory data block is prevented from being generated again, so that the running speed of the method function is increased.
For the memory data block with low change times, for example, when the parameter value of the method function a is 1, the memory data block with the change times of 2 is also automatically written into the memory in the running process. Along with the operation of the method function, which memory data block is needed can be quickly judged according to the parameter value and the change times of the method function, so that the memory data block can be directly used after being obtained from the disk space without completely generating all the memory data blocks of the method function again.
The invention further provides a mobile terminal which comprises a memory, a processor and a memory calling system. The memory calling system is used for realizing memory optimization according to the memory change frequency and reducing the action frequency of memory recovery and generation.
EXAMPLE III
As shown in fig. 6, a third embodiment of the present invention provides a mobile terminal 4. The mobile terminal 4 includes a memory 20, a processor 22, and a memory calling system 28.
The memory 20 includes at least one type of readable storage medium for storing an operating system and various types of application software installed in the mobile terminal 4, such as program codes of the memory calling system 28. In addition, the memory 20 may also be used to temporarily store various types of data that have been output or are to be output.
The processor 22 may be a Central Processing Unit (CPU), controller, microcontroller, microprocessor, or other data Processing chip in some embodiments. The processor 22 is typically operative to control overall operation of the mobile terminal 4. In this embodiment, the processor 22 is configured to run the program codes stored in the storage 20 or process data, for example, run the memory calling system 28.
Example four
Referring to fig. 7, a memory call system 28 according to a fourth embodiment of the present invention is provided. In this embodiment, the memory calling system 28 includes:
an obtaining module 800, configured to obtain the memory data blocks corresponding to all the method functions from the server 2 at regular time.
Specifically, the acquired content includes a method function name, a parameter value combination, memory change times, and a specific memory data block. Various method functions are called during the operation of the system and the application of the mobile terminal 4. Each method function carries parameters, and each parameter has a specific value. During the operation of a method function, various memory data blocks are generated. Therefore, the memory change frequency in the operation process of the method function is recorded and analyzed by taking the method function and the specific parameter thereof as a unit, so that the memory data blocks respectively corresponding to each change frequency can be obtained, and the memory data blocks corresponding to all the method functions are distinguished. For example, there is a method function a, which carries a parameter B. The value combination for parameter B included 1 and 3 in all the running records. Assuming that no matter what value the parameter B is, the memory data block a and the memory data block B are generated in the operation process, and the memory data block a and the memory data block B are not changed each time, the memory data block a and the memory data block B are the memory data blocks with the change frequency of 0 following the method function a. Assuming that when the value of the parameter B is 1, the generated memory data blocks have c and d; when the value of the parameter B is 3, the generated memory data blocks have c and e. Then, for the method function a when the value of the parameter B is 1, the memory data blocks c and d with the change times of 1; and for the method function A with the parameter B of 3, the memory data blocks c and e with the change times of 1. The obtaining module 800 obtains various memory data blocks corresponding to all the method functions counted by the server 2 from the server 2 at regular time.
When the memory data block counted in the server 2 changes, the changed memory data block is updated to the mobile terminal 4 in time through a push notification mechanism, so as to ensure that the memory data block in the mobile terminal 4 is the latest. And the mobile terminal 4 receives the push notification sent by the server 2, acquires the changed memory data block, and updates the memory data block to the disk space.
A saving module 802, configured to save all the acquired memory data blocks to the disk space of the mobile terminal 4.
Specifically, after obtaining the memory data blocks corresponding to all the method functions from the server 2, the storage module 802 stores the memory data blocks in the disk space of the mobile terminal 4 for direct use when the method functions need to be run subsequently. Because the disk space of the mobile terminal 4 is large, more memory data blocks can be stored, thereby facilitating the mobile terminal 4 to run various method functions.
The determining module 804 is configured to determine whether a memory data block corresponding to a method function in a memory is recycled when the method function needs to be called.
Specifically, when a certain method function needs to be called in the running process of the system or application of the mobile terminal 4, the determining module 804 first determines whether the memory data block corresponding to the method function in the memory is already recovered by the server 2. If not, the memory data block in the memory can be directly used to run the method function.
It should be noted that, for the memory data block with the change number of 0, when the memory is recycled after the corresponding method function is completed, the memory data block is not really recycled, but a countdown flag is performed, and within a time range (for example, 30 minutes) of the countdown flag, the memory data block is not recycled until the time range is passed (after 30 minutes). Thus, within the timeframe of the countdown flag (within 30 minutes), if the method function is run again, there is no need to generate these repeated memory data blocks again.
A searching module 806, configured to search, when the memory data block is recovered, the memory data block corresponding to the method function from the disk space of the mobile terminal 4.
Specifically, since all the method functions and the corresponding memory data blocks are obtained from the server 2 at a fixed time and stored in the disk space, the search module 806 may search the memory data blocks required for operating the method functions from the disk space according to information such as a method name, a parameter value combination, and the memory change times.
A writing module 808, configured to write the memory data block into a memory, so as to execute the method function.
Specifically, when the method function runs, if the memory data block is already recovered, the writing module 808 will automatically write the memory data block with the change frequency of 0 corresponding to the method function into the memory from the disk space, so as to avoid generating the memory data block again, and thus increase the running speed of the method function.
For the memory data block with low change times, for example, when the parameter value of the method function a is 1, the memory data block with the change times of 2 is also automatically written into the memory in the running process. Along with the operation of the method function, which memory data block is needed can be quickly judged according to the parameter value and the change times of the method function, so that the memory data block can be directly used after being obtained from the disk space without completely generating all the memory data blocks of the method function again.
EXAMPLE five
Referring to fig. 8, a fifth embodiment of the invention provides a memory call system 28. In this embodiment, the memory calling system 28 includes a recording module 810 and a sending module 812, in addition to the obtaining module 800, the saving module 802, the judging module 804, the searching module 806 and the writing module 808 in the fifth embodiment.
The recording module 810 is configured to monitor various method functions executed in the mobile terminal 4, and record information of each method function.
Specifically, the information includes a method function name, a parameter value combination, a memory change number, and a specific memory data block. The recording module 810 monitors various method functions called in the system and application running process of the mobile terminal 4, records parameter value combinations and memory change times in the running process, and records various corresponding memory data blocks under different method function names, parameter values and memory change times.
The obtaining module 800 is further configured to obtain a memory change time threshold set by the server 2.
Specifically, the server 2 may set a memory change time threshold, for example, 10 times, which indicates that all memory data blocks whose memory change times are less than or equal to the memory change time threshold need to be uploaded to the server 2 when the mobile terminal 4 monitors the operation of the method function. The obtaining module 800 obtains the memory change time threshold from the server 2.
The sending module 812 is configured to send the memory data block with the recorded memory change time being less than or equal to the memory change time threshold to the server 2 for statistics.
Specifically, according to the memory change time threshold received from the server 2, the sending module 812 selects a memory data block with a memory change time less than or equal to the memory change time threshold (less than or equal to 10 times) from all the recorded memory data blocks, and sends the memory data block to the server 2.
And the server 2 collects the memory data blocks uploaded by all the mobile terminals 4 in communication connection with the server, and then performs merging and filtering again according to the threshold of the memory change times. The merging and filtering includes merging the corresponding memory data blocks under the condition that the function names, the parameter values and the memory change times uploaded by each mobile terminal 4 are the same, analyzing whether memory changes of each mobile terminal 4 aiming at the memory data blocks are repeated or not so as to merge the memory change times of the memory data blocks, and judging whether the merged memory change times are larger than the memory change time threshold or not so as to determine whether the memory data blocks should be stored or deleted. That is to say, when the memory change times after the memory data blocks are merged is less than or equal to the memory change time threshold, the server 2 stores the memory data blocks, the corresponding method function names, the parameter values and the merged memory change times; and when the memory change times after the memory data blocks are merged are larger than the memory change time threshold, the server 2 deletes the memory data blocks and the related records.
For example, the method function a uploaded by the first mobile terminal 4 has a memory data block a with a memory change frequency of 10 times, and the second mobile terminal 4 also uploads the memory data block a with a memory change frequency of 10 times, but the server 2 analyzes the memory change frequency corresponding to the memory data block a uploaded by the first mobile terminal 4 and the second mobile terminal 4, and finds that only 5 times of memory changes are repeated, so that the memory change frequency corresponding to the memory data block a after the two are combined becomes 15 times, which is greater than the threshold of the memory change frequency, and the memory data block a is deleted by the server 2.
EXAMPLE six
The present invention also provides another embodiment, which is to provide a computer-readable storage medium storing a memory calling program, where the memory calling program is executable by at least one processor to cause the at least one processor to execute the steps of the memory calling method as described above.
It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
The above-mentioned serial numbers of the embodiments of the present invention are merely for description and do not represent the merits of the embodiments.
Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solutions of the present invention may be embodied in the form of a software product, which is stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal (such as a mobile phone, a computer, a server, an air conditioner, or a network device) to execute the method according to the embodiments of the present invention.
While the present invention has been described with reference to the embodiments shown in the drawings, the present invention is not limited to the embodiments, which are illustrative and not restrictive, and it will be apparent to those skilled in the art that various changes and modifications can be made therein without departing from the spirit and scope of the invention as defined in the appended claims.
Claims (8)
1. A memory calling method is applied to a mobile terminal, and is characterized by comprising the following steps:
monitoring various method functions operated in the mobile terminal, and recording information of each method function;
acquiring a memory change time threshold value set by a server;
sending the memory data block with the recorded memory change times smaller than or equal to the memory change time threshold value to the server for statistics;
the process of the server for counting the memory data blocks comprises the following steps:
collecting the memory data blocks uploaded by all mobile terminals in communication connection with the server;
combining corresponding memory data blocks under the condition that the name of the function, the parameter value combination and the memory change times of the method uploaded by each mobile terminal are the same;
analyzing whether memory change of each mobile terminal aiming at the memory data block is repeated or not so as to merge memory change times of the memory data block;
judging whether the combined memory change times is larger than the memory change time threshold value or not so as to determine whether the memory data block should be stored or deleted;
regularly acquiring memory data blocks corresponding to all the method functions from a server;
storing all the acquired memory data blocks to a disk space of the mobile terminal;
when a method function needs to be called, judging whether a memory data block corresponding to the method function in a memory is recycled;
when the memory data block is recovered, searching the memory data block corresponding to the method function from the disk space of the mobile terminal; and
and writing the memory data block into a memory to run the method function.
2. The memory calling method according to claim 1, wherein the information of each method function includes a method function name, a parameter value combination, a memory change number, and a specific memory data block; in the step of obtaining the memory data blocks corresponding to all the method functions from the server at regular time, the obtained content also includes the name of the method function, a combination of parameter values, the number of memory changes and a specific memory data block.
3. The memory calling method according to claim 1, wherein:
when the memory change times after the memory data blocks are merged are less than or equal to the memory change time threshold, the server stores the memory data blocks, corresponding method function names, parameter value combinations and the merged memory change times;
and when the memory change times after the memory data blocks are combined are larger than the memory change time threshold, the server deletes the memory data blocks and the related records.
4. The memory calling method according to claim 1, wherein for a memory data block whose change number is 0, when the memory is retrieved after the corresponding method function is completed, the memory data block is marked with a countdown, and within a time range of the countdown, the memory data block is not retrieved until the time range is passed before the memory data block is retrieved.
5. The memory calling method according to claim 2, wherein in the step of searching the memory data block corresponding to the method function from the disk space of the mobile terminal, the memory data block required for operating the method function is searched from the disk space according to the information of the method name, the parameter value combination, and the memory change times.
6. The memory calling method according to claim 1, further comprising the steps of:
and when the memory data block counted in the server changes, the mobile terminal receives a push notification sent by the server, acquires the changed memory data block, and updates the memory data block into the disk space.
7. A mobile terminal, characterized in that the mobile terminal comprises: memory, a processor, a screen and a memory calling program stored on the memory and executable on the processor, the memory calling program, when executed by the processor, implementing the steps of the memory calling method of any of claims 1 to 6.
8. A computer-readable storage medium, having stored thereon a memory caller, which when executed by a processor implements the steps of the memory call method of any one of claims 1 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201711446055.5A CN108196938B (en) | 2017-12-27 | 2017-12-27 | Memory calling method, mobile terminal and computer readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201711446055.5A CN108196938B (en) | 2017-12-27 | 2017-12-27 | Memory calling method, mobile terminal and computer readable storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN108196938A CN108196938A (en) | 2018-06-22 |
| CN108196938B true CN108196938B (en) | 2021-10-29 |
Family
ID=62584612
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201711446055.5A Active CN108196938B (en) | 2017-12-27 | 2017-12-27 | Memory calling method, mobile terminal and computer readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108196938B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112860444B (en) * | 2021-04-26 | 2021-08-20 | 腾讯科技（深圳）有限公司 | Memory calling information determining method and device, storage medium and electronic equipment |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1604051A (en) * | 2003-09-30 | 2005-04-06 | 三星电子株式会社 | Method and apparatus for dynamic memory management within an object-oriented program |
| CN1889737A (en) * | 2006-07-21 | 2007-01-03 | 华为技术有限公司 | Resource management method and system |
| CN101483050A (en) * | 2008-01-10 | 2009-07-15 | 信亿科技股份有限公司 | Memory magnetic disc and operation method thereof |
| CN106484580A (en) * | 2016-10-21 | 2017-03-08 | 腾讯科技（深圳）有限公司 | A kind of internal-memory detection method, apparatus and system |
| CN107277226A (en) * | 2017-05-11 | 2017-10-20 | 珠海金山网络游戏科技有限公司 | A kind of method and device for obtaining mobile phone application memory snapshot and Memory Allocation storehouse |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP1435576B1 (en) * | 2003-01-03 | 2013-03-20 | Austria Card Plastikkarten und Ausweissysteme GmbH | Method and apparatus for block-oriented memory management provided in smart card controllers |
| US20120203993A1 (en) * | 2011-02-08 | 2012-08-09 | SMART Storage Systems, Inc. | Memory system with tiered queuing and method of operation thereof |
| CN105224433B (en) * | 2014-06-23 | 2018-04-10 | 阿里巴巴集团控股有限公司 | A kind of internal memory monitoring method and server |
-
2017
- 2017-12-27 CN CN201711446055.5A patent/CN108196938B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1604051A (en) * | 2003-09-30 | 2005-04-06 | 三星电子株式会社 | Method and apparatus for dynamic memory management within an object-oriented program |
| CN1889737A (en) * | 2006-07-21 | 2007-01-03 | 华为技术有限公司 | Resource management method and system |
| CN101483050A (en) * | 2008-01-10 | 2009-07-15 | 信亿科技股份有限公司 | Memory magnetic disc and operation method thereof |
| CN106484580A (en) * | 2016-10-21 | 2017-03-08 | 腾讯科技（深圳）有限公司 | A kind of internal-memory detection method, apparatus and system |
| CN107277226A (en) * | 2017-05-11 | 2017-10-20 | 珠海金山网络游戏科技有限公司 | A kind of method and device for obtaining mobile phone application memory snapshot and Memory Allocation storehouse |
Non-Patent Citations (2)
| Title |
|---|
| Efficient garbage collection policy and block management method for NAND flash memory;Kee-Hoon Jang等;《2010 2nd International Conference on Mechanical and Electronics Engineering》;20100826;第327-331页 * |
| 面向Android系统的动态内存管理策略;姜仲秋 等;《测控技术》;20131231;第73-77页 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN108196938A (en) | 2018-06-22 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107967322B (en) | File classification display method, mobile terminal and computer readable storage medium | |
| CN107038245B (en) | Page switching method, mobile terminal and storage medium | |
| CN107562705B (en) | Data export method, server and computer readable storage medium | |
| CN107547741B (en) | Information processing method and device and computer readable storage medium | |
| CN107678698B (en) | Cache data cleaning method, server, terminal and computer readable storage medium | |
| CN108011937B (en) | Message pushing method, server, intelligent terminal and computer readable storage medium | |
| CN110180181B (en) | Method and device for capturing wonderful moment video and computer readable storage medium | |
| CN109766119B (en) | Recovery partition upgrade method, terminal and computer readable storage medium | |
| CN109584897B (en) | Video noise reduction method, mobile terminal and computer readable storage medium | |
| CN109151216B (en) | Application starting method, mobile terminal, server and computer readable storage medium | |
| CN108536383B (en) | Game control method, game control equipment and computer readable storage medium | |
| CN112597115A (en) | Container mirror image compression method and device, terminal equipment and medium | |
| CN110278481B (en) | Picture-in-picture implementation method, terminal and computer readable storage medium | |
| CN109445945B (en) | Memory allocation method of application program, mobile terminal, server and storage medium | |
| CN108833717B (en) | Information cleaning method and device, mobile terminal and computer readable storage medium | |
| CN108040116B (en) | Message pushing method, router and computer readable storage medium | |
| CN108377292B (en) | Method, terminal, server and computer storage medium for solving memory leakage | |
| CN107688497B (en) | Memory regulation and control method, equipment and computer readable storage medium | |
| CN111970738A (en) | Network switching control method, equipment and computer readable storage medium | |
| CN109062688B (en) | Memory allocation method, server and mobile terminal | |
| CN108183833B (en) | Response processing method and device and computer readable storage medium | |
| CN108196938B (en) | Memory calling method, mobile terminal and computer readable storage medium | |
| CN107766544B (en) | Information management method, terminal and computer readable storage medium | |
| CN107992564B (en) | Login verification processing method, mobile terminal and computer readable storage medium | |
| CN108304268B (en) | Memory optimization method, 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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |