CN113626833A - Card application data backup and recovery method and related equipment - Google Patents

Abstract

The invention provides a card application data backup and recovery method and related equipment, and relates to the field of terminal data, wherein the card application data backup method includes: randomly generating a first secret key in a card; A secret key for storage; use the first secret key to encrypt the personalized data of the first application in the card, where the first application is the card application installed in the card; backup the encrypted personalized data data. In the embodiment of the present invention, by encrypting the personalized data of the card application and storing the encryption key in the card, the security of the personalized data is improved while facilitating the card application to restore the personalized data.

Description

A kind of card application data backup and recovery method and related equipment

technical field

The present invention relates to the technical field of terminal data, in particular to a method and related equipment for backing up and restoring card application data.

Background technique

The installation and deletion of smart card (for example, SIM card of mobile terminal) applications belong to card content management. In the current card content management specification, when deleting a card application, it is necessary to delete all application data of the application, including the user's personalization data. , for example, the certificate, key, PIN, balance, etc. when the user uses the application; and when the data is updated, the application needs to be deleted first, and then the updated application is downloaded and installed again. This update process will also delete all the application data of the card application. Deletion, i.e. the user's personalization data is lost during the card application update process. Taking the security applications of smart cards as an example, such as bank shield, bus card, etc., the user's personal data cannot be retained, which means that the user needs to go to the bank to re-apply for the bank shield after deleting and reinstalling the application or after upgrading the application, and the balance of the bus card cannot be retained. Continuing to use it will bring inconvenience to users and is not conducive to business development.

It can be seen that, in the prior art, after the card application is deleted or updated, it is difficult to restore the user's personalized data, and it is inconvenient for the user to reinstall or update the subsequent application.

SUMMARY OF THE INVENTION

Embodiments of the present invention provide a card application data backup and recovery method and related equipment, so as to solve the problem that it is difficult to restore a user's personalized data after deletion or update of an existing card application.

In order to solve the above-mentioned technical problems, the present invention is achieved in this way:

In a first aspect, an embodiment of the present invention provides a method for backing up card application data, the method comprising:

Randomly generate the first secret key in the card;

storing the first secret key in the card;

encrypting personalization 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;

Back up encrypted personal data.

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

Encrypt the first secret key with a second secret key, wherein the second secret key is generated based on the card identifier when the first application is personalized;

The encrypted first secret key is stored in the card.

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

Store the encrypted first secret key in the card file system in the card;

and / or,

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;

and / or,

The encrypted first secret key is stored in the in-card operating system COS.

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

The storing of the encrypted first secret key in the second application in the card includes:

When the first application is a preset application, the encrypted first key is stored in the second application through an inter-application communication interface.

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

Back up encrypted personalization data to the cloud, and/or back up encrypted personalization data to the card file system in the card.

In a second aspect, an embodiment of the present invention provides a method for recovering card application data, the method comprising:

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, and the first application is a card application installed in the card;

obtaining personalized data encrypted with the first secret key;

The encrypted personalization data is decrypted using the first secret key.

Optionally, the obtaining the first secret key from the card includes:

Obtain the second secret key based on the card identifier;

Obtain the first secret key encrypted with the second secret key stored in the card;

Decrypt the encrypted first key by using the second key to obtain the first key.

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

reading the encrypted first secret key of the card file system stored in the card;

or,

reading 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;

or,

Read the encrypted first secret key stored in the operating system COS in the card.

Optionally, the step of obtaining the personalized data encrypted with the first secret key includes:

obtain the encrypted personalization data from the cloud;

Alternatively, the encrypted personalization data is obtained from the card file system in the card.

In a third aspect, an embodiment of the present invention provides a device for backing up card application data, the device comprising:

a generating module for randomly generating the first secret key in the card;

a first secret key storage module for storing the first secret key in the card;

an encryption module, configured to 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;

Backup module for backing up encrypted personal data.

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

The processor is used to randomly generate the first secret key in the card;

storing the first secret key in the card;

encrypting personalization 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;

Back up encrypted personal data.

In a fifth aspect, an embodiment of the present invention provides an electronic device, including: a processor, a memory, and a program stored on the memory and executable on the processor, when the program is executed by the processor The steps of implementing the method for backing up card application data described in the first aspect above.

In a sixth aspect, an embodiment of the present invention provides a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, the card application described in the first aspect above is implemented Steps of data backup method.

In a seventh aspect, an embodiment of the present invention provides a card application data recovery device, including:

The first obtaining module is used to obtain the first secret key from the card, wherein the first secret key is used to encrypt the personalized data of the first application in the card, and the first application is installed in the card. Card application within the card;

A second acquisition module, configured to acquire personalized data encrypted with the first secret key;

A decryption module, configured to decrypt the encrypted personalization data using the first secret key.

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

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, and the first application is installed in the card. Card application within the card;

obtaining personalized data encrypted with the first secret key;

The encrypted personalization data is decrypted using the first secret key.

In a ninth aspect, an embodiment of the present invention provides an electronic device, including: a processor, a memory, and a program stored on the memory and executable on the processor, when the program is executed by the processor The steps of implementing the method for recovering card application data described in the second aspect above.

In a tenth aspect, an embodiment of the present invention provides a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, the card application described in the second aspect above is implemented Steps of data recovery method.

In the above technical solution of the embodiment of the present invention, when the card application data is backed up, a first secret key is randomly generated in the card; the first secret key is stored in the card; the first secret key is stored in the card; The personalized data of the first application is encrypted, the first application is the card application installed in the card; the encrypted personalized data is backed up; when the card application data is restored, the first secret key is obtained from the card, wherein , the first secret key is used to encrypt the personalized data of the first application in the card, and the first application is the card application installed in the card; Personalization data; decrypt the encrypted personalization data using the first secret key. By encrypting the personalized data of the card application and storing the encryption key in the card, the security of the personalized data is improved while the recovery of the personalized data is convenient for the card application.

Description of drawings

In order to illustrate the technical solutions of the embodiments of the present invention more clearly, the following briefly introduces the accompanying drawings that need to be used in the description of the embodiments of the present invention. Obviously, the drawings in the following description are only some embodiments of the present invention. For those of ordinary skill in the art, other drawings can also be obtained from these drawings without creative labor.

1 is a flowchart of a method for backing up card application data provided by an embodiment of the present invention;

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

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

3 is a schematic diagram of a method for backing up card application data according to an embodiment of the present invention;

4 is a flowchart of a method for recovering card application data provided by an embodiment of the present invention;

5 is a schematic diagram of a method for recovering card application data provided by an embodiment of the present invention;

6 is a schematic diagram of a card application data backup device provided by an embodiment of the present invention;

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

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

FIG. 9 is a schematic diagram of still another electronic device provided by an embodiment of the present invention.

Detailed ways

The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, but not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the protection scope of the present invention.

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

Referring to FIG. 1, FIG. 1 is a flowchart of a method for backing up card application data provided by an embodiment of the present invention. As shown in FIG. 1, the method includes the following steps:

Step 101: Randomly generate a first secret key in the card.

In this embodiment of the present invention, the card may be a smart card (Smart Card), for example, a mobile terminal SIM card, a smart card including a secure element (Secure Element, SE), and the like. Optionally, the card is a card that complies with the relevant requirements of GlobalPlatform Card Specification 2.2.1 (GP2.2.1), and its technical architecture can refer to FIG. 2a.

The above-mentioned card application is installed in the card. Optionally, the card application may be preset or loaded into the card in a manner of downloading through a TSM (Trusted Service Management, Trusted Service Management) platform. Taking a mobile terminal SIM card as an example, its technical architecture can refer to Fig. 2b, wherein the Java applets and Toolkit appletes modules are card applications.

The first secret key is randomly generated in the card to encrypt the personalization data generated during the personalization process of the card application. The personalization data includes the information of the user when using the application, such as certificate, key, PIN, balance and so on.

Step 102: Store the first secret key in the card.

In the embodiment of the present invention, in the above step 102, the first secret key is stored in the card, that is, the secret key for encrypting the user's personalization data is stored in the form of the secret key not leaving the card, so as to improve the security of the user's personalization data. sex. Wherein, the first secret key is stored, and the first secret key can be stored in the card file system in the card, in the second application in the card, and/or in the card operating system COS (Chip operating system or Card operating system), wherein the second application is a card application installed in the card. The above-mentioned storage may be directly storing the first secret key itself, or may be storing the first secret key after further encryption.

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

In the embodiment of the present invention, in the above step 103, the personalized data encryption is applied to the card by using the first secret key, so as to facilitate the subsequent safe backup of the personalized data. Since the first secret key used to encrypt the personalization data is stored in the card, that is, the secret key cannot be stored in the card, so that the encrypted personalization data can be backed up in a more flexible way, and can be backed up in the card and/or outside the card. Encrypted personalization data is backed up.

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, and step 102 may be performed first and then step 103 may be performed, or step 103 may be performed first and then step 102 or simultaneously.

Step 104 , back up the encrypted personalized data.

In the embodiment of the present invention, in the foregoing step 104, the encrypted personalized data may be backed up in the card and/or outside the card.

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.

Among them, backing up the encrypted personalized data to the cloud can reduce the occupation of the card space by the personalized data backup. Optionally, backing up the encrypted personalized data to the cloud may be backing up the encrypted personalized data to the cloud through a secure channel between the card application and the business platform corresponding to the card application. Among them, the business platform can be understood as a platform that provides application services for card applications outside the card. For example, the business platform of the bank shield type card application is the banking business platform, which is provided by the bank, and the business of the bus card type card application. The platform is a public transportation business platform, which is provided by the public transportation system. Cloud backup through the above-mentioned secure channel can further improve the security of personalized data backup.

Wherein, the encrypted personalized data is backed up to the card file system in the card, which may be through files such as UICC (Universal Integrated Circuit Card, Universal Integrated Circuit Card)/USIM (Universal Subscriber Identity Module, Universal Subscriber Identity Module). Access the relevant API (ApplicationProgramming Interface, application program interface), and back up the encrypted personalized data to the card file system.

In this embodiment, the above-mentioned backup method is adopted, so that the personalized data can be kept without loss when the card application is reinstalled or the card application is upgraded. There is no need to re-personalize after the card application is reinstalled or updated. It can effectively improve user experience and promote the development of card carrier business.

Optionally, the above step 102 includes:

Encrypt the first secret key with a second secret key, wherein the second secret key is generated based on the card identifier when the first application is personalized;

The encrypted first secret key is stored in the card.

Wherein, the card application—the first application adds a second key during personalization, the second key is associated with the first application, and for the first application, the second keys of cards with the same ID are the same . Optionally, the second key is obtained by using a unique card identifier such as ICCID, which ensures that the second keys of cards with the same ID are consistent for the same application. Encrypt the first secret key with the second secret key, and store the encrypted first secret key in the card, even if other applications (not the first application) read the encrypted first secret key in the card The first secret key cannot be decrypted to obtain the first secret key, so that the encrypted personalized data cannot be decrypted, thereby further improving the security of the personalized data backup. Since the second key is associated with the first application, for the same application, the second keys of cards with the same ID are the same. When the first application is deleted and reinstalled or updated, the second key can still be restored according to the preset rules. The secret key is used to decrypt the first secret key, thereby further decrypting the encrypted personalization data.

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

Store the encrypted first secret key in the card file system in the card;

and / or,

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;

and / or,

The encrypted first secret key is stored in the in-card operating system COS.

Wherein, optionally, storing the encrypted first secret key in the card file system in the card includes: storing the encrypted first secret key through a file access related API (file system API) such as UICC/USIM to the card file system inside the card.

Optionally, when storing the first secret key by storing the encrypted first secret key in the second application in the card, the second application needs to be installed before storage, and the second application is used for Store the encrypted first secret key.

Optionally, the second application is installed in the card by the business platform of the first application; and the storing of the encrypted first secret key in the second application in the card includes:

When the first application is a preset application, the encrypted first key is stored in the second application through an inter-application communication interface.

The second application is installed in the card by the service platform corresponding to the first application, and the second application uses the first application as a preset application, that is, the second application uses the first application as a legal application, so the second application The first secret key corresponding to the first application is allowed to be stored. Optionally, the second application determines whether the first application is a legitimate application by determining an AID (Application Identifier, application identifier) of the first application. This legality judgment is also applicable to reading the first secret key from the second application, preventing illegal applications from obtaining the (encrypted) first secret key, thereby improving the security of personalized data backup.

Optionally, the storing the encrypted first secret key in the in-card operating system COS includes: storing the encrypted first secret key in the in-card operating system COS by calling a system API. The system API provides backup and recovery services for applications by distinguishing application data through AID, that is, the system API ensures that the first application cannot read and write data stored in COS by other applications, and the data stored in COS by the first application cannot be read and written by other applications. The encrypted first secret key is stored in the operating system COS in the card, which can improve the security of personalized data backup.

For the card application data backup method in this embodiment, reference may also be made to the schematic diagram of the card application data backup method shown in FIG. 3 .

The card in this embodiment applies the data backup method to randomly generate a first secret key in the card; store the first secret key in the card; use the first secret key to restore the first secret key in the card Personalized data of an application is encrypted, and the first application is a card application installed in the card; the encrypted personalized data is backed up. In the embodiment of the present invention, by encrypting the personalized data of the card application and storing the encryption key in the card, the security of the personalized data is improved while facilitating the card application to restore the personalized data.

Referring to FIG. 4, FIG. 4 is a flowchart of a method for recovering card application data provided by an embodiment of the present invention. As shown in FIG. 4, the method includes the following steps:

Step 401: Obtain 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, and the first application is a card installed in the card application.

The first secret key used to encrypt the personalization data of the first application is stored in the card, that is, the secret key used for encrypting the personalization data of the user is stored in the form that the secret key does not come out of the card, so as to improve the security of the personalization data of the user sex. When the data is recovered, the above-mentioned first secret key is obtained from the card.

Step 402: Obtain personalized data encrypted by using the first secret key.

Since the first secret key used to encrypt the personalization data is stored in the card, that is, the secret key cannot be stored in the card, so that the encrypted personalization data can be backed up in a more flexible way, and can be backed up in the card and/or outside the card. Encrypted personalization data is backed up. Wherein, in the obtaining of the personalized data encrypted with the first secret key, the personalized data encrypted with the first secret key may be obtained from inside the card and/or outside the card.

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.

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

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

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, and step 401 may be performed first and then step 402, or step 402 may be performed first and then step 401 or simultaneously.

Optionally, the above step 401 includes:

Obtain the second secret key based on the card identifier;

Obtain the first secret key encrypted with the second secret key stored in the card;

Decrypt the encrypted first key by using the second key to obtain the first key.

The first secret key is further encrypted by the second secret key and then stored in the card. When the first secret key is obtained from the card, it is necessary to obtain the second secret key based on the card identifier to decrypt the first secret key, so as to obtain the first secret key. Describe 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, the second keys of cards with the same ID are the same . Optionally, the second key can be recovered according to the distribution rule and the card identifier, and stored in the first application. Optionally, the business platform corresponding to the card application recovers the second key according to the dispersion rules and the card identifier, and writes the second key into the first key through the secure channel between the card application and the business platform. application.

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

reading the encrypted first secret key of the card file system stored in the card;

or,

reading 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;

or,

Read the encrypted first secret key stored in the operating system COS in the card.

Wherein, the reading of the encrypted first secret key of the card file system stored in the card may be reading the encrypted first secret key of the card file system stored in the card through a file system API key.

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

The reading of the encrypted first secret key stored in the operating system COS in the card may be reading the encrypted first secret key stored in the operating system COS in the card through a system API.

For the method for restoring card application data in this embodiment, reference may also be made to the schematic diagram of the method for restoring card application data shown in FIG. 5 .

After the card application is reinstalled or the card application is upgraded, 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 when the card application is reinstalled or the card application is upgraded. No loss, no need to re-personalize after reinstallation or update, users do not need to sign a new contract at a business outlet, and the balance can continue to be used, which can effectively improve the user experience and promote the development of card carrier business.

It should be noted that this embodiment is an implementation of the method for restoring card application data corresponding to the embodiment of the method for backing up card application data shown in FIG. For related descriptions, in order to avoid repeated descriptions, details are not repeated in this embodiment.

For the above-mentioned optional implementation manner, reference may be made to the relevant description in the embodiment shown in FIG. 1 . To avoid repeated descriptions, detailed descriptions are not repeated in this embodiment.

In the method for recovering card application data in this embodiment, a first secret key is obtained from the card, wherein the first secret key is used to encrypt the personalized data of the first application in the card, and the first application is A card application installed in the card; obtaining personalization data encrypted with the first secret key; decrypting the encrypted personalization data using the first secret key. In the embodiment of the present invention, by encrypting the personalization data of the card application, and storing the encryption key in the card, when the data is recovered, the key is obtained from the card, which facilitates the card application to recover the personalized data, and improves the personalization of the card application. data security.

Referring to FIG. 6, FIG. 6 is a schematic diagram of a card application data backup device provided by an embodiment of the present invention. As shown in FIG. 6, the card application data backup device 600 includes:

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

a first key storage module 602, configured to store the first key in the card;

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

The backup module 604 is used for backing up the encrypted personalization data.

Optionally, the first key storage module 602 includes:

a first secret key encryption unit, configured to encrypt the first secret key with a second secret key, wherein the second secret key is generated based on the card identifier when the first application is personalized;

The first secret key storage unit is used for storing the encrypted first secret key in the card.

Optionally, the first key storage unit specifically includes:

a first storage subunit for storing the encrypted first secret key in the card file system in the card;

and / or,

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;

and / or,

The third storage subunit is configured to store the encrypted first secret key in the in-card operating system COS.

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

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

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 the card file system in the card.

It should be noted that this embodiment is an implementation of the card application data backup device corresponding to the embodiment shown in FIG. 1 . For the specific implementation, please refer to the relevant description in the embodiment shown in FIG. 1 . The description is repeated, and details are not repeated in this embodiment.

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, and all implementations in the above-mentioned card application data backup method embodiments are applicable to the device, and can achieve the same or similar beneficial effect.

Specifically, as shown in FIG. 7 , 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 .

Further, the processor 705 is configured to randomly generate the first secret key in the card;

storing the first secret key in the card;

encrypting personalization 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;

Back up encrypted personal data.

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

Encrypt the first secret key with a second secret key, wherein the second secret key is generated based on the card identifier when the first application is personalized;

The encrypted first secret key is stored in the card.

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

Store the encrypted first secret key in the card file system in the card;

and / or,

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;

and / or,

The encrypted first secret key is stored in the in-card operating system COS.

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

The storing of the encrypted first secret key in the second application in the card includes:

When the first application is a preset application, the encrypted first key is stored in the second application through an inter-application communication interface.

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

Back up encrypted personalization data to the cloud, and/or back up encrypted personalization data to the card file system in the card.

In Figure 7, a bus architecture (represented by bus 701), which may include any number of interconnected buses and bridges, bus 701 will include one or more processors represented by processor 705 and memory represented by memory 706 The various circuits are linked together. The bus 701 may also link together various other circuits, such as peripherals, voltage regulators and power management circuits, etc., which are well known in the art and therefore will not be described further herein. Bus interface 704 provides an interface between bus 701 and transceiver 702 . Transceiver 702 may be a single element or multiple elements, such as multiple receivers and transmitters, providing means for communicating with various other devices over a transmission medium. The data processed by the processor 705 is transmitted on the wireless medium through the antenna 703 , and further, the antenna 703 also receives the data and transmits the data to the processor 705 .

Processor 705 is responsible for managing bus 701 and general processing, and may also provide various functions including timing, peripheral interface, voltage regulation, power management, and other control functions. In turn, memory 706 may be used to store data used by processor 705 in performing operations.

Optionally, the processor 705 may be a CPU, ASIC, FPGA or CPLD.

It should be noted that this embodiment is an implementation of the card application data backup device corresponding to the embodiment shown in FIG. 1 . For the specific implementation, please refer to the relevant description in the embodiment shown in FIG. 1 . The description is repeated, and details are not repeated in this embodiment.

The electronic backup device provided in the embodiment of the present invention is a device capable of executing the above-mentioned method for backing up card application data, and all implementations in the above-mentioned embodiments of the above-mentioned method for backing up card application data are applicable to the device, and can achieve the same or similar benefits. Effect.

An embodiment of the present invention further provides an electronic device, including: a processor, a memory, and a program stored on the memory and executable on the processor, and the program implements the above-mentioned card when executed by the processor Each process of the embodiments of the data backup method is applied, and the same technical effect can be achieved. To avoid repetition, details are not repeated here.

Embodiments of the present invention further provide a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, each process of the above-mentioned embodiment of the method for backing up application data for a card can be implemented, and can achieve the same In order to avoid repetition, the technical effect will not be repeated here. The computer-readable storage medium is, for example, a read-only memory (Read-Only Memory, ROM), a random access memory (Random Access Memory, RAM), a magnetic disk, or an optical disk.

Referring to FIG. 8, FIG. 8 is a schematic diagram of a card application data recovery device provided by an embodiment of the present invention. As shown in FIG. 8, the above card application data recovery device 800 includes:

The first obtaining module 801 is used to obtain a first secret key from the card, wherein the first secret key is used to encrypt the personalized data of the first application in the card, and the first application is installed in the card. the card application in the card;

A second obtaining module 802, configured to obtain personalized data encrypted by using the first secret key;

A decryption module 803, configured to decrypt the encrypted personalization data by using the first secret key.

Optionally, the first obtaining module 801 includes:

a first obtaining unit, configured to obtain the second secret key based on the card identifier;

A second obtaining unit, configured 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 secret key by using the second secret key to obtain the first secret key.

Optionally, the second obtaining unit includes:

a first reading subunit, used for reading the encrypted first secret key of the card file system stored in the card;

or,

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;

or,

The third reading subunit is used for reading the encrypted first secret key stored in the operating system COS in the card.

The second obtaining module 802 includes:

a cloud acquisition unit, configured to acquire the encrypted personalized data from the cloud;

or,

An in-card acquiring unit, configured to acquire the encrypted personalization data from a card file system in the card.

It should be noted that this embodiment is an implementation of the card application data recovery device corresponding to the embodiment shown in FIG. 4 , and reference may be made to the relevant description in the embodiment shown in FIG. 4 for the specific implementation. The description is repeated, and details are not repeated in this embodiment.

The card application data recovery device provided by the embodiment of the present invention is a device capable of executing the above-mentioned card application data recovery method, and all implementations in the above-mentioned card application data recovery method embodiments are applicable to the device, and can achieve the same or similar beneficial effect.

Specifically, as shown in FIG. 9 , 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 .

The processor 905 is configured to obtain a first secret key from the card, wherein the first secret key is used to encrypt the personalized data of a first application in the card, and the first application is installed on the card within the card app;

obtaining personalized data encrypted with the first secret key;

The encrypted personalization data is decrypted using the first secret key.

Optionally, the obtaining the first secret key from the card includes:

Obtain the second secret key based on the card identifier;

Obtain the first secret key encrypted with the second secret key stored in the card;

Decrypt the encrypted first key by using the second key to obtain the first key.

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

reading the encrypted first secret key of the card file system stored in the card;

or,

reading 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;

or,

Read the encrypted first secret key stored in the operating system COS in the card.

Optionally, the step of obtaining the personalized data encrypted with the first secret key includes:

obtain the encrypted personalization data from the cloud;

Alternatively, the encrypted personalization data is obtained from the card file system in the card.

In Figure 9, a bus architecture (represented by bus 901), which may include any number of interconnected buses and bridges, bus 901 will include one or more processors represented by processor 905 and memory represented by memory 906 The various circuits are linked together. The bus 901 may also link together various other circuits such as peripherals, voltage regulators, and power management circuits, etc., which are well known in the art and therefore will not be described further herein. Bus interface 904 provides an interface between bus 901 and transceiver 902 . Transceiver 902 may be a single element or multiple elements, such as multiple receivers and transmitters, that provide means for communicating with various other devices over a transmission medium. The data processed by the processor 905 is transmitted on the wireless medium through the antenna 903 , and further, the antenna 903 also receives the data and transmits the data to the processor 905 .

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

Optionally, the processor 905 may be a CPU, ASIC, FPGA or CPLD.

An embodiment of the present invention further provides an electronic device, including: a processor, a memory, and a program stored on the memory and executable on the processor, and the program implements the above-mentioned card when executed by the processor Each process of the data recovery method embodiment is applied, and the same technical effect can be achieved. To avoid repetition, details are not repeated here.

Embodiments of the present invention further provide a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium. When the computer program is executed by a processor, each process of the above-mentioned embodiment of the method for recovering application data for a card can be realized, and the same can be achieved. In order to avoid repetition, the technical effect will not be repeated here. The computer-readable storage medium is, for example, a read-only memory (Read-Only Memory, ROM), a random access memory (Random Access Memory, RAM), a magnetic disk, or an optical disk.

It should be noted that, herein, the terms "comprising", "comprising" or any other variation thereof are intended to encompass non-exclusive inclusion, such that a process, method, article or device comprising a series of elements includes not only those elements, It also includes other elements not expressly listed or inherent to such a process, method, article or apparatus. Without further limitation, an element qualified by the phrase "comprising a..." does not preclude the presence of additional identical elements in a process, method, article or apparatus that includes the element.

From the description of the above embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus a necessary general hardware platform, and of course hardware can also be used, but in many cases the former is better implementation. Based on this understanding, the technical solutions of the present invention can be embodied in the form of software products in essence or the parts that make contributions to the prior art, and the computer software products are stored in a storage medium (such as ROM/RAM, magnetic disk, CD-ROM), including several instructions to make a terminal (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) execute the methods described in the various embodiments of the present invention.

The embodiments of the present invention have been described above in conjunction with the accompanying drawings, but the present invention is not limited to the above-mentioned specific embodiments, which are merely illustrative rather than restrictive. Under the inspiration of the present invention, without departing from the spirit of the present invention and the scope protected by the claims, many forms can be made, which all belong to the protection of the present invention.

Claims (17)

1. a card application data backup method, is characterized in that, comprises: Randomly generate the first secret key in the card; storing the first secret key in the card; encrypting personalization 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; Back up encrypted personal data. 2. The method according to claim 1, wherein the step of storing the first secret key in the card comprises: Encrypt the first secret key with a second secret key, wherein the second secret key is generated based on the card identifier when the first application is personalized; The encrypted first secret key is stored in the card. 3. The method according to claim 2, wherein the step of storing the encrypted first secret key in the card comprises: Store the encrypted first secret key in the card file system in the card; and / or, 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; and / or, The encrypted first secret key is stored in the in-card operating system COS. 4. The method according to claim 3, wherein the second application is installed into the card by the service platform of the first application; The storing of the encrypted first secret key in the second application in the card includes: When the first application is a preset application, the encrypted first key is stored in the second application through an inter-application communication interface. 5. The method according to any one of claims 1 to 4, wherein the step of backing up the encrypted personalized data comprises: Back up encrypted personalization data to the cloud, and/or back up encrypted personalization data to the card file system in the card. 6. A method for recovering card application data, comprising: 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, and the first application is a card application installed in the card; obtaining personalized data encrypted with the first secret key; The encrypted personalization data is decrypted using the first secret key. 7. The method according to claim 6, wherein the obtaining the first secret key from the card comprises: Obtain the second secret key based on the card identifier; Obtain the first secret key encrypted with the second secret key stored in the card; Decrypt the encrypted first key by using the second key to obtain the first key. 8. The method according to claim 7, wherein the step of obtaining the first secret key encrypted with the second secret key stored in the card comprises: reading the encrypted first secret key of the card file system stored in the card; or, reading 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; or, Read the encrypted first secret key stored in the operating system COS in the card. 9. The method according to any one of claims 6 to 8, wherein the step of obtaining the personalized data encrypted by using the first secret key comprises: obtain the encrypted personalization data from the cloud; Alternatively, the encrypted personalization data is obtained from the card file system in the card. 10. A card application data backup device, comprising: a generating module for randomly generating the first secret key in the card; a first secret key storage module for storing the first secret key in the card; an encryption module, configured to 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; Backup module for backing up encrypted personal data. 11. An electronic device, characterized in that it comprises a processor, The processor is used to randomly generate the first secret key in the card; storing the first secret key in the card; encrypting personalization 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; Back up encrypted personal data. 12. An electronic device, characterized by comprising: a processor, a memory, and a program stored on the memory and executable on the processor, the program being executed by the processor to achieve as claimed in the claims Steps of the card application data backup method described in any one of 1 to 5. 13. A computer-readable storage medium, wherein a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, the computer program according to any one of claims 1 to 5 is implemented. Steps of the card application data backup method. 14. A card application data recovery device, comprising: The first obtaining module is used to obtain the first secret key from the card, wherein the first secret key is used to encrypt the personalized data of the first application in the card, and the first application is installed in the card. Card application within the card; A second acquisition module, configured to acquire personalized data encrypted with the first secret key; A decryption module, configured to decrypt the encrypted personalization data using the first secret key. 15. An electronic device, characterized in that it comprises a processor, 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, and the first application is installed in the card. Card application within the card; obtaining personalized data encrypted with the first secret key; The encrypted personalization data is decrypted using the first secret key. 16. An electronic device, characterized in that it comprises: a processor, a memory and a program stored on the memory and executable on the processor, the program being executed by the processor to achieve as claimed in the claims Steps of the card application data recovery method described in any one of 6 to 9. 17. A computer-readable storage medium, wherein a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, the computer program according to any one of claims 6 to 9 is implemented. The steps of the card application data recovery method.

Images