WO2021254214A1

WO2021254214A1 - Migration method and apparatus for android application program

Info

Publication number: WO2021254214A1
Application number: PCT/CN2021/098909
Authority: WO
Inventors: 王创
Original assignee: 华为技术有限公司
Priority date: 2020-06-20
Filing date: 2021-06-08
Publication date: 2021-12-23
Also published as: CN113821333A

Abstract

A migration method and apparatus for an Android application program, which belong to the technical field of operating systems. The method comprises: exporting basic resource information of an Android application program; calling an Ashmem kernel driver to export Ashmem resource information of the Android application program; calling a Binder kernel driver to export Binder resource information of the Android application program; generating a resource information set of the Android application program that comprises all the types of exported resource information; and sending the resource information set of the Android application program to a destination computing node, so that the destination computing node realizes the restoration of the Android application program on the basis of the resource information set of the Android application program. By means of the method, the export and restoration of basic resource information, Ashmem resource information and Binder resource information of an Android application program under an Android system can be realized, so as to realize the migration of the Android application program.

Description

Method and device for Android application program migration

This application claims the priority of a Chinese patent application filed on June 20, 2020 with the application number 202010569613.2 and the title of the invention "Method and Apparatus for Migrating Android Application Programs", the entire content of which is incorporated into this application by reference.

Technical field

This application relates to the technical field of operating systems, and in particular to a method and device for migrating Android applications.

Background technique

With the continuous development of network technology, Cloudphone has also begun to enter people's lives. The applications in the cloud mobile phone can all be deployed in the cloud computing node, and the cloud computing node provides the computing resources required by the application. In this way, problems such as heat generation and fast power consumption of the physical mobile phone can be effectively avoided. In some cases, applications need to be migrated from the current cloud computing node to other cloud computing nodes. For example, if a user wants an application to use higher-configuration hardware resources than the current cloud computing node, then the application needs to be migrated to In the cloud computing node that meets the needs of users.

Commonly used application migration tools, such as the Checkpoint/Restore In Userspace (CRIU) tool, can export the basic resource information of the application running on the Linux system to generate the resource information collection of the application, and In the new cloud computing node, according to the derived resource information set of the application, the basic resources of the application are restored to complete the migration of the application. Among them, the basic resource information may include process information, memory information, file information, etc. corresponding to the application program.

However, currently cloud mobile phones are mainly based on the Android system, that is, the applications running in the cloud computing nodes are Android applications. The Android system includes two basic services, Anonymous shared memory (Ahmem) service and Inter-process communication (Binder) service. Android applications need to use these two services when running, and will generate corresponding Ashmem resource information and Binder resource information. Using the above CRIU tool can only export and restore the basic resource information of the application, but cannot export and restore the Ashmem resource information and Binder resource information corresponding to the application, that is, it is impossible to realize the migration of the Android application.

Summary of the invention

The embodiment of the application provides a method and device for Android application migration, which can export and restore the resources of the Android application program under the Android system in the computing node, so as to realize the migration of the Android application program. The technical solution is as follows:

In the first aspect, a method for exporting resources of an Android application is provided. The method is applied to the original computing node. The method includes:

Export the first basic resource information of the first Android application. Call the first anonymous shared memory Ashmem kernel driver to export the first Ashmem resource information of the first Android application. Call the first inter-process communication Binder kernel driver to export the first Binder resource information of the first Android application. Generate the resource information set of the first Android application including the first basic resource information, the first Ashmem resource information, and the first Binder resource information. The resource information collection of the first Android application is sent to the target computing node, so that the target computing node restores the basic resources of the first Android application based on the first basic resource information, and calls the second Ashmem kernel driver based on the first Ashmem Resource information, restore the Ashmem resource of the first Android application, call the second Binder kernel driver, and restore the Binder resource of the first Android application based on the first Binder resource information.

In the solution provided by the embodiment of the present application, the computing node may be a server, a virtual machine, or the like. An Android application export recovery tool can be installed in the computing node. The original computing node can export the basic resource information of the first Android application through the basic resource management module in the Android application export recovery tool and write it into the resource information collection of the first Android application. The exported basic resource information of the first Android application may include process information, file information, memory information, etc. of the first Android application. It is also possible to use the Ashmem resource management module in the Android application export recovery tool to call the Ashmem kernel driver in the kernel driver module to export the Ashmem resource information and write it into the resource information collection of the first Android application. Ashmem resource information may include target shared memory information and shared file information shared by multiple processes of the first Android application. It is also possible to call the Binder kernel driver in the kernel driver module through the Binder resource management module, export the Binder resource information and write it into the resource information collection of the first Android application. The Binder resource information may include communication connection information between the client process of the first Android application and the server process of the target application.

After the original computing node writes the basic resource information, Ashmem resource information, and Binder resource information of the first Android application into the resource information collection of the first Android application, it can send the resource information of the first Android application and Target computing node. The destination computing node exports the recovery tool through the Android application, restores the basic resources of the first Android application based on the first basic resource information, calls the second Ashmem kernel driver, and restores the first Android application based on the first Ashmem resource information Call the second Binder kernel driver to restore the Binder resource of the first Android application based on the first Binder resource information.

Through this solution, the basic resource information, Ashmem resource information, and Binder resource information of the Android application under the Android system can be exported, and the target computing node restores the above-exported resources to realize the migration of the Android application .

In a possible implementation manner, the method further includes:

It is detected whether the first Android application program generates new basic resource information, and if it is detected that the first Android application program generates new basic resource information, then the newly generated basic resource information is derived. It is detected whether the first Android application program generates new Ashmem resource information, and if it is detected that the first Android application program generates new Ashmem resource information, then the newly generated Ashmem resource information is derived. It is detected whether the first Android application program generates new Binder resource information, and if it is detected that the first Android application program generates new Binder resource information, then the newly generated Binder resource information is derived. Generate a new resource information set of the first Android application that includes the newly generated basic resource information, the newly generated Ashmem resource information, and the newly generated Binder resource information. Send the newly added resource information set of the first Android application to the destination computing node.

In the solution shown in the embodiment of the present application, in the scenario of hot migration of the first Android application, the Android application export recovery tool in the original computing node exports the basic resource information and Ashmem resource of the first Android application for the first time. After the information and Binder resource information, you can also check whether the first Android application has newly generated resource information in the original computing node according to the preset period. If there is newly generated resource information, export the newly generated resource information to write In the new resource information collection of the first Android application. If it is detected that the total amount of newly generated resource information of the first Android application in the original computing node is greater than the preset threshold, the running of the first Android application in the original computing node may be stopped.

Through this solution, the hot migration of Android applications from the original computing node to the destination computing node can be realized.

In a second aspect, an Android application program migration method is provided, which is applied to a target computing node, and the method includes:

Acquire the resource set of the first Android application sent by the original computing node, where the resource set of the first Android application includes the first basic resource information of the first Android application, the first Ashmem resource information, and the first resource information of the first Android application. A Binder resource information. Based on the first basic resource information, the basic resource of the first Android application is restored. Call the Ashmem kernel driver, and restore the Ashmem resource of the first Android application based on the first Ashmem resource information. Invoke the Binder kernel driver, and restore the Binder resource of the first Android application based on the first Binder resource information.

In the solution shown in the embodiment of the present application, the Android application export recovery tool is also installed in the destination computing node. After the destination computing node receives the basic resource information set of the first Android application sent by the original computing node, it may The recovery tool is exported through the Android application, and the basic resources of the first Android application are restored based on the first basic resource information. Call the Ashmem kernel driver, and restore the Ashmem resource of the first Android application based on the first Ashmem resource information. Call the Binder kernel driver and restore the Binder resource of the first Android application based on the first Binder resource information.

In a possible implementation manner, the first basic resource information includes process information and file information of the first Android application;

The restoring the basic resources of the first Android application based on the first basic resource information includes:

Based on the process information, a process corresponding to the process information is created. Based on the file information, a file corresponding to the file information is created in the file system.

In the solution shown in the embodiment of the present application, the process information may include a process identification ID, a process status, etc., and the file information may include a file name, a file descriptor, read and write permissions, and the like. The basic resource management module in the Android application export recovery tool can create a process based on the process information and configure the process status. The aforementioned basic resource management module can create a process corresponding to the process information based on the process information, and create a file corresponding to the file information in the file system based on the file information.

In a possible implementation manner, the first Ashmem resource information includes target memory information of a shared memory shared by multiple processes of the first Android application and target file information of a shared file, and the target memory information includes the The attribute information and storage data of the shared memory shared by multiple target processes, and the file corresponding to the file information includes the target shared file corresponding to the target file information.

The restoring the Ashmem resource of the first Android application based on the first Ashmem resource information includes:

Create the target shared memory based on the target memory information, and configure the target shared memory based on the attribute information. Write the stored data into the target shared memory and use it as the file content data of the target shared file.

In the solution shown in the embodiment of the present application, the Ashmem resource information of the first Android application may include target memory information of the shared memory shared by multiple processes of the first Android application and target file information of the shared file. Among them, the target memory information includes the size of the shared memory shared by the multiple processes, read and write permissions, storage data, etc., and the target file information includes the name of the shared file, file descriptors, and so on. The Android application export recovery tool can call the Ashmem kernel driver in the kernel driver module through the Ashmem resource management module, create a target shared memory based on the target memory information, configure the target shared memory based on the attribute information, and write the stored data Enter the target shared memory and serve as the file content data of the target shared file.

In a possible implementation manner, the first Binder resource information includes communication connection information between the client process of the first Android application and the server process of the second Android application, and the process information The corresponding process includes the client process of the first Android application;

The restoring the Binder resource of the first Android application based on the first Binder resource information includes:

Based on the communication connection information, a communication connection between the client process and the server process of the second Android application in the target computing node is established.

In the solution shown in the embodiment of the present application, the Binder resource information of the first Android application may include communication connection information between the client process of the first Android application and the server process of the first Android application. The connection information may include basic data of the Binder client structure (binder_ref) of the client process of the first Android application and identification information of the Binder server structure (binder_node) of the server process of the third Android application. The Android application export recovery tool can call the Binder kernel driver in the kernel driver module through the Binder resource management module, and find the corresponding second Android application in the computing node according to the identification information of the above-mentioned Binder server structure (binder_node) And then establish a communication connection between the client process of the first Android application and the server process of the second Android application.

In a third aspect, a method for restoring a snapshot of an Android application program is provided. The method is applied to a computing node, and the method includes:

Receive the snapshot restoration instruction at the first moment of the first Android application. Acquire a stored snapshot of the first Android application corresponding to the first moment, where the snapshot of the first Android application includes first basic resource information of the first Android application, first Ashmem resource information, and The first Binder resource information. Based on the first basic resource information, the basic resource of the first Android application is restored. Call the Ashmem kernel driver, and restore the Ashmem resource of the first Android application based on the first Ashmem resource information. Invoke the Binder kernel driver, and restore the Binder resource of the first Android application based on the first Binder resource information.

In the solution shown in the embodiment of the present application, the computing node may store a snapshot generated at least one moment of the first Android application. When a problem occurs in the operation of the first Android application, the user can specify a snapshot at a moment in the stored snapshots of the first Android application, and use the snapshot to restore the snapshot of the first Android application. The process of using the snapshot to restore the Android application is the same as the process of restoring the basic resources of the Android application during the migration of the Android application in the second aspect above. The snapshot here is the same as that in the first aspect above. The resource information collection includes basic resource information of Android applications, Ashmem resource information, and Binder resource information.

In a possible implementation manner, the method further includes:

At the first moment, receiving a snapshot generation instruction for the first Android application. Derive the first basic resource information. Invoke the Ashmem kernel driver to export the first Ashmem resource information. Invoke the Binder kernel driver to export the first Binder resource information. A snapshot of the first Android application program including the first basic resource information, the first Ashmem resource information, and the first Binder resource information is generated. Correspondingly store the snapshot of the first Android application and the first moment.

In the solution shown in the embodiment of the present application, in order to restore the first Android application in time when there is a problem in the first Android application, the user generates the first Android application through the computing node at least at a specified time. A snapshot of the application program, and the generated snapshot of the first Android application program is correspondingly stored with the first moment when the snapshot is generated.

In a fourth aspect, a device for migrating an Android application program is provided. The device is applied to a target computing node, and the device includes:

The acquiring module is configured to acquire the resource set of the first Android application sent by the original computing node, wherein the resource set of the first Android application includes the first basic resource information of the first Android application, and the first basic resource information of the first Android application. Ashmem resource information and first Binder resource information; basic resource management module, used to export the first basic resource information of the first Android application;

The Ashmem resource management module is used to call the first anonymous shared memory Ashmem kernel driver to export the first Ashmem resource information corresponding to the first Android application;

The Binder resource management module is used to call the first inter-process communication Binder kernel driver to export the first Binder resource information corresponding to the first Android application;

A generating module, configured to generate a resource information set of the first Android application including the first basic resource information, the first Ashmem resource information, and the first Binder resource information;

The sending module is configured to send the resource information collection of the first Android application to a target computing node, so that the target computing node restores the basic resources of the first Android application based on the first basic resource information, and calls The second Ashmem kernel driver restores the Ashmem resource of the first Android application based on the first Ashmem resource information, calls the second Binder kernel driver, and restores the first Binder resource information based on the first Binder resource information. Binder resources for Android applications.

In a possible implementation manner, the sending module is further configured to send the resource information collection of the first Android application to the first computing node;

The basic resource management module is also used to detect whether the first Android application generates new basic resource information, and if it is detected that the first Android application generates new basic resource information, export the newly generated basic resource information;

The Ashmem resource management module is also used to detect whether the first Android application generates new Ashmem resource information, and if it is detected that the first Android application generates new Ashmem resource information, export the newly generated Ashmem resource information;

The Binder resource management module is also used to detect whether the first Android application generates new Binder resource information, and if it is detected that the first Android application generates new Binder resource information, export the newly generated Binder resource information;

The generating module is further configured to generate a new resource information set of the first Android application including the newly generated basic resource information, the newly generated Ashmem resource information, and the newly generated Binder resource information;

The sending module is further configured to send the newly added resource information set of the first Android application to the destination computing node.

In a fifth aspect, a device for migrating an Android application program is provided. The device is applied to a target computing node, and the device includes:

The acquiring module is configured to acquire the resource set of the first Android application sent by the original computing node, wherein the resource set of the first Android application includes the first basic resource information of the first Android application, and the first basic resource information of the first Android application. Ashmem resource information and first Binder resource information;

A basic resource management module, configured to restore the basic resources of the first Android application based on the first basic resource information;

The Ashmem resource management module is used to call the Ashmem kernel driver and restore the Ashmem resource of the first Android application based on the first Ashmem resource information;

The Binder resource management module is used to call the Binder kernel driver and restore the Binder resource of the first Android application based on the first Binder resource information.

The basic resource management module is used for:

Based on the process information, creating a process corresponding to the process information;

Based on the file information, a file corresponding to the file information is created in the file system.

In a possible implementation manner, the first Ashmem resource information includes target memory information of a shared memory shared by multiple processes of the first Android application program and target file information of a shared file, and the target memory information includes Attribute information and storage data of the shared memory shared by the multiple target processes, and the file corresponding to the file information includes the target shared file corresponding to the target file information;

The Ashmem resource management module is used for:

Create a target shared memory based on the target memory information, and configure the target shared memory based on the attribute information;

The storage data is written into the target shared memory and used as the file content data of the target shared file.

The Binder resource management module is used to:

In a sixth aspect, a device for restoring a snapshot of an Android application program is provided. The method is applied to a computing node, and the device includes:

The receiving module is used to receive the snapshot restoration instruction at the first moment of the first Android application;

The acquiring module is configured to acquire a stored snapshot of the first Android application corresponding to the first moment, wherein the snapshot of the first Android application includes the first basic resource information and the first Android application of the first Android application. -Ashmem resource information and the first Binder resource information;

In a possible implementation manner, the receiving module is further configured to:

At the first moment, receiving a snapshot generation instruction for the first Android application;

The basic resource management module is also used to export the first basic resource information;

The Ashmem resource management module is further configured to call the Ashmem kernel driver to export the first Ashmem resource information;

The Binder resource management module is further configured to call the Binder kernel driver to export the first Binder resource information;

The device further includes a generating module, configured to generate a snapshot of the first Android application including the first basic resource information, the first Ashmem resource information, and the first Binder resource information;

The device further includes a storage module for storing the snapshot of the first Android application program and the first moment in correspondence.

In a seventh aspect, a computing node is provided. The computing node includes a processor and a memory, and at least one instruction is stored in the memory. The instruction is loaded and executed by the processor to implement the above-mentioned first aspect. The operations performed by the Android application migration method described above, or the operations performed by the Android application migration method described in the second aspect described above, or the Android application snapshot restoration method described in the third aspect described above The action performed.

In an eighth aspect, a computer-readable storage medium is provided, and at least one instruction is stored in the storage medium, and the instruction is loaded and executed by a processor to implement the Android application migration method as described in the first aspect above The operations performed are either the operations performed by the Android application migration method described in the second aspect described above, or the operations performed by the Android application snapshot restoration method described in the third aspect described above.

In a ninth aspect, a computer program product containing instructions is provided, when the computer program product runs on a vehicle lane change trend recognition device, the computing node is caused to execute the Android application migration as described in the first aspect above , Or execute the Android application migration method as described in the second aspect above, or execute the Android application snapshot restoration method as described in the third aspect above.

The beneficial effects brought about by the technical solutions provided by the embodiments of this application are:

The technical solutions provided by the embodiments of the present application can export not only basic resource information of the Android application, but also Ashmem resource information and Binder resource information unique to the Android application. In addition, after the resource information set including the resource information is generated, and the resource information set of the Android application is sent to the destination computing node, the destination computing node can restore the basic resources, Ashmem resources, and Binder resources of the Android application to Realize the migration of Android applications.

Description of the drawings

FIG. 1 is a schematic diagram of a migration scenario of an Android application provided by an embodiment of the present application;

FIG. 2 is a schematic diagram of a snapshot restoration scene of an Android application provided by an embodiment of the present application;

3 is a schematic structural diagram of an Android application export recovery tool provided by an embodiment of the present application;

FIG. 4 is a schematic diagram of the principle of an Ashmem service provided by an embodiment of the present application;

FIG. 5 is a schematic diagram of the principle of a Binder service provided by an embodiment of the present application;

FIG. 6 is a flowchart of a method for migrating an Android application provided by an embodiment of the present application;

FIG. 7 is a schematic diagram of a quick startup scenario of an Android application provided by an embodiment of the present application;

FIG. 8 is a flowchart of a method for restoring an Android application program snapshot provided by an embodiment of the present application;

FIG. 9 is a schematic structural diagram of an Android application program migration device provided by an embodiment of the present application;

FIG. 10 is a schematic structural diagram of an Android application program migration device provided by an embodiment of the present application;

FIG. 11 is a schematic structural diagram of a device for restoring an Android application program snapshot provided by an embodiment of the present application;

FIG. 12 is a schematic structural diagram of a computing node provided by an embodiment of the present application.

detailed description

The embodiments of the present application provide a method and device for migrating an Android application program. The method can be implemented by an original computing node and a destination computing node that are installed with an Android application export recovery tool. Both the original computing node and the destination computing node may be servers, virtual machines, and so on.

As shown in Figure 1, this method can be applied to the scenario of Android application migration. The original computing node installed with the Android application export recovery tool can export the basic resource information, Ashmem resource information and Binder resource information of the first Android application through the Android application export recovery tool and write it into the resource information collection. It is sent to the destination computing node that also has the Android application export recovery tool installed, and the destination computing node restores the first Android application.

As shown in Fig. 2, this method can also be applied in the scenario where an Android application is quickly started. Deploying the Android application migration tool and the Android application export recovery tool can be installed in the original computing node with multiple Android applications. The original computing node can export the recovery tool through the Android application, and the export needs to be quickly started in the target computing node The resource information of the first Android application (Android application 2 in FIG. 2) is collected and sent to the startup resource storage device for storage. The target computing node can obtain the resource information collection of the first Android application that needs to be started quickly in the startup resource storage device, and restore the target Android application through the Android application export recovery tool, so as to realize the correctness in the target computing node. Quick launch of the first Android application.

The Android application export recovery tool installed in the aforementioned computing node may be a software tool, as shown in FIG. 3, the Android application export recovery tool may include three modules: an external interface gateway module, a resource management module, and a kernel driver module. Among them, the external interface gateway module and the resource management module run in the user space, and the kernel driver module runs in the kernel space. The external interface gateway module is used to provide external interfaces of the Android application export recovery tool, such as a command line interface, a HyperText Transfer Protocol (HTTP) interface, and so on. The resource management module includes a basic resource management module, an anonymous shared memory (Ahmem) resource management module, and an inter-process communication (Binder) module. The kernel drive module includes Ashmem kernel drive module and Binder kernel drive module. Among them, the basic resource management module is used to export and restore basic resource information of the Android application. The Ashmem resource management module is used to call the Ashmem kernel driver in the kernel driver module to realize the export and recovery of Ashmem resource information. The Binder resource management module is used to call the Binder kernel driver in the kernel driver module to realize the export and recovery of Binder resource information.

In order to facilitate the understanding of this application, some technical terms in this application are explained below.

1. Ashmem service

As shown in Figure 4, the target Android application includes process A and process B, and process A and process B respectively correspond to file descriptor tables (fdt). The file system (file sytem) includes files corresponding to each process, and the Ashmem module is a shared memory module. In the case that process A and process B have shared memory, the file descriptor table corresponding to process A and process B respectively contains a file descriptor pointing to the same file fileN in the file system, and the file content data of fileN is stored in Ashmem The target shared memory in the module.

Two, Binder service

As shown in Figure 5, the Android application A includes a client process, and the Android application B includes a server process. The client process in Android application A is in the Binder module "BinderA" in the kernel space. The BinderA includes a Binder process structure (binder_proc), a Binder client structure (binder_ref), and a Binder thread information structure (binder_thread). The server process in Android application B has a Binder module "BinderB" in the kernel space. The BinderB includes binder_proc, binder_thread and Binder server structure (binder_node). If you want to establish a communication connection between the client process of Android application A and the server process of Android application B, you need to make the node in the binder_ref of the client process point to the binder_node of the server process.

Fig. 6 is a flowchart of a method for migrating an Android application provided by an embodiment of the present application. The processing flow of the method may include the following steps:

Step 601: The original computing node derives the first basic resource information of the first Android application.

In implementation, an Android application export recovery tool can be deployed in the original computing node. When the first Android application needs to be migrated, the resource migration instruction for the first Android application can be sent to the Android application export recovery tool. , The resource migration instruction can be in the form of command line, HTTP request, etc.

After the Android application export recovery tool receives the resource migration instruction for the first Android application through the external interface gateway, it can export the basic resource information of the first Android application through the basic resource management module. The exported basic resource information of the first Android application may include process information, file information, memory information, etc. of the first Android application. Among them, the process information may include process identification (ID), process status, etc. The file information may include file size, file read and write permissions, file modification time, etc., and memory information may include a list of used memory areas and used memory Storage data, etc.

Step 602: The original computing node calls the first Ashmem kernel driver to export the first Ashmem resource information of the first Android application.

In implementation, after the Android application export recovery tool receives the resource migration instruction for the first Android application, it can also call the first Ashmem kernel driver in the kernel driver module through the Ashmem resource management module to perform operations on the Ashmem resource information. Export. Ashmem resource information may include target shared memory information and shared file information shared by multiple processes of the first Android application. Among them, the target shared memory information includes the attributes and storage data of the shared memory, and the shared file information includes the name, size, and file descriptor of the shared file.

Step 603: The original computing node calls the first Binder kernel driver to export the first Binder resource information of the first Android application.

In implementation, after the Android application export recovery tool receives the resource export instruction for the first Android application, it can also call the Binder kernel driver in the kernel driver module through the Binder resource management module to export Binder resource information. The Binder resource information may include communication connection information between the client process of the first Android application and the server process of the second Android application. The communication connection information may include the binder_ref of the client process of the first Android application and the identification information of the binder_node of the server process in the second Android application. The communication connection information is used to indicate the client process of the first Android application. There is a connection relationship between the binder_ref of the second Android application and the binder_node of the server process in the second Android application.

Step 604: The original computing node generates a first Android application resource set including the first basic resource information, the first Ashmem resource information, and the first Binder resource information.

In implementation, the derived first basic resource information, first Ashmem resource information, and first Binder resource information may be written into the resource collection of the first Android application.

Step 605: The original computing node sends the resource information collection of the first Android application to the destination computing node.

In implementation, the user can specify that the first Android application needs to be migrated to the destination computing node. Then, after the original computing node generates the resource information collection of the first Android application, the resource information collection of the first Android application can be sent To the destination computing node.

Step 606: The destination computing node obtains the resource information set of the first Android application sent by the original computing node.

Step 607: The destination computing node restores the basic resources of the first Android application based on the first basic resource information. Call the second Ashmem kernel driver, and restore the Ashmem resource of the first Android application based on the first Ashmem resource information. Call the second Binder kernel driver, and restore the Binder resource of the first Android application based on the first Binder resource information.

In the implementation, the Android application export recovery tool is also installed in the destination computing node. After obtaining the resource information collection of the first Android application sent by the original computing node, the destination computing node can export the recovery tool to the first Android application through the Android application. An Android application to restore. The following describes the recovery of the basic resources, Ashmem resources and Binder resources of the first Android application through the Android application export recovery tool:

1. The restoration of the basic resources of the first Android application.

Through the basic resource management module, based on the first basic resource information of the first Android application, the basic resources of the first Android application are restored.

The basic resource information of the first Android application includes process information, file information, memory information, etc. of the first Android application. Among them, process information can include process identification ID, process status, etc., file information can include file name, file read and write permissions, file modification time, file descriptors, etc., memory information can include a list of used memory areas, and information in used memory. Store data, etc.

The basic resource management module can create a corresponding process based on the process information and set the process status. You can also create a used memory area list based on the memory information, and write the corresponding storage data in the corresponding memory area. You can also create corresponding files in the file system (File System) based on file information, and configure file attributes such as file read and write permissions, file modification time, etc. You can also create a file descriptor table of the corresponding process, and set it in the file descriptor table. The newly created file corresponds to the file descriptor in the corresponding file information.

2. Ashmem resource recovery of the first Android application.

Call the Ashmem kernel driver in the kernel driver module through the Ashmem resource management module, and restore the Ashmem resource of the second Android application based on the second Ashmem resource information.

The Ashmem resource information of the first Android application program may include target memory information of a shared memory shared by multiple processes of the first Android application program and target file information of a shared file. Among them, the target memory information includes the size of the shared memory shared by the multiple processes, read and write permissions, storage data, etc., and the target file information includes the name of the shared file, file descriptors, and so on.

It should be noted here that the multiple processes of the first Android application here have been created when the above-mentioned basic resources are restored. The target shared file corresponding to the target file information has also been created when the above-mentioned basic resource is restored.

The Ashmem kernel driver can create a target shared memory according to the size of the shared memory shared by multiple processes in the target memory information, configure its read and write permissions, and write the stored data into the created target shared memory. Then use the stored data in the target shared memory as the content data of the target shared file. Completed Ashmem resource restoration of the first Android application.

3. Binder resource recovery of the first Android application.

The Binder kernel driver in the kernel driver module is called through the Binder resource management module, and the Binder resource of the first Android application is restored based on the second Binder resource information.

The Binder resource information of the first Android application may include communication connection information between the client process of the first Android application and the server process of the first Android application. The communication connection information may include the information of the first Android application. The basic data of the binder_ref of the client process and the identification information of the binder_node of the server process of the second Android application. In addition, the Binder resource information may also include configuration information, such as the basic data of the binder_proc and the basic data of the binder_thread of the client process of the second Android application. It can also include communication data between the client process and the server process.

It should be noted here that the client process of the first Android application here has been created when the above-mentioned basic resources are restored. The second Android application program is usually a public application program, and the second Android application program needs to be installed in both the original computing node and the destination computing node.

The Binder kernel driver can create the binder_proc, binder_thread, and binder_ref of the client process of the first Android application in the computing node according to the above configuration information. Then, according to the identification information of the binder_node of the server process of the second Android application in the communication connection information, search for the server process of the second Android application, and make the node in the binder_ref of the client process of the first Android application point to the search The binder_node of the server process of the second Android application to realize the communication connection between the client process of the first Android application and the server of the second Android application.

In a possible implementation manner, in a live migration scenario of an Android application, the original computing node may send the resource collection of the first Android application to the destination computing node, and the destination computing node will receive the first Android application based on the received first Android application. The resource collection of the application restores the first Android application. In this scenario, the first Android application program may still be running in the original computing node, and the original computing node may detect whether the first Android application program generates new resource information according to a preset detection period. Correspondingly, the processing can be as follows:

Export the basic resource management module of the recovery tool through the Android application to detect whether the first Android application generates new basic resource information, and if it detects that the first Android application generates new basic resource information, export the newly generated basic resource information .

Export the Ashmem resource management module of the recovery tool through the Android application to detect whether the first Android application generates new basic resource information, and if it detects that the first Android application generates new basic resource information, export the newly generated basic resource information Export.

Use the Binder resource management module of the Android application export recovery tool to detect whether the first Android application generates new Binder resource information. If it is detected that the first Android application generates new Binder resource information, export the newly generated Binder resource information .

Generate the new resource set of the first Android application including the newly generated basic resource information, the newly generated Ashmem resource information, and the newly generated Binder resource information, and send the new resource set of the first Android application to the destination computing node .

In addition, if after the first Android application is migrated to the destination computing node, the newly generated basic resource information of the first Android application, the newly generated Ashmem resource information, and the newly generated Binder resource information are detected in the original computing node. If the total amount is greater than the preset threshold, the running of the first Android application in the original computing node is stopped.

In a possible implementation manner, multiple Android applications including the first Android application can be installed in the computing node, and the first Android application needs to run in an independent computing node, then the computing node The node can export the basic resource information, Ashmem resource information, and Binder resource information of the first Android application through the Android application export recovery tool, and write them into the resource information collection of the first Android application. Then, stop running the first Android application in the original computing node, and send it to the startup resource storage device for storage. The destination computing node of the first Android application to be run may, after receiving the instruction to quickly start the first Android application, obtain the resource information set of the first Android application from the startup resource storage device, and execute the step 707 described above. The restoration of the basic resources, Ashmem resources, and Binder resources of the first Android application program completes the quick start of the first Android application program in the target computing node.

In the embodiments of the present application, in addition to the basic resource information of the Android application, Ashmem resource information and Binder resource information unique to the Android application can also be exported. In addition, after the resource information set including the resource information is generated, and the resource information set of the Android application is sent to the destination computing node, the destination computing node can restore the basic resources, Ashmem resources, and Binder resources of the Android application to Realize the migration of Android applications.

The embodiment of the present application also provides a method for restoring a snapshot of an Android application program. The method can be implemented by a computing node installed with a tool for exporting and restoring an Android application program.

As shown in Figure 7, this method can be applied to the scenario of Android application snapshot recovery. The computing node installed with the Android application migration tool can export the basic resource information, Ashmem resource information, and Binder resource information of the first Android application at least at one specified time through the Android application migration tool, and write it into the first Android application. In the snapshot. When there is a problem with the Android application, a snapshot of the first Android application exported at a certain moment can be obtained as needed, and the first Android application can be restored through the Android application export recovery tool.

Fig. 8 is a flowchart of a method for migrating an Android application provided by an embodiment of the present application. The processing flow of the method may include the following steps:

Step 801: Receive a snapshot restoration instruction at the first moment of the first Android application.

In an implementation, the computing node may store a snapshot generated at least one moment of the first Android application. When a problem occurs in the running of the first Android application, the user can send a snapshot restoration instruction of the first moment of the first application to the computing node.

Step 802: Obtain a stored snapshot of the first Android application corresponding to the first moment.

Wherein, the snapshot of the first Android application program includes the first basic resource information of the first Android application program, the first Ashmem resource information, and the first Binder resource information.

Step 803: Based on the first basic resource information, restore the basic resources of the first Android application, call the Ashmem kernel driver, based on the first Ashmem resource information, restore the Ashmem resource of the first Android application, call the Binder kernel driver, based on The first Binder resource information restores the Binder resource of the first Android application.

It should be noted that in this step 803, the computing node restores the first Android application based on a snapshot of the first Android application at a certain moment, which is the same as in the above step 607, the destination computing node is based on the first Android application. The method for restoring the first Android application program in the resource information collection of is the same, and will not be repeated here.

In a possible implementation manner, the user can generate and store a snapshot of the first Android application program through the computing node at at least one designated moment, so as to use it when a problem occurs with the first Android application program. Correspondingly, the processing can be as follows: at the first moment, a snapshot generation instruction for the first Android application is received. Export the first basic resource information. Call the Ashmem kernel driver to export the first Ashmem resource information. Call the Binder kernel driver to export the first Binder resource information. A snapshot of the first Android application program including the first basic resource information, the first Ashmem resource information, and the first Binder resource information is generated. The snapshot of the first Android application program is correspondingly stored with the first moment.

Based on the same technical concept, an embodiment of the present application also provides a device for migrating an Android application program. The device can be applied to a computing node. As shown in FIG. 9, the device includes:

The basic resource management module 910 is used to export the first basic resource information of the first Android application. Specifically, the function of deriving basic resource information in the above step 601 and other implicit steps can be realized.

The Ashmem resource management module 920 is used for the first Ashmem kernel driver to export the first Ashmem resource information corresponding to the first Android application. Specifically, the Ashmem resource information derivation function in step 602 above can be implemented, as well as other implicit steps.

The Binder resource management module 930 is configured to call the first Binder kernel driver and export the first Binder resource information corresponding to the first Android application. Specifically, the Binder resource information derivation function in step 603 above can be implemented, as well as other implicit steps.

The generating module 940 is configured to generate a resource information set of the first Android application including the first basic resource information, the first Ashmem resource information, and the first Binder resource information. Specifically, the generating function in step 604 and other implicit steps can be realized.

The sending module 950 is configured to send the resource information collection of the first Android application to a target computing node, so that the target computing node restores the basic resources of the first Android application based on the first basic resource information, Call the second Ashmem kernel driver, restore the Ashmem resource of the first Android application based on the first Ashmem resource information, call the second Binder kernel driver, and restore the first Binder resource information based on the first Binder resource information. A Binder resource of an Android application. Specifically, the sending function in the above step 605 and other implicit steps can be realized.

In a possible implementation, the sending module 950 is further configured to send the resource information collection of the first Android application to the first computing node;

The Ashmem resource management module 920 is also used to detect whether the first Android application generates new Ashmem resource information, and if it is detected that the first Android application generates new Ashmem resource information, export the newly generated Ashmem Resource information;

The Binder resource management module 930 is also used to detect whether the first Android application generates new Binder resource information, and if it is detected that the first Android application generates new Binder resource information, then export the newly generated Binder Resource information;

The generating module 940 is further configured to generate a new resource information set of the first Android application including the newly generated basic resource information, the newly generated Ashmem resource information, and the newly generated Binder resource information;

The sending module 950 is further configured to send the newly added resource information set of the first Android application to the destination computing node.

It should also be noted that the device for migrating an Android application provided in the above embodiment only uses the division of the above functional modules for illustration when the Android application is migrated. In actual applications, the above functional assignments can be assigned differently according to needs. The function module is completed, that is, the internal structure of the original computing node is divided into different function modules to complete all or part of the functions described above. In addition, the device for migrating an Android application program provided in the foregoing embodiment belongs to the same concept as the method embodiment of the Android application program migration. For the specific implementation process, please refer to the method embodiment, which will not be repeated here.

Based on the same technical concept, an embodiment of the present application also provides a device for migrating an Android application program. The device can be applied to a computing node. As shown in FIG. 10, the device includes:

The acquiring module 1010 is configured to acquire the resource set of the first Android application sent by the original computing node, where the resource set of the first Android application includes the first basic resource information of the first Android application and the first basic resource information of the first Android application. One Ashmem resource information and the first Binder resource information. Specifically, the acquisition function in step 606 above and other implicit steps can be implemented.

The basic resource management module 1020 is configured to restore the basic resources of the first Android application based on the first basic resource information. Specifically, the basic resource recovery function in step 607 and other implicit steps can be implemented.

The Ashmem resource management module 1030 is configured to call the Ashmem kernel driver and restore the Ashmem resource of the first Android application based on the first Ashmem resource information. Specifically, the Ashmem resource recovery function in step 607 above can be implemented, as well as other implicit steps.

The Binder resource management module 1040 is configured to call the Binder kernel driver and restore the Binder resource of the first Android application based on the first Binder resource information. Specifically, the Binder resource recovery function in step 607 and other implicit steps can be implemented.

The basic resource management module 1020 is used to:

The Ashmem resource management module 1030 is used to:

The Binder resource management module 1040 is used to:

It should also be noted that the device for migrating an Android application provided in the above embodiment only uses the division of the above functional modules for illustration when the Android application is migrated. In actual applications, the above functional assignments can be assigned differently according to needs. The function module is completed, that is, the internal structure of the target computing node is divided into different function modules to complete all or part of the functions described above. In addition, the device for migrating an Android application program provided in the foregoing embodiment belongs to the same concept as the method embodiment of the Android application program migration. For the specific implementation process, please refer to the method embodiment, which will not be repeated here.

Based on the same technical concept, an embodiment of the present application also provides a device for restoring a snapshot of an Android application program. The device can be applied to a computing node. As shown in FIG. 11, the device includes:

The receiving module 1110 is configured to receive a snapshot restoration instruction at the first moment of the first Android application;

The obtaining module 1120 is configured to obtain a stored snapshot of the first Android application corresponding to the first moment, wherein the snapshot of the first Android application includes the first basic resource information of the first Android application, The first Ashmem resource information and the first Binder resource information;

The basic resource management module 1130 is configured to restore the basic resources of the first Android application based on the first basic resource information;

The Ashmem resource management module 1140 is configured to call the Ashmem kernel driver, and restore the Ashmem resource of the first Android application based on the first Ashmem resource information;

The Binder resource management module 1150 is configured to call the Binder kernel driver and restore the Binder resource of the first Android application based on the first Binder resource information.

In a possible implementation manner, the receiving module 1110 is further configured to:

The basic resource management module 1130 is further configured to export the first basic resource information;

The Ashmem resource management module 1140 is also used to call the Ashmem kernel driver to export the first Ashmem resource information;

The Binder resource management module 1150 is further configured to call the Binder kernel driver to export the first Binder resource information;

It should also be noted that the device for restoring an Android application snapshot provided in the above embodiment only uses the division of the above functional modules for illustration when the Android application snapshot is restored. In actual applications, the above functions can be allocated according to needs. It is completed by different functional modules, that is, the internal structure of the computing node is divided into different functional modules to complete all or part of the functions described above. In addition, the device for restoring a snapshot of an Android application program provided in the foregoing embodiment belongs to the same concept as the method embodiment for restoring a snapshot of an Android application program. For the specific implementation process, please refer to the method embodiment, which will not be repeated here.

FIG. 12 is a schematic diagram of a computing node 1200 provided by an embodiment of the present application. In FIG. 12, the computing node may include a processor 1201 and a memory 1202. The processor 1201 may be a central processing unit (CPU). The processor 1201 may refer to one processor, or may include multiple processors. The memory 1202 may include volatile memory, such as random access memory (RAM); the memory may also include non-volatile memory, such as read-only memory (ROM), flash memory, and the like. The memory may also include a combination of the above-mentioned types of memory. The memory 1202 may refer to one memory, or may include multiple memories. The memory 1202 stores computer-readable instructions, and the computer-readable instructions can be executed by the processor 1201 to implement the Android application program migration or snapshot restoration method provided in the foregoing embodiments.

In the above-mentioned embodiments, it may be implemented in whole or in part by software, hardware, firmware or any combination thereof, and when implemented in software, it may be implemented in the form of a computer program product in whole or in part. The computer program product includes one or more computer instructions, and when the computer program instructions are loaded and executed on a device, the processes or functions described in the embodiments of the present application are generated in whole or in part. The computer instructions may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from a website, computer, server, or data center. Transmission to another website site, computer, server or data center via wired (such as coaxial optical cable, optical fiber, digital subscriber line) or wireless (such as infrared, wireless, microwave, etc.). The computer-readable storage medium may be any available medium that can be accessed by the device or a data storage device such as a server or data center integrated with one or more available media. The usable medium may be a magnetic medium (such as a floppy disk, a hard disk, and a magnetic tape, etc.), an optical medium (such as a digital video disk (Digital Video Disk, DVD), etc.), or a semiconductor medium (such as a solid state hard disk, etc.).

Those of ordinary skill in the art can understand that all or part of the steps in the foregoing embodiments can be implemented by hardware, or by a program instructing relevant hardware to be completed. The program can be stored in a computer-readable storage medium. The storage medium mentioned can be a read-only memory, a magnetic disk or an optical disk, etc.

The above is only an embodiment of this application and is not intended to limit this application. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of this application shall be included in the protection scope of this application. Inside.

Claims

An Android application migration method, characterized in that the method is applied to the original computing node, and the method includes:

Export the first basic resource information of the first Android application;

Calling the first anonymous shared memory Ashmem kernel driver to export the first Ashmem resource information of the first Android application;

Calling the first inter-process communication Binder kernel driver to export the first Binder resource information of the first Android application;

Generating a resource information set of the first Android application that includes the first basic resource information, the first Ashmem resource information, and the first Binder resource information;

Send the resource information collection of the first Android application to the target computing node, so that the target computing node restores the basic resources of the first Android application based on the first basic resource information, and calls the second Ashmem kernel driver The program restores the Ashmem resource of the first Android application based on the first Ashmem resource information, calls the second Binder kernel driver, and restores the Binder of the first Android application based on the first Binder resource information resource.
The method according to claim 1, wherein the method further comprises:

Detecting whether the first Android application program generates new basic resource information, and if it is detected that the first Android application program generates new basic resource information, exporting the newly generated basic resource information;

Detecting whether the first Android application program generates new Ashmem resource information, and if it is detected that the first Android application program generates new Ashmem resource information, export the newly generated Ashmem resource information;

Detecting whether the first Android application program generates new Binder resource information, and if it is detected that the first Android application program generates new Binder resource information, export the newly generated Binder resource information;

Generating a new resource information set of the first Android application that includes the newly generated basic resource information, the newly generated Ashmem resource information, and the newly generated Binder resource information;

Sending the newly added resource information set of the first Android application to the destination computing node.
An Android application program migration method, characterized in that the method is applied to a target computing node, and the method includes:

Obtain the resource set of the first Android application sent by the original computing node, where the resource set of the first Android application includes the first basic resource information of the first Android application, the first Ashmem resource information, and the first resource information of the first Android application. -Binder resource information;

Restore the basic resources of the first Android application based on the first basic resource information;

Call the Ashmem kernel driver, and restore the Ashmem resource of the first Android application based on the first Ashmem resource information;

Invoke the Binder kernel driver, and restore the Binder resource of the first Android application based on the first Binder resource information.
The method according to claim 3, wherein the first basic resource information includes process information and file information of the first Android application;

The restoring the basic resources of the first Android application based on the first basic resource information includes:

Based on the process information, creating a process corresponding to the process information;

Based on the file information, a file corresponding to the file information is created in the file system.
The method according to claim 4, wherein the first Ashmem resource information includes target memory information of a shared memory shared by multiple processes of the first Android application and target file information of a shared file, and The target memory information includes attribute information and storage data of the shared memory shared by the multiple target processes, and the file corresponding to the file information includes the target shared file corresponding to the target file information;

The restoring the Ashmem resource of the first Android application based on the first Ashmem resource information includes:

Create a target shared memory based on the target memory information, and configure the target shared memory based on the attribute information;

The storage data is written into the target shared memory and used as the file content data of the target shared file.
The method according to claim 4 or 5, wherein the first Binder resource information includes the communication between the client process of the first Android application and the server process of the second Android application Connection information, where the process corresponding to the process information includes the client process of the first Android application;

The restoring the Binder resource of the first Android application based on the first Binder resource information includes:

Based on the communication connection information, a communication connection between the client process and the server process of the second Android application in the target computing node is established.
A method for restoring a snapshot of an Android application program, wherein the method is applied to a computing node, and the method includes:

Receiving a snapshot restoration instruction at the first moment of the first Android application;

Acquire a stored snapshot of the first Android application corresponding to the first moment, where the snapshot of the first Android application includes first basic resource information of the first Android application, first Ashmem resource information, and The first Binder resource information;

Restore the basic resources of the first Android application based on the first basic resource information;

Call the Ashmem kernel driver, and restore the Ashmem resource of the first Android application based on the first Ashmem resource information;

Invoke the Binder kernel driver, and restore the Binder resource of the first Android application based on the first Binder resource information.
The method according to claim 7, wherein the method further comprises:

At the first moment, receiving a snapshot generation instruction for the first Android application;

Export the first basic resource information;

Calling the Ashmem kernel driver to export the first Ashmem resource information;

Calling the Binder kernel driver to export the first Binder resource information;

Generating a snapshot of the first Android application including the first basic resource information, the first Ashmem resource information, and the first Binder resource information;

Correspondingly store the snapshot of the first Android application and the first moment.
An Android application program migration device, characterized in that the device includes:

The basic resource management module is used to export the first basic resource information of the first Android application;

The Ashmem resource management module is used to call the first Ashmem kernel driver and export the first Ashmem resource information corresponding to the first Android application;

The Binder resource management module is used for the first Binder kernel driver to export the first Binder resource information corresponding to the first Android application;

A generating module, configured to generate a resource information set of the first Android application including the first basic resource information, the first Ashmem resource information, and the first Binder resource information;

The sending module is configured to send the resource information collection of the first Android application to a target computing node, so that the target computing node restores the basic resources of the first Android application based on the first basic resource information, and calls The second Ashmem kernel driver restores the Ashmem resource of the first Android application based on the first Ashmem resource information, calls the second Binder kernel driver, and restores the first Binder resource information based on the first Binder resource information. Binder resources for Android applications.
The device according to claim 9, wherein the sending module is further configured to send the resource information collection of the first Android application to a first computing node;

The basic resource management module is also used to detect whether the first Android application generates new basic resource information, and if it is detected that the first Android application generates new basic resource information, export the newly generated basic resource information;

The Ashmem resource management module is also used to detect whether the first Android application generates new Ashmem resource information, and if it is detected that the first Android application generates new Ashmem resource information, export the newly generated Ashmem resource information;

The Binder resource management module is also used to detect whether the first Android application generates new Binder resource information, and if it is detected that the first Android application generates new Binder resource information, export the newly generated Binder resource information;

The generating module is further configured to generate a new resource information set of the first Android application including the newly generated basic resource information, the newly generated Ashmem resource information, and the newly generated Binder resource information;

The sending module is further configured to send the newly added resource information set of the first Android application to the destination computing node.
An Android application program migration device, characterized in that the device is applied to a target computing node, and the device includes:

The acquiring module is used to acquire the resource collection of the first Android application sent by the original computing node, wherein the resource collection of the first Android application includes the first basic resource information of the first Android application, the first Ashmem resource information and first Binder resource information;

A basic resource management module, configured to restore the basic resources of the first Android application based on the first basic resource information;

The Ashmem resource management module is used to call the Ashmem kernel driver and restore the Ashmem resource of the first Android application based on the first Ashmem resource information;

The Binder resource management module is used to call the Binder kernel driver and restore the Binder resource of the first Android application based on the first Binder resource information.
The device according to claim 11, wherein the first basic resource information includes process information and file information of the first Android application;

The basic resource management module is used to:

Based on the process information, creating a process corresponding to the process information;

Based on the file information, a file corresponding to the file information is created in the file system.
The device according to claim 12, wherein the first Ashmem resource information includes target memory information of a shared memory shared by multiple processes of the first Android application and target file information of a shared file, and The target memory information includes attribute information and storage data of the shared memory shared by the multiple target processes, and the file corresponding to the file information includes the target shared file corresponding to the target file information;

The Ashmem resource management module is used for:

Create a target shared memory based on the target memory information, and configure the target shared memory based on the attribute information;

The storage data is written into the target shared memory and used as the file content data of the target shared file.
The device according to claim 12 or 13, wherein the first Binder resource information includes a communication connection between the client process of the first Android application and the server process of the second Android application Information, the process corresponding to the process information includes the client process of the first Android application;

The Binder resource management module is used to:

Based on the communication connection information, a communication connection between the client process and the server process of the second Android application in the target computing node is established.
A device for restoring a snapshot of an Android application program, wherein the method is applied to a computing node, and the device includes:

The receiving module is used to receive the snapshot restoration instruction at the first moment of the first Android application;

The acquiring module is configured to acquire a stored snapshot of the first Android application corresponding to the first moment, wherein the snapshot of the first Android application includes the first basic resource information and the first Android application of the first Android application. One Ashmem resource information and the first Binder resource information;

A basic resource management module, configured to restore the basic resources of the first Android application based on the first basic resource information;

The Ashmem resource management module is used to call the Ashmem kernel driver and restore the Ashmem resource of the first Android application based on the first Ashmem resource information;

The Binder resource management module is used to call the Binder kernel driver and restore the Binder resource of the first Android application based on the first Binder resource information.
The device according to claim 15, wherein the receiving module is further configured to:

At the first moment, receiving a snapshot generation instruction for the first Android application;

The basic resource management module is also used to export the first basic resource information;

The Ashmem resource management module is further configured to call the Ashmem kernel driver to export the first Ashmem resource information;

The Binder resource management module is further configured to call the Binder kernel driver to export the first Binder resource information;

The device further includes a generating module, configured to generate a snapshot of the first Android application including the first basic resource information, the first Ashmem resource information, and the first Binder resource information;

The device further includes a storage module for storing the snapshot of the first Android application program and the first moment in correspondence.
A computing node, characterized in that, the computing node includes a processor and a memory, and at least one instruction is stored in the memory, and the instruction is loaded and executed by the processor to implement claims as claimed in claim 1 to claim 2. The operations performed by the method for migrating Android applications, or the operations performed by the method for migrating Android applications as described in claim 3 to claim 6, or the operations performed by the method for migrating Android applications as described in claim 7 to claim 8, The operations performed by the method of recovering snapshots of Android apps.
A computer-readable storage medium, wherein at least one instruction is stored in the storage medium, and the instruction is loaded and executed by a processor to realize the migration of the Android application program according to claim 1 to claim 2. The operation performed by the method, or the operation performed by the method for migrating an Android application program as described in claim 3 to claim 6, or the method for restoring a snapshot of an Android application program as described in claim 7 to claim 8. The action performed.