Identity authentication method and device in offline transaction scene
A multi-modal authentication system using public-private key pairs and blockchain identity management verifies the legitimacy of digital wallet users and terminals, addressing transaction risks and ensuring secure offline transactions.
Patent Information
- Application Number
- CN202310651252.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2023-06-02
- Publication Date
- 2024-12-03
- Estimated Expiration
- 2043-06-02
AI Technical Summary
Existing digital wallet transaction systems lack robust authentication methods to ensure the legitimacy of both the wallet terminal device and the wallet application, leading to risks of user fund loss and information leakage during offline transactions.
Implement a multi-modal authentication system using public-private key pairs and blockchain identity management to verify the legitimacy of both the hard wallet user and terminal, involving identity certificate issuance and storage of authentication records on a blockchain.
Enhances security and reliability of offline transactions by ensuring dual authentication of the terminal and application, with tamper-proof authentication records stored on the blockchain.
Smart Images

Figure CN119067667A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the field of digital wallet technology, and in particular to an identity authentication method and device in an offline transaction scenario. Background Art
[0002] Digital hard wallets generally implement digital wallet-related functions based on technologies such as security chips, and provide services to users based on IC cards, mobile terminals, wearable devices, and IoT devices. Supporting point-to-point offline transactions is a basic feature of hard wallets. During hard wallet transactions, transaction authentication and message authentication are usually performed based on cryptographic technologies such as signatures and encryption. However, these authentication methods only authenticate the transaction process at the message level. If a transaction is conducted with an illegal hard wallet terminal, it may lead to risks such as user fund loss and information leakage. The legitimacy of the hard wallet terminal device cannot be guaranteed during the transaction, nor can the legitimacy of the hard wallet application on the hard wallet terminal be guaranteed. Summary of the invention
[0003] In view of this, an embodiment of the present invention provides an identity authentication method and device in an offline transaction scenario to solve the technical problem of transaction risks.
[0004] To achieve the above object, according to one aspect of an embodiment of the present invention, an identity authentication method in an offline transaction scenario is provided, which is applied to a hard wallet and includes:
[0005] Generate a first public-private key pair of the hard wallet user and a second public-private key pair of the hard wallet terminal in the security chip respectively;
[0006] Submitting the first public key of the hard wallet user and the second public key of the hard wallet terminal to the blockchain identity management system, and receiving the hard wallet user identity identifier and the hard wallet terminal identity identifier returned by the blockchain identity management system;
[0007] Sending identity certificate issuance requests to a hard wallet user identity certificate issuing agency and a hard wallet terminal identity certificate issuing agency respectively, and receiving a hard wallet user identity certificate issued by the hard wallet user identity certificate issuing agency and a hard wallet terminal identity certificate issued by the hard wallet terminal identity certificate issuing agency;
[0008] In an offline transaction scenario, identity authentication is performed based on the hard wallet user identity credential and the hard wallet terminal identity identifier.
[0009] In addition, according to another aspect of an embodiment of the present invention, an identity authentication method in an offline transaction scenario is provided, which is applied to a hard wallet user identity certificate issuing agency, including:
[0010] Generate a third public-private key pair and submit the third public key to the blockchain identity management system;
[0011] Receiving the identity identifier of the hard wallet user identity certificate issuing agency returned by the blockchain identity management system;
[0012] Receive a hard wallet user identity credential issuance request sent by the hard wallet;
[0013] The hard wallet user identity certificate is issued using the third private key, and the hard wallet user identity certificate is returned to the hard wallet.
[0014] In addition, according to another aspect of an embodiment of the present invention, an identity authentication method in an offline transaction scenario is provided, which is applied to a hard wallet terminal identity certificate issuing agency, including:
[0015] Generate a fourth public-private key pair, and submit the fourth public key to the blockchain identity management system;
[0016] Receiving the identity identifier of the hard wallet terminal identity certificate issuing agency returned by the blockchain identity management system;
[0017] Receive a hard wallet terminal identity credential issuance request sent by the hard wallet;
[0018] The fourth private key is used to issue a hard wallet terminal identity certificate, and the hard wallet terminal identity certificate is returned to the hard wallet.
[0019] In addition, according to another aspect of an embodiment of the present invention, an identity authentication method in an offline transaction scenario is provided, which is applied to a blockchain identity management system, including:
[0020] Receive a first public key of a hard wallet user and a second public key of a hard wallet terminal submitted by the hard wallet;
[0021] Generate a hard wallet user identity and its identity document, a hard wallet terminal identity and its identity document, and return the hard wallet user identity and the hard wallet terminal identity to the hard wallet;
[0022] Respectively receive the third public key submitted by the hard wallet user identity certificate issuing agency and the fourth public key submitted by the hard wallet terminal identity certificate issuing agency;
[0023] Generate a hard wallet user identity certificate issuing agency identity identifier and its identity document, a hard wallet terminal identity certificate issuing agency identity identifier and its identity document respectively, and return the hard wallet user identity certificate issuing agency identity identifier and the hard wallet terminal identity certificate issuing agency identity identifier to the hard wallet user identity certificate issuing agency and the hard wallet terminal identity certificate issuing agency respectively;
[0024] The identity document is used to store the binding relationship between the identity identifier and its public key.
[0025] In addition, according to another aspect of an embodiment of the present invention, an identity authentication device in an offline transaction scenario is provided, which is configured to be applied to a hard wallet, and includes:
[0026] A wallet public key module, used to generate a first public-private key pair of a hard wallet user and a second public-private key pair of a hard wallet terminal in a security chip;
[0027] A wallet identification module, used to submit the first public key of the hard wallet user and the second public key of the hard wallet terminal to the blockchain identity management system, and receive the hard wallet user identity and the hard wallet terminal identity returned by the blockchain identity management system;
[0028] A wallet identity module, used to send identity certificate issuance requests to a hard wallet user identity certificate issuing agency and a hard wallet terminal identity certificate issuing agency respectively, and receive a hard wallet user identity certificate issued by the hard wallet user identity certificate issuing agency and a hard wallet terminal identity certificate issued by the hard wallet terminal identity certificate issuing agency;
[0029] The authentication module is used to perform identity authentication based on the hard wallet user identity certificate and the hard wallet terminal identity in an offline transaction scenario.
[0030] In addition, according to another aspect of an embodiment of the present invention, an identity authentication device in an offline transaction scenario is provided, which is arranged in a hard wallet user identity certificate issuing institution, and includes:
[0031] The first generation module is used to generate a third public-private key pair, submit the third public key to the blockchain identity management system, and receive the identity identifier of the hard wallet user identity certificate issuing agency returned by the blockchain identity management system;
[0032] The first issuing module is used to receive a hard wallet user identity certificate issuance request sent by the hard wallet, use the third private key to issue the hard wallet user identity certificate, and return the hard wallet user identity certificate to the hard wallet.
[0033] In addition, according to another aspect of an embodiment of the present invention, an identity authentication device in an offline transaction scenario is provided, which is arranged in an identity certificate issuing institution of a hard wallet terminal, and includes:
[0034] A second generation module is used to generate a fourth public-private key pair, submit the fourth public key to the blockchain identity management system, and receive the identity identifier of the hard wallet terminal identity certificate issuing agency returned by the blockchain identity management system;
[0035] The second issuing module is used to receive a hard wallet terminal identity certificate issuance request sent by the hard wallet, use the fourth private key to issue the hard wallet terminal identity certificate, and return the hard wallet terminal identity certificate to the hard wallet.
[0036] In addition, according to another aspect of an embodiment of the present invention, an identity authentication device in an offline transaction scenario is provided, which is arranged in a blockchain identity management system, including:
[0037] A third generating module is used to receive the first public key of the hard wallet user and the second public key of the hard wallet terminal submitted by the hard wallet, generate the hard wallet user identity and its identity document, the hard wallet terminal identity and its identity document, and return the hard wallet user identity and the hard wallet terminal identity to the hard wallet;
[0038] The fourth generation module is used to receive the third public key submitted by the hard wallet user identity credential issuing agency and the fourth public key submitted by the hard wallet terminal identity credential issuing agency, respectively, generate the hard wallet user identity credential issuing agency identity identifier and its identity document, the hard wallet terminal identity credential issuing agency identity identifier and its identity document, and return the hard wallet user identity credential issuing agency identity identifier and the hard wallet terminal identity credential issuing agency identity identifier to the hard wallet user identity credential issuing agency and the hard wallet terminal identity credential issuing agency, respectively; wherein the identity document is used to store the binding relationship between the identity identifier and its public key.
[0039] According to another aspect of an embodiment of the present invention, there is further provided an electronic device, including:
[0040] one or more processors;
[0041] a storage device for storing one or more programs,
[0042] When the one or more programs are executed by the one or more processors, the one or more processors implement the method described in any one of the above embodiments.
[0043] According to another aspect of an embodiment of the present invention, a computer-readable medium is provided, on which a computer program is stored. When the program is executed by a processor, the method described in any one of the above embodiments is implemented.
[0044] According to another aspect of an embodiment of the present invention, a computer program product is provided, including a computer program, and when the computer program is executed by a processor, the method described in any one of the above embodiments is implemented.
[0045] One embodiment of the above invention has the following advantages or beneficial effects: because the technical means of identity authentication based on the hard wallet user identity certificate and the hard wallet terminal identity certificate in the offline transaction scenario is adopted by sending identity certificate issuance requests to the hard wallet user identity certificate issuing agency and the hard wallet terminal identity certificate issuing agency respectively, and receiving the hard wallet user identity certificate issued by the hard wallet user identity certificate issuing agency and the hard wallet terminal identity certificate issued by the hard wallet terminal identity certificate issuing agency, the technical problem of transaction risks in the prior art is overcome. In the offline payment mode of the hard wallet, the embodiment of the present invention introduces terminal authentication and application (user) authentication before the transaction payment, and enhances the security and reliability of the subsequent hard wallet offline payment process through multi-modal authentication guarantee. In addition, the embodiment of the present invention introduces blockchain technology to enhance trusted authentication and ensure that the authentication relationship cannot be tampered with; and the process of authentication behavior can be stored and proved, so that the authentication behavior can be traced.
[0046] The further effects of the above-mentioned non-conventional optional manner will be described below in conjunction with specific implementation examples. BRIEF DESCRIPTION OF THE DRAWINGS
[0047] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the prior art descriptions. 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 creative work. Among them:
[0048] Figure 1 is a schematic diagram of the main process of an identity authentication method in an offline transaction scenario according to an embodiment of the present invention;
[0049] Figure 2 is a schematic diagram of the system architecture of an identity authentication method in an offline transaction scenario according to an embodiment of the present invention;
[0050] Figure 3 It is a schematic diagram of the main process of an identity authentication method in an offline transaction scenario according to a reference embodiment of the present invention;
[0051] Figure 4 is a schematic diagram of the main process of an identity authentication method in an offline transaction scenario according to another embodiment of the present invention;
[0052] Figure 5 is a schematic diagram of the main process of an identity authentication method in an offline transaction scenario according to yet another embodiment of the present invention;
[0053] Figure 6is a schematic diagram of the main process of an identity authentication method in an offline transaction scenario according to yet another embodiment of the present invention;
[0054] Figure 7 is a schematic diagram of the main process of an identity authentication method in an offline transaction scenario according to another reference embodiment of the present invention;
[0055] Figure 8 is a schematic diagram of main modules of an identity authentication device in an offline transaction scenario according to an embodiment of the present invention;
[0056] Fig. 9 is a schematic diagram of main modules of an identity authentication device in an offline transaction scenario according to another embodiment of the present invention;
[0057] Fig.10 is a schematic diagram of main modules of an identity authentication device in an offline transaction scenario according to yet another embodiment of the present invention;
[0058] Fig.11 is a schematic diagram of main modules of an identity authentication device in an offline transaction scenario according to yet another embodiment of the present invention;
[0059] Fig.12 is an exemplary system architecture diagram to which embodiments of the present invention may be applied;
[0060] Fig.13 It is a schematic diagram of the structure of a computer system of a terminal device or a server suitable for implementing an embodiment of the present invention. DETAILED DESCRIPTION
[0061] The following is a description of exemplary embodiments of the present invention in conjunction with the accompanying drawings, including various details of the embodiments of the present invention to facilitate understanding, which should be considered as merely exemplary. Therefore, it should be recognized by those of ordinary skill in the art that various changes and modifications may be made to the embodiments described herein without departing from the scope and spirit of the present invention. Similarly, for clarity and conciseness, the description of well-known functions and structures is omitted in the following description.
[0062] Security and privacy protection are the key to the offline payment function of digital terminals, and the premise of conducting secure transactions is that the counterparty should first be a secure and reliable hard wallet terminal and hard wallet application. Therefore, it is necessary to ensure the security of offline point-to-point transactions of hard wallets from multiple dimensions and levels, especially the security authentication of terminal devices and applications.
[0063] In the embodiments of the present invention, the roles and systems involved include: hard wallet applications (embedded applications, that is, hard wallet users, installed in hard wallet terminals), hard wallet terminals (IoT devices such as mobile phones with security chips), identity certificate issuing agencies (for example, for mobile phone terminals, the terminal manufacturer is its identity certificate issuing agency) and blockchain identity management system. Hard wallet terminals are the carriers of hard wallet transactions, and are generally related devices with security chips, such as mobile phones or other IoT devices. Hard wallet users hold hard wallet terminals, open hard wallet accounts based on hard wallet applications installed on the terminals, and can conduct offline transactions with other hard wallet users. Identity certificate issuing agencies include hard wallet terminal identity certificate issuing agencies and hard wallet application identity certificate issuing agencies. Hard wallet terminal identity certificate issuing agencies are generally the production agencies or operating agencies of hard wallet terminals, such as mobile terminal manufacturers, IoT device manufacturers, etc. Hard wallet user identity certificate issuing agencies generally refer to agencies that issue certain identity certification attributes to users, such as agencies that issue ID cards, car driver's licenses, academic certificates, etc. Blockchain identity management system: mainly issues identity identification for each role, creates and updates identity documents, etc.
[0064] In the embodiment of the present invention, before two hard wallets conduct offline transactions, the hard wallet terminal device is first authenticated, and then the hard wallet application is authenticated, thereby enhancing the security and reliability of the subsequent hard wallet offline payment process through double trusted authentication.
[0065] For ease of understanding, in the embodiments of the present invention, the following related parameters are defined:
[0066] HWID: It is an identity issued by the blockchain management system. HWID_Device_d1 and HWID_Device_d2 represent the identity of the hard wallet terminal d1 and d2; HWID_User_a1 and HWID_User_a2 represent the identity of the hard wallet user a1 and a2; HWID_DeviceIssuer_D1 and HWID_DeviceIssuer_D2 represent the identity of the hard wallet terminal identity certificate issuing agency D1 and D2, HWID_UserIssuer_A1 and HWID_UserIssuer _A2 represents the identity identifiers A1 and A2 of the hard wallet user identity credential issuing agency; wherein, the hard wallet terminal of the hard wallet user a1 is d1, the hard wallet terminal identity credential issuing agency D1 issues an identity credential for the hard wallet terminal d1, and the hard wallet user identity credential issuing agency A1 issues an identity credential for the hard wallet user a1; wherein, the hard wallet terminal of the hard wallet user a2 is d2, the hard wallet terminal identity credential issuing agency D2 issues an identity credential for the hard wallet terminal d2, and the hard wallet user identity credential issuing agency A2 issues an identity credential for the hard wallet user a2.
[0067] Pk_Device and Sk_Device: refer to the public and private keys of the hard wallet terminal, which are generated in the security chip of the hard wallet terminal. Pk_Device_d1 / Sk_Device_d1, Pk_Device_d2 / Sk_Device_d2 represent the public and private key pairs of the hard wallet terminals d1 and d2 respectively.
[0068] Pk_user / Sk_user: refers to the public and private keys of the hard wallet user, which are generated in the security chip of the hard wallet terminal. Pk_user_a1 / Sk_user_a1, Pk_user_a2 / Sk_user_a2 represent the public and private key pairs of hard wallet users a1 and a2 respectively.
[0069] Pk_UserIssuer / Sk_UserIssuer, Pk_DeviceIssuer / Sk_DeviceIssuer: The public and private keys of the hard wallet user identity certificate issuing authority and the hard wallet terminal identity certificate issuing authority, respectively. Pk_UserIssuer_A1 / Sk_UserIssuer_A1, Pk_UserIssuer_A2 / Sk_UserIssuer_A2 represent the public and private key pairs of the hard wallet user identity certificate issuing authorities A1 and A2, respectively. Pk_DeviceIssuer_D1 / Sk_DeviceIssuer_D1, Pk_DeviceIssuer_D2 / Sk_DeviceIssuer_D2 represent the public and private key pairs of the hard wallet terminal identity certificate issuing authorities D1 and D2, respectively.
[0070] HWID-DOC (identity document): exists in the blockchain identity management system. Each HWID-DOC is a table in the Key-Value database. The corresponding HWID-DOC can be found through the HWID. When hard wallet users, hard wallet terminals, and identity certificate issuing agencies apply for HWID, the blockchain identity management system will write the corresponding binding relationship between their HWID and their public key in the identity document, such as the corresponding relationship between Pk_user_a1 and HWID_User_a1, the corresponding relationship between Pk_Device_d1 and HWID_Device_D1, etc. HWID-DOC is synchronized with the blockchain account book to ensure that it cannot be tampered with.
[0071] HWID-DOC update: When the hard wallet terminal and the hard wallet user add new identity credentials, the blockchain identity management system will update the user's HWID-DOC identity document. For example, if the identity credential issuing agency issues a new identity credential Credential to the hard wallet user a1, HWID-DOC will add the credential identifier, the verification relationship between the credential identifier and the public key of the identity credential issuing agency, etc. After the HWID-DOC identity document is updated, it is synchronized with the blockchain account book to ensure that it cannot be tampered with.
[0072] Credential: refers to an identity credential issued by an identity credential issuing agency. For example, when a hard wallet user A submits relevant information to an agency that grants him a certain identity attribute (physical certificate), and conducts relevant verification (password / face / ID card verification, etc.), the identity credential issuing agency generates an electronic credential and performs an electronic signature to indicate that the user has these identity attributes.
[0073] Blockchain identity management system: A blockchain platform that is responsible for issuing trusted identities to various roles, creating and maintaining their identity documents. Identity credential issuing agencies, hard wallets, etc. interact securely with the blockchain identity management system through secure channels.
[0074] SEID: The unique identifier of the security chip SE, which includes fields such as chip manufacturer, chip type, card business, and OS release date.
[0075] Figure 1 Schematic diagram of the main process of the identity authentication method in an offline transaction scenario according to an embodiment of the present invention. Figure 1 As shown, the identity authentication method in the offline transaction scenario is applied to a hard wallet and may include:
[0076] Step 101, generating a first public-private key pair of the hard wallet user and a second public-private key pair of the hard wallet terminal in the security chip respectively.
[0077] In the initialization phase (online phase), the hard wallet user and the hard wallet terminal generate their own public-private key pairs, namely the first public-private key pair of the hard wallet user and the second public-private key pair of the hard wallet terminal.
[0078] In this step, the hard wallet terminal and the hard wallet user are initialized, and the hard wallet and the hard wallet user generate public-private key pairs respectively, wherein: the hard wallet terminal d1 (d1 is a device manufactured by the terminal manufacturer D1) and the hard wallet terminal d2 (d2 is a device manufactured by the terminal manufacturer D2) generate public-private key pairs Pk_Device_d1 / Sk_Device_d1, Pk_Device_d2 / Sk_Device_d2 in the hard wallet security chip respectively; the hard wallet user a1 (holding the hard wallet terminal d1) and the hard wallet user a2 (holding the hard wallet terminal d2) generate public-private key pairs Pk_user_a1 / Sk_user_a1, Pk_user_a2 / Sk_user_a2 in the hard wallet security chip respectively.
[0079] It should be noted that the hard wallet can also submit the security chip identification SEID to the blockchain identity management system.
[0080] Step 102: submit the first public key of the hard wallet user and the second public key of the hard wallet terminal to the blockchain identity management system, and receive the hard wallet user identity and hard wallet terminal identity returned by the blockchain identity management system.
[0081] like Figure 2 As shown, after the public-private key pair is generated, the hard wallet submits the first public key of the hard wallet user and the second public key of the hard wallet terminal to the blockchain identity management system in a secure manner. After successful submission, the hard wallet user identity and hard wallet terminal identity returned by the blockchain identity management system will be received.
[0082] In this step, the hard wallet terminal and the hard wallet user each submit the public keys: Pk_Device_d1, Pk_Device_d2, Pk_user_a1, Pk_user_a2 to the blockchain identity management system, and the blockchain identity management system generates the identity identifiers HWID_Device_d1, HWID_Device_d2, HWID_User_a1, HWID_User_a2, HWID for each of the above roles, and returns the identity identifiers to each role respectively.
[0083] Step 103, sending identity credential issuance requests to the hard wallet user identity credential issuing agency and the hard wallet terminal identity credential issuing agency respectively, and receiving the hard wallet user identity credential issued by the hard wallet user identity credential issuing agency and the hard wallet terminal identity credential issued by the hard wallet terminal identity credential issuing agency.
[0084] like Figure 2As shown, the hard wallet terminal verifies its identity with its identity certificate issuing agency (usually mobile terminal and IoT device manufacturers). After the verification is passed, the identity certificate issuing agency of the hard wallet terminal generates a certificate that can verify its identity and signs it. The signed identity certificate is sent to the hard wallet terminal and stored in the security chip. The hard wallet user applies for different identity certificate certificates (such as driver's license, etc.) from his identity certificate issuing agency. The hard wallet user identity certificate issuing agency generates a certificate that can verify its identity and signs it. The signed identity certificate is sent to the hard wallet user and stored in the security chip of the hard wallet terminal.
[0085] Optionally, the hard wallet terminals d1 and d2 apply for their own trusted identity credentials from the hard wallet terminal identity credential issuing agencies D1 and D2 (generally terminal manufacturers) through the GP standard secure communication and authentication protocol SCP03 (a remote communication authentication protocol between security chips and security chip terminal manufacturers formulated by the international organization GP). The hard wallet terminal identity credential issuing agencies D1 and D2 first verify through the SCP02 protocol that the hard wallet terminals d1 and d2 are the devices they produce. Then, the hard wallet terminal identity credential issuing agencies (terminal manufacturers) D1 and D2 generate the identity credentials Credential_DeviceIssuer_d1 and Credential_DeviceIssuer_d2 of the hard wallet terminals based on the verifiable identity credential template, and use their private keys Sk_DeviceIssuer_D1 and Sk_DeviceIssuer_D2 to sign, indicating that the hard wallet terminal devices have been authenticated and verified by the terminal manufacturer. Finally, the hard wallet terminal identity certificate issuing agencies D1 and D2 (terminal manufacturers) send the identity certificates to the hard wallet terminals d1 and d2, and the hard wallet terminals d1 and d2 store the identity certificates in their respective security chips.
[0086] Optionally, hard wallet user a1 brings the identity identifier HWID_User_a1 and the SEID of the corresponding hard wallet terminal, and applies for identity verification to the hard wallet user identity credential issuing agency A1 corresponding to a certain identity attribute of the hard wallet user. After the verification is passed, the verifiable identity credential Credential_UserIssuer_a1 issued by agency A1 is obtained; hard wallet user a2 brings the identity identifier HWID_User_a2 and the SEID of the corresponding hard wallet terminal, and applies for identity verification to the hard wallet user identity credential issuing agency A2 corresponding to a certain identity attribute of the hard wallet user. After the verification is passed, the verifiable identity credential Credential_UserIssuer_a2 issued by agency A2 is obtained.
[0087] Step 104: in an offline transaction scenario, identity authentication is performed based on the hard wallet user identity credential and the hard wallet terminal identity identifier.
[0088] In the offline transaction scenario, two hard wallet terminals interact with each other through short-distance communication methods such as Bluetooth and NFC. Before the two hard wallet terminals conduct transactions, the payee and payee exchange the hard wallet terminal identity credentials and the hard wallet user identity credentials respectively, and verify the two identity credentials separately. After the dual identity authentication is passed, the log information is saved in the hard wallet security chip, and the two hard wallet users enter the next offline transaction operation.
[0089] According to the various embodiments described above, it can be seen that the embodiment of the present invention respectively sends an identity credential issuance request to the hard wallet user identity credential issuing agency and the hard wallet terminal identity credential issuing agency, receives the hard wallet user identity credential issued by the hard wallet user identity credential issuing agency and the hard wallet terminal identity credential issued by the hard wallet terminal identity credential issuing agency, and thus solves the technical problem of transaction risks in the prior art by using the technical means of identity authentication based on the hard wallet user identity credential and the hard wallet terminal identity identifier in the offline transaction scenario. In the offline payment mode of the hard wallet, the embodiment of the present invention introduces terminal authentication and application (user) authentication before making transaction payments, and enhances the security and reliability of the subsequent hard wallet offline payment process through multimodal authentication guarantees. Moreover, the embodiment of the present invention introduces blockchain technology to enhance trusted authentication and ensure that the authentication relationship cannot be tampered with; and the process of authentication behavior can be stored and proved, so that the authentication behavior can be traced.
[0090] Figure 3 is a schematic diagram of the main process of an identity authentication method in an offline transaction scenario according to a reference embodiment of the present invention. As another embodiment of the present invention, Figure 3 As shown, the identity authentication method in the offline transaction scenario is applied to a hard wallet and may include:
[0091] Step 301, generating a first public-private key pair of the hard wallet user and a second public-private key pair of the hard wallet terminal in the security chip respectively.
[0092] Step 302: Submit the first public key of the hard wallet user and the second public key of the hard wallet terminal to the blockchain identity management system, and receive the hard wallet user identity and hard wallet terminal identity returned by the blockchain identity management system.
[0093] Step 303, sending identity credential issuance requests to the hard wallet user identity credential issuing agency and the hard wallet terminal identity credential issuing agency respectively, and receiving the hard wallet user identity credential issued by the hard wallet user identity credential issuing agency and the hard wallet terminal identity credential issued by the hard wallet terminal identity credential issuing agency.
[0094] Step 304: Receive the third public key and the fourth public key issued by the blockchain identity management system.
[0095] Among them, the third public key is generated by the hard wallet user identity certificate issuing agency and submitted to the blockchain identity management system; the fourth public key is generated by the hard wallet terminal identity certificate issuing agency and submitted to the blockchain identity management system.
[0096] In order to verify identity credentials in offline transaction scenarios, the blockchain identity management system sends the public keys Pk_DeviceIssuer_D1, Pk_DeviceIssuer_D2, Pk_UserIssuer_A1, and Pk_UserIssuer_A2 of the identity credential issuing agencies D1, D2, A1, and A2 and presets them on all hard wallet terminals. The hard wallet terminals can save the public keys in the hard wallet application or in the security chip.
[0097] Step 305: In an offline transaction scenario, identity authentication is performed based on the hard wallet user identity credential and the hard wallet terminal identity identifier.
[0098] In an offline transaction scenario, two hard wallet terminals interact with each other through short-distance communication methods such as Bluetooth and NFC. Before the two hard wallet terminals conduct a transaction, the payee and payee exchange the hard wallet terminal identity certificate and the hard wallet user identity certificate respectively, and verify the two identity certificates respectively.
[0099] Optionally, if the hard wallet is the payee, identity authentication is performed based on the hard wallet user identity certificate and the hard wallet terminal identity identifier, including: sending an identity authentication request to the payee's hard wallet; receiving the hard wallet user identity certificate and the hard wallet terminal identity identifier returned by the payee's hard wallet; performing identity authentication on the hard wallet user identity certificate and the hard wallet terminal identity identifier returned by the payee's hard wallet based on the third public key and the fourth public key respectively; returning the authentication result to the payee's hard wallet; receiving the identity authentication request sent by the payee's hard wallet; returning the hard wallet user identity certificate and the hard wallet terminal identity identifier to the payee's hard wallet; receiving the authentication result returned by the payee's hard wallet.
[0100] Before two hard wallets conduct offline peer-to-peer transactions through wireless communication technologies such as NFC / Bluetooth (assuming that hard wallet user a1 pays hard wallet user a2), both parties first conduct trusted authentication of the terminal and the application, which can include the following steps:
[0101] Step 1: Hard wallet user a1 initiates an identity authentication request to a2, and a2 sends its user identity credential Credential_UserIssuer_a2 and the identity credential Credential_DeviceIssuer_d2 of the hard wallet terminal d2 to a1.
[0102] Step 2: The hard wallet application calls the public key Pk_DeviceIssuer_D2 preset on the hard wallet terminal to verify the signature of the terminal identity credential Credential_DeviceIssuer_d2; if the verification fails, the transaction is terminated, and the user a1 is prompted that the other party may be an untrusted terminal; after the verification is passed, the public key Pk_UserIssuer_A2 preset on the hard wallet terminal is called to verify the user identity credential Credential_UserIssuer_a2. If the verification fails, the transaction is terminated, and the user a1 is prompted that the other party may be an untrusted hard wallet application; the hard wallet terminal d1 locally saves the above operation logs.
[0103] Step 3: After the hard wallet user a1 successfully verifies the identity credentials of the payee's hard wallet terminal d2 and application a2, the hard wallet user a2 initiates an authentication request to a1.
[0104] Step 4: The hard wallet user a1 sends its user identity credential Credential_UserIssuer_a1 and the terminal identity credential Credential_DeviceIssuer_d1 of the hard wallet terminal d1 held to a2.
[0105] Step 5: The hard wallet application calls the public key Pk_DeviceIssuer_D1 preset on the hard wallet terminal to verify the signature of the terminal identity credential Credential_DeviceIssuer_d1; if the verification fails, the transaction is terminated, and the user a2 is prompted that the other party may be an untrusted terminal; after the verification is passed, the public key Pk_UserIssuer_A1 preset on the hard wallet terminal is called to verify the user identity credential Credential_UserIssuer_a1. If the verification fails, the transaction is terminated, and the user a2 is prompted that the other party may be an untrusted hard wallet application; the hard wallet terminal d2 saves the above operation logs locally.
[0106] Step 6: After a1 / a2 and d1 / d2 have verified their identity credentials, they can proceed to the subsequent transaction payment process.
[0107] Optionally, if the hard wallet is the payee, identity authentication is performed based on the hard wallet user identity certificate and the hard wallet terminal identity identifier, including: receiving an identity authentication request sent by the payer's hard wallet; returning the hard wallet user identity certificate and the hard wallet terminal identity identifier to the payer's hard wallet; receiving the authentication result returned by the payer's hard wallet; sending an identity authentication request to the payer's hard wallet; receiving the hard wallet user identity certificate and the hard wallet terminal identity identifier returned by the payer's hard wallet; performing identity authentication on the hard wallet user identity certificate and the hard wallet terminal identity identifier returned by the payer's hard wallet based on the third public key and the fourth public key respectively; returning the authentication result to the payer's hard wallet. Similar to the above process, it will not be repeated here.
[0108] Step 306: When the network connection is restored, the operation log of the identity authentication process is reported to the blockchain identity management system.
[0109] When the network is restored, the hard wallet terminals d1 and d2 will upload the operation logs to the blockchain identity management system, which can be used as a reference for subsequent security audits and risk tracing.
[0110] In addition, the specific implementation content of the identity authentication method in an offline transaction scenario in a reference embodiment of the present invention has been described in detail in the identity authentication method in the offline transaction scenario described above, so the repeated content will not be described here.
[0111] Figure 4 is a schematic diagram of the main process of an identity authentication method in an offline transaction scenario according to another embodiment of the present invention. As another embodiment of the present invention, Figure 4 As shown, the identity authentication method in the offline transaction scenario is applied to the hard wallet user identity certificate issuing agency, which may include:
[0112] Step 401, generate a third public-private key pair and submit the third public key to the blockchain identity management system.
[0113] like Figure 2 As shown, the hard wallet user identity certificate issuing agencies A1 and A2 generate public-private key pairs Pk_UserIssuer_A1 / Sk_UserIssuer_A1 and Pk_UserIssuer_A2 / Sk_UserIssuer_A2 in the secure server environment respectively, and then submit their respective public keys Pk_UserIssuer_A1 and Pk_UserIssuer_A2 to the blockchain identity management system.
[0114] Step 402: Receive the identity identifier of the hard wallet user identity certificate issuing agency returned by the blockchain identity management system.
[0115] The blockchain identity management system generates the identity identifiers HWID_UserIssuer_A1 and HWID_UserIssuer_A2 of the above institutions, and returns the identity identifiers to each institution respectively.
[0116] Step 403: Receive a hard wallet user identity credential issuance request sent by the hard wallet.
[0117] Step 404: Use the third private key to issue the hard wallet user identity certificate, and return the hard wallet user identity certificate to the hard wallet.
[0118] like Figure 2 As shown, the hard wallet user applies for different identity credentials (such as a driver's license, etc.) from his identity credential issuing agency. The hard wallet user's identity credential issuing agency generates a certificate that can verify the identity and signs it. The signed identity credential is issued to the hard wallet user and stored in the security chip of the hard wallet terminal.
[0119] Optionally, hard wallet user a1 brings the identity identifier HWID_User_a1 and the SEID of the corresponding hard wallet terminal, and applies for identity verification to the hard wallet user identity credential issuing agency A1 corresponding to a certain identity attribute of the hard wallet user. After the verification is passed, the verifiable identity credential Credential_UserIssuer_a1 issued by agency A1 is obtained; hard wallet user a2 brings the identity identifier HWID_User_a2 and the SEID of the corresponding hard wallet terminal, and applies for identity verification to the hard wallet user identity credential issuing agency A2 corresponding to a certain identity attribute of the hard wallet user. After the verification is passed, the verifiable identity credential Credential_UserIssuer_a2 issued by agency A2 is obtained.
[0120] Optionally, after step 404, the method further includes: submitting the hard wallet user identity certificate to the blockchain identity management system. After receiving the hard wallet user identity certificate, the blockchain identity management system stores the identity certificate and updates the hard wallet user identity certificate identifier to the corresponding identity document.
[0121] In addition, the specific implementation content of the identity authentication method in an offline transaction scenario in another embodiment of the present invention has been described in detail in the identity authentication method in the offline transaction scenario described above, so the repeated content will not be described here.
[0122] Figure 5 FIG. 1 is a schematic diagram of the main process of an identity authentication method in an offline transaction scenario according to another embodiment of the present invention. As another embodiment of the present invention, Figure 5 As shown, the identity authentication method in the offline transaction scenario is applied to the hard wallet terminal identity certificate issuing agency, which may include:
[0123] Step 501, generate a fourth public-private key pair, and submit the fourth public key to the blockchain identity management system.
[0124] like Figure 2 As shown, the hard wallet terminal identity certificate issuing agencies D1 and D2 generate public and private key pairs Pk_DeviceIssuer_D1 / SK_DeviceIssuer_D1 and Pk_DeviceIssuer_D2 / SK_DeviceIssuer_D2 in the secure server environment respectively, and then submit their respective public keys Pk_DeviceIssuer_D1 and Pk_DeviceIssuer_D2 to the blockchain identity management system.
[0125] Step 502: Receive the identity identifier of the hard wallet terminal identity certificate issuing agency returned by the blockchain identity management system.
[0126] The blockchain identity management system generates the identity identifiers HWID_DeviceIssuer_D1 and HWID_DeviceIssuer_D2 of the above institutions, and returns the identity identifiers to each institution respectively.
[0127] Step 503: Receive a hard wallet terminal identity certificate issuance request sent by the hard wallet.
[0128] Step 504: Use the fourth private key to issue a hard wallet terminal identity certificate, and return the hard wallet terminal identity certificate to the hard wallet.
[0129] like Figure 2 As shown, the hard wallet terminal verifies its identity with its identity certificate issuing agency (usually mobile terminal and IoT device manufacturers). After the verification is passed, the identity certificate issuing agency of the hard wallet terminal generates a certificate that can verify its identity and signs it. The signed identity certificate is sent to the hard wallet terminal and stored in the security chip.
[0130] Optionally, the hard wallet terminals d1 and d2 apply for their own trusted identity credentials from the hard wallet terminal identity credential issuing agencies D1 and D2 (generally terminal manufacturers) through the GP standard secure communication and authentication protocol SCP03 (a remote communication authentication protocol between security chips and security chip terminal manufacturers formulated by the international organization GP). The hard wallet terminal identity credential issuing agencies D1 and D2 first verify through the SCP02 protocol that the hard wallet terminals d1 and d2 are the devices they produce. Then, the hard wallet terminal identity credential issuing agencies (terminal manufacturers) D1 and D2 generate the identity credentials Credential_DeviceIssuer_d1 and Credential_DeviceIssuer_d2 of the hard wallet terminals based on the verifiable identity credential template, and use their private keys Sk_DeviceIssuer_D1 and Sk_DeviceIssuer_D2 to sign, indicating that the hard wallet terminal devices have been authenticated and verified by the terminal manufacturer. Finally, the hard wallet terminal identity certificate issuing agencies D1 and D2 (terminal manufacturers) send the identity certificates to the hard wallet terminals d1 and d2, and the hard wallet terminals d1 and d2 store the identity certificates in their respective security chips.
[0131] Optionally, after step 504, the method further includes: submitting the hard wallet terminal identity certificate to the blockchain identity management system. After receiving the hard wallet terminal identity certificate, the blockchain identity management system stores the identity certificate and updates the hard wallet terminal identity certificate identifier to the corresponding identity document.
[0132] In addition, the specific implementation content of the identity authentication method in an offline transaction scenario in another embodiment of the present invention has been described in detail in the identity authentication method in the offline transaction scenario described above, so the repeated content will not be described here.
[0133] Figure 6 is a schematic diagram of the main process of an identity authentication method in an offline transaction scenario according to another embodiment of the present invention. As another embodiment of the present invention, Figure 6 As shown, the identity authentication method in the offline transaction scenario is applied to the blockchain identity management system and may include:
[0134] Step 601, receiving a first public key of a hard wallet user and a second public key of a hard wallet terminal submitted by the hard wallet.
[0135] Step 602, generating a hard wallet user identity and its identity document, a hard wallet terminal identity and its identity document, and returning the hard wallet user identity and the hard wallet terminal identity to the hard wallet; wherein the identity document is used to store the binding relationship between the identity and its public key.
[0136] Step 603, receiving the third public key submitted by the hard wallet user identity certificate issuing agency and the fourth public key submitted by the hard wallet terminal identity certificate issuing agency respectively;
[0137] Step 604, respectively generate the identity identifier of the hard wallet user identity credential issuing agency and its identity document, the identity identifier of the hard wallet terminal identity credential issuing agency and its identity document, and return the identity identifier of the hard wallet user identity credential issuing agency and the identity identifier of the hard wallet terminal identity credential issuing agency to the hard wallet user identity credential issuing agency and the hard wallet terminal identity credential issuing agency, respectively; wherein the identity document is used to store the binding relationship between the identity identifier and its public key.
[0138] As mentioned above, each role and each organization submits their public keys Pk_Device_d1, Pk_Device_d2, Pk_user_a1, Pk_user_a2, Pk_DeviceIssuer_D1, Pk_DeviceIssuer_D2, Pk_UserIssuer_A1, Pk_UserIssuer_A2 to the blockchain identity management system. After receiving the public keys of each role and each organization, the blockchain identity management system generates identity identifiers HWID_Device_d1, HWID_Device_d2, HWID_User_a1, HWID_User_a2, HWID_DeviceIssuer_D1, HWID_DeviceIssuer_D2, HWID_UserIssuer_A1, HWID_UserIssuer_A2 for them respectively.
[0139] At the same time, the blockchain identity management system generates identity documents for the hard wallet terminal, hard wallet user, and identity credential issuing agency, HWID-DOC_User_a1, HWID-DOC_User_a2, HWID-DOC_Device_d1, HWID-DOC_Device_d2, HWID-DOC_UserIssuer_A1, HWID-DOC_UserIssuer_A2, HWID-DOC_DeviceIssuer_D1, and HWID-DOC_DeviceIssuer_D2.
[0140] Among them, the identity document is a key-value pair database table, and each identity document records the binding relationship between each identity identifier and its public key and other attributes, including: the binding relationship between the identity identifier of the hardware wallet terminal d1 / d2 and its public key, the binding relationship between the identity identifier of the hardware wallet terminal d1 / d2 and the SEID; the binding relationship between the identity identifier of the hardware wallet user a1 / a2 and its public key; the binding relationship between the identity identifier of the hardware wallet terminal identity certificate issuing agency D1 / D2 and its public key; the binding relationship between the identity identifier of the hardware wallet user identity certificate issuing agency A1 / A2 and its public key.
[0141] Next, the blockchain identity management system issues respective identity tags to the hard wallet terminal, hard wallet user, and identity certificate issuing agency; at the same time, their respective identity documents are automatically synchronized through the blockchain to ensure that they cannot be tampered with.
[0142] It should be noted that the embodiment of the present invention only exemplarily illustrates the order of each step, but there is no limitation on the execution order of step 601 and step 603.
[0143] In addition, the specific implementation content of the identity authentication method in an offline transaction scenario in another embodiment of the present invention has been described in detail in the identity authentication method in the offline transaction scenario described above, so the repeated content will not be described here.
[0144] Figure 7 Schematic diagram of the main process of the identity authentication method in an offline transaction scenario according to another reference embodiment of the present invention. Figure 7 As shown, the identity authentication method in the offline transaction scenario is applied to the blockchain identity management system and may include:
[0145] Step 701, receiving a first public key of a hard wallet user and a second public key of a hard wallet terminal submitted by the hard wallet.
[0146] Step 702, generating a hard wallet user identity and its identity document, a hard wallet terminal identity and its identity document, and returning the hard wallet user identity and the hard wallet terminal identity to the hard wallet.
[0147] Step 703, respectively receiving the third public key submitted by the hard wallet user identity certificate issuing agency and the fourth public key submitted by the hard wallet terminal identity certificate issuing agency.
[0148] Step 704, respectively generate the identity identifier of the hard wallet user identity credential issuing agency and its identity document, and the identity identifier of the hard wallet terminal identity credential issuing agency and its identity document, and return the identity identifier of the hard wallet user identity credential issuing agency and the identity identifier of the hard wallet terminal identity credential issuing agency to the hard wallet user identity credential issuing agency and the hard wallet terminal identity credential issuing agency, respectively.
[0149] Step 705: Receive the hard wallet user identity certificate submitted by the hard wallet user identity certificate issuing agency.
[0150] Step 706: store the hard wallet user identity credential, and write the binding relationship between the hard wallet user identity credential identifier and the third public key into the hard wallet user identity document.
[0151] Step 707: Receive the hard wallet terminal identity certificate submitted by the hard wallet terminal identity certificate issuing agency.
[0152] Step 708: store the hard wallet terminal identity credential, and write the binding relationship between the hard wallet terminal identity credential identifier and the fourth public key into the hard wallet user identity document.
[0153] Step 709: Send the third public key and the fourth public key to the hard wallet.
[0154] The hard wallet user applies for different identity credentials (such as driver's license, etc.) from his identity credential issuing agency. The identity credential issuing agency of the hard wallet user generates and signs a credential that can verify the identity. The signed identity credential is sent to the hard wallet user and stored in the security chip of the hard wallet terminal. The hard wallet terminal verifies the identity of the identity credential issuing agency (usually a mobile terminal and IoT device manufacturer). After the verification is passed, the identity credential issuing agency of the hard wallet terminal generates and signs a credential that can verify the identity of the hard wallet terminal. The signed identity credential is sent to the hard wallet terminal and stored in the security chip.
[0155] After the identity certificate is issued, the hard wallet terminal identity certificate issuing agency and the hard wallet user identity certificate issuing agency D1, D2, A1, A2 interact with the blockchain identity management system respectively, and the blockchain identity management system executes the update of the identity documents of the hard wallet terminals d1 and d2, and executes the update of the identity documents of the hard wallet applications a1 and a2. Among them:
[0156] For the hard wallet terminal d1, its identity document update work is to write the binding relationship between the verification public key Pk_DeviceIssuer_1 of the hard wallet terminal identity certificate issuing agency D1 and the identity certificate identifier into the identity document; for the hard wallet terminal d2, perform the same operation;
[0157] For hard wallet user a1, the identity document update work is to write the binding relationship between the verification public key Pk_UserIssuer_1 of the hard wallet user identity certificate issuing agency A1 and the identity certificate identifier into the identity document; for hard wallet user a2, perform the same operation;
[0158] The updated identity document is synchronized through the blockchain system.
[0159] Finally, the blockchain identity management system sends the public keys Pk_DeviceIssuer_D1, Pk_DeviceIssuer_D2, Pk_UserIssuer_A1, and Pk_UserIssuer_A2 of each identity credential issuing agency D1, D2, A1, and A2 and presets them on all hard wallet terminals, which can be saved in the hard wallet application or in the security chip.
[0160] In addition, the specific implementation content of the identity authentication method in an offline transaction scenario in another reference embodiment of the present invention has been described in detail in the identity authentication method in the offline transaction scenario described above, so the repeated content will not be described here.
[0161] As an embodiment of the present invention, the detailed steps of the identity authentication method in the offline transaction scenario of the embodiment of the present invention are as follows:
[0162] Phase 1: Hard wallet terminal and hard wallet identity and identity document generation
[0163] Step 1: The hard wallet terminal and the hard wallet user are initialized. The hard wallet terminal, the hard wallet user and the identity certificate issuing agency generate public and private key pairs respectively, where:
[0164] 1). The hard wallet terminal d1 (d1 is a device manufactured by the terminal manufacturer organization D1) and the hard wallet terminal d2 (d2 is a device manufactured by the terminal manufacturer organization D2) generate public and private key pairs Pk_Device_d1 / Sk_Device_d1, Pk_Device_d2 / Sk_Device_d2 in the hard wallet security chip respectively;
[0165] 2). Hard wallet user a1 (holding hardware wallet d1) and user a2 (holding hardware wallet d2) generate public and private key pairs Pk_user_a1 / Sk_user_a1 and Pk_user_a2 / Sk_user_a2 in the hard wallet security chip respectively;
[0166] 3). The hard wallet terminal identity certificate issuing agencies D1 and D2 generate public and private key pairs Pk_DeviceIssuer_D1 / SK_DeviceIssuer_D1 and Pk_DeviceIssuer_D2 / SK_DeviceIssuer_D2 in a secure server environment respectively;
[0167] 4). The hard wallet user identity certificate issuing agencies A1 and A2 generate public and private key pairs Pk_UserIssuer_A1 / Sk_UserIssuer_A1 and Pk_UserIssuer_A2 / Sk_UserIssuer_A2 in the secure server environment respectively.
[0168] Step 2: Submit public keys to the blockchain identity management system: The hard wallet terminal, hard wallet user, and each identity certificate issuing agency submit the public keys: Pk_Device_d1, Pk_Device_d2, Pk_user_a1, Pk_user_a2, Pk_DeviceIssuer_D1, Pk_DeviceIssuer_D2, Pk_UserIssuer_A1, and Pk_UserIssuer_A2 to the blockchain identity management system.
[0169] Step 3: The blockchain identity management system generates the identity identifiers of the above organizations and roles: HWID_Device_d1, HWID_Device_d2, HWID_User_a1, HWID_User_a2, HWID_DeviceIssuer_D1, HWID_DeviceIssuer_D2, HWID_UserIssuer_A1, HWID_UserIssuer_A2.
[0170] Step 4: The blockchain identity management system generates identity documents for the hard wallet terminal, hard wallet user, and each identity credential agency, HWID-DOC_User_a1, HWID-DOC_User_a2, HWID-DOC_Device_d1, HWID-DOC_Device_d2, HWID-DOC_UserIssuer_A1, HWID-DOC_UserIssuer_A2, HWID-DOC_DeviceIssuer_D1, and HWID-DOC_DeviceIssuer_D2.
[0171] Step 5: The blockchain identity management system issues respective identity identifiers to the hard wallet terminal, hard wallet user, and identity certificate issuing agency; their respective identity documents are automatically synchronized through the blockchain to ensure that they cannot be tampered with.
[0172] Phase 2: Credential Generation and Identity Document Update
[0173] Step 1: The hard wallet terminals d1 and d2 apply for their own identity credentials from the hard wallet terminal identity credential issuing agencies D1 and D2 (generally terminal manufacturers) through the GP standard secure communication and authentication protocol SCP03 (a remote communication authentication protocol between security chips and security chip terminal manufacturers formulated by the international organization GP). Terminal manufacturers D1 and D2 first verify through the SCP02 protocol that the hard wallet terminals d1 and d2 are the devices they produce;
[0174] Step 2: The hard wallet terminal identity certificate issuing agency (terminal manufacturer) D1 and D2 generate the identity certificates Credential_DeviceIssuer_d1 and Credential_DeviceIssuer_d2 of the hard wallet terminal based on the verifiable identity certificate template, and use their private keys Sk_DeviceIssuer_D1 and Sk_DeviceIssuer_D2 to sign, indicating that the hard wallet terminal device has been authenticated and verified by the terminal manufacturer;
[0175] Step 3: The identity certificate issuing agencies D1 and D2 (terminal manufacturers) of the hard wallet terminal issue the identity certificate to the hard wallet terminals d1 and d2, and the identity certificate is stored in the security chips of the terminals respectively;
[0176] Step 4: Hard wallet user a1 brings the identity identifier HWID_User_a1 and the SEID of the corresponding hard wallet terminal, and applies for identity verification to the hard wallet user identity certificate issuing agency A1 corresponding to a certain identity attribute. After the verification is passed, the identity certificate Credential_UserIssuer_a1 issued by agency A1 is obtained; hard wallet user a2 brings the identity identifier HWID_User_a2 and the SEID of the corresponding hard wallet terminal, and applies for identity verification to the hard wallet user identity certificate issuing agency A2 corresponding to a certain identity attribute. After the verification is passed, the identity certificate Credential_UserIssuer_a2 issued by agency A2 is obtained;
[0177] Step 5: The identity certificate issuing agencies D1, D2, A1, and A2 of the hard wallet terminal and the hard wallet user interact with the blockchain identity management system respectively. The blockchain identity management system executes the update of the identity documents of the hard wallet terminals d1 and d2, and executes the update of the user identity documents of the hard wallet applications a1 and a2.
[0178] Step 6: The updated identity document is synchronized through the blockchain system.
[0179] Step 7: The blockchain identity management system sends the public keys Pk_DeviceIssuer_D1, Pk_DeviceIssuer_D2, Pk_UserIssuer_A1, and Pk_UserIssuer_A2 of the identity credential issuing agencies D1, D2, A1, and A2 and presets them on all hard wallet terminals, which can be saved in the hard wallet application or in the security chip.
[0180] Phase 3: Peer-to-peer transaction identity authentication
[0181] Before two hard wallets conduct offline peer-to-peer transactions through wireless communication technologies such as NFC / Bluetooth (assuming that hard wallet user a1 pays hard wallet user a2), both parties first conduct trusted authentication of the terminal and the application.
[0182] After a1 / a2 and d1 / d2 have verified their respective identity credentials, they can enter the subsequent transaction payment process.
[0183] When the network is restored, the hard wallet terminals d1 and d2 will upload the operation logs to the blockchain identity management system, which can be used as a reference for subsequent security audits and risk tracing.
[0184] Figure 8 Schematic diagram of the main modules of an identity authentication device in an offline transaction scenario according to an embodiment of the present invention. Figure 8 As shown, the identity authentication device 800 in the offline transaction scenario is set to be applied to a hard wallet, including a wallet public key module 801, a wallet identification module 802, a wallet identity module 803 and an authentication module 804; wherein the wallet public key module 801 is used to generate a first public-private key pair of a hard wallet user and a second public-private key pair of a hard wallet terminal in a security chip; the wallet identification module 802 is used to submit the first public key of the hard wallet user and the second public key of the hard wallet terminal to the blockchain identity management system, and receive the hard wallet user identity identifier and the hard wallet terminal identity identifier returned by the blockchain identity management system; the wallet identity module 803 is used to send an identity certificate issuance request to the hard wallet user identity certificate issuing agency and the hard wallet terminal identity certificate issuing agency, respectively, and receive the hard wallet user identity certificate issued by the hard wallet user identity certificate issuing agency and the hard wallet terminal identity certificate issued by the hard wallet terminal identity certificate issuing agency; the authentication module 804 is used to perform identity authentication based on the hard wallet user identity certificate and the hard wallet terminal identity identifier in the offline transaction scenario.
[0185] Optionally, the authentication module 804 is further configured to:
[0186] Receive the third public key and the fourth public key issued by the blockchain identity management system;
[0187] Among them, the third public key is generated by the hard wallet user identity certificate issuing agency and submitted to the blockchain identity management system; the fourth public key is generated by the hard wallet terminal identity certificate issuing agency and submitted to the blockchain identity management system.
[0188] Optionally, if the hard wallet is the payer, the authentication module 804 is further used to:
[0189] Send an identity authentication request to the recipient's hard wallet;
[0190] Receive the hard wallet user identity certificate and hard wallet terminal identity identifier returned by the payee's hard wallet;
[0191] Based on the third public key and the fourth public key, identity authentication is performed on the hard wallet user identity certificate and the hard wallet terminal identity identifier returned by the payee's hard wallet respectively;
[0192] Returning the authentication result to the payee's hard wallet;
[0193] Receiving an identity authentication request sent by the payee's hard wallet;
[0194] Returning the hard wallet user identity certificate and the hard wallet terminal identity identifier to the payee hard wallet;
[0195] Receive the authentication result returned by the payee's hard wallet.
[0196] Optionally, if the hard wallet is the payee, the authentication module 804 is further used to:
[0197] Receive the identity authentication request sent by the payer's hard wallet;
[0198] Returning the hard wallet user identity certificate and the hard wallet terminal identity identifier to the payer hard wallet;
[0199] Receiving the authentication result returned by the payer's hard wallet;
[0200] Sending an identity authentication request to the payer's hard wallet;
[0201] Receive the hard wallet user identity certificate and hard wallet terminal identity identifier returned by the payer's hard wallet;
[0202] Based on the third public key and the fourth public key, identity authentication is performed on the hard wallet user identity certificate and the hard wallet terminal identity identifier returned by the payer's hard wallet respectively;
[0203] The authentication result is returned to the payer's hard wallet.
[0204] Optionally, a log module is also included to:
[0205] When the network connection is restored, the operation logs during the identity authentication process are reported to the blockchain identity management system.
[0206] Fig. 9 FIG. 1 is a schematic diagram of the main modules of an identity authentication device in an offline transaction scenario according to another embodiment of the present invention. Fig. 9 As shown, the identity authentication device 900 in the offline transaction scenario is set in the hard wallet user identity certificate issuing agency, including a first generation module 901 and a first issuance module 902; wherein the first generation module 901 is used to generate a third public-private key pair, submit the third public key to the blockchain identity management system, and receive the hard wallet user identity certificate issuing agency identity identifier returned by the blockchain identity management system; the first issuance module 902 is used to receive a hard wallet user identity certificate issuance request sent by the hard wallet, use the third private key to issue the hard wallet user identity certificate, and return the hard wallet user identity certificate to the hard wallet.
[0207] The first issuing module 902 is further used for:
[0208] Submit the hard wallet user identity credentials to the blockchain identity management system.
[0209] Fig.10 FIG. 1 is a schematic diagram of the main modules of an identity authentication device in an offline transaction scenario according to another embodiment of the present invention. Fig.10 As shown, the identity authentication device 1000 in the offline transaction scenario is arranged in the hard wallet terminal identity certificate issuing agency, including a second generation module 1001 and a second issuance module 1002; wherein, the second generation module 1001 is used to generate a fourth public-private key pair, submit the fourth public key to the blockchain identity management system, and receive the identity identifier of the hard wallet terminal identity certificate issuing agency returned by the blockchain identity management system; the second issuance module 1002 is used to receive a hard wallet terminal identity certificate issuance request sent by the hard wallet, use the fourth private key to issue the hard wallet terminal identity certificate, and return the hard wallet terminal identity certificate to the hard wallet.
[0210] Optionally, the second issuing module 1002 is further used for:
[0211] Submit the hard wallet terminal identity credential to the blockchain identity management system.
[0212] Fig.11 FIG. 1 is a schematic diagram of the main modules of an identity authentication device in an offline transaction scenario according to another embodiment of the present invention. Fig.11As shown, the identity authentication device 1100 in the offline transaction scenario is set in the blockchain identity management system, including a third generation module 1101 and a fourth generation module 1102; wherein the third generation module 1101 is used to receive the first public key of the hard wallet user and the second public key of the hard wallet terminal submitted by the hard wallet, generate the hard wallet user identity identifier and its identity document, the hard wallet terminal identity identifier and its identity document, and return the hard wallet user identity identifier and the hard wallet terminal identity identifier to the hard wallet; the fourth generation module 1102 is used to receive the third public key submitted by the hard wallet user identity certificate issuing agency and the fourth public key submitted by the hard wallet terminal identity certificate issuing agency, respectively, generate the hard wallet user identity certificate issuing agency identity identifier and its identity document, the hard wallet terminal identity certificate issuing agency identity identifier and its identity document, and return the hard wallet user identity certificate issuing agency identity identifier and the hard wallet terminal identity certificate issuing agency identity identifier to the hard wallet user identity certificate issuing agency and the hard wallet terminal identity certificate issuing agency, respectively; wherein the identity document is used to store the binding relationship between the identity identifier and its public key.
[0213] Optionally, it also includes:
[0214] An update module, configured to receive the hard wallet user identity credential submitted by the hard wallet user identity credential issuing agency; store the hard wallet user identity credential, and write the binding relationship between the hard wallet user identity credential identifier and the third public key into the hard wallet user identity document; receive the hard wallet terminal identity credential submitted by the hard wallet terminal identity credential issuing agency; store the hard wallet terminal identity credential, and write the binding relationship between the hard wallet terminal identity credential identifier and the fourth public key into the hard wallet user identity document;
[0215] The sending module is used to send the third public key and the fourth public key to the hard wallet.
[0216] It should be noted that the specific implementation content of the identity authentication device in the offline transaction scenario described in the present invention has been described in detail in the identity authentication method in the offline transaction scenario described above, so the repeated content will not be described here.
[0217] Fig.12 An exemplary system architecture 1200 is shown to which an identity authentication method in an offline transaction scenario or an identity authentication device in an offline transaction scenario according to an embodiment of the present invention can be applied.
[0218] like Fig.12As shown, the system architecture 1200 may include terminal devices 1201, 1202, 1203, a network 1204, and a server 1205. The network 1204 is used to provide a medium for communication links between the terminal devices 1201, 1202, 1203 and the server 1205. The network 1204 may include various connection types, such as wired, wireless communication links, or optical fiber cables, etc.
[0219] Users can use terminal devices 1201, 1202, and 1203 to interact with server 1205 through network 1204 to receive or send messages, etc. Various communication client applications can be installed on terminal devices 1201, 1202, and 1203, such as shopping applications, web browser applications, search applications, instant messaging tools, email clients, social platform software, etc. (only as examples).
[0220] The terminal devices 1201 , 1202 , and 1203 may be various electronic devices having a display screen and supporting web browsing, including but not limited to smart phones, tablet computers, laptop computers, and desktop computers, etc.
[0221] The server 1205 may be a server that provides various services, such as a backend management server (only an example) that provides support for shopping websites browsed by users using the terminal devices 1201, 1202, and 1203. The backend management server may analyze and process the received data such as the item information query request, and feed back the processing results to the terminal device.
[0222] It should be understood that Fig.12 The number of terminal devices, networks and servers in the embodiment is only for illustration. Any number of terminal devices, networks and servers may be provided according to implementation requirements.
[0223] Reference below Fig.13 , which shows a schematic diagram of the structure of a computer system 1300 of a terminal device suitable for implementing an embodiment of the present invention. Fig.13 The terminal device shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present invention.
[0224] like Fig.13As shown, the computer system 1300 includes a central processing unit (CPU) 1301, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 1302 or a program loaded from a storage part 1308 into a random access memory (RAM) 1303. In the RAM 1303, various programs and data required for the operation of the system 1300 are also stored. The CPU 1301, the ROM 1302, and the RAM 1303 are connected to each other via a bus 1304. An input / output (I / O) interface 1305 is also connected to the bus 1304.
[0225] The following components are connected to the I / O interface 1305: an input section 1306 including a keyboard, a mouse, etc.; an output section 1307 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc.; a storage section 1308 including a hard disk, etc.; and a communication section 1309 including a network interface card such as a LAN card, a modem, etc. The communication section 1309 performs communication processing via a network such as the Internet. A drive 1310 is also connected to the I / O interface 1305 as needed. A removable medium 1311, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 1310 as needed, so that a computer program read therefrom is installed into the storage section 1308 as needed.
[0226] In particular, according to the embodiments disclosed in the present invention, the process described above with reference to the flowchart can be implemented as a computer software program. For example, the embodiments disclosed in the present invention include a computer program, which includes a computer program carried on a computer-readable medium, and the computer program includes a program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from the network through the communication part 1309, and / or installed from the removable medium 1311. When the computer program is executed by the central processing unit (CPU) 1301, the above-mentioned functions defined in the system of the present invention are executed.
[0227] It should be noted that the computer-readable medium shown in the present invention may be a computer-readable signal medium or a computer-readable storage medium or any combination of the above two. The computer-readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present invention, a computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in combination with an instruction execution system, device or device. In the present invention, a computer-readable signal medium may include a data signal propagated in a baseband or as part of a carrier wave, which carries a computer-readable program code. This propagated data signal may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. Computer-readable signal media may also be any computer-readable medium other than computer-readable storage media, which may send, propagate or transmit a program for use by or in conjunction with an instruction execution system, apparatus or device. The program code contained on the computer-readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, optical cable, RF, etc., or any suitable combination of the above.
[0228] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, functions and operations of the system, method and computer program according to various embodiments of the present invention. In this regard, each box in the flow chart or block diagram can represent a module, a program segment, or a part of a code, and the above-mentioned module, program segment, or a part of a code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram or flow chart, and the combination of the boxes in the block diagram or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.
[0229] As another aspect, the present invention further provides a computer-readable medium, which may be included in the device described in the above embodiment; or may exist independently without being assembled into the device. The above computer-readable medium carries one or more programs, and when the above one or more programs are executed by a device, the device implements the method described in any of the above embodiments.
[0230] As another aspect, an embodiment of the present invention further provides a computer program product, including a computer program, and when the computer program is executed by a processor, the method described in any of the above embodiments is implemented.
[0231] The above specific implementations do not constitute a limitation on the protection scope of the present invention. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions may occur depending on design requirements and other factors. Any modification, equivalent substitution and improvement made within the spirit and principle of the present invention shall be included in the protection scope of the present invention.
Claims
1. An identity authentication method in an offline transaction scenario, characterized in that: Applicable to hard wallets, including: Generate a first public-private key pair of the hard wallet user and a second public-private key pair of the hard wallet terminal in the security chip respectively; Submitting the first public key of the hard wallet user and the second public key of the hard wallet terminal to the blockchain identity management system, and receiving the hard wallet user identity identifier and the hard wallet terminal identity identifier returned by the blockchain identity management system; Sending identity certificate issuance requests to a hard wallet user identity certificate issuing agency and a hard wallet terminal identity certificate issuing agency respectively, and receiving a hard wallet user identity certificate issued by the hard wallet user identity certificate issuing agency and a hard wallet terminal identity certificate issued by the hard wallet terminal identity certificate issuing agency; In an offline transaction scenario, identity authentication is performed based on the hard wallet user identity credential and the hard wallet terminal identity identifier.
2. The method according to claim 1, characterized in that In an offline transaction scenario, before identity authentication based on the hard wallet user identity certificate and the hard wallet terminal identity identifier, it also includes: Receive the third public key and the fourth public key issued by the blockchain identity management system; Among them, the third public key is generated by the hard wallet user identity certificate issuing agency and submitted to the blockchain identity management system; the fourth public key is generated by the hard wallet terminal identity certificate issuing agency and submitted to the blockchain identity management system.
3. The method according to claim 2, characterized in that If the hard wallet is the payer, identity authentication is performed based on the hard wallet user identity certificate and the hard wallet terminal identity identifier, including: Send an identity authentication request to the recipient's hard wallet; Receive the hard wallet user identity certificate and hard wallet terminal identity identifier returned by the payee's hard wallet; Based on the third public key and the fourth public key, identity authentication is performed on the hard wallet user identity certificate and the hard wallet terminal identity identifier returned by the payee's hard wallet respectively; Returning the authentication result to the payee's hard wallet; Receiving an identity authentication request sent by the payee's hard wallet; Returning the hard wallet user identity certificate and the hard wallet terminal identity identifier to the payee hard wallet; Receive the authentication result returned by the payee's hard wallet.
4. The method according to claim 2, characterized in that: If the hard wallet is the payee, identity authentication is performed based on the hard wallet user identity certificate and the hard wallet terminal identity identifier, including: Receive the identity authentication request sent by the payer's hard wallet; Returning the hard wallet user identity certificate and the hard wallet terminal identity identifier to the payer hard wallet; Receiving the authentication result returned by the payer's hard wallet; Sending an identity authentication request to the payer's hard wallet; Receive the hard wallet user identity certificate and hard wallet terminal identity identifier returned by the payer's hard wallet; Based on the third public key and the fourth public key, identity authentication is performed on the hard wallet user identity certificate and the hard wallet terminal identity identifier returned by the payer's hard wallet respectively; The authentication result is returned to the payer's hard wallet.
5. The method according to claim 3 or 4, characterized in that: Also includes: When the network connection is restored, the operation logs during the identity authentication process are reported to the blockchain identity management system.
6. An identity authentication method in an offline transaction scenario, characterized in that: Applicable to the issuing agency of the user identity certificate of the hard wallet, including: Generate a third public-private key pair and submit the third public key to the blockchain identity management system; Receiving the identity identifier of the hard wallet user identity certificate issuing agency returned by the blockchain identity management system; Receive a hard wallet user identity credential issuance request sent by the hard wallet; The hard wallet user identity certificate is issued using the third private key, and the hard wallet user identity certificate is returned to the hard wallet.
7. The method according to claim 6, characterized in that After returning the hard wallet user identity certificate to the hard wallet, it also includes: Submit the hard wallet user identity credentials to the blockchain identity management system.
8. An identity authentication method in an offline transaction scenario, characterized in that: Applicable to the issuing agency of identity certificate of hard wallet terminal, including: Generate a fourth public-private key pair, and submit the fourth public key to the blockchain identity management system; Receiving the identity identifier of the hard wallet terminal identity certificate issuing agency returned by the blockchain identity management system; Receive a hard wallet terminal identity credential issuance request sent by the hard wallet; The fourth private key is used to issue a hard wallet terminal identity certificate, and the hard wallet terminal identity certificate is returned to the hard wallet.
9. The method according to claim 8, characterized in that After returning the hard wallet terminal identity certificate to the hard wallet, it also includes: Submit the hard wallet terminal identity credential to the blockchain identity management system.
10. An identity authentication method in an offline transaction scenario, characterized in that: Applied to blockchain identity management systems, including: Receive a first public key of a hard wallet user and a second public key of a hard wallet terminal submitted by the hard wallet; Generate a hard wallet user identity and its identity document, a hard wallet terminal identity and its identity document, and return the hard wallet user identity and the hard wallet terminal identity to the hard wallet; Respectively receive the third public key submitted by the hard wallet user identity certificate issuing agency and the fourth public key submitted by the hard wallet terminal identity certificate issuing agency; Generate a hard wallet user identity certificate issuing agency identity identifier and its identity document, a hard wallet terminal identity certificate issuing agency identity identifier and its identity document respectively, and return the hard wallet user identity certificate issuing agency identity identifier and the hard wallet terminal identity certificate issuing agency identity identifier to the hard wallet user identity certificate issuing agency and the hard wallet terminal identity certificate issuing agency respectively; The identity document is used to store the binding relationship between the identity identifier and its public key.
11. The method according to claim 10, characterized in that Also includes: Receiving the hard wallet user identity certificate submitted by the hard wallet user identity certificate issuing institution; Storing the hard wallet user identity credential, and writing the binding relationship between the hard wallet user identity credential identifier and the third public key into the hard wallet user identity document; Receiving the hard wallet terminal identity certificate submitted by the hard wallet terminal identity certificate issuing institution; Storing the hard wallet terminal identity credential, and writing the binding relationship between the hard wallet terminal identity credential identifier and the fourth public key into the hard wallet user identity document; The third public key and the fourth public key are issued to the hard wallet.
12. An identity authentication device in an offline transaction scenario, characterized in that: Settings for use with hard wallets include: A wallet public key module, used to generate a first public-private key pair of a hard wallet user and a second public-private key pair of a hard wallet terminal in a security chip; A wallet identification module, used to submit the first public key of the hard wallet user and the second public key of the hard wallet terminal to the blockchain identity management system, and receive the hard wallet user identity and the hard wallet terminal identity returned by the blockchain identity management system; A wallet identity module, used to send identity certificate issuance requests to a hard wallet user identity certificate issuing agency and a hard wallet terminal identity certificate issuing agency respectively, and receive a hard wallet user identity certificate issued by the hard wallet user identity certificate issuing agency and a hard wallet terminal identity certificate issued by the hard wallet terminal identity certificate issuing agency; The authentication module is used to perform identity authentication based on the hard wallet user identity certificate and the hard wallet terminal identity in an offline transaction scenario.
13. An identity authentication device in an offline transaction scenario, characterized in that: Set up in the hard wallet user identity certificate issuing agency, including: The first generation module is used to generate a third public-private key pair, submit the third public key to the blockchain identity management system, and receive the identity identifier of the hard wallet user identity certificate issuing agency returned by the blockchain identity management system; The first issuing module is used to receive a hard wallet user identity certificate issuance request sent by the hard wallet, use the third private key to issue the hard wallet user identity certificate, and return the hard wallet user identity certificate to the hard wallet.
14. An identity authentication device in an offline transaction scenario, characterized in that: The identity certificate issuing agency set up in the hard wallet terminal includes: A second generation module is used to generate a fourth public-private key pair, submit the fourth public key to the blockchain identity management system, and receive the identity identifier of the hard wallet terminal identity certificate issuing agency returned by the blockchain identity management system; The second issuing module is used to receive a hard wallet terminal identity certificate issuance request sent by the hard wallet, use the fourth private key to issue the hard wallet terminal identity certificate, and return the hard wallet terminal identity certificate to the hard wallet.
15. An identity authentication device in an offline transaction scenario, characterized in that: Set up in the blockchain identity management system, including: A third generating module is used to receive the first public key of the hard wallet user and the second public key of the hard wallet terminal submitted by the hard wallet, generate the hard wallet user identity and its identity document, the hard wallet terminal identity and its identity document, and return the hard wallet user identity and the hard wallet terminal identity to the hard wallet; The fourth generation module is used to receive the third public key submitted by the hard wallet user identity credential issuing agency and the fourth public key submitted by the hard wallet terminal identity credential issuing agency, respectively, generate the hard wallet user identity credential issuing agency identity identifier and its identity document, the hard wallet terminal identity credential issuing agency identity identifier and its identity document, and return the hard wallet user identity credential issuing agency identity identifier and the hard wallet terminal identity credential issuing agency identity identifier to the hard wallet user identity credential issuing agency and the hard wallet terminal identity credential issuing agency, respectively; wherein the identity document is used to store the binding relationship between the identity identifier and its public key.
16. An electronic device, characterized in that: include: one or more processors; a storage device for storing one or more programs, When the one or more programs are executed by the one or more processors, the one or more processors implement the method according to any one of claims 1 to 11.
17. A computer readable medium having a computer program stored thereon, characterized in that: When the program is executed by a processor, the method according to any one of claims 1 to 11 is implemented.
18. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the method according to any one of claims 1 to 11 is implemented.
Citation Information
Patent Citations
Off-line payment method and consumption terminal for electronic purse
CN102096967A
Digital currency double offline payment realization method, device and apparatus and storage medium
CN111144862A
Digital wallet device and double offline transaction method thereof
CN115689559A
Blockchain-based transaction from offline wallet
WO2021005269A1
