CN115033305A - Application identification method and device, storage medium and electronic equipment - Google Patents
Application identification method and device, storage medium and electronic equipment Download PDFInfo
- Publication number
- CN115033305A CN115033305A CN202210745104.XA CN202210745104A CN115033305A CN 115033305 A CN115033305 A CN 115033305A CN 202210745104 A CN202210745104 A CN 202210745104A CN 115033305 A CN115033305 A CN 115033305A
- Authority
- CN
- China
- Prior art keywords
- application
- alive
- keep
- started
- reason information
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 117
- 230000006399 behavior Effects 0.000 claims description 19
- 238000004590 computer program Methods 0.000 claims description 12
- 230000008569 process Effects 0.000 description 54
- 238000013475 authorization Methods 0.000 description 27
- 230000000875 corresponding effect Effects 0.000 description 25
- 238000004140 cleaning Methods 0.000 description 21
- 238000012360 testing method Methods 0.000 description 19
- 238000009434 installation Methods 0.000 description 13
- 238000010586 diagram Methods 0.000 description 8
- 238000012545 processing Methods 0.000 description 4
- 230000002596 correlated effect Effects 0.000 description 3
- 230000006870 function Effects 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 3
- 238000013459 approach Methods 0.000 description 2
- 238000013461 design Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 230000007246 mechanism Effects 0.000 description 2
- 238000012544 monitoring process Methods 0.000 description 2
- 238000004088 simulation Methods 0.000 description 2
- 230000001276 controlling effect Effects 0.000 description 1
- 230000004083 survival effect Effects 0.000 description 1
- 238000010998 test method Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44505—Configuring for program initiating, e.g. using registry, configuration files
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D30/00—Reducing energy consumption in communication networks
- Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
The application discloses an application identification method, an application identification device, a storage medium and electronic equipment. The method comprises the following steps: acquiring starting reason information of a started application; and determining the started application of which the starting reason information meets the preset keep-alive condition as the keep-alive application. The method and the device can realize automatic identification keep-alive application.
Description
Technical Field
The present application belongs to the field of electronic technologies, and in particular, to an application identification method, apparatus, storage medium, and electronic device.
Background
A part of malicious applications in the current application market utilize the mechanism design of a system, and keep-alive is carried out by continuously researching various keep-alive means. The keep-alive behavior has a great influence on the performance, power consumption and stability of electronic equipment such as a smart phone, and a serious person can directly influence a user to operate the electronic equipment, so that the malicious keep-alive applications need to be identified, and the malicious keep-alive applications are correspondingly limited.
Disclosure of Invention
The embodiment of the application identification method and device, the storage medium and the electronic device can realize automatic identification of keep-alive application.
In a first aspect, an embodiment of the present application provides an application identification method, applied to an electronic device, including:
acquiring starting reason information of a started application;
and determining the started application of which the starting reason information meets the preset keep-alive condition as the keep-alive application.
In a second aspect, an application identification apparatus provided in an embodiment of the present application is applied to an electronic device, and includes:
the information acquisition module is used for acquiring the starting reason information of the started application;
and the application determining module is used for determining the started application of which the starting reason information meets the preset keep-alive condition as the keep-alive application.
In a third aspect, an embodiment of the present application provides a storage medium, on which a computer program is stored, and when the computer program is executed on a computer, the computer program is enabled to execute an application identification method provided by the embodiment of the present application.
In a fourth aspect, an embodiment of the present application further provides an electronic device, which includes a memory and a processor, where the processor is configured to execute the application identification method provided in the embodiment of the present application by calling a computer program stored in the memory.
In the embodiment of the application, the starting reason information of the started application is acquired; the started application of which the starting reason information meets the preset keep-alive condition is determined as the keep-alive application, so that the automatic identification of the keep-alive application can be realized.
Drawings
The technical solutions and advantages of the present application will become apparent from the following detailed description of specific embodiments of the present application when taken in conjunction with the accompanying drawings.
Fig. 1 is a schematic flowchart of an application identification method according to an embodiment of the present application.
Fig. 2 is a schematic view of a first scenario of an application identification method according to an embodiment of the present application.
Fig. 3 is a schematic diagram of a second scenario of an application identification method according to an embodiment of the present application.
Fig. 4 is a schematic diagram of a third scenario of an application identification method according to an embodiment of the present application.
Fig. 5 is a schematic diagram of a fourth scenario of an application identification method according to an embodiment of the present application.
Fig. 6 is a schematic structural diagram of an application identification device according to an embodiment of the present application.
Fig. 7 is a schematic structural diagram of a first electronic device according to an embodiment of the present application.
Fig. 8 is a schematic structural diagram of a second electronic device according to an embodiment of the present application.
Detailed Description
It should be noted that the terms "first", "second", and "third", etc. in this application are used to distinguish different objects, and are not used to describe a particular order. Furthermore, the terms "include" and "have," as well as any variations thereof, are intended to cover non-exclusive inclusions. For example, a process, method, system, article, or apparatus that comprises a list of steps or modules is not limited to only those steps or modules listed, but rather, some embodiments may include other steps or modules not listed or inherent to such process, method, article, or apparatus.
Reference herein to "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment can be included in at least one embodiment of the application. The appearances of the phrase in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. It is explicitly and implicitly understood by one skilled in the art that the embodiments described herein can be combined with other embodiments.
An embodiment of the present application provides an application identification method, an application identification apparatus, a storage medium, and an electronic device, where an execution subject of the application identification method may be the application identification apparatus provided in the embodiment of the present application, or the electronic device integrated with the application identification apparatus, where the application identification apparatus may be implemented in a hardware or software manner. The electronic device can be a smart phone, a tablet computer, a palm computer, a notebook computer and other devices which are provided with a processor and have application identification capability.
Referring to fig. 1, fig. 1 is a schematic flowchart of an application identification method provided in an embodiment of the present application, where the application identification method is applied to an electronic device, and the process may include:
in 101, start-up reason information of a started application is acquired.
Wherein the running of the application is originated from the starting of the application, and the starting of the application comprises the self-starting of the application and the active starting of the user. Whether the application is started automatically or started actively by the user, when the application is started, the application is the started application.
The start-up reason information of the started-up application describes a start-up reason of the started-up application. For example, if the start reason of a certain started application is self-starting after startup, the start reason information of the started application describes that the started application is self-starting after startup. For another example, if the start reason of a certain started application is user active start, the start reason information of the started application describes that the started application is user active start.
In this embodiment, the electronic device obtains start reason information of the started application to identify whether the started application is a keep-alive application based on the start reason information.
In 102, the started application with the start reason information meeting the preset keep-alive condition is determined as the keep-alive application.
The preset keep-alive condition is used for describing a specified condition which needs to be met by the starting reason information. And if the starting reason information of a certain started application meets the specified condition, determining that the started application is the keep-alive application. The preset keep-alive condition can be preset by a user or generated by the electronic equipment based on a certain rule.
The keep-alive application is a self-starting application, or an application started by a non-user actively, including a self-starting application, or an application pulled by other applications, that is, an application started by other applications. The keep-alive applications include malicious keep-alive applications and non-malicious keep-alive applications. A malicious keep-alive application is an application that is not self-launching authorized and self-launching by a user. A non-malicious keep-alive application is an application that is self-launching authorized and self-launching by a user.
And because the malicious keep-alive application can greatly affect the performance, power consumption and stability of electronic equipment such as a smart phone, after the malicious keep-alive application is identified, the electronic equipment can limit the malicious keep-alive application by adopting a corresponding strategy. And because the non-malicious keep-alive application is usually self-started under the condition that the user allows, the user can conveniently use the electronic equipment, and therefore, after the non-malicious keep-alive application is identified, the electronic equipment can limit the malicious keep-alive application without adopting a corresponding strategy.
In this embodiment, after the start reason information of the started application is acquired, the electronic device analyzes according to the start reason information of the started application to analyze whether the start reason information of the started application meets a preset keep-alive condition, and then the electronic device determines the started application of which the start reason information meets the preset keep-alive condition as the keep-alive application.
For example, it is assumed that the started applications include an application U1, an application U2, and an application U3, where the start reason information of the application U1 describes that the application U1 is self-started after being started, the start reason information of the application U2 describes that the application U2 is pulled up by the application U1, the start reason information of the application U3 describes that the application U3 is actively started by a user, and the preset keep-alive condition includes self-starting after being started, being pulled up by other applications, or being self-started after being cleaned up. The electronic device may determine that the start reason information of the application U1 and the application U2 satisfies the preset keep-alive condition, and the start reason information of the application U3 does not satisfy the preset keep-alive condition, then the electronic device determines that the application U1 and the application U2 are keep-alive applications, and the application U3 is not a keep-alive application.
And assuming that the start-up reason information of the application U1 describes that the application U1 does not perform power-on self-start authorization and self-starts after power-on, and the start-up reason information of the application U2 describes that the application U2 performs pull-up authorization by other applications and is pulled up by other applications, and the preset protection conditions include that the application U2 does not perform power-on self-start authorization and self-starts after power-on, is subjected to pull-up authorization by other applications and is pulled up by other applications, or is cleaned up and then starts up, the electronic device may determine that the application U1 is a malicious keep-alive application and the application U2 is a non-malicious keep-alive application.
In the embodiment, the starting reason information of the started application is acquired; the started application of which the starting reason information meets the preset keep-alive condition is determined as the keep-alive application, so that the automatic identification of the keep-alive application can be realized.
In an optional embodiment, before determining that the started application whose start reason information satisfies the preset keep-alive condition is the keep-alive application, the method further includes:
and if the starting reason information of the started application describes that the application is self-started after being started, determining that the starting reason information meets the preset keep-alive condition.
In this embodiment, the preset keep-alive condition may include self-starting after starting up, and then, if the start reason information of a certain started application describes that the application is self-started after starting up, the electronic device may determine that the start reason information of the started application satisfies the preset keep-alive condition.
It can be understood that some applications can be self-started by the user, so that the applications can be self-started after being started or when corresponding conditions are met, and the user is prevented from manually starting the applications after being started or when the corresponding conditions are met. For example, a user can perform startup self-starting authorization on commonly used applications, so that the applications subjected to the self-starting authorization can be automatically started after being started, and the user is prevented from manually starting the applications. In this embodiment, the preset keep-alive conditions may include that a self-start authorization is performed after the application is started and the application is self-started after the application is started, and if the start reason information of a certain started application describes that the application is self-started after the application is started and the application is self-started after the application is started, the electronic device may determine that the application is a non-malicious keep-alive application.
For example, assuming that the start reason information of the launched application U1 describes that it has been self-started after power-on authorization and self-started after power-on, the electronic device may determine that the launched application U1 is a non-malicious keep-alive application.
However, a part of the current application market exists that malicious applications utilize the mechanism design of the system itself to keep alive by continuously researching various keep-alive means. For example, one keep-alive method is: and on the premise that the user does not perform the power-on self-starting authorization, the system is automatically started after power-on. The keep-alive behavior has a great influence on the performance, power consumption and stability of electronic equipment such as a smart phone, and a serious person can directly influence a user to operate the electronic equipment, so that the malicious keep-alive applications need to be identified, and the malicious keep-alive applications are correspondingly limited. Based on this, the preset keep-alive conditions may include that the self-starting authorization is not performed after the electronic device is started, and the electronic device may determine that the electronic device is a non-malicious keep-alive application for the started application of which the start-up reason information describes that the self-starting authorization is not performed after the electronic device is started, and the started application is self-started after the electronic device is started. For example, assuming that the start reason information of the launched application U2 describes that it has not been self-started after power-on authorization and is self-started after power-on, the electronic device may determine that the launched application U2 is a malicious keep-alive application.
In an optional embodiment, before determining that the started application whose start reason information satisfies the preset keep-alive condition is the keep-alive application, the method further includes:
and if the starting reason information of the started application describes that the application is started automatically after being cleaned, determining that the starting reason information meets the preset keep-alive condition.
In this embodiment, the preset keep-alive condition may include self-starting after being cleaned, and then, if the start reason information of a certain started application describes that the application is self-started after being cleaned, the electronic device may determine that the start reason information of the started application meets the preset keep-alive condition.
It can be understood that some applications can be self-started by the user, so that the applications can be self-started after being started or when corresponding conditions are met, and the user is prevented from manually starting the applications after being started or when the corresponding conditions are met. For example, a user may perform self-starting authorization after cleaning a commonly used application, and when the cleaned application subjected to self-starting authorization is cleaned, the cleaned application subjected to self-starting authorization may be automatically started when the memory of the electronic device is sufficient to support the running of the cleaned application subjected to self-starting authorization, so as to prevent the user from manually starting the applications. In this embodiment, the preset keep-alive condition may include that the application is cleared and then self-started, and if the start reason information of a certain started application describes that the application is cleared and then self-started, the electronic device may determine that the application is a non-malicious keep-alive application.
For example, assuming that the launch cause information of the launched application U1 describes that it has been cleaned-up and self-launched, the electronic device may determine that the launched application U1 is a non-malicious keep-alive application.
Besides the malicious keep-alive mode of self-starting after starting on the premise that the user does not perform the start-up self-starting authorization, other malicious keep-alive modes also exist, for example, the method is applied to the premise that the user performs the self-starting authorization after being cleaned, and is self-started after being cleaned, for example, after being cleaned by the cleaning operation performed by the user. Based on this, the preset keep-alive condition may include that the started application is not cleared and then self-started, and the electronic device may determine that the started application is malicious keep-alive application, where the start reason information describes the started application which is not cleared and then self-started, and the self-start authorization is not cleared and then self-started after the clearing.
For example, assuming that the launch cause information of the launched application U2 describes that it has not been cleaned-up self-launch authorization and has been cleaned-up self-launch, the electronic device may determine that the launched application U2 is a malicious keep-alive application.
In an optional embodiment, before determining that the started application whose start reason information satisfies the preset keep-alive condition is the keep-alive application, the method further includes:
and if the starting reason information of the started application describes that the application is pulled up by other started applications, determining that the starting reason information meets the preset keep-alive condition.
In this embodiment, the preset keep-alive condition may include being pulled up by other started applications, and then, if the start reason information of a certain started application describes that the certain started application is started by other started applications, the electronic device may determine that the start reason information of the started application meets the preset keep-alive condition.
The fact that a certain started application is pulled up by other started applications means that a certain started application is started by other started applications.
It can be understood that, a user may authorize some applications to pull up other applications, for example, a game application needs an account of another instant messaging application to log in, when the game application logs in, if the instant messaging application is not started, the game application needs to start the instant messaging application, in order to avoid that the game application cannot log in, the user usually authorizes the game application to start the instant messaging application, that is, authorizes the game application to pull up the instant messaging application, and this behavior of authorizing an application to pull up other applications may be regarded as a non-malicious keep-alive behavior, therefore, in this embodiment, the preset keep-alive condition may include that the started application is pulled up by other started applications authorized to pull up the started application, if the start reason information of the started application describes that the started application is pulled up by other started applications authorized to pull up the started application, the electronic device can determine the launched application as a non-malicious keep-alive application.
For example, assuming that the launch cause information of the launched application U1 describes that it was pulled by the launched application U2 that authorized pulling thereof, the electronic device may determine that the launched application U1 is a non-malicious keep-alive application.
In addition to the malicious keep-alive methods, there may be other keep-alive methods, such as the application being automatically started by other started applications that are not authorized to pull it up. The preset keep-alive condition may include that the started application is pulled by other started applications not authorized to pull it, and for the started application pulled by other started applications not authorized to pull it, the electronic device may determine that it belongs to a malicious keep-alive application.
For example, assuming that the launch cause information of the launched application U3 describes that it was pulled by a launched application U4 that is not authorized to pull it, the electronic device may determine that the launched application U3 is a malicious keep-alive application.
In an optional embodiment, before acquiring the start reason information of the started application, the method further includes:
determining a related application related to the installed application, and installing the related application;
if the starting reason information of the started application describes that the application is pulled up by other started applications, determining that the starting reason information meets the preset keep-alive condition, wherein the steps comprise:
and if the starting reason information of the started application describes that the application is pulled up by the associated application, determining that the starting reason information meets the preset keep-alive condition.
Considering that the electronic device has limited storage space and cannot install all applications in the market at the same time, when identifying the keep-alive mode in which the started application is pulled up by other started applications, the electronic device may first determine the associated applications associated with the installed applications in the electronic device and install the associated applications to identify the keep-alive mode in which the started application is pulled up by other started applications, such as the associated applications associated therewith.
Wherein the associated applications associated with the installed applications include applications that have some association with the installed applications. For example, the associated application associated with the installed application may be an application that a user using the installed application is likely to use, or may be the same application as a developer of the installed application.
It can be understood that, if an application is an associated application associated with an installed application, the installed application is an application associated with the application, that is, the installed application is associated with the application.
For example, assuming that the installed applications in the electronic device include applications a1 and a2, where the associated applications of application a1 are applications A3 and a4, the associated applications of application a2 are applications A5 and A6, none of applications A3, a4, A5, and A6 are installed in the electronic device, the electronic device may install applications A3, a4, A5, and A6, and if the started application is application a1 whose start reason information describes that it is pulled by application A3, the electronic device may determine that application a1 is pulled by its associated application, so that the electronic device may determine that the start reason information of application a1 satisfies a preset keep-alive condition.
In an optional embodiment, determining an associated application associated with the installed application includes:
(1) acquiring user use behavior data;
(2) and determining an associated application associated with the installed application according to the user usage behavior data.
Wherein the user usage behavior data describes usage habits of the user using the application. For example, a user using the application U1 is likely to also use the application U2 and the application U3, and therefore, the application U1, the application U2 and the application U3 may serve as associated applications associated with each other, and then, when the application U1 is installed, the electronic device may install the application U2 and the application U3.
In an optional embodiment, determining an associated application associated with the installed application comprises:
(1) determining a developer of the installed application;
(2) an application of which the developer is the same as the developer of the installed application is determined as an associated application associated with the installed application.
Considering that mutual pull-up behaviors also exist between applications developed by the same developer, the electronic device can use the applications developed by the same developer as the associated applications, so that when the associated applications associated with the installed applications need to be installed, the developers of the installed applications are determined, and the applications of the developers, which are the same as the developers of the installed applications, are determined as the associated applications associated with the installed applications.
For example, assuming that the developer of the installed application U1 is developer D1, the developers of the uninstalled application U2 and the uninstalled application U3 are developer D1, the developer of the uninstalled application U4 is developer D2, and the developer of the uninstalled application U5 is developer D3, the electronic device may determine the uninstalled application U2 and the uninstalled application U3 as the associated application associated with the installed application U1.
In an optional embodiment, the correlated applications may also be determined directly when no application is installed in the electronic device, for example, by determining the correlated applications by a user using behavior data or a developer of the application, and installing the correlated applications. Then, the step of obtaining the starting reason information of the started application is executed.
In an optional embodiment, the application identification method further includes:
and if the started application is the application which is not cleaned up, determining the started application as the keep-alive application.
It will be appreciated that in addition to the malicious keep-alive approaches described above, there may be other malicious keep-alive approaches, such as applications that are not cleaned, e.g., cleaned by a cleaning operation. In this embodiment, the application is not cleaned up as a preset keep-alive condition, so that when a certain started application is not cleaned up, the electronic device can determine the started application as a keep-alive application, such as a malicious keep-alive application.
In an optional embodiment, the obtaining of the start reason information of the started application includes:
(1) acquiring a log of the electronic equipment;
(2) and analyzing the log of the electronic equipment to obtain the starting reason information of the started application.
The log of the electronic device records information of the electronic device in the operation process. For example, when an application generates a process, the log records application identification information (UID) of the application, process identification information (PID) of the process generated by the application, and corresponding start time, etc.
For example, as shown in fig. 2, the electronic device performs a restart operation after the application U1 is started to restart the electronic device. The electronic device obtains a log before the restart operation is performed, such as a log in a first preset time period before the restart operation is performed, and a log after the restart operation is performed, such as a log in a second preset time period after the restart operation is performed. The electronic device can determine, through analyzing the log, that the application U1 with UID 0001 reactivates its own process after the process P1 with PID 001 and the process P2 with PID 002 die due to the restart of the electronic device, which means that the processes P1 and P2 of the application U1 with UID 0001 are still alive after the electronic device is turned on, but the PID changes, that is, the PID of the process P1 becomes 003, and the PID of the process P2 becomes 004. Based on the above analysis, the electronic device may determine that the start-up reason information of the application U1 describes that the application U1 starts itself after being powered on.
For another example, as shown in fig. 3, the electronic device obtains a log during the running of the started application U1. The electronic device can determine, by analyzing the log, that the user does not perform an operation of starting the application U2 with UID of 0002, but the application U1 with UID of 0001 pulls up the process P3 with PID of 005 and the process P4 with PID of 006 of the application U2 with UID of 0002. Based on the above analysis, the electronic device may determine that the start reason information for application U2 describes that application U2 is pulled up by application U1.
For another example, as shown in fig. 4, the electronic device performs a cleaning operation after launching the application U1 to clean the application U1. The electronic device obtains a log before the cleaning operation is performed, such as a log in a third preset time period before the cleaning operation is performed, and a log after the cleaning operation is performed, such as a log in a fourth preset time period after the cleaning operation is performed. The electronic device can determine, by analyzing the log, that the application U1 with UID 0001 reactivates its own process after the process P1 with PID 001 and the process P2 with PID 002 are cleaned by the cleaning operation, and that the processes P1 and P2 of the application U1 with UID 0001 after cleaning are still alive, but the PID changes, that is, the PID of the process P1 becomes 003, and the PID of the process P2 becomes 004. Based on the above analysis, the electronic device may determine that the launch reason information for application U1 describes that application U1 self-launches after being cleaned.
In an alternative embodiment, as shown in FIG. 5, the electronic device performs a cleanup operation after launching application U1 to clean application U1. The electronic device obtains a log before the cleaning operation is performed, such as a log in a fifth preset time period before the cleaning operation is performed, and a log after the cleaning operation is performed, such as a log in a sixth preset time period after the cleaning operation is performed. By analyzing the log, the electronic device can determine that the processes under the application U1 with UID 0001 are not cleaned up by the cleaning operation, that the processes P1 and P2 of the application U1 with UID 0001 after cleaning are still in a survival state, and that the PID is not changed, that is, the PID of the process P1 is still 001, and the PID of the process P2 is still 002. Based on the analysis, the electronic device can determine that application U1 is an application that is not cleaned up by the clean-up operation, and then the electronic device can determine that the application UI is a keep-alive application, such as a malicious keep-alive application.
It should be noted that the first preset time period, the second preset time period, the third preset time period, the fourth preset time period, the fifth preset time period, and the sixth preset time period may be the same or different.
In an optional embodiment, after determining, as the keep-alive application, the started application whose start reason information satisfies the preset keep-alive condition, the method further includes:
(1) determining a keep-alive limiting strategy corresponding to the keep-alive application according to the starting reason information of the keep-alive application;
(2) and limiting keep-alive application keep-alive according to the limit keep-alive strategy.
It can be understood that, because malicious keep-alive behaviors will have a great influence on performance, power consumption and stability of electronic devices such as smart phones, and a serious person can also directly influence users to operate the electronic devices, such malicious keep-alive applications need to be identified, so as to correspondingly limit the malicious keep-alive applications.
For example, a developer can analyze different preset keep-alive conditions to determine a keep-alive limiting strategy for the different preset keep-alive conditions, and then, when the start reason information of the keep-alive application meets the corresponding preset keep-alive conditions, the electronic device can determine the keep-alive limiting strategy corresponding to the preset keep-alive conditions, and limit the keep-alive application keep-alive according to the keep-alive limiting strategy.
For example, if the preset keep-alive condition is that the power-on self-start authorization is not performed and the corresponding limit keep-alive policy S1 is self-started after power-on, the preset keep-alive condition is that the self-start authorization is not performed and the corresponding limit keep-alive policy S2 is self-started after cleaning is performed, the preset keep-alive condition is that the corresponding limit keep-alive condition S3 is pulled up by other started applications not authorized to pull up the keep-alive application, the start reason information of the keep-alive application U1 is that the self-start authorization is not performed and the keep-alive application U2 is self-started after power-on, and the start reason information of the keep-alive application U2 is pulled up by other started applications not authorized to pull up the keep-alive application U1, the electronic device may limit the keep-alive application U1 according to the limit keep-alive policy S1, and limit the keep-alive application U2 to keep-alive according to the limit keep-alive policy S3.
It can be understood that after the keep-alive application is limited to keep alive according to the keep-alive limitation strategy, the electronic device can further continue to identify the keep-alive application, that is, determine whether the start reason information of the keep-alive application still meets the preset keep-alive condition. If the start reason information of the keep-alive application still meets the preset keep-alive condition, the limitation keep-alive strategy can be determined to be not complete enough, and then the corresponding information can be reported, so that developers can update the limitation keep-alive strategy, and after the updated limitation keep-alive strategy is used for limiting the keep-alive application to keep alive, the start reason information of the keep-alive application can be successfully prevented from meeting the preset keep-alive condition.
In an optional embodiment, for the identified keep-alive application which is not cleaned by the cleaning operation, a corresponding keep-alive limitation strategy can be determined by a developer, so that the electronic device can limit keep-alive of the keep-alive application according to the keep-alive limitation strategy.
In an optional embodiment, in a test stage before the electronic device is shipped, the keep-alive application, such as malicious keep-alive application, is identified by the application identification method provided by the embodiment of the application, so that a corresponding keep-alive limiting strategy is proposed in advance to limit keep-alive of the keep-alive application, and the probability of the problem appearing on the hands of the user is reduced. In addition, at this stage, after the keep-alive application is limited to keep alive by the corresponding keep-alive strategy, the keep-alive application is continuously identified by the application identification method provided by the embodiment of the application, so as to determine whether the keep-alive application limited by the keep-alive strategy is still the keep-alive application. If the application is still the keep-alive application, the keep-alive limiting strategy can be optimized, and then the keep-alive application is continuously limited through the optimized keep-alive limiting strategy until the application is identified not to be the keep-alive application through the application identification method provided by the embodiment of the application.
Specifically, for a scenario that is not subject to self-starting authorization and is self-started after startup, a specific test process is as follows:
firstly, all applications of a software store or TOP5000 applications are acquired and installed in the test equipment, and considering the limited storage space of the test equipment, the installation test can be carried out in batches, for example, only 50 applications are installed at a time for testing until all the applications are tested. For the application installed in the electronic device, since the application has some service protocols/privacy protocols to be authorized, and additionally, the authority of some systems, such as an Android system and an IOS system, can be asked for, otherwise, the application cannot run, and if the application is in an un-started state after installation, the application is self-started through the system, so that a click is necessary, and a developer can click to start the application to complete the authorization. Subsequently, a restart operation may be performed. Because the keep-alive modes of different applications are different, the starting time after the startup is also different, and therefore, the specified time can be waited. And the electronic equipment acquires the log of the whole process and records the screen of the whole process. The electronic device may analyze the obtained log, and specifically includes: obtaining UID applied in the log; acquiring a time point of restarting operation in a log; and checking whether the UID is started in a process within a specified time after the restart operation is completed in the log, if so, determining that the application corresponding to the UID is a keep-alive application, and generating an application keep-alive report according to the log of the whole process and the screen recording of the whole process.
For the self-starting scene after the application is cleaned, the specific test process is as follows:
firstly, all applications of a software store or TOP5000 applications are acquired and installed in the testing equipment, and the installation test can be carried out in batches considering the limited storage space of the testing equipment, for example, only 50 applications are installed at one time for testing until all the applications are tested. For the application installed in the electronic device, since the application has some service protocols/privacy protocols to be authorized, and additionally, the permission of some systems, such as an Android system and an IOS system, can be requested, otherwise, the application cannot run, and if the application is in a state of never starting after installation, the application is self-started through the system, so that the click is necessary, and therefore, a developer can click to start the application to complete the authorization. Subsequently, random simulation operation, that is, operations of clicking, browsing, inputting and the like of the real user operation application can be executed. Then, a cleaning operation is performed on the started application in an attempt to kill the application process. Because the keep-alive modes of different applications are different, some applications are started immediately after the process is killed, and some applications may be started after a few minutes, so that the application can wait for a specified time. And the electronic equipment acquires the log of the whole process and records the screen of the whole process. The electronic device may analyze the obtained log, and specifically includes: obtaining UID applied in the log; acquiring a time point of cleaning operation in a log; and checking whether the UID is started in a process within a specified time after the cleaning operation is finished in the log, if so, determining that the application corresponding to the UID is a keep-alive application, and generating an application keep-alive report according to the log of the whole process and the screen recording of the whole process.
For the scenario where the application is pulled up by association, the specific test procedure is as follows:
firstly, all applications of a software store or TOP5000 applications are acquired and installed in the testing equipment, and the installation test can be carried out in batches considering the limited storage space of the testing equipment, for example, only 50 applications are installed at one time for testing until all the applications are tested. Since the scenario of association pull-up needs to be tested, all applications of the software store or TOP5000 applications can be arranged and combined to be combined into a plurality of groups for installation testing. Alternatively, a portion of the applications may be randomly selected for installation testing. Or, corresponding rules can be established to determine some interrelated applications to perform installation tests. First, a cleanup operation may be performed to clean up the unrelated application process. For the application installed in the electronic device, since the application has some service protocols/privacy protocols to be authorized, and additionally, the permission of some systems, such as an Android system and an IOS system, can be requested, otherwise, the application cannot run, and if the application is in a state of never starting after installation, the application is self-started through the system, so that the click is necessary, and developers can click to start the application to complete the authorization. Subsequently, random simulation operation, that is, operations of clicking, browsing, inputting and the like of the real user operation application can be executed. Due to different keep-alive modes of different applications, the specified time can be waited. And the electronic equipment acquires the log of the whole process and records the screen of the whole process. The electronic device may analyze the obtained log, and specifically includes: obtaining UID applied in the log; and checking whether a certain UID is pulled up by another UID in the log, if so, determining that the application corresponding to the UID is a keep-alive application, and generating an application keep-alive report according to the log of the whole process and the screen recording of the whole process.
And presenting all the application keep-alive reports to developers, and reserving on-site test equipment so that the developers have enough information to analyze keep-alive behaviors, such as malicious keep-alive behaviors. Moreover, a precondition can be preset, a debugging log is added, more information is acquired, and the problem positioning of developers is helped to the greatest extent.
Referring to fig. 6, fig. 6 is a schematic structural diagram of an application identification device according to an embodiment of the present application. The application recognition apparatus 200 is applied to an electronic device, and the application recognition apparatus 200 includes: an information acquisition module 201 and an application identification module 202.
An information obtaining module 201, configured to obtain start reason information of a started application.
An application determining module 202, configured to determine a started application for which the start reason information meets a preset keep-alive condition as a keep-alive application.
In an alternative embodiment, the application determination module 202 may be configured to: and if the starting reason information of the started application describes that the application is self-started after being started, determining that the starting reason information meets the preset keep-alive condition.
In an alternative embodiment, the application determination module 202 may be configured to: and if the starting reason information of the started application describes that the application is started automatically after being cleaned, determining that the starting reason information meets the preset keep-alive condition.
In an alternative embodiment, the application determining module 202 may be configured to: and if the starting reason information of the started application describes that the application is pulled up by other started applications, determining that the starting reason information meets the preset keep-alive condition.
In an optional embodiment, the application identification apparatus may further include an application installation module, and the application installation module may be configured to: determining a related application related to the installed application, and installing the related application;
an application determination module 202, which may be configured to: and if the starting reason information of the started application describes that the application is pulled up by the associated application, determining that the starting reason information meets the preset keep-alive condition.
In an alternative embodiment, the application installation module may be configured to: acquiring user use behavior data; and determining an associated application associated with the installed application according to the user usage behavior data.
In an alternative embodiment, the application installation module may be configured to: determining a developer of the installed application; an application of which the developer is the same as the developer of the installed application is determined as an associated application associated with the installed application.
In an optional embodiment, the information obtaining module 201 may be configured to: acquiring a log of the electronic equipment; and analyzing the log of the electronic equipment to obtain the starting reason information of the started application.
In an alternative embodiment, the application identification module 202 may be configured to: and if the started application is the application which is not cleaned up, determining the started application as the keep-alive application.
In an optional embodiment, the application identification apparatus may further include a limit keep-alive module, where the limit keep-alive module may be configured to: determining a keep-alive limitation strategy corresponding to the keep-alive application according to the starting reason information of the keep-alive application; and limiting keep-alive application keep-alive according to the keep-alive limiting strategy.
The embodiment of the present application provides a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed on a computer, the computer is caused to execute the application identification method provided in the embodiment.
The embodiment of the present application further provides an electronic device, which includes a memory and a processor, where the processor is configured to execute the application identification method provided in the embodiment by calling a computer program stored in the memory.
For example, the electronic device may be a mobile terminal such as a tablet computer or a smart phone. Referring to fig. 7, fig. 7 is a schematic structural diagram of an electronic device according to an embodiment of the present disclosure.
The electronic device 300 may comprise a processor 301, a memory 302, etc. Those skilled in the art will appreciate that the electronic device configuration shown in fig. 7 does not constitute a limitation of the electronic device and may include more or fewer components than shown, or some components may be combined, or a different arrangement of components.
The processor 301 is a control center of the electronic device, connects various parts of the entire electronic device using various interfaces and lines, performs various functions of the electronic device and processes data by running or executing an application program stored in the memory 302 and calling data stored in the memory 302, thereby integrally monitoring the electronic device.
The memory 302 may be used to store applications and data. The memory 302 stores applications containing executable code. The application programs may constitute various functional modules. The processor 301 executes various functional applications and data processing by running an application program stored in the memory 302.
In this embodiment, the processor 301 in the electronic device loads the executable code corresponding to the processes of one or more application programs into the memory 302 according to the following instructions, and the processor 301 runs the application programs stored in the memory 302, thereby implementing the following processes:
acquiring starting reason information of a started application;
and determining the started application of which the starting reason information meets the preset keep-alive condition as the keep-alive application.
Referring to fig. 8, the electronic device 300 may include a processor 301, a memory 302, an input unit 303, an output unit 304, and the like.
The processor 301 is a control center of the electronic device, connects various parts of the whole electronic device by using various interfaces and lines, and performs various functions of the electronic device and processes data by running or executing an application program stored in the memory 302 and calling the data stored in the memory 302, thereby performing overall monitoring of the electronic device.
The memory 302 may be used to store applications and data. The memory 302 stores applications containing executable code. The application programs may constitute various functional modules. The processor 301 executes various functional applications and data processing by running an application program stored in the memory 302.
The input unit 303 may be used to receive input numbers, character information, or user characteristic information, such as a fingerprint, and generate a keyboard, mouse, joystick, optical, or trackball signal input related to user setting and function control.
The output unit 304 may be used to display information input by or provided to a user and various graphical user interfaces of the electronic device, which may be made up of graphics, text, icons, video, and any combination thereof. The output unit may include a display screen, and the display screen may include a display area.
In this embodiment, the processor 301 in the electronic device loads the executable code corresponding to the processes of one or more application programs into the memory 302 according to the following instructions, and the processor 301 runs the application programs stored in the memory 302, thereby implementing the following processes:
acquiring starting reason information of a started application;
and determining the started application of which the starting reason information meets the preset keep-alive condition as the keep-alive application.
In an optional embodiment, before the processor 301 determines the started application with the start reason information satisfying the preset keep-alive condition as the keep-alive application, it may further perform: and if the starting reason information of the started application describes that the application is self-started after being started, determining that the starting reason information meets the preset keep-alive condition.
In an optional embodiment, before the processor 301 determines the started application with the start reason information satisfying the preset keep-alive condition as the keep-alive application, it may further perform: and if the starting reason information of the started application describes that the application is started automatically after being cleaned, determining that the starting reason information meets the preset keep-alive condition.
In an optional embodiment, before the processor 301 determines the started application with the start reason information satisfying the preset keep-alive condition as the keep-alive application, it may further perform: and if the starting reason information of the started application describes that the application is pulled up by other started applications, determining that the starting reason information meets the preset keep-alive condition.
In an optional embodiment, before the processor 301 obtains the start reason information of the started application, it may further perform: determining an associated application associated with the installed application, and installing the associated application; the processor 301 may execute, if the start reason information of the started application describes that the started application is pulled up by other started applications, when determining that the start reason information satisfies the preset keep-alive condition: and if the starting reason information of the started application describes that the application is pulled up by the associated application, determining that the starting reason information meets the preset keep-alive condition.
In an alternative embodiment, when the processor 301 executes the determination of the associated application associated with the installed application, it may execute: acquiring user use behavior data; and determining an associated application associated with the installed application according to the user usage behavior data.
In an alternative embodiment, when the processor 301 executes the determination of the associated application associated with the installed application, it may execute: determining a developer of the installed application; an application of which the developer is the same as the developer of the installed application is determined as an associated application associated with the installed application.
In an alternative embodiment, when the processor 301 obtains the start reason information of the started application, it may perform: acquiring a log of the electronic equipment; and analyzing the log of the electronic equipment to obtain the starting reason information of the started application.
In an alternative embodiment, the processor 301 may further perform: and if the started application is the application which is not cleaned up, determining the started application as the keep-alive application.
In an optional embodiment, after the processor 301 determines the started application with the start reason information satisfying the preset keep-alive condition as the keep-alive application, it may further perform: determining a keep-alive limitation strategy corresponding to the keep-alive application according to the starting reason information of the keep-alive application; and limiting keep-alive application keep-alive according to the keep-alive limiting strategy.
In the above embodiments, the descriptions of the embodiments have respective emphasis, and parts that are not described in detail in a certain embodiment may refer to the above detailed description of the application identification method, and are not described herein again.
The application identification device provided in the embodiment of the present application and the application identification method in the above embodiments belong to the same concept, and any method provided in the embodiment of the application identification method can be run on the application identification device, and the specific implementation process thereof is described in detail in the embodiment of the application identification method, and is not described herein again.
It should be noted that, for the application identification method in the embodiment of the present application, it can be understood by those skilled in the art that all or part of the process for implementing the application identification method in the embodiment of the present application can be completed by controlling the relevant hardware through a computer program, the computer program can be stored in a computer readable storage medium, such as a memory, and executed by at least one processor, and during the execution process, the process of the embodiment of the application identification method can be included. The storage medium may be a magnetic disk, an optical disk, a Read Only Memory (ROM), a random access Memory (RUM), etc.
It is understood that in the specific implementation of the present application, user information, such as user usage behavior data, logs and other related data, needs to be approved or approved by the user when the above embodiments of the present application are applied to specific products or technologies, and the collection, usage and processing of the related data need to comply with relevant laws and regulations and standards of relevant countries and regions.
In the application identification device according to the embodiment of the present application, each functional module may be integrated into one processing chip, or each module may exist alone physically, or two or more modules are integrated into one module. The integrated module can be realized in a hardware mode, and can also be realized in a software functional module mode. The integrated module, if implemented in the form of a software functional module and sold or used as a separate product, may also be stored in a computer-readable storage medium, such as a read-only memory, a magnetic disk or an optical disk.
The application identification method, the application identification device, the storage medium and the electronic device provided by the embodiments of the present application are described in detail above, and a specific example is applied in the present application to explain the principle and the implementation of the present application, and the description of the above embodiments is only used to help understand the method and the core idea of the present application; meanwhile, for those skilled in the art, according to the idea of the present application, there may be variations in the specific embodiments and the application scope, and in summary, the content of the present specification should not be construed as a limitation to the present application.
Claims (13)
1. An application identification method applied to electronic equipment is characterized by comprising the following steps:
acquiring starting reason information of a started application;
and determining the started application of which the starting reason information meets the preset keep-alive condition as the keep-alive application.
2. The application identification method according to claim 1, wherein before determining the started application whose start reason information satisfies the preset keep-alive condition as a keep-alive application, the method further comprises:
and if the starting reason information of the started application describes self-starting after starting, determining that the starting reason information meets the preset keep-alive condition.
3. The application identification method according to claim 1, wherein before determining the started application whose start reason information satisfies the preset keep-alive condition as a keep-alive application, the method further comprises:
and if the starting reason information of the started application describes that the application is started automatically after being cleaned, determining that the starting reason information meets a preset keep-alive condition.
4. The application identification method according to claim 1, wherein before determining the started application whose start reason information satisfies the preset keep-alive condition as a keep-alive application, the method further comprises:
and if the starting reason information of the started application describes that the application is pulled up by other started applications, determining that the starting reason information meets a preset keep-alive condition.
5. The application identification method according to claim 4, wherein before the obtaining of the start reason information of the started application, the method further comprises:
determining an associated application associated with the installed application and installing the associated application;
if the starting reason information of the started application describes that the started application is pulled up by other started applications, determining that the starting reason information meets the preset keep-alive condition comprises the following steps:
and if the starting reason information of the started application describes that the starting reason information is pulled up by the associated application, determining that the starting reason information meets the preset keep-alive condition.
6. The application identification method according to claim 5, wherein the determining the associated application associated with the installed application comprises:
acquiring user use behavior data;
and determining the associated application associated with the installed application according to the user usage behavior data.
7. The application identification method according to claim 5, wherein the determining the associated application associated with the installed application comprises:
determining a developer of the installed application;
determining an application having a developer that is the same as a developer of the installed application as an associated application associated with the installed application.
8. The application identification method according to claim 1, wherein the obtaining of the start reason information of the started application comprises:
acquiring a log of the electronic equipment;
and analyzing the log of the electronic equipment to obtain the starting reason information of the started application.
9. The application identification method of claim 1, further comprising:
and if the started application is the application which is not cleaned up, determining the started application as the keep-alive application.
10. The application identification method according to any one of claims 1 to 9, wherein after determining the started application whose start reason information satisfies the preset keep-alive condition as a keep-alive application, the method further comprises:
determining a keep-alive limiting strategy corresponding to the keep-alive application according to the starting reason information of the keep-alive application;
and limiting the keep-alive application keep-alive according to the limit keep-alive strategy.
11. An application recognition apparatus applied to an electronic device, comprising:
the information acquisition module is used for acquiring the starting reason information of the started application;
and the application determining module is used for determining the started application of which the starting reason information meets the preset keep-alive condition as the keep-alive application.
12. A storage medium having stored therein a computer program which, when run on a computer, causes the computer to execute the application recognition method of any one of claims 1 to 10.
13. An electronic device, characterized in that the electronic device comprises a processor and a memory, wherein the memory stores a computer program, and the processor is used for executing the application recognition method according to any one of claims 1 to 10 by calling the computer program stored in the memory.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210745104.XA CN115033305A (en) | 2022-06-27 | 2022-06-27 | Application identification method and device, storage medium and electronic equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210745104.XA CN115033305A (en) | 2022-06-27 | 2022-06-27 | Application identification method and device, storage medium and electronic equipment |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN115033305A true CN115033305A (en) | 2022-09-09 |
Family
ID=83127441
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210745104.XA Pending CN115033305A (en) | 2022-06-27 | 2022-06-27 | Application identification method and device, storage medium and electronic equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115033305A (en) |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107748698A (en) * | 2017-11-21 | 2018-03-02 | 广东欧珀移动通信有限公司 | Start control method, device, storage medium and the terminal of application with broadcast mode |
| CN107861773A (en) * | 2017-11-21 | 2018-03-30 | 广东欧珀移动通信有限公司 | Associate management-control method, device, storage medium and the mobile terminal started |
| CN110895473A (en) * | 2018-08-24 | 2020-03-20 | 山东华软金盾软件股份有限公司 | Self-starting keep-alive system and method based on android mobile device |
| CN111783090A (en) * | 2020-06-08 | 2020-10-16 | Oppo广东移动通信有限公司 | Information processing method and device, equipment and storage medium |
| CN112307465A (en) * | 2020-10-30 | 2021-02-02 | 上海中通吉网络技术有限公司 | Keep-alive pull-alive method, storage medium and equipment for coping with application program being checked and killed |
| CN113885944A (en) * | 2021-08-25 | 2022-01-04 | 荣耀终端有限公司 | Application background keep-alive method and device and electronic equipment |
| CN114168212A (en) * | 2020-09-09 | 2022-03-11 | 成都鼎桥通信技术有限公司 | Application processing method, device, equipment and computer readable storage medium |
-
2022
- 2022-06-27 CN CN202210745104.XA patent/CN115033305A/en active Pending
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107748698A (en) * | 2017-11-21 | 2018-03-02 | 广东欧珀移动通信有限公司 | Start control method, device, storage medium and the terminal of application with broadcast mode |
| CN107861773A (en) * | 2017-11-21 | 2018-03-30 | 广东欧珀移动通信有限公司 | Associate management-control method, device, storage medium and the mobile terminal started |
| CN110895473A (en) * | 2018-08-24 | 2020-03-20 | 山东华软金盾软件股份有限公司 | Self-starting keep-alive system and method based on android mobile device |
| CN111783090A (en) * | 2020-06-08 | 2020-10-16 | Oppo广东移动通信有限公司 | Information processing method and device, equipment and storage medium |
| CN114168212A (en) * | 2020-09-09 | 2022-03-11 | 成都鼎桥通信技术有限公司 | Application processing method, device, equipment and computer readable storage medium |
| CN112307465A (en) * | 2020-10-30 | 2021-02-02 | 上海中通吉网络技术有限公司 | Keep-alive pull-alive method, storage medium and equipment for coping with application program being checked and killed |
| CN113885944A (en) * | 2021-08-25 | 2022-01-04 | 荣耀终端有限公司 | Application background keep-alive method and device and electronic equipment |
Non-Patent Citations (1)
| Title |
|---|
| 中国信通院 等: "软件开发包（SDK）安全研究报告", pages 34 - 37, Retrieved from the Internet <URL:https://pdf.dfcfw.com/pdf/H3_AP202112291537269543_1.pdf?1640772050000.pdf> * |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109542744B (en) | Method, device, storage medium and terminal for detecting abnormal starting problem of terminal | |
| CN109522147A (en) | A kind of method, apparatus, storage medium and the terminal of record booting exception information | |
| US7721331B1 (en) | Methods and apparatus for performing a pre-processing activity | |
| US20060259819A1 (en) | Automated Method for Self-Sustaining Computer Security | |
| JP2007316637A (en) | Screensaver for individual application program | |
| US8781985B2 (en) | Addressing system degradation by application disabling | |
| CN111782416A (en) | Data reporting method, device, system, terminal and computer readable storage medium | |
| KR20110128632A (en) | Method and device for detecting malicious action of application program for smartphone | |
| CN113177001A (en) | Vulnerability detection method and device for open source component | |
| CN108563472B (en) | Service plug-in loading method and device based on multi-open application | |
| US10318731B2 (en) | Detection system and detection method | |
| CN113467981A (en) | Exception handling method and device | |
| CN113626276B (en) | Method, system, terminal and storage medium for identifying type of server HBA card | |
| CN112182581B (en) | Application testing method, device, application testing equipment and storage medium | |
| CN106802821B (en) | Method and device for identifying installation source of application program | |
| CN115913913B (en) | Network card pre-starting execution environment function fault positioning method and device | |
| CN109634782B (en) | Method and device for detecting system robustness, storage medium and terminal | |
| CN111783090A (en) | Information processing method and device, equipment and storage medium | |
| CN105809027B (en) | Permission control method and device for application program | |
| CN115033305A (en) | Application identification method and device, storage medium and electronic equipment | |
| CN111062035A (en) | Lesog software detection method and device, electronic equipment and storage medium | |
| CN115951947A (en) | Information interaction method and device and storage medium | |
| Johnson et al. | Dazed droids: A longitudinal study of android inter-app vulnerabilities | |
| CN104572199B (en) | The method and apparatus that a kind of No starting item starts | |
| CN108875371B (en) | Sandbox analysis method and device, electronic equipment and 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 |