Certificate verification method and device, equipment, storage medium and program product

Abstract

The invention provides a certificate checking method and device, equipment, a storage medium and a program product, and relates to the field of financial science and technology or other related fields. The method comprises the steps of obtaining a verification request through a verification system, obtaining certificate information to be verified of a user and a user ID, determining encrypted certificate information input by the user on a certificate information chain by using the user ID, determining a public key corresponding to the maintained certificate information of the user by using the user ID based on a pre-maintained hash table, and sending the public key to the user through the verification system. And decrypting the encrypted certificate information by using a public key to obtain decrypted certificate information, comparing the decrypted certificate information with the certificate information to be checked to obtain a comparison result, performing consensus verification on the comparison result to obtain a consensus verification result, and determining a checking result of the checking request based on the consensus verification result and outputting the checking result. According to the method provided by the invention, the reliability and stability of certificate checking are improved, and the business handling efficiency is improved.

Description

TECHNICAL FIELD

[0001] The present application relates to the field of financial technology or other related fields, in particular to a certificate verification method and device, equipment, storage medium and program product. BACKGROUND

[0002] At present, the citizen certificate system is large and diverse, including ID cards, household registration books, retirement certificates, passports and other certificates. In the scenes of government services, financial services, social governance, etc., the demand for cross-institutional and cross-regional certificate information online verification is increasingly frequent, such as bank account opening, loan approval handling, etc. Scenarios rely on efficient and accurate identity verification capabilities.

[0003] The prior art adopts a single central node centralized deployment mode to establish an online networking verification system. When multiple certificate information needs to be verified, the verification request corresponding to each certificate information is processed by the central node of the online networking verification system.

[0004] However, in the single central node centralized deployment mode adopted by the prior art, the user certificate information is more likely to be tampered with or leaked, with a high failure rate, which can easily cause systematic verification errors of user certificate information, reduce business handling efficiency, and further reduce user experience. SUMMARY

[0005] The present application provides a certificate verification method, device, equipment, storage medium and program product to improve the reliability and stability of certificate verification and further improve the business handling efficiency.

[0006] In a first aspect, the present application provides a certificate verification method applied to a verification system, comprising:

[0007] Obtaining a verification request, the verification request including a user ID and user certificate information to be verified; based on the verification request, obtaining encrypted certificate information corresponding to the user ID on the certificate information chain;

[0008] Based on the pre-maintained hash table, determining the public key corresponding to the certificate ID of the certificate information to be verified, decrypting the encrypted certificate information through the public key to obtain decrypted certificate information;

[0009] Comparing the decrypted certificate information with the certificate information to be verified to obtain a comparison result; performing consensus verification on the comparison result to obtain a consensus verification result; determining a verification result of the verification request based on the consensus verification result and outputting.

[0010] In a second aspect, the present application provides a certificate verification device applied to a verification system, comprising:

[0011] The acquisition module is configured to acquire a verification request, the verification request comprising a user ID and certificate information to be verified by the user; based on the verification request, encrypted certificate information corresponding to the user ID is acquired on a certificate information chain;

[0012] The processing module is configured to determine, based on a pre-maintained hash table, a public key corresponding to a certificate ID of the certificate information to be verified, decrypt the encrypted certificate information by using the public key, and obtain decrypted certificate information.

[0013] The processing module is further configured to compare the decrypted certificate information with the certificate information to be verified, obtain a comparison result, perform consensus verification on the comparison result, obtain a consensus verification result, and determine a verification result of the verification request based on the consensus verification result and output the verification result.

[0014] In a third aspect, an electronic device is provided, comprising a memory and a processor.

[0015] The memory stores computer-executable instructions.

[0016] The processor executes the computer-executable instructions stored in the memory, so that the processor executes the first aspect and / or various possible implementation manners of the first aspect.

[0017] In a fourth aspect, a computer-readable storage medium is provided, and the computer-readable storage medium stores computer-executable instructions. When the computer-executable instructions are executed by a processor, the computer-executable instructions are used to implement the first aspect and / or various possible implementation manners of the first aspect.

[0018] In a fifth aspect, a computer program product is provided, comprising a computer program. When the computer program is executed by a processor, the computer program implements the first aspect and / or various possible implementation manners of the first aspect.

[0019] The certificate verification method, device, equipment, storage medium and program product provided by the present application obtain a verification request by using a verification system, obtain certificate information to be verified by a user who handles a business and a user ID, determine encrypted certificate information of the user entered on a certificate information chain by using the user ID, determine a public key corresponding to the certificate information of the user maintained by using the user ID based on a pre-maintained hash table, decrypt the encrypted certificate information by using the public key, obtain decrypted certificate information, compare the decrypted certificate information with the certificate information to be verified, obtain a comparison result, perform consensus verification on the comparison result, obtain a consensus verification result, and determine a verification result of the verification request based on the consensus verification result and output the verification result. The present application improves the reliability and stability of certificate verification, and further improves the efficiency of business handling. BRIEF DESCRIPTION OF DRAWINGS

[0020] The accompanying drawings, which are incorporated herein and form a part of the specification, illustrate embodiments consistent with the present application and, together with the description, further serve to explain the principles of the application.

[0021] Figure 1 A flowchart of the method for identity verification provided by the present application is shown in the figure.

[0022] Figure 2 A schematic diagram of dynamic node exit provided by the present application is shown in the figure.

[0023] Figure 3 A schematic diagram of dynamic node join provided by the present application is shown in the figure.

[0024] Figure 4 A structural schematic diagram of the identity verification device provided by the present application is shown in the figure.

[0025] Figure 5 A structural schematic diagram of the electronic device provided by the present application is shown in the figure.

[0026] The specific embodiments of the present application have been shown in the above-described figures, and will be described in more detail hereinafter. These figures and the written description are not intended to limit the scope of the inventive concepts in any way, but to illustrate the inventive concepts to those skilled in the art by reference to specific embodiments. DETAILED DESCRIPTION

[0027] The exemplary embodiments will be described in detail herein with reference to the attached drawings. Unless otherwise specified, the same numbers refer to the same elements throughout the drawings and the description. The following description of the exemplary embodiments is not representative of all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with some aspects of the present application as detailed in the appended claims.

[0028] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data for analysis, stored data, displayed data, etc.) involved in the present application are all information and data authorized by the user or authorized by all parties, and the collection, storage, use, processing, transmission, provision, disclosure and application of related data comply with relevant laws, regulations and standards of relevant countries and regions, necessary security measures are taken, public order and good customs are not violated, and appropriate operation portals are provided for users to choose authorization or refusal.

[0029] And the present application relates to the big data analysis of user information (including but not limited to personal biological characteristics, identity data, consumption data, asset data, electronic terminal operation data, etc.), and the automatic decision is made by using artificial intelligence technology, the technical scheme is made based on the automatic decision result, the operation entrance is provided for the user, the user selects to agree or refuse the automatic decision result;If the user chooses to refuse, enter the expert decision process.

[0030] It should be noted that the certificate checking method, device, equipment, storage medium and program product provided by the present application can be used in the field of financial technology or other related fields, and can also be used in any field other than the field of financial technology or other related fields. The application field of the certificate checking method, device, equipment, storage medium and program product in the present application is not limited.

[0031] At present, the user certificate system is large and various, such as ID card, household booklet, retirement certificate, passport and other certificates. In the scenes of government service, financial business, social governance and the like, the demand for cross-institutional and cross-regional certificate information networking verification is increasing frequently, for example, bank account opening, loan approval and the like depend on efficient and accurate identity verification capability.

[0032] The prior art adopts a centralized architecture to build an online networking verification system. When the user certificate information needs to be networked and verified, the certificate information submitted by the user is compared with the input certificate information through a single central node, so as to feed back the notification of whether the certificate information passes according to the comparison result.

[0033] However, the online networking verification system of the prior art has weak information security protection in the centralized deployment mode, and the data is more likely to be tampered with or leaked, which brings security risks to user privacy. When the central node is down or attacked, it is easy to cause large-area verification service exception or paralysis, increase the system failure probability, and reduce the security and reliability of the certificate networking verification.

[0034] In addition, the online networking verification system of the prior art has insufficient processing capacity in high-load scenarios, and is difficult to cope with sudden traffic (such as financial business peak period, government centralized handling period). In high-concurrency scenarios, processing delay or service interruption may occur, for example, the bank may cause verification timeout due to high load of the central system during the peak period of account opening, affecting the business handling efficiency.

[0035] The certificate checking method, device, equipment, storage medium and program product provided by the present application aim to solve the above technical problems of the prior art.

[0036] The method for checking the certificate provided by the application, through the business personnel, the certificate information to be input by the user is input into the checking system, so as to check the authenticity of the certificate information to be input by the checking system, generate the public key and the private key after checking, upload the certificate information encrypted by using the private key to the block chain, obtain the certificate information chain, and maintain the public key to the hash table. After that, when the user comes to handle the business, the business personnel input the certificate information to be checked by the user into the checking system, so as to use the public key corresponding to the user to decrypt the certificate information by the checking system, obtain the decrypted certificate information, compare the decrypted certificate information with the certificate information to be checked, obtain the comparison result, broadcast the comparison result to 2f copy nodes in the checking system, obtain f+1 consensus verification result indicating that the comparison is correct, determine that the consensus is reached, and output the result of checking without error. If the checking result is not output within a predetermined time period, the comparison result is broadcast to 3f+1 copy nodes in the checking system, and the comparison result of the predetermined number of comparison results is verified by 3f+1 copy nodes. If the consensus verification of the predetermined number of comparison results is completed, the 3f+1 copy nodes are retained, the remaining nodes in the checking system are determined as fault nodes, the dynamic exit process of the fault nodes is executed, and when the fault nodes are checked normally or repaired normally, the dynamic joining process of the new nodes is executed. The application improves the reliability and stability of the certificate checking, further improves the business handling efficiency, and enhances the user experience.

[0037] The technical solutions of the application and how the technical solutions of the application solve the above technical problems will be described in detail below with specific embodiments. The following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments. The embodiments of the application will be described below with reference to the drawings.

[0038] Figure 1 The flowchart of the method for checking the certificate provided by the application is shown in Figure 1 The method comprises the following steps.

[0039] S101, obtain a checking request, the checking request comprising a user ID and certificate information to be checked by the user; based on the checking request, obtain the encrypted certificate information corresponding to the user ID on the certificate information chain.

[0040] More specifically, before obtaining the verification request, the business personnel information and the user's to-be-entered certificate information are obtained by the verification system; the current business personnel is authenticated based on the business personnel information; after the authentication passes, the authenticity of the to-be-entered certificate information is verified; and when the authenticity verification result indicates that the verification is correct, the public key and the private key are generated based on the to-be-entered certificate information; the to-be-entered certificate information is encrypted using the private key, the encrypted certificate information is uploaded to the blockchain to generate a certificate information chain; and the user ID is associated with the public key and uploaded to a hash table to obtain a pre-maintained hash table.

[0041] Optionally, the business personnel information includes but is not limited to the business personnel's work number and password.

[0042] In a possible embodiment, when the business personnel handles a business for a customer, the business personnel first inputs the work number and password, so as to verify the input work number and password by the verification system; after the verification passes, the customer's to-be-entered certificate information input by the business personnel is received, and the to-be-entered certificate information is submitted to an authoritative institution for authenticity verification; when the authenticity verification result indicates that the verification is correct, the public key and the private key are generated. Then the certificate information is encrypted using the private key and uploaded to the blockchain to obtain a certificate information chain, and the user ID is associated with the public key and stored in a hash table, so that in subsequent verification of the customer's identity by other institutions, the encrypted certificate information can be directly obtained from the certificate information chain and decrypted for comparison through the public key.

[0043] The embodiment guarantees the legality and security of the entered certificate information from the source by authenticating the business personnel and verifying the authenticity of the certificate after the authentication, thereby reducing the information leakage probability and improving the reliability and stability of the certificate verification process.

[0044] Optionally, after obtaining the verification request, it is determined whether the continuous request number of the verification request exceeds a preset threshold; when it is determined that the preset threshold is exceeded, flow limiting is triggered, and a request queuing prompt information is output.

[0045] The embodiment sets a continuous request threshold for the request quantity of the verification request, and when the current certificate verification request continuous request number exceeds the preset threshold, in order to prevent the same verification request from abnormally frequently initiating the verification request behavior, the verification system starts a flow limiting mechanism to feed back a queuing prompt information to the verification request, so as to avoid the verification system from collapsing or malfunctioning due to the abnormal request behavior, improve the reliability and stability of the verification process, and prioritize the processing of the subsequent request to improve the verification efficiency.

[0046] S102, based on the pre-maintained hash table, determine the public key corresponding to the certificate ID of the to-be-verified certificate information, decrypt the encrypted certificate information through the public key, and obtain the decrypted certificate information.

[0047] More specifically, the verification system obtains the public key associated with the user ID based on a pre-maintained hash table, and uses the public key to decrypt the encrypted document information obtained in step S101 to obtain the decrypted document information.

[0048] S103. Compare the decrypted document information with the document information to be verified to obtain the comparison result; perform consensus verification on the comparison result to obtain the consensus verification result; determine the verification result of the verification request based on the consensus verification result and output it.

[0049] More specifically, the consensus verification of the comparison results includes: broadcasting the comparison results to 2f replica nodes in the verification system so that each of the 2f replica nodes can perform consensus verification of the comparison results; obtaining the consensus verification results fed back by the 2f replica nodes; if at least f+1 consensus verification results indicate that the comparison is correct, then consensus is determined to be reached; otherwise, consensus is determined to be not reached.

[0050] In one possible embodiment, the verification system compares the decrypted document information with the document information to be verified, obtaining a comparison result (e.g., the comparison result is that the information matches). Based on a verification system with a total of 40 nodes and f=10, 2f replica nodes (i.e., 20 replica nodes) are determined, and the comparison result is broadcast to these 20 replica nodes so that they can verify the information matching result and provide feedback. If the verification system receives verification results indicating that the comparison is correct from at least f+1 (i.e., 11) replica nodes, a consensus is reached. Based on the consensus result, the verification is confirmed to be correct, and a notification message indicating that the verification is correct is output.

[0051] This embodiment uses a distributed consensus mechanism with 2f replica nodes to achieve consensus even when there are replica nodes with incorrect feedback comparisons. This improves the fault tolerance of the verification system when processing verification requests normally, and helps to improve the efficiency and accuracy of document verification.

[0052] Optionally, after the consensus verification of the comparison results, if no verification result of the verification request is output within a preset time period, the number of replica nodes is updated to 3f+1, so that the comparison results corresponding to the verification request can be verified by the 3f+1 replica nodes; after the 3f+1 replica nodes complete the consensus verification of the preset number of verification requests, at least one faulty node is identified and the faulty node is dynamically removed from the verification system; the replica nodes that performed the consensus verification are restored to 2f replica nodes, where the restored 2f replica nodes are nodes among the 3f+1 replica nodes, and 3f+1 does not exceed the total number of nodes.

[0053] In one possible embodiment, after a business user initiates a verification request, if no verification result is received from the terminal device operated by the business user within a preset time period, then 3f+1 replica nodes are used to perform consensus verification on the comparison result of the verification system. For example, in a verification system with a total of 40 nodes and f=10, 3f+1 replica nodes (i.e., 31 replica nodes) are determined, and the comparison result is broadcast to these 31 replica nodes so that they can verify the consistent comparison result and provide feedback. If the verification system receives verification results indicating that the comparison is correct from at least 2f+1 (i.e., 21) replica nodes, then consensus is reached. Based on the consensus result, the verification is confirmed to be correct, and a notification message indicating that the verification is correct is output. Then, the above 3f+1 replica nodes continue to process verification requests continuously until the 3f+1 replica nodes have completed the consensus verification corresponding to the preset number of verification requests. Then, 2f replica nodes are selected from the above 3f+1 replica nodes, and the subsequent consensus verification processing is performed using the 2f replica nodes.

[0054] In one possible embodiment, the above-mentioned 3f+1 replica nodes continue to process verification requests continuously until the current switch to 3f+1 replica nodes has completed the consensus verification corresponding to a preset number of verification requests. Then, the nodes in the verification system other than the above-mentioned 3f+1 replica nodes are identified as faulty nodes and removed from the verification system.

[0055] In one possible embodiment, the consensus verification mode using 2f replica nodes is the normal mode. If no verification result is output for a verification request within a preset time period, the verification system is determined to be faulty. All replica nodes of the verification system are then controlled to enter fault mode. In fault mode, 3f+1 replica nodes are used for consensus communication. After processing a preset number of verification requests in fault mode, 2f replica nodes are selected from the aforementioned 3f+1 replica nodes and switched to normal mode. If switching to normal mode is not possible at this time, nodes other than the 3f+1 replica nodes are identified as faulty nodes, and a dynamic protocol is used to remove the faulty nodes from the system. After the faulty nodes recover, they are added back as new nodes.

[0056] In this embodiment, when using 2f replica nodes for consensus verification, if no consensus verification result is returned within a preset time period, the system dynamically switches to a fault mode using 3f+1 replica nodes for consensus verification. When the 3f+1 replica nodes complete the consensus verification of a preset number of verification requests, it is determined that the 3f+1 replica nodes can perform consensus verification normally. At this time, the remaining nodes are identified as faulty nodes and exit. Simultaneously, 2f replica nodes are selected from the 3f+1 replica nodes to perform subsequent consensus verification processing. This ensures the continuity and robustness of the verification system in performing document verification when there are abnormal nodes, helps to improve the timeliness and reliability of the verification results, and further improves business processing efficiency and user experience.

[0057] Optionally, consensus verification of the comparison results corresponding to the verification request is performed by 3f+1 replica nodes. Specifically, this includes: broadcasting the comparison results to 3f+1 replica nodes in the verification system, so that each of the 3f+1 replica nodes performs consensus verification of the comparison results; and determining that consensus has been reached when at least 2f+1 consensus verification results indicate that the comparison is correct.

[0058] In this embodiment, when the verification system is faulty, a distributed consensus mechanism of 3f+1 replica nodes is adopted. Even if there are replica nodes with incorrect feedback comparisons, a consensus result can still be obtained, which improves the fault tolerance in scenarios with abnormal / faulty nodes and helps to improve the accuracy and reliability of document verification.

[0059] Optionally, the faulty node can dynamically exit the verification system, specifically by: broadcasting exit information to 3f+1 replica nodes through the faulty node, so that the 3f+1 replica nodes verify the signature of the faulty node after receiving the exit information, and broadcast a confirmation exit information after successful verification; broadcasting exit completion information when any replica node receives f+1 confirmation exit information; sending an agreement to exit notification to the faulty node when any replica node receives f+1 exit completion information; and exiting the verification system when the faulty node receives f+1 agreement to exit notifications.

[0060] Optionally, a master node is elected randomly from all nodes in the verification system, with the remaining nodes serving as slave nodes. For example, in this embodiment, the master node number is determined based on the total number of nodes and the current system time; that is, the master node number is the remainder of the current system time divided by the total number of nodes.

[0061] Optionally, when a node joins or leaves, the corresponding node is added or removed from the node information table, and the number of each node in the system is updated accordingly. Then, a new master node is elected based on the updated total number of nodes. After the master node election is completed, the system can enter normal mode for consensus verification.

[0062] In one possible embodiment, Figure 2 A schematic diagram of the dynamic node exit provided in this application is shown below. Figure 2 As shown, f=1. The faulty node broadcasts an exit message to 3f+1 replica nodes (i.e., the master node, slave node 1, slave node 2, and slave node 3). Upon receiving the exit message, the master node, slave node 1, slave node 2, and slave node 3 verify the faulty node's signature and broadcast a confirmation exit message upon successful verification. Taking slave node 1 as an example, when slave node 1 receives at least f+1 (i.e., 2) confirmation exit messages, it broadcasts an exit completion message. The master node, slave node 2, and slave node 3 broadcast confirmation exit messages in the same way. Continuing with slave node 1 as an example, when slave node 1 receives at least f+1 exit completion messages, it sends an agreement to exit to the faulty node. The master node, slave node 2, and slave node 3 broadcast exit completion messages in the same way. When the faulty node receives at least f+1 agreement to exit messages, it exits the verification system. After any node confirms successful verification, it modifies its node configuration information.

[0063] This embodiment controls the dynamic exit of faulty nodes from the system, avoiding the system's inability to return verification results within a preset time period due to the use of faulty nodes. This further avoids frequent switching between normal and fault modes, improving the stability and reliability of document verification and enhancing the efficiency and robustness of the verification system.

[0064] Optionally, after the faulty node is repaired, the repaired new node sends a join message to the master node among the 3f+1 replica nodes, so that the master node verifies the signature of the new node. After successful verification, it broadcasts a request for verification information. Each of the 3f+1 replica nodes performs signature verification on the master node and the new node in sequence, and broadcasts a verification success message after successful verification. When any slave node or master node receives f+1 verification success messages, it broadcasts confirmation of the new node's addition information, changes the node configuration information, and sends the changed node configuration information to the new node. When the new node receives f+1 confirmation messages of the new node's addition information and the node configuration information, it joins the verification system.

[0065] In one possible embodiment, Figure 3 A schematic diagram added to the dynamic nodes provided in this application, such as... Figure 3As shown, f=1. The new node broadcasts its joining information to the master node among the 3f+1 replica nodes. This allows the master node to verify the new node's signature upon receiving the joining information. After successful verification, it broadcasts a verification request to each of the 3f+1 replica nodes (i.e., slave node 1, slave node 2, and slave node 3). Taking slave node 1 as an example, upon receiving the verification request, slave node 1 sequentially verifies the signature of both the master node and the new node. After successful verification, it broadcasts the verification pass information to the master node, slave node 2, and slave node 3. The method for slave node 2 and slave node 3 to broadcast the verification pass information is similar. Taking the master node as an example, after receiving at least two verification pass messages, the master node broadcasts confirmation of the new information and modifies its node configuration information, sending the modified node configuration information to the new node. The method for slave node 1, slave node 2, and slave node 3 to broadcast the verification pass information is similar. When the new node receives at least two node configuration messages and confirmation of the new information, it joins the verification system.

[0066] This embodiment controls the access process of new nodes, making the process of adding new nodes independent of document verification, thereby improving the stability and reliability of document verification. At the same time, it enhances the verification of new nodes, improves the legality of new nodes and data consistency, and helps to improve the dynamic expansion capability and fault response capability of the verification system.

[0067] The document verification method provided in this application improves the security of document information by encrypting and storing it, and enhances the reliability of verification results by performing consensus verification on the comparison results. At the same time, it solves the problem that the existing technology cannot meet the verification needs of diverse documents, expands the application scenarios, and improves the efficiency of business processing.

[0068] Figure 4 A schematic diagram of the document verification device provided in this application is shown below. Figure 4 As shown, the document verification device 40 provided in this embodiment includes:

[0069] The acquisition module 401 is used to acquire a verification request, which includes a user ID and the user's identification document information to be verified; based on the verification request, the encrypted identification document information corresponding to the user ID is acquired from the identification document information chain;

[0070] The processing module 402 is used to determine the public key corresponding to the document ID of the document information to be verified based on a pre-maintained hash table, and to decrypt the encrypted document information using the public key to obtain the decrypted document information.

[0071] The processing module 402 is also used to compare the decrypted document information with the document information to be verified to obtain the comparison result; to perform consensus verification on the comparison result to obtain the consensus verification result; and to determine and output the verification result of the verification request based on the consensus verification result.

[0072] Optionally, the processing module 402 is further configured to broadcast the comparison results to the 2f replica nodes in the verification system, so that the 2f replica nodes can perform consensus verification by comparing the comparison results respectively.

[0073] Obtain consensus verification results from 2f replica nodes. If at least f+1 consensus verification results indicate that the comparison is correct, then consensus is determined to be achieved; otherwise, consensus is determined to be not achieved.

[0074] Optionally, the processing module 402 is further configured to update the number of replica nodes to 3f+1 if no verification result of the verification request is output within a preset time period after the consensus verification of the comparison result. This is so that the comparison result corresponding to the verification request can be verified through the 3f+1 replica nodes.

[0075] After 3f+1 replica nodes complete the consensus verification corresponding to a preset number of verification requests, at least one faulty node is identified and the faulty node is dynamically removed from the verification system.

[0076] The replica nodes that performed consensus verification will be restored to 2f replica nodes. The restored 2f replica nodes are nodes in the 3f+1 replica nodes, and 3f+1 does not exceed the total number of nodes.

[0077] Optionally, the processing module 402 is also used to broadcast the comparison results to the 3f+1 replica nodes in the verification system, so that the 3f+1 replica nodes can perform consensus verification by comparing the comparison results respectively.

[0078] Consensus is confirmed when at least 2f+1 consensus verification results are received indicating that the comparison is correct.

[0079] Optionally, the processing module 402 is also used to broadcast exit information to the 3f+1 replica nodes through the faulty node, so that the 3f+1 replica nodes verify the signature of the faulty node after receiving the exit information, and broadcast a confirmation of exit information after the verification is successful.

[0080] When any replica node receives f+1 confirmation messages for exit, it broadcasts an exit completion message.

[0081] When any replica node receives f+1 exit completion messages, it sends an exit consent notification to the faulty node.

[0082] The system exits when the faulty node receives f+1 consent exit notifications.

[0083] Optionally, the processing module 402 is also used to send the repaired new node to the master node among the 3f+1 replica nodes after the faulty node is repaired to normal, so that the master node can verify the signature of the new node and broadcast a request for verification information after the verification is successful.

[0084] The master node and the new node are signed and verified sequentially by each of the slave nodes in the 3f+1 replica nodes, and the verification is broadcast after the verification is successful.

[0085] When any slave node or master node receives f+1 verification passes, it broadcasts confirmation of the new information, changes the node configuration information, and sends the changed node configuration information to the new node.

[0086] When a new node receives f+1 confirmation messages for new additions and node configuration information, it is added to the verification system.

[0087] Optionally, the processing module 402 is also used to obtain business personnel information and user identification information to be entered before obtaining the verification request; and to verify the identity of the current business personnel based on the business personnel information;

[0088] After successful verification, the authenticity of the document information to be entered is checked; and when the authenticity check result indicates that the verification is correct, a public key and a private key are generated based on the document information to be entered.

[0089] The private key is used to encrypt the document information to be entered, and the encrypted document information is uploaded to the blockchain to generate a document information chain; the user ID is associated with the public key and uploaded to a hash table to obtain a pre-maintained hash table.

[0090] Optionally, the processing module 402 is further configured to determine, after obtaining the verification request, whether the number of consecutive requests for the verification request exceeds a preset threshold;

[0091] When the threshold is exceeded, rate limiting is triggered, and a request queuing prompt message is output.

[0092] The document verification device provided in this embodiment can execute the method provided in the above method embodiment. Its implementation principle and technical effect are similar, and will not be described in detail here.

[0093] Figure 5 A schematic diagram of the structure of the electronic device provided in this application. Figure 5 As shown, the electronic device 50 provided in this embodiment includes at least one processor 501 and a memory 502. Optionally, the device 50 further includes a communication component 503. The processor 501, memory 502, and communication component 503 are connected via a bus 504.

[0094] In a specific implementation, at least one processor 501 executes computer execution instructions stored in memory 502, causing at least one processor 501 to perform the above-described method.

[0095] The specific implementation process of processor 501 can be found in the above method embodiments, and its implementation principle and technical effect are similar. It will not be repeated here.

[0096] In the above embodiments, it should be understood that the processor can be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), etc. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in this invention can be directly implemented by a hardware processor, or implemented by a combination of hardware and software modules within the processor.

[0097] The memory may include random access memory (RAM) and may also include non-volatile memory (NVM), such as at least one disk storage device.

[0098] The bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. Buses can be categorized as address buses, data buses, control buses, etc. For ease of illustration, the buses shown in the accompanying drawings are not limited to a single bus or a single type of bus.

[0099] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the above-described method.

[0100] This application also provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, implement the above-described method.

[0101] The aforementioned readable storage medium can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk. The readable storage medium can be any available medium accessible to a general-purpose or special-purpose computer.

[0102] An exemplary readable storage medium is coupled to a processor, enabling the processor to read information from and write information to the readable storage medium. Of course, the readable storage medium can also be a component of the processor. The processor and the readable storage medium can reside in an Application Specific Integrated Circuit (ASIC). Alternatively, the processor and the readable storage medium can exist as discrete components in the device.

[0103] It should be noted that, for the sake of simplicity, the foregoing method embodiments are all described as a series of actions. However, those skilled in the art should understand that this application is not limited to the described order of actions, as some steps may be performed in other orders or simultaneously according to this application. Furthermore, those skilled in the art should also understand that the embodiments described in the specification are all optional embodiments, and the actions and modules involved are not necessarily essential to this application.

[0104] It should be further noted that although the steps in the flowchart are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowchart may include multiple sub-steps or multiple stages. These sub-steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these sub-steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the sub-steps or stages of other steps.

[0105] It should be understood that the above-described device embodiments are merely illustrative, and the device of this application can also be implemented in other ways. For example, the division of units / modules in the above embodiments is only a logical functional division, and there may be other division methods in actual implementation. For example, multiple units, modules, or components may be combined, or integrated into another system, or some features may be ignored or not executed.

[0106] Furthermore, unless otherwise specified, the functional units / modules in the various embodiments of this application can be integrated into one unit / module, or each unit / module can exist physically separately, or two or more units / modules can be integrated together. The integrated units / modules described above can be implemented in hardware or as software program modules.

[0107] When integrated units / modules are implemented in hardware, the hardware can be digital circuits, analog circuits, etc. The physical implementation of the hardware structure includes, but is not limited to, transistors, memristors, etc. Unless otherwise specified, the processor can be any suitable hardware processor, such as a CPU, GPU, FPGA, DSP, and ASIC, etc. Unless otherwise specified, the storage unit can be any suitable magnetic or magneto-optical storage medium, such as Resistive Random Access Memory (RRAM), Dynamic Random Access Memory (DRAM), Static Random Access Memory (SRAM), Enhanced Dynamic Random Access Memory (EDRAM), High-Bandwidth Memory (HBM), Hybrid Memory Cube (HMC), etc.

[0108] If the integrated unit / module is implemented as a software program module and sold or used as an independent product, it can be stored in a computer-readable storage device (CMD). Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a memory and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of the various embodiments of this application. The aforementioned memory includes various media capable of storing program code, such as a USB flash drive, read-only memory (ROM), random access memory (RAM), portable hard drive, magnetic disk, or optical disk.

[0109] In the above embodiments, the descriptions of each embodiment have their own emphasis. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions of other embodiments. The technical features of the above embodiments can be combined arbitrarily. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as the combination of these technical features does not contradict each other, it should be considered within the scope of this specification.

[0110] Other embodiments of this application will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of this application that follow the general principles of this application and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this application are indicated by the following claims.

[0111] It should be understood that this application is not limited to the precise structure described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this application is limited only by the appended claims.

Claims

1. A method for verifying identification documents, characterized in that, Applied to verification systems, including: Obtain a verification request, which includes a user ID and the user's identification document information to be verified; based on the verification request, obtain the encrypted identification document information corresponding to the user ID from the identification document information chain; Based on a pre-maintained hash table, the public key corresponding to the document ID of the document information to be verified is determined, and the encrypted document information is decrypted using the public key to obtain the decrypted document information. The decrypted document information is compared with the document information to be verified to obtain a comparison result; the comparison result is verified by consensus to obtain a consensus verification result; the verification result of the verification request is determined based on the consensus verification result and output.

2. The method according to claim 1, characterized in that, Consensus verification of the comparison results specifically includes: The comparison results are broadcast to 2f replica nodes in the verification system so that the 2f replica nodes can perform consensus verification on the comparison results respectively. Obtain the consensus verification results fed back by the 2f replica nodes. If at least f+1 consensus verification results indicate that the comparison is correct, then it is determined that consensus has been reached; otherwise, it is determined that consensus has not been reached.

3. The method according to claim 1 or 2, characterized in that, The method further includes: After the comparison results are verified by consensus, if the verification result of the verification request is not output within a preset time period, the number of replica nodes is updated to 3f+1, so that the comparison result corresponding to the verification request can be verified by consensus through 3f+1 replica nodes. After the 3f+1 replica nodes complete the consensus verification corresponding to a preset number of verification requests, at least one faulty node is identified, and the faulty node is dynamically removed from the verification system. The replica nodes that performed consensus verification are restored to 2f replica nodes, wherein the restored 2f replica nodes are nodes among the 3f+1 replica nodes, and the 3f+1 does not exceed the total number of nodes.

4. The method according to claim 3, characterized in that, Consensus verification of the comparison results corresponding to the verification request is performed using 3f+1 replica nodes, specifically including: By broadcasting the comparison results to the 3f+1 replica nodes in the verification system, the 3f+1 replica nodes can perform consensus verification on the comparison results respectively. Consensus is confirmed when at least 2f+1 consensus verification results are received indicating that the comparison is correct.

5. The method according to claim 3, characterized in that, Dynamically removing the faulty node from the verification system specifically includes: The faulty node broadcasts an exit message to 3f+1 replica nodes, so that the 3f+1 replica nodes, upon receiving the exit message, verify the signature of the faulty node and broadcast a confirmation of the exit message after successful verification. When any replica node receives f+1 confirmation messages for exit, it broadcasts an exit completion message. When any replica node receives f+1 exit completion messages, it sends an exit consent notification to the faulty node. The system exits when the faulty node receives f+1 consent exit notifications.

6. The method according to claim 3, characterized in that, Also includes: After the faulty node is repaired, the repaired new node sends a join message to the master node among the 3f+1 replica nodes, so that the master node can verify the signature of the new node. After the verification is successful, it broadcasts a request for verification information. The master node and the new node are sequentially signed and verified by each of the slave nodes in the 3f+1 replica nodes, and a verification success message is broadcast after the verification is successful. When any slave node or master node receives f+1 verification passes, it broadcasts confirmation of the new information, changes the node configuration information, and sends the changed node configuration information to the new node. The new node is added to the verification system when it receives f+1 confirmation messages and node configuration information.

7. The method according to claim 1, characterized in that, Also includes: Before obtaining the verification request, obtain the business personnel information and the user's identification document information to be entered; The identity of the current business personnel is verified based on the aforementioned business personnel information; After verification, the authenticity of the document information to be entered is checked. And when the authenticity verification result indicates that the verification is correct, a public key and a private key are generated based on the document information to be entered; The private key is used to encrypt the document information to be entered, and the encrypted document information is uploaded to the blockchain to generate a document information chain. The user ID is then associated with the public key and uploaded to a hash table to obtain a pre-maintained hash table.

8. The method according to claim 1, characterized in that, Also includes: After obtaining the verification request, determine whether the number of consecutive requests for the verification request exceeds a preset threshold; When the threshold is exceeded, rate limiting is triggered, and a request queuing prompt message is output.

9. A document verification device, characterized in that, Applied to verification systems, including: The acquisition module is used to acquire a verification request, which includes a user ID and the user's identification document information to be verified; based on the verification request, the encrypted identification document information corresponding to the user ID is acquired from the identification document information chain; The processing module is used to determine the public key corresponding to the document ID of the document information to be verified based on a pre-maintained hash table, and to decrypt the encrypted document information using the public key to obtain the decrypted document information. The processing module is further configured to compare the decrypted document information with the document information to be verified to obtain a comparison result; perform consensus verification on the comparison result to obtain a consensus verification result; and determine and output the verification result of the verification request based on the consensus verification result.

10. An electronic device, characterized in that, include: A processor, and a memory communicatively connected to the processor; The memory stores computer-executed instructions; The processor executes computer execution instructions stored in the memory to implement the method as described in any one of claims 1 to 8.

11. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions, which, when executed by a processor, are used to implement the method as described in any one of claims 1 to 8.

12. A computer program product, characterized in that, Includes a computer program that, when executed by a processor, implements the method of any one of claims 1 to 8.

Images