WO2011143852A1 - 应用程序的管理方法和装置、以及终端 - Google Patents

应用程序的管理方法和装置、以及终端 Download PDF

Info

Publication number
WO2011143852A1
WO2011143852A1 PCT/CN2010/076002 CN2010076002W WO2011143852A1 WO 2011143852 A1 WO2011143852 A1 WO 2011143852A1 CN 2010076002 W CN2010076002 W CN 2010076002W WO 2011143852 A1 WO2011143852 A1 WO 2011143852A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal
application
file
specified
format
Prior art date
Application number
PCT/CN2010/076002
Other languages
English (en)
French (fr)
Inventor
丁莹
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Priority to AU2010353673A priority Critical patent/AU2010353673B2/en
Priority to EP10851610.5A priority patent/EP2521034B1/en
Priority to US13/576,168 priority patent/US8555060B2/en
Publication of WO2011143852A1 publication Critical patent/WO2011143852A1/zh

Links

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/07Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/14Error detection or correction of the data by redundancy in operation
    • G06F11/1402Saving, restoring, recovering or retrying
    • G06F11/1446Point-in-time backing up or restoration of persistent data
    • G06F11/1458Management of the backup or restore process
    • G06F11/1469Backup restoration techniques
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44Arrangements for executing specific programs
    • G06F9/448Execution paradigms, e.g. implementations of programming paradigms
    • G06F9/4488Object-oriented
    • G06F9/4493Object persistence

Definitions

  • the present invention relates to the field of communications, and in particular, to an application management method and apparatus, and a terminal. Background technique
  • JAVA virtual machines have become a required configuration for most mobile terminals. Due to the existence of the JAVA virtual machine, the user can install the required JAVA application on the terminal using the JAVA virtual machine as a platform.
  • a JAVA application management module is provided in the mobile terminal for displaying and managing the stored or installed application, and can also be used to provide functions such as starting, installing, updating, deleting, setting, and the like of the application.
  • the current JAVA application management module does not enable JAVA applications to be backed up and restored on different terminals.
  • J2ME Java2 Micro Edition
  • JAVA 2 Micro Edition each JAVA virtual machine manufacturer needs to provide a suitable application programming interface (API).
  • API application programming interface
  • the current standard does not specify how JAVA application information is stored. Therefore, after installing an application using different JAVA virtual machines (that is, different JAVA platforms), various related information of the application (for example, database information, security) Setting information, etc.)
  • the storage structure in the file system is different. With simple backup and recovery, it is impossible to make the application meet the requirements of cross-platform operation.
  • the terminal can also use other application running environments, and there is also the problem that the application cannot be backed up and restored between different platforms developed in the same application environment.
  • the present invention provides an application management method and apparatus, and a terminal, in which the application cannot be backed up and run across platforms, and the limitation of the application is large, which causes inconvenience to the user to use the application normally.
  • the present invention provides an application management method for ensuring that a terminal of various operating platforms in an operating environment having the application can restore and run the managed application.
  • the management method of the application includes: the first terminal converts a file of the specified application saved by itself into an intermediate file of a predetermined intermediate format, wherein the intermediate format can be recognized by another terminal having an operating environment of the application The first terminal performs backup management on the specified application by storing the intermediate file to the specified storage location, so that the second terminal can restore the backed up application, wherein the second terminal and the first terminal both have the application Operating environment.
  • the method further includes: the second terminal recovering and managing the specified application by converting the intermediate file into a file of a specified format required by the second terminal, and storing the file of the specified format to the second terminal.
  • storing the intermediate file to the specified storage location further includes: the first terminal storing the predetermined type of identification information from the first terminal to the specified storage location; wherein the identifier information is used for verifying the second terminal.
  • the method further includes: acquiring, by the second terminal, the identification information of the predetermined type, determining whether the acquired identification information of the second terminal is the same as the identification information stored at the specified storage location; If it is determined to be the same, the second terminal is allowed to run the specified application that has undergone recovery management; if it is determined to be different, the second terminal is prohibited from running the specified application that has undergone recovery management.
  • the identifier information of the predetermined type includes one of the following: identifier information of the first terminal, and identifier information of the SIM card of the user identity module on the first terminal.
  • storing the intermediate file to the specified storage location further includes: encrypting the converted intermediate file according to a predetermined encryption algorithm, and the file subsequently stored to the specified storage location is the encrypted file.
  • the method further includes: decrypting the encrypted intermediate file, and converting the file converted to the specified format by the second terminal to the decrypted file when the management is resumed.
  • an application management method for ensuring that a terminal of various operating platforms in an operating environment having the application can restore and run the managed application.
  • the management method of the application program includes: the second terminal converts the intermediate file converted to the predetermined intermediate format stored at the specified storage location into a file of the specified format required by the second terminal, wherein the intermediate file is first
  • the terminal converts the file of the specified application, and the second terminal and the first terminal both have an operating environment of the application, and the intermediate format can be recognized by another terminal having an operating environment of the application; Save the converted file to the specified format for recovery management of the specified application.
  • an application management apparatus for ensuring that a terminal of various operating platforms in an operating environment having the application can restore and run the managed application.
  • the management device of the application includes: a conversion module, configured to convert a file of a specified application saved by the first terminal into an intermediate file of a predetermined intermediate format, wherein the intermediate format can be provided with an operating environment of the application
  • the other terminal identifies the storage module, and is configured to perform backup management on the specified application by storing the intermediate file to the specified storage location, so that the second terminal can restore the application, where the second terminal and the first terminal respectively have the The operating environment of the application.
  • the conversion module is further configured to convert the intermediate file into a file of a specified format required by the second terminal; the storage module is further configured to perform recovery management on the specified application by storing the file converted to the specified format to the second terminal.
  • the storage module is further configured to: store the predetermined type of identification information from the first terminal to the specified storage location; wherein the identifier information is used to verify the second terminal;
  • the device further includes: a detecting module, configured to acquire, according to the predetermined type of identification information, a second type of identification information, and determine whether the acquired identification information of the second terminal is the same as the identification information stored at the specified storage location; Allowing the second terminal to run the specified application that has undergone recovery management; if it is determined to be different, the second terminal is prohibited from running the specified application that has undergone recovery management.
  • a detecting module configured to acquire, according to the predetermined type of identification information, a second type of identification information, and determine whether the acquired identification information of the second terminal is the same as the identification information stored at the specified storage location; Allowing the second terminal to run the specified application that has undergone recovery management; if it is determined to be different, the second terminal is prohibited from running the specified application that has undergone recovery management.
  • the identifier information of the predetermined type includes one of the following: identifier information of the first terminal, and identifier information of the SIM card of the user identity module on the first terminal.
  • the device may further include: an encryption and decryption module, configured to encrypt the intermediate file according to a predetermined encryption algorithm before the storage module stores the intermediate file to the specified storage location, and the file stored by the storage module to the specified storage location is the encrypted middle
  • the file is also used to decrypt the encrypted file, and is converted into a file of the specified format by the conversion module when the management is resumed. The file obtained for decryption.
  • an application management apparatus for ensuring that terminals of various operating platforms in an operating environment having the application are capable of restoring and running the managed application.
  • the management device of the application program includes: a conversion module, configured to convert an intermediate file of a predetermined intermediate format into a file of a specified format required by the second terminal, wherein the intermediate file is used by the first terminal to the specified application
  • the file is formatted, and the second terminal and the first terminal both have an operating environment of the application, and the intermediate format can be recognized by other terminals having an operating environment of the application
  • the saving module is configured to be converted into a specified
  • the formatted file is stored to the second terminal for recovery management of the specified application.
  • the present invention also provides a terminal which can include the above-described management apparatus of the application according to the present invention.
  • the invention realizes universal backup management for the application by converting the application that needs to be backed up into an intermediate format that can be identified by a predetermined and different terminal platform, so that the terminal of the application needs to restore the intermediate format of the application. Convert to their respective required format to restore and use the application.
  • FIG. 1 is a flowchart of a method for managing an application according to an embodiment of the present invention
  • FIG. 2 is a flowchart showing a process of applying an application backup method according to the present embodiment to a terminal of a J2ME environment of JAVA after performing application backup;
  • FIG. 3 is a flowchart showing a process of applying the management method of the application according to the present embodiment to the terminal of the JA2 J2ME environment after the application is restored;
  • FIG. 4 is a flowchart showing a process of applying the management method of the application according to the present embodiment to the application running after the terminal of the JA2 J2ME environment;
  • FIG. 5 is a block diagram of an apparatus for managing an application according to an embodiment of the present invention
  • FIG. 6 is a block diagram of various functional modules on a terminal after terminal of a J2ME environment in which a management device of an application according to an embodiment of the present invention is used;
  • Fig. 7 shows a specific example of the storage manner of a file converted to an intermediate structure. detailed description
  • the present invention proposes to convert an application that needs to be backed up into a pre-defined intermediate format, in view of the problem that the application cannot be cross-platformed and run, which causes the application to be used in a large degree and causes inconvenience to the user to use the application normally.
  • Different terminal platforms can recognize the intermediate format and convert the intermediate format file into a format required by each, so that the application can be restored and used normally.
  • an application management method for ensuring that a terminal of various operating platforms in an operating environment having the application can restore and run the managed application.
  • the management method of the application according to this embodiment includes:
  • Step S101 The first terminal converts the file of the specified application saved by the first terminal into an intermediate file of a predetermined intermediate format, wherein the intermediate format can be recognized by other terminals having the running environment of the application (for example, a common file can be selected)
  • the format is as an intermediate format).
  • Step S103 The first terminal stores the intermediate file to the specified storage location (wherein the specified storage location may be a preset memory in the terminal, or may be a memory external to the terminal, such as a memory card external to the terminal)
  • the program performs backup management, so that the second terminal can restore the backed up application, wherein the second terminal and the first terminal both have an operating environment of the application (that is, as long as the first terminal and the second terminal have the same The operating environment of the application, even if the second terminal is different from the platform of the first terminal, the second terminal can also identify and restore the backed up application).
  • the application that needs to be backed up can be converted into a pre-specified and different The intermediate format that the terminal platform can recognize, thereby implementing universal backup management for the application, so that the terminal that needs to restore the application converts the file in the intermediate format into the format required by each, even if the second terminal and the first terminal
  • Different running platforms can also restore and normal use of applications backed up by the first terminal.
  • the file (intermediate file) stored at the specified storage location is converted into a file of a specified format required by the second terminal of the specified application, and the file of the specified format is stored to the first
  • the second terminal manages the recovery of the specified application. After that, the second terminal can use the restored application normally.
  • the operating environments of the first terminal and the second terminal are both J2ME environments of JAVA, but the operating platforms of the first terminal and the second terminal may be different, that is, The first terminal is different from the virtual machine of the second terminal, but since the backed up file is an intermediate format that the second terminal can recognize, the second terminal can convert and restore the backed up file, thereby performing recovery management on the application.
  • the JAVA application sequence listing interface is used for the user to select an application to be backed up; in step cl, the file can be encrypted before being stored in the external memory.
  • the terminal can also specify which applications need to be backed up or restored by default.
  • the process of storing the intermediate file to the specified storage location may further comprise: storing the predetermined type of identification information from the first terminal to the designated storage location, the identification information being used to authenticate the second terminal. Also, the identification information can be converted to the intermediate format and stored at the specified storage location.
  • the predetermined type of identification information may be acquired from the second terminal in advance, and the acquired identification information of the second terminal and the storage location of the specified storage location are determined. Whether the identification information is the same; if it is determined to be the same, the second terminal is allowed to run the specified application that has undergone recovery management; if it is determined to be different, the second terminal is prohibited from running the specified application that has undergone recovery management.
  • the new version of the platform is different from the application storage mode of the old version of the platform, so the new platform cannot be used under the original platform.
  • the saved application may be the identification information of the terminal (for example, the identification information may be IMSI, the certificate information of the terminal, and the like, which can uniquely identify the terminal), or may be the user identity module SIM card on the terminal.
  • Identification information for example, a telephone number of the terminal or a unique identifier of the SIM card
  • the first terminal and the second terminal are different terminals (for example, the user replaces the first terminal used by the second terminal), ie, the user The application on the first terminal needs to be restored to the second terminal.
  • the identity of the terminal itself changes, but the user usually does not replace the SIM card of the user identity module. Therefore, the user can
  • the identification information of the SIM card (for example, the telephone number of the terminal or the unique identifier of the SIM card) is used as a reference for a risk certificate.
  • terminal A is the terminal that originally installed the application, and then terminal A performs backup management on the application, and is terminated by the terminal.
  • B restores the application; thereafter, after completing the recovery, the terminal B performs backup management of the application, and the terminal C restores the application backed by the terminal B.
  • the terminal B performs the recovery management.
  • the SIM card telephone number X of the terminal A is stored in the terminal B, and before the terminal B runs the application, the verification is performed based on the stored SIM card telephone number X and the SIM card number carried on the terminal B, if the verification is not Pass, then prohibit terminal B from running the application.
  • the terminal B when the terminal B backs up the application, the file of the application is also backed up and the phone number X is stored at the same time.
  • the terminal C After the terminal B backs up the application, the terminal C will perform the recovery management, and the SIM card number will be X is stored in the terminal C, and before the terminal C runs the application, the verification is performed based on the stored SIM card phone number X and the SIM card number carried on the terminal C. If the verification fails, the terminal C is prohibited from running the application. application. That is to say, in the case of multiple backups and restores, when verifying each terminal, it is possible to refer to the identifier saved when the application is first installed.
  • the file converted to the intermediate format (ie, the intermediate file) may be encrypted according to a predetermined encryption algorithm, and then the encrypted file is stored to the specified storage. Storage location.
  • the encrypted intermediate file should first be decrypted according to the algorithm used in the encryption, and then the decrypted file is converted into the specified file.
  • the format is stored and stored to the second terminal, thereby completing the recovery of the application.
  • the user may be prompted to perform operation selection and perform corresponding operations according to the user's selection, thereby achieving the purpose of resolving the conflict. For example, if the user ignores according to the provided selection, the application is stopped to be restored; if the user selects replacement, the application currently installed on the second terminal is replaced with the application of the backup; if the user selects to increase, the application of the backup is added to the first Two terminal system.
  • Fig. 2 is a flow chart showing the processing of application backup after the application management method of the present embodiment is applied to the terminal of the J2ME environment of JAVA.
  • Step 201 Determine that the user selects one or more JAVA applications that need to be backed up.
  • Step 203 Extract the mobile terminal phone number (as the identification information referenced during verification) of the first installation of the JAVA application.
  • Step 204 Store the information obtained in step 202 and step 203 according to the intermediate format shown in FIG. 7 and save the file to the file system.
  • Step 205 Encrypt the file generated by step 204.
  • Step 206 Move the encrypted file to the removable memory card.
  • FIG. 3 is a flow chart showing the processing of application recovery after the application management method of the present embodiment is applied to the terminal of the J2ME environment of JAVA. As shown in FIG. 3, the following processes are specifically included:
  • Step 201 Insert the mobile memory card with the backup file into the terminal.
  • Step 302 Decrypt the backup file.
  • Step 303 Determine whether the decryption is successful. If successful, save the decrypted file to the file system, and execute step 304; if not, exit, and the process ends.
  • Step 304 Read information from the decrypted data according to the format of FIG.
  • Step 305 listing the JAVA application in the backup for the user to select the JAVA application that needs to be restored.
  • Step 306 Convert the information of the JAVA application that needs to be restored, and save the format required by the currently used JAVA virtual machine.
  • Step 307 Add a JAVA application to the terminal; if it detects that the same application already exists in the mobile phone, ask the user to perform an operation of adding, ignoring, or replacing the application; if the user selects to add, add the restored application to Terminal; If the user chooses to ignore, the application will not be restored. If the user chooses to replace, the application on the current terminal is replaced with the restored application.
  • Step 308 Associate the backed up JAVA application with the terminal phone number of the first installation of the application, that is, record the terminal phone number of the application source.
  • Fig. 4 is a flow chart showing the processing of verifying the terminal when the application management method according to the present embodiment is applied to the terminal of the JA2 J2ME environment and the restored application is run. As shown in Figure 4, the following steps are specifically included:
  • Step 401 Determine whether the phone number associated with the JAVA application (ie, the phone number recorded when the application was restored) matches the mobile terminal (the phone number of the mobile terminal), and if yes, perform step 402; if not, end the process. .
  • Step 402 running the JAVA application.
  • the backup application can also It was successfully restored to various JAVA terminals, thus achieving cross-platform recovery and operation of the application.
  • the application that needs to be backed up can be converted into an intermediate format that can be recognized by a predetermined and different terminal platform, thereby implementing universal backup management for the application, and the terminal that needs to restore the application can be the intermediate format.
  • the files are converted to their respective required formats to restore and use the application normally; and, by encrypting the files stored in the backup, the security of the backup files can be further improved; in addition, by prompting the user to perform the application recovery process
  • the conflict resolution method can ensure the stability and reliability of the application recovery.
  • the above processing can realize the universal backup and application recovery between different platforms in the J2ME environment of JAVA, and is also applicable to other environments such as Windows Mobile Pocket. A variety of platforms, with a wide range of practicality.
  • a management device for an application there is also provided a management device for an application.
  • the management device of the application includes: a conversion module 51, configured to convert a file of a specified application saved by the first terminal into an intermediate file of a predetermined intermediate format, where the intermediate format Can be identified by other terminals that have the operating environment of the application;
  • the storage module 52 is connected to the conversion module 51, configured to perform backup management on the specified application by storing the intermediate file to the specified storage location, so that the second terminal can restore the application, where the second terminal and the first terminal are both Have the operating environment of the application.
  • the application that needs to be backed up can be converted into an intermediate format that can be recognized by a predetermined and different terminal platform, thereby implementing universal backup management for the application, so that the terminal that needs to restore the application can be the middle
  • the formatted files are converted to their respective required formats to restore and function properly.
  • the conversion module 51 is further configured to convert the intermediate file into a second terminal (the second terminal is required to restore the terminal of the specified application)
  • the file of the specified format
  • the storage module 52 is further configured to perform recovery management on the specified application by storing the file converted to the specified format to the second terminal.
  • the storage module 52 is further configured to store the predetermined type of identification information from the first terminal to the specified storage location, wherein the identification information is used for verifying the second terminal, in order to verify the terminal running the restored application.
  • the device may further include: a detecting module (not shown), configured to acquire, from the second terminal, the identification information of the predetermined type, and determine whether the acquired identification information of the second terminal is the same as the identification information stored at the specified storage location; If the determination is the same, the second terminal is allowed to run the specified application that has undergone recovery management; if it is determined to be different, the second terminal is prohibited from running the specified application that has been restored and managed, so that the copyright of the application can be effectively maintained.
  • a detecting module (not shown), configured to acquire, from the second terminal, the identification information of the predetermined type, and determine whether the acquired identification information of the second terminal is the same as the identification information stored at the specified storage location; If the determination is the same, the second terminal is allowed to run the specified application that has undergone recovery management; if it is determined to be different, the second terminal is prohibited from running the specified application that has been restored and managed, so that the copyright of the application can be effectively maintained.
  • the foregoing predetermined type of identification information may include one of the following: the identification information of the first terminal, and the identification information of the SIM card of the user identity module on the first terminal.
  • the identification information of the terminal or the identification information of the SIM card may be used as the identifier to be used for verification, in the case that the second terminal and the first terminal are different terminals. Then, the identification information of the terminal or the SIM card identifier can be used as a reference.
  • the above apparatus may further include a selection module (not shown), an encryption decryption module (not shown), and a conflict processing module (not shown).
  • the selection module is used to display a list of applications for backup or recovery, so that the user can select an application that needs to be backed up or restored, which is helpful for backup or recovery of batch applications.
  • the conflict processing module is configured to process the selection process of the user in the case that the terminal already has an application that needs to be restored, for example, prompting the user to select to ignore the recovery operation, and replacing the originally saved application with the restored application file. Program files, add recovered applications to the terminal system.
  • the encryption and decryption module is configured to encrypt the intermediate file according to a predetermined encryption algorithm before the storage module stores the intermediate file to the specified storage location, so that when the backup management is performed, the file stored by the storage module to the specified storage location is encrypted. Intermediate file, thus ensuring the security of backup, avoiding others stealing The file data to be backed up; the encryption and decryption module is also used to decrypt the encrypted file, so that when the recovery management is performed, the converted module converts the file in the specified format required by the terminal that needs to restore the application to obtain the decrypted file. document.
  • the device may further be provided with a trigger module (not shown) for triggering a process of backing up or restoring files to the application, and notifying the relevant processing module after the process is triggered, for example, in the case of triggering the backup.
  • the conversion module can be notified to start the format conversion of the file to be backed up.
  • the conversion module can be notified to start converting the pre-backed file into the format desired by the second terminal. If the backup file is encrypted, the first The encryption and decryption module is notified to decrypt the backed up file. The specific process is not listed here.
  • FIG. 6 is a block diagram of the software in the terminal and the various functional modules of the above device.
  • the operating system 2 is the operating system of the terminal 1; the JAVA virtual machine management module 3 is an application on the operating system 2, and is responsible for managing the JAVA virtual machine 4 and the JAVA application 5; the JAVA virtual machine 4 itself has platform independence, which can be
  • the JAVA application 5 provides a runtime environment; the management device 6 of the application is used to provide backup, recovery and detection functions of the JAVA application 5; in the management device 6 of the application, the trigger module 7 is responsible for triggering the application on the terminal 1.
  • the conversion module 8 is responsible for parsing and converting the data, converting the special data format into a common format, and converting the general data format into the terminal 1 In the required format, the conversion module 8 can convert the file of the application on the terminal 1 from the format requested by the terminal 1 into a predetermined intermediate format, and convert the application saved from the external or internal memory when the backup is performed. Module 8 is capable of converting the stored intermediate format file to the file format required by terminal 1. ; 9 storage module responsible for the data stored in the external memory to implement a terminal application backup or copy data in the external memory to the terminal 1, in order to achieve restoring the application; detection module 10 is responsible for judging whether the restored application is allowed to be run by the terminal 1.
  • the management device 6 of the application in FIG. 6 may be a sub-module of the JAVA virtual machine management module 3, or may be a module of the mobile terminal 1 independent of the JAVA virtual machine management module 3. Moreover, the management device 6 of the application may further include a selection module, an encryption and decryption module, and a conflict processing module.
  • Figure 7 shows a specific example of how files converted to intermediate structures are stored.
  • the file in this intermediate format should be different from the format required by the virtual machine, ie the virtual machine does not recognize the format.
  • the application identifier (id) 76 is used to identify the application to which the information belongs; the attribute 77 is used to indicate the classification of the information, the possible classification has a database, security settings, and application information.
  • Data type 78 indicates the type used when the data is stored, for example, an integer, a string, etc.; the name 79 records the name of the data item; the value 710 is used to represent the specific data content; and the identification information 711 is used to indicate the initial installation of the application.
  • the identity information of the mobile terminal ie, the identification information of the predetermined type described above).
  • the apparatus according to the present embodiment can also implement the processing shown in Figs. 1 to 4, which has been described before, and will not be repeated here.
  • the device can Includes:
  • a conversion module configured to convert an intermediate file of a predetermined intermediate format into a second terminal a file of a specified format, wherein the intermediate file is format converted by the first terminal to the file of the specified application, and the second terminal and the first terminal both have an operating environment of the application, and the intermediate format can be provided with the application. Identification by other terminals of the operating environment of the program;
  • a saving module for recovering management of a specified application by storing a file converted to a specified format to a second terminal.
  • each function module in the device of the embodiment may be directly disposed in the terminal, and part or all of the function modules may be connected to the terminal itself according to actual needs.
  • the functional modules are integrated, and the above functional modules can be implemented by software or by hardware such as a CPU or a field programmable gate array.
  • a universal backup management is implemented for the application, and recovery is required.
  • the terminal of the application can convert the file in the intermediate format into the format required by each to restore and use the application normally; and, by encrypting the file stored in the backup, the security of the backup file can be further improved;
  • the stability and reliability of the application recovery can be ensured; and the above processing can realize the universal backup and application recovery between different platforms in the JAVA J2ME environment. It is also suitable for various platforms in other environments such as Windows Mobile Pocket, and has a wide range of practicalities.

Description

应用程序的管理方法和装置、 以及终端 技术领域
本发明涉及通信领域, 尤其涉及一种应用程序的管理方法和装置、 以 及终端。 背景技术
目前, JAVA虚拟机已经成为大多数移动终端的必需配置。 由于 JAVA 虚拟机的存在, 用户可以将 JAVA虚拟机作为平台在终端上安装需要的 JAVA应用程序。
通常,移动终端中设置有 JAVA应用程序管理模块, 用于显示并管理存 储或安装的应用程序, 还可用于提供应用程序的启动、 安装、 更新、 删除、 设置等功能。 但是, 目前的 JAVA应用程序管理模块并不能够使 JAVA应用 程序在不同终端上进行备份和恢复。
目前,虽然已经提出了针对 Java2微型版( J2ME , JAVA 2 Micro Edition ) 的相关标准规范,根据该标准,各个 JAVA虚拟机厂商需要提供符合要求的 应用程序编程接口 ( API, Application Programming Interface )„ 但是, 目前 的标准中并没有规定 JAVA应用程序信息的存储方式。 因此, 使用不同的 JAVA虚拟机(即不同的 JAVA平台 )安装应用程序后, 应用程序的各种相 关信息 (例如, 数据库信息、 安全设置信息等)在文件系统中的存储结构 是不同的。 仅仅釆用简单的备份和恢复, 无法使应用程序达到跨平台运行 的要求。
另外, 目前各个运营商都希望对各自 JAVA应用的版权进行保护, 不允 许 JAVA应用程序随便扩散。 因此, 当用户升级了终端的版本、 或者更换终 端后, 由于应用程序的使用存在较大的局限性, 用户将无法继续使用原终 端上的 JAVA应用,而需要重新获取并安装格式与当前终端版本相匹配的应 用程序。
类似地, 除了 JAVA之外, 目前终端还可以釆用其他的应用程序运行环 境, 并且, 同样会出现同一应用环境下开发的不同平台之间无法备份和恢 复应用程序的问题。
针对相关技术中终端的应用程序无法跨平台备份并运行而导致应用程 序使用的局限性大、 对用户正常使用应用程序造成不便的问题, 目前尚未 提出有效的解决方案。 发明内容
针对相关技术中应用程序无法跨平台备份并运行, 而导致应用程序使 用的局限性大、 对用户正常使用应用程序造成不便的问题, 本发明提出一 种应用程序的管理方法和装置、 以及终端, 能够对应用程序以通用的方式 进行备份, 从而保证应用程序能够在多个平台上恢复并正常运行。
本发明的技术方案是这样实现的:
本发明提供了一种应用程序的管理方法, 用于保证具备该应用程序的 运行环境下各种运行平台的终端均能够恢复并运行该被管理的应用程序。
根据本发明的应用程序的管理方法包括: 第一终端将自身保存的指定 应用程序的文件转换为预定的中间格式的中间文件, 其中, 中间格式能够 被具备该应用程序的运行环境的其他终端识别; 第一终端通过将中间文件 存储至指定存储位置, 来对指定应用程序进行备份管理, 使得第二终端能 够恢复经备份的应用程序, 其中, 第二终端与第一终端均具备该应用程序 的运行环境。
其中, 该方法还包括: 第二终端通过将中间文件转换为第二终端所要 求的指定格式的文件、 并将指定格式的文件存储至第二终端来对指定应用 程序进行恢复管理。 并且, 将中间文件存储至指定存储位置进一步包括: 第一终端将来自 第一终端的预定类型的标识信息存储至指定存储位置; 其中, 标识信息用 于对第二终端进行验证。
并且, 在对指定应用程序进行恢复管理之后, 该方法进一步包括: 从 第二终端获取预定类型的标识信息, 判断获取的第二终端的标识信息与指 定存储位置处存储的标识信息是否相同; 如果判断为相同, 则允许第二终 端运行经过恢复管理的指定应用程序; 如果判断为不相同, 则禁止第二终 端运行经过恢复管理的指定应用程序。
可选地, 预定类型的标识信息包括以下之一: 第一终端的标识信息、 第一终端上用户身份模块 SIM卡的标识信息。
此外, 将中间文件存储至指定存储位置进一步包括: 根据预定加密算 法对转换为中间文件进行加密, 且后续存储至指定存储位置的文件为加密 后的文件。
并且, 在第二终端对中间文件进行转换之前, 该方法还包括: 对加密 后的中间文件进行解密, 且恢复管理时被第二终端转换为指定格式的文件 为解密得到的文件。
根据本发明, 还提供了一种应用程序的管理方法, 用于保证具备该应 用程序的运行环境下各种运行平台的终端均能够恢复并运行该被管理的应 用程序。
根据本发明的应用程序的管理方法包括: 第二终端将指定存储位置处 存储的转换为预定的中间格式的中间文件转换为第二终端所要求的指定格 式的文件, 其中, 中间文件由第一终端对指定应用程序的文件进行格式转 换得到, 第二终端与第一终端均具备该应用程序的运行环境, 并且, 中间 格式能够被具备该应用程序的运行环境的其他终端识别; 第二终端通过保 存转换为指定格式的文件来对指定应用程序进行恢复管理。 根据本发明, 还提供了一种应用程序的管理装置, 用于保证具备该应 用程序的运行环境下各种运行平台的终端均能够恢复并运行该被管理的应 用程序。
根据本发明的应用程序的管理装置包括: 转换模块, 用于将第一终端 保存的指定应用程序的文件转换为预定的中间格式的中间文件, 其中, 中 间格式能够被具备该应用程序的运行环境的其他终端识别; 存储模块, 用 于通过将中间文件存储至指定存储位置, 来对指定应用程序进行备份管理, 使第二终端能够恢复应用程序, 其中, 第二终端与第一终端均具备该应用 程序的运行环境。
其中, 转换模块还用于将中间文件转换为第二终端所要求的指定格式 的文件; 存储模块还用于通过将转换为指定格式的文件存储至第二终端来 对指定应用程序进行恢复管理。
并且, 存储模块还用于将来自第一终端的预定类型的标识信息存储至 指定存储位置; 其中, 标识信息用于对第二终端进行验证;
并且, 该装置进一步包括: 检测模块, 用于从第二终端获取预定类型 的标识信息, 判断获取的第二终端的标识信息与指定存储位置处存储的标 识信息是否相同; 如果判断为相同, 则允许第二终端运行经过恢复管理的 指定应用程序; 如果判断为不相同, 则禁止第二终端运行经过恢复管理的 指定应用程序。
可选地, 预定类型的标识信息包括以下之一: 第一终端的标识信息、 第一终端上用户身份模块 SIM卡的标识信息。
该装置还可包括: 加密解密模块, 用于在存储模块将中间文件存储至 指定存储位置之前, 根据预定加密算法对中间文件进行加密, 且存储模块 存储至指定存储位置的文件为加密后的中间文件; 加密解密模块还用于对 加密后的文件进行解密, 且恢复管理时被转换模块转换为指定格式的文件 为解密得到的文件。
根据本发明, 还提供了一种应用程序的管理装置, 用于保证具备该应 用程序的运行环境下各种运行平台的终端均能够恢复并运行该被管理的应 用程序。
根据本发明的应用程序的管理装置包括: 转换模块, 用于将预定的中 间格式的中间文件转换为第二终端所要求的指定格式的文件, 其中, 中间 文件由第一终端对指定应用程序的文件进行格式转换得到, 第二终端与第 一终端均具备该应用程序的运行环境, 并且, 中间格式能够被具备该应用 程序的运行环境的其他终端识别; 保存模块, 用于通过将转换为指定格式 的文件存储至第二终端来对指定应用程序进行恢复管理。
本发明还提供了一种终端, 该终端可以包括上述根据本发明的应用程 序的管理装置。
本发明通过将需要备份的应用程序转换为预先规定的、 不同的终端平 台能够识别的中间格式, 从而对应用程序实现了通用性备份管理, 以便需 要恢复该应用程序的终端将该中间格式的文件转换为各自要求的格式, 从 而恢复并正常使用该应用程序。 附图说明
图 1是根据本发明实施例的应用程序的管理方法的流程图;
图 2是将根据本实施例的应用程序的管理方法应用于 JAVA的 J2ME环 境的终端后进行应用程序备份的处理流程图;
图 3是将根据本实施例的应用程序的管理方法应用于 JAVA的 J2ME环 境的终端后进行应用程序恢复的处理流程图;
图 4是将根据本实施例的应用程序的管理方法应用于 JAVA的 J2ME环 境的终端后运行恢复的应用程序的处理流程图;
图 5是根据本发明实施例的应用程序的管理装置的框图; 图 6是将根据本发明实施例的应用程序的管理装置用于 JAVA的 J2ME 环境的终端后终端上各个功能模块的框图;
图 7示出了转换为中间结构的文件的存放方式的一个具体实例。 具体实施方式
针对相关技术中应用程序无法跨平台备份并运行而导致应用程序使用 的局限性大、 对用户正常使用应用程序造成不便的问题, 本发明提出, 将 需要备份的应用程序转换为预先规定的中间格式, 不同的终端平台能够识 别该中间格式并将该中间格式的文件转换为各自要求的格式, 从而能够恢 复并正常使用该应用程序。
下面将结合附图, 详细描述本发明的实施例。
根据本发明的实施例, 提供了一种应用程序的管理方法, 用于保证具 备该应用程序的运行环境下各种运行平台的终端均能够恢复并运行该被管 理的应用程序。
如图 1所示, 根据本实施例的应用程序的管理方法包括:
步骤 S101 , 第一终端将其保存的指定应用程序的文件转换为预定的中 间格式的中间文件, 其中, 中间格式能够被具备该应用程序的运行环境的 其他终端识别 (例如, 可以选择通用的文件格式作为中间格式)。
步骤 S103 , 第一终端通过将中间文件存储至指定存储位置 (其中, 指 定存储位置可以是终端内的预设存储器、 也可以是与终端外接的存储器, 如终端外接的存储卡) 来对指定应用程序进行备份管理, 使得第二终端能 够恢复经备份的应用程序, 其中, 第二终端与第一终端均具备该应用程序 的运行环境(也就是说, 只要第一终端与第二终端均具备该应用程序的运 行环境, 即使第二终端与第一终端的平台不同, 第二终端同样能够识别并 恢复该被备份的应用程序)。
借助上述处理, 能够将需要备份的应用程序转换为预先规定的、 不同 的终端平台能够识别的中间格式, 从而对应用程序实现了通用性备份管理, 以便需要恢复该应用程序的终端将该中间格式的文件转换为各自要求的格 式, 即使第二终端与第一终端的运行平台不同, 也能够恢复并正常使用由 第一终端备份的应用程序。
在对应用程序完成备份之后, 通过将指定存储位置处存储的文件 (中 间文件)转换为期望恢复指定应用程序的第二终端所要求的指定格式的文 件、 并将该指定格式的文件存储至第二终端来对指定应用程序进行恢复管 理。 之后, 第二终端即可正常使用恢复的应用程序。
在将上述处理应用于基于 JAVA的 J2ME环境的终端时,第一终端与第 二终端的运行环境均为 JAVA的 J2ME环境,但是第一终端与第二终端的运 行平台可能并不相同, 即, 第一终端与第二终端的虚拟机不同, 但是由于 备份的文件为第二终端能够识别的中间格式, 因此第二终端能够转换并恢 复该备份的文件, 从而对应用程序进行恢复管理。
在将上述处理应用于基于 JAVA的 J2ME环境的终端时,在进行应用程 序备份时, 具体包括以下步骤:
( al )激活备份 JAVA应用程序的流程, 确定要备份的应用程序;
( bl )分解应用程序的所有信息以及标识信息 (可以是终端的标识或 SIM卡的标识等, 用于对恢复该应用程序的终端进行验证), 将其转换成与 虚拟机无关的中间格式;
( cl )将上述步骤得到的文件存储到外部存储器中。
优选地, 在步骤 al中确定备份的应用程序时, 釆用构建 JAVA应用程 序列表界面供用户选择需要备份的应用程序; 在步骤 cl中可以在将文件存 储到外部存储器前对文件进行加密。 除了用户手动选择应用程序之外, 终 端还可以默认指定需要备份或恢复的应用程序。
在基于 JAVA的 J2ME环境的终端中, 在进行应用程序恢复时, 具体包 括以下步骤:
( a2 )激活恢复 JAVA应用程序的流程;
( b2 )从外部存储器中获取备份数据;
( c2 )对数据格式进行转换, 将与虚拟机无关的中间格式转换成移动 终端要求的格式;
( d2 )将恢复的应用程序添加到移动终端上, 并记录应用程序的身份 标识信息。
此外, 可选地, 将中间文件存储至指定存储位置的处理可以进一步包 括: 将来自第一终端的预定类型的标识信息存储至指定存储位置, 该标识 信息用于对第二终端进行验证。 并且, 同样可以将标识信息转换为中间格 式后存储在指定存储位置处。
在对指定应用程序进行恢复管理之后, 如果第二终端需要运行恢复的 应用程序, 可以预先从第二终端获取预定类型的标识信息, 判断获取的第 二终端的标识信息与指定存储位置处存储的标识信息是否相同; 如果判断 为相同, 则允许第二终端运行经过恢复管理的指定应用程序; 如果判断为 不相同, 则禁止第二终端运行经过恢复管理的指定应用程序。
优选地, 如果第一终端与第二终端为同一终端 (例如, 终端的软件平 台版本被更新, 新版本的平台与旧版本的平台的应用程序存储方式不同, 所以新平台无法使用原旧平台下保存的应用程序), 预定类型的标识信息可 以是终端的标识信息 (例如, 标识信息可以是 IMSI、 终端的证书信息等能 够唯一标识该终端的信息 ),也可以是终端上用户身份模块 SIM卡的标识信 息(例如, 终端的电话号码或 SIM卡的唯一标识); 如果第一终端与第二终 端是不同的终端 (例如, 用户用第二终端替换原使用的第一终端), 即, 用 户需要将第一终端上的应用程序恢复到第二终端上, 由于终端本身的标识 会发生变化, 但是用户通常不会更换用户身份模块 SIM卡, 因此, 可以将 SIM卡的标识信息 (例如, 终端的电话号码或 SIM卡的唯一标识 )作为一险 证的参照。
此外, 还可以选择其他能够标识终端或 SIM卡的信息作为验证时参照 的标识, 本文不再列举。
并且, 4艮设存在三个终端, 即, 终端 A、 终端 B和终端 C , 其中, 终 端 A是最初安装该应用程序的终端, 之后, 终端 A对该应用程序进行了备 份管理, 并由终端 B恢复了该应用程序; 此后, 终端 B在完成恢复之后, 又对该应用程序进行了备份管理, 并由终端 C恢复了终端 B备份的应用程 序。 在上述过程中, 如果在终端 A安装该应用程序时, 选择终端 A的 SIM 卡电话号码作为上述预定类型的标识信息, 则在终端 A备份该应用程序之 后,终端 B在进行恢复管理时,会将终端 A的 SIM卡电话号码 X存储至终 端 B中, 并在终端 B运行该应用程序之前, 基于该存储的 SIM卡电话号码 X以及终端 B上本身携带的 SIM卡号码进行验证, 如果验证未通过, 则禁 止终端 B运行该应用程序。
并且, 当终端 B备份该应用程序时, 同样会备份该应用程序的文件并 同时存储电话号码 X, 则在终端 B备份该应用程序之后, 终端 C在进行恢 复管理时,会将 SIM卡电话号码 X存储至终端 C中,并在终端 C运行该应 用程序之前, 基于该存储的 SIM卡电话号码 X 以及终端 C上本身携带的 SIM卡号码进行验证, 如果验证未通过, 则禁止终端 C运行该应用程序。 也就是说, 在多次备份和恢复的情况下, 在对每个终端进行验证时, 可以 参照首次安装该应用程序时保存的标识。
通过根据标识信息进行验证的过程, 能够对应用程序的版权提供有效 的保护。
为了保证备份文件的安全性, 可以根据预定加密算法对转换为中间格 式后的文件 (即中间文件)进行加密, 之后将加密后的文件存储至指定存 储位置。
相应地, 在第二终端对中间文件进行转换之前(即恢复备份的文件之 前),应当首先根据加密时釆用的算法对加密后的中间文件进行解密,之后, 将解密得到的文件转换为指定格式并存储至第二终端, 从而完成应用程序 的恢复。
此外, 在进行应用程序的恢复时, 当发现要恢复的应用程序已经存在 于第二终端上, 则可以提示用户进行操作选择, 并根据用户的选择进行相 应的操作, 从而达到解决冲突的目的。 例如, 如果用户根据提供的选择忽 略, 则停止恢复该应用; 如果用户选择替换, 则用该备份的应用替换第二 终端上当前安装的应用; 如果用户选择增加, 则将备份的应用增加到第二 终端的系统。
下面将详细描述 JAVA系统中应用程序备份和恢复的处理过程。
图 2是才艮据本实施例的应用程序的管理方法应用于 JAVA的 J2ME环境 的终端后进行应用程序备份的处理流程图。
如图 2所示, 具体包括以下处理过程:
步骤 201 ,确定用户选择需要进行备份的一个或者多个 JAVA应用程序。 步骤 202 , 获取要进行备份的所有 JAVA应用程序中存储的信息。
步骤 203 , 提取初次安装 JAVA应用的移动终端电话号码(作为验证时 参照的标识信息)。
步骤 204,将步骤 202和步骤 203中获取到的信息按照图 7所示的中间 格式进行存储, 保存到文件系统。
步骤 205 , 加密步骤 204产生的文件。
步骤 206, 移动加密的文件到移动存储卡。
图 3是才艮据本实施例的应用程序的管理方法应用于 JAVA的 J2ME环境 的终端后进行应用程序恢复的处理流程图。 如图 3所示, 具体包括以下处理过程:
步骤 201 , 将存有备份文件的移动存储卡插到终端上。
步骤 302, 解密备份文件。
步骤 303 , 判断是否解密成功, 如果成功, 则将解密后的文件保存到文 件系统, 并执行步骤 304; 如果不成功则退出, 处理结束。
步骤 304, 从解密后的数据中按照图 7的格式读取信息。
步骤 305 ,列出备份中的 JAVA应用程序,供用户选择需要恢复的 JAVA 应用程序。
步骤 306, 将需要恢复的 JAVA应用程序的信息进行转换, 保存为当前 使用的 JAVA虚拟机需要的格式。
步骤 307, 将 JAVA应用程序添加到终端中; 如果检测到手机中已经存 在相同的应用, 就询问用户进行执行添加、 忽略、 或者替换应用等操作; 如果用户选择添加, 则将恢复的应用添加到终端; 如果用户选择忽略, 就 不恢复该应用, 如果用户选择替换, 就用恢复的应用替换当前终端上的应 用。
步骤 308 , 将备份好的 JAVA应用程序和初次安装该应用程序的终端电 话号码进行关联, 即记录应用程序来源的终端电话号码。
图 4是才艮据本实施例的应用程序的管理方法应用于 JAVA的 J2ME环境 的终端后在运行恢复的应用程序时对终端进行验证的处理流程图。 如图 4 所示, 具体包括以下步骤:
步骤 401 , 判断 JAVA应用程序相关联的电话号码(即之前应用程序恢 复时记录的电话号码)是否和移动终端 (本身的电话号码) 匹配, 如果匹 配, 则执行步骤 402; 不匹配, 则结束处理。
步骤 402, 运行 JAVA应用程序。
这样, 即使终端上的 JAVA虚拟机发生变化,备份的应用程序同样能够 被成功恢复到各种 JAVA终端上, 从而实现了应用程序的跨平台恢复和运 行。
通过上述处理, 能够将需要备份的应用程序转换为预先规定的、 不同 的终端平台能够识别的中间格式, 从而对应用程序实现了通用性备份管理, 需要恢复该应用程序的终端能够将该中间格式的文件转换为各自要求的格 式, 从而恢复并正常使用该应用程序; 并且, 通过对备份存储的文件进行 加密, 能够进一步提高备份文件的安全性; 此外, 通过提示用户进行应用 程序恢复过程中的冲突解决方式, 可以保证应用程序恢复的稳定性和可靠 性; 并且, 上述处理能够实现 JAVA的 J2ME环境下不同平台之间的通用性 备份和应用恢复, 同时也适用于 Windows Mobile Pocket等其他环境下的各 种平台, 具有广泛的实用性。
根据本发明的本实施例, 还提供了一种应用程序的管理装置。
如图 5所示, 根据本发明实施例的应用程序的管理装置包括: 转换模块 51 , 用于将第一终端保存的指定应用程序的文件转换为预定 的中间格式的中间文件, 其中, 中间格式能够被具备该应用程序的运行环 境的其他终端识别;
存储模块 52, 连接至转换模块 51 , 用于通过将中间文件存储至指定存 储位置, 来对指定应用程序进行备份管理, 使第二终端能够恢复应用程序, 其中, 第二终端与第一终端均具备该应用程序的运行环境。
通过上述装置, 能够将需要备份的应用程序转换为预先规定的、 不同 的终端平台能够识别的中间格式, 从而对应用程序实现了通用性备份管理, 便于需要恢复该应用程序的终端能够将该中间格式的文件转换为各自要求 的格式, 从而恢复并正常使用该应用程序。
在对备份的应用程序的文件进行恢复时, 转换模块 51还用于将中间文 件转换为第二终端 (第二终端为期望恢复指定应用程序的终端) 所要求的 指定格式的文件; 存储模块 52还用于通过将转换为指定格式的文件存储至 第二终端来对指定应用程序进行恢复管理。
其中, 为了对运行恢复的应用程序的终端进行验证, 存储模块 52还用 于将来自第一终端的预定类型的标识信息存储至指定存储位置, 其中, 标 识信息用于对第二终端进行验证。
该装置还可以进一步包括: 检测模块(未示出), 用于从第二终端获取 预定类型的标识信息, 判断获取的第二终端的标识信息与指定存储位置处 存储的标识信息是否相同; 如果判断为相同, 则允许第二终端运行经过恢 复管理的指定应用程序; 如果判断为不相同, 则禁止第二终端运行经过恢 复管理的指定应用程序, 从而能够有效维护应用程序的版权。
可选地, 上述预定类型的标识信息可以包括以下之一: 第一终端的标 识信息、 第一终端上用户身份模块 SIM卡的标识信息。 其中, 在第二终端 与第一终端为同一终端的情况下, 可以将终端的标识信息或 SIM卡的标识 信息作为验证时参照的标识, 在第二终端与第一终端为不同终端的情况下, 则可以将终端的标识信息或 SIM卡标识作为参照。
优选的, 上述装置还可以包括选择模块(未示出)、 加密解密模块(未 示出)和冲突处理模块(未示出)。 其中, 选择模块, 用于显示供备份或恢 复的应用程序列表, 以便用户选择需要备份或恢复的应用程序, 有助于实 现批量应用程序的备份或恢复。 冲突处理模块, 用于处理恢复过程中, 在 终端已经存在需要恢复的应用的情况下为用户提供处理方案的选择, 例如, 提示用户选择忽略恢复操作、 利用恢复的应用程序文件替换原保存的应用 程序文件、 添加恢复的应用程序到终端系统。 加密解密模块, 用于在存储 模块将中间文件存储至指定存储位置之前, 根据预定加密算法对中间文件 进行加密, 这样, 在进行备份管理时, 由存储模块存储至指定存储位置的 文件为经过加密的中间文件, 从而保证了备份的安全性, 避免其他人盗取 备份的文件数据; 加密解密模块还用于对加密后的文件进行解密, 这样, 在进行恢复管理时, 被转换模块转换为需要恢复该应用程序的终端所要求 的指定格式的文件为解密后得到的文件。
其中, 上述装置还可以设置有触发模块(未示出), 用于触发对应用程 序的文件备份或恢复的过程, 并在过程触发后通知相关的处理模块, 例如, 在触发备份的情况下, 可以通知转换模块开始对需要备份的文件进行格式 转换, 当触发恢复流程时, 可以通知转换模块开始将预先备份的文件转换 为第二终端期望的格式, 如果备份的文件是经过加密的, 可以首先通知加 密解密模块对备份的文件进行解密, 具体过程这里不再列举。
图 6是终端中软件以及上述装置的各个功能模块的框图。
如图 6所示,在将上述装置应用于 JAVA应用环境的终端后,终端内的 功能模块具体功能如下:
操作系统 2为终端 1的操作系统; JAVA虚拟机管理模块 3为操作系统 2上的一个应用, 负责管理 JAVA虚拟机 4和 JAVA应用程序 5; JAVA虚拟 机 4自身具有平台无关性, 其能够为 JAVA应用程序 5提供运行时环境; 应 用程序的管理装置 6用于提供 JAVA应用程序 5的备份、 恢复和检测功能; 在应用程序的管理装置 6中, 触发模块 7负责触发终端 1上应用程序的备 份或恢复从外部存储器、 内部存储器等存储位置将应用程序恢复到终端 1 上; 转换模块 8 负责数据的解析转换, 能够将特殊数据格式转换成通用格 式, 也能够将通用数据格式转换成终端 1 所要求的格式, 在进行备份时, 转换模块 8能够将终端 1上应用程序的文件由终端 1要求的格式转换为预 定的中间格式, 在恢复来自外部或内部存储器中保存的应用程序时, 转换 模块 8能够将存储的中间格式的文件转换为终端 1要求的文件格式; 存储 模块 9负责将数据存储到外部存储器实现终端 1的应用程序备份, 或将外 部存储器中的数据拷贝到终端 1 上, 从而实现应用程序的恢复; 检测模块 10负责判断恢复的应用是否允许被终端 1运行。
可选地,图 6中的应用程序的管理装置 6可以为 JAVA虚拟机管理模块 3的子模块,也可以为移动终端 1中独立于 JAVA虚拟机管理模块 3的模块。 并且, 应用程序的管理装置 6 中还可以进一步包括选择模块、 加密解密模 块、 和冲突处理模块。
由于 JAVA应用程序被安装运行后会产生很多附加的信息,这些信息在 不同的 JAVA虚拟机中要求的格式是不同的。 因此需要对 JAVA应用程序中 的信息进行分解, 将信息以一种通用的格式存放。 图 7 示出了转换为中间 结构的文件的存放方式的一个具体实例。 优选地, 这种中间格式的文件应 当不同于虚拟机需要的格式, 即虚拟机无法识别该格式。 如图 7所示, 在 该存放方式中, 应用程序的标识(id ) 76 用于标识信息所属的应用程序; 属性 77用于表示信息的分类、 可能的分类有数据库、 安全设置、 以及应用 信息等; 数据类型 78表示数据存储时使用的类型, 例如, 整型、 字符串等; 名称 79记录数据项的名称; 值 710用于表示具体的数据内容; 身份识别信 息 711 用于表示初次安装应用的移动终端的身份信息 (即上述预定类型的 标识信息)。
应当注意, 图 7所示的存储方式仅仅是一个具体实例, 在实际应用中, 可以根据需要增加其他相关的信息或省略部分信息, 本文不再——举例说 明。
此外, 根据本实施例的装置同样能够实现图 1至图 4所示的处理, 具 体过程之前已经描述, 这里不再重复。
另外, 对于性能较为低端的终端, 其本身可能不具备应用程序的备份 功能, 而是单纯地恢复已经备份好的文件, 这些终端内同样能够设置应用 程序的管理装置, 此时, 该装置可以包括:
转换模块, 用于将预定的中间格式的中间文件转换为第二终端所要求 的指定格式的文件, 其中, 中间文件由第一终端对指定应用程序的文件进 行格式转换得到, 第二终端与第一终端均具备该应用程序的运行环境, 并 且, 中间格式能够被具备该应用程序的运行环境的其他终端识别;
保存模块, 用于通过将转换为指定格式的文件存储至第二终端来对指 定应用程序进行恢复管理。
除了将根据本实施例的装置设置在终端内, 还可以将本实施例的装置 中的各个功能模块直接设置在终端中, 并且, 可以根据实际需要将上述功 能模块中的部分或全部与终端本身的功能模块进行集成, 并且, 上述功能 模块既可以通过软件实现, 也可以通过 CPU、 现场可编程门阵列等硬件实 现。
综上所述, 借助于本发明的上述技术方案, 通过将需要备份的应用程 序转换为预先规定的、 不同的终端平台能够识别的中间格式, 从而对应用 程序实现了通用性备份管理, 需要恢复该应用程序的终端能够将该中间格 式的文件转换为各自要求的格式, 从而恢复并正常使用该应用程序; 并且, 通过对备份存储的文件进行加密, 能够进一步提高备份文件的安全性; 此 外, 通过提示用户进行应用程序恢复过程中的冲突解决方式, 可以保证应 用程序恢复的稳定性和可靠性; 并且, 上述处理能够实现 JAVA的 J2ME环 境下不同平台之间的通用性备份和应用恢复, 同时也适用于 Windows Mobile Pocket等其他环境下的各种平台, 具有广泛的实用性。
以上所述仅为本发明的较佳实施例而已, 并不用以限制本发明, 凡在 本发明的精神和原则之内, 所作的任何修改、 等同替换、 改进等, 均应包 含在本发明的保护范围之内。

Claims

权利要求书
1、 一种应用程序的管理方法, 用于保证具备所述应用程序的运行环境 下各种运行平台的终端均能够恢复并运行管理的所述应用程序, 其特征在 于, 所述方法包括:
第一终端将自身保存的指定应用程序的文件转换为预定的中间格式的 中间文件, 其中, 所述中间格式能够被具备所述应用程序的运行环境的其 他终端识别;
所述第一终端通过将所述中间文件存储至指定存储位置, 来对所述指 定应用程序进行备份管理, 使第二终端能够恢复经备份的所述应用程序, 其中, 所述第二终端与所述第一终端均具备所述应用程序的运行环境。
2、 根据权利要求 1所述的管理方法, 其特征在于, 所述方法还包括: 所述第二终端通过将所述中间文件转换为所述第二终端所要求的指定 格式的文件, 并将所述指定格式的文件存储至所述第二终端来对所述指定 应用程序进行恢复管理。
3、 根据权利要求 2所述的管理方法, 其特征在于, 将所述中间文件存 储至所述指定存储位置进一步包括:
所述第一终端将来自所述第一终端的预定类型的标识信息存储至所述 指定存储位置; 其中, 所述标识信息用于对所述第二终端进行验证。
4、 根据权利要求 3所述的管理方法, 其特征在于, 在所述第二终端对 所述指定应用程序进行恢复管理之后, 所述方法进一步包括:
从所述第二终端获取所述预定类型的标识信息, 判断获取的所述第二 终端的标识信息与所述指定存储位置处存储的标识信息是否相同;
如果判断为相同, 则允许所述第二终端运行经过恢复管理的所述指定 应用程序;
如果判断为不相同, 则禁止所述第二终端运行经过恢复管理的所述指 定应用程序。
5、 根据权利要求 3或 4所述的管理方法, 其特征在于, 所述预定类型 的标识信息包括以下之一:
所述第一终端的标识信息、 所述第一终端上用户身份模块 SIM卡的标 识信息。
6、 根据权利要求 1或 2所述的管理方法, 其特征在于, 将所述中间文 件存储至所述指定存储位置进一步包括:
根据预定加密算法对所述中间文件进行加密, 且后续存储至所述指定 存储位置的文件为加密后的所述文件。
7、 根据权利要求 6所述的管理方法, 其特征在于, 在所述第二终端对 所述中间文件进行转换之前, 所述方法还包括:
对加密后的所述中间文件进行解密, 且恢复管理时被所述第二终端转 换为所述指定格式的文件为解密得到的文件。
8、 一种应用程序的管理方法, 用于保证具备所述应用程序的运行环境 下各种运行平台的终端均能够恢复并运行管理的所述应用程序, 其特征在 于, 所述方法包括:
第二终端将指定存储位置处存储的转换为预定的中间格式的中间文件 转换为所述第二终端所要求的指定格式的文件, 其中, 所述中间文件由第 一终端对指定应用程序的文件进行格式转换得到, 所述第二终端与所述第 一终端均具备所述应用程序的运行环境, 并且, 所述中间格式能够被具备 所述应用程序的运行环境的其他终端识别;
所述第二终端通过保存转换为所述指定格式的所述文件来对所述指定 应用程序进行恢复管理。
9、 一种应用程序的管理装置, 用于保证具备所述应用程序的运行环境 下各种运行平台的终端均能够恢复并运行管理的所述应用程序, 其特征在 于, 所述装置包括:
转换模块 , 用于将第一终端保存的指定应用程序的文件转换为预定的 中间格式的中间文件, 其中, 所述中间格式能够被具备所述应用程序的运 行环境的其他终端识别;
存储模块, 用于通过将所述中间文件存储至指定存储位置, 来对所述 指定应用程序进行备份管理, 使第二终端能够恢复所述应用程序, 其中, 所述第二终端与所述第一终端均具备所述应用程序的运行环境。
10、 根据权利要求 9所述的管理装置, 其特征在于, 所述转换模块还 用于将所述中间文件转换为所述第二终端所要求的指定格式的文件; 所述 存储模块还用于通过将转换为所述指定格式的所述文件存储至所述第二终 端来对所述指定应用程序进行恢复管理。
11、 根据权利要求 10所述的管理装置, 其特征在于, 所述存储模块还 用于将来自所述第一终端的预定类型的标识信息存储至所述指定存储位 置; 其中, 所述标识信息用于对所述第二终端进行险证;
并且, 所述装置进一步包括:
检测模块, 用于从所述第二终端获取所述预定类型的标识信息, 判断 获取的所述第二终端的标识信息与所述指定存储位置处存储的标识信息是 否相同;
如果判断为相同, 则允许所述第二终端运行经过恢复管理的所述指定 应用程序;
如果判断为不相同, 则禁止所述第二终端运行经过恢复管理的所述指 定应用程序。
12、 根据权利要求 11所述的管理装置, 其特征在于, 所述预定类型的 标识信息包括以下之一:
所述第一终端的标识信息、 所述第一终端上用户身份模块 SIM卡的标 识信息。
13、 根据权利要求 10所述的管理装置, 其特征在于, 还包括: 加密解密模块, 用于在所述存储模块将所述中间文件存储至所述指定 存储位置之前, 根据预定加密算法对所述中间文件进行加密, 且所述存储 模块存储至所述指定存储位置的文件为加密后的所述中间文件;
所述加密解密模块还用于对加密后的所述文件进行解密, 且恢复管理 时被所述转换模块转换为所述指定格式的文件为解密得到的所述文件。
14、 一种应用程序的管理装置, 用于保证具备所述应用程序的运行环 境下各种运行平台的终端均能够恢复并运行管理的所述应用程序, 其特征 在于, 所述装置包括:
转换模块, 用于将预定的中间格式的中间文件转换为第二终端所要求 的指定格式的文件, 其中, 所述中间文件由第一终端对指定应用程序的文 件进行格式转换得到, 所述第二终端与所述第一终端均具备所述应用程序 的运行环境, 并且, 所述中间格式能够被具备所述应用程序的运行环境的 其他终端识别;
保存模块, 用于通过将转换为所述指定格式的所述文件存储至所述第 二终端来对所述指定应用程序进行恢复管理。
15、 一种终端, 其特征在于, 包括根据权利要求 9至 14中任一项所述 的应用程序的管理装置。
PCT/CN2010/076002 2010-05-21 2010-08-13 应用程序的管理方法和装置、以及终端 WO2011143852A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
AU2010353673A AU2010353673B2 (en) 2010-05-21 2010-08-13 Managing method, device and terminal for application program
EP10851610.5A EP2521034B1 (en) 2010-05-21 2010-08-13 Managing method, device and terminal for application program
US13/576,168 US8555060B2 (en) 2010-05-21 2010-08-13 Managing method, device and terminal for application program

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201010187234.3 2010-05-21
CN201010187234A CN101853184A (zh) 2010-05-21 2010-05-21 应用程序的管理方法和装置、以及终端

Publications (1)

Publication Number Publication Date
WO2011143852A1 true WO2011143852A1 (zh) 2011-11-24

Family

ID=42804690

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2010/076002 WO2011143852A1 (zh) 2010-05-21 2010-08-13 应用程序的管理方法和装置、以及终端

Country Status (5)

Country Link
US (1) US8555060B2 (zh)
EP (1) EP2521034B1 (zh)
CN (1) CN101853184A (zh)
AU (1) AU2010353673B2 (zh)
WO (1) WO2011143852A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113204376A (zh) * 2021-04-27 2021-08-03 网银在线(北京)科技有限公司 文件解析方法、装置、计算机设备以及存储介质

Families Citing this family (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8468172B2 (en) * 2010-05-14 2013-06-18 Sap Ag Integrated application server and data server processes with matching data formats
WO2013023440A1 (zh) 2011-08-15 2013-02-21 联想(北京)有限公司 一种应用管理方法及设备
CN103092721B (zh) * 2011-10-31 2017-04-19 联想(北京)有限公司 一种应用备份方法、电子设备及系统
US9635549B2 (en) 2011-09-01 2017-04-25 Nokia Technologies Oy Providing subscriber identity module function
KR101907422B1 (ko) * 2012-02-10 2018-10-12 한국전자통신연구원 네트워크 애플리케이션 통합 개발장치, 그 통합 개발방법 및 그것을 이용하는 서버
CN103546879B (zh) * 2012-07-13 2018-02-16 国民技术股份有限公司 一种sim卡处理数据的方法及系统
US9398114B2 (en) 2012-11-23 2016-07-19 Mediatek Inc. Methods for automatically managing installed applications and determining application recommendation result based on auxiliary information and related computer readable media
TWI488066B (zh) * 2012-12-27 2015-06-11 Chunghwa Telecom Co Ltd 防止檔案以加密形式外洩的防護方法
EP3125110A4 (en) * 2014-04-16 2017-04-19 Huawei Technologies Co., Ltd. Software upgrade method and terminal
US10069738B2 (en) * 2015-04-01 2018-09-04 At&T Intellectual Property I, L.P. One cellular radio to support multiple phone lines and data at a location
CN106550102A (zh) * 2015-09-21 2017-03-29 中国移动通信集团公司 一种数据处理方法、装置及sim卡
CN106610875A (zh) * 2015-10-23 2017-05-03 先智云端数据股份有限公司 混合备份还原管理系统及其备份方法、还原方法
JP6951768B2 (ja) * 2017-01-19 2021-10-20 株式会社クリエイターズ・ヘッド 情報制御プログラム、情報制御システム、及び情報制御方法
CN110262757A (zh) * 2019-06-24 2019-09-20 北京奇艺世纪科技有限公司 一种数据处理方法及装置
CN114780208B (zh) * 2022-05-05 2023-08-08 安超云软件有限公司 验证多平台虚拟机备份有效性方法、系统、装置及存储介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040172484A1 (en) * 2000-04-04 2004-09-02 Gudmundur Hafsteinsson Device-specific communicating between a transmitting device and a receving device
US20040249854A1 (en) * 2003-03-24 2004-12-09 Barnes-Leon Maria Theresa Common common object
CN101247589A (zh) * 2007-07-04 2008-08-20 华为技术有限公司 移动终端数据的转换/备份方法、设备和系统

Family Cites Families (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US3479146A (en) * 1966-10-28 1969-11-18 Exxon Research Engineering Co Fluid flow distributor
JPH09325904A (ja) * 1996-06-04 1997-12-16 Nec Corp ファームウエア情報のバックアップ方法
US20010037404A1 (en) 2000-04-04 2001-11-01 Gudmundur Hafsteinsson System for wireless communication of data between a WEB server and a device using a wireless application protocol
US20020111972A1 (en) 2000-12-15 2002-08-15 Virtual Access Networks. Inc. Virtual access
JP4907059B2 (ja) * 2004-01-26 2012-03-28 大日本印刷株式会社 コンピュータシステムおよびそのデータの自動バックアップ方法
US20060026587A1 (en) * 2004-07-28 2006-02-02 Lemarroy Luis A Systems and methods for operating system migration
EP1667021A1 (de) * 2004-12-03 2006-06-07 Jerry Muse Woldeab Datensicherungsverfahren für ein Kommunikationsgerät
CN100433867C (zh) * 2004-12-08 2008-11-12 华为技术有限公司 一种防止移动终端中个人数据丢失的方法及装置
US10380538B2 (en) * 2005-09-27 2019-08-13 Bdna Corporation Discovery of electronic assets using fingerprints
WO2008109291A1 (en) * 2007-03-02 2008-09-12 Palm, Inc. Intelligent migration between devices having different hardware or software configuration

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040172484A1 (en) * 2000-04-04 2004-09-02 Gudmundur Hafsteinsson Device-specific communicating between a transmitting device and a receving device
US20040249854A1 (en) * 2003-03-24 2004-12-09 Barnes-Leon Maria Theresa Common common object
CN101247589A (zh) * 2007-07-04 2008-08-20 华为技术有限公司 移动终端数据的转换/备份方法、设备和系统

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113204376A (zh) * 2021-04-27 2021-08-03 网银在线(北京)科技有限公司 文件解析方法、装置、计算机设备以及存储介质

Also Published As

Publication number Publication date
EP2521034A1 (en) 2012-11-07
US8555060B2 (en) 2013-10-08
EP2521034B1 (en) 2015-10-07
AU2010353673B2 (en) 2013-11-21
US20120303954A1 (en) 2012-11-29
AU2010353673A1 (en) 2012-08-30
EP2521034A4 (en) 2013-01-23
CN101853184A (zh) 2010-10-06

Similar Documents

Publication Publication Date Title
WO2011143852A1 (zh) 应用程序的管理方法和装置、以及终端
US20160378458A1 (en) Method and device for system application installation package, and terminal
EP3103048B1 (en) Content item encryption on mobile devices
CN100565419C (zh) 在计算装置中备份并恢复数据的方法
WO2014000613A1 (zh) 系统修复方法、装置及存储介质
WO2008154862A1 (fr) Procédé de gestion pour un système de terminal intelligent et terminal intelligent
WO2012106878A1 (zh) 信息安全处理的方法及装置
CN111158719B (zh) 应用软件升级方法及装置
CN107066298B (zh) 无痕运行应用程序的方法及装置
KR100660641B1 (ko) 휴대 단말기의 부팅 보안 방법 및 그 휴대 단말기
JP5087502B2 (ja) 操作ログ管理装置及び操作ログ管理方法
US8171469B2 (en) Package compatibility
CN110990124A (zh) 云主机恢复方法和装置
CN104915266A (zh) 一种应用程序保护方法及装置
CN112379890A (zh) Whatsapp的数据拷贝方法
CN104346299A (zh) 一种移动终端更新的控制方法和装置
CN112749383A (zh) 软件认证方法和相关产品
KR101763184B1 (ko) 백업을 이용한 파일 복구 방법
JP5169904B2 (ja) データバックアップシステム、復号装置及びデータバックアップ方法
JP2009169868A (ja) 記憶領域アクセス装置及び記憶領域のアクセス方法
CN106294020B (zh) 安卓系统应用分区文件保护方法及终端
CN111291404A (zh) 安卓设备WhatsApp的crypt12备份解密方法、系统、装置和存储介质
CN113228016A (zh) 用于勒索软件解密的设备和方法
JP6460765B2 (ja) 情報処理装置、情報処理装置の制御方法、プログラム
CN106598773A (zh) 可信系统还原装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 10851610

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2010851610

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 13576168

Country of ref document: US

WWE Wipo information: entry into national phase

Ref document number: 2010353673

Country of ref document: AU

ENP Entry into the national phase

Ref document number: 2010353673

Country of ref document: AU

Date of ref document: 20100813

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE