Real-name digital identity management method, signature device and verification device based on blockchain
By storing public keys and ID numbers on the blockchain and combining biometric information for real-name authentication, the problems of insufficient real-name authentication and redundancy of blockchain information in the existing technology are solved, and real-name based on blockchain is realized Digital identity management improves security and credibility, ensuring the authenticity and non-deniability of identity and behavior.
Patent Information
- Application Number
- CN202010237882.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2020-03-30
- Publication Date
- 2024-11-26
- Estimated Expiration
- 2040-03-30
AI Technical Summary
The existing digital identity management solution based on blockchain has problems such as insufficient real-name authentication, redundant blockchain information, reduced trust caused by hosting private keys, and high resource consumption in the verification process.
The identity identification information and security factors are marked through the private key to form a digital signature, and the public key and ID number are stored by the blockchain, and real-name authentication is performed in combination with biometric information to reduce the amount of information stored in the blockchain. Users manage the private keys themselves. And add anti-vitro and anti-replay mechanisms during the verification process.
Real-name digital identity management based on blockchain is realized, which improves credibility and security, reduces blockchain storage information, ensures identity authenticity and behavior non-repudiation, reduces resource consumption, and enhances user control.
Smart Images

Figure CN113472521B_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of blockchain technology, and in particular to a real-name digital identity management method, signature device, and verification device based on blockchain. Background Art
[0002] In the field of informatization, digital identity is very important. For ordinary information systems, an account is a simple way to express digital identity. Without the protection of an account and password, important information in the information system will be easily leaked, digital assets will suffer losses, and there may be economic losses. For business systems related to the important interests of users, real-name authentication is required to ensure that only the user himself can handle related business. Only in this way can the legal responsibility of the relevant person be investigated when problems arise. For systems that require digital signatures, such as emails, in addition to account and password, there must also be a digital certificate related to the identity. The authenticity of the information is guaranteed through digital signatures to prevent information tampering and denial of responsibility.
[0003] At present, there are many blockchain-based digital identity solutions on the market, but these solutions always have some shortcomings in terms of authenticity, traceability, non-repudiation, security, etc., which are summarized as follows:
[0004] (1) No real-name authentication. Without real-name authentication, legal responsibility cannot be pursued. Although some solutions have implemented real-name authentication, they do not verify biometric information, which may lead to fraudulent use.
[0005] (2) Too much information is stored in the blockchain, such as nationality, place of origin, etc. The storage cost of the blockchain is very expensive, and the amount of information stored in the blockchain should be minimized. In addition, from the perspective of blockchain information transparency and user privacy protection, the amount of information stored in the blockchain should also be minimized.
[0006] (3) Private key hosting. Although private key hosting can facilitate user operations and prevent users from forgetting their private keys, it means that trust is reduced and there is a risk of misuse. It also means that security is reduced and the hosting service may be attacked, resulting in a large number of key leaks.
[0007] (4) The verification process does not consider the risk of signature information being stolen or replayed. If the signature information is intercepted and used for other purposes or reused, it may cause economic losses. Summary of the invention
[0008] The embodiments of this specification provide a real-name digital identity management method, a signature device, and a verification device based on blockchain, which are used to solve the following technical problems in the prior art:
[0009] No real-name authentication;
[0010] Information redundancy in blockchain;
[0011] Trust is reduced after the private key is managed;
[0012] The verification process consumes resources.
[0013] The embodiments of this specification adopt the following technical solutions:
[0014] The first aspect of the embodiment of the invention provides a real-name digital identity management method based on blockchain, comprising:
[0015] The identity information and security factors are marked by a private key to form a digital signature, and the private key and its corresponding public key are generated by the signing client;
[0016] The identity identification information and the digital signature are sent to the verification client, so that the verification client obtains the public key stored on the blockchain according to the identity identification information, decrypts the digital signature, and verifies whether the identity identification information and the security factor are legal.
[0017] In one example, the identity information and security factors are marked by a private key to form a digital signature, including:
[0018] The signing client determines an asymmetric encryption algorithm for forming the digital signature according to a business scenario.
[0019] In one example, marking the identity information and the security factor by a private key to form a digital signature, and sending the identity information and the digital signature to the verification client includes:
[0020] The signing client performs a hash operation on the business content to obtain a hash value of the business content;
[0021] The signing client encrypts the identity information, the security factor and the hash value of the business content through a private key to form a digital signature, and sends the business content, the identity information and the digital signature to the verification client.
[0022] A second aspect of an embodiment of the present invention provides a real-name digital identity management method based on blockchain, comprising:
[0023] Receiving identity information and a digital signature sent by a signing client, wherein the digital signature is formed by the signing client marking the identity information and the security factor through a private key;
[0024] The public key stored on the blockchain is obtained according to the identity identification information, and the digital signature is decrypted to verify whether the identity identification information and the security factor are legal.
[0025] In one example, the verifying whether the identity information and the security factor are legal includes:
[0026] The household registration information and biometric information in the identity identification information are compared with the household registration information and biometric information corresponding to the identity identification information pre-stored in the blockchain to determine whether the identity identification information is legal.
[0027] In one example, the verifying whether the identity information and the security factor are legal includes:
[0028] Determine the number and type of security factors decrypted from the digital signature, where the type of security factors includes at least one or more of a timestamp, a sequence number, and a special prompt;
[0029] The security factor is compared with the security factor related to the identity identification information in the blockchain to determine whether the security factor is legitimate.
[0030] In one example, decrypting the digital signature to verify whether the identity information and the security factor are legitimate includes:
[0031] The verification client calculates the business content sent by the signing client according to the hash algorithm agreed upon by both parties to obtain a hash value of the business content;
[0032] The verification client uses the public key to decrypt the digital signature to obtain a hash value of another business content;
[0033] Compare the hash values of two business contents to see if they are consistent, to determine whether the business contents have been tampered with.
[0034] In one example, in the step of obtaining a public key stored on a blockchain according to the identity information, storing the public key in the blockchain in advance includes:
[0035] The ID number in the user's identity information, the public key generated for the user by the specified cryptographic algorithm, and the name of the specified cryptographic algorithm are sent to the blockchain for real-name authentication, so that the blockchain saves the user's identity information, public key and the name of the cryptographic algorithm after the authentication, wherein other information in the identity information is stored outside the blockchain.
[0036] A third aspect of an embodiment of the present invention provides a real-name digital identity management signature device based on blockchain, at least one processor; and
[0037] a memory communicatively connected to the at least one processor; wherein,
[0038] The memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to:
[0039] The identity information and security factors are marked by a private key to form a digital signature, wherein the private key and its corresponding public key are generated by a signature client on the signature device;
[0040] The identity identification information and the digital signature are sent to the verification client, so that the verification client obtains the public key stored on the blockchain according to the identity identification information, decrypts the digital signature, and verifies whether the identity identification information and the security factor are legal.
[0041] A fourth aspect of an embodiment of the present invention provides a real-name digital identity management and verification device based on blockchain, at least one processor; and
[0042] a memory communicatively connected to the at least one processor; wherein,
[0043] The memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to:
[0044] Receiving identity information and a digital signature sent by a signing client, wherein the digital signature is formed by the signing client marking the identity information and the security factor through a private key;
[0045] The public key stored on the blockchain is obtained according to the identity identification information, and the digital signature is decrypted to verify whether the identity identification information and the security factor are legal.
[0046] At least one of the above technical solutions adopted in the embodiments of this specification can achieve the following beneficial effects:
[0047] (1) Compared with centralized solutions, blockchain-based solutions are more credible;
[0048] (2) Real-name authentication. The embodiments of the present invention are different from the anonymous digital identity of general blockchains. The digital identity of the present invention is authenticated by real name, and the real identity of the user is authenticated by biometric technology combined with reliable public security data. Combining the real-name authenticated digital identity with human behavior can trace human behavior, investigate the legal responsibilities of relevant people, and reward good and punish evil;
[0049] (3) Streamline the information in the blockchain. Only the user's ID number, cryptographic algorithm name, and public key are stored in the blockchain, and the rest of the information can be stored outside the blockchain. In business dealings, the most important and core content is to determine the authenticity of the identity, prevent impersonation, prevent fake identities, and prevent denial of ownership. As long as the authenticity of the ID number is guaranteed and the business is indeed handled by the person himself, the root of the problem is grasped. In addition to the ID number, information such as gender, place of origin, etc. can be stored by a centralized trusted system outside the blockchain;
[0050] (4) Users generate public and private keys by themselves, keep their private keys, and store public keys in the blockchain. Users have complete control over their digital identities. At the same time, the openness and immutability of the blockchain make digital identities authentic and behaviors irrefutable;
[0051] (5) Different asymmetric cryptographic algorithms can be agreed upon and selected according to the different security environment requirements of various businesses, so that the method has a wider applicability and the system has unlimited scalability in terms of security algorithms;
[0052] (6) The verification process includes elements to prevent fraud and replay, such as timestamps, serial numbers, and special prompts, to prevent fraudulent use of digital signatures after they are intercepted, to prevent digital signatures from being used for other purposes, and to ensure the authenticity of user behavior;
[0053] (7) The embodiments of the present invention have a wide range of application scenarios. They can be used in scenarios such as electronic identity verification, business transactions that require digital signatures, and as a login authentication method for information systems. BRIEF DESCRIPTION OF THE DRAWINGS
[0054] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:
[0055] Figure 1 A schematic diagram of the overall architecture of the real-name identity management method provided by an embodiment of the present invention;
[0056] Figure 2 A schematic diagram of a real-name authentication application process provided by an embodiment of the present invention;
[0057] Figure 3 A schematic diagram of the real-name authentication service process provided by an embodiment of the present invention;
[0058] Figure 4 A schematic diagram of checking for duplicate real-name digital identity information provided by an embodiment of the present invention;
[0059] Figure 5A schematic diagram of a first method flow chart provided by an embodiment of the present invention;
[0060] Figure 6 A schematic diagram of a second method flow chart provided by an embodiment of the present invention;
[0061] Figure 7 A schematic diagram of a real-name digital identity signature process in a first application scenario provided by an embodiment of the present invention;
[0062] Figure 8 A schematic diagram of a real-name digital identity authentication process in a first application scenario provided by an embodiment of the present invention;
[0063] Fig. 9 A schematic diagram of a real-name digital identity signature process in a second application scenario provided by an embodiment of the present invention;
[0064] Fig.10 A schematic diagram of a real-name digital identity authentication process in a second application scenario provided by an embodiment of the present invention;
[0065] Fig.11 A schematic diagram of a real-name digital identity signature process in a third application scenario provided by an embodiment of the present invention;
[0066] Fig.12 A schematic diagram of a real-name digital identity authentication process in a third application scenario provided by an embodiment of the present invention;
[0067] Fig.13 A schematic diagram of a real-name digital identity management signature device framework based on blockchain provided in an embodiment of the present invention;
[0068] Fig.14 A schematic diagram of a real-name digital identity management and verification device framework based on blockchain provided in an embodiment of the present invention. DETAILED DESCRIPTION
[0069] In order to make the purpose, technical solutions and advantages of this specification more clear, the technical solutions of this application will be clearly and completely described below in combination with the specific embodiments of this specification and the corresponding drawings. Obviously, the described embodiments are only part of the embodiments of this application, not all of them. Based on the embodiments in the specification, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.
[0070] Combining digital identity with human behavior can trace human behavior and reward good and punish evil; combining digital identity with digital assets can protect people's rights and interests from infringement. The above results are all based on the authenticity and credibility of digital identity. If the digital identity is used fraudulently or the data is tampered with, the above beneficial effects cannot be achieved.
[0071] Before the emergence of blockchain technology, the problem of digital identity and real-name authentication was solved in a centralized way. The centralized system is controlled by one organization. When a dispute occurs, there may be illegal acts such as tampering with data and deleting logs to eliminate evidence. Compared with decentralized blockchain solutions, the credibility of centralized solutions is weaker. In addition, centralized systems are prone to single point failures, and system abnormalities or network congestion may cause service unavailability.
[0072] Blockchain uses a decentralized consensus mechanism to achieve information that is not tamperable, non-repudiable, and trustworthy. Blockchain, especially data on public blockchains, is open and transparent. In combination with the technical characteristics of blockchain, this case proposes a real-name digital identity management method and system based on blockchain. The credibility and provability of real-name digital identity-related information are guaranteed by the non-tamperability, non-repudiation, openness, and transparency of blockchain information. The decentralized characteristics of blockchain prevent single point failures of services.
[0073] The embodiments of the present invention provide a real-name digital identity management method and corresponding solutions based on blockchain to address a series of problems related to integrity and security, such as digital identity theft or fraudulent use, centralized system information tampering, denial of rights, and identity concealment and non-traceability. The methods can ensure the authenticity of user identities and behaviors, prevent information systems from being illegally accessed by bad people, protect the various rights and interests of the people recorded in the information system, and ensure that people abide by laws and regulations and be honest and trustworthy in business dealings.
[0074] The technical solutions provided by various embodiments of the present application are described in detail below in conjunction with the accompanying drawings.
[0075] Figure 1 The overall architecture diagram of the real-name identity management method provided by the embodiment of the present invention is as follows: Figure 1 As shown, the blockchain-based real-name digital identity management method proposed in the embodiment of the present invention includes five business processes: digital identity application, real-name authentication, digital identity preservation, digital identity use and verification. For the convenience of description, these five business processes are logically attributed to five business modules: application client, real-name authentication service, alliance blockchain, digital signature client, and verification client.
[0076] It can be understood that, depending on the usage scenarios, the application client, digital signature client and verification client can be understood as the manifestation of different services in a user terminal or multiple separate device terminals, and the embodiments of the present invention do not impose any special restrictions on this. In addition, the business logic of the application client and the digital signature client can be completed by one client, or the business logic of the application client and the verification client can be completed by one client, and the embodiments of the present invention do not impose any special restrictions on this.
[0077] The real-name authentication service joins the alliance blockchain as a client of the alliance blockchain. The alliance blockchain issues a digital certificate to the real-name authentication service. Only the client with the alliance blockchain digital certificate can write the user's real-name digital identity into the alliance blockchain. This mechanism ensures the credibility of the real-name digital identity data.
[0078] Figure 2 A schematic diagram of the real-name authentication application process provided by an embodiment of the present invention, such as Figure 2 As shown, the biometric information type is set according to the business scenario, and the applicant's specific biometric information is collected through the biometric collection device. The embodiment of the present invention supports real-name authentication methods of multiple biometric information types, such as portrait, fingerprint, iris and other biometric recognition technologies.
[0079] The application client sets the asymmetric cryptographic algorithm according to the business scenario, and then generates an asymmetric key pair, including a public key and a private key, according to the specified asymmetric cryptographic algorithm. Supports multiple asymmetric cryptographic algorithms, such as RAS, SM2, etc. The application client gives the private key to the applicant for safekeeping, and then sends the biometric information type set according to the business scenario, the applicant's biometric data, the applicant's ID number, the asymmetric cryptographic algorithm name set according to the business scenario, and the public key generated by the above process as parameters to the real-name authentication service, requesting the real-name authentication service to perform real-name authentication.
[0080] Figure 3 A schematic diagram of the real-name authentication service process provided by an embodiment of the present invention, such as Figure 3 As shown in the figure, after receiving the real-name authentication request from the applicant client, the real-name authentication service on the blockchain first verifies whether the biometric data and the ID number match based on the three parameters of biometric information type, applicant's biometric data, and applicant's ID number, combined with reliable public security data. If the two do not match, an error message indicating that the real-name authentication failed is returned to the applicant client, and the entire process ends. If the two match, the applicant's ID number, asymmetric cryptography algorithm name, and public key are sent to the alliance blockchain, requesting the alliance blockchain to save the user's real-name digital identity information.
[0081] Figure 4Schematic diagram of real-name digital identity information duplication check provided by an embodiment of the present invention. Figure 4 As shown in the figure, after receiving the save request from the real-name authentication service, the alliance blockchain will hand over the real-name digital identity information (including the applicant's ID number, asymmetric cryptography algorithm name and public key) to the smart contract for processing. The alliance blockchain smart contract first uses the applicant's ID number and asymmetric cryptography algorithm name as search conditions to verify whether there is duplicate data. If there is duplicate data, it will not be saved, and a duplicate data error will be returned to the real-name authentication service, and the real-name authentication service will return a duplicate data error to the application client. If there is no duplicate data, the real-name digital identity information, including the applicant's ID number, asymmetric cryptography algorithm name and public key, will be saved, and then a successful save message will be returned to the real-name authentication service, and the real-name authentication service will return a successful real-name digital identity application message to the application client.
[0082] Figure 5 A schematic diagram of a first method flow chart provided in an embodiment of the present invention is as follows: Figure 5 As shown, the embodiment of the present invention provides a first blockchain-based real-name digital identity management method, including:
[0083] S501 marks the identity information and security factors with a private key to form a digital signature, wherein the private key and its corresponding public key are generated by the signing client;
[0084] S502 sends the identity identification information and the digital signature to the verification client, so that the verification client obtains the public key stored on the blockchain according to the identity identification information, decrypts the digital signature, and verifies whether the identity identification information and the security factor are legal.
[0085] According to a specific embodiment of the present invention, the signing client may determine the type of asymmetric encryption algorithm for forming the digital signature according to a business scenario.
[0086] According to a specific embodiment of the present invention, the identity identification information and security factors are marked by a private key to form a digital signature, and the identity identification information and the digital signature are sent to a verification client, including: the signing client performs a hash operation on the business content to obtain a hash value of the business content; the signing client encrypts the identity identification information, the security factor and the hash value of the business content by a private key to form a digital signature, and sends the business content, the identity identification information and the digital signature to the verification client.
[0087] Figure 6 A second method flow chart provided in an embodiment of the present invention is as follows: Figure 6 As shown, the embodiment of the present invention provides a second blockchain-based real-name digital identity management method, including:
[0088] S601 receives identity information and a digital signature sent by a signing client, where the digital signature is formed by the signing client marking the identity information and security factors with a private key;
[0089] S602 obtains the public key stored on the blockchain according to the identity identification information, decrypts the digital signature, and verifies whether the identity identification information and the security factor are legal.
[0090] According to a specific embodiment of the present invention, in verifying whether the identity identification information and the security factor are legal, verifying the identity identification information includes: comparing the household registration information and biometric information in the identity identification information with the household registration information and biometric information corresponding to the identity identification information pre-stored in the blockchain to determine whether the identity identification information is legal.
[0091] According to a specific embodiment of the present invention, in verifying whether the identity identification information and the security factor are legal, verifying the security factor includes: determining the number and type of security factors decrypted from the digital signature, the type of the security factor including at least one or more of a timestamp, a serial number, and a special prompt; comparing the security factor with the security factor related to the identity identification information in the blockchain to determine whether the security factor is legal.
[0092] According to a specific embodiment of the present invention, the decryption of the digital signature to verify whether the identity identification information and the security factor are legal may also include: the verification client calculates the business content sent by the signing client according to the hash algorithm agreed upon by both parties to the business, and obtains a hash value of the business content; the verification client uses the public key to decrypt the digital signature to obtain a hash value of another business content; and compares whether the hash values of the two business contents are consistent to determine whether the business content has been tampered with.
[0093] According to a specific embodiment of the present invention, the public key stored on the blockchain is obtained according to the identity information, and the public key is stored in the blockchain in advance, including: the ID number in the user's identity information, the public key generated for the user by the specified cryptographic algorithm, and the name of the specified cryptographic algorithm are sent to the blockchain for real-name authentication, so that the blockchain saves the user's identity information, public key and the name of the cryptographic algorithm after the authentication, wherein other information in the identity information is stored outside the blockchain. This step corresponds to Figure 2-Figure 4 steps.
[0094] The method of the embodiment of the present invention supports a wide range of real-name digital identity application scenarios, which are summarized into three main application scenarios for the convenience of description: simple scenario (first application scenario), anti-tampering scenario (second application scenario), and anti-fraud scenario (third application scenario). These three scenarios are introduced below in conjunction with the accompanying drawings.
[0095] Figure 7 and Figure 8 It represents the use and verification method of real-name digital identity in the first application scenario (simple scenario), which is suitable for scenarios such as logging into the system that only require simple identity verification.
[0096] Figure 7 The following is a schematic diagram of the real-name digital identity signature process in the first application scenario provided by the embodiment of the present invention. Figure 7 As shown in the figure, the signing client sets an asymmetric cryptographic algorithm according to the business scenario. The signing client uses the user's private key to encrypt the ID number and security factor using an asymmetric cryptographic algorithm to obtain a digital signature. The security factor is negotiated and determined by both parties based on specific needs. It can be a single security factor or multiple security factors, such as a timestamp, serial number, special prompt, etc. Finally, the signing client sends the digital identity information, including the ID number and digital signature, to the verification client.
[0097] Figure 8 The following is a schematic diagram of the real-name digital identity authentication process in the first application scenario provided by the embodiment of the present invention. Figure 8 As shown, after the verification client receives the real-name digital identity information (including ID number and digital signature) of the signing client, it first queries the alliance blockchain for relevant information about the real-name digital identity based on the ID number and the asymmetric cryptographic algorithm name set according to the business scenario, including the ID number, asymmetric cryptographic algorithm name and public key. If no result is found, the decryption fails, and an error message indicating that the decryption failed is returned to the signing client, and the process ends. If a result is found, the corresponding asymmetric cryptographic algorithm is determined according to the asymmetric cryptographic algorithm name in the query result, and then the public key in the query result is used to decrypt the real digital signature to obtain the ID number and security factor. If the decryption fails, an error message indicating that the decryption failed is returned to the signing client, and the process ends.
[0098] The verification client compares the plaintext ID number from the signing client with the ID number decrypted from the digital signature to determine whether the two are consistent. If the two are inconsistent, it is determined to be an illegal identity, and an error message of illegal identity is returned to the signing client, and the process ends. If they are consistent, continue to verify whether the security factor is legal.
[0099] The verification client verifies the security factor decrypted from the digital signature to determine whether it is legal. The security factor is determined by negotiation between the two parties based on specific needs. It can be a single security factor or multiple security factors. For example, if it is a timestamp, verify whether the timestamp is within the predetermined range; if it is a serial number, verify whether the serial number is the predetermined number; if it is a special prompt, verify whether the special prompt is the same as the predetermined special prompt, etc. If the verification fails, it is determined to be an illegal security factor, and an error message of illegal security factor is returned to the signing client, and the process ends. If the verification is successful, a message of successful verification is returned to the signing client.
[0100] Fig. 9 and Fig.10 It represents the use and verification method of real-name digital identity in the second application scenario (anti-tampering scenario), which is suitable for systems such as e-mail and electronic contracts, which need to verify the real identity of the user and prevent the business content from being tampered with.
[0101] Fig. 9 The following is a schematic diagram of the real-name digital identity signature process in the second application scenario provided by the embodiment of the present invention. Fig. 9 As shown, the signing client first performs a hash operation on the business content to obtain a business content hash value. Then, an asymmetric cryptographic algorithm is set according to the needs of the business scenario, and the ID number, security factor and business content hash value are encrypted using the user's private key using an asymmetric cryptographic algorithm to obtain a digital signature. The security factor is negotiated and determined by both parties to the business based on specific needs. It can be a single security factor or multiple security factors, such as a timestamp, serial number, special prompt, etc. The hash algorithm is also negotiated and determined by both parties to the business, such as: SM3, MD5, SHA256, etc. Finally, the signing client sends the digital identity information (including ID number and digital signature) and business content to the verification client.
[0102] Fig.10 A schematic diagram of a real-name digital identity authentication process in a second application scenario provided by an embodiment of the present invention, such as Fig.10As shown, after the verification client receives the real-name digital identity information (including ID number and digital signature) and business content of the signing client, it first queries the alliance blockchain for relevant information about the real-name digital identity based on the ID number and the asymmetric cryptographic algorithm name set according to the business scenario, including the ID number, asymmetric cryptographic algorithm name and public key. If no result is found, the decryption fails, and an error message indicating that the decryption failed is returned to the signing client, and the process ends. If a result is found, the corresponding asymmetric cryptographic algorithm is determined according to the asymmetric cryptographic algorithm name in the query result, and then the digital signature is decrypted using the public key in the query result to obtain the ID number, security factor and business content hash value. If the decryption fails, an error message indicating that the decryption failed is returned to the signing client, and the process ends.
[0103] The verification client compares the plaintext ID number from the signing client with the ID number decrypted from the digital signature to determine whether the two are consistent. If the two are inconsistent, it is determined to be an illegal identity, and an error message of illegal identity is returned to the signing client, and the process ends. If they are consistent, continue to verify whether the security factor is legal.
[0104] The verification client verifies the security factor decrypted from the digital signature to determine whether it is legal. The security factor is determined by negotiation between the two parties based on specific needs. It can be a single security factor or multiple security factors. For example, if it is a timestamp, verify whether the timestamp is within the predetermined range; if it is a serial number, verify whether the serial number is the predetermined number; if it is a special prompt, verify whether the special prompt is the same as the predetermined special prompt, etc. If the verification fails, it is determined to be an illegal security factor, and an error message of the illegal security factor is returned to the signing client, and the process ends. If the verification succeeds, continue to verify whether the business data has been tampered with.
[0105] The verification client calculates the hash value of the business content from the signing client according to the hash algorithm agreed upon by both parties, such as SM3, MD5, SHA256, etc., and compares it with the business hash value decrypted from the digital signature to determine whether the two are consistent. If the two are inconsistent, it is determined that the business data has been tampered with, and an error message indicating that the business data has been tampered with is returned to the signing client, and the process ends. If the verification is successful, a verification success message is returned to the signing client.
[0106] Fig.11 and Fig.12It indicates the use and verification method of real-name digital identity in the third application scenario (anti-fraudulent use), which is applicable to scenarios such as entering venues and handling business, where the resident ID card needs to be presented and verified. It is necessary to ensure the authenticity of the ID card and the consistency between the ID card and the person. Therefore, the real-name digital identity verification method in the anti-fraudulent use scenario, in addition to completing all the steps of the real-name digital identity verification method in the simple scenario, also needs to verify on-site whether the biometrics are consistent with the real-name digital identity.
[0107] Fig.11 A schematic diagram of a real-name digital identity signature process in a third application scenario provided by an embodiment of the present invention, such as Fig.11 As shown in the figure, an asymmetric cryptographic algorithm is set according to the business scenario. The signing client first uses the user's private key to encrypt the ID number and security factor using an asymmetric cryptographic algorithm to obtain a digital signature. The security factor is negotiated and determined by both parties based on specific needs. It can be a single security factor or multiple security factors, such as a timestamp, serial number, special prompt, etc. Finally, the signing client displays the digital identity information in the form of a QR code so that the verification client can obtain the digital identity information by scanning the QR code; or the digital identity information is transmitted to the verification client through NFC technology. Digital identity information includes the ID number and digital signature.
[0108] Fig.12 The real-name digital identity authentication process in the third application scenario provided by the embodiment of the present invention is shown as follows: Fig.12 As shown, the verification client obtains the real-name digital identity information by scanning the QR code of the signing client, or receives the real-name digital identity information of the client through an NFC device. After the verification client receives the real-name digital identity information (including the ID number and digital signature), it first queries the alliance blockchain for relevant information about the real-name digital identity based on the ID number and the asymmetric cryptographic algorithm name set according to the business scenario, including the ID number, asymmetric cryptographic algorithm name and public key. If no result is found, an error message indicating that the decryption failed is displayed, and the entire verification process ends. If a result is found, the corresponding asymmetric cryptographic algorithm is determined according to the asymmetric cryptographic algorithm name in the query result, and then the public key in the query result is used to decrypt the real digital signature to obtain the ID number and security factor. If the decryption fails, an error message indicating that the decryption failed is displayed, and the entire verification process ends.
[0109] The verification client compares the plaintext ID number from the signing client with the ID number decrypted from the digital signature to determine whether the two are consistent. If the two are inconsistent, it is determined to be an illegal identity, and an error message indicating that the identity verification failed is displayed, ending the entire verification process. If they are consistent, it continues to verify whether the security factor is legal.
[0110] The verification client verifies the security factor decrypted from the digital signature to determine whether it is legal. The security factor is determined by negotiation between the two parties based on specific needs. It can be a single security factor or multiple security factors. For example, if it is a timestamp, verify whether the timestamp is within the predetermined range; if it is a serial number, verify whether the serial number is the predetermined number; if it is a special prompt, verify whether the special prompt is the same as the predetermined special prompt, etc. If the verification fails, it is determined to be an illegal security factor, and an error message of illegal identity document is displayed, ending the entire verification process. If the verification is successful, continue to verify the user's biometrics.
[0111] The verification client collects the user's biometric information through the biometric collection device according to the set biometric information type. The verification client supports multiple biometric verification methods, such as portrait, fingerprint, iris and other biometric recognition technologies. The verification client verifies whether the biometric data matches the ID number based on the set biometric information type, the user's biometric data, and the ID number, combined with reliable public security data. If the verification fails, it is determined to be identity fraud, and a message indicating that the ID verification is wrong is displayed, ending the entire verification process. If the verification is successful, a message indicating that the verification is successful is displayed.
[0112] Based on the same idea, some embodiments of the present application also provide devices and non-volatile computer storage media corresponding to the above methods.
[0113] Fig.13 A schematic diagram of a real-name digital identity management signature device framework based on blockchain provided by an embodiment of the present invention. As shown in the figure, the embodiment of the present application provides a real-name digital identity management signature device based on blockchain, including:
[0114] at least one processor; and,
[0115] a memory communicatively connected to the at least one processor; wherein,
[0116] The memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to:
[0117] The identity information and security factors are marked by a private key to form a digital signature, wherein the private key and its corresponding public key are generated by a signature client on the signature device;
[0118] The identity identification information and the digital signature are sent to the verification client, so that the verification client obtains the public key stored on the blockchain according to the identity identification information, decrypts the digital signature, and verifies whether the identity identification information and the security factor are legal.
[0119] Fig.14 A schematic diagram of a real-name digital identity management and verification device framework based on blockchain provided by an embodiment of the present invention. As shown in the figure, the embodiment of the present application provides a real-name digital identity management and verification device based on blockchain, including:
[0120] at least one processor; and,
[0121] a memory communicatively connected to the at least one processor; wherein,
[0122] The memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to:
[0123] Receiving identity information and a digital signature sent by a signing client, wherein the digital signature is formed by the signing client marking the identity information and the security factor through a private key;
[0124] The public key stored on the blockchain is obtained according to the identity identification information, and the digital signature is decrypted to verify whether the identity identification information and the security factor are legal.
[0125] Each embodiment in this application is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the device and medium embodiments, since they are basically similar to the method embodiments, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiments.
[0126] The devices and media provided in the embodiments of the present application correspond one-to-one to the methods. Therefore, the devices and media also have similar beneficial technical effects as the corresponding methods. Since the beneficial technical effects of the methods have been described in detail above, the beneficial technical effects of the devices and media will not be repeated here.
[0127] Those skilled in the art will appreciate that embodiments of the present invention may be provided as methods, systems, or computer program products. Therefore, the present invention may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the present invention may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.
[0128] The present invention is a method, device (system), and computer program product according to an embodiment of the present invention.
[0129] The flowcharts and / or block diagrams of the products are described. It should be understood that each process and / or block in the flowcharts and / or block diagrams, as well as the combination of processes and / or blocks in the flowcharts and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowcharts. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.
[0130] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.
[0131] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.
[0132] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.
[0133] The memory may include non-permanent storage in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. The memory is an example of a computer-readable medium.
[0134] Computer readable media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. Information can be computer readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include temporary computer readable media (transitory media), such as modulated data signals and carrier waves.
[0135] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.
[0136] The above is only an embodiment of the present application and is not intended to limit the present application. For those skilled in the art, the present application may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims of the present application.
Claims
1. A real-name digital identity management method based on blockchain, characterized in that: include: The identity information and security factors are marked by a private key to form a digital signature, and the private key and its corresponding public key are generated by the signing client; Sending the identity information and the digital signature to the verification client, so that the verification client obtains the public key stored on the blockchain according to the identity information, decrypts the digital signature, and verifies whether the identity information and the security factor are legal; The step of marking the identity information and the security factor by using a private key to form a digital signature, and sending the identity information and the digital signature to the verification client comprises: The signing client performs a hash operation on the business content to obtain a hash value of the business content; The signing client encrypts the identity information, the security factor and the hash value of the business content by using a private key to form a digital signature, and sends the business content, the identity information and the digital signature to the verification client; Receiving identity information and a digital signature sent by a signing client, wherein the digital signature is formed by the signing client marking the identity information and the security factor through a private key; Obtaining the public key stored on the blockchain according to the identity information, decrypting the digital signature to verify whether the identity information and the security factor are legal; The verifying whether the identity identification information and the security factor are legal includes: Compare the household registration information and biometric information in the identity information with the household registration information and biometric information corresponding to the identity information pre-stored in the blockchain to determine whether the identity information is legal; The verifying whether the identity identification information and the security factor are legal includes: Determine the number and type of security factors decrypted from the digital signature, where the type of security factors includes at least one or more of a timestamp, a sequence number, and a special prompt; Comparing the security factor with the security factor associated with the identity information in the blockchain to determine whether the security factor is legitimate; Decrypting the digital signature to verify whether the identity information and the security factor are legal includes: The verification client calculates the business content sent by the signing client according to the hash algorithm agreed upon by both parties to obtain a hash value of the business content; The verification client uses the public key to decrypt the digital signature to obtain a hash value of another business content; Compare the hash values of two business contents to see if they are consistent, to determine whether the business contents have been tampered with; The step of obtaining a public key stored on the blockchain according to the identity identification information and storing the public key in the blockchain in advance includes: The ID number in the user's identity information, the public key generated for the user by the specified cryptographic algorithm, and the name of the specified cryptographic algorithm are sent to the blockchain for real-name authentication, so that the blockchain saves the user's identity information, public key and the name of the cryptographic algorithm after the authentication, wherein other information in the identity information is stored outside the blockchain.
2. The method according to claim 1, characterized in that The identity information and security factors are marked by a private key to form a digital signature, including: The signing client determines an asymmetric encryption algorithm for forming the digital signature according to a business scenario.
3. A real-name digital identity management signature device based on blockchain, characterized in that: at least one processor; as well as, a memory communicatively connected to the at least one processor; wherein, The memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to: The identity information and security factors are marked by a private key to form a digital signature, wherein the private key and its corresponding public key are generated by a signature client on the signature device; Sending the identity information and the digital signature to the verification client, so that the verification client obtains the public key stored on the blockchain according to the identity information, decrypts the digital signature, and verifies whether the identity information and the security factor are legal; The step of marking the identity information and the security factor by using a private key to form a digital signature, and sending the identity information and the digital signature to the verification client comprises: The signing client performs a hash operation on the business content to obtain a hash value of the business content; The signing client encrypts the identity information, the security factor and the hash value of the business content by using a private key to form a digital signature, and sends the business content, the identity information and the digital signature to the verification client; Receiving identity information and a digital signature sent by a signing client, wherein the digital signature is formed by the signing client marking the identity information and the security factor through a private key; Obtaining the public key stored on the blockchain according to the identity information, decrypting the digital signature to verify whether the identity information and the security factor are legal; The verifying whether the identity identification information and the security factor are legal includes: Compare the household registration information and biometric information in the identity information with the household registration information and biometric information corresponding to the identity information pre-stored in the blockchain to determine whether the identity information is legal; The verifying whether the identity identification information and the security factor are legal includes: Determine the number and type of security factors decrypted from the digital signature, where the type of security factors includes at least one or more of a timestamp, a sequence number, and a special prompt; Comparing the security factor with the security factor associated with the identity information in the blockchain to determine whether the security factor is legitimate; Decrypting the digital signature to verify whether the identity information and the security factor are legal includes: The verification client calculates the business content sent by the signing client according to the hash algorithm agreed upon by both parties to obtain a hash value of the business content; The verification client uses the public key to decrypt the digital signature to obtain a hash value of another business content; Compare the hash values of two business contents to see if they are consistent, to determine whether the business contents have been tampered with; The step of obtaining a public key stored on the blockchain according to the identity identification information and storing the public key in the blockchain in advance includes: The ID number in the user's identity information, the public key generated for the user by the specified cryptographic algorithm, and the name of the specified cryptographic algorithm are sent to the blockchain for real-name authentication, so that the blockchain saves the user's identity information, public key and the name of the cryptographic algorithm after the authentication, wherein other information in the identity information is stored outside the blockchain.
4. A real-name digital identity management and verification device based on blockchain, characterized in that: at least one processor; and, a memory communicatively connected to the at least one processor; wherein, The memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to: Receiving identity information and a digital signature sent by a signing client, wherein the digital signature is formed by the signing client marking the identity information and the security factor through a private key; Obtaining the public key stored on the blockchain according to the identity information, decrypting the digital signature to verify whether the identity information and the security factor are legal; The step of marking the identity information and the security factor by using a private key to form a digital signature, and sending the identity information and the digital signature to the verification client comprises: The signing client performs a hash operation on the business content to obtain a hash value of the business content; The signing client encrypts the identity information, the security factor and the hash value of the business content by using a private key to form a digital signature, and sends the business content, the identity information and the digital signature to the verification client; Receiving identity information and a digital signature sent by a signing client, wherein the digital signature is formed by the signing client marking the identity information and the security factor through a private key; Obtaining the public key stored on the blockchain according to the identity information, decrypting the digital signature to verify whether the identity information and the security factor are legal; The verifying whether the identity identification information and the security factor are legal includes: Compare the household registration information and biometric information in the identity information with the household registration information and biometric information corresponding to the identity information pre-stored in the blockchain to determine whether the identity information is legal; The verifying whether the identity identification information and the security factor are legal includes: Determine the number and type of security factors decrypted from the digital signature, where the type of security factors includes at least one or more of a timestamp, a sequence number, and a special prompt; Comparing the security factor with the security factor associated with the identity information in the blockchain to determine whether the security factor is legitimate; Decrypting the digital signature to verify whether the identity information and the security factor are legal includes: The verification client calculates the business content sent by the signing client according to the hash algorithm agreed upon by both parties to obtain a hash value of the business content; The verification client uses the public key to decrypt the digital signature to obtain a hash value of another business content; Compare the hash values of two business contents to see if they are consistent, to determine whether the business contents have been tampered with; The step of obtaining a public key stored on the blockchain according to the identity identification information and storing the public key in the blockchain in advance includes: The ID number in the user's identity information, the public key generated for the user by the specified cryptographic algorithm, and the name of the specified cryptographic algorithm are sent to the blockchain for real-name authentication, so that the blockchain saves the user's identity information, public key and the name of the cryptographic algorithm after the authentication, wherein other information in the identity information is stored outside the blockchain.
Citation Information
Patent Citations
Electronic bank identification method, system and intelligent card adopting the method
CN101101686A
Method and system for identification authentication using biology characteristics
CN101442407A
User identity verification method, apparatus and system based on block chain
CN107579817A
Digital identity verification method, apparatus and system based on block chains
CN107888382A
Encryption communication method and system for blockchain node
CN108768630A
