CN112307465A - Keep-alive pull-alive method, storage medium and equipment for coping with application program being checked and killed - Google Patents
Keep-alive pull-alive method, storage medium and equipment for coping with application program being checked and killed Download PDFInfo
- Publication number
- CN112307465A CN112307465A CN202011194366.9A CN202011194366A CN112307465A CN 112307465 A CN112307465 A CN 112307465A CN 202011194366 A CN202011194366 A CN 202011194366A CN 112307465 A CN112307465 A CN 112307465A
- Authority
- CN
- China
- Prior art keywords
- application program
- killed
- alive
- background
- service process
- 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 149
- 230000010485 coping Effects 0.000 title claims abstract description 11
- 230000008569 process Effects 0.000 claims abstract description 114
- 230000000694 effects Effects 0.000 claims abstract description 28
- 238000004891 communication Methods 0.000 claims description 3
- 238000004590 computer program Methods 0.000 claims description 3
- 230000004044 response Effects 0.000 claims description 2
- 230000006870 function Effects 0.000 description 4
- 238000011161 development Methods 0.000 description 2
- 238000010586 diagram Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 230000004075 alteration Effects 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 230000004083 survival effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/50—Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems
- G06F21/51—Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems at application loading time, e.g. accepting, rejecting, starting or inhibiting executable software based on integrity or source reliability
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/50—Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems
- G06F21/52—Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems during program execution, e.g. stack integrity ; Preventing unwanted data erasure; Buffer overflow
- G06F21/54—Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems during program execution, e.g. stack integrity ; Preventing unwanted data erasure; Buffer overflow by adding security routines or objects to programs
Abstract
The application relates to a keep-alive pull-alive method, a storage medium and equipment for coping with the condition that an application program is killed, wherein when the application program is started, a working service is started, a task manager is registered on the equipment carried by the application program, and a daemon process is started. Because the daemon process at least comprises two mutually protected processes, the mutually protected processes can be mutually activated, when one daemon process is killed, the rest daemon processes activate the killed daemon process, and the daemon process is ensured not to be completely killed. On the premise that the daemon process normally runs, whether the application program is checked and killed is detected through the daemon process, and when the application program is checked and killed, the application program is restarted through the daemon process, so that the keep-alive pull-alive of the application program is achieved. In the application, the application program is kept alive and pulled alive by setting two mutually protected processes, so that the effect of preventing the application program from being checked and killed is better.
Description
Technical Field
The present application relates to the field of application program live-live technologies, and in particular, to a live-live-live method, a storage medium, and a device for coping with an application program being killed.
Background
With the development of science and technology and the development of services, various applications are more and more installed on various devices, but when the applications run in the background, the applications are exposed to the risk of being maliciously killed and killed by a system or a third party application, so that the stable running of the applications is influenced.
Disclosure of Invention
To overcome the problems in the related art at least to some extent, the present application provides a keep-alive method, a storage medium, and a device for responding to an application program being killed.
The scheme of the application is as follows:
according to a first aspect of the embodiments of the present application, there is provided a keep-alive pull-alive method for dealing with an application program being killed, including:
starting a work service when an application program is started, and registering a task manager on equipment carried by the application program;
starting a daemon process; the daemon process at least comprises two mutually protected processes;
and detecting whether the application program is checked and killed through the daemon process, and restarting the application program through the daemon process when the application program is checked and killed.
Preferably, in an implementation manner of the present application, the method further includes:
simultaneously starting a local service process and a remote service process, and binding the local service process and the remote service process as the daemon process to enable the local service process and the remote service process to monitor each other; wherein: the local service process is loaded on the equipment and used for maintaining the local running of the application program; and the remote service process is loaded on a remote server.
Preferably, in an implementation manner of the present application, the method further includes:
when the local service process is checked and killed, restarting the local service process through the remote service process; and when the remote service process is killed, restarting the remote service process through the local service process.
Preferably, in an implementation manner of the present application, the method further includes:
and detecting whether the application program runs in a background or not, and maintaining the activity of the application program through a pre-established background normally-open process when the application program runs in the background.
Preferably, in an implementable manner of the present application, the maintaining of the activity of the application program through a pre-established background always-on process specifically includes:
detecting whether the equipment is turned off;
when the device is turned off and the application program is in background running, playing silent background music to maintain the activity of the application program;
when the device does not screen off and the application program runs in the background, playing the silent background music to maintain the activity of the application program;
and when the device does not screen off and the application program is not in background running, stopping playing the silent background music.
Preferably, in an implementation manner of the present application, the maintaining the activity of the application program through a pre-established background always-on process specifically further includes:
when the device is turned off and the application program runs in the background, displaying an active window with preset pixels on a notification bar to maintain the activity of the application program;
when the device is not stopped and the application program is in background operation, displaying the active window of preset pixels on a notification bar to maintain the activity of the application program;
and stopping displaying the active window on a notification bar when the device is not turned off and the application program is not in background running.
Preferably, in an implementable manner of the present application, the predetermined pixel is 1 pixel.
Preferably, in an implementation manner of the present application, the detecting whether the application is killed or not by using a pre-established daemon process specifically includes:
and when receiving the broadcast sent before the application program is killed and closed through a pre-established daemon process, judging that the application program is killed.
According to a second aspect of embodiments of the present application, there is provided a storage medium storing a computer program which, when executed by a processor, implements a keep-alive pull-alive method for coping with an application program being killed as described in any one of the above.
According to a third aspect of the embodiments of the present application, there is provided a keep-alive pull-alive device for dealing with application program being killed, including:
a processor and a memory;
the processor and the memory are connected through a communication bus:
the processor is used for calling and executing the program stored in the memory;
the memory is used for storing a program, and the program is at least used for executing the keep-alive pull-alive method for coping with the application program being killed in any one of the above ways.
The technical scheme provided by the application can comprise the following beneficial effects: in the application, when the application program is started, the work service is started, the task manager is registered on the equipment carried by the application program, and the daemon process is started. Because the daemon process at least comprises two mutually protected processes, the mutually protected processes can be mutually activated, when one daemon process is killed, the rest daemon processes activate the killed daemon process, and the daemon process is ensured not to be completely killed. On the premise that the daemon process normally runs, whether the application program is checked and killed is detected through the daemon process, and when the application program is checked and killed, the application program is restarted through the daemon process, so that the keep-alive pull-alive of the application program is achieved. In the application, the application program is kept alive and pulled alive by setting two mutually protected processes, so that the effect of preventing the application program from being checked and killed is better.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the application.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and together with the description, serve to explain the principles of the application.
Fig. 1 is a flowchart illustrating a keep-alive pull-alive method for dealing with an application program being killed according to an embodiment of the present application;
FIG. 2 is a flowchart illustrating a keep-alive pull method for responding to an application program being killed according to another embodiment of the present application;
fig. 3 is a schematic diagram of a specific manner of maintaining the activity of an application program through a pre-established background always-on process according to an embodiment of the present application.
Fig. 4 is a schematic structural diagram of a keep-alive pull-alive device for dealing with application program being killed according to an embodiment of the present application.
Reference numerals: a processor-21; a memory-22.
Detailed Description
Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present application, as detailed in the appended claims.
Fig. 1 is a schematic flowchart of a keep-alive pull method for responding to an application program being killed according to an embodiment of the present application, and referring to fig. 1, a keep-alive pull method for responding to an application program being killed includes:
s11: starting a work service when an application program is started, and registering a task manager on equipment carried by the application program;
s12: starting a daemon process; the daemon process at least comprises two mutually protected processes;
the starting of the daemon process specifically comprises the following steps: simultaneously starting a local service process and a remote service process, and binding the local service process and the remote service process as a daemon process to enable the local service process and the remote service process to monitor each other; wherein: the local service process is carried on the equipment and used for maintaining the local running of the application program; the remote service process is loaded on a remote server.
Mutual protection of the daemon processes is realized by the following modes:
when the local service process is searched and killed, restarting the local service process through the remote service process; and when the remote service process is killed, restarting the remote service process through the local service process. The two processes run together and are protected mutually, and the processes can be maintained to run continuously in a certain sense.
S13: whether the application program is checked and killed is detected through the daemon process, and when the application program is checked and killed, the application program is restarted through the daemon process.
Detecting whether the application program is killed or not through a pre-established daemon process, specifically comprising:
and when the broadcast sent before the application program is killed and closed is received through the pre-established daemon process, judging that the application program is killed.
In this embodiment, a program for transmitting a broadcast before being killed and closed is preset in an application program. When the application program is checked and killed, the application program can actively send a broadcast to the daemon process to inform the daemon process to pull the application program.
In the embodiment, the application program is kept alive and pulled alive by setting two mutually protected processes, so that the effect of preventing the application program from being killed is better.
In order to combine and use multiple technical means to achieve a better keep-alive and pull-alive effect on an application program, a keep-alive and pull-alive method for responding to the application program being killed in some embodiments is further included, referring to fig. 2:
s14: whether the application program runs in a background is detected, and when the application program runs in the background, the activity of the application program is maintained through a pre-established background normally-open process.
Maintaining the activity of the application program through a pre-established background normally-open process, referring to fig. 3, specifically includes:
detecting whether the equipment is turned off;
1) when the equipment is turned off and the application program runs in the background, playing silent background music to maintain the activity of the application program;
when the device does not screen off and the application program runs in the background, playing silent background music to maintain the activity of the application program;
and when the device does not screen off and the application program is not in background running, stopping playing the silent background music.
Playing silent background music does not cause any influence on the use of the device by the user, and simultaneously ensures the activity of the application program in background operation.
2) When the device is in screen-off and the application program runs in the background, displaying an active window of a preset pixel in a notification bar to maintain the activity of the application program;
when the device does not screen and the application program runs in the background, displaying an active window of a preset pixel in a notification bar to maintain the activity of the application program;
and stopping displaying the active window on the notification bar when the device is not turned off and the application program is not in background running.
Preferably, the predetermined pixel is 1 pixel.
The active window of 1 pixel is displayed in the notification bar, so that the device using of a user is not influenced, and the activity of the application program in background running is ensured.
In some embodiments, the method for keeping alive and pulling alive in response to the application program being killed includes starting a daemon process, playing silent background music, encapsulating a function of displaying a 1-pixel active window in a notification bar into a software development kit, binding the software development kit and the application program, installing the software development kit and the application program on a user device in a binding manner, and enabling an application program provider to open a corresponding interface on a server for the software development kit bound by the application program to use.
After an application program is started on equipment of a user, initializing the software development kit, starting working service by the software development kit, and registering a task manager on the equipment carried by the application program; starting a local service process and a remote service process, and binding the local service process and the remote service process as a daemon process; whether silent background music is played or not is decided based on whether the device is off screen or not, whether an application is in a background state or not, and whether a 1-pixel active window is displayed in a notification bar or not.
The effect of keep-alive and pull-alive is achieved by combining and using various technical means, and the purpose of improving the survival rate of the application program is achieved.
A storage medium storing a computer program which, when executed by a processor, implements a keep-alive pull-alive method for coping with application program being killed as in any one of the above embodiments.
A keep-alive pull device for coping with application program being killed, referring to fig. 4, comprising:
a processor 21 and a memory 22;
the processor 21 is connected to the memory 22 by a communication bus:
the processor 21 is configured to call and execute a program stored in the memory 22;
a memory 22 for storing a program for executing at least the keep-alive pull method for coping with application program kill as in any of the above embodiments.
It is understood that the same or similar parts in the above embodiments may be mutually referred to, and the same or similar parts in other embodiments may be referred to for the content which is not described in detail in some embodiments.
It should be noted that, in the description of the present application, the terms "first", "second", etc. are used for descriptive purposes only and are not to be construed as indicating or implying relative importance. Further, in the description of the present application, the meaning of "a plurality" means at least two unless otherwise specified.
Any process or method descriptions in flow charts or otherwise described herein may be understood as representing modules, segments, or portions of code which include one or more executable instructions for implementing specific logical functions or steps of the process, and the scope of the preferred embodiments of the present application includes other implementations in which functions may be executed out of order from that shown or discussed, including substantially concurrently or in reverse order, depending on the functionality involved, as would be understood by those reasonably skilled in the art of the present application.
It should be understood that portions of the present application may be implemented in hardware, software, firmware, or a combination thereof. In the above embodiments, the various steps or methods may be implemented in software or firmware stored in memory and executed by a suitable instruction execution system. For example, if implemented in hardware, as in another embodiment, any one or combination of the following techniques, which are known in the art, may be used: a discrete logic circuit having a logic gate circuit for implementing a logic function on a data signal, an application specific integrated circuit having an appropriate combinational logic gate circuit, a Programmable Gate Array (PGA), a Field Programmable Gate Array (FPGA), or the like.
It will be understood by those skilled in the art that all or part of the steps carried by the method for implementing the above embodiments may be implemented by hardware related to instructions of a program, which may be stored in a computer readable storage medium, and when the program is executed, the program includes one or a combination of the steps of the method embodiments.
In addition, functional units in the embodiments of the present application may be integrated into one processing module, or each unit may exist alone physically, or two or more units 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 stand-alone product, may also be stored in a computer readable storage medium.
The storage medium mentioned above may be a read-only memory, a magnetic or optical disk, etc.
In the description herein, reference to the description of the term "one embodiment," "some embodiments," "an example," "a specific example," or "some examples," etc., means that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the application. In this specification, the schematic representations of the terms used above do not necessarily refer to the same embodiment or example. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples.
Although embodiments of the present application have been shown and described above, it is understood that the above embodiments are exemplary and should not be construed as limiting the present application, and that variations, modifications, substitutions and alterations may be made to the above embodiments by those of ordinary skill in the art within the scope of the present application.
Claims (10)
1. A keep-alive pull-alive method for coping with application program being checked and killed is characterized by comprising the following steps:
starting a work service when an application program is started, and registering a task manager on equipment carried by the application program;
starting a daemon process; the daemon process at least comprises two mutually protected processes;
and detecting whether the application program is checked and killed through the daemon process, and restarting the application program through the daemon process when the application program is checked and killed.
2. The method of claim 1, further comprising:
simultaneously starting a local service process and a remote service process, and binding the local service process and the remote service process as the daemon process to enable the local service process and the remote service process to monitor each other; wherein: the local service process is loaded on the equipment and used for maintaining the local running of the application program; and the remote service process is loaded on a remote server.
3. The method of claim 2, further comprising:
when the local service process is checked and killed, restarting the local service process through the remote service process; and when the remote service process is killed, restarting the remote service process through the local service process.
4. The method of claim 1, further comprising:
and detecting whether the application program runs in a background or not, and maintaining the activity of the application program through a pre-established background normally-open process when the application program runs in the background.
5. The method according to claim 4, wherein the maintaining of the activity of the application through a pre-established background always-on process specifically comprises:
detecting whether the equipment is turned off;
when the device is turned off and the application program is in background running, playing silent background music to maintain the activity of the application program;
when the device does not screen off and the application program runs in the background, playing the silent background music to maintain the activity of the application program;
and when the device does not screen off and the application program is not in background running, stopping playing the silent background music.
6. The method according to claim 5, wherein the maintaining of the activity of the application through a pre-established background always-on process further comprises:
when the device is turned off and the application program runs in the background, displaying an active window with preset pixels on a notification bar to maintain the activity of the application program;
when the device is not stopped and the application program is in background operation, displaying the active window of preset pixels on a notification bar to maintain the activity of the application program;
and stopping displaying the active window on a notification bar when the device is not turned off and the application program is not in background running.
7. The method of claim 6, wherein the predetermined pixel is 1 pixel.
8. The method according to claim 1, wherein the detecting whether the application is killed or not through a pre-established daemon process specifically comprises:
and when receiving the broadcast sent before the application program is killed and closed through a pre-established daemon process, judging that the application program is killed.
9. A storage medium storing a computer program which, when executed by a processor, implements a keep-alive pull method according to any one of claims 1 to 8 in response to an application being killed.
10. A keep-alive pull device that handles applications being killed, comprising:
a processor and a memory;
the processor and the memory are connected through a communication bus:
the processor is used for calling and executing the program stored in the memory;
the memory is used for storing a program, and the program is at least used for executing the keep-alive pull-alive method for coping with the application program being checked and killed according to any one of claims 1-8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011194366.9A CN112307465A (en) | 2020-10-30 | 2020-10-30 | Keep-alive pull-alive method, storage medium and equipment for coping with application program being checked and killed |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011194366.9A CN112307465A (en) | 2020-10-30 | 2020-10-30 | Keep-alive pull-alive method, storage medium and equipment for coping with application program being checked and killed |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112307465A true CN112307465A (en) | 2021-02-02 |
Family
ID=74334122
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011194366.9A Pending CN112307465A (en) | 2020-10-30 | 2020-10-30 | Keep-alive pull-alive method, storage medium and equipment for coping with application program being checked and killed |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112307465A (en) |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113407300A (en) * | 2021-05-21 | 2021-09-17 | 荣耀终端有限公司 | Application false killing evaluation method and related equipment |
| CN113645104A (en) * | 2021-10-19 | 2021-11-12 | 北京国科天迅科技有限公司 | FC switch bus configuration management software monitoring method and device |
| CN114816546A (en) * | 2022-04-28 | 2022-07-29 | 合肥高维数据技术有限公司 | Client application program multi-keep-alive method and system |
| CN115033305A (en) * | 2022-06-27 | 2022-09-09 | Oppo广东移动通信有限公司 | Application identification method and device, storage medium and electronic equipment |
| CN117407068A (en) * | 2023-12-08 | 2024-01-16 | 厦门她趣信息技术有限公司 | Method for activating Android process by multiple strategies |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9384151B1 (en) * | 2013-06-27 | 2016-07-05 | Emc Corporation | Unified SCSI target management for managing a crashed service daemon in a deduplication appliance |
| CN105791596A (en) * | 2016-05-05 | 2016-07-20 | 绿网天下（福建）网络科技股份有限公司 | Method for preventing uninstalling of APP |
| CN107844342A (en) * | 2017-11-21 | 2018-03-27 | 广东欧珀移动通信有限公司 | Management-control method, device and the storage medium and mobile terminal of application program keep-alive |
| CN109819502A (en) * | 2019-01-04 | 2019-05-28 | 维沃移动通信有限公司 | A kind of game on-hook method and apparatus |
| CN109992310A (en) * | 2019-03-12 | 2019-07-09 | 中国平安财产保险股份有限公司 | Application program keepalive method, device, computer equipment and storage medium |
| CN110764965A (en) * | 2019-09-04 | 2020-02-07 | 深圳壹账通智能科技有限公司 | Process daemon method and device, electronic equipment and storage medium |
| CN111026450A (en) * | 2019-12-11 | 2020-04-17 | 上海德拓信息技术股份有限公司 | Method for continuous background operation of government affair terminal application |
| CN111064590A (en) * | 2018-10-16 | 2020-04-24 | 腾讯科技（深圳）有限公司 | Abnormal state repairing method and device and readable storage medium |
| CN111290949A (en) * | 2020-01-21 | 2020-06-16 | 上海悦易网络信息技术有限公司 | Process daemon method and equipment |
-
2020
- 2020-10-30 CN CN202011194366.9A patent/CN112307465A/en active Pending
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9384151B1 (en) * | 2013-06-27 | 2016-07-05 | Emc Corporation | Unified SCSI target management for managing a crashed service daemon in a deduplication appliance |
| CN105791596A (en) * | 2016-05-05 | 2016-07-20 | 绿网天下（福建）网络科技股份有限公司 | Method for preventing uninstalling of APP |
| CN107844342A (en) * | 2017-11-21 | 2018-03-27 | 广东欧珀移动通信有限公司 | Management-control method, device and the storage medium and mobile terminal of application program keep-alive |
| CN111064590A (en) * | 2018-10-16 | 2020-04-24 | 腾讯科技（深圳）有限公司 | Abnormal state repairing method and device and readable storage medium |
| CN109819502A (en) * | 2019-01-04 | 2019-05-28 | 维沃移动通信有限公司 | A kind of game on-hook method and apparatus |
| CN109992310A (en) * | 2019-03-12 | 2019-07-09 | 中国平安财产保险股份有限公司 | Application program keepalive method, device, computer equipment and storage medium |
| CN110764965A (en) * | 2019-09-04 | 2020-02-07 | 深圳壹账通智能科技有限公司 | Process daemon method and device, electronic equipment and storage medium |
| CN111026450A (en) * | 2019-12-11 | 2020-04-17 | 上海德拓信息技术股份有限公司 | Method for continuous background operation of government affair terminal application |
| CN111290949A (en) * | 2020-01-21 | 2020-06-16 | 上海悦易网络信息技术有限公司 | Process daemon method and equipment |
Non-Patent Citations (1)
| Title |
|---|
| 向治洪在知乎: "Android 应用进程保活", pages 1 - 7, Retrieved from the Internet <URL:https://zhuanlan.zhihu.com/p/79324310> * |
Cited By (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113407300A (en) * | 2021-05-21 | 2021-09-17 | 荣耀终端有限公司 | Application false killing evaluation method and related equipment |
| CN113407300B (en) * | 2021-05-21 | 2022-08-12 | 荣耀终端有限公司 | Application false killing evaluation method and related equipment |
| CN113645104A (en) * | 2021-10-19 | 2021-11-12 | 北京国科天迅科技有限公司 | FC switch bus configuration management software monitoring method and device |
| CN114816546A (en) * | 2022-04-28 | 2022-07-29 | 合肥高维数据技术有限公司 | Client application program multi-keep-alive method and system |
| CN115033305A (en) * | 2022-06-27 | 2022-09-09 | Oppo广东移动通信有限公司 | Application identification method and device, storage medium and electronic equipment |
| CN117407068A (en) * | 2023-12-08 | 2024-01-16 | 厦门她趣信息技术有限公司 | Method for activating Android process by multiple strategies |
| CN117407068B (en) * | 2023-12-08 | 2024-03-29 | 厦门她趣信息技术有限公司 | Method for activating Android process by multiple strategies |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112307465A (en) | Keep-alive pull-alive method, storage medium and equipment for coping with application program being checked and killed | |
| US9185179B2 (en) | Re-establishing push notification channels via user identifiers | |
| CN106933660B (en) | Method for realizing application process keep-alive under android platform | |
| CN107704274B (en) | Method, storage medium, equipment and the system waken up for Android application host process | |
| US9489029B2 (en) | Operating system independent network event handling | |
| CN110971922B (en) | Live broadcast and microphone connection state monitoring method, client, server, medium and system | |
| US7430620B2 (en) | Change notification in USB devices | |
| US20030208687A1 (en) | Antivirus stand-alone network or internet appliance and methods therefor | |
| US20090285369A1 (en) | Emergency notification through reserved network communication channels | |
| WO2022100724A1 (en) | Video playback method and apparatus | |
| GB2518739A (en) | Custom Correlation of a Distributed Business Transaction | |
| CN106155844B (en) | A kind of self-recovery method and self recoverable system of WEB server | |
| CN107678782B (en) | Process protection method, device, equipment and computer readable storage medium | |
| WO2021022710A1 (en) | Message queue processing method, device, electronic apparatus, and computer readable non-volatile storage medium | |
| US20180198886A1 (en) | Message transmission method and device | |
| CN111694674A (en) | Message distribution processing method, device, equipment and storage medium | |
| CN103763529B (en) | A kind of digital supervision plateform system and its method for quickly accessing warning device | |
| US20040109406A1 (en) | Facilitating communications with clustered servers | |
| CN110764965A (en) | Process daemon method and device, electronic equipment and storage medium | |
| CN109683974B (en) | Awakening method for application background service process in mobile terminal and related equipment | |
| CN109032767B (en) | Asynchronous multi-process business processing system, method, device and storage medium | |
| CN110308951A (en) | A kind of processing method and processing device of startup interface Caton, equipment, storage medium | |
| CN111813625B (en) | Health checking method and device for distributed server cluster | |
| US20120022925A1 (en) | Method for broadcasting advertisements on electronic device | |
| CN109076008B (en) | Suppressing indication of incoming communications in a user interface |
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 |