WO2019061331A1

WO2019061331A1 - Method, apparatus and readable storage medium for blocking app-to-app wake-up

Info

Publication number: WO2019061331A1
Application number: PCT/CN2017/104497
Authority: WO
Inventors: 杨绪鹏; 刘维锋
Original assignee: 深圳传音通讯有限公司
Priority date: 2017-09-29
Filing date: 2017-09-29
Publication date: 2019-04-04

Abstract

Disclosed is an apparatus and a readable storage medium for blocking app-to-app wake-up, the method comprising the steps of: upon detecting that a first application is activated, detecting, via AMS (Activity Manager Service in Android), whether a second application is woken up (S10); if the second application is woken up, acquiring identification information of an application running in foreground and marking the same as first identification information; acquiring identification information of the second application and marking the same as second identification information (S20); and if the first identification information and the second identification information do not match, blocking services of the second application from running (S30). The method can be used to realize blocking of app-to-app wake-up processes without requiring collection of a large amount of data and data analysis, thereby increasing the efficiency of blocking app-to-app wake-up and lowering the cost of blocking the same.

Description

Method, device, and readable storage medium that prohibit applications from waking each other

Technical field

The present invention relates to the field of communications technologies, and in particular, to a method, a device, and a readable storage medium for prohibiting application programs from awakening each other.

Background technique

Applications developed by the same manufacturer or applications developed by related vendors may wake up each other. When one of the applications starts, another or multiple applications are also launched. For example, when Baidu Mobile Assistant is launched, Baidu Maps and Baidu Browsers that have not been started before will also be launched. Baidu Maps and Baidu Browser services will also be pulled up, resulting in increased memory usage of the terminal and processing speed of the terminal system. Reduce, increase the power consumption of the terminal and other consequences.

The currently used methods for prohibiting applications from waking each other are generally to collect related applications that are frequently awake from each other in the commonly used applications in the country through big data technology, and then these applications are still awakened when other applications are started. This approach requires the support of big data technology, requires a large amount of data collection, and then through data analysis to find applications that wake each other. However, with the development of terminal technologies, the types of applications on the market continue to increase, so data collection and data analysis are required to accurately prohibit applications from awakening each other. It can be seen that the existing methods for prohibiting applications from awakening each other are costly and inefficient.

Summary of the invention

The main object of the present invention is to provide a method, a device, and a readable storage medium for prohibiting application programs from awakening each other, and to solve the technical problem of high cost and low efficiency of the existing method for prohibiting application mutual wake-up.

To achieve the above object, the present invention provides a method for prohibiting applications from waking up each other, and the method for prohibiting applications from waking each other includes the steps of:

When it is detected that the first application is started, it is detected by the Android Activity Manager service AMS whether a second application is awakened;

If the second application is awakened, obtaining identification information of the application running in the foreground, recording the first identification information, and acquiring the identification information of the second application, and recording the second identification information;

If the matching of the first identification information and the second identification information fails, the service operation of the second application is prohibited.

Preferably, if the matching of the first identifier information and the second identifier information fails, the step of disabling the service operation of the second application comprises:

And if the matching of the first identifier information and the second identifier information fails, acquiring authorization information of the second application;

Determining, according to the authorization information, whether the second application has a running permission;

If it is determined that the second application does not have the running permission according to the authorization information, the service running of the second application is prohibited.

Preferably, after the step of determining, according to the authorization information, whether the second application has a running right, the method further includes

If it is determined according to the authorization information that the second application has running permission, the service of the second application is allowed to run.

Preferably, if the determining that the second application has running permission according to the authorization information, the step of allowing the service of the second application to run includes:

If it is determined that the second application has a running permission according to the authorization information, determining whether the service that the second application is running has a running permission;

If the service that the second application is running has running permission, the service that the second application is running is allowed to run.

Preferably, if the determining that the second application has a running right according to the authorization information, determining whether the service running by the second application has a running right, the method further includes:

If the running service of the second application is not running, the running of the service running by the second application is prohibited.

Preferably, if the second application is awakened, acquiring identification information of the application running in the foreground, recording the first identification information, and acquiring the identification information of the second application, and recording the second identifier After the steps of the information, it also includes:

Determining whether the first identification information and the second identification information are successfully matched;

If the first identification information and the second identification information match successfully, the service of the second application is allowed to run.

If the matching of the first identification information and the second identification information fails, the application component of the second application is disabled, and/or the process corresponding to the second application service is killed.

Preferably, after the step of disabling the service of the second application by the first identification information and the second identification information, the method further includes:

Adding the second identification information to the disabled list corresponding to the first application.

In addition, in order to achieve the above object, the present invention also provides an apparatus for prohibiting applications from waking each other, the apparatus for prohibiting applications from waking each other, including a memory, a processor, and a memory stored on the processor and on the processor A running program that prohibits applications from waking each other, and the program for prohibiting application wake-ups from each other is executed by the processor to implement the steps of the method of prohibiting the application from awakening each other as described above.

In addition, in order to achieve the above object, the present invention further provides a computer readable storage medium having stored thereon a program for prohibiting application programs from waking each other, and the program for prohibiting application programs from waking each other is executed by a processor. The steps of the method of prohibiting application wake-ups from each other as described above are implemented.

The invention detects whether a second application is awakened by the AMS when detecting that the first application is started; if the second application is awakened, acquiring the identification information of the application running in the foreground, recorded as the first An identification information, and the identification information of the second application is recorded as the second identification information; if the matching of the first identification information and the second identification information fails, the service of the second application is prohibited run. When the application in the mobile terminal is started, if the application that is awake is detected by the AMS, and the awake application is not the application running in the foreground of the mobile terminal, the application that is awake is prohibited. The service is running. In the process of prohibiting application mutual wake-up, it does not need a lot of data collection and data analysis, which improves the efficiency of prohibiting applications from waking each other and reduces the cost of prohibiting applications from awakening each other.

DRAWINGS

1 is a schematic structural diagram of a hardware operating environment involved in an embodiment of the present invention;

2 is a schematic flowchart of a first embodiment of a method for prohibiting applications from awakening each other according to the present invention;

3 is a schematic flowchart of disabling service operation of the second application program if the first identifier information and the second identifier information fail to match in the embodiment of the present invention;

FIG. 4 is a schematic flowchart of allowing the service of the second application to run according to the authorization information, if the second application has the running permission according to the authorization information;

FIG. 5 is a schematic flowchart diagram of a fourth embodiment of a method for prohibiting application programs from awakening each other according to the present invention.

The implementation, functional features, and advantages of the present invention will be further described in conjunction with the embodiments.

Detailed ways

It is understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.

The solution of the embodiment of the present invention is mainly: when detecting that the first application is started, detecting whether a second application is awakened by the Android Activity Manager service AMS; if the second application is awakened, acquiring The identification information of the application running in the foreground is recorded as the first identification information, and the identification information of the second application is obtained as the second identification information; if the first identification information matches the second identification information If it fails, the service running of the second application is prohibited. To solve the problem of high cost and low efficiency in the existing method of prohibiting applications from awakening each other.

As shown in FIG. 1, FIG. 1 is a schematic structural diagram of a hardware operating environment involved in an embodiment of the present invention.

It should be noted that FIG. 1 may be a schematic structural diagram of a hardware operating environment of a device that prohibits applications from waking each other. The device for prohibiting the application from waking up to each other in the embodiment of the present invention may be a terminal device such as a PC, a smart phone, or a portable computer.

As shown in FIG. 1, the device for prohibiting applications from waking up each other may include: a processor 1001, such as a CPU, a network interface 1004, a memory 1005, and a communication bus 1002. Among them, the communication bus 1002 is used to implement connection communication between these components. The user interface 1003 can include a display, an input unit such as a keyboard, and the optional user interface 1003 can also include a standard wired interface, a wireless interface. The network interface 1004 can optionally include a standard wired interface, a wireless interface (such as a WI-FI interface). The memory 1005 may be a high speed RAM memory or a stable memory (non-volatile) Memory), such as disk storage. The memory 1005 can also optionally be a storage device independent of the aforementioned processor 1001.

Optionally, the device that prohibits the application from waking each other may also include a camera, RF (Radio) Frequency, RF) circuits, sensors, audio circuits, WiFi modules, and more.

It will be understood by those skilled in the art that the device structure shown in FIG. 1 for prohibiting applications from waking up to each other does not constitute a limitation of the terminal, and may include more or less components than those illustrated, or combine some components, or different. Parts layout.

As shown in FIG. 1, a memory 1005 as a computer storage medium may include an operating system and a program for prohibiting applications from waking each other. Among them, the operating system is a program that manages and controls device hardware and software resources that prohibit applications from waking each other, and supports programs that prohibit applications from waking each other and other software or programs.

In the device shown in FIG. 1 for prohibiting applications from waking each other, the user interface 1003 is configured to receive an operation instruction of the user, start the application, and add the second identification information to the disabled list corresponding to the first application; the network interface 1004 It is mainly used to access the network, perform data connection, etc.; and the processor 1001 can be used to call a program stored in the memory 1005 that prohibits applications from waking each other, and performs the following operations:

Further, if the matching of the first identifier information and the second identifier information fails, the step of disabling the service operation of the second application includes:

Further, after the step of determining, according to the authorization information, whether the second application has a running right, the processor 1001 may further be configured to invoke a program stored in the memory 1005 that prohibits applications from waking each other, and performs the following steps. :

Further, if it is determined that the second application has running permission according to the authorization information, the step of allowing the service of the second application to run includes:

Further, if it is determined that the second application has a running right according to the authorization information, the processor 1001 may further be used to call after determining whether the service running by the second application has a running right. A program stored in the memory 1005 that prohibits applications from waking each other and performs the following steps:

Further, if the second application is awakened, acquiring identification information of the application running in the foreground, recording the first identification information, and acquiring the identification information of the second application, and recording the second identifier After the step of information, the processor 1001 can also be used to call a program stored in the memory 1005 that prohibits applications from waking each other, and performs the following steps:

Further, after the step of disabling the service of the second application is disabled, the processor 1001 may further be configured to invoke the storage in the memory 1005. Programs that prohibit applications from waking each other and perform the following steps:

Based on the above-described hardware structure, various embodiments of a method of prohibiting applications from awakening each other are proposed.

Referring to FIG. 2, FIG. 2 is a schematic flowchart diagram of a first embodiment of a method for prohibiting application programs from awakening each other according to the present invention.

In this embodiment, an embodiment of a method for prohibiting applications from waking each other is provided. It should be noted that although the logical order is shown in the flowchart, in some cases, it may be different from the order here. Perform the steps shown or described.

In this embodiment, the method for prohibiting the application from waking each other is applicable to the mobile terminal, and the method for prohibiting the application from awakening each other includes:

In step S10, when it is detected that the first application is started, it is detected by the Android Activity Manager service AMS whether a second application is woken up.

When the mobile terminal detects that the first application is started, the mobile terminal passes the AMS (Android Activity Manager) Service, Android Activity Manager Service) detects if a second application is woken up, ie detects if a second application is launched. Specifically, the user can launch the first application by clicking an icon of the first application in the mobile terminal, or set the first application to be automatically started when the mobile terminal starts. Mobile terminal passes AMS start Process The Locked method detects if the second application's service is pulled up in the background when the first application starts. If the service of the second application is pulled up in the background, it indicates that the second application is woken up; if the service of the second application is not pulled up, it indicates that the second application is not awake. With AMS, you can manage the progress of applications in your mobile terminal. In this embodiment, there may be one second application, and there may be multiple second applications.

Step S20: If the second application is awakened, obtain the identification information of the application running in the foreground, record the first identification information, and obtain the identification information of the second application, and record it as the second identification information.

When the mobile terminal detects that the second application is awakened when the first application is started, the mobile terminal acquires the identification information of the application that is running in the foreground, and records it as the first identification information, and acquires the second application. The identification information is recorded as the second identification information. It should be noted that the start through AMS Process The Locked method may acquire related information of all the awakened second applications in the first application startup in the mobile terminal, where the related information includes the identifier of the second application in addition to the information required for the second application to run. information. In this embodiment, the identification information is the package name of the application, and an application can be uniquely determined by the package name, and different applications can be distinguished by the package name. In other embodiments, the identification information of the application may also be represented by other information that can distinguish different applications. For example, when the package name of the mobile terminal is running PakageNameB, the PakageNameB is recorded as the first identification information, and the obtained package name of the second application is PakageNameC, and the PakageNameC is recorded as the second identification information.

Step S30: If the matching of the first identification information and the second identification information fails, the service operation of the second application is prohibited.

When the mobile terminal acquires the first identification information and the second identification information, the first identification information and the second identification information are matched. If the first identification information and the second identification information fail to match, the mobile terminal prohibits the service running of the second application, so that the second application enters the sleep state from the awake state. Specifically, when the package name of the application running in the foreground of the mobile terminal does not match the package name of the second application, that is, when PakageNameB and PakageNameC are different, the mobile terminal prohibits the service operation of the second application.

Further, step S30 includes:

In step a, if the matching of the first identifier information and the second identifier information fails, the application component of the second application is disabled, and/or the process corresponding to the second application service is killed.

If the first identification information fails to match the second identification information, the mobile terminal disables the application component of the second application, and/or kills the process corresponding to the second application service to prohibit the operation of the second application service. Wherein, an application of the mobile terminal is composed of a plurality of components, each component implements a specific function, and some components can enter the application as an entry point of the mobile terminal system, and the components of the application cooperate to form a complete application. An application has 4 different types of components, each with its own unique purpose and life cycle. The four components are: Activities, Services, Content Providers and Broadcast Receivers; an activity represents a window interface that interacts with the user; a service component does not provide an interactive interface, runs in the background, generally runs for a long time or performs remote access; Provider manages a set of shared application data; Broadcast Receivers are used to respond to system level broadcast notifications, including but not limited to screen shutdown, low battery and photo taking.

Further, the method for prohibiting applications from awakening each other further includes:

Step b: Determine whether the first identification information and the second identification information match successfully.

Step c: If the first identification information and the second identification information are successfully matched, the service of the second application is allowed to run.

When the mobile terminal acquires the first identifier information and the second identifier information, the mobile terminal matches the first identifier information and the second identifier information, and determines whether the first identifier information and the second identifier information match successfully. If the first identifier information and the second identifier information are consistent, the first identifier information and the second identifier information are successfully matched; if the first identifier information and the second identifier information are inconsistent, the first identifier information and the second identifier information are matched. failure.

When the first identification information and the second identification information match successfully, the mobile terminal allows the service of the second application to run. It can be understood that, in this embodiment, when the first identification information and the second identification information are successfully matched, it indicates that the second application is an application that is running in the foreground of the mobile terminal.

In this embodiment, when detecting that the first application is started, it is detected by the AMS whether a second application is awakened; if the second application is awakened, acquiring identification information of the application running in the foreground is recorded as The first identification information, and the identification information of the second application is recorded as the second identification information; if the matching of the first identification information and the second identification information fails, the second application is prohibited The service is running. When the application in the mobile terminal is started, if the application that is awake is detected by the AMS, and the awake application is not the application running in the foreground of the mobile terminal, the application that is awake is prohibited. The service is running. In the process of prohibiting application mutual wake-up, it does not need a lot of data collection and data analysis, which improves the efficiency of prohibiting applications from waking each other and reduces the cost of prohibiting applications from awakening each other.

Further, a second embodiment of the method for prohibiting application wake-ups from each other is proposed.

The method for prohibiting the application from waking each other to each other is different from the first embodiment of the method for prohibiting the application from waking up each other. Referring to FIG. 3, step S30 includes:

Step S31: If the first identifier information and the second identifier information fail to match, obtain the authorization information of the second application.

Step S32: Determine, according to the authorization information, whether the second application has running permission.

When the first identification information and the second identification information fail to match, the mobile terminal acquires the authorization information of the second application, and determines whether the second application has the running permission according to the obtained authorization information. In this embodiment, the authorization information may be represented by a specific character. Specifically, the specific character may be associated with the package name of the second application, and the authorization of the second application is obtained by the package name of the second application. information. If the authorization information is represented by the character “0” and the character “1”, when the character corresponding to the authorization information is “0”, it indicates that the second application is authorized; for example, when the character corresponding to the authorization information is “1”, Indicates that the second application is not authorized. It should be noted that, in this embodiment, if the second application is authorized, it indicates that when the first application is started, the second application is allowed to be woken up, that is, the second application has running permission; if the second application is used; If the program is not authorized, it indicates that when the first application is started, the second application is prohibited from being woken up, that is, the second application does not have the running program.

In this embodiment, the authorization information of the second application may be preset by the user, and the user may decide whether to wake up the second application when the first application is started according to specific needs. Specifically, a mapping relationship between the first application and the second application authorization information is established, and the authorization information of the second application is obtained by using the mapping relationship. In the mapping relationship, the package name of the first application is stored in association with the package name of the second application, and the package name of the second application is found by the package name of the first application, and the second application package name is determined by the second application package name. Authorization information for the second application.

Step S33: If it is determined that the second application does not have the running permission according to the authorization information, prohibiting the service running of the second application.

Step S34: If it is determined that the second application has running permission according to the authorization information, allowing the service of the second application to run.

If it is determined according to the authorization information that the second application does not have the running permission, the mobile terminal prohibits the service running of the second application. If it is determined according to the authorization information that the second application has running permission, the service of the second application is allowed to run.

In this embodiment, when the first identification information and the second identification information are inconsistent, it is further determined according to the authorization information of the second application whether to wake up the second application when the first application is started. It is implemented that the user can wake up the second application when the first application is started according to specific needs, instead of prohibiting any second application from being woken up when the first application is started, thereby improving the prohibition of the application by the mobile terminal. The intelligence of the mutual wake-up process.

Further, a third embodiment of the method of the present invention for prohibiting applications from awakening each other is proposed.

The method for prohibiting the application from waking each other to each other is different from the second embodiment of the method for prohibiting the application from awakening each other. Referring to FIG. 4, step S34 includes:

Step S341, if it is determined that the second application has running permission according to the authorization information, determine whether the service that the second application is running has running permission.

If it is determined according to the authorization information that the second application has running permission, the mobile terminal determines whether the service running by the second application has running permission. Specifically, the mobile terminal may determine, according to the service authority corresponding to the service that the second application is running, whether the service that the second application is running has running permission. It should be noted that the service authority corresponding to the service in the second application may be preset. If a service in the second application has a service right, it indicates that the service has a running right; if a service in the second application does not have a service right, it indicates that the service does not have a running right. Specifically, the service authority of the second application service may be represented by a specific character, and the character representing the service authority may be stored in association with the identification information of the second application, so as to determine the service authority of the second application to run the service. If the "00" character is used to indicate that the service of the second application does not have a service right, the "11" character is used to indicate that the service of the second application has a service right.

Further, in order to distinguish the running rights of different services of the second application, the service identifier of the second application may be added to the character representing the service authority to distinguish the service rights of the different services.

Step S342, if the running service of the second application is running, the service running by the second application is allowed to run.

Step S343: If the running service of the second application is not running, the running of the service that the second application is running is prohibited.

If the service running by the second application has running permission, the mobile terminal allows the service running by the second application to run; if the running service of the second application is not running, the mobile terminal prohibits the second application from being The running service is running.

In this embodiment, during the process of mutual wake-up of the application, according to the running permission of the service that is being awake, the running permission of the running service of the second application determines whether to prohibit the running of the service running by the second application, thereby prohibiting the application from awakening each other. The specific service of the second application is used as a prohibited unit, that is, during the startup process of the first application, only part of the service of the second application that is awake can be disabled, and the process of prohibiting the application from awakening each other by the mobile terminal is improved. Intelligence in the middle.

Further, a fourth embodiment of the method of the present invention for prohibiting applications from awakening each other is proposed.

The method for prohibiting the application from waking each other to each other is different from the first, second, and/or third embodiments of the method for prohibiting the application from awakening each other. Referring to FIG. 5, the method for prohibiting the application from awakening each other further includes :

Step S40: Add the second identification information to the disabled list corresponding to the first application.

After the service of the second application is prohibited from running, the mobile terminal adds the second identification information of the second application to the disabled list corresponding to the first application. It can be understood that, when the first application is started, the mobile terminal prohibits the second application corresponding to the second identification information in the first application disable list from being woken up.

Further, when the user wants to wake up the identification information and activate a second application in the disabled list when the first application is started, the mobile terminal may use the second identifier corresponding to the second application according to the operation instruction triggered by the user. The information is moved out of the disabled list to wake up the second application when the first application is launched.

In this embodiment, the identification information of the second application that is prohibited from being run is added to the disabled list of the first application, so that when the subsequent first application is started, the second application corresponding to the identification information in the disabled list is prohibited from being activated. The program improves the efficiency of prohibiting the second application from being launched when the first application is launched.

In addition, the embodiment of the present invention further provides a computer readable storage medium, where the program for prohibiting application programs from waking up each other is stored on the computer readable storage medium, and the program for prohibiting application programs from waking each other is executed by the processor as follows: step:

Further, after the step of determining, according to the authorization information, whether the second application has a running right, the program for prohibiting the application from waking each other by the processor is implemented as follows:

Further, if it is determined that the second application has a running permission according to the authorization information, and after determining, by the step of determining whether the service running by the second application has a running right, the prohibiting the application from awakening each other The following steps are implemented when the program is executed by the processor:

Further, if the second application is awakened, acquiring identification information of the application running in the foreground, recording the first identification information, and acquiring the identification information of the second application, and recording the second identifier After the step of information, the program for prohibiting the application from waking each other is executed by the processor to implement the following steps:

Further, after the step of disabling the service of the second application is prohibited if the first identification information fails to match the second identification information, the program that prohibits the application from waking each other is executed by the processor. The following steps are implemented:

The embodiments of the computer readable storage medium of the present invention are basically the same as the foregoing methods for prohibiting the application from awakening each other, and are not described herein again.

It is to be understood that the term "comprises", "comprising", or any other variants thereof, is intended to encompass a non-exclusive inclusion, such that a process, method, article, or device comprising a series of elements includes those elements. It also includes other elements that are not explicitly listed, or elements that are inherent to such a process, method, article, or device. An element that is defined by the phrase "comprising a ..." does not exclude the presence of additional equivalent elements in the process, method, item, or device that comprises the element.

The serial numbers of the embodiments of the present invention are merely for the description, and do not represent the advantages and disadvantages of the embodiments.

Through the description of the above embodiments, those skilled in the art can clearly understand that the foregoing embodiment method can be implemented by means of software plus a necessary general hardware platform, and of course, can also be through hardware, but in many cases, the former is better. Implementation. Based on such understanding, the technical solution of the present invention, which is essential or contributes to the prior art, may be embodied in the form of a software product stored in a storage medium (such as ROM/RAM, disk, The optical disc includes a number of instructions for causing a terminal device (which may be a cell phone, a computer, a server, an air conditioner, or a network device, etc.) to perform the methods described in various embodiments of the present invention.

The above are only the preferred embodiments of the present invention, and are not intended to limit the scope of the invention, and the equivalent structure or equivalent process transformations made by the description of the present invention and the drawings are directly or indirectly applied to other related technical fields. The same is included in the scope of patent protection of the present invention.

Claims

A method for prohibiting applications from waking each other, wherein the method for prohibiting applications from waking each other includes the following steps:

When it is detected that the first application is started, it is detected by the Android Activity Manager service AMS whether a second application is awakened;

If the second application is awakened, obtaining identification information of the application running in the foreground, recording the first identification information, and acquiring the identification information of the second application, and recording the second identification information;

If the matching of the first identification information and the second identification information fails, the service operation of the second application is prohibited.
The method for prohibiting an application from waking each other according to claim 1, wherein if the matching of the first identification information and the second identification information fails, the service of the second application is prohibited from running. The steps include:

And if the matching of the first identifier information and the second identifier information fails, acquiring authorization information of the second application;

Determining, according to the authorization information, whether the second application has a running permission;

If it is determined that the second application does not have the running permission according to the authorization information, the service running of the second application is prohibited.
The method for prohibiting an application from waking each other according to claim 2, wherein the step of determining whether the second application has a running right according to the authorization information further includes

If it is determined according to the authorization information that the second application has running permission, the service of the second application is allowed to run.
The method for prohibiting an application from waking each other according to claim 3, wherein if the second application has a running permission according to the authorization information, the service of the second application is allowed to run. The steps include:

If it is determined that the second application has a running permission according to the authorization information, determining whether the service that the second application is running has a running permission;

If the service that the second application is running has running permission, the service that the second application is running is allowed to run.
The method for prohibiting an application from waking each other according to claim 4, wherein if it is determined that the second application has a running right according to the authorization information, determining that the second application is running a service After the step of running permissions, it also includes:

If the running service of the second application is not running, the running of the service running by the second application is prohibited.
The method for prohibiting an application from waking up each other according to claim 1, wherein if the second application is awakened, obtaining identification information of an application running in the foreground is recorded as first identification information, and After the step of obtaining the identifier information of the second application, which is recorded as the second identifier information, the method further includes:

Determining whether the first identification information and the second identification information are successfully matched;

If the first identification information and the second identification information match successfully, the service of the second application is allowed to run.
The method for prohibiting an application from waking each other according to claim 1, wherein if the matching of the first identification information and the second identification information fails, the service of the second application is prohibited from running. The steps include:

If the matching of the first identification information and the second identification information fails, the application component of the second application is disabled, and/or the process corresponding to the second application service is killed.
The method for prohibiting an application from awakening each other according to any one of claims 1 to 7, wherein if the first identification information and the second identification information fail to match, the second application is prohibited. After the steps of the program's service run, it also includes:

Adding the second identification information to the disabled list corresponding to the first application.
A device for prohibiting applications from waking each other, wherein the device for prohibiting applications from waking each other includes a memory, a processor, and a forbidden application stored on the memory and operable on the processor to wake each other The program of the method for inhibiting application wake-up from each other as claimed in any one of claims 1 to 8 when the program for prohibiting application wake-up from each other is executed by the processor.
A computer readable storage medium, characterized in that the computer readable storage medium stores a program for prohibiting application programs from waking each other, and the program for prohibiting application wake-up from each other is implemented by the processor as claimed in claim 1 The method of the method of prohibiting an application from awakening each other as set forth in any one of 8.