Contract file processing method and device, equipment and storage medium

Abstract

The invention provides a contract file processing method and device, equipment and a storage medium. The invention relates to the technical field of blockchains. The method comprises the following steps: generating a contract file in response to an editing operation; according to preset inspection rule information, performing compliance inspection processing on the contract file to generate inspection result information; wherein the preset checking rule information is clause rule information for checking clauses in the contract file. If the check result information represents that the contract file is a correct result, sending and storing the contract file in a preset block chain; executing the contract file according to a preset smart contract in the block chain, and generating execution result information; wherein the execution result information is used for indicating actual execution data of each stage of the contract file. According to the method provided by the invention, the problem of low contract supervision efficiency in the prior art is solved.

Description

Technical Field

[0001] This application relates to the field of blockchain technology, and in particular to a method, apparatus, device and storage medium for processing contract documents. Background Technology

[0002] Currently, compared to paper contracts, which involve repeated revisions and are cumbersome to retrieve after archiving, electronic contracts are more convenient and easier to manage assets. Therefore, further optimization of electronic contract management is necessary.

[0003] In the current technology, electronic contracts for managed state-owned assets and other assets still rely on manual or semi-manual screening and supervision, as well as one-on-one guidance and solution output.

[0004] However, in the existing technology, the traditional model is mainly based on manual or semi-manual methods, which leads to low efficiency in contract supervision. Summary of the Invention

[0005] This application provides a method, apparatus, device, and storage medium for processing contract documents, in order to solve the problem of low efficiency in contract supervision in the prior art.

[0006] Firstly, this application provides a method for processing contract documents, applied to electronic devices, including:

[0007] In response to editing operations, generate contract documents;

[0008] According to the preset inspection rule information, the contract document is subjected to compliance inspection processing to generate inspection result information; wherein, the preset inspection rule information is the clause rule information for inspecting the clauses in the contract document;

[0009] If the verification result information indicates that the contract document is correct, the contract document is sent and stored in a preset blockchain; and the contract document is executed according to the preset smart contract in the blockchain to generate execution result information; wherein, the execution result information is used to indicate the actual execution data of each stage of the contract document.

[0010] In one possible design, the step of performing compliance inspection on the contract documents according to preset inspection rule information and generating inspection result information includes:

[0011] Based on the legal clause rules information in the preset inspection rules information, the contract documents are subjected to compliance inspection processing, and the legal clause result information in the inspection result information is generated;

[0012] Based on the business terms rules information in the preset inspection rules information, the contract documents are subjected to compliance inspection processing, and the business terms result information in the inspection result information is generated.

[0013] In one possible design, the legal clause and rule information includes a preset legal clause template library, a preset legal and regulatory database, and a preset legal analysis system;

[0014] The process of performing compliance inspection on the contract document based on the legal clause rule information in the preset inspection rule information, and generating legal clause result information in the inspection result information, includes:

[0015] The clauses in the contract document are compared and verified with standard clauses in a preset legal clause template library to generate the first legal clause result information in the verification result information; wherein, the first legal clause result information includes whether the clauses in the contract document are missing or incorrect;

[0016] The clauses in the contract document are input into a preset legal database to perform compliance verification on the clauses, generating a second legal clause result information in the verification result information; wherein, the second legal clause result information includes whether the clauses in the contract document comply with the preset legal database.

[0017] The clauses in the contract document are input into a preset legal analysis system for high-risk testing, generating third legal clause result information in the test results information; wherein, the third legal clause result information includes dangerous clauses in the contract document whose risk level is higher than a preset risk threshold, and modification suggestions for the dangerous clauses.

[0018] In one possible design, the business terms and rules information includes a preset industry standard rule base and preset contract business rules information;

[0019] The step of performing compliance inspection on the contract document based on the business clause rule information in the preset inspection rule information, and generating business clause result information in the inspection result information, includes:

[0020] The terms in the contract document are matched and verified against industry standards in a pre-defined industry standard rule base to generate the first business terms result information in the verification result information; wherein, the first business terms result information includes whether the terms in the contract document comply with industry standards;

[0021] Based on preset contract business rules information, the clauses in the contract document are subjected to compliance verification processing, and the second business clause result information is generated in the verification result information.

[0022] The data involved in the contract document is compared and verified with the actual data in the electronic device to generate the third business clause result information in the verification result information; wherein, the third business clause result information includes whether the data involved in the contract document is consistent with the actual data, and the erroneous data that occurs when they are inconsistent.

[0023] In one possible design, the method further includes:

[0024] In response to a signature operation, the signed contract document is obtained; wherein, the signature operation includes operations initiated by the user on the electronic device side and operations initiated by the user's trading partner;

[0025] The step of executing the contract file according to the preset smart contract in the blockchain and generating execution result information includes:

[0026] According to the preset smart contract in the blockchain, the signed contract file is executed, and during the execution process, the contract execution status and any abnormal transactions generated are monitored and verified to obtain monitoring result information;

[0027] If the monitoring results indicate an abnormal situation, a prompt message is sent to the preset monitoring system; and execution result information is generated based on the contract execution status and the abnormal transactions generated.

[0028] In one possible design, if the verification result information indicates that the contract document is correct, then the contract document is sent and stored in a preset blockchain, including:

[0029] For each contract document, if the verification result information indicates that the contract document is correct, then the contract document is hashed to obtain a hash value;

[0030] Data extraction is performed on the preset key data in the contract document to obtain the key data;

[0031] The contract document, its hash value, and key data are all sent to and stored in a pre-defined blockchain.

[0032] In one possible design, the contract document, its hash value, and key data are all sent to and stored in a pre-defined blockchain, including:

[0033] Determine the type of the contract document;

[0034] Determine the storage node in the preset blockchain that corresponds to the type;

[0035] The hash value and key data of the contract document are used as index data;

[0036] Based on a pre-defined distributed hash table, each contract file and its index data are stored on different storage nodes in the blockchain.

[0037] In one possible design, generating a contract document in response to an editing operation includes:

[0038] In response to the selection of a preset contract template, the target template is identified and displayed;

[0039] In response to an editing operation on the target template, a contract document is generated.

[0040] In one possible design, the method further includes:

[0041] If a dispute is detected during the execution of the contract documents, the dispute will be arbitrated according to the preset arbitration rules and supporting documents of the contract documents, and an arbitration result will be generated.

[0042] Secondly, this application provides a contract document processing apparatus, comprising:

[0043] The generation module is used to generate contract documents in response to editing operations;

[0044] The inspection module is used to perform compliance inspection on the contract document according to preset inspection rule information and generate inspection result information; wherein, the preset inspection rule information is the clause rule information for inspecting the clauses in the contract document;

[0045] The sending module is used to send and store the contract document in a preset blockchain if the inspection result information indicates that the contract document is correct.

[0046] The execution module is used to execute the contract file according to the preset smart contract in the blockchain and generate execution result information; wherein, the execution result information is used to indicate the actual execution data of each stage of the contract file.

[0047] In one possible design, the inspection module includes:

[0048] The first inspection unit is used to perform compliance inspection on the contract documents according to the legal clause rule information in the preset inspection rule information, and generate legal clause result information in the inspection result information.

[0049] The second inspection unit is used to perform compliance inspection on the contract document according to the business clause rule information in the preset inspection rule information, and generate business clause result information in the inspection result information.

[0050] In one possible design, the legal clause and rule information includes a preset legal clause template library, a preset legal and regulatory database, and a preset legal analysis system;

[0051] The first inspection unit is specifically used for:

[0052] The clauses in the contract document are compared and verified with standard clauses in a preset legal clause template library to generate the first legal clause result information in the verification result information; wherein, the first legal clause result information includes whether the clauses in the contract document are missing or incorrect;

[0053] The clauses in the contract document are input into a preset legal database to perform compliance checks on the clauses, generating a second legal clause result information in the check result information; wherein, the second legal clause result information includes whether the clauses in the contract document comply with the preset legal database.

[0054] The clauses in the contract document are input into a preset legal analysis system for high-risk testing, generating third legal clause result information in the test results information; wherein, the third legal clause result information includes dangerous clauses in the contract document whose risk level is higher than a preset risk threshold, and modification suggestions for the dangerous clauses.

[0055] In one possible design, the business terms and rules information includes a preset industry standard rule base and preset contract business rules information;

[0056] The second inspection unit is specifically used for:

[0057] The terms in the contract document are matched and verified against industry standards in a preset industry standard rule base to generate the first business terms result information in the verification result information; wherein, the first business terms result information includes whether the terms in the contract document comply with industry standards.

[0058] Based on preset contract business rules information, the clauses in the contract document are subjected to compliance verification processing, and the second business clause result information is generated in the verification result information.

[0059] The data involved in the contract document is compared and verified with the actual data in the electronic device to generate the third business clause result information in the verification result information; wherein, the third business clause result information includes whether the data involved in the contract document is consistent with the actual data, and the erroneous data that occurs when they are inconsistent.

[0060] In one possible design, the device is also specifically used for:

[0061] In response to a signature operation, the signed contract document is obtained; wherein, the signature operation includes operations initiated by the user on the electronic device side and operations initiated by the user's trading partner;

[0062] The execution module is specifically used for:

[0063] According to the preset smart contract in the blockchain, the signed contract file is executed, and during the execution process, the contract execution status and any abnormal transactions generated are monitored and verified to obtain monitoring result information;

[0064] If the monitoring results indicate an abnormal situation, a prompt message is sent to the preset monitoring system; and execution result information is generated based on the contract execution status and the abnormal transactions generated.

[0065] In one possible design, the sending module includes:

[0066] A hash unit is used to perform hash processing on each contract file if the verification result information indicates that the contract file is correct, and obtain a hash value.

[0067] The extraction unit is used to extract key data from the preset key data of the contract document to obtain the key data.

[0068] The sending unit is used to send and store the contract document, the hash value of the contract document, and the key data of the contract document into a preset blockchain.

[0069] In one possible design, the transmitting unit is specifically used for:

[0070] Determine the type of the contract document;

[0071] Determine the storage node in the preset blockchain that corresponds to the type;

[0072] The hash value and key data of the contract document are used as index data;

[0073] Based on a pre-defined distributed hash table, each contract file and its index data are stored on different storage nodes in the blockchain.

[0074] In one possible design, the generation module is specifically used for:

[0075] In response to the selection of a preset contract template, the target template is identified and displayed;

[0076] In response to an editing operation on the target template, a contract document is generated.

[0077] In one possible design, the device is also specifically used for:

[0078] If a dispute is detected during the execution of the contract documents, the dispute will be arbitrated according to the preset arbitration rules and supporting documents of the contract documents, and an arbitration result will be generated.

[0079] Thirdly, embodiments of this application provide an electronic device, including: at least one processor and a memory; the memory stores computer-executable instructions; the at least one processor executes the computer-executable instructions stored in the memory, causing the at least one processor to perform the contract document processing method described in the first aspect and various possible designs of the first aspect.

[0080] Fourthly, embodiments of this application provide a computer-readable storage medium storing computer-executable instructions. When a processor executes the computer-executable instructions, it implements the contract document processing method described in the first aspect and various possible designs of the first aspect.

[0081] Fifthly, embodiments of this application provide a computer program product, including a computer program that, when executed by a processor, implements the contract document processing method described in the first aspect and various possible designs of the first aspect.

[0082] The contract document processing method, apparatus, equipment, and storage medium provided in this application generate contract documents in response to editing operations. Based on preset inspection rules, the contract documents undergo compliance inspection processing to generate inspection result information; wherein, the preset inspection rules are the clause rules information for inspecting the terms in the contract documents. If the inspection result information indicates that the contract document is correct, the contract document is sent and stored in a preset blockchain; and according to a preset smart contract in the blockchain, the contract document is executed to generate execution result information; wherein, the execution result information is used to indicate the actual execution data at each stage of the contract document. In this solution, the contract document undergoes compliance inspection processing to generate inspection result information. Users can modify the contract document according to the inspection result information to obtain a correct contract document, which is then sent and stored in the blockchain. According to the preset smart contract in the blockchain, the signed contract document is executed to generate execution result information. Therefore, by using blockchain technology, leveraging its characteristics of immutability, decentralization, and transparency, a new solution is provided for the supervision of state-owned assets. Through compliance verification, the legality and accuracy of contract documents are guaranteed, aiming to improve the management efficiency and transparency of state-owned assets, reduce management costs, and ensure the legality and security of asset transactions, thereby addressing the problem of low efficiency in contract supervision under existing technologies. Attached Figure Description

[0083] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0084] Figure 1 A flowchart illustrating a method for processing contract documents provided in an embodiment of this application;

[0085] Figure 2 A flowchart illustrating another method for processing contract documents provided in this application embodiment;

[0086] Figure 3 A flowchart illustrating another method for processing contract documents provided in this application embodiment;

[0087] Figure 4 A schematic diagram of the structure of a contract document processing device provided in an embodiment of this application;

[0088] Figure 5 A schematic diagram of another contract document processing apparatus provided in this application embodiment;

[0089] Figure 6 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application.

[0090] The accompanying drawings illustrate specific embodiments of this application, which will be described in more detail below. These drawings and descriptions are not intended to limit the scope of the concept in any way, but rather to illustrate the concept of this application to those skilled in the art through reference to particular embodiments. Detailed Implementation

[0091] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

[0092] It should be noted that the collection, storage, use, processing, transmission, provision, and disclosure of financial data or user data involved in the technical solution of this application all comply with relevant laws and regulations and do not violate public order and good morals. The user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, and displayed data) involved in this application are all information and data authorized by the user or fully authorized by all parties. Furthermore, the collection, use, and processing of related data must comply with relevant laws, regulations, and standards, and corresponding operation entry points are provided for users to choose to authorize or refuse. In addition, certain software, components, models, and other existing industry solutions may be mentioned in the embodiments of this application. These should be considered exemplary, and their purpose is merely to illustrate the feasibility of implementing the technical solution of this application, but does not mean that the applicant has already used or necessarily used such solutions.

[0093] Currently, compared to paper contracts, which involve repeated revisions and are cumbersome to retrieve after archiving, electronic contracts are more convenient and easier to manage assets. Therefore, further optimization of electronic contract management is necessary.

[0094] In one example, electronic contracts for managed state-owned assets still rely on manual or semi-manual screening and supervision, providing one-on-one guidance and solutions. However, in existing technologies, the traditional model, which is mainly manual or semi-manual, results in low efficiency in contract supervision.

[0095] In one example, the contract lacks transparency, the regulatory system suffers from information silos, and there are problems such as difficulty in contract enforcement and easy data tampering.

[0096] Terminology Explanation:

[0097] Blockchain infrastructure: serving as the foundation for data storage and verification.

[0098] Smart contracts: Code that automatically executes the terms of a contract.

[0099] Regulatory node: A node responsible for supervising and verifying transactions.

[0100] To address the aforementioned technical problems, this application proposes the following technical concept: The signed contract document is sent to the blockchain, and according to a pre-defined smart contract in the blockchain, the signed contract document is executed, generating execution result information. This solves the problem of low efficiency in contract supervision in existing technologies.

[0101] The technical solution of this application and how the technical solution of this application solves the above-mentioned technical problems are described in detail below with specific embodiments. These 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 this application will now be described with reference to the accompanying drawings.

[0102] Figure 1 A flowchart illustrating a method for processing contract documents provided in this application embodiment is shown below. Figure 1 As shown, the method includes:

[0103] Step 101: In response to the editing operation, generate the contract document.

[0104] For example, the executing entity of this embodiment may be an electronic device, a terminal device, a contract document processing device or apparatus, or other apparatus or apparatus capable of executing this embodiment, and there is no limitation thereto. In this embodiment, the executing entity is described as an electronic device.

[0105] First, users must verify their identity and log in. After successful login, a contract document is generated based on the user's editing actions. Specifically, the user's identity is verified using technologies such as digital certificates and biometrics to ensure the authenticity and reliability of the user's identity. The identity verification process is as follows:

[0106] 1.1 User Information Registration

[0107] Facial data collection: Users collect facial data by following system prompts in front of electronic devices equipped with identity authentication systems, such as mobile phones, computers, or dedicated recognition devices with cameras. The system uses facial recognition technology to extract key feature points from the user's face, forming a unique set of facial feature vectors that accurately represent the user's facial features.

[0108] Generate User Identifier: The system generates a unique digital identity for each user. This identifier is usually a string of encrypted characters or numbers that is associated with the user's facial feature vector and other necessary personal information (such as name, ID number, etc.).

[0109] 1.2 Blockchain Account Creation

[0110] Creating a blockchain account: Users create their own account on the blockchain network, which has a unique public key and private key. The public key is used to publicly identify the user on the blockchain, while the private key is kept securely by the user and used to sign transactions and operations, ensuring the security and authenticity of information.

[0111] On-chain information storage: The user's facial feature vector, user identifier, and other relevant personal information are encrypted and stored on the blockchain as a transaction record. The distributed ledger nature of the blockchain ensures that this information is copied and stored by multiple nodes, and the failure or tampering of any single node will not affect the integrity and availability of the data.

[0112] 1.3 Blockchain Verification and Use

[0113] Re-collecting facial data: When users need to authenticate their identity, they can collect facial data again through electronic devices. The collection process is similar to that during registration, and the system will extract the current facial feature vector.

[0114] Feature comparison: The facial feature vector collected this time is compared with the facial feature vector stored on the blockchain during user registration. A specific algorithm is used to calculate the similarity between the two to determine whether they belong to the same user.

[0115] Authentication request: If the facial feature comparison passes, the system will generate an authentication request containing the user's public key, current timestamp, and other information, and sign the request using the user's private key.

[0116] Blockchain verification: The signed authentication request is sent to the blockchain network. Upon receiving the request, a blockchain node first verifies the validity of the signature using the user's public key, ensuring the request was initiated by a legitimate user and has not been tampered with. Then, the node checks information such as the timestamp in the request to prevent security issues such as replay attacks.

[0117] Certification result recording and verification

[0118] Record authentication results: If authentication is successful, the blockchain generates a new transaction record, recording the user's successful authentication information, including authentication time, authentication location, and other relevant data, and adds this record to the blockchain. If authentication fails, the corresponding failure information is also recorded.

[0119] Verification and Use: In scenarios where user identity verification is required, relevant systems can confirm the validity of the user's identity by querying authentication records on the blockchain. Due to the immutable nature of the blockchain, these authentication records have high credibility and authority, providing a reliable basis for user identity authentication for various applications.

[0120] Step 102: Perform compliance inspection on the contract documents according to the preset inspection rule information and generate inspection result information; wherein, the preset inspection rule information is the clause rule information for inspecting the clauses in the contract documents.

[0121] For example, the preset inspection rule information is the clause rule information for inspecting the clauses in the contract document. For instance, the inspection rule information includes legal clause rule information and business clause rule information. The legal clause rule information is used to inspect whether the clauses in the contract document comply with legal clauses, and the business clause rule information is used to inspect whether the clauses in the contract document comply with business clauses.

[0122] In this step, the contract documents are subjected to compliance inspection based on the legal clauses and rules in the preset inspection rules information, and the contract documents are subjected to compliance inspection based on the business clauses and rules in the inspection rules information, generating inspection result information, which indicates whether the inspection of the contract documents is correct.

[0123] Step 103: If the verification result information indicates that the contract document is correct, the contract document is sent and stored in the preset blockchain; and the contract document is executed according to the preset smart contract in the blockchain to generate execution result information; wherein, the execution result information is used to indicate the actual execution data of each stage of the contract document.

[0124] For example, if the verification result indicates that the contract document is correct, the contract document is sent and stored in a pre-defined blockchain. Then, a pre-defined smart contract in the blockchain can be invoked to execute the contract document according to its terms, generating execution result information that indicates the actual execution data at each stage of the contract document.

[0125] In this embodiment, a contract document is generated in response to an editing operation. Based on preset inspection rules, the contract document undergoes compliance inspection, generating inspection result information. The preset inspection rules are the clause rules for inspecting the terms in the contract document. If the inspection result information indicates that the contract document is correct, the contract document is sent and stored in a preset blockchain. The contract document is then executed according to a preset smart contract in the blockchain, generating execution result information. This execution result information indicates the actual execution data at each stage of the contract document. In this solution, the contract document undergoes compliance inspection, generating inspection result information. Users can modify the contract document based on the inspection result information to obtain a correct contract document, which is then sent and stored in the blockchain. The signed contract document is executed according to a preset smart contract in the blockchain, generating execution result information. Therefore, by using blockchain technology, leveraging its immutability, decentralization, and transparency, a new solution for state-owned asset supervision is provided. Compliance inspection ensures the legality and accuracy of contract documents, aiming to improve the efficiency and transparency of state-owned asset management, reduce management costs, and ensure the legality and security of asset transactions, thereby addressing the problem of low efficiency in contract supervision in existing technologies.

[0126] Figure 2 A flowchart illustrating another method for processing contract documents provided in this application embodiment is shown below. Figure 2 As shown, the method includes:

[0127] Step 201: In response to the editing operation, generate the contract document.

[0128] In one example, step 201 includes: in response to a selection operation for a preset contract template, identifying and displaying a target template; and in response to an editing operation for the target template, generating a contract document.

[0129] For example, the electronic device has multiple standardized contract templates pre-stored. Users can select different templates to edit and customize as needed. In response to the user's selection, the target template is determined and displayed. In response to the user's editing operation on the target template, a contract document is generated.

[0130] Step 202: Based on the legal clause rules information in the preset inspection rules information, perform compliance inspection on the contract documents and generate the legal clause result information in the inspection result information.

[0131] In one example, the legal clause rules information includes a preset legal clause template library, a preset legal and regulatory database, and a preset legal analysis system. Step 202 includes: comparing and verifying the clauses in the contract document with the standard clauses in the preset legal clause template library to generate first legal clause result information in the verification result information; wherein, the first legal clause result information includes whether the clauses in the contract document are missing or incorrect; inputting the clauses in the contract document into the preset legal and regulatory database to perform compliance verification on the clauses, generating second legal clause result information in the verification result information; wherein, the second legal clause result information includes whether the clauses in the contract document comply with preset legal and regulatory laws and regulations; inputting the clauses in the contract document into the preset legal analysis system to perform high-risk verification, generating third legal clause result information in the verification result information; wherein, the third legal clause result information includes dangerous clauses in the contract document whose risk level is higher than a preset risk threshold, and modification suggestions for dangerous clauses.

[0132] For example, based on the legal clause rules information in the preset inspection rules information, the contract documents are subjected to legal compliance inspection processing, and the legal clause result information in the inspection result information is generated.

[0133] Specifically, a legal clause template library is pre-established, covering common legal clauses in various contracts, such as contract parties, rights and obligations, and liability for breach of contract. During the intelligent editing process of the contract document, the clauses entered by the user are compared with the standard clauses in the legal clause template library to detect whether there are any missing key clauses or discrepancies with the standard clauses. This results in the generation of the first legal clause result information, which includes whether the clauses in the contract document are missing or incorrect.

[0134] The terms in the contract document are input into a pre-defined legal and regulatory database, which then performs real-time query and verification of the smart contract's terms. For example, natural language processing technology is used to analyze whether the terms comply with relevant laws and regulations, such as whether they violate mandatory provisions of the Contract Law or the Consumer Rights Protection Law. This analysis then generates a second legal clause result, which includes whether the terms in the contract document comply with the pre-defined laws and regulations.

[0135] The contract clauses are input into a pre-set legal analysis system. Utilizing AI-based analysis, the system simulates the thinking and judgment of legal experts, intelligently performing a comprehensive analysis of the contract to identify potential legal risks and generate professional legal opinions and suggestions. This results in a third-party legal clause analysis, which includes clauses in the contract exceeding a pre-set risk threshold and suggested modifications. Therefore, users can use these third-party legal clause analysis results to make targeted modifications, resulting in a correct contract and ensuring its legal compliance.

[0136] Step 203: Based on the business clause rule information in the preset inspection rule information, perform compliance inspection on the contract documents and generate the business clause result information in the inspection result information.

[0137] In one example, the business terms and rules information includes a preset industry standard rule library and preset contract business rules information; step 203 includes: matching and verifying the terms in the contract document with the industry standards in the preset industry standard rule library to generate first business terms result information in the verification result information; wherein, the first business terms result information includes whether the terms in the contract document comply with the industry standards; based on the preset contract business rules information, performing compliance verification on the terms in the contract document to generate second business terms result information in the verification result information; comparing and verifying the data involved in the contract document with the actual data in the electronic device to generate third business terms result information in the verification result information; wherein, the third business terms result information includes whether the data involved in the contract document is consistent with the actual data, and erroneous data that occurs in the case of inconsistency.

[0138] For example, the contract documents are subjected to business compliance inspection processing based on the business clause rule information in the preset inspection rule information, and the business clause result information in the inspection result information is generated.

[0139] Specifically, an industry standard rule library is pre-established based on the business norms and standards of different industries. During smart contract editing, the business clauses involved in the contract are matched with the corresponding industry standard rules of the contract itself to check whether they comply with the industry's common business processes, quality standards, technical specifications, and other requirements. The first business clause result information is generated in the inspection result information, which includes whether the clauses in the contract document comply with industry standards.

[0140] By combining the company's own business processes and management requirements, internal contract business rules are pre-defined. Before signing smart contract documents, the terms of the contract documents are internally validated based on the pre-defined contract business rules, generating a second business clause result in the validation result information. This ensures that the contract documents comply with the company's approval processes, permission settings, business scope, and other internal management regulations, preventing violations of internal regulations.

[0141] The data in the contract documents is compared and verified against the actual data in the electronic devices to check whether the data in the contract documents is consistent with the data in the relevant business systems. This verification result generates a third business clause result information, which includes whether the data in the contract documents is consistent with the actual data and any errors that occur in cases of inconsistency. For example, data such as product quantity, price, and delivery time in the contract are compared with data from the company's inventory management system, pricing system, and production planning system to ensure the accuracy and consistency of the contract data and avoid business risks caused by data inconsistencies.

[0142] Therefore, users can make targeted modifications based on the results of the first, second, and third business terms to obtain the correct contract documents, which can help users improve the contract terms and ensure the business compliance of the contract.

[0143] It should be noted that operations such as typo correction can also be performed on contract documents. For example, the text in the contract document can be identified and verified according to a preset dictionary. There are no limitations on this.

[0144] Step 204: In response to the signing operation, obtain the signed contract document; wherein, the signing operation includes the operation issued by the user on the electronic device side and the operation issued by the user's trading partner.

[0145] For example, after both parties confirm that everything is correct, they electronically sign the document, generating a signed contract document in response to their online signing actions. The signing actions include those initiated by the user on the electronic device and those initiated by the user's trading partner; the signature employs asymmetric encryption technology to ensure its unforgeability.

[0146] Step 205: If the inspection result information indicates that the contract document is correct, then the contract document is sent and stored in the preset blockchain.

[0147] In one example, step 205 includes: for each contract document, if the verification result information indicates that the contract document is correct, then the contract document is hashed to obtain a hash value; the preset key data of the contract document is extracted to obtain key data; and the contract document, the hash value of the contract document, and the key data of the contract document are all sent and stored in a preset blockchain.

[0148] In one example, “sending and storing the contract file, the hash value of the contract file, and the key data of the contract file to a preset blockchain” includes: determining the type of the contract file; determining the storage node in the preset blockchain corresponding to the type; using the hash value and key data of the contract file as index data; and storing each contract file and its index data on different storage nodes in the blockchain based on a preset distributed hash table.

[0149] For example, before storing contract documents and other documentary evidence on the blockchain, the contract documents are hashed, converting the content of the document into a unique hash value. This hash value serves as the document's "fingerprint," ensuring the integrity and authenticity of the contract documents. Simultaneously, key information from the contract documents is extracted, such as filename, file type, contract number, relevant party information, and document creation time. This metadata, along with the hash value and the contract documents themselves, is then stored on the blockchain.

[0150] Furthermore, the electronic device determines the type of the signed contract document. For example, the type may include one or more of the following: asset transaction records, contract terms, execution status, on-chain storage, etc. Based on a preset mapping relationship between types and storage locations, the electronic device determines the corresponding storage node in a preset blockchain. The hash value and key data of the signed contract document are used as index data; based on a preset distributed hash table, each contract document and its index data are stored on different storage nodes in the blockchain, thus ensuring that all signed contract documents are stored on the blockchain, achieving decentralized storage and preventing data tampering and loss. Simultaneously, the electronic device provides functions such as contract retrieval, updating, and termination.

[0151] For example, an efficient index structure can be built based on file metadata stored on the blockchain. Distributed indexing technologies, such as distributed hash tables (DHTs) or blockchain-based distributed indexing protocols, can be used to distribute index data of different contract documents across multiple blockchain storage nodes to improve query efficiency and system scalability.

[0152] Therefore, by using blockchain technology to build a decentralized database, all transaction records, contract terms, and execution status of state-owned assets will be stored on the blockchain, which can be viewed by anyone, ensuring the immutability and transparency of the data.

[0153] Step 206: Execute the contract document according to the preset smart contract in the blockchain and generate execution result information; wherein, the execution result information is used to indicate the actual execution data of each stage of the contract document.

[0154] In one example, step 206 includes: executing the signed contract file according to the preset smart contract in the blockchain, and during the execution process, monitoring and verifying the contract execution status and abnormal transactions to obtain monitoring result information; if the monitoring result information indicates that there is an abnormal situation, sending a prompt message to the preset regulatory system; and generating execution result information based on the contract execution status and abnormal transactions.

[0155] For example, electronic devices automatically execute contract terms through smart contracts in the blockchain, such as automatically calculating fees and distributing profits. During execution, the contract execution status and any abnormal transactions are monitored and verified on regulatory nodes, yielding monitoring results. If the monitoring results indicate an anomaly, a notification is sent to the pre-set regulatory system, meaning that the regulator is immediately notified upon detection of an anomaly. Based on the contract execution status and any abnormal transactions, execution result information is generated. Therefore, by automatically executing contract terms through smart contracts, such as asset transfers and profit distribution, manual intervention is reduced, management costs are lowered, and management efficiency is improved.

[0156] Step 207: If a dispute is detected during the execution of the signed contract documents, the dispute will be arbitrated according to the preset arbitration rules and supporting documents of the contract documents, and the arbitration result information will be generated.

[0157] For example, when an electronic device detects a dispute arising during the execution of a signed contract, it provides online arbitration services. Based on preset arbitration rules and supporting documents of the signed contract, it arbitrates the dispute and quickly provides the arbitration result. The supporting documents of the signed contract serve as actual evidence. Furthermore, the electronic device can perform data analysis on the executed signed contract data, generating statistical reports and trend analysis data, thereby providing decision-makers with reference information and helping to optimize the allocation and management strategies of state-owned assets.

[0158] For example, the electronic device displays a user interface, and within the contract dispute module's user interface, an intuitive search interface is provided. Users can enter keywords such as contract number, party names, disputed matters, document types, etc., or they can select specific filter criteria, such as time range, document status, etc., to accurately locate the required document evidence.

[0159] When a user submits a search request, the electronic device, based on the user's input keywords and filtering criteria, uses intelligent search algorithms to search the index structure, enabling it to quickly locate the blockchain block and storage location of documents related to a specific contract dispute. The search algorithm can incorporate natural language processing techniques to perform semantic analysis on keywords, improving search accuracy. For example, it can semantically match fuzzy keywords entered by the user with metadata in the index to identify the most relevant documents.

[0160] After the search algorithm finds relevant document evidence, it sorts the search results based on factors such as relevance to the search keywords, document importance, and chronological order. On the user interface, the search results are displayed in a clear list or visualization, providing users with basic document information such as filename, file type, document summary, and relevant contract information, allowing users to quickly understand the document content and select the specific document they wish to view.

[0161] Furthermore, before users search for document evidence, their identities are verified through a digital identity authentication mechanism on the blockchain. Only authorized users can access and search for document evidence related to a specific contract dispute. User permission information is stored on the blockchain, ensuring the security and immutability of permission management. Detailed access control policies are formulated based on user roles and permissions. For example, the two parties to a contract may have different permissions; one party may be able to view all disputed document evidence, while the other party may only be able to view some publicly available documents. For document evidence involving trade secrets or sensitive information, stricter access permissions are set, allowing only specific authorized personnel to access it. Finally, user document evidence search behavior on the blockchain can be security audited and recorded, including search keywords, search time, and accessed documents. These audit records are stored on the blockchain as immutable evidence of user operations, allowing for traceability and review when needed, ensuring that user search behavior complies with compliance requirements and access control policies.

[0162] Therefore, the regulatory nodes are controlled by a dedicated regulatory department, which is responsible for monitoring the system's operation and resolving disputes through online arbitration services to ensure that contract execution complies with legal and regulatory requirements.

[0163] In this embodiment, a contract document is generated in response to an editing operation. The contract document undergoes compliance verification based on the legal clause rules in the preset verification rules information, generating legal clause result information in the verification result information. Similarly, the contract document undergoes compliance verification based on the business clause rules in the preset verification rules information, generating business clause result information in the verification result information. A signed contract document is obtained in response to a signing operation; the signing operation includes operations initiated by the user on the electronic device side and operations initiated by the user's trading partner. If the verification result information indicates that the contract document is correct, the contract document is sent and stored in a preset blockchain. The contract document is executed according to a preset smart contract in the blockchain, generating execution result information; this execution result information indicates the actual execution data at each stage of the contract document. If a dispute is detected during the execution of the signed contract document, the dispute is arbitrated according to preset arbitration rules information and supporting documents of the contract document, generating arbitration result information. Therefore, by using blockchain technology, leveraging its characteristics of immutability, decentralization, and transparency, a new solution is provided for the supervision of state-owned assets. Through compliance verification, the legality and accuracy of contract documents are guaranteed, aiming to improve the management efficiency and transparency of state-owned assets, reduce management costs, and ensure the legality and security of asset transactions, thereby addressing the problem of low efficiency in contract supervision under existing technologies.

[0164] Figure 3 A flowchart illustrating another method for processing contract documents provided in this application is shown below. Figure 3 As shown, the method includes: a user identity authentication module, a contract template generation module, a contract editing and signing module, a contract storage and management module, a contract execution and monitoring module, a contract dispute resolution module, and a data analysis and reporting module.

[0165] The platform comprises the following modules: 1. User Identity Authentication Module: Utilizing digital certificates and biometric technologies to ensure the authenticity and reliability of user identities. 2. Contract Template Generation Module: Providing standardized contract templates, allowing users to select and customize different templates as needed. 3. Contract Editing and Signing Module: Users can directly edit contract content on the platform, and both parties can electronically sign after confirming accuracy. The signature uses asymmetric encryption technology to ensure its unforgeability. 4. Contract Storage and Management Module: All signed contracts are stored on the blockchain, achieving decentralized storage and preventing data tampering and loss. The platform also provides contract retrieval, update, and termination functions. 5. Contract Execution Monitoring Module: Automatically executing contract terms through smart contracts, such as automatically calculating fees and distributing profits. Real-time monitoring and verification of contract execution and abnormal transactions are conducted at regulatory nodes, and regulatory authorities are immediately notified upon detection of any anomalies. 6. Dispute Resolution Module: Providing online arbitration services when disputes arise during contract execution. A ruling is quickly issued based on pre-set arbitration rules and evidence. 7. Data Analysis and Reporting Module: Analyzes contract data on the platform to generate statistical reports and trend analysis data, providing reference for decision-makers.

[0166] Figure 4 This is a schematic diagram of the structure of a contract document processing device provided in an embodiment of this application, as shown below. Figure 4 As shown, the contract document processing device 30 includes:

[0167] Module 31 is used to generate contract documents in response to editing operations;

[0168] The inspection module 32 is used to perform compliance inspection on the contract documents according to the preset inspection rule information and generate inspection result information; wherein, the preset inspection rule information is the clause rule information for inspecting the clauses in the contract documents;

[0169] The sending module 33 is used to send and store the contract document in a preset blockchain if the inspection result information indicates that the contract document is correct.

[0170] The execution module 34 is used to execute the contract document according to the preset smart contract in the blockchain and generate execution result information; wherein, the execution result information is used to indicate the actual execution data of each stage of the contract document.

[0171] The apparatus in this embodiment can execute the technical solutions in the above method. Its specific implementation process and technical principles are the same, and will not be repeated here.

[0172] Figure 5 This is a schematic diagram of the structure of another contract document processing apparatus provided in an embodiment of this application. Figure 4 Based on the illustrated embodiments, as Figure 5 As shown, the inspection module 32 includes:

[0173] The first inspection unit 321 is used to perform compliance inspection on the contract documents according to the legal clause rule information in the preset inspection rule information, and generate the legal clause result information in the inspection result information.

[0174] The second inspection unit 322 is used to perform compliance inspection on the contract documents according to the business clause rule information in the preset inspection rule information, and generate the business clause result information in the inspection result information.

[0175] In one example, the legal clause and rule information includes a pre-set legal clause template library, a pre-set legal and regulatory database, and a pre-set legal analysis system;

[0176] The first inspection unit 321 is specifically used for:

[0177] The clauses in the contract document are compared and verified with the standard clauses in the preset legal clause template library to generate the first legal clause result information in the verification result information; the first legal clause result information includes whether the clauses in the contract document are missing or incorrect;

[0178] The clauses in the contract document are entered into a pre-set legal database to perform compliance checks on the clauses, generating a second legal clause result information in the check result information; the second legal clause result information includes whether the clauses in the contract document comply with the pre-set legal database.

[0179] The clauses in the contract documents are input into a pre-set legal analysis system for high-risk testing, generating third-party legal clause result information in the test results. The third-party legal clause result information includes dangerous clauses in the contract documents whose risk level is higher than the pre-set risk threshold, as well as modification suggestions for the dangerous clauses.

[0180] In one example, the business terms and rules information includes a pre-defined industry standard rule base and pre-defined contract business rules information;

[0181] The second inspection unit 322 is specifically used for:

[0182] The terms in the contract document are matched and verified against industry standards in a pre-defined industry standard rule base to generate the first business terms result information in the verification result information; the first business terms result information includes whether the terms in the contract document comply with industry standards.

[0183] Based on the preset contract business rules information, the clauses in the contract documents are subjected to compliance verification processing, and the second business clause result information is generated in the verification result information.

[0184] The data involved in the contract documents is compared and verified with the actual data in the electronic device to generate the third business clause result information in the verification result information; the third business clause result information includes whether the data involved in the contract documents is consistent with the actual data, and the erroneous data that occurs when there is a discrepancy.

[0185] In one example, the device is also specifically used for:

[0186] In response to a signature operation, the signed contract document is obtained; the signature operation includes operations initiated by the user on the electronic device side and operations initiated by the user's trading partner.

[0187] Execution module 34 is specifically used for:

[0188] Based on the pre-set smart contract in the blockchain, the signed contract document is executed, and during the execution process, the contract execution status and any abnormal transactions generated are monitored and verified to obtain monitoring result information;

[0189] If the monitoring results indicate an anomaly, a notification is sent to the pre-set monitoring system; and execution result information is generated based on the contract execution status and any abnormal transactions.

[0190] In one example, the sending module 33 includes:

[0191] Hash unit 331 is used to perform hash processing on each contract file if the verification result information indicates that the contract file is correct, and obtain a hash value.

[0192] Extraction unit 332 is used to extract key data from the pre-set key data of the contract documents to obtain key data;

[0193] Sending unit 333 is used to send and store the contract document, the hash value of the contract document, and the key data of the contract document into a preset blockchain.

[0194] In one example, the sending unit 333 is specifically used for:

[0195] Determine the type of contract document;

[0196] Identify the storage node in the pre-defined blockchain that corresponds to the type;

[0197] Use the hash value and key data of the contract documents as index data;

[0198] Based on a pre-defined distributed hash table, each contract file and its index data are stored on different storage nodes in the blockchain.

[0199] In one example, module 31 is generated, specifically for:

[0200] In response to the selection of a preset contract template, the target template is identified and displayed;

[0201] Generate contract documents in response to editing operations on the target template.

[0202] In one example, the device is also specifically used for:

[0203] If a dispute arises during the execution of a signed contract document, the dispute will be arbitrated based on the preset arbitration rules and supporting documents of the contract document, and an arbitration result will be generated.

[0204] The apparatus in this embodiment can execute the technical solutions in the above method. Its specific implementation process and technical principles are the same, and will not be repeated here.

[0205] It should be noted that the division of the various modules in the above device is merely a logical functional division. In actual implementation, they can be fully or partially integrated into a single physical entity, or they can be physically separated. These modules can be implemented entirely in software via processing element calls; they can be fully implemented in hardware; or some modules can be implemented in software via processing element calls, while others are implemented in hardware. Each module can be a separate processing element, or it can be integrated into a chip within the device. Alternatively, it can be stored as program code in the device's memory, and its functions can be called and executed by a processing element. Furthermore, these modules can be fully or partially integrated together, or they can be implemented independently. The processing element here can be an integrated circuit with signal processing capabilities. During implementation, each step of the above method or each of the above modules can be completed through integrated logic circuits in the processor element or through software instructions.

[0206] Figure 6 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Figure 6 As shown, the electronic device 40 may include: a transceiver 41, a processor 42, and a memory 43.

[0207] Processor 42 executes computer execution instructions stored in memory, causing processor 42 to perform the scheme in the above embodiments. Processor 42 can be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it can also be a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components.

[0208] The memory 43 is connected to the processor 42 via the system bus and completes communication between them. The memory 43 is used to store computer program instructions.

[0209] Transceiver 41 can be used to obtain the task to be run and the configuration information of the task to be run.

[0210] The system bus can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. The system bus can be divided into address bus, data bus, control bus, etc. For ease of representation, only one thick line is used in the diagram, but this does not indicate that there is only one bus or one type of bus. Transceivers are used to enable communication between database access devices and other computers (e.g., clients, read-write libraries, and read-only libraries). Memory may include random access memory (RAM) and may also include non-volatile memory.

[0211] The electronic device provided in this application embodiment can be the terminal device described in the above embodiments.

[0212] This application also provides a chip for executing instructions, which is used to execute the technical solution of the contract document processing method in the above embodiments.

[0213] This application also provides a computer-readable storage medium storing computer instructions that, when executed on a computer, cause the computer to perform the technical solution of the contract document processing method described in the above embodiments.

[0214] This application also provides a computer program product, which includes a computer program stored in a computer-readable storage medium. At least one processor can read the computer program from the computer-readable storage medium, and when the at least one processor executes the computer program, it can implement the technical solution of the contract document processing method in the above embodiments.

[0215] In the several embodiments provided in this application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are merely illustrative; for instance, the division of modules is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple modules may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be indirect coupling or communication connection through some interfaces, devices, or modules, and may be electrical, mechanical, or other forms.

[0216] The modules described as separate components may or may not be physically separate. The components shown as modules may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to implement the solution of this embodiment according to actual needs.

[0217] Furthermore, the functional modules in the various embodiments of this application can be integrated into one processing unit, or each module can exist physically separately, or two or more modules can be integrated into one unit. The unit composed of the above modules can be implemented in hardware or in the form of hardware plus software functional units.

[0218] The integrated modules described above, implemented as software functional modules, can be stored in a computer-readable storage medium. These software functional modules, stored in a storage medium, include several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) or processor to execute some steps of the methods of the various embodiments of this application.

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

[0220] The memory may include high-speed RAM, and may also include non-volatile storage (NVM), such as at least one disk storage device, and may also be a USB flash drive, external hard drive, read-only memory, disk or optical disc, etc.

[0221] 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.

[0222] The aforementioned storage medium can be implemented from 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 storage medium can be any available medium accessible to general-purpose or special-purpose computers.

[0223] An exemplary storage medium is coupled to a processor, enabling the processor to read information from and write information to the storage medium. Alternatively, the storage medium can be an integral part of the processor. The processor and storage medium can reside in an Application Specific Integrated Circuit (ASIC). Alternatively, the processor and storage medium can exist as discrete components in an electronic control unit or main control device.

[0224] Those skilled in the art will understand that all or part of the steps of the above-described method embodiments can be implemented by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When executed, the program performs the steps of the above-described method embodiments; and the aforementioned storage medium includes various media capable of storing program code, such as ROM, RAM, magnetic disks, or optical disks.

[0225] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some or all of the technical features therein. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of this application.

Claims

1. A method for processing contract documents, characterized in that, Applied to electronic devices, including: In response to editing operations, generate contract documents; According to the preset inspection rule information, the contract document is subjected to compliance inspection processing to generate inspection result information; wherein, the preset inspection rule information is the clause rule information for inspecting the clauses in the contract document; If the verification result information indicates that the contract document is correct, the contract document is sent and stored in a preset blockchain; and the contract document is executed according to the preset smart contract in the blockchain to generate execution result information; wherein, the execution result information is used to indicate the actual execution data of each stage of the contract document.

2. The method according to claim 1, characterized in that, The step of performing compliance inspection on the contract documents according to preset inspection rule information and generating inspection result information includes: Based on the legal clause rules information in the preset inspection rules information, the contract documents are subjected to compliance inspection processing, and the legal clause result information in the inspection result information is generated; Based on the business terms rules information in the preset inspection rules information, the contract documents are subjected to compliance inspection processing, and the business terms result information in the inspection result information is generated.

3. The method according to claim 2, characterized in that, The legal clause and rule information includes a preset legal clause template library, a preset legal and regulatory database, and a preset legal analysis system; The process of performing compliance inspection on the contract document based on the legal clause rule information in the preset inspection rule information, and generating legal clause result information in the inspection result information, includes: The clauses in the contract document are compared and verified with standard clauses in a preset legal clause template library to generate the first legal clause result information in the verification result information; wherein, the first legal clause result information includes whether the clauses in the contract document are missing or incorrect; The clauses in the contract document are input into a preset legal database to perform compliance verification on the clauses, generating a second legal clause result information in the verification result information; wherein, the second legal clause result information includes whether the clauses in the contract document comply with the preset legal database. The clauses in the contract document are input into a preset legal analysis system for high-risk testing, generating third legal clause result information in the test results information; wherein, the third legal clause result information includes dangerous clauses in the contract document whose risk level is higher than a preset risk threshold, and modification suggestions for the dangerous clauses.

4. The method according to claim 2, characterized in that, The business terms and rules information includes a pre-set industry standard rule base and pre-set contract business rules information; The step of performing compliance inspection on the contract document based on the business clause rule information in the preset inspection rule information, and generating business clause result information in the inspection result information, includes: The terms in the contract document are matched and verified against industry standards in a pre-defined industry standard rule base to generate the first business terms result information in the verification result information; wherein, the first business terms result information includes whether the terms in the contract document comply with industry standards; Based on preset contract business rules information, the clauses in the contract document are subjected to compliance verification processing, and the second business clause result information is generated in the verification result information. The data involved in the contract document is compared and verified with the actual data in the electronic device to generate the third business clause result information in the verification result information; wherein, the third business clause result information includes whether the data involved in the contract document is consistent with the actual data, and the erroneous data that occurs when they are inconsistent.

5. The method according to claim 1, characterized in that, The method further includes: In response to a signature operation, the signed contract document is obtained; wherein, the signature operation includes operations initiated by the user on the electronic device side and operations initiated by the user's trading partner; The step of executing the contract file according to the preset smart contract in the blockchain and generating execution result information includes: According to the preset smart contract in the blockchain, the signed contract file is executed, and during the execution process, the contract execution status and any abnormal transactions generated are monitored and verified to obtain monitoring result information; If the monitoring results indicate an abnormal situation, a prompt message is sent to the preset monitoring system; and execution result information is generated based on the contract execution status and the abnormal transactions generated.

6. The method according to claim 1, characterized in that, If the inspection result indicates that the contract document is correct, then the contract document is sent and stored in a preset blockchain, including: For each contract document, if the verification result information indicates that the contract document is correct, then the contract document is hashed to obtain a hash value; Data extraction is performed on the preset key data in the contract document to obtain the key data; The contract document, its hash value, and key data are all sent to and stored in a pre-defined blockchain.

7. The method according to claim 6, characterized in that, The contract document, its hash value, and key data are all sent and stored in a pre-defined blockchain, including: Determine the type of the contract document; Determine the storage node in the preset blockchain that corresponds to the type; The hash value and key data of the contract document are used as index data; Based on a pre-defined distributed hash table, each contract file and its index data are stored on different storage nodes in the blockchain.

8. The method according to claim 1, characterized in that, The process of generating a contract document in response to an editing operation includes: In response to the selection of a preset contract template, the target template is identified and displayed; In response to an editing operation on the target template, a contract document is generated.

9. The method according to any one of claims 1-8, characterized in that, The method further includes: If a dispute is detected during the execution of the contract documents, the dispute will be arbitrated according to the preset arbitration rules and supporting documents of the contract documents, and an arbitration result will be generated.

10. A contract document processing apparatus, characterized in that, include: The generation module is used to generate contract documents in response to editing operations; The inspection module is used to perform compliance inspection on the contract document according to preset inspection rule information and generate inspection result information; wherein, the preset inspection rule information is the clause rule information for inspecting the clauses in the contract document; The sending module is used to send and store the contract document in a preset blockchain if the inspection result information indicates that the contract document is correct. The execution module is used to execute the contract file according to the preset smart contract in the blockchain and generate execution result information; wherein, the execution result information is used to indicate the actual execution data of each stage of the contract file.

11. 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-9.

12. 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-9.

13. 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-9.

Images