A method for signing and approving enterprise-level digital documents

Abstract

The present invention relates to the field of enterprise-level digital file management, and in particular to a method for signing and approving enterprise-level digital files, the method comprising obtaining the to-be-approved file and the approval process data uploaded by the approval initiator at the credit node, and generating initial transaction data based on the approval process data; sending the to-be-approved file to the corresponding approver in sequence for approval based on the approval process data, generating intermediate transaction data based on the approval process of the approver; and generating final transaction data when the last approver completes the approval. The initial transaction data, intermediate transaction data and final transaction data are all sent to at least three endorsement nodes using the Fabric transaction process through a consensus mechanism. The digital file signing and approval method provided by the present invention is credible, traceable and non-copyable, and can be transferred and used between group enterprises, industries and business alliances.

Description

Technical Field

[0001] The present invention relates to the field of enterprise-level digital file management, and in particular to a method for signing and approving enterprise-level digital files. Background Art

[0002] Enterprise-level digital files such as documents and drawings need to be signed and approved with legal responsibility within the group and between enterprise alliances. The electronic signature approval process in the existing technology mainly uses the local area network to perform electronic authorization through unilateral authorization. Since digital signatures are easy to copy, the authorized use cannot be traced and the credibility is low, the existing electronic signature approval can only be accepted within relatively credible enterprises, and is not suitable for large-scale organizations such as group enterprises, industries and business alliances. Therefore, this field urgently needs a highly reliable, traceable, and non-copyable digital file signing and approval authorization process and method that can be transmitted between group enterprises, industries and business alliances. Summary of the invention

[0003] The purpose of the present invention is to provide a method for signing and approving enterprise-level digital files, thereby solving the above-mentioned problems existing in the prior art.

[0004] In order to achieve the above object, the technical solution adopted by the present invention is as follows:

[0005] A method for signing and approving enterprise-level digital files, the method comprising:

[0006] Obtain the documents to be approved and the approval process data uploaded by the approval initiator on the credit node, and create initial transaction data based on the approval process data; the approval process data includes the unique block hash value of the document to be approved, the approval order and the identity data of the corresponding approver, and the NFT signature of the approval initiator;

[0007] Based on the approval process data, the documents to be approved are sent to corresponding approvers in sequence for approval, and intermediate transaction data is created based on the approval process of the approvers;

[0008] When the last approver completes the approval, the final transaction data is obtained based on the initial transaction data and the intermediate transaction data;

[0009] Among them, the initial transaction data, intermediate transaction data and final transaction data are all sent to at least 3 endorsement nodes using the Fabric transaction process through the consensus mechanism.

[0010] Preferably, the approval process of the approver includes receiving and reviewing the document to be approved, and copying the NFT signature to the corresponding approval area of ​​the document to be approved.

[0011] Preferably, the approval initiator and the signatory both log in to the credit node through biometric identification or account and password login to obtain corresponding user identity authority.

[0012] Preferably, when the approval initiator or approver logs into the credit node for the first time, a unique NFT signature needs to be created.

[0013] Preferably, the NFT signature is generated based on the NFT development protocol ERC-721, including signature content encoding, signer identity information and NFT minting data.

[0014] The beneficial effects of the present invention are:

[0015] The present invention provides a method for signing and approving enterprise-level digital files. Through a decentralized approach, the present invention digitizes signatures and uses digital signatures as indivisible copyrights among enterprise alliances. Each authorized use will be endorsed by at least three endorsement nodes. The signing and approval process, authorization method, and identity data will all be recorded in the block, so that the electronic signed and approved documents have a credible basis for transmission among enterprises, industries, and business alliances. It is also a powerful practice for enterprise-level blockchain signing and approval tracing and problem tracing. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] Figure 1 It is a flowchart of a method for signing and approving enterprise-level digital files in an embodiment of the present invention. DETAILED DESCRIPTION

[0017] In order to make the purpose, technical solution and advantages of the present invention more clearly understood, the present invention is further described in detail below in conjunction with the accompanying drawings. It should be understood that the specific implementation methods described herein are only used to explain the present invention and are not used to limit the present invention.

[0018] like Figure 1 As shown, the present invention provides a method for signing and approving enterprise-level digital files, the method comprising:

[0019] S101, obtain the documents to be approved and the approval process data uploaded by the approval initiator on the credit node, and create initial transaction data based on the approval process data. The approval process data includes the unique block hash value of the documents to be approved, the approval order and the identity data of the corresponding approver, and the NFT signature of the approval initiator.

[0020] S102, based on the approval process data, the documents to be approved are sent to corresponding approvers in sequence for approval, and intermediate transaction data is created based on the approval process of the approvers.

[0021] S103, when the last approver completes the approval, the final transaction data is obtained based on the initial transaction data and the intermediate transaction data.

[0022] Among them, the initial transaction data, intermediate transaction data and final transaction data are all sent to at least 3 endorsement nodes using the Fabric transaction process through the consensus mechanism.

[0023] In this embodiment, the computer needs to access the enterprise network and become a trusted node before it can participate in the exchange of data related to the enterprise network. In the cross-institutional communication scenario, multiple companies that cooperate with each other form an alliance. Only members of the alliance can join the blockchain and participate in work collaboration. Such blockchains that require permission to join are called enterprise networks. Trusted nodes are generally deployed as servers, hosts or workstations within the enterprise or group, which achieve weak centralization to achieve a secure consensus between enterprises. Because of commercial secrets, each node consistently stores the hash of the business data signed by consensus and the data signed by other parties. Access rights are limited to participating electronic documents, and hashes of other data are only stored.

[0024] In this embodiment, users need to verify their identity before they can join the enterprise network through the trusted node. The identity verification method can be a biometric method or an account and password login method. After the identity is verified, the user can log in to the trusted node through the computer client, and the authorized identity can establish or delete data transactions on the trusted node.

[0025] In this embodiment, when the approval initiator or the signatory logs in to the credit node for the first time, it is necessary to generate a unique and traceable identification information - NFT signature on the enterprise-level network blockchain. The signature format is saved in ordinary .jpg format and based on the NFT open protocol (ERC-721) through enterprise services, the information of the "digital content" itself and the casting data are extracted and recorded. These data include: signature content encoding, signer biometric encoding, signer authorization scope, subsidiary signing rights that the digital signature holder can enjoy, NFT casting time, and NFT ownership holder information. At the same time, the NFT signature can also add other additional information as needed.

[0026] In this embodiment, the approval initiator creates or uploads a digital file that needs to be signed and approved. The file may contain documents, drawings, etc. At the same time, the file to be approved also contains one or more approval areas. At the same time, a piece of approval process data containing the approval order is created. The approval process data includes the unique block hash value of the file to be approved, the NFT signature of the approval initiator, and the identity data corresponding to each approval area. The approval initiator creates an initial transaction data when publishing the document. The initial transaction data uses the Fabric transaction process to send the approval process and NFT signature information to at least 3 endorsement nodes through the consensus mechanism.

[0027] In this embodiment, the approver accesses the credit node through identity authorization, receives the document to be approved and reviews it. If the approval is agreed, the NFT signature is copied in the corresponding approval area of ​​the document to be approved, and an intermediate transaction data is created at the same time. The intermediate transaction data uses the Fabric transaction process to send the approval process and NFT signature information to at least 3 endorsement nodes through the consensus mechanism. When all the approvers in the approval process have completed the approval process, the final transaction data is generated. The final transaction data contains the initial transaction data and all intermediate transaction data, that is, the unique block hash value of the document to be approved, the approval process data, and the transaction hash value confirmed by each approver. The final transaction data is also sent to at least 3 endorsement nodes through the consensus mechanism using the Fabric transaction process.

[0028] In this embodiment, Fabric provides a system architecture that executes first, sorts later, and then verifies. This is actually a hybrid model that combines passive replication and active replication. If the contract execution results returned by multiple endorsement nodes are inconsistent, Fabric can identify uncertainty before the data is written, thereby avoiding the writing of inconsistent data. Unlike the traditional blockchain smart contracts that run serially on all nodes, Fabric smart contracts can run in parallel on different endorsement nodes, thereby improving the system transaction throughput. At the same time, as the number of endorsement nodes increases dynamically, the number of contracts that can run in parallel in the system will also increase, thereby achieving a certain degree of scalability. In essence, the traditional blockchain propagates transaction data to all nodes and achieves state consistency by executing on all nodes. Fabric only executes transactions on some trusted endorsement nodes, and then propagates the execution results to all nodes to achieve state consistency.

[0029] The method of the present invention will be further described below in conjunction with another embodiment. The present invention provides a method for signing and approving an enterprise-level digital file, comprising the following steps:

[0030] S201. A computer is connected to an enterprise-level network to become a trusted node and participate in data exchange related to the enterprise network.

[0031] S202. The approval initiator logs in to the client directly through biometric identification to log in to the credit node.

[0032] S203. Create a local area network signature digital copyright with identity authorization - NFT signature.

[0033] S204. Create and upload a file to be approved, which contains one or more approval areas; at the same time, create a process data, which contains a unique block hash value and data transaction node data (derived from the hash value of the credit target identity determined by the approval process); the creator publishes the file and creates a transaction data at the same time, and the transaction data uses the consensus mechanism to send the approval process and NFT signature to at least 3 endorsement nodes using the Fabric transaction process.

[0034] S205. Send to the signatory in sequence according to the customized process.

[0035] S206. The approver accesses the trust node through identity trust, receives the file data and checks it.

[0036] S207. After the approver agrees to approve, the authorized NFT signature will be copied in the approval area and a transaction data will be created. The transaction data will send the approval process and NFT signature to at least 3 endorsement nodes using the Fabric transaction process through the consensus mechanism.

[0037] S208. The document to be approved enters the next approval node that has been determined in the process data created in S204, and executes steps S205, S206, and S207 in sequence, repeating the cycle until all approval nodes complete the approval process.

[0038] S209: After the last approval node completes the approval process of the document to be approved, the final transaction data is generated, and the transaction data is sent to at least 3 endorsement nodes using the Fabric transaction process through the consensus mechanism.

[0039] By adopting the above technical solution disclosed in the present invention, the following beneficial effects are obtained:

[0040] The present invention provides a method for signing and approving enterprise-level digital files. Through a decentralized approach, the present invention digitizes signatures and uses digital signatures as indivisible copyrights among enterprise alliances. Each authorized use will be endorsed by at least three endorsement nodes. The signing and approval process, authorization method, and identity data will all be recorded in the block, so that the electronic signed and approved documents have a credible basis for transmission among enterprises, industries, and business alliances. It is also a powerful practice for enterprise-level blockchain signing and approval tracing and problem tracing.

[0041] The above is only a preferred embodiment of the present invention. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principle of the present invention. These improvements and modifications should also be considered as the scope of protection of the present invention.

Claims

1. A method for signing and approving enterprise-level digital documents, characterized in that: The method comprises: Obtain the documents to be approved and the approval process data uploaded by the approval initiator on the credit node, and create initial transaction data based on the approval process data; the approval process data includes the unique block hash value of the document to be approved, the approval order and the identity data of the corresponding approver, and the NFT signature of the approval initiator; Based on the approval process data, the documents to be approved are sent to corresponding approvers in sequence for approval, and intermediate transaction data is created based on the approval process of the approvers; When the last approver completes the approval, the final transaction data is obtained based on the initial transaction data and the intermediate transaction data; The initial transaction data, intermediate transaction data and final transaction data are all sent to at least three endorsing nodes using the Fabric transaction process through the consensus mechanism; The approval process of the approver includes receiving and reviewing the document to be approved, and copying the NFT signature to the corresponding approval area of ​​the document to be approved; The approval initiator and the signatory both log in to the credit node through biometrics or account password login to obtain the corresponding user identity authority; When the approval initiator or approver logs in to the credit node for the first time, a unique NFT signature needs to be created; The NFT signature is generated based on the NFT development protocol ERC-721, including signature content encoding, signer identity information and NFT minting data.

Images