Card application data backup and recovery method and related equipment

Abstract

The present invention provides a card application data backup and recovery method and related equipment, relating to the field of terminal data. The card application data backup method includes: randomly generating a first key within a card; storing the first key within the card; encrypting personalized data of a first application within the card using the first key, where the first application is a card application installed within the card; and backing up the encrypted personalized data. In embodiments of the present invention, by encrypting the personalized data of the card application and storing the encryption key within the card, the security of the personalized data is improved while facilitating the recovery of the personalized data by the card application.

Description

Technical Field

[0001] The present invention relates to the field of terminal data technology, and in particular to a card application data backup and recovery method and related equipment. Background Art

[0002] The installation and deletion of smart card (e.g., SIM card of a mobile terminal) applications belong to card content management. In the current card content management specifications, when deleting a card application, all application data of the application needs to be deleted, including the user's personalized data, such as the certificate, key, PIN, balance, etc. when the user uses the application; and when updating data, it is also necessary to delete the application first, and then re-download and install the updated application. This update process will also delete all application data of the card application, that is, the user's personalized data will be lost during the card application update process. Taking the security applications of smart cards as an example, such as bank shield and bus card, the user's personalized data cannot be retained, which means that after deleting and reinstalling the application or upgrading the application, the user needs to go to the bank to reapply for bank shield and bus card balances, which cannot be retained for continued use. This brings inconvenience to users and is not conducive to business development.

[0003] It can be seen that in the prior art, after a card application is deleted or updated, it is difficult to restore the user's personalized data, which is inconvenient for the user to reinstall or update the application subsequently. Summary of the Invention

[0004] The embodiment of the present invention provides a card application data backup and recovery method and related equipment to solve the problem that it is difficult to restore the user's personalized data after the existing card application is deleted or updated.

[0005] To solve the above-mentioned technical problems, the present invention is achieved as follows:

[0006] In a first aspect, an embodiment of the present invention provides a card application data backup method, the method comprising:

[0007] A first secret key is randomly generated in the card;

[0008] Storing the first secret key in the card;

[0009] encrypting personalized data of a first application in the card using the first secret key, where the first application is a card application installed in the card;

[0010] Back up encrypted personal data.

[0011] Optionally, the step of storing the first secret key in the card includes:

[0012] encrypting the first key using a second key, wherein the second key is generated based on the card identifier when the first application is personalized;

[0013] The encrypted first secret key is stored in the card.

[0014] Optionally, the step of storing the encrypted first secret key in the card includes:

[0015] Storing the encrypted first secret key in the card file system;

[0016] and / or,

[0017] storing the encrypted first secret key in a second application in the card, where the second application is a card application installed in the card;

[0018] and / or,

[0019] The encrypted first secret key is stored in the card operating system COS.

[0020] Optionally, the second application is installed into the card by the service platform of the first application;

[0021] The step of storing the encrypted first secret key in the second application in the card includes:

[0022] In the case where the first application is a preset application, the encrypted first secret key is stored in the second application through the inter-application communication interface.

[0023] Optionally, the step of backing up the encrypted personalized data includes:

[0024] The encrypted personalized data is backed up to the cloud, and / or the encrypted personalized data is backed up to the card file system in the card.

[0025] In a second aspect, an embodiment of the present invention provides a card application data recovery method, the method comprising:

[0026] Obtaining a first secret key from a card, wherein the first secret key is used to encrypt personalized data of a first application in the card, the first application being a card application installed in the card;

[0027] Obtaining personalized data encrypted using the first secret key;

[0028] The encrypted personalized data is decrypted using the first secret key.

[0029] Optionally, obtaining the first secret key from the card includes:

[0030] Obtaining a second secret key based on the card identifier;

[0031] Obtaining the first secret key encrypted with the second secret key stored in the card;

[0032] The encrypted first key is decrypted using the second key to obtain the first key.

[0033] Optionally, the step of obtaining the first key encrypted with the second key stored in the card includes:

[0034] Reading the encrypted first key stored in the card file system in the card;

[0035] or,

[0036] reading the encrypted first key of a second application stored in the card, where the second application is a card application installed in the card;

[0037] or,

[0038] The encrypted first secret key stored in the card operating system COS is read.

[0039] Optionally, the step of obtaining the personalized data encrypted using the first secret key includes:

[0040] Obtaining the encrypted personalized data from the cloud;

[0041] Alternatively, the encrypted personalized data is obtained from a card file system in the card.

[0042] In a third aspect, an embodiment of the present invention provides a card application data backup device, the device comprising:

[0043] A generation module, used to randomly generate a first secret key in the card;

[0044] A first secret key storage module, used for storing the first secret key in the card;

[0045] an encryption module, configured to encrypt personalized data of a first application in the card using the first secret key, where the first application is a card application installed in the card;

[0046] The backup module is used to back up encrypted personalized data.

[0047] In a fourth aspect, an embodiment of the present invention provides an electronic device, including a processor,

[0048] The processor is configured to randomly generate a first secret key in the card;

[0049] Storing the first secret key in the card;

[0050] encrypting personalized data of a first application in the card using the first secret key, where the first application is a card application installed in the card;

[0051] Back up encrypted personal data.

[0052] In a fifth aspect, an embodiment of the present invention provides an electronic device comprising: a processor, a memory, and a program stored in the memory and executable on the processor, wherein when the program is executed by the processor, the steps of the card application data backup method described in the first aspect are implemented.

[0053] In a sixth aspect, an embodiment of the present invention provides a computer-readable storage medium having a computer program stored thereon. When the computer program is executed by a processor, the steps of the card application data backup method described in the first aspect are implemented.

[0054] In a seventh aspect, an embodiment of the present invention provides a card application data recovery device, comprising:

[0055] a first acquisition module, configured to acquire a first secret key from a card, wherein the first secret key is used to encrypt personalized data of a first application in the card, the first application being a card application installed in the card;

[0056] A second acquisition module, configured to acquire the personalized data encrypted using the first secret key;

[0057] A decryption module is configured to decrypt the encrypted personalized data using the first secret key.

[0058] In an eighth aspect, an embodiment of the present invention provides an electronic device, including a processor,

[0059] The processor is configured to obtain a first secret key from the card, wherein the first secret key is used to encrypt personalized data of a first application in the card, the first application being a card application installed in the card;

[0060] Obtaining personalized data encrypted using the first secret key;

[0061] The encrypted personalized data is decrypted using the first secret key.

[0062] In the ninth aspect, an embodiment of the present invention provides an electronic device comprising: a processor, a memory, and a program stored in the memory and runnable on the processor, wherein when the program is executed by the processor, the steps of the card application data recovery method described in the second aspect are implemented.

[0063] In a tenth aspect, an embodiment of the present invention provides a computer-readable storage medium having a computer program stored thereon. When the computer program is executed by a processor, the steps of the card application data recovery method described in the second aspect are implemented.

[0064] In the technical solution of the embodiment of the present invention, when backing up card application data, a first key is randomly generated within the card; the first key is stored within the card; the personalized data of a first application within the card is encrypted using the first key, where the first application is a card application installed within the card; the encrypted personalized data is backed up; and when restoring card application data, the first key is retrieved from the card, where the first key is used to encrypt the personalized data of the first application within the card, where the first application is a card application installed within the card; the personalized data encrypted using the first key is retrieved; and the encrypted personalized data is decrypted using the first key. By encrypting the personalized data of the card application and storing the encryption key within the card, the security of the personalized data is improved while facilitating the restoration of the personalized data by the card application. BRIEF DESCRIPTION OF THE DRAWINGS

[0065] In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the following briefly introduces the drawings required for use in describing the embodiments of the present invention. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0066] Figure 1 This is a flow chart of a card application data backup method provided by an embodiment of the present invention;

[0067] Figure 2a is a schematic diagram of a card technology architecture provided by an embodiment of the present invention;

[0068] Figure 2b is a schematic diagram of a card technology architecture provided by an embodiment of the present invention;

[0069] Figure 3 1 is a schematic diagram of a card application data backup method provided by an embodiment of the present invention;

[0070] Figure 4 This is a flow chart of a card application data recovery method provided by an embodiment of the present invention;

[0071] Figure 5 1 is a schematic diagram of a card application data recovery method provided by an embodiment of the present invention;

[0072] Figure 6 1 is a schematic diagram of a card application data backup device provided by an embodiment of the present invention;

[0073] Figure 7 is a schematic diagram of an electronic device provided by an embodiment of the present invention;

[0074] Figure 8is a schematic diagram of a card application data recovery device provided by an embodiment of the present invention;

[0075] Figure 9 is a schematic diagram of another electronic device provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0076] The following will clearly and completely describe the technical solutions in the embodiments of the present invention in conjunction with the accompanying drawings. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of them. All other embodiments obtained by ordinary technicians in this field based on the embodiments of the present invention without making any creative efforts shall fall within the scope of protection of the present invention.

[0077] In an embodiment of the present invention, a card application data backup method is proposed to solve the problem that it is difficult to restore a user's personalized data after the existing card application is deleted or updated.

[0078] See also Figure 1 , Figure 1 FIG. 1 is a flow chart of a card application data backup method provided by an embodiment of the present invention. Figure 1 As shown, the method includes the following steps:

[0079] Step 101: randomly generate a first secret key in the card.

[0080] In the embodiment of the present invention, the card may be a smart card, for example, a mobile terminal SIM card, a smart card including a secure element (SE), etc. Optionally, the card is a card that complies with the relevant requirements of Global Platform Card Specification 2.2.1 (GP2.2.1), and its technical architecture can be referred to Figure 2a .

[0081] The above card application is installed in the card. Optionally, the card application can be pre-installed or loaded into the card by downloading through the TSM (Trusted Service Management) platform. Taking the mobile terminal SIM card as an example, its technical architecture can be referred to Figure 2b , in which Java applets and Toolkit appletes modules are card applications.

[0082] A first secret key is randomly generated in the card and is used to encrypt the personalized data generated during the card application personalization process. The above personalized data includes information when the user uses the application, such as certificates, keys, PINs, balances, etc.

[0083] Step 102: Store the first secret key in the card.

[0084] In this embodiment of the present invention, in step 102, the first key is stored within the card. This means that the key used to encrypt the user's personalized data is stored without leaving the card, thereby improving the security of the user's personalized data. The first key can be stored in a card file system, a second application within the card, and / or a chip operating system (COS) within the card, where the second application is a card application installed within the card. This storage can be performed directly on the first key itself or after further encryption.

[0085] Step 103: Use the first secret key to encrypt personalized data of a first application in the card, where the first application is a card application installed in the card.

[0086] In this embodiment of the present invention, in step 103, the first key is used to encrypt the card application personalized data, facilitating the subsequent secure backup of the personalized data. Because the first key used to encrypt the personalized data is stored within the card, i.e., the key never leaves the card, the encrypted personalized data can be backed up in a more flexible manner, either on or off the card.

[0087] Here, it should be understood that the order of step 102 and step 103 in the method of the specific embodiment of the present invention is not limited. Step 102 can be executed first and then step 103, or step 103 can be executed first and then step 102, or they can be executed simultaneously.

[0088] Step 104: Back up the encrypted personalized data.

[0089] In the embodiment of the present invention, in the above step 104, the encrypted personalized data may be backed up inside the card and / or outside the card.

[0090] Optionally, the encrypted personalized data is backed up to the cloud, and / or the encrypted personalized data is backed up to a card file system in the card.

[0091] Backing up the encrypted personalized data to the cloud can reduce the space occupied by the personalized data backup on the card. Optionally, backing up the encrypted personalized data to the cloud can be done through a secure channel between the card application and the service platform corresponding to the card application. The service platform can be understood as a platform outside the card that provides application services for the card application. For example, the service platform for a bank shield-type card application is a bank service platform provided by the bank, while the service platform for a bus card-type card application is a bus service platform provided by the bus system. Backing up the personalized data to the cloud through this secure channel can further improve the security of the personalized data backup.

[0092] Among them, the encrypted personalized data is backed up to the card file system in the card, and the encrypted personalized data can be backed up to the card file system by accessing the relevant API (Application Programming Interface) through files such as UICC (Universal Integrated Circuit Card) / USIM (Universal Subscriber Identity Module).

[0093] The above-mentioned backup method is adopted in this embodiment, which can retain personalized data without loss when the card application is reinstalled or upgraded. There is no need to re-personalize after reinstallation or update. Users do not need to go to the business outlets to re-sign and the balance can continue to be used. It can effectively improve user experience and promote the development of card carrier business.

[0094] Optionally, the above step 102 includes:

[0095] encrypting the first key using a second key, wherein the second key is generated based on the card identifier when the first application is personalized;

[0096] The encrypted first secret key is stored in the card.

[0097] The card application (the first application) adds a second key during personalization. This second key is associated with the first application, and for the first application, all cards with the same ID have the same second key. Optionally, the second key is derived using a unique card identifier, such as an ICCID, to ensure that all cards with the same ID have the same second key for the same application. The first key is encrypted using the second key and stored on the card. Even if another application (not the first application) reads the encrypted first key on the card, it cannot decrypt it to obtain the first key and thus decrypt the encrypted personalized data, further enhancing the security of the personalized data backup. Because the second key is associated with the first application, all cards with the same ID have the same second key for the same application. When the first application is deleted and reinstalled or updated, the second key can be restored according to pre-set rules to decrypt the first key and, therefore, the encrypted personalized data.

[0098] The step of storing the encrypted first secret key in the card includes:

[0099] Storing the encrypted first secret key in the card file system;

[0100] and / or,

[0101] storing the encrypted first secret key in a second application in the card, where the second application is a card application installed in the card;

[0102] and / or,

[0103] The encrypted first secret key is stored in the card operating system COS.

[0104] Optionally, storing the encrypted first key in a card file system in the card includes: storing the encrypted first key in a card file system in the card through a file access related API (file system API) such as UICC / USIM.

[0105] Optionally, when the first key is stored by storing the encrypted first key in a second application in the card, the second application needs to be installed before storage, and the second application is used to store the encrypted first key.

[0106] Optionally, the second application is installed into the card by the service platform of the first application; and storing the encrypted first secret key into the second application in the card includes:

[0107] In the case where the first application is a preset application, the encrypted first secret key is stored in the second application through the inter-application communication interface.

[0108] The second application is installed into the card by the business platform corresponding to the first application, and the second application uses the first application as the preset application, that is, the second application uses the first application as a legitimate application, so that the second application is allowed to store the first key corresponding to the first application. Optionally, the second application determines whether the first application is a legitimate application by judging the AID (Application Identifier) ​​of the first application. This legitimacy judgment is also applicable to reading the first key from the second application, preventing illegal applications from obtaining the (encrypted) first key, thereby improving the security of personalized data backup.

[0109] Optionally, storing the encrypted first key in the card operating system COS includes: storing the encrypted first key in the card operating system COS by calling a system API. The system API distinguishes application data by AID and provides backup and recovery services for applications. That is, the system API ensures that the first application cannot read or write data stored in COS by other applications, and the data stored in COS by the first application cannot be read or written by other applications. Storing the encrypted first key in the card operating system COS can improve the security of personalized data backup.

[0110] The card application data backup method in this embodiment can also be referred to in the attached Figure 3 The diagram shows a card application data backup method.

[0111] The card application data backup method in this embodiment randomly generates a first key within the card; stores the first key within the card; uses the first key to encrypt the personalized data of a first application within the card, where the first application is a card application installed within the card; and backs up the encrypted personalized data. By encrypting the personalized data of the card application and storing the encryption key within the card, this embodiment of the present invention facilitates the restoration of the personalized data by the card application while improving the security of the personalized data.

[0112] See also Figure 4 , Figure 4 This is a flow chart of a card application data recovery method provided by an embodiment of the present invention. Figure 4 As shown, the method includes the following steps:

[0113] Step 401: Obtain a first key from a card, wherein the first key is used to encrypt personalized data of a first application in the card, and the first application is a card application installed in the card.

[0114] The first key used to encrypt the personalized data of the first application is stored on the card. This ensures that the key is not removed from the card, thus improving the security of the user's personalized data. When data is restored, the first key is retrieved from the card.

[0115] Step 402: Obtain personalized data encrypted using the first secret key.

[0116] Because the first key used to encrypt the personalized data is stored within the card, i.e., the key never leaves the card, the encrypted personalized data can be backed up in a more flexible manner. The encrypted personalized data can be backed up within the card and / or off the card. The personalized data encrypted with the first key can be obtained from within the card and / or off the card.

[0117] Optionally, the encrypted personalized data is obtained from the cloud; or, the encrypted personalized data is obtained from a card file system in the card.

[0118] Optionally, obtaining the encrypted personalized data from the cloud includes: obtaining the encrypted personalized data backed up by the service platform from the cloud through a secure channel between the card application and the service platform corresponding to the card application.

[0119] Step 403: Decrypt the encrypted personalized data using the first secret key.

[0120] Here, it should be understood that the order of step 401 and step 402 in the method of the specific embodiment of the present invention is not limited. Step 401 can be executed first and then step 402, or step 402 can be executed first and then step 401, or they can be executed simultaneously.

[0121] Optionally, the above step 401 includes:

[0122] Obtaining a second secret key based on the card identifier;

[0123] Obtaining the first secret key encrypted with the second secret key stored in the card;

[0124] The encrypted first key is decrypted using the second key to obtain the first key.

[0125] The first key is further encrypted with the second key and stored within the card. To retrieve the first key from the card, the second key is obtained based on the card identifier to decrypt the first key, thereby obtaining the first key. The second key is generated based on the card identifier when the first application is personalized; the second key is associated with the first application, and for the first application, cards with the same ID have the same second key. Optionally, the second key can be recovered based on the dispersion rules and the card identifier and stored within the first application. Optionally, the service platform corresponding to the card application recovers the second key based on the dispersion rules and the card identifier and writes the second key to the first application via a secure channel between the card application and the service platform.

[0126] Optionally, the step of obtaining the first key encrypted with the second key stored in the card includes:

[0127] Reading the encrypted first key stored in the card file system in the card;

[0128] or,

[0129] reading the encrypted first key of a second application stored in the card, where the second application is a card application installed in the card;

[0130] or,

[0131] The encrypted first secret key stored in the card operating system COS is read.

[0132] The reading of the encrypted first key of the card file system stored in the card may be performed by reading the encrypted first key of the card file system stored in the card through a file system API.

[0133] The reading of the encrypted first key of the second application stored in the card may be reading the encrypted first key of the second application stored in the card through an inter-application calling interface.

[0134] The reading of the encrypted first key stored in the card operating system COS may be performed by reading the encrypted first key stored in the card operating system COS through a system API.

[0135] The card application data recovery method in this embodiment can also be referred to in the attached Figure 5 The diagram shows a card application data recovery method.

[0136] After reinstalling or upgrading the card application, the personalized data decrypted in step 403 can be restored to the reinstalled or upgraded card application, that is, the personalized data can be retained without loss when the card application is reinstalled or upgraded. There is no need to re-personalize after reinstalling or updating. Users do not need to go to the business outlets to re-sign and the balance can continue to be used, which can effectively improve user experience and promote the development of card carrier business.

[0137] It should be noted that this embodiment is Figure 1 The implementation method of the card application data recovery method corresponding to the embodiment of the card application data backup method shown in FIG. Figure 1 To avoid duplication, the relevant descriptions in the illustrated embodiment will not be repeated in this embodiment.

[0138] The above optional implementation can be found in Figure 1 To avoid duplication, the relevant descriptions in the illustrated embodiment will not be repeated in this embodiment.

[0139] The card application data recovery method in this embodiment obtains a first key from the card, wherein the first key is used to encrypt personalized data of a first application within the card, the first application being a card application installed on the card; obtains the personalized data encrypted using the first key; and decrypts the encrypted personalized data using the first key. In this embodiment of the present invention, the personalized data of the card application is encrypted and the encryption key is stored within the card. During data recovery, the key is retrieved from the card, thereby facilitating recovery of the personalized data by the card application while improving the security of the personalized data.

[0140] See also Figure 6 , Figure 6 Schematic diagram of a card application data backup device provided by an embodiment of the present invention. Figure 6 As shown, the card application data backup device 600 includes:

[0141] A generating module 601 is used to randomly generate a first secret key in the card;

[0142] A first key storage module 602, configured to store the first key in the card;

[0143] an encryption module 603, configured to encrypt personalized data of a first application in the card using the first secret key, where the first application is a card application installed in the card;

[0144] The backup module 604 is used to back up the encrypted personalized data.

[0145] Optionally, the first key storage module 602 includes:

[0146] a first key encryption unit, configured to encrypt the first key using a second key, wherein the second key is generated based on a card identifier when the first application is personalized;

[0147] The first secret key storage unit is used to store the encrypted first secret key in the card.

[0148] Optionally, the first key storage unit specifically includes:

[0149] The first storage subunit is used to store the encrypted first secret key in a card file system in the card;

[0150] and / or,

[0151] a second storage subunit, configured to store the encrypted first secret key in a second application in the card, where the second application is a card application installed in the card;

[0152] and / or,

[0153] The third storage subunit is used to store the encrypted first secret key in the card operating system COS.

[0154] Optionally, the second application is installed into the card by the service platform of the first application;

[0155] The second storage subunit is specifically configured to store the encrypted first secret key in a second application via an inter-application communication interface when the first application is a preset application.

[0156] Optionally, the backup module 604 is specifically configured to back up the encrypted personalized data to the cloud, and / or back up the encrypted personalized data to a card file system in the card.

[0157] It should be noted that this embodiment is Figure 1 The implementation of the card application data backup device in the embodiment shown is shown in FIG. Figure 1 To avoid duplication, the relevant descriptions in the illustrated embodiment will not be repeated in this embodiment.

[0158] The card application data backup device provided in the embodiment of the present invention is a device capable of executing the above-mentioned card application data backup method. Therefore, all implementation methods in the above-mentioned card application data backup method embodiment are applicable to the device and can achieve the same or similar beneficial effects.

[0159] For details, see Figure 7 As shown, an embodiment of the present invention further provides an electronic device, including a bus 701 , a transceiver 702 , an antenna 703 , a bus interface 704 , a processor 705 and a memory 706 .

[0160] Furthermore, the processor 705 is configured to randomly generate a first secret key in the card;

[0161] Storing the first secret key in the card;

[0162] encrypting personalized data of a first application in the card using the first secret key, where the first application is a card application installed in the card;

[0163] Back up encrypted personal data.

[0164] Optionally, the step of storing the first secret key in the card includes:

[0165] encrypting the first key using a second key, wherein the second key is generated based on the card identifier when the first application is personalized;

[0166] The encrypted first secret key is stored in the card.

[0167] Optionally, the step of storing the encrypted first secret key in the card includes:

[0168] Storing the encrypted first secret key in the card file system;

[0169] and / or,

[0170] storing the encrypted first secret key in a second application in the card, where the second application is a card application installed in the card;

[0171] and / or,

[0172] The encrypted first secret key is stored in the card operating system COS.

[0173] Optionally, the second application is installed into the card by the service platform of the first application;

[0174] The step of storing the encrypted first secret key in the second application in the card includes:

[0175] In the case where the first application is a preset application, the encrypted first secret key is stored in the second application through the inter-application communication interface.

[0176] Optionally, the step of backing up the encrypted personalized data includes:

[0177] The encrypted personalized data is backed up to the cloud, and / or the encrypted personalized data is backed up to the card file system in the card.

[0178] exist Figure 7In the embodiment, the bus architecture (represented by bus 701) is shown. Bus 701 may include any number of interconnected buses and bridges. Bus 701 links together various circuits including one or more processors represented by processor 705 and memory represented by memory 706. Bus 701 may also link together various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and are therefore not described further herein. Bus interface 704 provides an interface between bus 701 and transceiver 702. Transceiver 702 may be one element or multiple elements, such as multiple receivers and transmitters, providing a unit for communicating with various other devices on a transmission medium. Data processed by processor 705 is transmitted on a wireless medium via antenna 703. Furthermore, antenna 703 receives data and transmits the data to processor 705.

[0179] The processor 705 is responsible for managing the bus 701 and general processing, and may also provide various functions, including timing, peripheral interfaces, voltage regulation, power management, and other control functions. The memory 706 may be used to store data used by the processor 705 when performing operations.

[0180] Optionally, the processor 705 may be a CPU, an ASIC, an FPGA, or a CPLD.

[0181] It should be noted that this embodiment is Figure 1 The implementation of the card application data backup device in the embodiment shown is shown in FIG. Figure 1 To avoid duplication, the relevant descriptions in the illustrated embodiment will not be repeated in this embodiment.

[0182] The electronic backup device provided in the embodiment of the present invention is a device capable of executing the above-mentioned card application data backup method. Therefore, all implementation methods in the above-mentioned card application data backup method embodiment are applicable to the device and can achieve the same or similar beneficial effects.

[0183] An embodiment of the present invention further provides an electronic device comprising: a processor, a memory, and a program stored in the memory and executable on the processor. When the program is executed by the processor, the various processes of the above-mentioned card application data backup method embodiment are implemented, and the same technical effect can be achieved. To avoid repetition, they will not be described here.

[0184] An embodiment of the present invention further provides a computer-readable storage medium having a computer program stored thereon. When executed by a processor, the computer program implements the various processes of the aforementioned card application data backup method embodiment and achieves the same technical effects. To avoid repetition, the details are not described here. The computer-readable storage medium may be, for example, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0185] See also Figure 8 , Figure 8 FIG. 1 is a schematic diagram of a card application data recovery device provided by an embodiment of the present invention. Figure 8 As shown, the card application data recovery device 800 includes:

[0186] A first acquisition module 801 is configured to acquire a first key from a card, wherein the first key is used to encrypt personalized data of a first application in the card, the first application being a card application installed in the card;

[0187] A second obtaining module 802 is configured to obtain the personalized data encrypted using the first key;

[0188] The decryption module 803 is configured to decrypt the encrypted personalized data using the first secret key.

[0189] Optionally, the first obtaining module 801 includes:

[0190] A first obtaining unit, configured to obtain a second secret key based on a card identifier;

[0191] A second obtaining unit is used to obtain the first secret key encrypted with the second secret key stored in the card;

[0192] The first decryption unit is configured to decrypt the encrypted first key using the second key to obtain the first key.

[0193] Optionally, the second acquiring unit includes:

[0194] a first reading sub-unit, configured to read the encrypted first secret key stored in the card file system in the card;

[0195] or,

[0196] a second reading subunit, configured to read the encrypted first secret key of a second application stored in the card, where the second application is a card application installed in the card;

[0197] or,

[0198] The third reading sub-unit is used to read the encrypted first secret key stored in the card operating system COS.

[0199] The second acquisition module 802 includes:

[0200] A cloud acquisition unit, configured to acquire the encrypted personalized data from the cloud;

[0201] or,

[0202] The card acquisition unit is used to acquire the encrypted personalized data from the card file system in the card.

[0203] It should be noted that this embodiment is Figure 4 The embodiment of the card application data recovery device corresponding to the embodiment shown in the figure can be found in the specific embodiment. Figure 4 To avoid duplication, the relevant descriptions in the illustrated embodiment will not be repeated in this embodiment.

[0204] The card application data recovery device provided in the embodiment of the present invention is a device capable of executing the above-mentioned card application data recovery method. Therefore, all implementation methods in the above-mentioned card application data recovery method embodiment are applicable to the device and can achieve the same or similar beneficial effects.

[0205] For details, see Figure 9 As shown, an embodiment of the present invention further provides a receiving end device, including a bus 901, a transceiver 902, an antenna 903, a bus interface 904, a processor 905 and a memory 906.

[0206] Processor 905 is configured to obtain a first key from a card, wherein the first key is used to encrypt personalized data of a first application in the card, where the first application is a card application installed in the card;

[0207] Obtaining personalized data encrypted using the first secret key;

[0208] The encrypted personalized data is decrypted using the first secret key.

[0209] Optionally, obtaining the first secret key from the card includes:

[0210] Obtaining a second secret key based on the card identifier;

[0211] Obtaining the first secret key encrypted with the second secret key stored in the card;

[0212] The encrypted first key is decrypted using the second key to obtain the first key.

[0213] Optionally, the step of obtaining the first key encrypted with the second key stored in the card includes:

[0214] Reading the encrypted first key stored in the card file system in the card;

[0215] or,

[0216] reading the encrypted first key of a second application stored in the card, where the second application is a card application installed in the card;

[0217] or,

[0218] The encrypted first secret key stored in the card operating system COS is read.

[0219] Optionally, the step of obtaining the personalized data encrypted using the first secret key includes:

[0220] Obtaining the encrypted personalized data from the cloud;

[0221] Alternatively, the encrypted personalized data is obtained from a card file system in the card.

[0222] exist Figure 9 In the embodiment, the bus architecture (represented by bus 901) is shown. Bus 901 may include any number of interconnected buses and bridges. Bus 901 links together various circuits including one or more processors represented by processor 905 and memory represented by memory 906. Bus 901 may also link together various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and are therefore not described further herein. Bus interface 904 provides an interface between bus 901 and transceiver 902. Transceiver 902 may be one element or multiple elements, such as multiple receivers and transmitters, providing a unit for communicating with various other devices on a transmission medium. Data processed by processor 905 is transmitted on a wireless medium via antenna 903. Furthermore, antenna 903 receives data and transmits the data to processor 905.

[0223] The processor 905 is responsible for managing the bus 901 and general processing, and may also provide various functions, including timing, peripheral interfaces, voltage regulation, power management, and other control functions. The memory 906 may be used to store data used by the processor 905 when performing operations.

[0224] Optionally, the processor 905 may be a CPU, an ASIC, an FPGA, or a CPLD.

[0225] An embodiment of the present invention further provides an electronic device comprising: a processor, a memory, and a program stored in the memory and executable on the processor. When the program is executed by the processor, the various processes of the above-mentioned card application data recovery method embodiment are implemented, and the same technical effect can be achieved. To avoid repetition, they will not be described here.

[0226] An embodiment of the present invention further provides a computer-readable storage medium having a computer program stored thereon. When executed by a processor, the computer program implements the various processes of the aforementioned card application data recovery method embodiment and achieves the same technical effects. To avoid repetition, the details are not described here. The computer-readable storage medium may be, for example, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0227] It should be noted that, in this document, the terms "comprises," "includes," or any other variations thereof are intended to encompass non-exclusive inclusion, such that a process, method, article, or apparatus comprising a series of elements includes not only those elements but also other elements not explicitly listed, or elements inherent to such process, method, article, or apparatus. In the absence of further limitations, an element defined by the phrase "comprising a ..." does not exclude the presence of other identical elements in the process, method, article, or apparatus comprising the element.

[0228] Through the description of the above embodiments, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus the necessary general hardware platform, and of course can also be implemented by hardware, but in many cases the former is a better embodiment. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art, can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk), and includes a number of instructions for enabling a terminal (which can be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in each embodiment of the present invention.

[0229] The embodiments of the present invention are described above in conjunction with the accompanying drawings, but the present invention is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of the present invention, ordinary technicians in this field can also make many forms without departing from the scope of protection of the present invention and the claims, all of which are protected by the present invention.

Claims

1. A card application data backup method, characterized in that: include: A first secret key is randomly generated in the card; Storing the first secret key in the card; encrypting personalized data of a first application in the card using the first secret key, where the first application is a card application installed in the card; Backing up the encrypted personalized data, wherein the personalized data is decrypted and restored to the reinstalled or upgraded first application; The step of storing the first secret key in the card includes: Encrypting the first key using a second key, wherein the second key is generated based on the card identifier when the first application is personalized, and the second keys of cards with the same application and the same identity identifier are the same; Storing the encrypted first secret key in the card; The step of storing the encrypted first secret key in the card includes: The encrypted first secret key is stored in a second application in the card, where the second application is a card application installed in the card, and the second application is installed in the card by a service platform of the first application.

2. The method according to claim 1, characterized in that The step of storing the encrypted first secret key in the card further includes: Storing the encrypted first secret key in the card file system; and / or, The encrypted first secret key is stored in the card operating system COS.

3. The method according to claim 2, characterized in that The step of storing the encrypted first secret key in the second application in the card includes: In the case where the first application is a preset application, the encrypted first secret key is stored in the second application through the inter-application communication interface.

4. The method according to any one of claims 1 to 3, characterized in that The step of backing up the encrypted personalized data includes: The encrypted personalized data is backed up to the cloud, and / or the encrypted personalized data is backed up to the card file system in the card.

5. A card application data recovery method, characterized in that: include: Obtaining a first key from a card, wherein the first key is used to encrypt personalized data of a first application in the card, the first application being a card application installed in the card, and the first key is randomly generated in the card; Obtaining personalized data encrypted using the first secret key; decrypting the encrypted personalized data using the first secret key; Restoring the decrypted personalized data to the first application after reinstallation or upgrading; The obtaining of the first secret key from the card includes: Obtaining a second key based on the card identifier, where the second key is generated based on the card identifier when the first application is personalized. Cards with the same application and the same identity identifier have the same second key; Obtaining the first secret key encrypted with the second secret key stored in the card; decrypting the encrypted first key using the second key to obtain the first key; The step of obtaining the first key encrypted by the second key stored in the card includes: The encrypted first secret key of a second application stored in the card is read, where the second application is a card application installed in the card, and the second application is installed in the card by the service platform of the first application.

6. The method according to claim 5, characterized in that The step of obtaining the first key encrypted by the second key stored in the card further includes: Reading the encrypted first key stored in the card file system in the card; or, The encrypted first secret key stored in the card operating system COS is read.

7. The method according to any one of claims 5 to 6, characterized in that The step of obtaining the personalized data encrypted using the first secret key includes: Obtaining the encrypted personalized data from the cloud; Alternatively, the encrypted personalized data is obtained from a card file system in the card.

8. A card application data backup device, characterized in that: include: A generation module, used to randomly generate a first secret key in the card; A first secret key storage module, used for storing the first secret key in the card; an encryption module, configured to encrypt personalized data of a first application in the card using the first secret key, where the first application is a card application installed in the card; A backup module, configured to back up the encrypted personalized data, wherein the personalized data is decrypted and restored to the reinstalled or upgraded first application; The first key storage module includes: a first key encryption unit, configured to encrypt the first key using a second key, wherein the second key is generated based on the card identifier when the first application is personalized, and the second keys of cards with the same application and the same identity identifier are the same; A first secret key storage unit, configured to store the encrypted first secret key in the card; The first secret key storage unit specifically includes: The second storage subunit is used to store the encrypted first secret key in a second application in the card, where the second application is a card application installed in the card, and the second application is installed in the card by the service platform of the first application.

9. An electronic device, characterized in that: Including processor, The processor is configured to randomly generate a first secret key in the card; Storing the first secret key in the card; encrypting personalized data of a first application in the card using the first secret key, where the first application is a card application installed in the card; Backing up the encrypted personalized data, wherein the personalized data is decrypted and restored to the reinstalled or upgraded first application; The step of storing the first secret key in the card includes: Encrypting the first key using a second key, wherein the second key is generated based on the card identifier when the first application is personalized, and the second keys of cards with the same application and the same identity identifier are the same; Storing the encrypted first secret key in the card; The step of storing the encrypted first secret key in the card includes: The encrypted first secret key is stored in a second application in the card, where the second application is a card application installed in the card, and the second application is installed in the card by a service platform of the first application.

10. An electronic device, characterized in that: include: A processor, a memory, and a program stored in the memory and executable on the processor, wherein when the program is executed by the processor, the steps of the card application data backup method according to any one of claims 1 to 4 are implemented.

11. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a computer program, which, when executed by a processor, implements the steps of the card application data backup method according to any one of claims 1 to 4.

12. A card application data recovery device, characterized in that: include: a first acquisition module, configured to acquire a first key from a card, wherein the first key is used to encrypt personalized data of a first application in the card, the first application being a card application installed in the card, and the first key being randomly generated in the card; A second acquisition module, configured to acquire the personalized data encrypted using the first secret key; a decryption module, configured to decrypt the encrypted personalized data using the first secret key; The device is also used to: Restoring the decrypted personalized data to the first application after reinstallation or upgrading; The first acquisition module includes: a first acquiring unit, configured to acquire a second key based on the card identifier, where the second key is generated based on the card identifier when the first application is personalized, and the second keys of cards with the same application and the same identity identifier are the same; A second obtaining unit is used to obtain the first secret key encrypted with the second secret key stored in the card; a first decryption unit, configured to decrypt the encrypted first key using the second key to obtain the first key; The second acquiring unit includes: The second reading subunit is used to read the encrypted first secret key of the second application stored in the card, where the second application is a card application installed in the card, and the second application is installed in the card by the business platform of the first application.

13. An electronic device, characterized in that: Including processor, The processor is configured to obtain a first key from a card, wherein the first key is used to encrypt personalized data of a first application in the card, the first application being a card application installed in the card, and the first key is randomly generated in the card; Obtaining personalized data encrypted using the first secret key; decrypting the encrypted personalized data using the first secret key; Restoring the decrypted personalized data to the first application after reinstallation or upgrading; The obtaining of the first secret key from the card includes: Obtaining a second key based on the card identifier, where the second key is generated based on the card identifier when the first application is personalized. Cards with the same application and the same identity identifier have the same second key; Obtaining the first secret key encrypted with the second secret key stored in the card; decrypting the encrypted first key using the second key to obtain the first key; The step of obtaining the first key encrypted by the second key stored in the card includes: The encrypted first secret key of a second application stored in the card is read, where the second application is a card application installed in the card, and the second application is installed in the card by the service platform of the first application.

14. An electronic device, characterized in that: include: A processor, a memory, and a program stored in the memory and executable on the processor, wherein when the program is executed by the processor, the steps of the card application data recovery method according to any one of claims 5 to 7 are implemented.

15. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a computer program, which, when executed by a processor, implements the steps of the card application data recovery method according to any one of claims 5 to 7.

Images