CN111176849A - Application program management method, device and storage medium - Google Patents
Application program management method, device and storage medium Download PDFInfo
- Publication number
- CN111176849A CN111176849A CN201911424314.3A CN201911424314A CN111176849A CN 111176849 A CN111176849 A CN 111176849A CN 201911424314 A CN201911424314 A CN 201911424314A CN 111176849 A CN111176849 A CN 111176849A
- Authority
- CN
- China
- Prior art keywords
- application
- blacklist
- preset
- judging whether
- processing command
- 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.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
- G06F9/5005—Allocation of resources, e.g. of the central processing unit [CPU] to service a request
- G06F9/5027—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals
-
- 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/445—Program loading or initiating
- G06F9/44594—Unloading
Abstract
The invention discloses an application program management method. The method comprises the following steps: acquiring running state data of an application; judging whether the application needs to be placed in a blacklist or not according to the running state data; if the application needs to be placed in the blacklist, the application is locked, and the historical blacklist times of the application are acquired; judging whether the application needs to be unloaded according to the number of times of the historical blacklist; and if the application is determined to be required to be uninstalled, uninstalling the application. The invention also discloses an application program management device and a computer readable storage medium. The invention can realize the multi-stage processing of the application management and avoid the direct uninstallation of the application caused by temporary faults.
Description
Technical Field
The present invention relates to the field of application management, and in particular, to a method and an apparatus for managing an application program, and a computer-readable storage medium.
Background
At present, along with the popularization of smart televisions, more and more applications are installed on the televisions, so that users can perform more and more functions and have better and better watching experience.
But as tv-installed applications increase, management of applications becomes increasingly difficult. In the past, the management method of the installed application records the application with a large number of television blocking times due to excessive memory consumption, and prompts a user to unload the application so as to reduce the consumption of the television memory and the blocking times of the television. However, this management method is easy to make the use experience good, but some factors temporarily cause the running application of the system to be uninstalled, so that the user cannot use the application subsequently, which affects the use experience of the user.
Disclosure of Invention
The invention mainly aims to provide an application program management method, an application program management device and a computer readable storage medium, aiming at realizing multi-level processing on application management and avoiding direct uninstallation of the application due to temporary faults.
In order to achieve the above object, the present invention provides an application management method, including the steps of:
acquiring running state data of an application;
judging whether the application needs to be placed in a blacklist or not according to the running state data;
if the application needs to be placed in the blacklist, the application is locked, and the historical blacklist times of the application are acquired;
judging whether the application needs to be unloaded according to the number of times of the historical blacklist;
and if the application is determined to be required to be uninstalled, uninstalling the application.
Optionally, the operation state data includes a CPU occupancy rate, a memory usage rate, and an abnormal number, and the step of determining whether the application needs to be placed in the blacklist according to the operation state data includes:
judging whether the CPU occupancy rate is higher than a preset first threshold, the memory utilization rate is higher than a preset second threshold and/or the abnormal times are larger than a preset third threshold;
and if the CPU occupancy rate is higher than a preset first threshold value, the memory utilization rate is higher than a preset second threshold value and/or the abnormal times are larger than a preset third threshold value, judging that the application needs to be put into a blacklist.
Optionally, the step of determining whether to uninstall the application according to the number of times of the history blacklist includes:
comparing the historical blacklist times with a preset fourth threshold value, and judging whether the historical blacklist times is greater than the preset fourth threshold value;
and if the number of times of the historical blacklist is greater than a preset fourth threshold value, determining that the application needs to be uninstalled.
Optionally, the step of locking the application further comprises, before the step of:
displaying a locking prompt and receiving a processing command;
if the processing command is an agreement, locking the application;
and if the processing command is not agreed, recording the processing command and skipping the step of locking the application.
Optionally, before the step of uninstalling the application, the method further includes:
displaying an unloading prompt and receiving a processing command;
if the processing command is an agreement, uninstalling the application;
and if the processing command is not agreed, recording the processing command and skipping the step of unloading the application.
Optionally, the step of locking the application comprises:
acquiring source information of the application, and judging whether the application is a third-party source application or not according to the source information;
and if the application is not the third-party source application, sending application modification information to the application developer.
Optionally, the step of obtaining source information of the application and determining whether the application is a third-party source application according to the source information further includes:
if the application is the third-party source application, acquiring version information of the application, and judging whether the application is the latest version according to the version information;
if the version of the application is not the latest version, the application is upgraded to the latest version, and the lock of the application of the latest version is released.
Optionally, the step of sending the application modifying information to the application developer further includes:
acquiring an rectification state of an application, and judging whether the rectification of the application is finished according to the rectification state;
and if the application is completely reformed, unlocking the reformed application.
In order to achieve the above object, the present invention also provides an application management apparatus including: a memory, a processor and an application management program stored on the memory and executable on the processor, the application management program when executed by the processor implementing the steps of the application management method as described above.
In addition, to achieve the above object, the present invention also provides a computer readable storage medium having an application management program stored thereon, the application management program, when executed by a processor, implementing the steps of the application management method described above.
The invention provides an application program management method, an application program management device and a computer storage medium. In the method, operation state data of an application is acquired; judging whether the application needs to be placed in a blacklist or not according to the running state data; if the application needs to be placed in the blacklist, the application is locked, and the historical blacklist times of the application are acquired; judging whether the application needs to be unloaded according to the number of times of the historical blacklist; and if the application is determined to be required to be uninstalled, uninstalling the application. Through the mode, the application can be managed in multiple levels according to the running state data of the application, such as the memory utilization rate of the application, and the like, and is divided into multiple processing levels according to the application condition, the application is prevented from being directly unloaded due to a temporary problem by setting the blacklist, the application is firstly put into the blacklist, and the application is unloaded only when the application is put into the blacklist for too many times, so that the application is prevented from being directly unloaded due to a temporary problem, and the user experience is improved.
Drawings
FIG. 1 is a schematic diagram of an apparatus in a hardware operating environment according to an embodiment of the present invention;
FIG. 2 is a flowchart illustrating a first embodiment of a method for managing application programs according to the present invention;
FIG. 3 is a flowchart illustrating a second embodiment of an application management method according to the present invention;
FIG. 4 is a flowchart illustrating a third embodiment of a method for managing application programs according to the present invention;
FIG. 5 is a flowchart illustrating a fourth embodiment of a method for managing application programs according to the present invention;
FIG. 6 is a flowchart illustrating a fifth embodiment of an application management method according to the present invention;
FIG. 7 is a flowchart illustrating a sixth embodiment of a method for managing application programs according to the present invention;
FIG. 8 is a flowchart illustrating a seventh embodiment of an application management method according to 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.
As shown in fig. 1, fig. 1 is a schematic device structure diagram of a hardware operating environment according to an embodiment of the present invention.
The terminal of the embodiment of the invention can be a PC, and can also be a terminal device with a data processing function, such as a smart phone, a tablet computer, a portable computer and the like.
As shown in fig. 1, the terminal may include: a processor 1001, such as a CPU, a network interface 1004, a user interface 1003, a memory 1005, a communication bus 1002. Wherein a communication bus 1002 is used to enable connective communication between these components. The user interface 1003 may include a Display screen (Display), an input unit such as a Keyboard (Keyboard), and the optional user interface 1003 may also include a standard wired interface, a wireless interface. The network interface 1004 may optionally include a standard wired interface, a wireless interface (e.g., WI-FI interface). The memory 1005 may be a high-speed RAM memory or a non-volatile memory (e.g., a magnetic disk memory). The memory 1005 may alternatively be a storage device separate from the processor 1001.
Optionally, the terminal may further include a camera, a Radio Frequency (RF) circuit, a sensor, an audio circuit, a Wi-Fi module, and the like. Such as light sensors, motion sensors, and other sensors. Specifically, the light sensor may include an ambient light sensor that may adjust the brightness of the display screen according to the brightness of ambient light, and a proximity sensor that may turn off the display screen and/or the backlight when the mobile terminal is moved to the ear. As one of the motion sensors, the gravity acceleration sensor can detect the magnitude of acceleration in each direction (generally, three axes), detect the magnitude and direction of gravity when the mobile terminal is stationary, and can be used for applications (such as horizontal and vertical screen switching, related games, magnetometer attitude calibration), vibration recognition related functions (such as pedometer and tapping) and the like for recognizing the attitude of the mobile terminal; of course, the mobile terminal may also be configured with other sensors such as a gyroscope, a barometer, a hygrometer, a thermometer, and an infrared sensor, which are not described herein again.
Those skilled in the art will appreciate that the terminal structure shown in fig. 1 is not intended to be limiting and may include more or fewer components than those shown, or some components may be combined, or a different arrangement of components.
As shown in fig. 1, a memory 1005, which is a kind of computer storage medium, may include therein an operating system, a network communication module, a user interface module, and an application management program.
In the terminal shown in fig. 1, the network interface 1004 is mainly used for connecting to a backend server and performing data communication with the backend server; the user interface 1003 is mainly used for connecting a client (user side) and performing data communication with the client; and the processor 1001 may be configured to invoke an application manager stored in the memory 1005 and perform the following operations:
acquiring running state data of an application;
judging whether the application needs to be placed in a blacklist or not according to the running state data;
if the application needs to be placed in the blacklist, the application is locked, and the historical blacklist times of the application are acquired;
judging whether the application needs to be unloaded according to the number of times of the historical blacklist;
and if the application is determined to be required to be uninstalled, uninstalling the application.
Further, the processor 1001 may call an application manager stored in the memory 1005, and also perform the following operations:
the operation state data comprises CPU occupancy rate, memory utilization rate and abnormal times, and the step of judging whether the application needs to be placed in a blacklist or not according to the operation state data comprises the following steps:
judging whether the CPU occupancy rate is higher than a preset first threshold, the memory utilization rate is higher than a preset second threshold and/or the abnormal times are larger than a preset third threshold;
and if the CPU occupancy rate is higher than a preset first threshold value, the memory utilization rate is higher than a preset second threshold value and/or the abnormal times are larger than a preset third threshold value, judging that the application needs to be put into a blacklist.
Further, the processor 1001 may call an application manager stored in the memory 1005, and also perform the following operations:
the step of judging whether the application needs to be unloaded according to the number of times of the historical blacklist comprises the following steps:
comparing the historical blacklist times with a preset fourth threshold value, and judging whether the historical blacklist times is greater than the preset fourth threshold value;
and if the number of times of the historical blacklist is greater than a preset fourth threshold value, determining that the application needs to be uninstalled.
Further, the processor 1001 may call an application manager stored in the memory 1005, and also perform the following operations:
the step of locking the application further comprises, before the step of:
displaying a locking prompt and receiving a processing command;
if the processing command is an agreement, locking the application;
and if the processing command is not agreed, recording the processing command and skipping the step of locking the application.
Further, the processor 1001 may call an application manager stored in the memory 1005, and also perform the following operations:
before the step of uninstalling the application, the method further comprises:
displaying an unloading prompt and receiving a processing command;
if the processing command is an agreement, uninstalling the application;
and if the processing command is not agreed, recording the processing command and skipping the step of unloading the application.
Further, the processor 1001 may call an application manager stored in the memory 1005, and also perform the following operations:
the step of locking the application then comprises:
acquiring source information of the application, and judging whether the application is a third-party source application or not according to the source information;
and if the application is not the third-party source application, sending application modification information to the application developer.
Further, the processor 1001 may call an application manager stored in the memory 1005, and also perform the following operations:
the step of obtaining the source information of the application and judging whether the application is a third party source application according to the source information further comprises:
if the application is the third-party source application, acquiring version information of the application, and judging whether the application is the latest version according to the version information;
if the version of the application is not the latest version, the application is upgraded to the latest version, and the lock of the application of the latest version is released.
Further, the processor 1001 may call an application manager stored in the memory 1005, and also perform the following operations:
the step of sending the application modification information to the application developer further comprises:
acquiring an rectification state of an application, and judging whether the rectification of the application is finished according to the rectification state;
and if the application is completely reformed, unlocking the reformed application.
The specific embodiment of the application management device of the present invention is substantially the same as the following embodiments of the application management method, and will not be described herein again.
Referring to fig. 2, fig. 2 is a flowchart illustrating a first embodiment of an application management method according to the present invention, where the application management method includes:
step S100, acquiring running state data of an application;
in this embodiment, the running state data of the application is obtained, specifically, the running state data may be CPU occupancy, memory usage, and abnormal times, and may also be other data. Further, the CPU occupancy rate and the memory usage rate may be obtained through a local layer (Native layer) of the system, and the CPU occupancy rate and the memory usage rate of all applications of the system are obtained through monitoring and obtaining by a BIN program in the local layer. The abnormal times can be obtained through an application layer of the system, abnormal points are buried in the Framework, various abnormal data of the Framework are notified to the application layer in a broadcasting mode, and the application layer collects and counts the abnormal data to obtain the abnormal times.
Step S200, judging whether the application needs to be placed in a blacklist or not according to the running state data;
and after the running state data are obtained, analyzing the running state data, and judging whether the application needs to be placed in a blacklist or not according to an analysis result. Specifically, the running state data number may be compared with a preset threshold, and whether the application needs to be placed in the blacklist is determined according to a comparison result. The blacklist refers to an application abnormal list, and if the application is placed in the blacklist, corresponding measures are taken for the application, such as limiting application operation and the like. In this embodiment, the step of analyzing the running state data number and determining whether the application needs to be placed in the blacklist according to the analysis result may be performed at the cloud of the system. The method comprises the steps that after a Native layer obtains the CPU occupancy rate and the memory utilization rate, the CPU occupancy rate and the memory utilization rate are sent to a cloud, meanwhile, after the application layer obtains the abnormal times, the abnormal times are sent to the cloud, after the cloud obtains running state data such as the CPU occupancy rate, the memory utilization rate and the abnormal times, the cloud analyzes the running state data, and judges whether the application needs to be placed into a blacklist or not according to an analysis result.
If it is determined that the application needs to be placed in the blacklist, step S300 is executed: locking the application and acquiring the historical blacklist times of the application;
and if the application needs to be put into the blacklist, locking the application and acquiring the historical blacklist times of the application. Specifically, the application may be locked to restrict the application from running, or temporarily disable the application by a temporary restriction measure such as restricting user login. And after locking, acquiring the history blacklist times of the application from the history data of the blacklist. In this embodiment, if the cloud determines that the application needs to be placed in the blacklist, the cloud feeds back the determination result to the local layer (Native layer), and the BIN program of the local layer (Native layer) locks the application.
Step S400, judging whether the application needs to be uninstalled according to the number of times of the history blacklist;
after the number of times of the historical blacklist is obtained, judging whether the application needs to be uninstalled according to the number of times of the historical blacklist, specifically, comparing the number of times of the historical blacklist with a preset number threshold, judging whether the number of times of the historical blacklist is greater than the preset number threshold, if the number of times of the historical blacklist is greater than the preset number threshold, judging that the application needs to be uninstalled, and if the number of times of the historical blacklist is less than or equal to the preset number threshold, judging that the application does not need to be uninstalled.
If it is determined that the application needs to be uninstalled, step S500 is executed: the application is unloaded.
And if the application is judged to be required to be unloaded, unloading the application according to the judgment result.
The invention provides an application program management method, an application program management device and a computer storage medium. In the method, operation state data of an application is acquired; judging whether the application needs to be placed in a blacklist or not according to the running state data; if the application needs to be placed in the blacklist, the application is locked, and the historical blacklist times of the application are acquired; judging whether the application needs to be unloaded according to the number of times of the historical blacklist; and if the application is determined to be required to be uninstalled, uninstalling the application. Through the mode, the application can be managed in multiple levels according to the running state data of the application, such as the memory utilization rate of the application, and the like, and is divided into multiple processing levels according to the application condition, the application is prevented from being directly unloaded due to a temporary problem by setting the blacklist, the application is firstly put into the blacklist, and the application is unloaded only when the application is put into the blacklist for too many times, so that the application is prevented from being directly unloaded due to a temporary problem, and the user experience is improved.
Referring to fig. 3, fig. 3 is a flowchart illustrating an application management method according to a second embodiment of the present invention.
Based on the foregoing embodiment, in this embodiment, step S200 includes:
step S210, judging whether the CPU occupancy rate is higher than a preset first threshold value, whether the memory utilization rate is higher than a preset second threshold value and/or whether the abnormal times are larger than a preset third threshold value;
in this embodiment, the operation status data includes at least one of CPU occupancy, memory usage, and abnormal times, or a combination of two or more of them. And comparing the CPU occupancy rate, the memory utilization rate and the abnormal times with preset thresholds, and judging whether the CPU occupancy rate is higher than a preset first threshold, whether the memory utilization rate is higher than a preset second threshold and/or whether the abnormal times is larger than a preset third threshold.
If the CPU occupancy is higher than a preset first threshold, the memory usage rate is higher than a preset second threshold, and/or the abnormal number is greater than a preset third threshold, then step S220 is executed: determining that the application needs to be placed in a blacklist;
if the CPU occupancy rate is higher than a preset first threshold value, the fact that the application occupies a large amount of system CPU and has a large influence on system operation is indicated, and the fact that the application needs to be placed in a blacklist is judged.
If the memory utilization rate is higher than a preset second threshold, it indicates that the application occupies a larger system memory, and has a larger influence on system operation, and it is determined that the application needs to be placed in a blacklist.
If the abnormal times are larger than a preset third threshold, the abnormal operation of the application is serious, the influence on the operation of the system is large, and the application needs to be put into a blacklist.
If the application occupies a large amount of system memory and has a large influence on system operation, it is determined that the application needs to be placed in the blacklist.
Further, if the CPU occupancy rate is lower than or equal to a preset first threshold, the memory usage rate is lower than or equal to a preset second threshold, and the number of abnormal times is lower than or equal to a preset third threshold, it may be determined that the application does not need to be placed in a blacklist.
If the CPU occupancy rate is lower than or equal to a preset first threshold, the memory usage rate is lower than or equal to a preset second threshold and/or the abnormal times are smaller than or equal to a preset third threshold, it indicates that the application runs well, and no abnormal condition occurs, and it is determined that the application does not need to be placed in a blacklist.
It should be noted that in the specific implementation, the determination may be performed according to any one or more of the above determination conditions, and as long as the determination result satisfies one or more of the above conditions, it is determined that the application has a large influence on the system operation, and at this time, it is determined that the application is placed in a blacklist.
Referring to fig. 4, fig. 4 is a flowchart illustrating a third embodiment of an application management method according to the present invention.
Based on the foregoing embodiment, in this embodiment, step S400 includes:
step S410, comparing the historical blacklist times with a preset fourth threshold value, and judging whether the historical blacklist times is greater than the preset fourth threshold value;
in this embodiment, whether the application needs to be uninstalled is determined according to the number of times of the historical blacklist, and first, the number of times of the historical blacklist is compared with a preset fourth threshold, and whether the number of times of the historical blacklist is greater than the preset fourth threshold is determined.
If the number of times of the history blacklist is greater than a preset fourth threshold, executing step S420: determining that an application needs to be uninstalled;
and if the historical blacklist times is larger than a preset fourth threshold, the application is indicated to be placed in the blacklist more times, and the application is determined to be unloaded.
Further, if the number of times of the history blacklist is less than or equal to a preset fourth threshold, it may be determined that the application does not need to be uninstalled.
If the number of times of the historical blacklist is less than or equal to a preset fourth threshold, the application is not placed in the blacklist for many times, and therefore the application does not need to be uninstalled. The preset fourth threshold value can be set in an adjustable manner according to the system and the application condition.
Referring to fig. 5, fig. 5 is a flowchart illustrating a fourth embodiment of an application management method according to the present invention.
Based on the foregoing embodiment, in this embodiment, before step S300, the method further includes:
step S600, displaying a locking prompt and receiving a processing command;
in this embodiment, before the application is locked, a lock prompt is sent to the user, and a processing command returned by the user according to the lock prompt is received, where the returned processing command may be an agreement or a disagreement.
If the processing command is approved, step S610 is executed: locking the application;
and if the processing command of the user is agreement, which indicates that the user agrees to lock the application, executing operation to lock the application.
If the processing command is not approved, step S620 is executed: recording the process command and skipping the step of locking the application.
And if the processing command of the user is not agreed, the user does not agree to lock the application, the execution operation records the processing command, and the step of locking the application is skipped.
Referring to fig. 6, fig. 6 is a flowchart illustrating an application management method according to a fifth embodiment of the present invention.
Based on the foregoing embodiment, in this embodiment, before step S500, the method further includes:
step S700, displaying an unloading prompt and receiving a processing command;
in this embodiment, before the application is uninstalled, an uninstall prompt may be sent to the user, and a processing command returned by the user according to the uninstall prompt may be accepted, where the returned processing command may be an agreement or a disagreement.
If the processing command is approved, step S710 is executed: uninstalling the application;
and if the processing command of the user is agreement, which indicates that the user agrees to uninstall the application, executing operation to uninstall the application.
If the processing command is not approved, step S720 is executed: recording the processing command and skipping the step of uninstalling the application.
And if the processing command of the user is not agreed, the user does not agree to unload the application, the execution operation records the processing command, and the step of unloading the application is skipped.
Referring to fig. 7, fig. 7 is a flowchart illustrating a sixth embodiment of an application management method according to the present invention.
Based on the foregoing embodiment, in this embodiment, after step S300, the method further includes:
step S800, acquiring source information of the application, and judging whether the application is a third-party source application according to the source information;
in this embodiment, after the application is locked, source information of the application may also be obtained, and whether the application is a third-party source application is determined according to the source information, that is, whether the application is an application program of the system itself is determined.
If the application is not the third party source application, step S810 is executed: and sending the application rectification information to an application developer.
And if the application is judged not to be the third-party source application, namely the application is the application carried by the system, sending the application rectification information to an application developer so that the application developer rectifies according to the application rectification information.
Further, the method comprises the following steps of;
if the application is a third party source application, step S820 is executed: acquiring version information of an application, and judging whether the application is the latest version or not according to the version information;
if the application is judged to be the third-party source application, acquiring version information of the application, and judging whether the application is the latest version according to the version information; and comparing the version information of the application with the latest version information to judge whether the application is the latest version.
If not, execute step S830: upgrading the application to the latest version and unlocking the application of the latest version.
And if the version information of the application is not the latest version, upgrading the application to the latest version and unlocking the application of the latest version.
Referring to fig. 8, fig. 8 is a flowchart illustrating an application management method according to a seventh embodiment of the present invention.
Based on the foregoing embodiment, in this embodiment, after step S810, the method further includes:
step 840, obtaining the modification state of the application, and judging whether the application is modified according to the modification state;
in this embodiment, when it is determined that the application is not the third-party source application, the application modifying information is sent to the application developer, so that the application developer can obtain the modifying state of the application after modifying according to the application modifying information, and determine whether the application is modified according to the modifying state.
If the application is finished, step S850 is executed: and unlocking the application after the rectification is finished.
And if the application is completely reformed, unlocking the reformed application.
Specifically, the specific process of this embodiment may be as follows: in this embodiment, the system is divided into a Native layer, an application layer and a cloud, the Native layer implements a BIN program similar to a system watchdog, and is responsible for monitoring the occupancy rate and memory usage of all application CPUs installed in the system, and reporting data to the cloud via an HTTP network request. Meanwhile, the method can perform exception point burying on the Framework, inform the application layer of various exceptions thrown by the Framework in a broadcasting mode, process exception data by the application layer APK, count the occurrence frequency of the exceptions and report the data to the cloud.
The method comprises the steps that data are taken by a cloud, data analysis is carried out, results are fed back to an application layer APK, for the application with high CPU occupancy rate and serious memory consumption or frequent collapse, the APK prompts a user that the application causes system blockage or abnormal collapse, whether the application is placed in a small black room or not and informs the user of a punishment result of the application, after the user agrees, the application layer APK informs a Native layer BIN program to kill an application process and locks the application process, meanwhile, a processing result is synchronized to the cloud, if the application is the application of the cloud, the cloud sends a reforming mail to an application developer, after a developer repairs a bug, the application is released from the small black room to the cloud, and after the cloud approves, the developer informs a Native layer to release monitoring of the application process; if the application is a three-party application, the user is prompted by how many days the application stays in a small dark room, whether to try to download a new version in the application market is determined, and whether the third party is repaired is seen. If the application is closed for a plurality of times, prompting the user whether to uninstall the application.
According to the method, different severe levels are divided aiming at application abnormity, when the application crashes, the process is timely killed, the influence on the system performance is avoided all the time, meanwhile, through a small black house management mode, the situation that a user can only think of unloading the application once encountering the application crash is avoided, and the opportunity of modifying the application is provided.
In addition, the embodiment of the invention also provides a computer readable storage medium.
The computer readable storage medium of the present invention has stored thereon an application management program, which when executed by a processor implements the steps of the application management method as described above.
The method implemented when the application management program running on the processor is executed may refer to various embodiments of the application management method of the present invention, and details are not described herein.
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 system 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 system. 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 system 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 solution of the present invention may be embodied in the form of a software product, which is stored in a storage medium (e.g., ROM/RAM, magnetic disk, optical disk) as described above and includes instructions for enabling a terminal device (e.g., 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.
The above description is only a preferred embodiment of the present invention, and not intended to limit the scope of the present invention, and all modifications of equivalent structures and equivalent processes, which are made by using the contents of the present specification and the accompanying drawings, or directly or indirectly applied to other related technical fields, are included in the scope of the present invention.
Claims (10)
1. An application management method, characterized by comprising the steps of:
acquiring running state data of an application;
judging whether the application needs to be placed in a blacklist or not according to the running state data;
if the application needs to be placed in the blacklist, the application is locked, and the historical blacklist times of the application are acquired;
judging whether the application needs to be unloaded according to the number of times of the historical blacklist;
and if the application is determined to be required to be uninstalled, uninstalling the application.
2. The method for managing application programs according to claim 1, wherein the operation status data includes CPU occupancy, memory usage, and abnormal times, and the step of determining whether the application needs to be placed in the blacklist according to the operation status data includes:
judging whether the CPU occupancy rate is higher than a preset first threshold, the memory utilization rate is higher than a preset second threshold and/or the abnormal times are larger than a preset third threshold;
and if the CPU occupancy rate is higher than a preset first threshold value, the memory utilization rate is higher than a preset second threshold value and/or the abnormal times are larger than a preset third threshold value, judging that the application needs to be put into a blacklist.
3. The method for application management as claimed in claim 1, wherein the step of determining whether the application needs to be uninstalled according to the number of times of the history blacklist comprises:
comparing the historical blacklist times with a preset fourth threshold value, and judging whether the historical blacklist times is greater than the preset fourth threshold value;
and if the number of times of the historical blacklist is greater than a preset fourth threshold value, determining that the application needs to be uninstalled.
4. The application management method of claim 1, wherein the step of locking the application is preceded by the step of:
displaying a locking prompt and receiving a processing command;
if the processing command is an agreement, locking the application;
and if the processing command is not agreed, recording the processing command and skipping the step of locking the application.
5. The application management method of claim 1, wherein the step of uninstalling the application is preceded by the step of:
displaying an unloading prompt and receiving a processing command;
if the processing command is an agreement, uninstalling the application;
and if the processing command is not agreed, recording the processing command and skipping the step of unloading the application.
6. The application management method of claim 1 wherein the step of locking the application is followed by:
acquiring source information of the application, and judging whether the application is a third-party source application or not according to the source information;
and if the application is not the third-party source application, sending application modification information to the application developer.
7. The method for managing application programs according to claim 6, wherein the step of obtaining the source information of the application and determining whether the application is a third party source application according to the source information further comprises:
if the application is the third-party source application, acquiring version information of the application, and judging whether the application is the latest version according to the version information;
if the version of the application is not the latest version, the application is upgraded to the latest version, and the lock of the application of the latest version is released.
8. The application management method of claim 6 wherein the step of sending the application revision information to the application developer is followed by further comprising:
acquiring an rectification state of an application, and judging whether the rectification of the application is finished according to the rectification state;
and if the application is completely reformed, unlocking the reformed application.
9. An application management apparatus, characterized in that the application management apparatus comprises: memory, a processor and an application management program stored on the memory and executable on the processor, the application management program when executed by the processor implementing the steps of the application management method according to any of claims 1 to 8.
10. A computer-readable storage medium, having an application management program stored thereon, which when executed by a processor implements the steps of the application management method according to any one of claims 1 to 8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911424314.3A CN111176849A (en) | 2019-12-30 | 2019-12-30 | Application program management method, device and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911424314.3A CN111176849A (en) | 2019-12-30 | 2019-12-30 | Application program management method, device and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111176849A true CN111176849A (en) | 2020-05-19 |
Family
ID=70649143
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911424314.3A Pending CN111176849A (en) | 2019-12-30 | 2019-12-30 | Application program management method, device and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111176849A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112328935A (en) * | 2020-10-29 | 2021-02-05 | 胡培培 | Application program pushing system and method based on big data |
| CN115544502A (en) * | 2022-03-07 | 2022-12-30 | 荣耀终端有限公司 | Terminal software control method, electronic equipment and storage medium |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20160162275A1 (en) * | 2014-12-03 | 2016-06-09 | Verizon Patent And Licensing Inc. | Identification and isolation of incompatible applications during a platform update |
| CN107423097A (en) * | 2017-07-28 | 2017-12-01 | 北京明朝万达科技股份有限公司 | The management method and device of a kind of application program |
| CN107526638A (en) * | 2017-08-01 | 2017-12-29 | 广东欧珀移动通信有限公司 | Applied program processing method, device, mobile terminal and storage medium |
| CN108090359A (en) * | 2018-01-05 | 2018-05-29 | 广东小天才科技有限公司 | A kind of application program monitoring method and application server |
| CN109739598A (en) * | 2018-12-24 | 2019-05-10 | Oppo广东移动通信有限公司 | A kind of bright screen method and device of terminal, equipment and storage medium |
-
2019
- 2019-12-30 CN CN201911424314.3A patent/CN111176849A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20160162275A1 (en) * | 2014-12-03 | 2016-06-09 | Verizon Patent And Licensing Inc. | Identification and isolation of incompatible applications during a platform update |
| CN107423097A (en) * | 2017-07-28 | 2017-12-01 | 北京明朝万达科技股份有限公司 | The management method and device of a kind of application program |
| CN107526638A (en) * | 2017-08-01 | 2017-12-29 | 广东欧珀移动通信有限公司 | Applied program processing method, device, mobile terminal and storage medium |
| CN108090359A (en) * | 2018-01-05 | 2018-05-29 | 广东小天才科技有限公司 | A kind of application program monitoring method and application server |
| CN109739598A (en) * | 2018-12-24 | 2019-05-10 | Oppo广东移动通信有限公司 | A kind of bright screen method and device of terminal, equipment and storage medium |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112328935A (en) * | 2020-10-29 | 2021-02-05 | 胡培培 | Application program pushing system and method based on big data |
| CN112328935B (en) * | 2020-10-29 | 2021-11-12 | 朱理薇 | Application program pushing system and method based on big data |
| CN115544502A (en) * | 2022-03-07 | 2022-12-30 | 荣耀终端有限公司 | Terminal software control method, electronic equipment and storage medium |
| CN115544502B (en) * | 2022-03-07 | 2024-04-23 | 荣耀终端有限公司 | Terminal software management and control method, electronic equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9679130B2 (en) | Pervasive package identifiers | |
| CN107766747B (en) | Method for verifying integrity of application program installation package, mobile terminal and server | |
| US20130333039A1 (en) | Evaluating Whether to Block or Allow Installation of a Software Application | |
| KR20150048136A (en) | Secure firmware updates | |
| US20130067563A1 (en) | Apparatus and method for managing permission information of application | |
| US20140283044A1 (en) | Method and Device For Preventing Application in an Operating System From Being Uninstalled | |
| CN111176849A (en) | Application program management method, device and storage medium | |
| CN111191226A (en) | Method, device, equipment and storage medium for determining program by using privilege-offering vulnerability | |
| US10516699B2 (en) | Electronic device and method for suggesting response manual in occurrence of denial | |
| CN110502263B (en) | Upgrade package manufacturing method, system and computer readable storage medium | |
| CN108021630B (en) | Junk file cleaning method, intelligent terminal and computer readable storage medium | |
| CN111200744B (en) | Multimedia playing control method and device and intelligent equipment | |
| CN107908956B (en) | Resource access request monitoring method and device and readable storage medium | |
| CN106569851B (en) | Application program processing method and device | |
| CN111581005A (en) | Terminal repairing method, terminal and storage medium | |
| EP3239880B1 (en) | Legal installation package acquiring method and apparatus, computer program and recording medium | |
| CN110659082A (en) | Application program interface display method and device, terminal and storage medium | |
| EP3671463A1 (en) | Server, electronic device, and control method thereof | |
| CN113747244B (en) | Multimedia data protection method, terminal equipment and server | |
| CN111552537B (en) | Theme switching method and device, computer equipment and storage medium | |
| CN110944320B (en) | Smart card identification method, smart card identification system and computer-readable storage medium | |
| CN114880003A (en) | System upgrading method of intelligent terminal, intelligent terminal and storage medium | |
| US20170277528A1 (en) | Application installation system and method for handheld devices | |
| CN109815429B (en) | Browser page closing processing method and device | |
| CN109032651B (en) | Application updating method, intelligent 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 |