CN117407068A - Method for activating Android process by multiple strategies - Google Patents
Method for activating Android process by multiple strategies Download PDFInfo
- Publication number
- CN117407068A CN117407068A CN202311683035.5A CN202311683035A CN117407068A CN 117407068 A CN117407068 A CN 117407068A CN 202311683035 A CN202311683035 A CN 202311683035A CN 117407068 A CN117407068 A CN 117407068A
- Authority
- CN
- China
- Prior art keywords
- account
- application program
- program
- pull
- registering
- 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.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 140
- 230000003213 activating effect Effects 0.000 title claims abstract description 12
- 238000012544 monitoring process Methods 0.000 claims abstract description 11
- 230000001360 synchronised effect Effects 0.000 claims description 33
- FFBHFFJDDLITSX-UHFFFAOYSA-N benzyl N-[2-hydroxy-4-(3-oxomorpholin-4-yl)phenyl]carbamate Chemical compound OC1=C(NC(=O)OCC2=CC=CC=C2)C=CC(=C1)N1CCOCC1=O FFBHFFJDDLITSX-UHFFFAOYSA-N 0.000 claims description 15
- 239000011230 binding agent Substances 0.000 claims description 4
- 238000004891 communication Methods 0.000 claims description 4
- 230000006870 function Effects 0.000 claims description 3
- 230000008447 perception Effects 0.000 claims description 3
- 230000000737 periodic effect Effects 0.000 claims description 3
- 230000004913 activation Effects 0.000 claims 5
- 230000000694 effects Effects 0.000 abstract description 2
- 230000009977 dual effect Effects 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 230000005540 biological transmission Effects 0.000 description 1
- 238000001514 detection method Methods 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
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/4401—Bootstrapping
- G06F9/4418—Suspend and resume; Hibernate and awake
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3003—Monitoring arrangements specially adapted to the computing system or computing system component being monitored
- G06F11/302—Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system component is a software system
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3051—Monitoring arrangements for monitoring the configuration of the computing system or of the computing system component, e.g. monitoring the presence of processing resources, peripherals, I/O links, software programs
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computing Systems (AREA)
- Quality & Reliability (AREA)
- Computer Security & Cryptography (AREA)
- Mathematical Physics (AREA)
- Stored Programmes (AREA)
Abstract
The invention discloses a method for activating an Android process by multiple strategies, which comprises the following steps: s1, when an application program is installed, an account synchronization mechanism is adopted to carry out a live pulling process; s2, after the application program is installed, when the equipment is started, a contact directory mechanism is adopted to carry out a pull-alive process; s3, when the application program is checked and killed, a Native layer inter-process file lock monitoring mechanism is adopted to carry out a live process; the invention integrates various pull-up technical means, adopts an account synchronization mechanism to carry out the pull-up process when an application program is installed, adopts a contact directory mechanism to carry out the pull-up process when equipment is started, adopts a Native layer inter-process file lock monitoring mechanism to carry out the pull-up process when the application program is checked and killed, greatly improves the speed and success rate of re-pull-up after the application program is checked and killed, greatly improves the compatibility, availability and efficiency, and can effectively pull up with the shortest time after the application program is checked and killed, thereby having good use effect.
Description
Technical Field
The invention relates to the technical field of application program pull-up, in particular to a method for pulling up an Android process by multiple strategies.
Background
In the Android system, lifecycle management of applications is automatically done by the system. When the system resources are tensed, the system kills some application programs running in the background according to a certain strategy so as to release the resources. This results in the possibility that the application may be killed by the system during background operation, thereby affecting the stable operation of the application. To address this problem, android developers typically use a technique called "pull-up". The "pull-live" is that by some technical means, the application program can be automatically restarted after being killed by the system, thereby ensuring the continuous running of the application program.
The Chinese patent with the application number of CN202011194366.9 discloses a keep-alive pull-alive method for checking and killing an application program, and the method monitors whether the application program is terminated by utilizing a daemon on the premise that the daemon works normally, and when the application program is terminated, the daemon restarts the application program to realize continuous running and restarting of the application program, so that the problems in the related technology are solved to a certain extent. However, this solution still has the following drawbacks: 1. the technical scheme of the dual service daemon is effective only at android8.0 and versions below, and the versions after android8.0 are ineffective, because an operating system can limit the operation of background service in order to save batteries and memory, and if the service is killed by the system, the dual service daemon cannot work normally; 2. the method has the advantages that the limitation is large, the device is not supported to be started and the software is not supported to be pulled after being installed, the scheme relies on broadcasting to inform daemon to be pulled, and the realization premise of broadcasting is that the software must be started to enter for registration and transmission after being installed; 3. detecting hysteresis, the scheme informs the daemon service process to be closed through the system checking and killing to detect whether the application program is checked and killed, and informs the remote service to be closed through a Binder mechanism after the system checking and killing, and the detection hysteresis can be caused because time consumption exists in cross-process communication, so that the daemon cannot be pulled to be active in the shortest time.
Disclosure of Invention
The method integrates various pull-up technical means, adopts an account synchronization mechanism to carry out the pull-up process when an application program is installed, adopts a contact directory mechanism to carry out the pull-up process when equipment is started, adopts a Native layer inter-process file lock monitoring mechanism to carry out the pull-up process when the application program is checked and killed, greatly improves the speed and success rate of re-pull-up after the application program is checked and killed, greatly improves compatibility, usability and efficiency, and can effectively pull up in the shortest time after the application program is checked and killed, and has good use effect.
In order to achieve the above purpose, the present invention adopts the following technical scheme:
a method for activating an Android process by multiple strategies comprises the following steps:
s1, when an application program is installed, an account synchronization mechanism is adopted to carry out a live pulling process; the pulling and activating process of the account synchronization mechanism comprises the following steps:
s11, installing an application program;
s12, respectively registering a content provider, a registration synchronization adapter service and a registration account authentication service;
s13, starting an application program;
s14, creating an automatic synchronous account: designating the name and type of the automatic synchronous account, declaring authority in the program list file, and starting the automatic synchronous function of the account by calling the setIsSyncable method of the contentResolver;
s15, adding a periodic synchronous account: after the synchronous account is established, a new synchronous account is added into the system by calling an addaccounterExplicitly method of an account manager AccountManager;
s16, carrying out live pulling on a regular account program: after the newly created synchronous account is added into the system, the account program of the system is notified to start automatic synchronization by calling the addPeriodiesSync method of the ContentResolver, and the system account program periodically performs synchronous pull-up;
s2, after the application program is installed, when the equipment is started, a contact directory mechanism is adopted to carry out a pull-alive process;
and S3, when the application program is checked and killed, a Native layer inter-process file lock monitoring mechanism is adopted to carry out a pull-active process.
Preferably, the process of registering the content provider in step S12 is: and registering account content providers in the manifest file of the application program, wherein the registered account content providers are used for searching the content providers of the corresponding accounts when the system performs account synchronization and are used for executing the account related query operation.
Preferably, the process of registering the synchronization adapter in step S12 is: in the manifest file of the application program, a synchronous adapter service is registered, the synchronous adapter service is associated with a system account program through a Binder communication mechanism, and the account program is periodically activated.
Preferably, the process of registering the account authentication service in step S12 is: in the manifest file of the application, an account authentication service for setting the type, name, and icon of the synchronous account is registered.
Preferably, the pull-alive procedure of the contact directory mechanism in step S2 is as follows:
s21, installing an application program: the package manager on the device is responsible for installing the application program and scanning the manifest file of the application program;
s22, registering the content provider: registering a contact directory content provider, contact directory, in a manifest file of an application, the content provider being for association with a contact program of a system;
s23, starting equipment: after the equipment is started, the contact person process service android.process.acore is responsible for pulling the program;
s24, detecting a contact directory: the contact program of the system detects a program with a contact directory content provider contact directory in real time;
s25, automatic pull-up procedure: the contacts of the system automatically pull the program of the contact directory content provider contact directory.
Preferably, in step S3, the pull-alive process of the Native layer inter-process file lock monitoring mechanism is as follows:
s31, installing an application program;
s32, registering the monitor: registering a monitor for specifying the target program to be pulled and the target process to be pulled in a manifest file of the application program;
s33, starting an application program;
s34, the application program respectively creates a service process 1 and a service process 2 in the JAVA layer;
s35, the application program calls a Native layer method in the service process 1, and creates a subprocess through twice fork, so as to obtain an orphan process 1; the application program calls a Native layer method in the service process 2, and creates a subprocess through twice fork, so as to obtain an orphan process 2;
s36, creating a shared file lock: the application program creates a shared file lock shared with each other in the orphan process 1 and orphan process 2 of the Native layer;
s37, searching and killing a perception process: the application program judges whether the orphan processes are checked and killed by the system or not by sensing the state of the shared file lock in the Native layer;
s38, the orphan processes are alive: the orphan process 1 and the orphan process 2 establish association through a shared file lock, one orphan process is immediately perceived by the other orphan process after being checked and killed by the system, and then a monitor is started by calling context.
After the technical scheme is adopted, compared with the background technology, the invention has the following advantages:
1. the invention has good compatibility: through testing, the device with the latest Android14 can be effectively activated, and the device with the latest Android14 can be activated on any existing Android version device due to an account synchronization mechanism AccountSyncAdapter.
2. The invention has strong usability: the invention supports the pulling and activating after the equipment is started and the program is installed, which benefits from the contact directory mechanism, when the program is installed or the equipment is started, the contact providing program of the system can automatically pull and activate the program containing the directory provider, thereby greatly improving the usability of the pulling and activating scene.
3. The invention has high pull-out efficiency: the invention can sense and effectively pull and activate in the shortest time after the program is checked and killed, which benefits from the inter-process file lock monitoring mechanism of the Native layer, the program needs to use at least two processes, the processes are related to each other through the file lock in the Native layer, and one process can pull up other related processes immediately after being checked and killed, thereby ensuring higher pull and activate rate.
Drawings
FIG. 1 is a schematic flow chart of the present invention;
FIG. 2 is a schematic diagram of a process for performing pull-up by the account synchronization mechanism of the present invention;
FIG. 3 is a flow chart of the contact directory mechanism of the present invention for pull-alive;
fig. 4 is a schematic flow chart of a Native layer inter-process file lock monitoring mechanism for carrying out pull-alive according to the present invention.
Detailed Description
The present invention will be described in further detail with reference to the drawings and examples, in order to make the objects, technical solutions and advantages of the present invention more apparent. It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the scope of the invention.
It should be noted that, in the present invention, terms "upper", "lower", "left", "right", "vertical", "horizontal", "inner", "outer", etc. are all based on the orientation or positional relationship shown in the drawings, and are merely for convenience of describing the present invention and simplifying the description, and do not indicate or imply that the apparatus or element of the present invention must have a specific orientation, and thus should not be construed as limiting the present invention.
Examples
As shown in fig. 1 to 4, a method for activating an Android process by using multiple strategies includes the following steps:
s1, when an application program is installed, an account synchronization mechanism is adopted to carry out a live pulling process; the pulling and activating process of the account synchronization mechanism comprises the following steps:
s11, installing an application program;
s12, respectively registering a content provider, a registration synchronization adapter service and a registration account authentication service;
the process of registering the content provider in step S12 is: registering account content providers in a manifest file of an application program, wherein the registered account content providers are used for searching the content providers of corresponding accounts when the system performs account synchronization and executing related query operation of the accounts;
the process of registering the synchronization adapter in step S12 is as follows: registering a synchronous adapter service in a manifest file of an application program, associating the synchronous adapter service with a system account program through a Binder communication mechanism, and periodically activating the account program;
the process of registering the account authentication service in step S12 is as follows: registering an account authentication service in a manifest file of an application program, wherein the account authentication service is used for setting the type, the name and the icon of a synchronous account;
s13, starting an application program;
s14, creating an automatic synchronous account: designating the name and type of the automatic synchronous account, declaring authority in the program list file, and starting the automatic synchronous function of the account by calling the setIsSyncable method of the contentResolver;
s15, adding a periodic synchronous account: after the synchronous account is established, a new synchronous account is added into the system by calling an addaccounterExplicitly method of an account manager AccountManager;
s16, carrying out live pulling on a regular account program: after the newly created synchronous account is added into the system, the account program of the system is notified to start automatic synchronization by calling the addPeriodiesSync method of the ContentResolver, and the system account program periodically performs synchronous pull-up;
s2, after the application program is installed, when the equipment is started, a contact directory mechanism is adopted to carry out a pull-alive process;
the pull-alive process of the contact directory mechanism in step S2 is as follows:
s21, installing an application program: the package manager on the device is responsible for installing the application program and scanning the manifest file of the application program;
s22, registering the content provider: registering a contact directory content provider, contact directory, in a manifest file of an application, the content provider being for association with a contact program of a system;
s23, starting equipment: after the equipment is started, the contact person process service android.process.acore is responsible for pulling the program;
s24, detecting a contact directory: the contact program of the system detects a program with a contact directory content provider contact directory in real time;
s25, automatic pull-up procedure: the contact of the system automatically pulls up a program of a contact directory content provider contact directory;
s3, when the application program is checked and killed, a Native layer inter-process file lock monitoring mechanism is adopted to carry out a live process;
in step S3, the pull-alive process of the Native layer inter-process file lock monitoring mechanism is as follows:
s31, installing an application program;
s32, registering the monitor: registering a monitor for specifying the target program to be pulled and the target process to be pulled in a manifest file of the application program;
s33, starting an application program;
s34, the application program respectively creates a service process 1 and a service process 2 in the JAVA layer;
s35, the application program calls a Native layer method in the service process 1, and creates a subprocess through twice fork, so as to obtain an orphan process 1; the application program calls a Native layer method in the service process 2, and creates a subprocess through twice fork, so as to obtain an orphan process 2;
s36, creating a shared file lock: the application program creates a shared file lock shared with each other in the orphan process 1 and orphan process 2 of the Native layer;
s37, searching and killing a perception process: the application program judges whether the orphan processes are checked and killed by the system or not by sensing the state of the shared file lock in the Native layer;
s38, the orphan processes are alive: the orphan process 1 and the orphan process 2 establish association through a shared file lock, one orphan process is immediately perceived by the other orphan process after being checked and killed by the system, and then a monitor is started by calling context.
The present invention is not limited to the above-mentioned embodiments, and any changes or substitutions that can be easily understood by those skilled in the art within the technical scope of the present invention are intended to be included in the scope of the present invention. Therefore, the protection scope of the present invention should be subject to the protection scope of the claims.
Claims (6)
1. The method for activating the Android process by using multiple strategies is characterized by comprising the following steps of:
s1, when an application program is installed, an account synchronization mechanism is adopted to carry out a live pulling process; the pulling and activating process of the account synchronization mechanism comprises the following steps:
s11, installing an application program;
s12, respectively registering a content provider, a registration synchronization adapter service and a registration account authentication service;
s13, starting an application program;
s14, creating an automatic synchronous account: designating the name and type of the automatic synchronous account, declaring authority in the program list file, and starting the automatic synchronous function of the account by calling the setIsSyncable method of the contentResolver;
s15, adding a periodic synchronous account: after the synchronous account is established, a new synchronous account is added into the system by calling an addaccounterExplicitly method of an account manager AccountManager;
s16, carrying out live pulling on a regular account program: after the newly created synchronous account is added into the system, the account program of the system is notified to start automatic synchronization by calling the addPeriodiesSync method of the ContentResolver, and the system account program periodically performs synchronous pull-up;
s2, after the application program is installed, when the equipment is started, a contact directory mechanism is adopted to carry out a pull-alive process;
and S3, when the application program is checked and killed, a Native layer inter-process file lock monitoring mechanism is adopted to carry out a pull-active process.
2. The method for multi-policy Android process activation in accordance with claim 1, wherein: the process of registering the content provider in step S12 is: and registering account content providers in the manifest file of the application program, wherein the registered account content providers are used for searching the content providers of the corresponding accounts when the system performs account synchronization and are used for executing the account related query operation.
3. The method for multi-policy Android process activation in accordance with claim 1, wherein: the process of registering the synchronization adapter in step S12 is as follows: and registering a synchronous adapter service in a manifest file of the application program, wherein the synchronous adapter service is used for associating with a system account program through a Binder communication mechanism and is periodically activated by the account program.
4. The method for multi-policy Android process activation in accordance with claim 1, wherein: the process of registering the account authentication service in step S12 is as follows: in the manifest file of the application, an account authentication service for setting the type, name, and icon of the synchronous account is registered.
5. The method for multi-policy Android process activation in accordance with claim 1, wherein: the pull-alive process of the contact directory mechanism in step S2 is as follows:
s21, installing an application program: the package manager on the device is responsible for installing the application program and scanning the manifest file of the application program;
s22, registering the content provider: registering a contact directory content provider, contact directory, in a manifest file of an application, the content provider being for association with a contact program of a system;
s23, starting equipment: after the equipment is started, the contact person process service android.process.acore is responsible for pulling the program;
s24, detecting a contact directory: the contact program of the system detects a program with a contact directory content provider contact directory in real time;
s25, automatic pull-up procedure: the contacts of the system automatically pull the program of the contact directory content provider contact directory.
6. The method for multi-policy Android process activation in accordance with claim 1, wherein: in step S3, the pull-alive process of the Native layer inter-process file lock monitoring mechanism is as follows:
s31, installing an application program;
s32, registering the monitor: registering a monitor for specifying the target program to be pulled and the target process to be pulled in a manifest file of the application program;
s33, starting an application program;
s34, the application program respectively creates a service process 1 and a service process 2 in the JAVA layer;
s35, the application program calls a Native layer method in the service process 1, and creates a subprocess through twice fork, so as to obtain an orphan process 1; the application program calls a Native layer method in the service process 2, and creates a subprocess through twice fork, so as to obtain an orphan process 2;
s36, creating a shared file lock: the application program creates a shared file lock shared with each other in the orphan process 1 and orphan process 2 of the Native layer;
s37, searching and killing a perception process: the application program judges whether the orphan processes are checked and killed by the system or not by sensing the state of the shared file lock in the Native layer;
s38, the orphan processes are alive: the orphan process 1 and the orphan process 2 establish association through a shared file lock, one orphan process is immediately perceived by the other orphan process after being checked and killed by the system, and then a monitor is started by calling context.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311683035.5A CN117407068B (en) | 2023-12-08 | 2023-12-08 | Method for activating Android process by multiple strategies |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311683035.5A CN117407068B (en) | 2023-12-08 | 2023-12-08 | Method for activating Android process by multiple strategies |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN117407068A true CN117407068A (en) | 2024-01-16 |
| CN117407068B CN117407068B (en) | 2024-03-29 |
Family
ID=89494664
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202311683035.5A Active CN117407068B (en) | 2023-12-08 | 2023-12-08 | Method for activating Android process by multiple strategies |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117407068B (en) |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20090106234A1 (en) * | 2007-09-07 | 2009-04-23 | Alexander Siedlecki | Apparatus and methods for web marketing tools and digital archives - web portal advertising arts |
| CN109144677A (en) * | 2017-06-16 | 2019-01-04 | 百度在线网络技术（北京）有限公司 | The method and apparatus of keep-alive process for Android system |
| CN111309395A (en) * | 2020-02-10 | 2020-06-19 | 北京星选科技有限公司 | Object keep-alive method and device, electronic equipment and computer readable storage medium |
| CN111399924A (en) * | 2020-03-18 | 2020-07-10 | 山东车微联信息技术股份有限公司 | Method, terminal and storage medium for keeping application process alive under android platform |
| 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 |
| CN115993997A (en) * | 2022-12-21 | 2023-04-21 | 瀚高基础软件股份有限公司 | PostgreSQL database orphan transaction cleaning method |
-
2023
- 2023-12-08 CN CN202311683035.5A patent/CN117407068B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20090106234A1 (en) * | 2007-09-07 | 2009-04-23 | Alexander Siedlecki | Apparatus and methods for web marketing tools and digital archives - web portal advertising arts |
| CN109144677A (en) * | 2017-06-16 | 2019-01-04 | 百度在线网络技术（北京）有限公司 | The method and apparatus of keep-alive process for Android system |
| CN111309395A (en) * | 2020-02-10 | 2020-06-19 | 北京星选科技有限公司 | Object keep-alive method and device, electronic equipment and computer readable storage medium |
| CN111399924A (en) * | 2020-03-18 | 2020-07-10 | 山东车微联信息技术股份有限公司 | Method, terminal and storage medium for keeping application process alive under android platform |
| 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 |
| CN115993997A (en) * | 2022-12-21 | 2023-04-21 | 瀚高基础软件股份有限公司 | PostgreSQL database orphan transaction cleaning method |
Also Published As
| Publication number | Publication date |
|---|---|
| CN117407068B (en) | 2024-03-29 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109379337B (en) | Keep-alive method for application process under android platform | |
| KR100833673B1 (en) | Method for monitoring and reporting events by media gateways | |
| CN106412656B (en) | The method that Android smart machine quickly connects bluetooth | |
| WO2016206528A1 (en) | Method for implementing automatic bluetooth reconnection in android system | |
| CN103401896B (en) | Method and system are shared in a kind of many Android client service | |
| US10491452B2 (en) | Method and system for clustered real-time correlation of trace data fragments describing distributed transaction executions | |
| CN111427594B (en) | Application program running method and device | |
| US20210243136A1 (en) | Method, device and system for resource allocation | |
| CN108108296B (en) | Cloud testing method, server and client | |
| WO2010029362A2 (en) | Embedded background lifecycle manager | |
| CN117407068B (en) | Method for activating Android process by multiple strategies | |
| CN112860408A (en) | Process keep-alive method, device and system in cloud reality machine and storage medium | |
| JP2017536759A (en) | Method and apparatus for self-healing after disconnection of base station | |
| WO2019000790A1 (en) | Method and device for calling remote procedure using synchronous mode | |
| CN114327519A (en) | Implementation method and device for installing application on intelligent POS equipment | |
| CN107465553A (en) | A kind of method and system that can report router state automatically | |
| CN113965496A (en) | Method for optimizing response of screen projection process | |
| CN111464394B (en) | Node monitoring method and device and storage medium | |
| CN114826981B (en) | System and method for realizing application resident in cloud mobile phone | |
| CN112068876A (en) | Process management method, device and system | |
| CN111400081A (en) | Process guarding method and device, electronic equipment and computer storage medium | |
| CN103856537A (en) | Method, platform and system for obtaining operation state of application program on terminal | |
| CN110928787A (en) | Automatic test script recording and playback method, device, equipment and storage medium | |
| CN115640169A (en) | Method, system, device and storage medium for ensuring that a master cluster stops providing services | |
| CN102263797A (en) | Session control method and device |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20240424 Address after: Room 902, No. 33 Xishanwei Road, Software Park Phase III, Xiamen City, Fujian Province, 361000 Patentee after: Xiamen Shequ Information Technology Co.,Ltd. Country or region after: China Address before: Room 902, No. 33 Xishanwei Road, Software Park Phase III, Xiamen City, Fujian Province, 361024 Patentee before: Xiamen Shequ Information Technology Co.,Ltd. Country or region before: China Patentee before: Xiamen Huanqu Information Technology Co.,Ltd. Patentee before: Xiamen Seal Cloud Information Technology Co.,Ltd. |
|
| TR01 | Transfer of patent right |