Form paperless and alliance chain-based informatization document management method

Abstract

The invention provides an informatization document management method based on form paperless and alliance chains, which comprises the following steps: extracting uncompleted informatization documents from an informatization document pool to generate an intelligent auditing task, and determining all auditing nodes and auditing sequences responsible for auditing the informatization documents in different alliance chains; intelligent auditing tasks are distributed to auditing nodes in sequence, the auditing nodes call an auditing rule base and an auditing algorithm assembly to conduct intelligent auditing on the informatization document, and after auditing is completed, cross-chain transmission of auditing results among different alliance chains is achieved through an intelligent contract; according to the method, document cross-department auditing is achieved based on an alliance chain of a MultiChain architecture and an intelligent contract, by combining an artificial intelligence algorithm, the workload of manual auditing is reduced, repeated auditing and submitting work is reduced, the delivery speed of informatization documents is increased, the work efficiency of digital project management is improved, meanwhile, the project management work quality is improved, and the project management efficiency is improved. And audit risks are reduced.

Description

Technical Field

[0001] The present invention relates to the technical field of document digital management, and particularly to an information-based document management method based on form paperless and consortium blockchain. Background Art

[0002] The full life cycle management of a project can reflect the level of project management, and the quality of project management directly affects the quality, progress, safety and other key elements of the project. In the actual construction of a project, the phased results of the project are often reflected in the form of documents. A large number of information-based documents generated are not only important work achievements, but also contribute to the improvement of the organization's project management level.

[0003] In some large enterprises, the number of digital projects per year can reach hundreds, and the delivery of information-based documents is about tens of thousands. The document output units involve design units, construction units, testing units, supervision units, etc. The quality review and process control of a large number of information-based documents require the participation of project delivery parties to ensure the timely and quality delivery of project deliverables, optimize the project construction process, and reduce the acceptance pressure of project construction units. However, at present, the review of information-based documents mostly relies on manual work, resulting in slow review of information-based documents and a large investment in human resources. Summary of the Invention

[0004] In view of this, the purpose of the present invention is to provide an information-based document management method based on form paperless and consortium blockchain to solve the problems of slow review progress and large investment in human resources in the prior art for information-based document review.

[0005] To achieve the above-mentioned invention purpose, the present invention provides an information-based document management method based on form paperless and consortium blockchain, and the method includes:

[0006] S101. Establish an information-based document pool to collect un-reviewed information-based documents, and extract un-reviewed information-based documents from the information-based document pool to generate corresponding intelligent review tasks, where the intelligent review tasks include un-reviewed information-based documents;

[0007] S102. Determine all review nodes that need to review the information-based documents and the review order of each review node according to the intelligent review tasks;

[0008] S103. Assign the intelligent review tasks to the review nodes in the review order, and the review nodes call the review rule library and the review algorithm component to perform intelligent review on the information-based documents;

[0009] S104. After the intelligent review is completed, call the reminder rule library to generate a reminder plan and execute the reminder plan.

[0010] Further, the information-based document pool obtains information-based document information from the intelligent control system through the data collection and interaction interface. The information-based document information includes document upload numbers, document types, document names, document-related project information, and document review status information. When the intelligent review task corresponding to the information-based document is in progress or has been completed, the information-based document pool modifies the document review status information of the corresponding information-based document.

[0011] Further, after determining all the review nodes that need to review the information-based document and the review order of each review node according to the intelligent review task, it is determined whether each review node is in the same internal chain. The internal chain is a consortium chain. If two adjacent review nodes in the review order are in the same internal chain, then for two adjacent review nodes in the same internal chain, the following operations are performed:

[0012] S201. The review node that conducts the prior review calls the review rule library and the review algorithm component to conduct an intelligent review of the information-based document. After the intelligent review is completed, the first smart contract is triggered. The first smart contract transmits the information-based document and the intelligent review result to the review node that conducts the subsequent review;

[0013] S202. The review node that conducts the subsequent review calls the review rule library and the review algorithm component to conduct an intelligent review of the information-based document. After the intelligent review is completed, the first smart contract is triggered to update the intelligent review result;

[0014] After all the review nodes in the same internal chain and adjacent in the review order have completed the intelligent review of the information-based document, the first smart contract generates a review process log and stores the review process log on the internal chain where it is located. The review process log includes review node information, review rule and review algorithm component call information, information-based document information, and intelligent review results.

[0015] Further, if two adjacent review nodes in the review order are not in the same internal chain, then for two adjacent review nodes not in the same internal chain, the following operations are performed:

[0016] S301. The review node that conducts the prior review calls the review rule library and the review algorithm component to conduct an intelligent review of the information-based document. After the intelligent review is completed, the first smart contract and the second smart contract are triggered. The first smart contract generates a review process log and stores the review process log on the internal chain where it is located. The second smart contract generates a cross-chain request including the information-based document and the intelligent review result and sends the cross-chain request to the cross-chain middleware;

[0017] S302. The cross-chain middleware sends the cross-chain request to the internal chain where the audit node under subsequent audit is located, triggering the third smart contract. The third smart contract obtains the cross-chain request and parses it to obtain the information-based document and the intelligent audit result, and transmits the information-based document to the audit node under subsequent audit;

[0018] S303. The audit node under subsequent audit calls the audit rule library and the audit algorithm component to conduct intelligent audit on the information-based document. After the intelligent audit is completed, it triggers the first smart contract. The first smart contract generates an audit process log and stores the audit process log on the internal chain where it is located;

[0019] S304. The cross-chain middleware generates a cross-chain request transmission log and stores the cross-chain request transmission log on the intermediate chain.

[0020] Furthermore, when the cross-chain middleware receives a cross-chain request and when the third smart contract obtains the cross-chain request, the sender of the cross-chain request is authenticated. The authentication includes:

[0021] S401. The receiver of the cross-chain request sends an authentication request to the sender of the cross-chain request;

[0022] S402. After receiving the authentication request, the sender of the cross-chain request determines the time when the authentication request is sent, and obtains the real-world information corresponding to the time when the authentication request is sent from the specified real-world information source;

[0023] S403. The sender of the cross-chain request determines the historical audit data acquisition strategy corresponding to the real-world information obtained in the previous step according to the correspondence between the real-world information and the historical data acquisition strategy;

[0024] S404. The sender of the cross-chain request acquires the historical audit data stored in the internal chain of other participants except the sender and the receiver of the authentication request in this round of intelligent audit according to the historical audit data acquisition strategy;

[0025] S405. The sender of the cross-chain request uses a preset data conversion method to convert the acquired historical audit data into input parameters of a preset key generation algorithm, generates a first verification key through the preset key generation algorithm, and sends the first verification key to the receiver of the cross-chain request;

[0026] S406. The receiver of the cross-chain request generates a second verification key, compares the second verification key with the first verification key, and if the comparison passes, it determines that the authentication passes.

[0027] Furthermore, the audit node calls the audit rule library and the audit algorithm component to conduct intelligent audit on the information-based document, including:

[0028] S501. Analyze the informatized document to determine the corresponding audit category of the informatized document;

[0029] S502. Further analyze the informatized document to determine the corresponding audit scenario of the informatized document, and determine the audit rules according to the audit scenario;

[0030] S503. Invoke the audit algorithm component to parse the informatized document, obtain all audit elements included in the informatized document, automatically audit the audit elements based on the audit rules, and output the audit results.

[0031] Further, step S104 includes:

[0032] S601. Analyze the informatized document that has completed intelligent audit to obtain the project type, project stage and reminder category of the informatized document;

[0033] S602. Determine the applicable reminder rules for the informatized document according to the obtained project type, project stage and reminder category;

[0034] S603. Generate a reminder task plan according to the applicable reminder rules for the informatized document, and automatically execute the reminder task plan;

[0035] S604. Collect and record the feedback of the reminded person.

[0036] Further, the audit algorithm component that can be invoked when performing intelligent audit on the informatized document is a registered audit algorithm component. The audit algorithm component is registered by filling in the registration information. The audit algorithm component includes a general document full-text parsing and recognition component package, a document information extraction component package, and a document audit element and rule matching and verification component package.

[0037] Compared with the prior art, the beneficial effects of the present invention are:

[0038] An information-based document management method based on form paperless and consortium blockchain provided by the present invention manages the collection of information-based documents through an information-based document pool, extracts uncompleted information-based documents from it to generate corresponding intelligent review tasks, determines all review nodes and review sequences that need to review the information-based documents according to the intelligent review tasks, distributes the intelligent review tasks to the review nodes according to the review sequence, the review nodes call the review rule library and the review algorithm component to conduct intelligent review on the information-based documents, after the intelligent review is completed, call the reminder rule library to generate a reminder plan, and prompt the relevant project personnel by automatically executing the reminder plan. The method uses digital and intelligent methods to carry out the process control work of project construction. By combining artificial intelligence algorithms, it reduces the workload of manual review, reduces duplicate review and duplicate submission work, improves the delivery quality of information-based documents in each stage, improves the work efficiency of digital project management while also improving the work quality of project management and reducing audit risks. BRIEF DESCRIPTION OF THE DRAWINGS

[0039] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the following will briefly introduce the drawings required for description in the embodiments. Obviously, the following drawings are only the preferred embodiments of the present invention. For those of ordinary skill in the art, without creative efforts, other drawings can be obtained based on these drawings.

[0040] Figure 1 It is a schematic diagram of the overall process of an information-based document management method based on form paperless and consortium blockchain provided by an embodiment of the present invention. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0041] The following describes the principles and features of the present invention with reference to the drawings. The listed embodiments are only used to explain the present invention and are not used to limit the scope of the present invention.

[0042] Refer to Figure 1 , this embodiment provides an information-based document management method based on form paperless and consortium blockchain. The method includes the steps of:

[0043] S101. Establish an information-based document pool to collect un-reviewed information-based documents, extract un-reviewed information-based documents from the information-based document pool to generate corresponding intelligent review tasks, and the intelligent review tasks include un-reviewed information-based documents.

[0044] In this embodiment, the information-based document pool obtains information-based document information from the intelligent control system through the data collection and interaction interface. The information-based document information includes a document upload number, a document type, a document name, document associated project information, and document review status information. When the intelligent review task corresponding to the information-based document is in progress or has been completed, the information-based document pool modifies the document review status information of the corresponding information-based document. The document review status includes un-reviewed, in-review, and reviewed.

[0045] S102. Determine all review nodes that need to review the information-based document according to the intelligent review task and the review order of each review node.

[0046] S103. Assign the intelligent review task to the review nodes according to the review order. The review nodes call the review rule library and the review algorithm component to perform intelligent review on the information-based document.

[0047] S104. After the intelligent review is completed, call the reminder rule library to generate a reminder plan and execute the reminder plan.

[0048] As an alternative embodiment, after determining all review nodes that need to review the information-based document according to the intelligent review task and the review order of each review node, determine whether each review node is in the same internal chain, and the internal chain is a consortium chain. Exemplarily, the consortium chain can adopt the MultiChain architecture. If two adjacent review nodes in the review order are in the same internal chain, then for two adjacent review nodes in the same internal chain, the following operations are performed:

[0049] S201. The review node that reviews first calls the review rule library and the review algorithm component to perform intelligent review on the information-based document. After the intelligent review is completed, trigger the first intelligent contract, and the first intelligent contract transmits the information-based document and the intelligent review result to the review node that reviews later.

[0050] S202. The review node that reviews later calls the review rule library and the review algorithm component to perform intelligent review on the information-based document. After the intelligent review is completed, trigger the first intelligent contract to update the intelligent review result;

[0051] After all review nodes in the same internal chain and adjacent in the review order have completed the intelligent review of the information-based document, the first intelligent contract generates a review process log and stores the review process log on the internal chain where it is located. The review process log includes review node information, review rule and review algorithm component call information, information-based document information, and intelligent review results.

[0052] The review of information-based documents may be carried out within a unit or a department. In this alternative embodiment, for multiple review nodes within the same unit or department, the internal chain they are in is the same. Therefore, if two adjacent review nodes in the review order of the intelligent review task are in the same internal chain, after the prior review node conducts an intelligent review of the information-based document, it triggers the first smart contract to transmit the information-based document and the intelligent review result to the subsequent review node. And after the subsequent review node completes the intelligent review of the information-based document, the first smart contract is triggered again to update the intelligent review result.

[0053] In this alternative embodiment, the review rules and / or review algorithm components that different review nodes can call vary according to their different permissions. Different review permissions can be assigned to the review nodes according to the specific review work they are responsible for. It can be understood that in order to improve the review efficiency, multiple review nodes can be responsible for the same review work to simultaneously review different information-based documents and reduce the review queuing time of information-based documents.

[0054] In this alternative embodiment, the first smart contract controls the transmission of information-based documents in the same internal chain, and transmits and updates the intelligent review result. After the continuous intelligent review process in the same internal chain ends, the first smart contract records the review process, generates the corresponding review process log and saves it to the internal chain for subsequent traceability.

[0055] As another alternative embodiment, if two adjacent review nodes in the review order are not in the same internal chain, then for two adjacent review nodes that are not in the same internal chain, the following steps are executed:

[0056] S301. The prior review node calls the review rule library and the review algorithm component to conduct an intelligent review of the information-based document. After the intelligent review is completed, the first smart contract and the second smart contract are triggered. The first smart contract generates a review process log and stores the review process log on the internal chain where it is located. The second smart contract generates a cross-chain request including the information-based document and the intelligent review result and sends the cross-chain request to the cross-chain middleware.

[0057] S302. The cross-chain middleware sends the cross-chain request to the internal chain where the subsequent review node is located, triggers the third smart contract. The third smart contract obtains the cross-chain request and parses it to obtain the information-based document and the intelligent review result, and transmits the information-based document to the subsequent review node.

[0058] S303. At the audit node for post - audit, call the audit rule library and the audit algorithm component to perform intelligent audit on the informatization document. After the intelligent audit is completed, trigger the first intelligent contract. The first intelligent contract generates an audit process log and stores the audit process log on the internal chain where it is located.

[0059] S304. The cross - chain middleware generates a cross - chain request transmission log and stores the cross - chain request transmission log on the intermediate chain.

[0060] In this optional embodiment, an internal chain includes a first intelligent contract and a second intelligent contract. The function of the first intelligent contract is the same as that in the previous embodiment, which is used to manage the transmission of informatization documents and intelligent audit results in the internal chain, and generate and save the audit process log to the internal chain where it is located when the next audit node in the audit sequence is not a node in the internal chain where it is located, or when the intelligent audit process ends. The function of the second intelligent contract is to generate a cross - chain request and transmit the cross - chain request to the cross - chain middleware.

[0061] If the audit of the informatization document involves multiple units or departments, the audit nodes involved in the intelligent audit task may be respectively in different internal chains. In this optional embodiment, after the intelligent audit process in the internal chain ends, a cross - chain request is sent to the internal chain where the next audit node responsible for intelligent audit is located through a pre - configured second intelligent contract, and it can also receive cross - chain requests sent by other internal chains through a pre - configured third intelligent contract.

[0062] In this optional embodiment, the cross - chain middleware is responsible for forwarding cross - chain requests between different internal chains. After completing the forwarding of the cross - chain request, the cross - chain middleware generates a cross - chain request transmission log and stores the cross - chain request transmission log on the intermediate chain to facilitate subsequent tracing of the cross - chain request transmission record. The cross - chain request transmission log includes the cross - chain request sending time, sender information, cross - chain request receiving time, receiver information, and cross - chain request content information.

[0063] It can be understood that in this optional embodiment, the first intelligent contract, the second intelligent contract, and the third intelligent contract are configured in different internal chains and are also used to achieve the functions mentioned in the foregoing embodiments.

[0064] This optional embodiment realizes the transmission of intelligent audit results and informatization documents between different internal chains through intelligent contracts and cross - chain middleware, enabling different units or departments that use different internal chains for data storage management to also achieve cross - chain linkage for informatization document audit through an efficient and reliable mechanism, thereby improving the audit efficiency.

[0065] As another alternative embodiment, when the cross-chain middleware receives a cross-chain request and when the third smart contract obtains the cross-chain request, the sender of the cross-chain request is authenticated, and the authentication includes:

[0066] S401. The receiver of the cross-chain request sends an authentication request to the sender of the cross-chain request.

[0067] S402. After receiving the authentication request, the sender of the cross-chain request determines the time when the authentication request is sent, and obtains the real-world information corresponding to the time when the authentication request is sent from the specified real-world information source.

[0068] In this alternative embodiment, the real-world information generated at different times should be random, and the types of content of the randomly generated real-world information are limited, and there are at least three different information contents. For example, the real-world information can be the temperature in a certain place in the real world, or the wind direction, wind speed, etc.

[0069] S403. The sender of the cross-chain request determines the historical audit data acquisition strategy corresponding to the real-world information obtained in the previous step according to the corresponding relationship between the real-world information and the historical data acquisition strategy.

[0070] In this alternative embodiment, different real-world information corresponds to one historical data acquisition strategy, so the types of content of the real-world information must be limited. After determining the content of the randomly generated real-world information, the corresponding historical data acquisition strategy can be further determined.

[0071] S404. The sender of the cross-chain request obtains the historical audit data stored in its internal chain from other participants in this round of intelligent audit except the sender and receiver of the authentication request according to the historical audit data acquisition strategy.

[0072] S405. The sender of the cross-chain request uses a preset data conversion method to convert the obtained historical audit data into input parameters of a preset key generation algorithm, generates a first verification key through the preset key generation algorithm, and sends the first verification key to the receiver of the cross-chain request.

[0073] S406. The receiver of the cross-chain request generates a second verification key, compares the second verification key with the first verification key, and if the comparison passes, it is determined that the authentication passes. The generation principle of the second verification key is the same as that of the first verification key, and will not be elaborated here.

[0074] This optional embodiment determines a historical data acquisition strategy based on the real information source of randomly generated content, and acquires corresponding historical data from other participants in intelligent review based on the randomly determined historical data acquisition strategy. By converting the acquired historical data, parameters that can be input into the key generation algorithm are obtained, and then a first verification key or a second verification key is generated through a preset key generation algorithm, so that the authentication content can be randomly generated, thereby increasing the difficulty of forging authentication content and enhancing the reliability and security of authentication.

[0075] As another optional embodiment, the audit node calls the audit rule library and the audit algorithm component to perform intelligent audit on the informatization document, including:

[0076] S501. Analyze the informatization document to determine the audit category corresponding to the informatization document.

[0077] S502. Further analyze the informatization document to determine the audit scenario corresponding to the informatization document, and determine the audit rule according to the audit scenario.

[0078] S503. Call the audit algorithm component to parse the informatization document, obtain all audit elements included in the informatization document, automatically audit the audit elements based on the audit rule, and output the audit result.

[0079] In this optional embodiment, the audit element is the smallest logical input parameter unit for document problem verification in intelligent audit. For example, the document compilation time, contract start time, contract end time, etc. are all audit elements. Selecting these elements as input parameters, these key relevant information are extracted and compared and verified during document audit. Different review elements can be combined into different audit rules, different audit rules can belong to different audit scenarios, different audit scenarios can belong to different audit categories, and the audit category corresponds to multiple document parsing templates. Each document to be audited performs the audit work according to the corresponding document parsing template.

[0080] The audit rules include two types: general rules and special rules. General rules refer to a type that is used in document audit, such as the rule "whether the document compilation time is within the project implementation period"; private rules refer to audit rules that can only be used for certain types of documents. For example, for contract-related issues, the rule "whether the contract amount uses both the large and small formats at the same time, and whether the amounts in both cases are equal" is a special rule.

[0081] In this optional embodiment, the audit rule description information includes basic information such as rule attribute (general, special), belonging audit category, audit scenario, used audit elements, associated template, associated algorithm component, display color, rule status, creator, creation time, etc. If the rule attribute is general, the associated template is empty.

[0082] As another alternative embodiment, step S104 includes:

[0083] S601. Analyze the informatized document that has completed intelligent review to obtain the project type, project stage, and reminder category of the informatized document.

[0084] S602. Determine the reminder rules applicable to the informatized document according to the obtained project type (bidding and procurement document, contract document, process document), project stage (contract signing, requirement, design, code development, testing, deployment, preliminary acceptance, final acceptance), and reminder category (project progress reminder, project deliverable quality status reminder, project report output status reminder).

[0085] In this alternative embodiment, the reminder rules include milestone nodes that need to be reminded, reminder methods, reminder objects, reminder frequencies, reminder intervals, etc.

[0086] S603. Generate a reminder task plan according to the reminder rules applicable to the informatized document and automatically execute the reminder task plan.

[0087] S604. Collect and record the feedback of the reminded person.

[0088] As another alternative embodiment, the audit algorithm component that can be called during the intelligent review of the informatized document is a registered audit algorithm component. The audit algorithm component is registered by filling in the registration information. The audit algorithm component includes a general document full-text parsing and recognition component package, a document information extraction component package, and a document audit element and rule matching and verification component package.

[0089] In this alternative embodiment, the registration information includes component number, component source (artificial intelligence platform, intelligent review tool), deployment location, component type (document parsing component, audit component, verification component), component version, call parameters, creation time, creator, modification time, and modifier.

[0090] The categories of the audit algorithm components, the names of the included components, the uses and functions of each component are shown in Table 1.

[0091] Table 1

[0092]

[0093]

[0094] The above are only the preferred embodiments of the present invention and are not intended to limit the present invention. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present invention shall be included in the protection scope of the present invention.

Claims

1. An information-based document management method based on paperless forms and alliance chain, characterized in that: The method comprises: S101, establishing an informationized document pool to collect unaudited informationized documents, extracting unaudited informationized documents from the informationized document pool to generate corresponding intelligent audit tasks, wherein the intelligent audit tasks include unaudited informationized documents; S102, determining all audit nodes that need to be audited for the informationized document and the audit order of each audit node according to the intelligent audit task; S103, assigning intelligent audit tasks to audit nodes according to the audit order, and the audit nodes calling the audit rule library and the audit algorithm component to perform intelligent audit on the informationized documents; S104: After the intelligent audit is completed, the reminder rule library is called to generate a reminder plan, and the reminder plan is executed.

2. According to claim 1, an information-based document management method based on paperless forms and alliance chain is characterized in that: The informationized document pool obtains informationized document information from the intelligent management and control system through a data collection interactive interface. The informationized document information includes document upload number, document type, document name, document-related project information, and document review status information. When the intelligent review task corresponding to the informationized document is in execution or completed, the informationized document pool modifies the document review status information of the corresponding informationized document.

3. According to claim 1, the information-based document management method based on paperless forms and alliance chain is characterized in that: After determining all audit nodes that need to be audited for the informationized document and the audit order of each audit node according to the intelligent audit task, determine whether each audit node is in the same internal chain, which is a consortium chain. If two adjacent audit nodes in the audit order are in the same internal chain, then for the two audit nodes in the same internal chain and adjacent in the audit order, execute: S201, the audit node that conducts the prior audit calls the audit rule library and the audit algorithm component to conduct an intelligent audit on the informationized document. After the intelligent audit is completed, the first intelligent contract is triggered, and the first intelligent contract transmits the informationized document and the intelligent audit result to the audit node that conducts the subsequent audit; S202: The audit node of the post-audit calls the audit rule library and the audit algorithm component to perform intelligent audit on the information document. After the intelligent audit is completed, the first smart contract is triggered to update the intelligent audit result; After the audit nodes in the same internal chain and with adjacent audit order have completed the intelligent audit of the informationized documents, the first smart contract generates an audit process log and stores the audit process log on the internal chain. The audit process log includes audit node information, audit rules and audit algorithm component call information, informationized document information and intelligent audit results.

4. According to claim 3, the information-based document management method based on paperless forms and alliance chain is characterized in that: If two adjacent audit nodes in the audit sequence are not in the same internal chain, then for the two audit nodes that are not in the same internal chain and have adjacent audit sequences, execute: S301. The audit node that has been audited previously calls the audit rule library and the audit algorithm component to perform intelligent audit on the informationized document. After the intelligent audit is completed, the first smart contract and the second smart contract are triggered. The first smart contract generates an audit process log and stores the audit process log on the internal chain. The second smart contract generates a cross-chain request including the informationized document and the intelligent audit result, and sends the cross-chain request to the cross-chain middleware. S302, the cross-chain middleware sends the cross-chain request to the internal chain where the audit node for post-audit is located, triggering the third smart contract, which obtains and parses the cross-chain request, obtains the information document and the smart audit result, and transmits the information document to the audit node for post-audit; S303: The audit node of the post-audit calls the audit rule library and the audit algorithm component to perform intelligent audit on the information document. After the intelligent audit is completed, the first smart contract is triggered. The first smart contract generates an audit process log and stores the audit process log on the internal chain. S304. The cross-chain middleware generates a cross-chain request transmission log and stores the cross-chain request transmission log on the intermediate chain.

5. According to claim 4, the information-based document management method based on paperless forms and alliance chain is characterized in that: When the cross-chain middleware receives the cross-chain request and the third smart contract obtains the cross-chain request, the sender of the cross-chain request is authenticated, and the authentication includes: S401. The receiver of the cross-chain request sends an identity authentication request to the sender of the cross-chain request; S402: After receiving the identity authentication request, the sender of the cross-chain request determines the time when the identity authentication request is issued, and obtains the real information corresponding to the time when the identity authentication request is issued from the specified real information source; S403. The sender of the cross-chain request determines the historical audit data acquisition strategy corresponding to the real information acquired in the previous step according to the correspondence between the real information and the historical data acquisition strategy; S404. The sender of the cross-chain request obtains the historical audit data stored in its internal chain from other participants in this round of intelligent audit except the sender and receiver of the identity authentication request according to the historical audit data acquisition strategy; S405. The sender of the cross-chain request uses a preset data conversion method to convert the acquired historical audit data into input parameters of a preset key generation algorithm, generates a first verification key through the preset key generation algorithm, and sends the first verification key to the receiver of the cross-chain request; S406. The recipient of the cross-chain request generates a second verification key, and compares the second verification key with the first verification key. If the comparison is successful, the identity authentication is determined to be successful.

6. According to claim 3 or 4, an information-based document management method based on paperless forms and alliance chain is characterized in that: The audit node calls the audit rule library and audit algorithm components to perform intelligent audit on information documents, including: S501. Analyze the information documents and determine the audit categories corresponding to the information documents; S502, further analyzing the informationized document, determining the audit scenario corresponding to the informationized document, and determining the audit rules according to the audit scenario; S503: Call the audit algorithm component to parse the information document, obtain all audit elements contained in the information document, automatically audit the audit elements based on the audit rules, and output the audit results.

7. According to claim 1, the information-based document management method based on paperless forms and alliance chain is characterized in that: Step S104 includes: S601. Analyze the information documents that have completed intelligent review to obtain the project type, project stage and reminder category of the information documents; S602, determining reminder rules applicable to the informationized document according to the obtained project type, project stage and reminder category; S603, generating a reminder task plan according to the reminder rules applicable to the informationized document, and automatically executing the reminder task plan; S604. Collect and record feedback from the person being reminded.

8. According to claim 1, the information-based document management method based on paperless forms and alliance chain is characterized in that: The audit algorithm component that can be called when performing intelligent audit on information documents is a registered audit algorithm component. The audit algorithm component is registered by filling in registration information. The audit algorithm component includes a general document full-text parsing and recognition component package, a document information extraction component package, and a document audit element and rule matching verification component package.

Images