CN107844342B - Application program keep alive management and control method, device and storage medium and mobile terminal - Google Patents

Abstract

The embodiment of the application discloses a control method and a control device for keeping application program alive, a storage medium and a mobile terminal, wherein the method comprises the following steps: acquiring application information of an application program requesting to set foreground service; judging whether the application program can set foreground service or not based on the application information according to a preset foreground service setting strategy; and if not, forbidding the application program to set foreground service so as to forbid the application program to keep alive through setting the foreground service. According to the technical scheme, the keep-alive operation of the management and control application program can be reasonable, the rogue application program is prevented from being kept alive through setting of the foreground service, running resources and electric quantity of the mobile terminal are wasted, and the running smoothness of the mobile terminal is improved.

Description

Application program keep alive management and control method, device and storage medium and mobile terminal

technical field

The embodiments of the present application relate to the technical field of application management and control, and in particular, to a management and control method, device, storage medium, and mobile terminal for keeping an application program alive.

Background technique

There are more and more types and functions of applications in mobile terminals such as mobile phones, which provide convenience for people's life and work. People can use mobile phones to make calls, listen to music, watch videos, and play games. However, some rogue applications use some keep-alive methods to self-start or keep running in order to keep themselves running all the time. In the related art, there are defects in the management and control method for application program keep-alive, which needs to be improved.

SUMMARY OF THE INVENTION

The embodiments of the present application provide a method, device, storage medium, and mobile terminal for managing and controlling application program keep-alive, which can reasonably manage and control the keep-alive of application programs.

In a first aspect, an embodiment of the present application provides a management and control method for application keep-alive, including:

Get the application information of the application requesting to set the foreground service;

According to the preset foreground service setting policy, based on the application information, determine whether the application can set the foreground service;

If not, the application program is prohibited from setting the foreground service, so as to prohibit the application program from keeping alive by setting the foreground service.

In a second aspect, an embodiment of the present application provides a management and control device for keeping an application program alive, including:

The application information acquisition module is used to acquire the application information of the application requesting to set the foreground service;

a foreground service setting judging module, configured to judge whether the application can set a foreground service based on the application information according to a preset foreground service setting policy;

The foreground service setting prohibition module is configured to prohibit the application from setting the foreground service if the application cannot set the foreground service, so as to prohibit the application from starting by setting the foreground service.

In a third aspect, an embodiment of the present application provides a computer-readable storage medium on which a computer program is stored, and when the program is executed by a processor, implements the management and control method for keeping an application program alive as provided in the first aspect.

In a fourth aspect, an embodiment of the present application provides a mobile terminal, including a memory, a processor, and a computer program stored in the memory and running on the processor, and the processor implements the implementation as provided in the first aspect when executed The application keep-alive control method.

This embodiment of the present application obtains the application information of the application that requests to set the foreground service, and judges whether the application can set the foreground service based on the application information according to the preset foreground service setting policy. The application sets the foreground service to prevent the application from being kept alive by setting the foreground service, so that the keep alive operation of the application can be reasonably controlled, so as to avoid wasting the running resources and the operating resources of the mobile terminal due to some rogue applications keeping themselves alive. The power consumption also improves the smoothness of the operation of the mobile terminal.

Description of drawings

FIG. 1 is a flowchart of a management and control method for application program keep alive provided by an embodiment of the present application;

FIG. 2 is a flowchart of another application program keep-alive management and control method provided by an embodiment of the present application;

FIG. 3 is a flowchart of another application program keep-alive management and control method provided by an embodiment of the present application;

FIG. 4 is a schematic structural diagram of a management and control device for keeping an application program alive according to an embodiment of the present application;

FIG. 5 is a schematic structural diagram of a mobile terminal provided by an embodiment of the present application;

FIG. 6 is a schematic structural diagram of another mobile terminal provided by an embodiment of the present application.

Detailed ways

In order to make the objectives, technical solutions and advantages of the present application clearer, the specific embodiments of the present application will be further described in detail below with reference to the accompanying drawings. It should be understood that the specific embodiments described herein are only used to explain the present application, but not to limit the present application. In addition, it should be noted that, for the convenience of description, the drawings only show some but not all of the contents related to the present application. Before discussing the exemplary embodiments in greater detail, it should be mentioned that some exemplary embodiments are described as processes or methods depicted as flowcharts. Although a flowchart depicts various operations (or steps) as a sequential process, many of the operations may be performed in parallel, concurrently, or concurrently. Additionally, the order of operations can be rearranged. The process may be terminated when its operation is complete, but may also have additional steps not included in the figures. The processes may correspond to methods, functions, procedures, subroutines, subroutines, and the like.

FIG. 1 shows a flowchart of an application program keep alive management and control method provided by an embodiment of the present application. The method in this embodiment may be executed by an application program keep alive management and control device, and the device may be implemented by hardware and/or software. The device can be implemented in the mobile terminal as a part of the mobile terminal. The mobile terminals described in the implementation of this application include devices such as mobile phones, tablet computers, or notebooks.

As shown in FIG. 1 , the method for managing and controlling application program keeping alive provided by this embodiment includes the following steps:

Step 101: Obtain application information of an application requesting to set a foreground service.

Service is a non-visual background running logic used to provide background running services for applications, which can be called services, such as background music playback services. The service is almost always running in the background, and it has been doing the hard work silently all the time. However, the system priority of the service is still relatively low. When the system runs out of memory, the service running in the background may be recycled. If you want the service to keep running all the time without being recycled due to insufficient system memory, you can consider using the foreground service, then the system will consider the service visible to the user and will not kill it when the memory is insufficient. The biggest difference between the service or the application foreground service corresponding to the service and the ordinary service is that it will always have a running icon displayed in the status bar of the system. After pulling down the status bar, you can see more detailed information, very similar effect of notification. This method of setting the foreground service to keep the application alive will also be used by some rogue applications. After setting a service of the application as the foreground service by setting the notification, it will actively clear the notification, so that the user cannot perceive it, but Because the system is a foreground service, it will not clean it up, so that the process of the application remains resident, so as to keep the application alive. Wherein, the keep alive of the application may be started by setting a foreground service after the application is closed, or it may be a certain service that is set as a foreground service during the running process of the application to keep running permanently, the embodiment of the present application This is not restricted.

The technical solution provided in this embodiment is applicable to an application scenario in which an application is kept alive by setting a foreground service. When it is detected that the event of the application requesting to set the foreground service is triggered, the application information of the application requesting to set the foreground service is obtained.

Wherein, the detecting that the event of the application requesting to set the foreground service is triggered may include: detecting that the event of calling the setting function for setting the foreground service is triggered, and the setting function may be the startForeground function.

The application information may include application attribute information and/or application setting information and/or application running information and the like of the application. The application attribute information may include information such as a user identifier (User Identifier, UID), an application package name, and a process identifier (Process Identifier, PID). The application setting information may include: whether the application is set as a member in the set whitelist, or whether the self-starting switch of the application is set to on, or whether the application is set as a frequently used application of the user, and the like. The application running information may include: running information such as the frequency of use of the application, the running priority or the type of the application, or the feedback information of the user during the running process of the application, or whether the application has a corresponding foreground interface during the running process And/or set the number of times the foreground service is running, etc. The user's feedback information may include that the user manually closes the application.

Step 102 , according to the preset foreground service setting policy, based on the application information, determine whether the application can set the foreground service, if yes, go to step 103 , otherwise go to step 104 .

Based on the application attribute information and/or application setting information and/or application running information according to the preset foreground service setting policy, it is determined whether the application can set the foreground service. If the judgment result is that the application program can set foreground service, it means that the application program is a normal application program, and the operation of setting foreground service for the application program can be controlled to be executed. If the judgment result is that the application program cannot be set If the application is a foreground service, it means that the application is a rogue application, and the application is prohibited from setting a foreground service.

Step 103 , prohibiting the application from setting the foreground service, so as to prohibit the application from keeping alive by setting the foreground service.

Wherein, the implementation manner of prohibiting the application from setting the foreground service may be prohibiting calling the above-mentioned setting function to set the foreground service, or prohibiting the execution of the operation of canceling the notification, so that the user knows that such an application has set the foreground service, The user can choose whether to close the application. After it is determined according to the above step 102 that the application is a rogue application, by prohibiting the application from setting the foreground service, the application can be prohibited from setting the foreground service to keep alive.

Step 104: Control the execution of an operation of setting a foreground service for the application.

In some embodiments, the following steps may also be included: saving the application package name of the application as an interception record, and displaying the interception record to the user.

In some embodiments, the following step may also be included: if the application is a built-in application of the system, allowing the application to set a foreground service.

In some embodiments, the following step may be further included: locally acquiring the preset foreground setting policy from a server or a mobile terminal.

In some embodiments, before judging whether the application can set the foreground service based on the application information according to the preset foreground service setting policy, the following step may be further included: judging that the application requests to be set as the foreground service Whether the target service satisfies the second setting condition, if so, it is determined that the application can set the target service as a foreground service; if not, the application is determined based on the application information according to a preset foreground service setting policy Whether the program can set the foreground service or determine that the application cannot set the target service as the foreground service. The second setting condition may be that the service name of the target service is in a preset service whitelist, or the service type of the target service is a setting service type, such as a payment service type.

In the method provided by this embodiment, by obtaining the application information of the application requesting to set the foreground service, and according to the preset foreground service setting policy based on the application information, it is judged whether the application can set the foreground service, and if the judgment result is that it cannot be set , then the application is prohibited from setting the foreground service to prevent the application from keeping alive by setting the foreground service, so that the keep-alive operation of the application can be reasonably controlled, so as to avoid wasting the mobile terminal due to some rogue applications keeping themselves alive. Operating resources, power and traffic also improve the smoothness of mobile terminal operation.

FIG. 2 shows a flowchart of another application program keep-alive management and control method provided by an embodiment of the present application. As shown in FIG. 2 , the method provided by this embodiment includes the following steps:

Step 201: Obtain application information of an application requesting to set a foreground service.

Step 202: According to the first preset foreground service setting policy, based on the application setting information of the application, determine whether the application can set the foreground service. If yes, go to step 203, otherwise go to step 204.

In some embodiments, this step 202 may include: if the application is in the whitelist for setting, determining that the application can set the foreground service, otherwise, determining that the application cannot set the foreground service; or , if the self-starting switch of the application program is turned on, it is determined that the application program can set the foreground service; otherwise, it is determined that the application program cannot set the foreground service. If the application is in the set whitelist, it means that the application is a normal application, and it can be determined that the application can be set as a foreground service; otherwise, it means that the application is a rogue application, and it is determined that the application cannot be set to a foreground service. ; If the self-start switch of the application program is turned on, it means that the application program is a normal application that can self-start and keep alive in a timely manner, then it can be determined that the application program can be set as a foreground service, otherwise, the application program is a rogue application, Then it is determined that the application cannot set the foreground service. Among them, applications commonly used by users or relatively basic can be set in the whitelist, for example, the WeChat application is set in the whitelist, but the game application is not set in the whitelist.

Optionally, the method further includes the following step: locally acquiring the preset whitelist from the server or the mobile terminal. Further, the preset whitelist can be updated in real time, for example, when an update instruction from the user is received, the preset whitelist is updated, or when a target application that meets the update conditions is detected, the target application is added. To the preset whitelist, the update condition may include adding the target application to the preset whitelist when the number of times the target application is launched by the user reaches the set launch times, or when the number of self-launches is greater than the set launch times, from the preset whitelist. delete.

Optionally, after determining that the application can set the foreground service, it may further include: judging whether the system sends a corresponding notification after the application sets the foreground service; if not, blacklisting the application , the application is not allowed to set foreground services subsequently. Generally, if the application sets up the foreground service, the corresponding notification will be displayed in the status bar. If the system does not send a notification, it means that the rogue application has cleared the notification in order not to let the user know that it is running secretly. The application is added to the blacklist.

Step 203 , prohibiting the application from setting the foreground service, so as to prohibit the application from keeping alive by setting the foreground service.

Step 204: Control the execution of an operation of setting a foreground service for the application.

The method provided by this embodiment determines whether the application can set the foreground service by acquiring the application information of the application requesting to set the foreground service, and based on the application setting information of the application according to the first preset foreground service setting policy, If the judgment result is no, the application is prohibited from setting the foreground service to prevent the application from keeping alive by setting the foreground service, which can reasonably control the keep-alive operation of the application and avoid keeping itself alive due to some rogue applications. , and the running resources, power and traffic of the mobile terminal are wasted, and the smoothness of the operation of the mobile terminal is also improved.

FIG. 3 shows a flowchart of another application program keep-alive management and control method provided by an embodiment of the present application. As shown in FIG. 3 , the method provided by this embodiment includes the following steps:

Step 301: Obtain application information of an application requesting to set a foreground service.

Step 302: According to the second preset foreground service setting policy, based on the application running information of the application, determine whether the application can set the foreground service, if yes, go to step 303, otherwise go to step 304.

In some embodiments, this step 302 may include: if the setting attribute of the application satisfies the first setting condition, determining that the application can set the foreground service; otherwise, determining that the application cannot be set Foreground service, the set attribute includes at least one of frequency of use, running priority and type; or, if the application program is an application program without a foreground interface and the number of times of setting the foreground service is greater than the set number of times, then determine The application program cannot set the foreground service, otherwise, it is determined that the application program can set the foreground service. Wherein, the first setting condition may include that the use frequency is greater than the set frequency, the operation priority is greater than the set priority, and the application type is at least one of the set types. When the frequency of use is greater than the set frequency, it means that the application is an application frequently used by the user and is a normal application. Exemplarily, the setting type may be a calendar, a shooting type, or the like.

Optionally, after determining that the application can set the foreground service, the method further includes: judging whether the system sends a notification after the application has set the foreground service; The application is not allowed to set a foreground service.

Step 303 , prohibit the application from setting the foreground service, so as to prohibit the application from keeping alive by setting the foreground service.

Step 304: Control the execution of an operation of setting a foreground service for the application.

In the method provided by this embodiment, by acquiring the application information of the application requesting to set the foreground service, it is judged whether the application can set the foreground service based on the application running information of the application according to the second preset foreground service setting policy, If the judgment result is no, the application is prohibited from setting the foreground service to prevent the application from keeping alive by setting the foreground service, which can reasonably control the keep-alive operation of the application and avoid keeping itself alive due to some rogue applications. , and the running resources, power and traffic of the mobile terminal are wasted, and the smoothness of the operation of the mobile terminal is also improved.

FIG. 4 is a schematic structural diagram of a management and control device for keeping an application program alive according to an embodiment of the present application. The device may be implemented by software and/or hardware and integrated in a mobile terminal. As shown in FIG. 4 , the device includes an application information acquisition module 41 , a foreground service setting judgment module 42 and a foreground service setting prohibition module 43 .

The application information obtaining module 41 is used for obtaining the application information of the application requesting to set the foreground service;

The foreground service setting judging module 42 is configured to judge whether the application can set the foreground service based on the application information according to the preset foreground service setting policy;

The foreground service setting prohibition module 43 is configured to prohibit the application from setting the foreground service if the application cannot set the foreground service, so as to prohibit the application from starting by setting the foreground service.

The device for managing and controlling the application program keeping alive provided by this embodiment determines whether the application program can set the foreground service according to the preset foreground service setting policy based on the application information by acquiring the application information of the application program that requests to set the foreground service, If the judgment result is no, the application is prohibited from setting the foreground service to prevent the application from keeping alive by setting the foreground service, which can reasonably control the keep-alive operation of the application and avoid keeping itself alive due to some rogue applications. , and the running resources and power of the mobile terminal are wasted, and the smoothness of the running of the mobile terminal is also improved.

Optionally, the foreground service setting judgment module includes:

The first foreground service setting judging unit is configured to, according to a first preset foreground service setting policy, judge whether the application program can set the foreground service based on the application setting information of the application program.

Optionally, the foreground service setting judgment module includes:

The second foreground service setting judging unit is configured to, according to a second preset foreground service setting policy, determine whether the application can set the foreground service based on the application running information of the application.

Optionally, the first foreground service setting judgment unit is specifically used for:

If the application is in the set whitelist, it is determined that the application can set the foreground service; otherwise, it is determined that the application cannot be set to the foreground service; or,

If the self-starting switch of the application program is turned on, it is determined that the application program can set the foreground service; otherwise, it is determined that the application program cannot set the foreground service.

Optionally, the second foreground service setting judgment unit is specifically used for:

If the set attribute of the application satisfies the first set condition, it is determined that the application can set the foreground service; otherwise, it is determined that the application cannot set the foreground service, and the set attribute includes the frequency of use, running at least one of priority and type; or,

If the application program is an application program without a foreground interface and the number of times of setting the foreground service is greater than the set number of times, it is determined that the application program cannot set the foreground service; otherwise, it is determined that the application program can set the foreground service.

Optionally, the device may also include:

a preset foreground setting strategy acquisition module, configured to locally obtain the preset foreground setting strategy from a server or a mobile terminal; and/or,

The preset whitelist obtaining module is configured to obtain the preset whitelist locally from the server or the mobile terminal.

Optionally, the device may also include:

a notification sending judgment module, used to determine whether the system sends a notification after the application program can set the foreground service after determining that the application program can set the foreground service;

The blacklist adding module is used for blacklisting the application if no notification is issued, and subsequently not allowing the application to set foreground services.

Optionally, the device further includes:

The foreground service setting module is configured to judge whether the target service requested by the application program to be set as the foreground service satisfies the second setting condition, and if so, determine that the application program can set the target service as the foreground service.

Embodiments of the present application further provide a storage medium containing computer-executable instructions, where the computer-executable instructions are used to execute a management and control method for application program keeping alive when executed by a computer processor, and the method includes:

Get the application information of the application requesting to set the foreground service;

According to the preset foreground service setting policy, based on the application information, determine whether the application can set the foreground service;

If not, the application program is prohibited from setting the foreground service, so as to prohibit the application program from keeping alive by setting the foreground service.

storage medium - any of various types of memory devices or storage devices. The term "storage medium" is intended to include: installation media, such as CD-ROMs, floppy disks, or tape devices; computer system memory or random access memory, such as DRAM, DDR RAM, SRAM, EDO RAM, Rambus RAM, etc. ; non-volatile memory, such as flash memory, magnetic media (eg hard disk or optical storage); registers or other similar types of memory elements, etc. The storage medium may also include other types of memory or combinations thereof. In addition, the storage medium may be located in the first computer system in which the program is executed, or may be located in a second, different computer system connected to the first computer system through a network such as the Internet. The second computer system may provide program instructions to the first computer for execution. The term "storage medium" may include two or more storage media that may reside in different locations (eg, in different computer systems connected by a network). The storage medium may store program instructions (eg, embodied as a computer program) executable by one or more processors.

Of course, a storage medium containing computer-executable instructions provided by the embodiments of the present application, the computer-executable instructions of which are not limited to the management and control operations for keeping the application program alive as described above, and can also execute the storage medium provided by any embodiment of the present application. Related operations in the control method of application keep-alive.

The embodiments of the present application provide a mobile terminal, in which the mobile terminal can integrate the application program keep alive management and control device provided by the embodiments of the present application. FIG. 5 is a schematic structural diagram of a mobile terminal according to an embodiment of the present application. The mobile terminal 500 may include: a memory 501, a processor 502, and a computer program stored on the memory 501 and executed on the processor 502, and the processor 502 implements the applications described in the embodiments of the present application when the processor 502 executes the computer program The control method of program keep-alive.

The mobile terminal provided by the embodiment of the present application can reasonably control the keep-alive operation of the application program, so as to prevent the rogue application program from keeping alive by setting the foreground service, which wastes the operating resources and power of the mobile terminal, and also improves the running efficiency of the mobile terminal. Fluency.

FIG. 6 is a schematic structural diagram of another mobile terminal provided by an embodiment of the present application. As shown in FIG. 6 , the mobile terminal may include: a memory 601, a central processing unit (Central Processing Unit, CPU) 602 (also known as a processor, Hereinafter referred to as CPU), the memory 601 is used to store executable program codes; the processor 602 runs a program corresponding to the executable program codes by reading the executable program codes stored in the memory 601, To perform: obtain the application information of the application requesting to set the foreground service; judge whether the application can set the foreground service based on the application information according to the preset foreground service setting policy; if not, prohibit the application A foreground service is set to prohibit the application from being kept alive by setting a foreground service.

The mobile terminal further includes: a peripheral interface 603, an RF (Radio Frequency, radio frequency) circuit 605, an audio circuit 606, a speaker 611, a power management chip 608, an input/output (I/O) subsystem 609, a touch screen 612, and other Input/control devices 610 and external ports 604, these components communicate through one or more communication buses or signal lines 607.

It should be understood that the illustrated mobile terminal 600 is only an example of a mobile terminal, and that the mobile terminal 600 may have more or fewer components than those shown in the figure, two or more components may be combined, Or can have different component configurations. The various components shown in the figures may be implemented in hardware, software, or a combination of hardware and software, including one or more signal processing and/or application specific integrated circuits.

The following will describe in detail the mobile terminal provided by this embodiment for keeping the application program alive. The mobile terminal is a mobile phone as an example.

Memory 601, which can be accessed by CPU 602, peripheral interface 603, etc., said memory 601 can include high-speed random access memory, and can also include non-volatile memory, such as one or more disk storage devices, flash memory devices , or other volatile solid-state storage devices.

A peripheral interface 603 that can connect the input and output peripherals of the device to the CPU 502 and the memory 601 .

I/O subsystem 609 , which can connect input and output peripherals on the device, such as touch screen 612 and other input/control devices 610 , to peripherals interface 603 . The I/O subsystem 609 may include a display controller 6091 and one or more input controllers 6092 for controlling other input/control devices 610 . Wherein, one or more input controllers 6092 receive electrical signals from or send electrical signals to other input/control devices 610, which may include physical buttons (push buttons, rocker buttons, etc. ), dial pad, slide switch, joystick, click wheel. Notably, the input controller 6092 can be connected to any of the following: a keyboard, an infrared port, a USB interface, and a pointing device such as a mouse.

The touch screen 612, which is an input interface and an output interface between the user terminal and the user, displays visual output to the user, and the visual output may include graphics, text, icons, videos, and the like.

Display controller 6091 in I/O subsystem 609 receives electrical signals from touch screen 612 or sends electrical signals to touch screen 612 . The touch screen 612 detects the contact on the touch screen, and the display controller 6091 converts the detected contact into interaction with the user interface object displayed on the touch screen 612, that is, to realize human-computer interaction, and the user interface object displayed on the touch screen 612 can be run. Icons for games, icons for connecting to the corresponding network, etc. It is worth noting that the device may also include a light mouse, which is a touch-sensitive surface that does not display visual output, or an extension of the touch-sensitive surface formed by a touch screen.

The RF circuit 605 is mainly used to establish the communication between the mobile phone and the wireless network (ie, the network side), and realize the data reception and transmission between the mobile phone and the wireless network. Such as sending and receiving text messages, e-mails, etc. Specifically, the RF circuit 605 receives and transmits RF signals, also known as electromagnetic signals, the RF circuit 605 converts electrical signals into electromagnetic signals or converts electromagnetic signals into electrical signals, and communicates with communication networks and other devices through the electromagnetic signals to communicate. RF circuitry 605 may include known circuitry for performing these functions including, but not limited to, antenna systems, RF transceivers, one or more amplifiers, tuners, one or more oscillators, digital signal processors, CODECs ( COder-DECoder, codec) chip set, subscriber identity module (Subscriber Identity Module, SIM) and so on.

The audio circuit 606 is mainly used for receiving audio data from the peripheral interface 603 , converting the audio data into an electrical signal, and sending the electrical signal to the speaker 611 .

The speaker 611 is used to restore the voice signal received by the mobile phone from the wireless network through the RF circuit 605 to sound and play the sound to the user.

The power management chip 608 is used for power supply and power management for the hardware connected to the CPU 602 , the I/O subsystem and the peripheral interface 603 .

The application keep-alive management and control device, storage medium, and mobile terminal provided in the above embodiments can execute the application keep-alive management and control method provided by any embodiment of the present application, and have corresponding functional modules and beneficial effects for executing the method. For technical details that are not described in detail in the foregoing embodiments, reference may be made to the management and control method for application keep-alive provided by any embodiment of the present application.

The above are only the preferred embodiments of the present application and the applied technical principles. The present application is not limited to the specific embodiments described herein, and various obvious changes, readjustments and substitutions that can be made by those skilled in the art will not depart from the protection scope of the present application. Therefore, although the present application has been described in detail through the above embodiments, the present application is not limited to the above embodiments, and can also include more other equivalent embodiments without departing from the concept of the present application. The scope is determined by the scope of the claims.

Claims (11)

1. A control method for keeping alive of an application program is characterized by comprising the following steps:

acquiring application information of an application program requesting to set foreground service;

judging whether the application program can set foreground service or not based on the application information according to a preset foreground service setting strategy;

if not, forbidding the application program to set foreground service so as to forbid the application program to keep alive through setting the foreground service;

the determining whether the application program can set foreground service based on the application information according to the preset foreground service setting policy includes:

and if the application program is the application program without the foreground interface and the frequency of setting the foreground service is greater than the set frequency, determining that the application program cannot set the foreground service, otherwise, determining that the application program can set the foreground service.

2. The method of claim 1, wherein the determining whether the application program can set the foreground service based on the application information according to the preset foreground service setting policy comprises:

and judging whether the application program can set foreground service or not based on the application setting information of the application program according to a first preset foreground service setting strategy.

3. The method of claim 1, wherein the determining whether the application program can set the foreground service based on the application information according to the preset foreground service setting policy comprises:

and judging whether the application program can set foreground service or not based on the application running information of the application program according to a second preset foreground service setting strategy.

4. The method of claim 2, wherein the determining whether the application can set the foreground service based on the application setting information of the application according to the first preset foreground service setting policy comprises:

if the application program is in a set white list, determining that the application program can set foreground service, otherwise, determining that the application program cannot set foreground service; or,

and if the self-starting switch of the application program is turned on, determining that the application program can set foreground service, otherwise, determining that the application program cannot set foreground service.

5. The method according to claim 3, wherein the determining whether the application program can set the foreground service based on the application running information of the application program according to the second preset foreground service setting policy comprises:

if the set attribute of the application program meets a first set condition, determining that the application program can set foreground service, otherwise, determining that the application program can not set foreground service, wherein the set attribute comprises at least one of use frequency, operation priority and type.

6. The method of claim 4, further comprising:

locally acquiring the preset foreground setting strategy from a server or a mobile terminal; and/or the presence of a gas in the gas,

and locally acquiring the set white list from a server or a mobile terminal.

7. The method of claim 4 or 5, after determining that the application can set a foreground service, further comprising:

judging whether the system sends out a corresponding notice after the application program sets foreground service;

if not, the application program is listed in a blacklist, and the application program is not allowed to set foreground service subsequently.

8. The method of claim 1, further comprising:

and judging whether the target service set as foreground service requested by the application program meets a second set condition, and if so, determining that the target service can be set as foreground service by the application program.

9. The utility model provides a management and control device of application keep-alive which characterized in that includes:

the application information acquisition module is used for acquiring the application information of the application program requesting to set the foreground service;

a foreground service setting judgment module, configured to judge whether the application program can set a foreground service based on the application information according to a preset foreground service setting policy;

a foreground service setting prohibition module, configured to prohibit the application from setting a foreground service if the application cannot set the foreground service, so as to prohibit the application from starting by setting the foreground service;

the foreground service setting judgment module comprises: a second foreground service setting judgment unit;

the second foreground service setting judgment unit is specifically configured to: and if the application program is the application program without the foreground interface and the frequency of setting the foreground service is greater than the set frequency, determining that the application program cannot set the foreground service, otherwise, determining that the application program can set the foreground service.

10. A computer-readable storage medium, on which a computer program is stored, which, when executed by a processor, implements a method of governing application bootstrapping according to any one of claims 1-8.

11. A mobile terminal comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor implements the method for managing application self-launching as claimed in any one of claims 1 to 8 when executing the computer program.

Images