Method and terminal for backing up and restoring application

Abstract

The invention discloses a method for backing up and restoring an application and a terminal. The application backup method comprises the steps that data to be backed up are determined through a cloud backup application, and whether the cloud backup application has the authority of calling a backup management service or not is judged through an expansion interface management service; if yes, forwarding the to-be-backed-up data to the backup management service through the expansion interface management service, so that the backup management service is bound with a to-be-backed-up application corresponding to the to-be-backed-up data; and creating a transmission channel between the cloud backup application and the to-be-backed-up application through the backup management service, and transmitting application data of the to-be-backed-up application to the cloud backup application based on the transmission channel so as to upload the application data to a cloud end for backup through the cloud backup application. According to the method, on the basis of a native application backup mechanism, authority management can be enhanced, and the backup restoration capability can be optimized.

Description

Technical Field

[0001] The present invention relates to the technical field of backup and restoration, and in particular to a method and terminal for backing up and restoring applications. Background Art

[0002] The Android native system provides a set of application data backup and restore mechanisms. Figure 1 As shown in the figure, the native backup and restore mechanism of the Android system is: 1. The BackupManagerService (backup management service) in the Framework (system framework) binds the BackupAgent (backup agent service) in the application to be backed up. BackupAgent is a natively defined public component, in which the backup interface has a default implementation, and personalized backup data is performed based on the backup interface. 2. The BackupManagerService binds the BackupTransport (backup transport service) in the cloud backup application. The cloud backup application must implement the backup interface in this BackupTransport by itself, and store the backed-up data and upload it to the cloud based on the backup interface. 3. The BackupManagerService creates a transmission channel and transmits the descriptor to the application to be backed up and the cloud backup application respectively. 4. The application to be backed up transmits its own private data to the BackupTransport of the cloud backup application through the BackupAgent.

[0003] The application to be backed up in the native backup and restore mechanism transmits data by itself, so there is no additional permission management. The application can only back up its own data, and the cloud backup application in the native backup and restore mechanism must be pre-installed in the burned image to allow the backup service to be used. Therefore, with the widespread application of the Android system in financial terminals and other fields, the backup and restore mechanism provided by the native system no longer meets the needs of many industry users in terms of security and backup and restore capabilities. Summary of the invention

[0004] The technical problem to be solved by the present invention is to provide a method and terminal for backing up and restoring applications, which can strengthen authority management and optimize backup and restoration capabilities based on the native application backup mechanism.

[0005] In order to solve the above technical problems, a technical solution adopted by the present invention is: A method for backing up an application, comprising: Determine the data to be backed up through the cloud backup application, and determine whether the cloud backup application has the authority to call the backup management service through the extended interface management service; If yes, forwarding the data to be backed up to the backup management service through the extended interface management service, so that the backup management service is bound to the application to be backed up corresponding to the data to be backed up; A transmission channel is created between the cloud backup application and the application to be backed up through the backup management service, and application data of the application to be backed up is transmitted to the cloud backup application based on the transmission channel, so that the application data is uploaded to the cloud for backup through the cloud backup application.

[0006] In order to solve the above technical problems, another technical solution adopted by the present invention is: A method for restoring an application, based on the above-mentioned method for backing up an application, comprises: Determine the data to be restored through the cloud backup application, and extend the interface management service to determine whether the cloud backup application has the authority to call the backup management service; If yes, forwarding the data to be restored to the backup management service through the extended interface management service, so that the backup management service is bound to the application to be restored corresponding to the data to be restored; A transmission channel is created between the cloud backup application and the application to be restored through the backup management service, and the application data downloaded from the cloud by the cloud backup application is transmitted to the application to be restored based on the transmission channel, so as to install the application to be restored based on the application data.

[0007] In order to solve the above technical problems, another technical solution adopted by the present invention is: A backup application terminal includes a first memory, a first processor, and a first computer program stored in the first memory and running on the first processor. When the first processor executes the first computer program, each step in the above-mentioned backup application method is implemented.

[0008] In order to solve the above technical problems, another technical solution adopted by the present invention is: A terminal for restoring an application includes a second memory, a second processor, and a second computer program stored in the second memory and running on the second processor. When the second processor executes the second computer program, each step in the above-mentioned method for restoring an application is implemented.

[0009] The beneficial effects of the present invention are as follows: a cloud backup application refers to an application that provides the function of backing up data to the cloud, and data to be backed up refers to an application that needs to back up data to the cloud. Before calling the backup management service, the cloud backup application controls the calling permissions of the cloud backup application through the extended interface management service, thereby improving the system's permission control over backup and restore data. At the same time, because the cloud backup application calls the backup management service through the extended interface management service, the cloud backup application can obtain the permissions of the backup management service through the extended interface management service as a normal application, without having to obtain permissions by presetting it in the burned image. The present invention adds an extended interface management service to the native backup and restore mechanism, which strengthens permission management and optimizes backup and restore capabilities without being affected by the native backup and restore mechanism, thereby effectively improving the compatibility of backup and restore. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] Figure 1 A schematic diagram of the architecture of a method for backing up an application described in the background technology; Figure 2 A flowchart of a method for backing up an application provided by an embodiment of the present invention; Figure 3 A schematic diagram of the architecture of a method for backing up an application provided by an embodiment of the present invention; Figure 4 A flowchart of a method for restoring an application provided by an embodiment of the present invention; Figure 5 A schematic diagram of the structure of a terminal for a backup application provided by an embodiment of the present invention; Figure 6 A schematic diagram of the structure of a terminal for restoring an application provided by an embodiment of the present invention; Description of labels: 100. A terminal for backup application; 101. A first memory; 102. A first processor; 200. A terminal for restore application; 201. A second memory; 202. A second processor. DETAILED DESCRIPTION

[0011] In order to explain the technical content, achieved objectives and effects of the present invention in detail, the following is an explanation in combination with the implementation modes and the accompanying drawings.

[0012] An embodiment of the present invention provides a method for backing up an application, comprising: Determine the data to be backed up through the cloud backup application, and determine whether the cloud backup application has the authority to call the backup management service through the extended interface management service; If yes, forwarding the data to be backed up to the backup management service through the extended interface management service, so that the backup management service is bound to the application to be backed up corresponding to the data to be backed up; A transmission channel is created between the cloud backup application and the application to be backed up through the backup management service, and application data of the application to be backed up is transmitted to the cloud backup application based on the transmission channel, so that the application data is uploaded to the cloud for backup through the cloud backup application.

[0013] From the above description, it can be seen that the beneficial effect of the present invention is that before calling the backup management service, the cloud backup application controls the calling authority of the cloud backup application through the extended interface management service, thereby improving the system's authority control over backup and restore data. At the same time, because the cloud backup application calls the backup management service through the extended interface management service, the cloud backup application can obtain the authority of the backup management service through the extended interface management service as a normal application, without having to obtain the authority by presetting it in the burned image. The present invention adds an extended interface management service to the native backup and restore mechanism. While strengthening authority management and optimizing backup and restore capabilities, it is not affected by the native backup and restore mechanism, effectively improving the compatibility of backup and restore.

[0014] Further, judging whether the cloud backup application has the authority to call the backup management service through the extended interface management service includes: Verifying the signature of the cloud backup application according to the calling application package name and signature fingerprint preset by the extended interface management service, and parsing the signature if the verification passes; If the parsing result includes a preset permission field, it is determined that the cloud backup application has the permission to call the backup management service.

[0015] From the above description, it can be seen that the cloud backup application is verified by the extended interface management service. When the cloud backup application's signature includes a permission field, it indicates that the cloud backup application has the permission to call the backup management service. The present invention controls the permissions of the caller, i.e., the cloud backup application, through the extended interface management service, so that the cloud backup application can be installed like a common application without pre-setting in advance, thereby improving the flexibility of the backup and restore mechanism.

[0016] Furthermore, before the backup management service is bound to the application to be backed up corresponding to the data to be backed up, the method further includes: Detecting, by means of the backup management service, whether the calling application package name and signature fingerprint of the extended interface management service are consistent with the preset caller information; If yes, allowing the backup management service to be bound to the application to be backed up corresponding to the data to be backed up; Otherwise, the backup management service is not allowed to be bound to the application to be backed up corresponding to the data to be backed up, and the backup is terminated.

[0017] From the above description, it can be seen that the backup management service verifies whether the caller identity of the extended interface management service conforms to the preset information, thereby implementing the control of the caller identity and improving the security of backup management.

[0018] Furthermore, the data to be backed up determined by the cloud backup application includes: The backup application package name of the application to be backed up is determined through the cloud backup application, and a backup file is created in the private data area of ​​the cloud backup application based on the application to be backed up to obtain the file descriptor of the backup file, and the backup application package name and the file descriptor are used as the data to be backed up.

[0019] From the above description, it can be seen that the backup application package name is included in the data to be backed up determined by the cloud backup application, so that different backup management can be performed for different applications later. At the same time, the backup file created by the cloud backup application for writing application data can only be stored in the private data area, which can effectively prevent data from being illegally obtained, thereby ensuring data security.

[0020] Further, creating a transmission channel between the cloud backup application and the application to be backed up through the backup management service includes: Through the backup management service, a transmission channel is created between the cloud backup application and the application to be backed up based on the file descriptor, so that the transmission data of the transmission channel is written into the backup file.

[0021] From the above description, it can be seen that the backup files are stored in the private data area of ​​the cloud backup application. In order to ensure that the application data transmitted by the backed up application can be stored in the private data area with higher security, a transmission channel is created based on the file descriptor to ensure that the application data can be written to the backup file and then stored in the private data area to improve data security.

[0022] Furthermore, before the backup management service is bound to the application to be backed up corresponding to the data to be backed up, the method further includes: Detecting whether the application identifier corresponding to the backup application package name is within the backup range configured by the backup management service; If the application identifier is within the backup range, detecting whether the backup application package name is included in the filter application list configured by the backup management service; If the backup application package name is not included, the backup management service is allowed to be bound to the application to be backed up corresponding to the data to be backed up.

[0023] From the above description, it can be seen that the backup management service is configured with an application backup scope and a filtered application list. The application backup scope limits the backup to only some applications whose application identifiers meet the requirements. The filtered application list limits the applications that the user does not want to be backed up, thereby implementing a customized backup strategy and permission management for backup applications, thereby improving backup security.

[0024] Further, transmitting the application data of the application to be backed up to the cloud backup application based on the transmission channel includes: Encrypting and compressing the application data of the application to be backed up; Packing the compressed application data into a file stream; The one file stream is written into the transmission channel for transmission to the cloud backup application.

[0025] From the above description, it can be seen that encrypting and compressing the application to be backed up and packaging it into a file stream for transmission effectively improves the data transmission efficiency, thereby improving the backup efficiency.

[0026] Another embodiment of the present invention provides a method for restoring an application, which is based on the above-mentioned method for backing up an application and includes: Determine the data to be restored through the cloud backup application, and determine whether the cloud backup application has the authority to call the backup management service through the extended interface management service; If yes, forwarding the data to be restored to the backup management service through the extended interface management service, so that the backup management service is bound to the application to be restored corresponding to the data to be restored; A transmission channel is created between the cloud backup application and the application to be restored through the backup management service, and the application data downloaded from the cloud by the cloud backup application is transmitted to the application to be restored based on the transmission channel, so as to install the application to be restored based on the application data.

[0027] From the above description, it can be seen that the beneficial effect of the present invention is that before calling the backup management service, the cloud backup application controls the calling authority of the cloud backup application through the extended interface management service, thereby improving the system's authority control over backup and restore data. At the same time, because the cloud backup application calls the backup management service through the extended interface management service, the cloud backup application does not need to be pre-installed in the burned image, and it is allowed to obtain backup and restore data through the extended interface management service as a normal application. The present invention adds an extended interface management service to the native backup and restore mechanism. While strengthening authority management and optimizing backup and restore capabilities, it is not affected by the native backup and restore mechanism, effectively improving the compatibility of backup and restore.

[0028] Another embodiment of the present invention provides a terminal for backup application, including a first memory, a first processor, and a first computer program stored in the first memory and running on the first processor, and the first processor implements each step of the above-mentioned method for backup application when executing the first computer program.

[0029] Another embodiment of the present invention provides a terminal for restoring an application, comprising a second memory, a second processor, and a second computer program stored in the second memory and running on the second processor, wherein the second processor implements each step of the above-mentioned method for restoring an application when executing the second computer program.

[0030] The above-mentioned method and terminal for backing up and restoring applications of the present invention can be applied to the Android native system, which can strengthen the permission management and optimize the backup and restoration capabilities based on the native application backup mechanism, and is described below through specific implementation methods: Please refer to Figure 2 and Figure 3 , Embodiment 1 of the present invention is: A method for backing up an application, comprising: S110: Determine the data to be backed up through the cloud backup application, and determine whether the cloud backup application has the authority to call the backup management service through the extended interface management service.

[0031] It should be noted that the extended interface management service (Titan) is used to transfer and manage all extended system service interfaces. Since the backup management service (BackupManagerService) in the system framework will extend many interfaces provided to cloud backup applications, if different services implement interface permission management separately, there will be a large number of redundant resources in the system and the permission management will not be unified. Therefore, a customized extended interface management service (Titan) is used to provide applications with a unified system extended interface service.

[0032] In some embodiments, since the cloud backup application is a common application and is allowed to be installed in the terminal after the system leaves the factory, before step S1, the cloud backup application needs to apply for the calling permission of the extended interface management service (Titan) through the specified application instruction Titan.extperm.BACKUP_[GET / SET].

[0033] Specifically, in step S110, the data to be backed up is determined by the cloud backup application including: S1101. Determine a backup application package name of an application to be backed up through a cloud backup application, create a backup file in a private data area of ​​the cloud backup application based on the application to be backed up, obtain a file descriptor of the backup file, and use the backup application package name and the file descriptor as data to be backed up.

[0034] It should be noted that the application to be backed up must be an application installed in the system data area. That is, the cloud backup application is only allowed to back up applications installed in the system data area. Among them, backup processing is not allowed for applications that are pre-installed in the burn-in image but the upgraded version is installed in the system data area. The backup files written by the backup management service can only be stored in the specified directory of the private data area of ​​the cloud backup application, and cannot be stored in the SD (secure memory) card storage area. If the backup file is to be shared to the SD card storage area, the cloud backup application needs to move the backup file for storage. The file format of the backup file is the same as the native data, which allows you to choose whether to compress the backup file, whether to encrypt it with the passed password, and whether to include the application installation package for installation during restore, and other selection mechanisms.

[0035] Specifically, in step S110, judging whether the cloud backup application has the authority to call the backup management service through the extended interface management service includes: S1102: Verify the signature of the cloud backup application according to the calling application package name and signature fingerprint preset by the extended interface management service, and if the verification passes, parse the signature.

[0036] S1103: If the parsing result includes a preset permission field, it is determined that the cloud backup application has permission to call the backup management service.

[0037] In some embodiments, the extended interface management service (Titan) defines a permission field for using the backup interface. If the cloud backup application wants to use this permission, the cloud backup application needs to set the permission field in the signature body when signing. The extended interface management service (Titan) verifies the signature body of the cloud backup application. After the verification passes, the permission field is parsed out, and the cloud backup application is considered to have the permission to call the backup interface. At this time, the backup interface of the backup management service (BackupManagerService) is called by the extended interface management service (Titan).

[0038] In some embodiments, if the parsing result does not include a preset permission field, it is determined that the cloud backup application does not have permission to call the backup management service, the backup is stopped, and application backup failure information is returned.

[0039] It should be noted that the cloud backup application can directly access public files such as camera pictures and videos on the SD card storage area, so the system framework does not need to customize the backup and restore interface of this type of data. In addition, the cloud backup application can call the getAppSizeInfo interface of the extended interface management service (Titan) to query the size of the application package and the storage space occupied by the data, so as to estimate the transmission time and the remaining available storage space based on the size of the application package. When the available storage space in the system data area is less than 150M, triggering backup and restore is not allowed to avoid the storage space being full.

[0040] S120: If yes, forwarding the data to be backed up to the backup management service through the extended interface management service, so that the backup management service is bound to the application to be backed up corresponding to the data to be backed up.

[0041] In some embodiments, the extended interface management service (Titan) forwards the file descriptor of the backup file and the backup application package name of the application to be backed up to the backup management service (BackupManagerService).

[0042] In some embodiments, only one application can be backed up at one time and only one backup file is generated.

[0043] Specifically, before the backup management service is bound to the application to be backed up corresponding to the data to be backed up, the method further includes: S210: Detect, through the backup management service, whether the calling application package name and signature fingerprint of the extended interface management service are consistent with preset caller information.

[0044] S220: If yes, allow the backup management service to be bound to the application to be backed up corresponding to the data to be backed up.

[0045] S230: Otherwise, the backup management service is not allowed to be bound to the application to be backed up corresponding to the data to be backed up, and the backup is terminated.

[0046] In some embodiments, the extended interface management service (Titan) acts as a proxy and manager of the system extended interface, which specifies the application package name and signature fingerprint of the system extended interface. The backup management service (BackupManagerService) checks the package name and signature fingerprint of the extended interface management service (Titan) to prevent other services from proxying the extended interface. In addition, since the interface extended by the system framework (Framework) is provided to general applications through the extended interface management service (Titan), it also allows other system applications to call it. For the permission management of other system applications, it is checked through the native application signature mechanism, that is, the system application needs to declare its permissions and obtain the permission to call the extended interface only after signing with the platform key.

[0047] S130: Create a transmission channel between the cloud backup application and the application to be backed up through the backup management service, and transmit the application data of the application to be backed up to the cloud backup application based on the transmission channel, so as to upload the application data to the cloud for backup through the cloud backup application.

[0048] Specifically, in step S130, creating a transmission channel between the cloud backup application and the application to be backed up by the backup management service includes: S1301. Through the backup management service, create a transmission channel between the cloud backup application and the application to be backed up based on the file descriptor, so that transmission data of the transmission channel is written into the backup file.

[0049] In some embodiments, the cloud backup application and the application to be backed up use the native BackupAgent transmission method. It should be noted that since the backup data is transmitted by the application to be backed up itself, it is not necessary to use root permissions to read it. Therefore, for applications that declare "android:allowBackup="false" that do not allow backup, the backup application method based on the present invention can also achieve forced backup.

[0050] In some embodiments, if the application to be backed up uses the native android:fullBackupContent declaration to include and filter the backup file rules, the corresponding rules should be followed during the backup process. android:fullBackupContent is an attribute pointing to an XML file that lists in detail which files or directories the application should include during the automatic backup process. If the application uses this declaration to specify the files and directories to be backed up, the system needs to include the specified files and directories when backing up, thereby preventing the application from backing up data out of bounds.

[0051] Specifically, in step S130, transmitting the application data of the application to be backed up to the cloud backup application based on the transmission channel includes: S1302: Encrypt and compress the application data of the application to be backed up.

[0052] S1303: Pack the compressed application data into a file stream.

[0053] S1304: Write the one file stream into the transmission channel for transmission to the cloud backup application.

[0054] In some embodiments, during the process of backing up the application to be backed up, all processes of the application to be backed up need to be terminated. If the application to be backed up is in use, the backup operation should not be triggered.

[0055] Please refer to Figure 3 , Embodiment 2 of the present invention is: A method for backing up an application, which is different from the first embodiment in that: Before the backup management service is bound to the application to be backed up corresponding to the data to be backed up, the method further includes: S240: Detect whether the application identifier corresponding to the backup application package name is within the backup range of the backup management service configuration.

[0056] In some embodiments, the backup scope specifically includes common applications whose application identifier UID is greater than or equal to 10,000.

[0057] S250: If the application identifier is within the backup range, detecting whether the list of filtered applications configured by the backup management service contains the backup application package name.

[0058] S260: If the backup application package name is not included, allowing the backup management service to be bound to the application to be backed up corresponding to the data to be backed up.

[0059] In some embodiments, two configuration items are added to the configuration list of the system framework, one of which is the backup function switch, and the other is the filter application list switch. These two configuration items are read-only data and do not allow dynamic modification. Among them, the backup function switch is turned off by default to prevent malicious programs from obtaining the privacy data of applications through the backup mechanism. It can only be enabled when the user has customized requirements.

[0060] Please refer to Figure 4 , Embodiment 3 of the present invention is: A method for restoring an application, based on the method for backing up an application in the first or second embodiment, comprises: S310: Determine the data to be restored through the cloud backup application, and extend the interface management service to determine whether the cloud backup application has the authority to call the backup management service.

[0061] S320: If yes, forwarding the data to be restored to the backup management service through the extended interface management service, so that the backup management service is bound to the application to be restored corresponding to the data to be restored.

[0062] S330: Create a transmission channel between the cloud backup application and the application to be restored through the backup management service, and transmit the application data downloaded from the cloud by the cloud backup application to the application to be restored based on the transmission channel, so as to install the application to be restored based on the application data.

[0063] In some embodiments, the application data to be restored can only be stored in a specified directory in the private data area of ​​the cloud backup application, and cannot be stored in the SD card storage area.

[0064] In some embodiments, if the application to be restored has been installed, first check whether the signature of the installed application is consistent with the record information of the application to be restored. If they are consistent, clear the old data of the installed application and then import the application data into the installed application.

[0065] In some embodiments, if the application data of the application to be restored contains an application installation package, the installation process will be automatically executed if the application to be restored is not installed. If the installed application version is lower than the version of the application to be restored, the update installation process will also be executed.

[0066] A method for restoring an application in this embodiment corresponds to a method for backing up an application in the second embodiment, except that after the transmission channel is established, the backup data is transmitted from the cloud backup application to the application to be restored.

[0067] Please refer to Figure 5 , Embodiment 4 of the present invention is: A terminal 100 for a backup application includes a first memory 101, a first processor 102, and a first computer program stored in the first memory 101 and running on the first processor 102. When the first processor 102 executes the first computer program, each step in a method for a backup application in the above-mentioned embodiment 1 or embodiment 2 is implemented.

[0068] Please refer to Figure 6 , Embodiment 5 of the present invention is: A terminal 200 for restoring an application includes a second memory 201, a second processor 202, and a second computer program stored in the second memory 201 and running on the second processor 202. When the second processor 202 executes the second computer program, each step in the method for restoring an application in the above-mentioned embodiment 3 is implemented.

[0069] In summary, the present invention provides a method and terminal for backing up and restoring applications, which extends the backup interface in the native backup management service so that the backup function is not affected by the native backup function. At the same time, the application and permissions that call the backup interface are managed and controlled through the extended interface management service, thereby improving the backup security. At the same time, the extended interface management service can identify applications that users do not want to be backed up, so it can meet the user's customized backup needs and improve the flexibility of application backup. In addition, since the cloud backup application calls the backup management service through the extended interface management service, the cloud backup application can obtain the permissions of the backup management service through the extended interface management service as a normal application, without the need to obtain permissions by pre-setting the burned image, thereby simplifying the application backup process. The present invention adds an extended interface management service to the native backup and restore mechanism. While strengthening permission management and optimizing backup and restore capabilities, it is not affected by the native backup and restore mechanism, effectively improving the compatibility of backup and restore.

[0070] The above descriptions are merely embodiments of the present invention and are not intended to limit the patent scope of the present invention. Any equivalent transformations made using the contents of the present invention's specification and drawings, or directly or indirectly applied in related technical fields, are also included in the patent protection scope of the present invention.

Claims

1. A method for backing up an application, characterized in that: include: Determine the data to be backed up through the cloud backup application, and determine whether the cloud backup application has the authority to call the backup management service through the extended interface management service; If yes, forwarding the data to be backed up to the backup management service through the extended interface management service, so that the backup management service is bound to the application to be backed up corresponding to the data to be backed up; A transmission channel is created between the cloud backup application and the application to be backed up through the backup management service, and application data of the application to be backed up is transmitted to the cloud backup application based on the transmission channel, so that the application data is uploaded to the cloud for backup through the cloud backup application.

2. A method for backing up an application according to claim 1, characterized in that: Determining whether the cloud backup application has the authority to call the backup management service through the extended interface management service includes: Verifying the signature of the cloud backup application according to the calling application package name and signature fingerprint preset by the extended interface management service, and parsing the signature if the verification passes; If the parsing result includes a preset permission field, it is determined that the cloud backup application has the permission to call the backup management service.

3. A method for backing up an application according to claim 2, characterized in that: Before the backup management service is bound to the application to be backed up corresponding to the data to be backed up, the method further includes: Detecting, by means of the backup management service, whether the calling application package name and signature fingerprint of the extended interface management service are consistent with the preset caller information; If yes, allowing the backup management service to be bound to the application to be backed up corresponding to the data to be backed up; Otherwise, the backup management service is not allowed to be bound to the application to be backed up corresponding to the data to be backed up, and the backup is terminated.

4. A method for backing up an application according to claim 1, characterized in that: The data to be backed up through the cloud backup application includes: The backup application package name of the application to be backed up is determined through the cloud backup application, and a backup file is created in the private data area of ​​the cloud backup application based on the application to be backed up, and the file descriptor of the backup file is obtained, and the backup application package name and the file descriptor are used as the data to be backed up.

5. A method for backing up an application according to claim 4, characterized in that: Creating a transmission channel between the cloud backup application and the application to be backed up by the backup management service includes: Through the backup management service, a transmission channel is created between the cloud backup application and the application to be backed up based on the file descriptor, so that the transmission data of the transmission channel is written into the backup file.

6. A method for backing up an application according to claim 4, characterized in that: Before the backup management service is bound to the application to be backed up corresponding to the data to be backed up, the method further includes: Detecting whether the application identifier corresponding to the backup application package name is within the backup range configured by the backup management service; If the application identifier is within the backup range, detecting whether the backup application package name is included in the filter application list configured by the backup management service; If the backup application package name is not included, the backup management service is allowed to be bound to the application to be backed up corresponding to the data to be backed up.

7. A method for backing up an application according to claim 1, characterized in that: Transmitting the application data of the application to be backed up to the cloud backup application based on the transmission channel includes: Encrypting and compressing the application data of the application to be backed up; Packing the compressed application data into a file stream; The one file stream is written into the transmission channel for transmission to the cloud backup application.

8. A method for restoring an application, characterized in that: A method for restoring a backup application according to any one of claims 1 to 7, comprising: Determine the data to be restored through the cloud backup application, and determine whether the cloud backup application has the authority to call the backup management service through the extended interface management service; If yes, forwarding the data to be restored to the backup management service through the extended interface management service, so that the backup management service is bound to the application to be restored corresponding to the data to be restored; A transmission channel is created between the cloud backup application and the application to be restored through the backup management service, and the application data downloaded from the cloud by the cloud backup application is transmitted to the application to be restored based on the transmission channel, so as to install the application to be restored based on the application data.

9. A terminal for backup application, comprising a first memory, a first processor, and a first computer program stored in the first memory and running on the first processor, characterized in that: When the first processor executes the first computer program, each step in the method for backing up an application as described in any one of claims 1 to 8 is implemented.

10. A terminal for restoring an application, comprising a second memory, a second processor, and a second computer program stored in the second memory and running on the second processor, characterized in that: When the second processor executes the second computer program, the steps of the method for restoring an application as claimed in claim 9 are implemented.

Images