A blockchain-based international trade document credible circulation management system and method

Abstract

The application provides a blockchain-based international trade document credible flow management system and method. According to the current load state corresponding to the international trade document and the communication interface description file of the target flow node, the target communication load is generated. The protocol conversion voucher is generated by combining the current load state and the target communication load. The transmission voucher is generated according to the transmission maintenance factor before and after the protocol conversion. The transmission voucher and the protocol conversion voucher are associated and written into the blockchain to obtain the protocol conversion witness chain. In response to the receiving verification request of the target communication load initiated by the document receiving terminal, the all-around credible verification is carried out based on the protocol conversion witness chain to obtain the credible verification result, and then the document receiving terminal is controlled to accept and flow the target communication load. The application can realize the traceable verification and credible flow control of the cross-node conversion process of the international trade document.

Description

Technical Field

[0001] This application relates to the field of blockchain technology for trusted cross-border data transfer, and more specifically, to a blockchain-based trusted transfer management system and method for international trade documents. Background Technology

[0002] In international trade, international trade documents need to be transmitted and processed between multiple circulation nodes, such as exporting companies, importing companies, freight forwarders, carriers, ports, customs, banks and insurance institutions. Due to the differences in communication protocols, message formats, field encoding methods and interface specifications used by different circulation nodes, documents usually need to undergo protocol adaptation, field mapping and message encapsulation during cross-institutional transmission.

[0003] Existing technologies typically involve communication gateways or intermediate conversion platforms performing document protocol conversion and sending the converted communication payload to the target circulation node. However, existing solutions lack a unified and verifiable recording mechanism for the payload correlation before and after protocol conversion, key preservation factors during transmission, and the protocol conversion operation itself. When documents pass through multiple circulation nodes, it is difficult to confirm whether the received documents originate from legitimate preceding documents, to determine the continuity and consistency of payloads between adjacent circulation stages, and to trace the conversion rules, execution process, and operational permissions used in the protocol conversion. Furthermore, existing document circulation records are usually kept separately by each participating institution, resulting in data fragmentation, ease of record modification, and a lack of shared credible evidence across institutions. When disputes arise regarding document content, conversion anomalies, or unauthorized circulation, it is difficult to quickly locate the abnormal stage based on unified credible records and thereby control the target circulation node's acceptance or continued forwarding of the relevant documents. Therefore, achieving traceable verification and credible circulation control of international trade documents across nodes has become a challenge for the industry. Summary of the Invention

[0004] This application provides a blockchain-based trusted circulation management system and method for international trade documents, which can realize traceable verification and trusted circulation control of the cross-node conversion process of international trade documents.

[0005] Firstly, this application provides a blockchain-based method for the trusted transfer and management of international trade documents, comprising the following steps:

[0006] Based on the current payload status corresponding to the international trade documents and the communication interface description file of the target transfer node, the protocol is converted to generate the target communication payload;

[0007] The cross-agency communication gateway generates a protocol conversion certificate by combining the current payload status with the target communication payload, and generates a transmission certificate based on the transmission retention factor before and after the protocol conversion;

[0008] The transmission certificate and the protocol conversion certificate are associated and written into the blockchain to form a protocol conversion witness chain for the international trade documents among multiple circulation nodes;

[0009] In response to the document receiving terminal of the target transfer node initiating a verification request for the target communication payload, a comprehensive trusted verification is performed based on the protocol conversion witness chain to obtain a trusted verification result.

[0010] Based on the trusted verification result, the document receiving terminal is controlled to accept and transfer the target communication payload.

[0011] In some embodiments, the generation of the target communication payload involves protocol conversion based on the current payload status corresponding to the international trade document and the communication interface description file of the target transfer node. Specifically, this includes:

[0012] The cross-agency communication gateway determines the protocol conversion operator based on the current communication protocol in the current payload status corresponding to the international trade document and the communication interface description file corresponding to the target transfer node;

[0013] When the current communication protocol is inconsistent with the target communication protocol in the communication interface description file, the protocol conversion operator performs cross-border protocol adaptation conversion on the current communication payload to generate the target communication payload.

[0014] When the current communication protocol is consistent with the target communication protocol, node routing encapsulation is performed on the current communication payload to generate a target communication payload with the target flow node interface identifier.

[0015] In some embodiments, the generation of a protocol conversion certificate by the cross-agency communication gateway, combining the current payload state with the target communication payload, specifically includes:

[0016] The cross-institutional communication gateway obtains the conversion session identifier corresponding to this cross-border protocol conversion and the on-chain index of the previous protocol conversion certificate;

[0017] Normalized summaries are extracted from the current communication payload and the target communication payload respectively to obtain the pre-conversion payload summary and the post-conversion payload summary;

[0018] Based on the operator identifier, operator version, and conversion rule summary of the protocol conversion operator, generate the operator execution fingerprint;

[0019] A conversion context summary is generated based on the pre-conversion payload summary, the post-conversion payload summary, the operator execution fingerprint, the conversion session identifier, and the on-chain index of the previous protocol conversion credential.

[0020] The witness data to be signed, which includes the transformation context digest and the anti-replay challenge, is digitally signed to obtain the gateway signature;

[0021] The witness data to be signed, the gateway signature, and the operator execution fingerprint are encapsulated into a protocol conversion credential and stored in the secure storage area of ​​the cross-agency communication gateway.

[0022] In some embodiments, generating transmission credentials based on the transmission retention factor before and after protocol conversion specifically includes:

[0023] Transmission preservation factors are extracted from the current communication payload before protocol conversion and the target communication payload after protocol conversion, respectively, to obtain the set of preservation factors before conversion and the set of preservation factors after conversion.

[0024] According to the mapping rules corresponding to the protocol conversion operator, establish the factor mapping relationship between the pre-conversion retention factor set and the post-conversion retention factor set;

[0025] Based on the preservation relationship determination rule, the factor mapping relationship is verified to obtain the preservation relationship verification result;

[0026] When the relationship verification result is passed, a transmission certificate is generated based on the factor mapping relationship, the protocol conversion operator identifier, the current transfer sequence number, and the corresponding protocol conversion certificate.

[0027] In some embodiments, associating the transmission certificate with the protocol conversion certificate and writing it into the blockchain to form a protocol conversion witness chain for the international trade document among multiple circulation nodes specifically includes:

[0028] Obtain the conversion credential digest and the transmission credential digest, and generate an associated digest based on the conversion credential digest and the transmission credential digest;

[0029] The associated summary, the payload summary before and after conversion, the current transfer sequence number, and the on-chain index of the previous protocol conversion certificate are encapsulated into on-chain registration data;

[0030] The on-chain registration data is submitted to the blockchain by calling the smart contract interface of the blockchain node through the cross-institutional communication gateway;

[0031] The smart contract re-determines the association digest based on the conversion credential digest and the transmission credential digest, and verifies whether the re-obtained association digest is consistent with the association digest in the on-chain registration data;

[0032] When the associated digest verification passes, the successor relationship of adjacent protocol conversion certificates is established, and a protocol conversion witness chain is generated based on the flow sequence and payload connection logic.

[0033] In some embodiments, performing comprehensive trust verification based on the protocol conversion witness chain to obtain the trust verification result specifically includes:

[0034] According to the successor-successor relationship and flow sequence in the protocol conversion witness chain, verify the on-chain index connection relationship and the flow sequence number continuity relationship between adjacent protocol conversion certificates;

[0035] Verify whether the converted payload summary of the previous protocol conversion document is consistent with the converted payload summary of the subsequent protocol conversion document in adjacent protocol conversion documents;

[0036] Based on the converted payload digest of the end protocol conversion certificate and the target payload digest received by the target transfer node, verify whether the target payload received by the target transfer node is consistent with the end payload of the protocol conversion witness chain.

[0037] Based on the cross-border gateway permissions, node access permissions, and the conversion rules corresponding to the protocol conversion operator, verify whether this cross-border protocol conversion is an authorized and compliant operation.

[0038] A reliable verification result is generated based on the verification results of each verification.

[0039] In some embodiments, controlling the acceptance and transfer behavior of the document receiving terminal for the target communication payload based on the trusted verification result specifically includes:

[0040] When the trusted verification result is passed, an acceptance permission instruction is sent to the target transfer node, driving the document receiving terminal to perform the storage operation, document review operation, service forwarding operation or subsequent protocol conversion operation of the target communication payload;

[0041] When the trusted verification result fails, a blocking command is sent to the target transfer node to control the document receiving terminal to suspend the acceptance, storage, or continued transfer of the target communication payload.

[0042] Secondly, this application provides a blockchain-based trusted transfer management system for international trade documents, used to execute a blockchain-based trusted transfer management method for international trade documents, including:

[0043] The protocol conversion module is used to perform protocol conversion based on the current payload status of the international trade documents and the communication interface description file of the target flow node, and generate the target communication payload.

[0044] The certificate generation module is used to generate protocol conversion certificates by the cross-agency communication gateway in combination with the current payload status and the target communication payload, and to generate transmission certificates based on the transmission retention factor before and after the protocol conversion.

[0045] The witness chain construction module is used to associate the transmission certificate and the protocol conversion certificate and write them into the blockchain to form a protocol conversion witness chain for the international trade documents among multiple circulation nodes;

[0046] The witness chain verification module is used to respond to the verification request for receiving the target communication payload initiated by the document receiving terminal of the target transfer node, and to perform a comprehensive trusted verification based on the protocol conversion witness chain to obtain a trusted verification result.

[0047] The transfer control module is used to control the acceptance and transfer behavior of the target communication payload by the document receiving terminal based on the trusted verification result.

[0048] Thirdly, this application provides a computer device, the computer device including a memory and a processor, the memory storing code, and the processor being configured to acquire the code and execute the above-described blockchain-based trusted transfer management method for international trade documents.

[0049] Fourthly, this application provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the aforementioned blockchain-based trusted transfer management method for international trade documents.

[0050] The technical solutions provided by the embodiments disclosed in this application have the following beneficial effects:

[0051] This application provides a blockchain-based trusted transfer management system and method for international trade documents. The system involves: performing protocol conversion based on the current payload status of the international trade document and the communication interface description file of the target transfer node to generate a target communication payload; generating a protocol conversion certificate by a cross-institutional communication gateway combining the current payload status and the target communication payload, and generating a transmission certificate based on the transmission retention factor before and after the protocol conversion; associating the transmission certificate with the protocol conversion certificate and writing it into the blockchain to form a protocol conversion witness chain for the international trade document among multiple transfer nodes; responding to a verification request for receiving the target communication payload initiated by the document receiving terminal of the target transfer node, performing comprehensive trusted verification based on the protocol conversion witness chain to obtain a trusted verification result; and controlling the document receiving terminal's acceptance and transfer behavior of the target communication payload based on the trusted verification result.

[0052] Therefore, this application demonstrates several key advantages. First, it adaptively selects between protocol conversion and direct routing based on communication protocol matching, avoiding redundant operations, reducing data processing overhead, and enhancing adaptability to multi-protocol scenarios. Second, by adaptively extracting flow retention factors and quantifying the compliance of factor mapping, combined with dual-credential association binding and chain-based evidence storage mechanisms, it deeply links protocol conversion adaptation behavior with business data authenticity verification results. Relying on time sequence numbers and on-chain indexes to connect the entire flow record, it constructs an immutable and fully traceable document flow link, avoiding risks such as credential forgery, split verification, and data tampering, ensuring the authenticity and integrity of the flow data. Third, by adopting a four-layer progressive layered verification mechanism, it can verify the integrity of the witness chain, the consistency of payload connection, the authenticity of end data, and the compliance of flow operations node by node, effectively locating abnormal flow nodes and problem types, and intercepting unauthorized flow behavior. Finally, based on the verification results, differentiating actions are taken to accept and archive or block the transfer of documents, thereby achieving automated management of document circulation and effectively improving the security, standardization, and traceability of cross-institutional transfer of international trade documents under heterogeneous agreements.

[0053] In summary, the technical solution adopted in this application can realize traceable verification and reliable flow control of international trade documents across nodes. Attached Figure Description

[0054] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only for this embodiment of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0055] Figure 1 This is an exemplary flowchart of a blockchain-based trusted transfer management method for international trade documents, as shown in some embodiments of this application.

[0056] Figure 2 This is a schematic diagram illustrating an application scenario of a blockchain-based trusted transfer management method for international trade documents, according to some embodiments of this application.

[0057] Figure 3 This is an exemplary flowchart illustrating the generation protocol conversion witness chain according to some embodiments of this application;

[0058] Figure 4 This is a schematic diagram of the structure of a blockchain-based trusted international trade document management system according to some embodiments of this application;

[0059] Figure 5This is a schematic diagram of the structure of a computer device for implementing a blockchain-based trusted transfer management method for international trade documents, according to some embodiments of this application. Detailed Implementation

[0060] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of the embodiments. Based on the embodiments of this application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of this application.

[0061] This application provides a blockchain-based trusted transfer management system and method for international trade documents. Its core is to perform protocol conversion based on the current payload status of the international trade document and the communication interface description file of the target transfer node to generate a target communication payload. A cross-institutional communication gateway generates a protocol conversion certificate by combining the current payload status and the target communication payload, and generates a transmission certificate based on the transmission retention factor before and after the protocol conversion. The transmission certificate and the protocol conversion certificate are associated and written into the blockchain to form a protocol conversion witness chain for the international trade document across multiple transfer nodes. In response to a verification request for the target communication payload initiated by the document receiving terminal of the target transfer node, a comprehensive trusted verification is performed based on the protocol conversion witness chain to obtain a trusted verification result. Based on the trusted verification result, the acceptance and transfer behavior of the document receiving terminal for the target communication payload is controlled. This scheme enables traceable verification and trusted transfer control of the cross-node conversion process of international trade documents.

[0062] To better understand the above technical solutions, a detailed description of the technical solutions will be provided below in conjunction with the accompanying drawings and specific embodiments. (Refer to...) Figure 1 The diagram is an exemplary flowchart of a blockchain-based trusted transfer management method for international trade documents, according to some embodiments of this application. The diagram mainly includes the following steps:

[0063] In step S101, the target communication payload is generated by performing protocol conversion based on the current payload status corresponding to the international trade document and the communication interface description file of the target transfer node.

[0064] In some embodiments, the target communication payload is generated by performing protocol conversion based on the current payload status corresponding to the international trade document and the communication interface description file of the target transfer node. Specifically, this can be achieved in the following manner:

[0065] The cross-agency communication gateway determines the protocol conversion operator based on the current communication protocol in the current payload status corresponding to the international trade document and the communication interface description file corresponding to the target transfer node;

[0066] When the current communication protocol is inconsistent with the target communication protocol in the communication interface description file, the protocol conversion operator performs cross-border protocol adaptation conversion on the current communication payload to generate the target communication payload.

[0067] When the current communication protocol is consistent with the target communication protocol, node routing encapsulation is performed on the current communication payload to generate a target communication payload with the target flow node interface identifier.

[0068] In this application, Figure 2 This is a schematic diagram of an application scenario for a blockchain-based trusted transfer management method for international trade documents, as shown in some embodiments of this application. As shown in the figure, the cross-institutional communication gateway connects the current transfer node and the target transfer node respectively. The international trade document-related data output by the current transfer node is converted by the cross-institutional communication gateway and then used in conjunction with the blockchain network to realize certificate storage, and finally transmitted to the document receiving terminal of the target transfer node.

[0069] It should be noted that the current payload status includes the current communication protocol, the current communication payload, and the current transfer node identifier; the current communication payload refers to the transmissible electronic data carrier formed when international trade documents are output from the current transfer node, which can be a message, file, data packet, or interface request data; the current communication protocol refers to the communication protocol or message specification followed by the current communication payload during output or transmission; the communication interface description file is the communication interface specification published by the target transfer node, including the target communication protocol, interface identifier, interface address, and message format; the target communication protocol is the data receiving protocol or message specification specified in the communication interface description file; the protocol conversion operator is deployed on the cross-institutional communication gateway and is a set of rules for converting source protocol data to target protocol data; the target communication payload refers to the communication payload that can be identified and received by the target transfer node after cross-border protocol adaptation conversion or node routing encapsulation.

[0070] In practice, firstly, the current transfer node pushes the current payload status containing international trade document information to the cross-agency communication gateway. The cross-agency communication gateway extracts the current communication protocol from the current payload status and reads the target communication protocol from the target transfer node's communication interface description file. Based on the protocol mapping lookup table pre-configured locally by the gateway, it matches and selects the protocol conversion operator corresponding to the current communication protocol and the target communication protocol. The protocol mapping lookup table is pre-configured based on the publicly available interface protocol specifications of each international trade node. The protocol conversion operator consists of protocol header reassembly rules, message field mapping rules, encoding conversion rules, and format verification rules.

[0071] It should be noted that both the current circulation node and the target circulation node are cross-border business institution nodes participating in the circulation of international trade documents, specifically including international trade participants such as exporting companies, importing companies, freight forwarders, carriers, port authorities, customs, banks and insurance institutions.

[0072] In practice, if the current communication protocol is inconsistent with the target communication protocol, the communication gateway invokes the matched protocol conversion operator to perform conversion processing. Following the standardized conversion rules built into the protocol conversion operator, it completes the mapping of payload service field formats, encoding conversion, and protocol header reassembly. It also performs compliance verification according to the target node interface specifications to ensure that the processed data fully adapts to the target communication protocol requirements, generating a compliant target communication payload. If the current communication protocol is consistent with the target communication protocol, there is no need to modify the payload service content. The communication gateway performs node routing encapsulation on the current communication payload. Based on the message type, a preset encapsulation strategy is used to distinguish the writing location. Fixed message type data is written to the message header, file type and extended data are written to the extended fields, and the target transfer node interface identifier and routing information are appended to generate a target communication payload with the target transfer node interface identifier. Finally, the cross-organizational communication gateway outputs the generated target communication payload to the target transfer node.

[0073] It should be noted that the cross-organizational communication gateway determines whether to initiate protocol adaptation and conversion by comparing the current communication protocol with the target communication protocol. When the protocols are inconsistent, a target communication payload conforming to the target interface specification is generated. When the protocols are consistent, data delivery is achieved by relying on node routing encapsulation. This not only meets the data conversion needs between heterogeneous protocols in international trade documents, but also eliminates redundant conversion operations when the protocols are the same, reducing processing overhead and improving the adaptability of this solution to international trade multi-protocol flow scenarios.

[0074] In step S102, the cross-agency communication gateway generates a protocol conversion certificate by combining the current load status with the target communication load, and generates a transmission certificate based on the transmission retention factor before and after the protocol conversion.

[0075] In some embodiments, the generation of protocol conversion credentials by the cross-agency communication gateway in combination with the current payload state and the target communication payload can be specifically carried out in the following manner:

[0076] The cross-institutional communication gateway obtains the conversion session identifier corresponding to this cross-border protocol conversion and the on-chain index of the previous protocol conversion certificate;

[0077] Normalized summaries are extracted from the current communication payload and the target communication payload respectively to obtain the pre-conversion payload summary and the post-conversion payload summary;

[0078] Based on the operator identifier, operator version, and conversion rule summary of the protocol conversion operator, generate the operator execution fingerprint;

[0079] A conversion context summary is generated based on the pre-conversion payload summary, the post-conversion payload summary, the operator execution fingerprint, the conversion session identifier, and the on-chain index of the previous protocol conversion credential.

[0080] The witness data to be signed, which includes the transformation context digest and the anti-replay challenge, is digitally signed to obtain the gateway signature;

[0081] The witness data to be signed, the gateway signature, and the operator execution fingerprint are encapsulated into a protocol conversion credential and stored in the secure storage area of ​​the cross-agency communication gateway.

[0082] It should be noted that the conversion session identifier is used to uniquely identify this cross-border protocol conversion session, ensuring that the conversion operations of the same document in multiple transfers can be tracked and associated; the on-chain index of the previous protocol conversion certificate is an identifier sequence number uniquely assigned by the blockchain node to each on-chain registered data, possessing global uniqueness and temporal increment, used to uniquely locate a single transfer evidence record; the operator execution fingerprint is used to prove the conversion logic on which this protocol conversion is based, avoiding the problem of only recording the conversion result without being able to trace the conversion rules; the conversion context digest is used to bind the information of each link involved in this conversion into a whole; the anti-replay challenge is a random number, timestamp, incrementing sequence number or a combination thereof, used to distinguish the data to be signed and witnessed in different conversion sessions, preventing historical witness data from being submitted repeatedly or misused; the protocol conversion certificate is used to record the payload association relationship, conversion operator information and gateway signature information of this protocol conversion.

[0083] In practice, firstly, the cross-institutional communication gateway obtains the conversion session identifier from the current protocol conversion session and queries the on-chain index of the previous protocol conversion certificate from the blockchain. If the current conversion is the first protocol conversion and there is no prior conversion record or corresponding certificate, the on-chain index parameter of the previous certificate is uniformly assigned a value according to a preset empty string to complete the initialization of the index parameters for the first conversion, ensuring that the first round of protocol conversion certificates can be successfully uploaded to the blockchain for archiving. Secondly, before the digest calculation, the cross-institutional communication gateway performs unified preprocessing on the current communication payload and the target communication payload according to the general standardized specifications for cross-border data interaction, removing redundant differences that do not affect the core business content of the certificate, and unifying the field arrangement order, character encoding format, time display format, and null value expression method. After preprocessing, the fixed digest value is calculated using the SHA-256 one-way encrypted digest algorithm commonly used in the blockchain evidence storage field, obtaining the pre-conversion payload digest and the post-conversion payload digest respectively. This preprocessing method can avoid the problem of inconsistent digests of homogeneous business data caused by differences in message format, field sorting, and encoding, ensuring the effectiveness of digest comparison. Then, the communication gateway retrieves the operator identifier, operator version, and conversion rule summary corresponding to this protocol conversion. It integrates all operator information according to a preset fixed concatenation order and character concatenation rules to generate a unique operator execution fingerprint. Among them, the operator identifier is used to locate the currently invoked protocol conversion operator; the operator version is used to distinguish operator iteration versions; and the conversion rule summary is a rule hash summary that is pre-generated and solidified during the deployment phase of the protocol conversion operator. The gateway directly reads and obtains it during the process of retrieving this protocol conversion operator, and it is used to characterize the field mapping, format conversion, and message encapsulation rules executed in this conversion.

[0084] In addition, in specific implementation, the cross-institutional communication gateway, according to a fixed priority combination, sequentially integrates and encapsulates the pre-conversion payload digest, post-conversion payload digest, operator execution fingerprint, conversion session identifier, and on-chain index of the previous protocol conversion credential using a fixed, undelimited character concatenation method to generate a unique corresponding conversion context digest. Subsequently, the cross-institutional communication gateway generates an anti-replay challenge for the current session using a combination of the current timestamp and a session random number. The conversion context digest and the anti-replay challenge are integrated into complete data to be signed, and the gateway's built-in private key is used to perform encrypted signing on the data to be signed, generating a valid gateway signature. Finally, the data to be signed, the gateway signature, and the operator execution fingerprint are uniformly encapsulated to generate a standardized protocol conversion credential, which is synchronously stored in the gateway's dedicated local secure storage area, completing the localized credential storage.

[0085] It should be noted that by converting the session identifier and the on-chain index of the previous certificate, the protocol conversion operations of each link in the certificate circulation process are linked, forming a complete and traceable circulation link; the gateway private key signature can effectively ensure the authenticity of the source and integrity of the protocol conversion certificate, eliminating the risk of certificate forgery and tampering; the dedicated secure storage area can avoid data loss, illegal reading and tampering before the certificate is put on the chain, ensuring the credibility of the circulation certificate.

[0086] In some embodiments, generating transmission credentials based on the transmission retention factor before and after protocol conversion can be achieved in the following ways:

[0087] Transmission preservation factors are extracted from the current communication payload before protocol conversion and the target communication payload after protocol conversion, respectively, to obtain the set of preservation factors before conversion and the set of preservation factors after conversion.

[0088] According to the mapping rules corresponding to the protocol conversion operator, establish the factor mapping relationship between the pre-conversion retention factor set and the post-conversion retention factor set;

[0089] Based on the preservation relationship determination rule, the factor mapping relationship is verified to obtain the preservation relationship verification result;

[0090] When the relationship verification result is passed, a transmission certificate is generated based on the factor mapping relationship, the protocol conversion operator identifier, the current transfer sequence number, and the corresponding protocol conversion certificate.

[0091] It should be noted that the transmission retention factor is used to characterize the communication payload characteristics of international trade documents that need to remain consistent or meet a preset mapping relationship before and after the protocol conversion, including at least one key business field among document number, trade terms, amount, quantity, and party information; the retention factor mapping relationship is used to represent the correspondence of the same business element in different fields, different codes, or different message structures before and after the protocol conversion; the current transfer sequence number is a unique sequence value generated by the gateway's time-sequential increment, used to identify the time sequence position of the current protocol conversion in the complete document transfer path; the transmission certificate is used to record the key business factors that need to remain consistent or meet the mapping relationship before and after the protocol conversion, so as to prove that there is a verifiable transmission succession relationship between the target communication payload and the current communication payload.

[0092] In practice, firstly, an adaptive extraction operation of the transmission preservation factor is performed. The current communication payload before protocol conversion and the target communication payload after protocol conversion are read independently. Standardized preprocessing is then performed on the two sets of heterogeneous payload data: For a single set of payload data, the communication gateway sequentially parses and decodes the message fields, unifying them to the UTF-8 standard encoding format. Fields are sorted according to the preset hierarchical specifications of the service message. Leading and trailing whitespace characters, invalid placeholder fields, and redundant fields in the protocol header and transmission encapsulation are removed, leaving only the original service data fields that can be used for service fidelity verification. After preprocessing, each service field within the preprocessed current communication payload and target communication payload is processed separately. Similarity is calculated using a weighted average across three dimensions: numerical content, field format, and hierarchical structure. This quantifies the numerical deviation and structural variability of each field. The gateway then filters low-variability fields within each load group based on a preset fidelity threshold range. Furthermore, it uses a K-means clustering algorithm to aggregate and categorize all field variation indicators, identifying highly stable core business fields whose variation converges within the threshold range. These are then grouped into independent pre-conversion retention factor sets and post-conversion retention factor sets. The fidelity threshold is generated by the communication gateway through a statistical adaptive calculation based on the variation data of all fields. By statistically analyzing the mean and variance of all field variations, a fidelity threshold range suitable for this document transfer scenario is dynamically generated.

[0093] In addition, in specific implementation, the communication gateway relies on the exclusive mapping rules of the protocol conversion operator invoked in this protocol conversion to complete the association matching of the two sets of retention factor sets. Specifically, for the scenarios of field renaming, encoding mode switching, and message hierarchy structure reorganization that occur in this transfer, a dynamic adaptation mapping logic is adopted, and the matching process follows a fixed priority execution order: the primary basis is the matching of business field primary keys, the encoding conversion association relationship is the secondary basis, and the message structure adaptation rule is the last resort basis. For each business factor in the retention factor set before conversion, the communication gateway combines the field association mapping table built into the operator, the encoding conversion correspondence, and the structure adaptation rule to match the corresponding same-source business factor in the target communication payload. If multiple results conflict during the matching process, the business primary key matching result is uniformly used as the sole judgment criterion. In this way, all factors are associated and bound one by one, establishing a one-to-one bidirectional mapping relationship between the retention factors before and after conversion, realizing accurate docking of the same-source business factors with different message formats and encoding modes in heterogeneous protocol scenarios.

[0094] It should be noted that the field association mapping table, the encoding conversion correspondence, and the structure adaptation rules are all pre-built and stored within the protocol conversion operator, serving as dedicated binding rules generated when the operator is formed. Specifically, the field association mapping table records the source correspondence between primary key fields of the new and old protocols; the encoding conversion correspondence defines the equivalent conversion standards for field values, encoding formats, and time formats; and the structure adaptation rules match the field nesting levels and mounting relationships of heterogeneous messages.

[0095] In practice, relying on preset hierarchical relationship determination rules, all factor mapping relationships are quantitatively verified item by item to obtain standardized relationship verification results. Specifically, a differentiated hierarchical verification mechanism is adopted. For core fixed business factors in international trade documents, such as amount, document number, and transaction entity, which cannot be changed, a full numerical consistency verification is performed, requiring that the values ​​and content before and after conversion be completely consistent, without any numerical deviation or content difference. For variable business factors, such as date format, character encoding, and field display format, which allow compliant conversion, a mapping compliance verification is performed according to the standardized format specifications built into the current protocol conversion operator. Format conversion is only allowed within the format, encoding, and display specifications stipulated in the protocol. Once field content is tampered with, numerical deviation is found, or illegal format replacement is determined to be non-compliant. The verification is then conducted to determine whether the converted data conforms to the corresponding protocol specifications and business standards. Only when all factor mapping relationships are verified to be compliant is the overall relationship verification result determined to be passed. Any inconsistency of any core factor or non-compliant conversion of variable factors results in a failed verification. Finally, assuming the verification result is passed, the communication gateway integrates multi-dimensional flow identifiers and compliance verification data to form a standardized transmission certificate. Specifically, the gateway retrieves the operator identifier corresponding to this protocol conversion, the flow sequence number corresponding to the current flow link, and all verified and compliant factor mapping relationship data. At the same time, it binds the protocol conversion certificate generated in this flow and the corresponding on-chain evidence information. According to the preset fixed data encapsulation structure, the above-mentioned data are systematically integrated and the overall data is encrypted and encapsulated using the gateway's built-in fixed encryption algorithm. Finally, a transmission certificate with anti-tampering, traceability, and verifiability characteristics is generated. This transmission certificate retains the factor mapping relationship before and after this protocol conversion, the adaptation rules of the protocol conversion operator called in this time, the document flow sequence information, and the associated protocol conversion certificate evidence content. This can effectively prove that this protocol conversion only adapts and adjusts the communication protocol standard and message hierarchy structure, and does not tamper with or change the core business data of international trade documents throughout the process, realizing the reliable and authentic verification of document cross-institutional flow data in heterogeneous protocol scenarios.

[0096] It should be noted that by adaptively extracting the transmission retention factor before and after the protocol conversion, quantifying the verification factor to map compliance, and binding the protocol conversion certificate to generate a unique transmission certificate, an independent and reliable verification basis can be provided for the cross-institutional document transfer. At the same time, the bidirectional association and binding of the transmission certificate and the protocol conversion certificate link the format adaptation behavior of the protocol conversion with the verification results of business data authenticity, thus constructing a complete document transfer traceability link and effectively improving the traceability and overall credibility of the cross-institutional transfer process of international trade documents.

[0097] In step S103, the transmission certificate and the protocol conversion certificate are associated and written into the blockchain to form a protocol conversion witness chain for the international trade document among multiple circulation nodes.

[0098] Preferably, in some embodiments, reference is made to Figure 3 As shown in the figure, this is an exemplary flowchart illustrating the generation of a protocol conversion witness chain according to some embodiments of this application. In this embodiment, associating the transmission certificate with the protocol conversion certificate and writing it into the blockchain to form a protocol conversion witness chain for the international trade document among multiple circulation nodes can be achieved through the following steps:

[0099] In step S1031, a conversion credential digest and a transmission credential digest are obtained, and an association digest is generated based on the conversion credential digest and the transmission credential digest.

[0100] In step S1032, the associated summary, the payload summary before and after conversion, the current transfer sequence number, and the on-chain index of the previous protocol conversion certificate are encapsulated into on-chain registration data.

[0101] In step S1033, the on-chain registration data is submitted to the blockchain by calling the smart contract interface of the blockchain node through the cross-institutional communication gateway;

[0102] In step S1034, the smart contract re-determines the association digest based on the conversion credential digest and the transmission credential digest, and verifies whether the re-obtained association digest is consistent with the association digest in the on-chain registration data;

[0103] In step S1035, when the associated digest verification passes, the successor relationship of adjacent protocol conversion certificates is established, and a protocol conversion witness chain is generated based on the flow sequence and payload connection logic.

[0104] It should be noted that the conversion certificate digest is a digest value obtained by hashing the protocol conversion certificate, used to fix the compliance certificate corresponding to a single protocol conversion operation; the transmission certificate digest is a digest value obtained by hashing the transmission certificate, used to fix the authenticity verification certificate for a single transfer; the association digest is used to indicate the binding relationship between the protocol conversion certificate and the transmission certificate; the protocol conversion witness chain is used to record the protocol conversion relationship, payload digest connection relationship, and certificate succession relationship of the same international trade document in different transfer stages, so that subsequent transfer nodes can verify the source continuity and conversion credibility of the target communication payload based on the on-chain records.

[0105] In practical implementation, firstly, the communication gateway retrieves the protocol conversion certificate and transmission certificate. To avoid digest calculation deviations caused by differences in encoding and text format between different devices, unified byte normalization processing is performed on the two types of certificate data: the certificate data is uniformly translated into a UTF-8 standard byte stream, redundant whitespace characters and format control characters are cleaned, and the character format is unified to ensure that the original bytes participating in the hash calculation are completely consistent. After normalization, the SHA-256 hash algorithm is used to perform hash operations on the two types of normalized certificate data respectively, generating unique corresponding conversion certificate digests and transmission certificate digests. To avoid data edge cases caused by simple string concatenation... To address boundary confusion and collision issues, the gateway uses a dedicated fixed separator to distinguish field boundaries according to the system's preset standardized rules. It strictly adheres to a fixed concatenation order: conversion credential summary first, followed by transmission credential summary. The concatenation result is then hashed using the same SHA-256 algorithm to generate a unique association summary for each transfer. This association summary strongly binds the protocol conversion credential and transmission credential into an indivisible evidence unit. Any credential tampering, loss, or replacement will cause the association summary verification to fail, effectively avoiding the risks of credential splitting verification and single-point tampering. This achieves integrated evidence binding of protocol conversion compliance behavior and business authenticity verification results. Secondly, the communication gateway follows a preset fixed structured encapsulation specification. All parameters are systematically collected according to a fixed field arrangement order: association summary, pre-conversion payload summary, post-conversion payload summary, transfer sequence number, and on-chain index of the preceding credential. Simultaneously, field compliance verification is performed, eliminating null values ​​and abnormal format data, unifying the data type and storage format of each field, and finally encapsulating and generating on-chain registration data with fixed fields, standardized structure, accurate parsing by smart contracts, and adaptability to blockchain evidence storage requirements.

[0106] In addition, in the specific implementation, the communication gateway calls the dedicated smart contract write interface built into the blockchain node to complete the permission verification and format pre-verification, and then uploads the registered data on the chain for evidence storage. Next, after receiving the on-chain registration data, the smart contract first performs a pre-verification of field integrity. This verifies whether core fields such as the association digest, dual payload digest, flow sequence number, and on-chain index of the preceding certificate are complete, and whether there are any null values ​​or illegal formats, filtering out invalid evidence storage requests. Based on the verification of field completeness and compliance, the smart contract extracts the conversion certificate digest and transmission certificate digest embedded in the data. It reuses the SHA-256 hash algorithm, fixed digest concatenation order, and boundary separation rules that are completely consistent with the gateway end, and re-iterates and calculates a new association digest locally to avoid verification deviations caused by cross-device and cross-end algorithm differences. The smart contract performs a byte-level consistency comparison between the newly recalculated association digest locally and the original association digest pre-stored in the on-chain registration data. If the two match completely, it determines that the binding relationship between the protocol conversion certificate and the transmission certificate corresponding to this flow is genuine, complete, and without tampering or missing parts. If there are any differences in the byte content, it directly determines that the certificate binding relationship is abnormal, rejects this data from being uploaded to the chain, and marks the abnormal flow log, achieving accurate and compliant verification of the certificate binding relationship.

[0107] In addition, in specific implementation, under the premise that the association summary verification is completely passed, the smart contract initiates the time-series chain aggregation logic to complete the construction of the full-link witness chain. Specifically, the smart contract uses the globally unique time-series flow sequence number in the on-chain registered data, combined with the on-chain index of the previous protocol conversion certificate, to anchor the time-series progression relationship between the current flow node and the previous flow node, and constructs a successor chain association mapping of adjacent certificates. The entire process follows the core rules of document flow of increasing time sequence, connected payload, and progressive nodes, prohibiting reverse association, cross-series binding, and duplicate attachment of abnormal association behaviors, ensuring that the chain structure is completely matched with the real cross-institutional flow path. The smart contract solidifies and stores the on-chain registered data, successor association relationship of certificates, and node time sequence position information of this compliant on-chain data in blocks, and successively aggregates the protocol conversion records, payload data fingerprints, and certificate binding and storage information of each cross-institutional flow node, and finally connects them in an orderly manner to form a protocol conversion witness chain that covers the entire process of international trade documents, is traceable node by node, is time-unique, and cannot be tampered with.

[0108] It should be noted that by binding two types of core vouchers with standardized association summaries, a strong correlation is achieved between protocol conversion adaptation operations and the results of factor fidelity verification. Any tampering or missing data in either type of voucher will lead to the failure of association summary verification, thus avoiding the risks of voucher splitting verification and data tampering from the root. At the same time, by relying on the time sequence flow number and on-chain index to build the successive association of vouchers, the protocol conversion operations of the same document in different cross-institutional flow nodes can be sequentially linked to form complete and traceable chain-like evidence storage data.

[0109] In step S104, in response to the verification request for receiving the target communication payload initiated by the document receiving terminal of the target transfer node, a comprehensive trusted verification is performed based on the protocol conversion witness chain to obtain a trusted verification result.

[0110] In specific implementation, in response to the document receiving terminal of the target transfer node initiating a reception verification request for the target communication payload, that is: after receiving the target communication payload, the document receiving terminal of the target transfer node initiates a reception verification request to the cross-institutional communication gateway. The reception verification request includes a summary of the target communication payload, the identifier of the target transfer node, and the on-chain index corresponding to this transfer. After receiving the request, the cross-institutional communication gateway triggers a comprehensive trusted verification process based on the protocol conversion witness chain.

[0111] In some embodiments, comprehensive trust verification is performed based on the protocol conversion witness chain to obtain the trust verification result, which can be specifically achieved in the following manner:

[0112] According to the successor-successor relationship and flow sequence in the protocol conversion witness chain, verify the on-chain index connection relationship and the flow sequence number continuity relationship between adjacent protocol conversion certificates;

[0113] Verify whether the converted payload summary of the previous protocol conversion document is consistent with the converted payload summary of the subsequent protocol conversion document in adjacent protocol conversion documents;

[0114] Based on the converted payload digest of the end protocol conversion certificate and the target payload digest received by the target transfer node, verify whether the target payload received by the target transfer node is consistent with the end payload of the protocol conversion witness chain.

[0115] Based on the cross-border gateway permissions, node access permissions, and the conversion rules corresponding to the protocol conversion operator, verify whether this cross-border protocol conversion is an authorized and compliant operation.

[0116] A reliable verification result is generated based on the verification results of each verification.

[0117] It should be noted that the final protocol conversion certificate is the last protocol conversion certificate in the protocol conversion witness chain, and its converted payload digest should be consistent with the digest of the target communication payload actually received by the target transfer node.

[0118] In practice, firstly, the cross-institutional communication gateway starts from the initial protocol conversion certificate in the protocol conversion witness chain and verifies the on-chain index connection relationship and the continuity of the flow sequence number between adjacent protocol conversion certificates according to the flow sequence and successor relationship. If the on-chain index connection relationship between any adjacent certificates is not established or the flow sequence number is discontinuous, the witness chain integrity verification is deemed to have failed, and the entire trust verification process is terminated. Secondly, after verifying the integrity of the witness chain, the cross-institutional communication gateway verifies the payload connection relationship between adjacent protocol conversion certificates pair by pair. Specifically, for each pair of adjacent certificates, it compares whether the converted payload digest of the previous certificate and the converted payload digest of the next certificate are completely byte-matched. If the payload digests of any pair of adjacent certificates are inconsistent, the payload connection verification is deemed to have failed, the protocol conversion witness chain is broken, and the trust verification process is terminated. Then, the converted payload digest of the protocol conversion certificate at the end of the protocol conversion witness chain is obtained and precisely compared with the digest data of the target communication payload received by the current target transfer node after normalized hash calculation. If they match, it indicates that the payload received by the target transfer node is consistent with the payload recorded at the end of the witness chain, and the payload has not been tampered with. If they do not match, the target payload verification is deemed to have failed. Next, the pre-stored cross-border gateway authorization table and node access permission list are retrieved, and combined with the built-in adaptation rules of the protocol conversion operator called in this transfer, the cross-border protocol conversion is verified to be an authorized and compliant operation. The specific verification contents include: whether the cross-institutional communication gateway performing the protocol conversion is in the authorized gateway list, whether the target transfer node has access permissions, and whether the protocol conversion operator used in this conversion conforms to the built-in adaptation rules. If any verification item fails, the authorization compliance verification is deemed to have failed. Finally, the cross-organizational communication gateway generates a trusted verification result based on the verification results of the above-mentioned verification items: if all verification items pass the verification, the trusted verification result is passed, indicating that the target communication payload is trusted, the protocol conversion witness chain is complete, and the conversion operation is compliant; if any verification item fails, the trusted verification result is failed, and the specific anomaly type such as link breakage, data tampering, and unauthorized operation is accurately located based on the failed verification dimension.

[0119] It should be noted that, through a four-layer progressive verification of the integrity of the protocol conversion witness chain, the consistency of payload connection, the authenticity of the end payload, and the compliance of authorization, a systematic and reliable verification of the entire process of cross-protocol transfer of international trade documents is achieved; the hierarchical comparison mechanism of payload summaries ensures that any data inconsistency at any stage can be accurately located; and the authorization compliance verification prevents unauthorized gateways or nodes from participating in the document transfer, thereby improving the security and reliability of cross-institutional document transfer.

[0120] In step S105, based on the trusted verification result, the document receiving terminal is controlled to accept and transfer the target communication payload.

[0121] In some embodiments, controlling the acceptance and transfer behavior of the document receiving terminal for the target communication payload based on the trusted verification result can be achieved in the following ways:

[0122] When the trusted verification result is passed, an acceptance permission instruction is sent to the target transfer node, driving the document receiving terminal to perform the storage operation, document review operation, service forwarding operation or subsequent protocol conversion operation of the target communication payload;

[0123] When the trusted verification result fails, a blocking command is sent to the target transfer node to control the document receiving terminal to suspend the acceptance, storage, or continued transfer of the target communication payload.

[0124] First, the document receiving terminal obtains the trusted verification result and identifies whether the trusted verification result is passed or failed: when the trusted verification result is passed, the cross-organizational communication gateway sends an acceptance permission instruction to the target transfer node; the acceptance permission instruction includes an acceptance permission identifier, a digest value of the target communication payload, and a trusted verification result certificate; after receiving the acceptance permission instruction, the document receiving terminal matches the corresponding execution action according to the local preset business transfer rules: if it needs to be archived, it performs the warehousing and archiving operation; if it needs to be manually reviewed, it submits the document review process; if it needs to continue cross-organizational transmission, it performs the business forwarding or connection protocol conversion operation; before executing any business operation, the terminal first uses the unified data regularization and hash calculation standard of steps S102 and S103 to perform a secondary digest calculation on the currently received target communication payload, and performs a byte-level consistency comparison with the standard digest carried by the instruction. Only after the secondary verification is correct can the subsequent business process be promoted, to avoid the payload being tampered with after the pre-verification is passed. Secondly, when the trusted verification result fails, the cross-institutional communication gateway sends a blocking instruction to the target transfer node. This blocking instruction includes a blocking reason identifier, failed verification item information, abnormal communication transfer type, and corresponding witness chain node index information. Upon receiving the blocking instruction, the document receiving terminal immediately freezes all business processes of this payload, prohibiting acceptance, storage, review, and forwarding operations, and locally records this blocking anomaly. Simultaneously, the communication gateway reuses the unified on-chain data encapsulation rules from step S103, packaging the verification dimension, anomaly type, corresponding transfer sequence number, and voucher index information of this failed verification onto the blockchain for evidence storage, enabling auditable and traceable abnormal transfers. After completing the acceptance or blocking operation, the terminal sends the operation execution result back to the cross-institutional communication gateway, completing the closed-loop process of a single trusted document transfer.

[0125] It should be noted that by distinguishing between verification success and verification failure and executing acceptance permission or blocking operations respectively, the document receiving terminal can automatically execute the corresponding processing logic based on the trusted verification result, thereby improving the automation level and security of cross-institutional document transfer.

[0126] Therefore, this application demonstrates several key advantages. First, it adaptively selects between protocol conversion and direct routing based on communication protocol matching, avoiding redundant operations, reducing data processing overhead, and enhancing adaptability to multi-protocol scenarios. Second, by adaptively extracting flow retention factors and quantifying the compliance of factor mapping, combined with dual-credential association binding and chain-based evidence storage mechanisms, it deeply links protocol conversion adaptation behavior with business data authenticity verification results. Relying on time sequence numbers and on-chain indexes to connect the entire flow record, it constructs an immutable and fully traceable document flow link, avoiding risks such as credential forgery, split verification, and data tampering, ensuring the authenticity and integrity of the flow data. Third, by adopting a four-layer progressive layered verification mechanism, it can verify the integrity of the witness chain, the consistency of payload connection, the authenticity of end data, and the compliance of flow operations node by node, effectively locating abnormal flow nodes and problem types, and intercepting unauthorized flow behavior. Finally, based on the verification results, differentiating actions are taken to accept and archive or block the transfer of documents, thereby achieving automated management of document circulation and effectively improving the security, standardization, and traceability of cross-institutional transfer of international trade documents under heterogeneous agreements.

[0127] In summary, the technical solution adopted in this application can realize traceable verification and reliable flow control of international trade documents across nodes.

[0128] Furthermore, in another aspect of this application, in some embodiments, this application provides a blockchain-based trusted transfer management system for international trade documents, referencing... Figure 4 The figure is a schematic diagram of the structure of a blockchain-based trusted international trade document management system according to some embodiments of this application. The blockchain-based trusted international trade document management system includes:

[0129] Protocol conversion module 201 is used to perform protocol conversion based on the current payload status corresponding to the international trade document and the communication interface description file of the target transfer node, and generate the target communication payload.

[0130] The credential generation module 202 is used to generate a protocol conversion credential by the cross-agency communication gateway in combination with the current payload status and the target communication payload, and to generate a transmission credential based on the transmission retention factor before and after the protocol conversion.

[0131] The witness chain construction module 203 is used to associate the transmission certificate and the protocol conversion certificate into the blockchain to form a protocol conversion witness chain for the international trade document among multiple circulation nodes.

[0132] Witness chain verification module 204 is used to respond to the document receiving terminal of the target transfer node's reception verification request for the target communication payload, and perform comprehensive trusted verification based on the protocol conversion witness chain to obtain a trusted verification result.

[0133] The transfer control module 205 is used to control the acceptance and transfer behavior of the target communication payload by the document receiving terminal based on the trusted verification result.

[0134] In addition, this application also provides a computer device, which includes a memory and a processor. The memory stores code, and the processor is configured to acquire the code and execute the above-described blockchain-based trusted transfer management method for international trade documents.

[0135] In some embodiments, reference Figure 5 The figure is a schematic diagram of the structure of a computer device implementing a blockchain-based trusted transfer management method for international trade documents, according to some embodiments of this application. The blockchain-based trusted transfer management method for international trade documents in the above embodiments can... Figure 5 The computer device shown is used to implement this, and the computer device includes at least one processor 301, a communication bus 302, a memory 303, and at least one communication interface 304.

[0136] The processor 301 may be a general-purpose central processing unit (CPU), an application-specific integrated circuit (ASIC), or one or more devices used to control the execution of the blockchain-based trusted transfer management method for international trade documents in this application.

[0137] The communication bus 302 can be used to transmit information between the aforementioned components.

[0138] The memory 303 may be a read-only memory (ROM) or other type of static storage device capable of storing static information and instructions, random access memory (RAM) or other type of dynamic storage device capable of storing information and instructions, or electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compressed optical discs, laser discs, optical discs, digital universal optical discs, Blu-ray discs, etc.), magnetic disks or other magnetic storage devices, or any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible by a computer, but not limited thereto. The memory 303 may exist independently and be connected to the processor 301 via the communication bus 302. The memory 303 may also be integrated with the processor 301.

[0139] The memory 303 stores program code for executing the scheme of this application, and its execution is controlled by the processor 301. The processor 301 executes the program code stored in the memory 303. The program code may include one or more software modules. In the above embodiments, the determination of the blockchain-based international trade document trusted flow management method can be implemented by the processor 301 and one or more software modules in the program code in the memory 303.

[0140] Communication interface 304 uses any transceiver-like device for communicating with other devices or communication networks, such as Ethernet, radio access network (RAN), wireless local area networks (WLAN), etc.

[0141] In a specific implementation, as one example, a computer device may include multiple processors, each of which may be a single-core (single-CPU) processor or a multi-core (multi-CPU) processor. Here, a processor may refer to one or more devices, circuits, and / or processing cores used to process data (e.g., computer program instructions).

[0142] The aforementioned computer device can be a general-purpose computer device or a special-purpose computer device. In specific implementations, the computer device can be a desktop computer, a portable computer, a network server, a handheld digital assistant (PDA), a mobile phone, a tablet computer, a wireless terminal device, a communication device, or an embedded device. This application does not limit the type of computer device.

[0143] In addition, this application also provides a computer-readable storage medium storing a computer program, which, when executed by a processor, implements the above-mentioned blockchain-based trusted transfer management method for international trade documents.

[0144] Although preferred embodiments of this application have been described, those skilled in the art, upon learning the basic inventive concept, can make other changes and modifications to these embodiments. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments as well as all changes and modifications falling within the scope of this application.

[0145] Obviously, those skilled in the art can make various modifications and variations to this application without departing from the spirit and scope of this application. Therefore, if such modifications and variations fall within the scope of the claims of this application and their equivalents, this application also intends to include such modifications and variations.

Claims

1. A blockchain-based method for the trusted transfer and management of international trade documents, characterized in that, The steps include the following: Based on the current payload status corresponding to the international trade documents and the communication interface description file of the target transfer node, the protocol is converted to generate the target communication payload; The cross-agency communication gateway generates a protocol conversion certificate by combining the current payload status with the target communication payload, and generates a transmission certificate based on the transmission retention factor before and after the protocol conversion; The transmission certificate and the protocol conversion certificate are associated and written into the blockchain to form a protocol conversion witness chain for the international trade documents among multiple circulation nodes; In response to the document receiving terminal of the target transfer node initiating a verification request for the target communication payload, a comprehensive trusted verification is performed based on the protocol conversion witness chain to obtain a trusted verification result. Based on the trusted verification result, the document receiving terminal is controlled to accept and transfer the target communication payload.

2. The method as described in claim 1, characterized in that, Based on the current payload status corresponding to the international trade documents and the communication interface description file of the target flow node, protocol conversion is performed to generate the target communication payload, which specifically includes: The cross-agency communication gateway determines the protocol conversion operator based on the current communication protocol in the current payload status corresponding to the international trade document and the communication interface description file corresponding to the target transfer node; When the current communication protocol is inconsistent with the target communication protocol in the communication interface description file, the protocol conversion operator performs cross-border protocol adaptation conversion on the current communication payload to generate the target communication payload. When the current communication protocol is consistent with the target communication protocol, node routing encapsulation is performed on the current communication payload to generate a target communication payload with the target flow node interface identifier.

3. The method as described in claim 1, characterized in that, The protocol conversion certificate generated by the cross-agency communication gateway, combining the current payload status with the target communication payload, specifically includes: The cross-institutional communication gateway obtains the conversion session identifier corresponding to this cross-border protocol conversion and the on-chain index of the previous protocol conversion certificate; Normalized summaries are extracted from the current communication payload and the target communication payload respectively to obtain the pre-conversion payload summary and the post-conversion payload summary; Based on the operator identifier, operator version, and conversion rule summary of the protocol conversion operator, generate the operator execution fingerprint; A conversion context summary is generated based on the pre-conversion payload summary, the post-conversion payload summary, the operator execution fingerprint, the conversion session identifier, and the on-chain index of the previous protocol conversion credential. The witness data to be signed, which includes the transformation context digest and the anti-replay challenge, is digitally signed to obtain the gateway signature; The witness data to be signed, the gateway signature, and the operator execution fingerprint are encapsulated into a protocol conversion credential and stored in the secure storage area of ​​the cross-agency communication gateway.

4. The method as described in claim 1, characterized in that, The generation of transmission credentials based on the transmission retention factors before and after the protocol conversion specifically includes: Transmission preservation factors are extracted from the current communication payload before protocol conversion and the target communication payload after protocol conversion, respectively, to obtain the set of preservation factors before conversion and the set of preservation factors after conversion. According to the mapping rules corresponding to the protocol conversion operator, establish the factor mapping relationship between the pre-conversion retention factor set and the post-conversion retention factor set; Based on the preservation relationship determination rule, the factor mapping relationship is verified to obtain the preservation relationship verification result; When the relationship verification result is passed, a transmission certificate is generated based on the factor mapping relationship, the protocol conversion operator identifier, the current transfer sequence number, and the corresponding protocol conversion certificate.

5. The method as described in claim 1, characterized in that, The process of associating the transmission certificate with the protocol conversion certificate and writing it into the blockchain to form a protocol conversion witness chain for the international trade document across multiple circulation nodes specifically includes: Obtain the conversion credential digest and the transmission credential digest, and generate an associated digest based on the conversion credential digest and the transmission credential digest; The associated summary, the payload summary before and after conversion, the current transfer sequence number, and the on-chain index of the previous protocol conversion certificate are encapsulated into on-chain registration data. The on-chain registration data is submitted to the blockchain by calling the smart contract interface of the blockchain node through the cross-institutional communication gateway; The smart contract re-determines the association digest based on the conversion credential digest and the transmission credential digest, and verifies whether the re-obtained association digest is consistent with the association digest in the on-chain registration data; When the associated digest verification passes, the successor relationship between adjacent protocol conversion certificates is established, and a protocol conversion witness chain is generated based on the flow sequence and payload connection logic.

6. The method as described in claim 1, characterized in that, Based on the aforementioned protocol, a comprehensive trust verification is performed on the witness chain to obtain the following specific trust verification results: According to the successor-successor relationship and flow sequence in the protocol conversion witness chain, verify the on-chain index connection relationship and the flow sequence number continuity relationship between adjacent protocol conversion certificates; Verify whether the converted payload summary of the previous protocol conversion document is consistent with the converted payload summary of the subsequent protocol conversion document in adjacent protocol conversion documents; Based on the converted payload digest of the end protocol conversion certificate and the target payload digest received by the target transfer node, verify whether the target payload received by the target transfer node is consistent with the end payload of the protocol conversion witness chain. Based on the cross-border gateway permissions, node access permissions, and the conversion rules corresponding to the protocol conversion operator, verify whether this cross-border protocol conversion is an authorized and compliant operation. A reliable verification result is generated based on the verification results of each verification.

7. The method as described in claim 1, characterized in that, Based on the trusted verification result, controlling the acceptance and transfer behavior of the document receiving terminal for the target communication payload specifically includes: When the trusted verification result is passed, an acceptance permission instruction is sent to the target transfer node, driving the document receiving terminal to perform the storage operation, document review operation, service forwarding operation or subsequent protocol conversion operation of the target communication payload; When the trusted verification result fails, a blocking command is sent to the target transfer node to control the document receiving terminal to suspend the acceptance, storage, or continued transfer of the target communication payload.

8. A blockchain-based trusted transfer management system for international trade documents, used to execute the blockchain-based trusted transfer management method for international trade documents as described in any one of claims 1 to 7, characterized in that, The system includes: The protocol conversion module is used to perform protocol conversion based on the current payload status of the international trade documents and the communication interface description file of the target flow node, and generate the target communication payload. The certificate generation module is used to generate protocol conversion certificates by the cross-agency communication gateway in combination with the current payload status and the target communication payload, and to generate transmission certificates based on the transmission retention factor before and after the protocol conversion. The witness chain construction module is used to associate the transmission certificate and the protocol conversion certificate and write them into the blockchain to form a protocol conversion witness chain for the international trade documents among multiple circulation nodes; The witness chain verification module is used to respond to the verification request for receiving the target communication payload initiated by the document receiving terminal of the target transfer node, and to perform a comprehensive trusted verification based on the protocol conversion witness chain to obtain a trusted verification result. The transfer control module is used to control the acceptance and transfer behavior of the target communication payload by the document receiving terminal based on the trusted verification result.

9. A computer device, characterized in that, The computer device includes a memory and a processor, the memory storing code, and the processor being configured to retrieve the code and execute the blockchain-based trusted transfer management method for international trade documents as described in any one of claims 1 to 7.

10. A computer-readable storage medium storing a computer program, characterized in that, When the computer program is executed by the processor, it implements the blockchain-based trusted transfer management method for international trade documents as described in any one of claims 1 to 7.

Images