Removal / cancellation checking system and method for electronic contract file

Abstract

The invention discloses a de-checking method for an electronic contract file, which comprises the following steps of: receiving the electronic contract file, performing information verification, generating a de-business code and adding the de-business code into the contract file if the de-business code does not exist in the electronic contract file, and adding a two-dimensional code and a checking address link into the contract file, solidifying the current file state information to generate a new layout file; if the electronic contract file has a service release code, the file verification unit selects a service type and queries a release record; recording change state information of the state of the electronic contract file, and performing chain storage and solidification on the change state information; the identity verification module is used for carrying out multi-factor identity verification on the contract relieving applicant; the two-dimensional code associates the electronic contract file state and the service release code in real time, selects a service type, and queries and displays a release record; and batch de-signing and state updating of the electronic contract file are provided. It is ensured that the current state of the signed contract file can be determined, and legal risks caused by poor information of all parties are avoided.

Description

Technical Field

[0001] The present invention relates to the field of artificial intelligence technology, and in particular to a method for checking the cancellation / cancellation of an electronic contract document. Background Art

[0002] With the implementation and enforcement of the "Electronic Signature Law" for many years, multiple electronic signature products have been stored, and the application of electronic signatures has become very popular in many industries such as real estate, finance, government affairs, and education. The application scenarios of electronic documents (including electronic contracts, electronic receipts, electronic certificates, etc.) have involved all aspects of life.

[0003] Compared with traditional paper documents, electronic documents have many characteristics, among which the ability to be copied and reproduced is very prominent. Traditional paper documents can be physically recycled, destroyed, stamped with a seal of invalidation, etc., but the ability to copy and reproduce electronic documents makes it difficult to trace the final effectiveness of electronic documents.

[0004] When it is necessary to terminate or cancel a contract that has already taken effect, traditional paper contracts are very convenient to cancel because the number of copies is fixed and they can be physically destroyed. However, a signed and valid electronic contract can be saved by copying and duplicating, and is indistinguishable from the original contract. When a dispute occurs, Party A and Party B will each produce the contract before and after the cancellation as evidence. Both are real electronic contracts, but one is valid and the other is invalid. However, lawyers and judges cannot quickly determine which is the invalidated and which is the valid electronic contract. They must supplement multiple proof materials or spend more time on verification afterwards, which wastes resources and reduces trial efficiency.

[0005] For example, Party A and Party B have signed an electronic contract A. After the contract is signed, during the execution process, due to changes in business conditions, if one party proposes to terminate the original contract A, the current processing method is to sign a new termination agreement B and mark the original contract A as invalid. However, if the electronic contract copied by the user during the validity period of Contract A cannot be traced later, when a dispute occurs, one party presents a copy of Contract A within the validity period, which has no invalid mark and is no different from the original contract. Except for judging by time, it is impossible to determine whether A is valid. For electronic files, this is easy to achieve by modifying the time of the electronic file.

[0006] If a complete description of the business is required, two contracts A and B are required. If a dispute occurs, one party can only provide a copy of the validity period of Contract A as evidence, and it is difficult for the verification party to prove that Contract A is an invalid electronic contract. Due to the limitations of verification methods and conditions, Contract A may still be considered to be a real and valid electronic contract, and the user who provides Contract B needs to provide further materials to prove the invalidity of Contract A, resulting in information asymmetry, great waste of resources and inconvenience in use.

[0007] Publication number: CN107316182A, name "A method and system for generating an electronic contract evidence chain", performs the following steps: collect and generate electronic files of headshots of personnel at the contract signing site and electronic files of materials; after the electronic files are reviewed, they are archived in a database; a HASH value corresponding to each electronic file is generated, and the HASH value corresponding to each electronic file is encrypted by an encryption algorithm and then merged to generate a corresponding QR code; each electronic file is merged to generate a layout file, and the unique contract ID of the electronic contract and the QR code are inserted into the layout file; a timestamp and a digital signature are added to the layout file to form a formal electronic contract and publish it, and both parties to the contract obtain the corresponding encryption key. The method for generating an electronic contract evidence chain of the present invention ensures the integrity, authenticity and verifiability of the electronic contract evidence chain.

[0008] Publication number: Name "A method for invalidating an electronic contract", provides a method for invalidating an electronic contract, including the following steps: when the electronic signature system creates a user, in addition to creating a digital certificate and an ordinary electronic seal, it also creates and generates an "invalidated" electronic seal; the user logs in to the electronic signature system, uploads the electronic contract, creates a signing process, and specifies that the electronic contract is signed by each signatory; to execute the electronic contract invalidation, each signatory of the electronic contract needs to take turns to stamp the "invalidated" electronic seal through digital signature; all signatories of the electronic contract unanimously stamp the "invalidated" electronic seal, indicating that the contract has been invalidated. Regardless of how many intermediate signed documents are formed before the electronic contract is fully signed; or multiple electronic copies are generated by copying, the status of the electronic contract can be judged through the system's traceability chain.

[0009] Publication number: CN111429113A, a method for withdrawing and returning an electronic contract. It includes: checking and recording the issuance order requirements, signing validity period and contract status of the contract document; performing withdrawal and return logic control according to the issuance order, signing validity period, contract status and next operation step; when the contract initiator or recipient withdraws or returns the electronic contract, submits the corresponding reasons and explanations. The electronic contract withdrawal and return management method can reflect the signing intention between the parties who sign the contract online, and improve the signing validity of the electronic contract. Combined with the issuance order requirements, signing validity period and signing progress of the contract document of the contract initiator, it provides withdrawal and return management of the contract offer and commitment before the electronic contract is signed, and provides classification management of the withdrawn and returned contract documents.

[0010] Although the above-mentioned existing technologies have added a contract ID and a QR code to the contract termination document, affixed a cancellation mark, etc., and are capable of submitting corresponding reasons and explanations, they lack a unified and tamper-proof recording mechanism, and still fail to solve problems such as the copying and tampering of electronic contracts, the verification efficiency in legal disputes, and the lack of contract changes and status management. Summary of the invention

[0011] In view of this, the present invention tracks and processes the entire process of signing and using electronic contract documents, and records the subsequent changes to the electronic contract documents that are valid after signing, so as to facilitate inquiries about changes to the electronic documents. For example, the termination information (such as abolition, negotiated termination, unilateral termination, abandonment, etc.) of the electronic contract documents signed and confirmed by both parties is truthfully recorded. After the electronic contract document takes effect, the changes and termination records of the electronic contract document after signing can be quickly queried and displayed through the contract document, so as to resolve the information gap generated during the signing and use of the electronic contract documents, which results in the problem of being unable to promptly prove the validity or invalidity of the contract documents provided by oneself in dispute resolution.

[0012] Based on the first aspect of the present invention, a release inspection system for electronic contract documents is proposed, including a file receiving and verification module, a status update and solidification module, an identity authentication module, a query and display module, and a batch processing module. The file receiving and verification module receives the electronic contract document and performs information verification. If there is no release business code in the electronic contract document, the file marking unit generates a release business code and adds it to the contract document, and adds a QR code and a verification address link to the contract document. The release file generation unit solidifies the current file status information and generates a new format file. If there is a release business code in the electronic contract document, the file verification unit selects the business type and queries the release record. The status update and solidification module records the change status information of the electronic contract document status, and performs chain storage and solidification on the change record. The identity authentication module performs multi-factor identity authentication on the applicant for contract release. The query and display module associates the electronic contract document status with the release business code in real time, selects the business type, and queries and displays the release record. The batch processing module provides batch release signatures and status updates for electronic contract documents.

[0013] Further preferably, verifying the identity information of the release applicant includes: searching for the effective contract document signed by the applicant through the release business number, extracting the electronic signature of the applicant from the effective contract document and the contract release application document for handwriting comparison, if the electronic signature handwriting is the same, the release applicant is a qualified applicant.

[0014] Further preferably, the generation of a QR code to real-time associate the electronic contract file status with the business code includes: adding the release business code to the contract release file in the form of a QR code and encrypting it, generating an encrypted release file containing the business code and encryption information, adding a release timestamp to the encrypted release file, generating a random number based on a release file system identifier, and calculating a unique ID code for the release file based on the random number.

[0015] Further preferably, the receiving of the electronic contract file and performing information verification includes: the file verification module calculates the hash value of the original signed contract file, the hash value of the terminated contract file, the hash value of the electronic signature in the original electronic contract file and the file in the termination application, and detects the integrity, digital certificates, and legitimacy of digital handwriting signatures of files stored in the cloud mode and the privatized local deployment mode by comparing the hash value of the contract file and the hash value of the electronic signature before and after the contract is terminated.

[0016] Further preferably, the calculation of the unique ID code of the release file based on the random number includes reading the content of the contract file to be released, obtaining the time when the file release request was generated as the current timestamp, and using the private key of the contract signing system to generate a digital signature, specifically including: calculating the hash value H(F) of the contract file F according to the formula: H(F)=SHA-256(F), generating the unique identifier UID of the contract file according to the hash value and timestamp of the contract file according to the formula: UID=SHA-256(H(F)+T), sequentially concatenating the contract signing system identifier S, the unique identifier UID, the timestamp T, the hash value H(F) of the contract file, and the business code string R to form an original string R; signing R with the private key of the contract signing system to generate a digital signature σ; and concatenating the original string R and the digital signature σ to form a business code for releasing the contract file.

[0017] Further preferably, the receiving of the electronic contract file and information verification includes: the file verification module decomposes the release business code BC, extracts from BC according to the business code combination rule: system identifier S′, file unique identifier UID′, timestamp T′, file hash value H′(F), digital signature σ′; uses the same algorithm as that for generating the business code to calculate the hash value H′(F) of the content of the release contract file, wherein, H′(F)=SHA-256(F); compare H(F) and H′(F). If they match, the verification is successful. Otherwise, a prompt “the file content has been tampered with” is sent. According to the extracted timestamp T and the hash value H′(F) of the contract file, the unique identifier UID′ is calculated according to the formula UID′=SHA-256(H′(F)+T′), and compared with the unique identifier UID of the contract file. If they are the same, they match. Otherwise, a prompt “the file unique identifier is invalid” is sent. According to the system identifier S′, the file unique identifier UID′, the timestamp T′, and the file hash value H′(F) obtained from the contract cancellation file, the business coding string is combined. The specific combination method can be: R′=S′+"−"+UID′+"−"+T′+"−"+H′(F) Obtain the business code and use the public key of the file signing system to verify the signature. If the verification is successful, it means the signature is valid, otherwise a "signature invalid" prompt is sent; verify through the registration center whether the system identifier S' comes from a trusted system. If it comes from a trusted system, the verification is successful, otherwise a "source system invalid" prompt is sent.

[0018] Further preferably, a state update data record structure of chain storage entries is used to record the state of the terminated or invalidated contract file, including: the unique identifier of the file File ID, the contract change type Change Type, the change time Timestamp, the change reason Reason, the hash value H of the last recorded stateprev , the hash value H of the current record status current , link the previous state and the current state to form a new chain, calculate the hash value before and after the state change and write it into the blockchain storage record, where, according to the formula: H current = SHA-256(File ID+Change Type+Timestamp+Reason+H prev ) Calculate the hash value H of the current record state current。

[0019] Based on the second aspect of the present application, a method for checking the release of an electronic contract document is proposed, including receiving an electronic contract document and performing information verification, generating a contract release business code for the electronic contract document to be released / invalidated, and extracting the contract release business code for the electronic contract document that has been released / invalidated; if there is no release business code, performing multi-factor identity authentication on the applicant for contract release, generating a release business code and adding it to the contract document, and adding a QR code and a verification address link to the contract document; solidifying the current file status information and generating a new layout file; if there is a release business code, the file verification unit selects the business type and queries the release record; recording the change status information of the electronic contract document status, and chain-storing and solidifying the change record; query and display module: the QR code is used to associate the electronic contract document status with the release business code in real time, the business type is selected, and the release record is queried and displayed; batch processing module: provides batch release signing and status update of electronic contract documents.

[0020] Further preferably, verifying the identity information of the release applicant includes: searching for the effective contract document signed by the applicant through the release business number, extracting the electronic signature of the applicant from the effective contract document and the contract release application document for handwriting comparison, if the electronic signature handwriting is the same, the release applicant is a qualified applicant.

[0021] Further preferably, the generation of a QR code to real-time associate the electronic contract file status with the business code includes: adding the release business code to the contract release file in the form of a QR code and encrypting it, generating an encrypted release file containing the business code and encryption information, adding a release timestamp to the encrypted release file, generating a random number based on a release file system identifier, and calculating a unique ID code for the release file based on the random number.

[0022] Further preferably, the receiving of the electronic contract file and performing information verification includes: the file verification module calculates the hash value of the original signed contract file, the hash value of the terminated contract file, the hash value of the electronic signature in the original electronic contract file and the file in the termination application, and detects the integrity, digital certificates, and legitimacy of digital handwriting signatures of files stored in the cloud mode and the privatized local deployment mode by comparing the hash value of the contract file and the hash value of the electronic signature before and after the contract is terminated.

[0023] Further preferably, the calculation of the unique ID code of the release file based on the random number includes reading the content of the contract file to be released, obtaining the time when the file release request was generated as the current timestamp, and using the private key of the contract signing system to generate a digital signature, specifically including: calculating the hash value H(F) of the contract file F according to the formula: H(F)=SHA-256(F), generating the unique identifier UID of the contract file according to the hash value and timestamp of the contract file according to the formula: UID=SHA-256(H(F)+T), sequentially concatenating the contract signing system identifier S, the unique identifier UID, the timestamp T, the hash value H(F) of the contract file, and the business code string R to form an original string R; signing R with the private key of the contract signing system to generate a digital signature σ; and concatenating the original string R and the digital signature σ to form a business code for releasing the contract file.

[0024] Further preferably, the receiving of the electronic contract file and information verification includes: the file verification module decomposes the release business code BC, and extracts from BC according to the business code combination rule: system identifier S′, file unique identifier UID′, timestamp T′, file hash value H′(F), digital signature σ′; uses the same algorithm as that for generating the business code to calculate the hash value H′(F) of the content of the release contract file: H′(F)=SHA-256(F); compares H(F) and H′(F), if they match, the verification is successful, otherwise a prompt "the file content has been tampered with" is sent; calculates the unique identifier UID′ according to the formula UID′=SHA-256(H′(F)+T′) based on the extracted timestamp T and the contract file hash value H′(F), and compares it with the contract file unique identifier UID, if they are the same, they match, otherwise a prompt "the file unique identifier is invalid" is sent; combines the business code string based on the system identifier S′, file unique identifier UID′, timestamp T′, and file hash value H′(F) obtained from the release contract file, and the specific combination method can be: R′=S′+"−"+UID′+"−"+T′+"−"+H′(F), obtain the business code, use the file signing system public key to verify the signature. If the verification is successful, it means the signature is valid, otherwise a "signature invalid" prompt is sent; verify through the registration center whether the system identifier S′ comes from a trusted system. If it comes from a trusted system, the verification is successful, otherwise a "source system invalid" prompt is sent.

[0025] Further preferably, the state update data record structure of the chain storage entry is used to record the state of the terminated or invalidated contract file, including: the unique identifier of the file File ID, the contract change type Change Type, the change time Timestamp, the change reason Reason, the hash value Hprev of the previous record state, the hash value Hcurrent of the current record state, linking the previous state and the current state to form a new chain, calculating the hash values ​​before and after the state change and writing them into the blockchain storage record, wherein, according to the formula: Hcurrent = SHA-256(File ID+Change Type+Timestamp+Reason+Hprev) Calculate the hash value Hcurrent of the current record state.

[0026] The present invention manages and traces the electronic contract documents that are to be cancelled after signing. By assigning a unique code to the signed electronic contract document, a unique code is generated for each electronic contract, and the code cannot be tampered with, thereby achieving the identity uniqueness and traceability of the electronic contract. The operation traces during the signing and cancellation of the electronic contract document can be traced through the code. The cancellation record is solidified, and through the chain storage and solidification mechanism, the cancellation record cannot be maliciously tampered with, meeting the inspection requirements as evidence in subsequent dispute resolution. File version control, when the signed electronic contract document is abolished or cancelled, a new file version is generated, and the original contract document is cancelled and marked at the same time, ensuring that the current status of the document can be clearly understood when the document is obtained after the contract document is signed, avoiding legal risks caused by information asymmetry for all parties. BRIEF DESCRIPTION OF THE DRAWINGS

[0027] Figure 1 The method for releasing and checking the electronic contract document in this exemplary embodiment; like Figure 2 Shown is a schematic diagram of the process of verifying file information in an exemplary embodiment of the present application. DETAILED DESCRIPTION

[0028] After the electronic document contract is signed, for example, both parties have signed an electronic contract A. After the contract is signed, the original contract A needs to be terminated due to changes in the business. The current processing method is to sign a new termination agreement B. If the invalidated electronic contract A is copied multiple times during the validity period and used later, it will cause losses and it will be difficult to track it in the judicial litigation stage. Two contracts, A and B, are required to fully describe the business activities. Since electronic documents are easy to be tampered with, if one party modifies the signing time of the contract, it will be very difficult to determine which contract is true and valid. If a dispute occurs, one party can only provide contract A for judicial prosecution. When the judicial institution obtains contract A, it cannot accurately verify whether the contract is true and valid, which is easy to produce information asymmetry. If the other party presents contract B, if one party has objections, judicial appraisal and other activities are required to determine which contract is the valid contract. This will cause instability in the promotion and use of electronic contracts and greatly waste social resources.

[0029] The present invention proposes a method for cancelling and checking electronic contract documents, which effectively manages the cancellation process of signed valid electronic contract documents, and facilitates indexing of cancellation matters by uniquely encoding electronic documents and using synthetic codes such as the private key of the contract signing system and the unique file identifier; real-time data recording solves the problem of data source during query; adopts data synchronization, builds a centralized system, and implements it in a centralized and distributed manner to solve the problem of privacy. Trace the cancellation status of electronic documents to ensure the security and integrity of the documents.

[0030] The method for releasing and checking electronic contract documents proposed in this application is intended to solve the following main problems existing in the current management and use of electronic contracts: The problem of copying and tampering of electronic contracts. The copyable and tamperable nature of electronic documents makes it impossible to simply control their effectiveness through physical means. For example, when an electronic contract needs to be terminated or revoked, if the contract document is copied, the original contract and the terminated contract may exist at the same time, making it difficult to quickly verify which one is the valid contract.

[0031] The verification efficiency is low in legal disputes. When a contract dispute occurs, the submitted electronic contract may not have a clear cancellation mark, and additional evidence is required to prove the validity or invalidity of the contract. This verification method is not only time-consuming, but also increases the complexity of legal trials and wastes judicial and social resources.

[0032] There is a lack of change and status management for electronic contracts. The current electronic contract system usually lacks effective management of the subsequent status of the document (such as termination, abolition) after signing, resulting in the inability to trace contract change information and the inability to judge the legality and effectiveness of the document through simple technical means.

[0033] There is a lack of a unified and tamper-proof recording mechanism. The existing method of recording contract status does not have a high degree of anti-tampering capabilities, and cannot guarantee the authenticity and reliability of contract termination or cancellation records, which may lead to the risk of data falsification in legal disputes.

[0034] The present invention uses a unique code to identify contract documents, and generates a unique business code for each electronic contract to ensure the uniqueness and non-tamperability of the contract document, thereby improving the security of the electronic contract document; real-time recording of contract status changes: using a chain storage and solidification mechanism to record changes in the entire life cycle of the contract document from signing to termination, ensuring that the change process is transparent and traceable; a multi-dimensional identity authentication mechanism provides a multi-factor identity authentication method to ensure the legitimacy of the termination applicant, thereby improving the security of the contract termination operation; provides an efficient verification tool to quickly verify the contract status through QR codes, link addresses, etc., to resolve disputes caused by information asymmetry; is compatible with multiple deployment modes, supports cloud and private deployment modes, and meets the needs of different enterprises for data privacy and system integration.

[0035] The signing of existing electronic contract documents has shown a commercial trend. The signing and verification systems for electronic contract documents are deployed in the private domain of the company providing signature services. For the benefit of the enterprise and the data security of customers, the signature service company is usually a closed intranet and will only provide the signatory with the final text after signing. The use and management of the electronic contract documents after signing are in an unconstrained free state. It is very difficult to obtain the status changes of the contract documents after signing.

[0036] The realization of the release and inspection of electronic contract documents includes: document reception and verification, status update and solidification, identity verification, query and display, and batch processing. Document reception and verification module: receives the electronic contract documents to be signed and have been signed, and verifies their integrity and legality, generates or extracts business codes, generates business codes for the electronic contract documents to be signed, and extracts business codes for the signed electronic contract documents; Status update and solidification module: is responsible for recording the change information of the document status, and chain-storing and solidifying the change records; Identity verification module: provides users with multi-factor identity verification to ensure the legitimacy of the applicant for release; Query and display module: supports real-time query of document status through QR code, business code or other methods; Batch processing module: realizes efficient batch operations, including batch signing, release and status update.

[0037] like Figure 1 The figure shows a flow chart of the method for releasing and checking the electronic contract document in the exemplary embodiment of the present application. Specifically, it includes: The electronic contract file is imported, and the electronic contract file information is verified to see if there is a business code for the termination in the file. If there is a business code, select the business type and query the termination record, and display the termination record. At the same time, a termination record is added, and the identity of the contract termination applicant is authenticated. The applicant imports the termination description, and the termination record is solidified and published. If there is no business code, a unique code is generated, a QR code and a verification address are added to the file, the current contract file status information is solidified, and a new layout file is generated.

[0038] The exemplary embodiment of the present application provides a system for releasing and checking electronic contract files, including a file receiving and verification module, a status update and solidification module, an identity verification module, a query and display module, and a batch processing module. The file receiving and verification module also includes: an information verification unit, a file marking unit, a release file generation unit, and a file verification unit. The file receiving and verification module receives the electronic contract file and performs information verification. If there is no release business code in the electronic contract file, the file marking unit generates a release business code and adds it to the contract file, and adds a QR code and a verification address link to the contract file. The release file generation unit solidifies the current file status information and generates a new format file; if there is a release business code in the electronic contract file, the file verification unit selects the business type and queries the release record; the status update and solidification module records the change status information of the electronic contract file status, and performs chain storage and solidification of the change record; the identity verification module performs multi-factor identity verification on the applicant for contract release; the query and display module associates the electronic contract file status with the release business code in real time, selects the business type, and queries and displays the release record; the batch processing module provides batch release signatures and status updates for electronic contract files.

[0039] Receive electronic contract files. When it is necessary to terminate or invalidate an electronic contract that is valid after being signed by all parties to the contract, the file receiving unit receives an electronic contract file to be terminated or invalidated. The received file can be any electronic contract document. Contract information is extracted from the electronic contract file, including signing information, contract terms and related unique identifiers. The historical record of the contract in the system is identified through the unique identifier.

[0040] Compare the signature handwriting of the applicant for contract termination, obtain the applicant's electronic signature in the contract termination application document, search for the contract document signed by the applicant through the contract business number, extract the electronic signature of the signatory in the signed and effective contract document, and compare the handwriting with the electronic signature of the applicant for termination. If they are consistent, agree to terminate or invalidate the contract document application and further verify the contract document.

[0041] like Figure 2 Shown is a schematic diagram of the process of verifying file information in an exemplary embodiment of the present application.

[0042] Verify the integrity and legality of the received electronic contract document information to be terminated. Verification includes checking the legality of the signature, the integrity of the contract, and the authenticity of the contract content to ensure that the document has not been tampered with before the contract is terminated or invalidated.

[0043] The file receiving and verification module verifies the incoming electronic contract files to be terminated signed by different platforms, calculates the source contract file hash, the signed contract file hash, the terminated contract file hash, and the electronic signature hash of the terminated applicant and the contract signatory. Check the integrity of the file through the hash value data of the file before and after the electronic signature and the signature, and detect the legitimacy of the digital certificate and digital handwriting signature. If the electronic signatures of the parties in the electronic contract document are completed by different applications and different signing platforms, the integrity and legitimacy of the file can be verified by testing the digital certificate.

[0044] Check whether the contract document contains the business release code and determine whether the business release code exists.

[0045] The file release system checks the received contract files to be released to see if there is a release business code in the format file. If there is no release business code, it means that the contract file has never been released or invalidated, and a new business code is generated. If there is a release business code, it means that the contract file has been released or processed. The current status is confirmed by querying the release record to prevent repeated operations.

[0046] For the format files that have not been de-coded, a unique code is generated and marked on the file, generating a unique code that is used as an identifier for contract tracing and recording. At the same time, a QR code or link address is added to the file to point to the storage location of the contract file that has been de-coded or cancelled, so as to facilitate the verification of the status of the contract file in the future. This operation provides a convenient query method for subsequent contract tracing and verification.

[0047] Considering that the electronic contract document release system has a cloud mode and a private local deployment mode, a business code is set for each electronic contract document to be released, and the business code is used to verify which electronic contract document release system the electronic contract document comes from. The business code consists of a system identifier, file content, timestamp, and private key. Obtain the contract signing system identifier S, sign the unique identifier of the electronic contract file system, such as UUID or domain name, and calculate the hash value as the contract signing source system identifier. Obtain the unique code File ID of the file marked as F, read the content of the electronic contract file to be released, and obtain the generation time of the contract file as the current timestamp; use the private key of the contract signing system to generate a digital signature. Specifically, the following method can be used to implement it: obtain the electronic contract file F, calculate the 256-bit hash value H(F) of the electronic contract file: H(F)=SHA-256(F); generate the unique identifier UID of the electronic contract file to be released based on the hash value and timestamp of the contract file: UID=SHA-256(H(F)+T); obtain the original business code string R based on the unique identifier UID of the electronic contract file: R=S+"−"+UID+"−"+T+"−"+H(F). Among them, the symbol "−" can be used as a string connection symbol.

[0048] Use the private key of the contract signing system to sign R to generate a digital signature σ: σ=Sign(R). The final business code BC is constructed based on the business code string and the digital signature as follows: BC=R+"−"+σ. This signature is the signature of the digital certificate.

[0049] The business code calculated by the above method is the unique business code of this contract termination document, which ensures the uniqueness of the contract document. Combined with the digital signature, it is also used for the termination operation of files in multiple systems, which can directly and quickly determine and verify the source of the file.

[0050] The verification module obtains the business code BC, file content F, and public key (used to verify the digital signature) of the electronic contract document to ensure that the source of the document is credible, the content is complete, and the code has not been tampered with.

[0051] The verification method of this exemplary embodiment includes: The verification module decomposes the business code BC, and extracts from BC according to the business code combination rules: system identifier S′, file unique identifier UID′, timestamp T′, file hash value H′(F), and digital signature σ′; the file hash value is verified, specifically including: calculating the hash value of the contract file content based on the obtained electronic contract file, using the same calculation formula as that for generating the business code, and calculating and verifying the hash value H′(F) of the contract file content: H′(F)=SHA-256(F).

[0052] Verify the contract file content and compare H(F) and H′(F). If they match, verification succeeds. Otherwise, verification fails and a “file content has been tampered with” prompt is sent.

[0053] Verify the file unique identifier. Calculate the unique identifier UID′ according to the extracted timestamp T and the contract file hash value H(F) according to the formula UID′=SHA-256(H(F)+T′), and compare it with the generated contract unique identifier. If UID and UID′ are the same, they match. Otherwise, the verification fails and a prompt "File unique identifier is invalid" is sent.

[0054] Verify the digital signature: Combine the business code string based on the system identifier S′, file unique identifier UID′, timestamp T′, and file hash value H′(F) obtained from the contract termination document. The specific combination method can be: R′=S′+"−"+UID′+"−"+T′+"−"+H′(F) Get the business code R' and use the public key to verify the signature of R'. If the verification is successful, it means the signature is valid. Otherwise, a "signature invalid" prompt is sent.

[0055] Verify system identifier: Verify whether the system identifier S comes from a trusted system through verification by the registration center or by internal comparison within the system. If so, the verification is successful; otherwise, a prompt "the source system is invalid" is sent.

[0056] Solidify the cancellation or cancellation records. Solidify the cancellation or cancellation records of the contract. The solidification process can ensure the immutability of the records through technologies such as digital signatures or blockchain encryption to ensure the authenticity and reliability of the cancellation or cancellation operation. The state update data record structure of the chain storage entry is used to record the cancellation or cancellation file status, including: the unique identifier of the file File ID, the change type (such as cancellation, cancellation, revision) Change Type, the change time Timestamp, the reason for the change Reason, the hash value of the previous state Hprev, and the hash value of the current state record Hcurrent. Update the cancellation and cancellation status in real time. The status update includes: extracting the previous state hash H of the contract file pre， , calculate the hash H of the current record status of the contract file current , link the previous state and the current state to form a new chain, calculate the hash value before and after the state change and write it into the blockchain storage record. According to the formula: H current = SHA-256(File ID + Change Type + Timestamp + Reason + H prev ) Calculate the current status hash of the contract file to be terminated.

[0057] Among them, the type of termination Change Type includes type tags such as contract cancellation, revision, and termination. Timestamp is the time of the change when the termination application is submitted, which is a timestamp value. Reason is a text type, which includes the reason for the termination application, the explanatory document when the termination applicant proposes the termination, and File ID is the unique identifier of the termination contract file.

[0058] Publish decryption or cancellation records, and display or return the final processing results. Publish the solidified contract cancellation or cancellation records in a timely manner so that the relevant contract status can be publicly queried in real time. The released cancellation or cancellation records contain the time of cancellation or cancellation, the reason explanation and the identity information of the operator. Display the final processing results of contract cancellation or cancellation according to the user's query or needs. Users can obtain the cancellation or cancellation status and historical traceability information of the contract by querying the unique code or scanning the QR code, ensuring that all relevant parties can obtain the update of the contract status in a timely manner. The status history can be displayed through a visual interface, and the query can be performed using the business code, file hash value or scanning QR code direction. The query results are in the form of a file status timeline, including the signing time, change records (cancellation, cancellation, etc.).

[0059] Select the business type and update the cancellation or cancellation record. After selecting the business type corresponding to the contract file to be cancelled (such as cancellation or cancellation), perform operations on the cancellation or cancellation record, including: querying the existing cancellation record. If the record shows that the contract has been cancelled or terminated, it will prompt that the contract has been processed; if the file does not have a cancellation or cancellation record mark, add a new cancellation or cancellation record and mark the operation as "pending identity verification."

[0060] The following example illustrates the use of the cancellation / cancellation checking system for electronic contract documents. The user submits the electronic contract document and attaches basic information (such as contract number, reason for termination application, etc.). Check the format, completeness and other basic elements of the submitted contract document to be terminated.

[0061] Display business type options, read contract status and contextual conditions (such as whether it has been abolished, whether there is a termination record, etc., which can be expanded according to business development), and dynamically display optional business types. The optional business types include: Termination of contract: both parties negotiate to terminate the contract, Unilateral abolition: one party actively abolishes the contract due to special circumstances, Revision of contract: modify existing contract terms, Supplementary agreement: add new additional terms, Cancellation of contract: completely mark the contract as invalid.

[0062] The user selects the business type. The user selects the business type on the interface. The available interface elements include: Single choice: used to display options for multiple business types, Drop-down menu: When there are many options, use a drop-down menu, Icon + Description Card: Display the icon and description of each business type in an intuitive way.

[0063] The system verifies the legitimacy of the selection and checks whether the business type selected by the user is compatible with the current status of the contract. This includes that a voided contract cannot be voided again, and a contract that has not yet come into effect cannot be terminated.

[0064] The verification logic includes: current status check: the system checks the current status of the contract (signed, in progress, invalidated, etc.), authority check: verifies whether the applicant has the authority to select the business type (such as whether the consent of all contracting parties is required, whether it is proposed by the authority, etc.), history record check: query the contract history to avoid repeated or conflicting operations.

[0065] Confirm the selection, select the business type: such as "Terminate the contract", etc. Subsequent impact: Explain the possible impact of selecting this business type on the contract (such as contract termination, irreversibility, etc.).

[0066] According to the selected business type, the corresponding processing flow includes: termination of contract: the system generates a termination record and both parties confirm it; abolition of contract: the system generates an abolition mark and solidifies the relevant records; revision of contract: the system enters the contract revision process and generates a revised version.

[0067] To ensure the legitimacy of the applicant for termination or cancellation, identity verification is performed on the applicant. Identity verification includes multi-factor authentication, which can be achieved through password, fingerprint or face recognition to ensure that only the party involved in the contract can initiate an application for termination or cancellation of the contract.

[0068] The user submits an application for cancellation or revocation, together with relevant identity information.

[0069] Identity verification: The system confirms the identity of the applicant through multi-factor verification (such as password, digital signature, face recognition, etc.). After verification, a mark is generated, including: if the verification is successful, the system generates a release or invalidation mark and attaches it to the contract document; if the verification fails, the operation is directly rejected and the process is terminated; record the operation log: whether it is successful or failed, the applicant's operation behavior is recorded for review.

[0070] Submit an application for contract termination or cancellation. After identity verification, the applicant submits an application for termination or cancellation, including relevant background information, the reason for contract termination, and whether the other contracting parties agree. This explanation is used for recording and archiving, and provides a basis for subsequent inquiries and verifications.

[0071] The following specific examples further illustrate the verification of the integrity and legality of electronic contract document information.

[0072] The verification unit in the electronic contract document release system verifies the incoming electronic files, checks the integrity of the contract documents by detecting the data integrity through hash values, and verifies the legitimacy of the contract documents by detecting digital certificates and digital signatures.

[0073] The business code is a unique code that includes the file generation time and file ID. After the electronic contract document is signed and becomes effective, a unique inquiry ID is generated for each document. The file ID is added to the effective timestamp of the electronic contract document to generate a unique business code for the electronic contract document.

[0074] When the verification system receives an electronic contract file that needs to be verified, the verification unit verifies the business code of the received electronic contract file, and queries the relevant release record based on the business code. If the file belongs to the approval category, the release record will be displayed and the approval process will be entered; if the file belongs to an ordinary file, a release record will be added and the identity of the applicant will be verified. After passing the verification, the applicant can submit a release statement, and the verification system will publish the release record.

[0075] Generate a unique code. The generating unit generates a unique business code for the contract document. Add a QR code or a code address to the document, add the generated business code to the document in the form of a QR code or other form, encrypt the current document related information; generate a new encrypted document containing the business code and encryption information; and publish the relevant records of document release.

[0076] The encrypted file generation time can be obtained by the following methods: file generation timestamp, such as 1625097600, which indicates the file generation timestamp.

[0077] Generate a 128-bit random number based on the electronic contract signing system identifier S to be scrapped, use some characters in the random number as the version number, and some characters as the file number. Calculate the unique ID code of the electronic contract file to be scrapped. The following is a specific example to illustrate the file business code generation method.

[0078] To avoid duplication of recorded data, random numbers of any size can be used, such as randomly generating a 128-bit binary number: R=R0, R1, R2,…, R127, where each bit of the random number Ri is 0 or 1.

[0079] Set some characters in the random number (such as the first 4 bits of the 13th byte to 0100 (indicating the 4th version), set R96R97R98R99=0100, for version compatibility. Set the first 2 bits of the 17th byte to 10: such as R64R65=10.

[0080] This application supports batch signing and status change operations on large-scale files. It uses task queues to decompose batch operations into multiple parallel tasks. Each task is processed on an independent computing node, and the results are archived uniformly.

[0081] The present invention can effectively manage the process of electronic document cancellation, facilitate indexing by uniquely encoding the electronic contract documents for contract cancellation, record data, solve the problem of querying the source of data, trace the status of the electronic contract documents after signing, such as by centralized and distributed data synchronization, solve the problem of privacy, and ensure the security and integrity of the currently provided documents.

Claims

1. A system for checking and releasing electronic contract documents, characterized in that: It includes a file receiving and verification module, a status update and solidification module, an identity verification module, a query and display module, and a batch processing module. The file receiving and verification module receives the electronic contract file and verifies the information. If there is no release business code in the electronic contract file, the file marking unit generates a release business code and adds it to the contract file, and adds a QR code and a verification address link to the contract file. The release file generation unit solidifies the current file status information and generates a new format file. If there is a release business code in the electronic contract file, the file verification unit selects the business type and queries the release record. The status update and solidification module records the change status information of the electronic contract file status, and performs chain storage and solidification of the change status information. Identity verification module: Perform multi-factor identity verification on the applicant for contract termination; Query and display module: The QR code associates the electronic contract document status with the termination business code in real time, selects the business type, and queries and displays the termination record; Batch processing module: provides batch termination signature and status update of electronic contract documents.

2. The system according to claim 1, characterized in that Verifying the identity information of the applicant for termination includes: searching for the effective contract document signed by the applicant through the unique file identifier, extracting the effective contract document and the electronic signature of the applicant for contract termination for handwriting comparison; if the electronic signatures are the same, the applicant for termination is a qualified applicant.

3. The system according to claim 1 or 2, characterized in that: The method of generating a QR code to associate the electronic contract file status with the business code in real time includes: adding the release business code to the contract release file in the form of a QR code and encrypting it, generating an encrypted release file containing the business code and encryption information, adding a release timestamp to the encrypted release file, generating a random number based on the release file system identifier, and calculating the unique ID code of the release file based on the random number.

4. The system according to claim 1 or 2, characterized in that: The receiving of electronic contract files and information verification includes: the file verification module calculates the hash value of the original signed contract file, the hash value of the terminated contract file, the hash value of the electronic signature in the original electronic contract file and the file in the termination application, and detects the integrity, digital certificates, and legitimacy of digital handwriting signatures of files stored in the cloud mode and the private local deployment mode by comparing the hash value of the contract file and the hash value of the electronic signature before and after the termination.

5. The system according to claim 3, characterized in that The method of calculating the unique ID code of the release file based on a random number includes reading the content of the contract file to be released, obtaining the time when the file release request was generated as the current timestamp, and using the private key of the contract signing system to generate a digital signature, specifically including: calculating the hash value H(F) of the contract file F according to the formula: H(F)=SHA-256(F); calling the formula: UID=SHA-256(H(F)+T) according to the hash value and timestamp of the contract file to generate the unique identifier UID of the contract file; sequentially concatenating the contract signing system identifier S, the identifier UID, the timestamp T, and the hash value H(F) of the contract file to form a business code string R; using the private key of the contract signing system to sign R to generate a digital signature σ; and concatenating the string R and the digital signature σ to form a contract file release business code.

6. The system according to claim 5, characterized in that The receiving of the electronic contract file and information verification comprises: the file verification module decomposes the release business code BC, and extracts from BC according to the business code combination rule: system identifier S′, file unique identifier UID′, timestamp T′, file hash value H′(F), digital signature σ′; uses the same algorithm as that for generating the business code to calculate the hash value H′(F) of the content of the release contract file: H′(F)=SHA-256(F); compares H(F) and H′(F), if they match, the verification is successful, otherwise, a "file content tampered" prompt is sent; calculates the unique identifier UID′ according to the formula UID′=SHA-256(H′(F)+T′) based on the extracted timestamp T and the contract file hash value H′(F), and compares it with the contract file unique identifier UID, if they are the same, they match, otherwise, a "file unique identifier is invalid" prompt is sent; combines the business code string according to the system identifier S′, file unique identifier UID′, timestamp T′, and file hash value H′(F) obtained from the release contract file, and the specific combination method can be: R′=S′+"−"+UID′+"−"+T′+"−"+H′(F) Obtain the business code and use the public key of the file signing system to verify the signature. If the verification is successful, it means the signature is valid, otherwise a "signature invalid" prompt is sent; verify through the registration center whether the system identifier S' comes from a trusted system. If it comes from a trusted system, the verification is successful, otherwise a "source system invalid" prompt is sent.

7. The system according to any one of claims 1, 2, 5 and 6, characterized in that: The state update data record structure of the chain storage entry is used to record the state of the terminated or invalidated contract file, including: the unique identifier of the file File ID, the contract change type Change Type, the change time Timestamp, the change reason Reason, the hash value H of the previous record state prev , the hash value H of the current record status current , link the previous state and the current state to form a new chain, calculate the hash value before and after the state change and write it into the blockchain storage record, where, according to the formula: H current = SHA-256(File ID+Change Type+Timestamp+Reason+H prev ) Calculate the hash value H of the current record state current .

8. A method for de-verifying an electronic contract document, characterized in that: Receive electronic contract documents and verify information, generate contract cancellation business codes for electronic contract documents to be cancelled / invalidated, and extract contract cancellation business codes for cancelled / invalidated electronic contract documents; if there is no cancellation business code, perform multi-factor identity authentication on the contract cancellation applicant, generate a cancellation business code and add it to the contract document, and add a QR code and a verification address link to the contract document; solidify the current file status information and generate a new format file; if there is a cancellation business code, the file verification unit selects the business type and queries the cancellation record; record the change status information of the electronic contract document status, and chain store and solidify the change record; Query and display module: The QR code associates the electronic contract document status with the termination business code in real time, selects the business type, and queries and displays the termination record; Batch processing module: provides batch termination signature and status update of electronic contract documents.

9. The method according to claim 8, characterized in that Verifying the identity information of the applicant for termination includes: searching for the effective contract document signed by the applicant through the unique document identifier, extracting the electronic signature of the applicant from the effective contract document and the contract termination application document for handwriting comparison; if the electronic signatures are the same, the applicant for termination is a qualified applicant.

10. The method according to claim 8 or 9, characterized in that: The method of generating a QR code to associate the electronic contract file status with the business code in real time includes: adding the release business code to the contract release file in the form of a QR code and encrypting it, generating an encrypted release file containing the business code and encryption information, adding a release timestamp to the encrypted release file, generating a random number based on the release file system identifier, and calculating the unique ID code of the release file based on the random number.

11. The method according to claim 8 or 9, characterized in that: The receiving of electronic contract files and information verification includes: the file verification module calculates the hash value of the original signed contract file, the hash value of the contract termination file, the hash value of the electronic signature in the original electronic contract file and the termination application file, and detects the integrity, digital certificates, and legitimacy of digital handwriting signatures of files stored in the cloud mode and the private local deployment mode by comparing the hash value of the contract file and the hash value of the electronic signature before and after the contract termination.

12. The method according to claim 10, characterized in that The method of calculating the unique ID code of the release file based on a random number includes reading the content of the contract file to be released, obtaining the time when the file release request was generated as the current timestamp, and using the private key of the contract signing system to generate a digital signature, specifically including calculating the hash value H(F) of the contract file F according to the formula: H(F)=SHA-256(F), calling the formula: UID=SHA-256(H(F)+T) according to the hash value and timestamp of the contract file to generate the unique identifier UID of the contract file, sequentially concatenating the contract signing system identifier S, the unique identifier UID, the timestamp T, and the hash value H(F) of the contract file to form a business code string R; using the private key of the contract signing system to sign R to generate a digital signature σ; and concatenating the string R and the digital signature σ to form a business code for releasing the contract file.

13. The method according to claim 12, characterized in that The receiving of the electronic contract file and information verification comprises: the file verification module decomposes the release business code BC, and extracts from BC according to the business code combination rule: system identifier S′, file unique identifier UID′, timestamp T′, file hash value H′(F), digital signature σ′; uses the same algorithm as that for generating the business code to calculate the hash value H′(F) of the content of the release contract file: H′(F)=SHA-256(F); compares H(F) and H′(F), if they match, the verification is successful, otherwise, a "file content tampered" prompt is sent; calculates the unique identifier UID′ according to the formula UID′=SHA-256(H′(F)+T′) based on the extracted timestamp T and the contract file hash value H′(F), and compares it with the contract file unique identifier UID, if they are the same, they match, otherwise, a "file unique identifier is invalid" prompt is sent; combines the business code string according to the system identifier S′, file unique identifier UID′, timestamp T′, and file hash value H′(F) obtained from the release contract file, and the specific combination method can be: R′=S′+"−"+UID′+"−"+T′+"−"+H′(F) Obtain the business code and use the public key of the file signing system to verify the signature. If the verification is successful, it means the signature is valid, otherwise a "signature invalid" prompt is sent; verify through the registration center whether the system identifier S' comes from a trusted system. If it comes from a trusted system, the verification is successful, otherwise a "source system invalid" prompt is sent.

14. The method according to any one of claims 8 to 13, characterized in that: The state update data record structure of the chain storage entry is used to record the state of the terminated or invalidated contract file, including: the unique identifier of the file File ID, the contract change type Change Type, the change time Timestamp, the change reason Reason, the hash value H of the previous record state prev , the hash value H of the current record status current , link the previous state and the current state to form a new chain, calculate the hash value before and after the state change and write it into the blockchain storage record, where, according to the formula: Hcurrent = SHA-256(File ID+Change Type+Timestamp+Reason+Hprev) Calculate the hash value Hcurrent of the current record state.

Images