A blockchain-based cross-domain business process collaborative trusted data communication method and system

Abstract

The application relates to the technical field of business process collaboration, and discloses a cross-domain business process collaboration credible data communication method and system based on a block chain, which comprises the following steps: S1. constructing a communication intelligent contract; S2. sending an asymmetric key pair to each party participating in business collaboration in a block chain; S3. sending a request for initiating business data transmission to a business data receiver; S4. the receiver obtaining the request content in step S3 by listening to the block chain and analyzing the request content; S5. the receiver generating a transmission key pair and a business data transmission subject and initiating a response to the business data sender; S6. the sender obtaining the response content; S7. the sender generating a result of encrypting business data by using a public key and sending the result of encrypting the business data by using the public key to the receiver; S8. the receiver obtaining the result by transmitting the public key and listening to the block chain, and obtaining the business data by analyzing the result by using the transmission key. The application solves the problem that the existing business process collaboration technology cannot guarantee confidentiality and anonymous communication, and has the characteristics of high efficiency and convenience.

Description

Technical Field

[0001] This invention relates to the field of business process collaboration technology, and more specifically, to a blockchain-based cross-domain business process collaboration trusted data communication method and system. Background Technology

[0002] Cross-domain business process collaboration, such as supply chain cooperation, can effectively utilize the resources of all parties involved to improve their respective performance. However, data communication in collaboration is quite complex. Because the visibility of data varies in different scenarios, it is not fully visible to all participants, thus requiring confidentiality in data communication.

[0003] Blockchain is a key concept in cryptocurrency, essentially a decentralized distributed database. The network transaction information blocks generated at the blockchain's underlying layer require cryptographic principles to establish relationships between successive blocks, thereby verifying the validity of information and ensuring its immutability. While much research has focused on using smart contracts in blockchains to control the orderly execution of collaborative processes and improve trustworthiness, these studies rarely address data visibility issues. Without data processing, data is typically transmitted on the blockchain through public broadcasting.

[0004] While using blockchain technology to regulate and ensure orderly collaboration in cross-domain business processes, there is an urgent need to guarantee the confidentiality of business data transmission to ensure the trustworthiness of data communication. Furthermore, as in supply chain collaboration, there is a need to prevent the transmission of business data from being detected, necessitating a degree of anonymous communication, which is also crucial for ensuring the trustworthiness of data communication. Therefore, how to achieve trustworthy data communication in cross-domain business processes such as supply chain collaboration while meeting the requirements of confidentiality and anonymity is the technical problem this application aims to solve.

[0005] A data asset trading method, computer device, and readable storage medium based on blockchain are disclosed. Specifically, this invention builds a blockchain network based on the Fabric blockchain framework, treating data assets as private data and uploading them to the chain. This allows the uploaded data to retain hash digests while simultaneously removing specific data within a limited time, solving the data redundancy problem caused by multiple sales of data assets and reducing the storage pressure on the blockchain.

[0006] However, existing technologies have not solved the problem that existing business process collaboration technologies cannot guarantee confidentiality and anonymous communication. Therefore, how to invent a process collaboration data communication method that guarantees confidentiality and anonymous communication is an urgent problem to be solved in this technical field. Summary of the Invention

[0007] To address the issues of confidentiality and anonymous communication in existing business process collaboration technologies, this invention provides a blockchain-based cross-domain business process collaboration trusted data communication method and system, which is highly efficient and convenient.

[0008] To achieve the above-mentioned objectives of this invention, the technical solution adopted is as follows:

[0009] A blockchain-based method for trusted data communication in cross-domain business processes includes the following steps:

[0010] S1. Construct communication smart contracts suitable for business data transmission in blockchain-based business process collaboration;

[0011] S2. Send a unique pair of asymmetric keys to each party participating in the blockchain business collaboration. The public key is publicly visible and serves as the basis for authentication of the participants, while the private key is kept by each party.

[0012] S3. When data transmission is required, the business data sender calls the communication smart contract to generate a request for business data transmission and initiates the request to the business data receiver.

[0013] S4. The business data recipient obtains the request content from step S3 by listening to the blockchain, verifies the identity of the business data sender, and parses the request content using the recipient's own private key.

[0014] S5. The business data receiver generates a pair of business data transmission key pairs and a business data transmission topic locally, and calls the communication smart contract to generate a response and send a response to the business data sender;

[0015] S6. The business data sender obtains the response content in step S5 by listening to the blockchain, verifies the identity of the business data receiver, and uses the sender's own private key to obtain the business data transmission public key and business data transmission topic.

[0016] S7. The business data sender generates the result of public key encryption of business data by calling the smart contract, and sends the result of public key encryption of business data to the business data receiver.

[0017] S8. The business data recipient obtains the result in step S7 by listening to the blockchain, transmitting the public key, and then obtaining the business data through the business data transmission key parsing result generated in step S5.

[0018] Preferably, the smart contract specifically includes:

[0019] Field 1: Topic: The subject of the message;

[0020] Field 2: Data: The encrypted message;

[0021] Field 3: Sender: The sender's identity;

[0022] Field 4: Digest: The sender's digital signature;

[0023] Field 5: EnvNonce: Represents proof of work.

[0024] Furthermore, in step S2, a unique pair of asymmetric keys is sent to each party participating in the blockchain business collaboration, specifically as follows:

[0025] When each party involved in a business collaboration joins the blockchain, they receive a unique asymmetric key pair. The public key is publicly visible and serves as the basis for authentication of participating parties, while the private key is kept secret by each party. The public key is denoted as K. x The private key is denoted as K. x ′, K x As can be seen from all parties, K x Only x itself is visible; for the transmitted message D, we have:

[0026] K′ X (K x (D))=D.

[0027] Furthermore, in step S3, the business data sender invokes the communication smart contract to generate a request for business data transmission and initiates the request to the business data receiver, specifically as follows:

[0028] Sender A initiates a data transmission request to receiver B. Let the request content be Q. B's public key is used to process and embed the information into Q, resulting in message K. B (Q) Stored on all members of the blockchain; the communication method smart contract field description is as follows:

[0029] Topic = K B

[0030] DATA=K B (Q)

[0031] Sender = K A

[0032] Digest = K A ′(SM3(K B (Q))).

[0033] Furthermore, in step S4, verifying the identity of the service data sender specifically involves:

[0034] The receiver calculates the hash value H1 of Data using the national cryptographic SM3 algorithm, and simultaneously calculates the hash value H2 calculated by the sender using the sender and digest algorithms, where H2 = K. A (Digest); If H1 = H2, it means that the message did indeed come from A and has not been tampered with.

[0035] Furthermore, in step S5, the service data receiver locally generates a pair of service data transmission key pairs and a service data transmission topic, specifically as follows:

[0036] The receiver generates an asymmetric key pair K using the national cryptographic SM2 algorithm, which is used exclusively for this data transmission. t and K′ t and a temporary Topic T t , public key K t After being encapsulated into a message, it is processed and embedded with Data; the smart contract field description for the communication method is as follows:

[0037] Topic = K A

[0038] DATA=K A (K t T t )

[0039] Sender = V B

[0040] Digest = K B ′(SM3(K A (K t T t ))).

[0041] Furthermore, in step S6, verifying the identity of the business data recipient specifically involves:

[0042] The sender calculates the hash value H1 of Data using the national cryptographic SM3 algorithm, and simultaneously calculates the hash value H2 calculated by the receiver using the sender and digest methods, where H2 = K. B (Digest); H1 = H2, indicating that the message indeed came from B, has not been tampered with, and the sender deciphered the original message using its own private key, K. A ′(DATA), parsing the key K used for data transmission t and data transmission Topic T t .

[0043] Furthermore, in step S7, when the business data sender generates the result of public-key encrypted business data by calling the smart contract and sends the result of public-key encrypted business data to the business data receiver, sender A uses K. t Encrypt the data using T t As a Topic; the smart contract field description for the communication method is as follows:

[0044] Topic = T t

[0045] DATA=K t (D)

[0046] Sender = K A

[0047] Digest = K A ′(SM3(K t (D))).

[0048] Furthermore, in step S8, the business data is obtained through the business data transmission key parsing result generated in step S5, specifically by: obtaining the business data through the K key generated by the receiver in step S5. t ′, as the encryption key K t The corresponding decryption key, the method to obtain data D is to use K t Decrypt DATA, D = K t ′(DATA)=K t ′(DATA=K t (D)).

[0049] A blockchain-based cross-domain business process collaborative trusted data communication system includes a contract construction module, a key sending module, a message processing module, a message listening module, a message sending module, and a data storage module.

[0050] The contract construction module is used to call the communication smart contract to generate a request for business data transmission; and to generate the result of public key encryption of business data by calling the smart contract.

[0051] The key sending module is used to send a unique pair of asymmetric keys to each party participating in the blockchain business collaboration. The public key is publicly visible and serves as the basis for authentication of the participants, while the private key is kept by each party.

[0052] The message processing module is used to call the content of the communication smart contract to generate a request for business data transmission; verify the identity of the business data sender, and use the receiver's own private key to parse the request content; and use the sender's own private key to obtain the business data transmission public key and the business data transmission topic.

[0053] The message monitoring module is used to monitor the blockchain, obtain the request content in step S3, and verify the identity of the business data sender; monitor the blockchain, obtain the response content, and verify the identity of the business data receiver; monitor the blockchain, transmit the public key through the communication smart contract content, and obtain the transmitted content.

[0054] The message sending module is used to respond to the business data sender by calling the content of the communication smart contract; and to send the result of encrypting the business data with the public key to the business data receiver.

[0055] The data storage module is used to receive the request content, business data, business data transmission public key, and business data transmission topic parsed by the message processing module.

[0056] The beneficial effects of this invention are as follows:

[0057] This invention discloses a blockchain-based method for trusted data communication in cross-domain business process collaboration. Specifically, it constructs a communication smart contract suitable for business data transmission in blockchain-based business process collaboration. The smart contract generates the transmission request, response content, and the result of encrypting business data with a public key. Combining the public and private keys, the generated content is parsed to perform trusted data communication in cross-domain business process collaboration. This solves the problem that existing business process collaboration technologies cannot guarantee confidentiality and anonymous communication, and is highly efficient and convenient. Attached Figure Description

[0058] Figure 1 This is a flowchart of a blockchain-based cross-domain business process collaborative trusted data communication method as described in this invention.

[0059] Figure 2 This is an interactive diagram illustrating the application of the blockchain-based cross-domain business process collaborative trusted data communication method described in this invention to cross-domain business process collaboration.

[0060] Figure 3 This is a data transmission flowchart of a blockchain-based cross-domain business process collaborative trusted data communication method according to the present invention.

[0061] Figure 4 This is a schematic diagram illustrating the interaction of various modules during business data transmission in the blockchain-based cross-domain business process collaborative trusted data communication method and system described in this invention.

[0062] Figure 5 This is a schematic diagram illustrating the specific functions of each module in a blockchain-based cross-domain business process collaborative trusted data communication method and system during business data transmission, as described in this invention. Detailed Implementation

[0063] The present invention will now be described in detail with reference to the accompanying drawings and specific embodiments.

[0064] Example 1

[0065] like Figure 1 As shown, a blockchain-based method for cross-domain business process collaborative trusted data communication includes the following steps:

[0066] S1. Construct communication smart contracts suitable for business data transmission in blockchain-based business process collaboration;

[0067] S2. Send a unique pair of asymmetric keys to each party participating in the blockchain business collaboration. The public key is publicly visible and serves as the basis for authentication of the participants, while the private key is kept by each party.

[0068] S3. When data transmission is required, the business data sender calls the communication smart contract to generate a request for business data transmission and initiates the request to the business data receiver.

[0069] S4. The business data recipient obtains the request content from step S3 by listening to the blockchain, verifies the identity of the business data sender, and parses the request content using the recipient's own private key.

[0070] S5. The business data receiver generates a pair of business data transmission key pairs and a business data transmission topic locally, and calls the communication smart contract to generate a response and send a response to the business data sender;

[0071] S6. The business data sender obtains the response content in step S5 by listening to the blockchain, verifies the identity of the business data receiver, and uses the sender's own private key to obtain the business data transmission public key and business data transmission topic.

[0072] S7. The business data sender generates the result of public key encryption of business data by calling the smart contract, and sends the result of public key encryption of business data to the business data receiver.

[0073] S8. The business data recipient obtains the result in step S7 by listening to the blockchain, transmitting the public key, and then obtaining the business data through the business data transmission key parsing result generated in step S5.

[0074] Example 2

[0075] A blockchain-based method for trusted data communication in cross-domain business processes includes the following steps:

[0076] S1. Construct communication smart contracts suitable for business data transmission in blockchain-based business process collaboration;

[0077] S2. Send a unique pair of asymmetric keys to each party participating in the blockchain business collaboration. The public key is publicly visible and serves as the basis for authentication of the participants, while the private key is kept by each party.

[0078] S3. When data transmission is required, the business data sender calls the communication smart contract to generate a request for business data transmission and initiates the request to the business data receiver.

[0079] S4. The business data recipient obtains the request content from step S3 by listening to the blockchain, verifies the identity of the business data sender, and parses the request content using the recipient's own private key.

[0080] S5. The business data receiver generates a pair of business data transmission key pairs and a business data transmission topic locally, and calls the communication smart contract to generate a response and send a response to the business data sender;

[0081] S6. The business data sender obtains the response content in step S5 by listening to the blockchain, verifies the identity of the business data receiver, and uses the sender's own private key to obtain the business data transmission public key and business data transmission topic.

[0082] S7. The business data sender generates the result of public key encryption of business data by calling the smart contract, and sends the result of public key encryption of business data to the business data receiver.

[0083] S8. The business data recipient obtains the result in step S7 by listening to the blockchain, transmitting the public key, and then obtaining the business data through the business data transmission key parsing result generated in step S5.

[0084] like Figure 2 As shown, when the business data communication method and system of this invention are applied to business process collaboration, the business process management system is the center controlling the entire collaboration process. The process collaboration smart contract is used to control the orderly progress of the process collaboration and record the collaboration process in an immutable form on the blockchain. The process collaboration provides an interface for the business process management system to interact with the process collaboration smart contract. These three parts are the basic system for process collaboration based on blockchain. The content of the business data communication method and system of this invention includes: a communication method smart contract for transmitting messages, and business data transmission for the interaction between the business process management system and the communication method smart contract.

[0085] In this embodiment, the present invention uses the national cryptographic SM2 algorithm for generating asymmetric keys and encrypting and decrypting messages; it uses the national cryptographic SM3 algorithm as a hash algorithm for digital signatures and verification; the default underlying blockchain technology also adopts the SM2 and SM3 algorithms; wherein, the SM2 algorithm is an elliptic curve public key cryptography algorithm, and the SM3 algorithm is a cryptographic hash function algorithm.

[0086] In one embodiment, the smart contract specifically includes:

[0087] Field 1: Topic: The subject of the message;

[0088] In this embodiment, the Topic is used by member nodes to filter transactions. If a Topic is the same as the public key of a member node or the public key of data transmission, then the recipient of the transaction is considered to be that member node.

[0089] Field 2: Data: The encrypted message;

[0090] In this embodiment, Data is the result obtained by encrypting the original message using the public key of the member node or the public key of the business data transmission.

[0091] Field 3: Sender: The sender's identity;

[0092] In this embodiment, the sender is represented by the sender's public key.

[0093] Field 4: Digest: The sender's digital signature;

[0094] In this embodiment, Digest first uses the SM3 algorithm to digest the content of Data, and then uses the sender's private key to encrypt and generate a digest using the SM2 algorithm, which is used together with the sender's identity to verify the sender's identity.

[0095] Field 5: EnvNonce: Represents proof of work.

[0096] In this embodiment, EnvNonce is used to detect whether the smart contract parameters generated by the message processing module are incorrect. On the other hand, since this field requires a certain amount of calculation based on the Data field using the SM3 algorithm, it can, to some extent, prevent malicious network members from frequently calling the smart contract and causing interference to the network environment.

[0097] In one embodiment, step S2 involves sending a unique pair of asymmetric keys to each party participating in the blockchain-based business collaboration, specifically as follows:

[0098] When each party involved in a business collaboration joins the blockchain, they receive a unique asymmetric key pair. The public key is publicly visible and serves as the basis for authentication of participating parties, while the private key is kept secret by each party. The public key is denoted as K. X The private key is denoted as K. X ′, K X As can be seen from all parties, K X Only x itself is visible; for the transmitted message D, we have:

[0099] K′ X (K X (D))=D.

[0100] In one embodiment, in step S3, the business data sender invokes the communication smart contract content to generate a request for business data transmission and initiates the request for business data transmission to the business data receiver, specifically as follows:

[0101] Sender A initiates a data transmission request to receiver B. Let the request content be Q. B's public key is used to process and embed the information into Q, resulting in message K. B (Q) Stored on all members of the blockchain; the communication method smart contract field description is as follows:

[0102] Topic = K B

[0103] DATA=K B (Q)

[0104] Sender = K A

[0105] Digest = K A ′(SM3(K B (Q))).

[0106] In this embodiment, for members other than B, because B's private key K is not available... B Therefore, it is impossible to parse the original message. So only B can parse the specific message content.

[0107] In one embodiment, step S4, verifying the identity of the business data sender, specifically involves:

[0108] The receiver calculates the hash value H1 of Data using the SM3 algorithm, and simultaneously calculates the hash value H2 calculated by the sender using the sender and digest algorithms, where H2 = K. A (Digest); If H1 = H2, it means that the message did indeed come from A and has not been tampered with.

[0109] In one embodiment, in step S5, the business data receiver generates a pair of business data transmission key pairs and a business data transmission topic locally, specifically as follows:

[0110] The receiver generates an asymmetric key pair K using the SM2 algorithm, which is used exclusively for this data transmission. t and K′ t and a temporary Topic T t , public key K t After being encapsulated into a message, it is processed and embedded with Data; the smart contract field description for the communication method is as follows:

[0111] Topic = K A

[0112] DATA=K A (K t T t )

[0113] Sender = V B

[0114] Digest = K B ′(SM3(K A (K t T t ))).

[0115] In this embodiment, the purpose of this is to ensure that even if B's ​​private key is leaked, other members will not have K. T To analyze the real message.

[0116] In one embodiment, step S6, verifying the identity of the business data recipient, specifically involves:

[0117] The sender calculates the hash value H1 of Data using the SM3 algorithm, and simultaneously calculates the hash value H2 calculated by the receiver using the sender and digest algorithms, where H2 = K. B (Digest); H1 = H2, indicating that the message indeed came from B, has not been tampered with, and the sender deciphered the original message using its own private key, K. A ′(DATA), parsing the key K used for data transmission t and data transmission Topic T t .

[0118] In this embodiment, for members other than A, because B's private key K is not available... A Therefore, the original message cannot be parsed.

[0119] In one embodiment, in step S7, when the business data sender generates the result of public-key encrypted business data by calling a smart contract and sends the result of public-key encrypted business data to the business data receiver, sender A uses K. t Encrypt the data using T t As a Topic; the smart contract field description for the communication method is as follows:

[0120] Topic = T t

[0121] DATA=K t (D)

[0122] Sender = K A

[0123] Digest = K A ′(SM3(K t (D))).

[0124] In this embodiment, since only A and B, the members of the entire blockchain network, know T... t K t The specific meaning of K is that, therefore, for more convenient and faster data transmission, only A needs to use K. t Encrypt the data using T t As a topic, T can facilitate information filtering for B. At this time, other members of the network do not know about T. t The meaning of "A" is unclear, so it's unknown which member A sent the data to. On the other hand, if the business data needs to be recorded on the process collaboration smart contract, then only the hash value calculated by the SM3 algorithm needs to be recorded.

[0125] In one embodiment, in step S8, obtaining the service data through the service data transmission key parsing result generated in step S5 specifically involves: obtaining the service data through the K key generated by the receiver in step S5. t ′, as the encryption key K t The corresponding decryption key, the method to obtain data D is to use K t Decrypt DATA, D = K t ′(DATA)=K t ′(DATA=K t (D)).

[0126] In this embodiment, receiver B has now received the service data transmitted from sender A. Because the topic is irregular and temporary during the transmission of the service data, other network members only know that A invoked the smart contract, but cannot know the specific communication target, B. If the service data is on a process coordination smart contract, its correctness can be verified using the hash value calculated by the SM3 algorithm.

[0127] like Figure 3 As shown, when the blockchain-based cross-domain business process collaborative trusted data communication method described in this invention is applied, the sender first initiates a business data transmission request to the receiver, then the receiver receives the message, verifies its identity, and responds, then the sender verifies its identity and transmits the business data, and the receiver accepts the business data.

[0128] In this embodiment, a formal analysis of the above communication steps using the Dolev-Yao attacker model is also performed. The following analysis focuses only on whether the attacker can recover the real data from the DATA field. The attacker's information set is initialized as follows:

[0129] T = {K A K B}

[0130] In step two, the attacker's information set expands to:

[0131] T = {K A K B K B (Q), K A ′(SM3(K B (Q)))}

[0132] In step four, the attacker's information set expands to:

[0133] T = {K A K B K B (Q), K A ′(SM3(K B (Q))), K A (K t T t ), K B ′(SM3(K A (K t T t )))}

[0134] During step six, the attacker's information and its expansion are as follows:

[0135] T = {K A K B K B (Q), K A ′(SM3(K B (Q))), K A (K t T t ), K B ′(SM3(K A (K tT t ))), K t (D)}

[0136] For this information set, the decomposition operations that an attacker can perform are:

[0137] K A (K A ′(SM3(K B (Q))))=SM3(K B (Q))

[0138] K B (K B ′(SM3(K A (K t T t ))))=SM3(K A (K t T t ))

[0139] The two new pieces of information extracted are useless for recovering data D.

[0140] Furthermore, if the private keys of A and B are leaked, i.e., K... A ′, K B If '∈T, then the attacker can perform the following decomposition operation:

[0141] K B ′(K B (Q))=Q

[0142] K′ A (K A (K t T t ))=(K t T t )

[0143] At this point, the attacker knows the communication messages between A and B, and can find the specific messages in which A transmits data to B, but because the attacker does not have K... t The corresponding decryption key K t Therefore, the information K transmitted in step six cannot be transferred. t (D) is reduced to D. And K t The storage location of K′ is not in the blockchain, so attackers cannot obtain K′. t .

[0144] Example 3

[0145] like Figure 5As shown, a blockchain-based cross-domain business process collaborative trusted data communication system includes a contract construction module, a key sending module, a message processing module, a message listening module, a message sending module, and a data storage module.

[0146] In this embodiment, the process of business data transmission in the business data communication system of the present invention is as follows: Figure 4 As shown;

[0147] The contract construction module is used to call the communication smart contract to generate a request for business data transmission; and to generate the result of public key encryption of business data by calling the smart contract.

[0148] The key sending module is used to send a unique pair of asymmetric keys to each party participating in the blockchain business collaboration. The public key is publicly visible and serves as the basis for authentication of the participants, while the private key is kept by each party.

[0149] The message processing module is used to call the content of the communication smart contract to generate a request for business data transmission; verify the identity of the business data sender, and use the receiver's own private key to parse the request content; and use the sender's own private key to obtain the business data transmission public key and the business data transmission topic.

[0150] In this embodiment, the message processing module needs to calculate an EnvNonce in all steps, so that the first N bits of the hash value calculated by the SM3 algorithm for “Data+EnvNonce” are 0.

[0151] When data transmission is required, the original business data transmission request information is encrypted using the SM2 algorithm and the public key of the business data receiver, based on the information of the business data sender and the business data receiver. This generates the fields of the communication smart contract and sends it to the message sending module. This message processing module belongs to the business data sender.

[0152] A pair of business data transmission key pairs (asymmetric keys) and a business data transmission topic are generated locally. The fields required by the smart contract for the communication method are generated and sent to the message sending module. At the same time, the message sending module is informed to listen for transactions with Topic = this business data transmission topic. At this time, the message processing module is the business data receiver.

[0153] The message is received from the message listening module. The business data transmission key and business data transmission topic in step four are parsed using the SM2 algorithm. Using the key and topic, along with the original business data, the required fields for generating the communication method smart contract in step six are executed and sent to the message sending module. At this point, the message processing module is the business data sender.

[0154] The message processing module receives messages from the message listening module, uses the key generated in step four and the SM2 algorithm to recover the encrypted data, and sends the recovered data to the data storage module. At this point, the message processing module is the business data receiver.

[0155] The message monitoring module is used to monitor the blockchain, obtain the request content in step S3, and verify the identity of the business data sender; monitor the blockchain, obtain the response content, and verify the identity of the business data receiver; monitor the blockchain, transmit the public key through the communication smart contract content, and obtain the transmitted content.

[0156] In this embodiment, the message listening module filters transactions of the communication smart contract by the Topic field, verifies the EnvNonce field and the identity of the transaction caller, and sends the message to the message processing module if the verification is successful. The initial Topic field set for listening by the business data sender and receiver is Topics = {their own public key}. After executing step four, the business data receiver adds a business data transmission topic T. t Topics = {its own public key, T} t After performing step seven to restore the data, delete the service transmission topic, Topics = {its own public key}.

[0157] The message sending module is used to respond to the business data sender by calling the content of the communication smart contract; and to send the result of encrypting the business data with the public key to the business data receiver.

[0158] The message sending module verifies whether the EnvNonce field meets the requirements of the field information from the message processing module. If the verification is successful, the smart contract calls the communication method to initiate a transaction and send the message to the blockchain.

[0159] The data storage module is used to receive the request content, business data, business data transmission public key, and business data transmission topic parsed by the message processing module.

[0160] In this embodiment, the data storage module is used to receive the data recovered by the message processing module when the business data receiver performs step seven, for querying by the business process management system.

[0161] Obviously, the above embodiments of the present invention are merely examples for clearly illustrating the present invention, and are not intended to limit the implementation of the present invention. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of the present invention should be included within the protection scope of the claims of the present invention.

Claims

1. A blockchain-based method for trusted data communication in cross-domain business processes, characterized in that: Includes the following steps: S1. Construct communication smart contracts suitable for business data transmission in blockchain-based business process collaboration; S2. Send a unique pair of asymmetric keys to each party participating in the blockchain business collaboration, where the public key is publicly visible and serves as the basis for participant identity authentication, while the private key is kept by each party. S3. When data transmission is required, the business data sender calls the communication smart contract to generate a request for business data transmission and initiates the request to the business data receiver. S4. The business data recipient obtains the request content from step S3 by listening to the blockchain, verifies the identity of the business data sender, and parses the request content using the recipient's own private key. S5. The business data recipient generates a pair of business data transmission key pairs and a business data transmission topic locally, and calls the communication smart contract to generate a response and send a response to the business data sender; S6. The business data sender obtains the response content in step S5 by listening to the blockchain, verifies the identity of the business data receiver, and uses the sender's own private key to obtain the business data transmission public key and business data transmission topic; S7. The business data sender generates the result of encrypting the business data with a public key by calling the smart contract, and sends the result of encrypting the business data with a public key to the business data receiver; S8. The business data recipient obtains the result in step S7 by listening to the blockchain, transmitting the public key, and obtaining the business data through the business data transmission key parsing result generated in step S5; The smart contracts specifically include: Field 1: The subject of the message; Field 2: : Encrypted message; Field 3: : Sender's identity; Field 4: The sender's digital signature; Field 5: : Represents proof of workload; In step S2, a unique pair of asymmetric keys is sent to each party participating in the blockchain business collaboration, specifically as follows: When each party involved in a business collaboration joins the blockchain, they receive a unique asymmetric key pair. The public key is publicly visible and serves as the basis for participant authentication, while the private key is kept secret by each party. The public key is denoted as... The private key is recorded as , As can be seen from all parties, only Visible on its own; for the transmitted message have: 。 2. The blockchain-based cross-domain business process collaborative trusted data communication method according to claim 1, characterized in that: In step S3, the business data sender invokes the communication smart contract to generate a request for business data transmission and initiates the request to the business data receiver, specifically as follows: sender To the recipient Initiate a data transmission request, assuming the request content is... ,pass The public key is used for information processing and embedding, and the final message is... Stored across all members of the blockchain; the communication method smart contract field description is as follows: in, This represents the public key of receiver B. This represents the public key of sender A. Indicates national secrets algorithm, This represents the private key of sender A.

3. The blockchain-based cross-domain business process collaborative trusted data communication method according to claim 2, characterized in that: In step S4, verifying the identity of the service data sender specifically involves: The recipient uses national cryptographic standards. The algorithm calculates Hash value At the same time, through and Calculate the hash value calculated by the sender. , ;like This indicates that the message did indeed come from [the source]. And it has not been tampered with.

4. The blockchain-based cross-domain business process collaborative trusted data communication method according to claim 3, characterized in that: In step S5, the service data receiver generates a pair of service data transmission key pairs and a service data transmission topic locally, specifically as follows: The recipient uses national cryptographic standards. The algorithm generates an asymmetric key pair that will be used exclusively for this data transmission. and , and a temporary , public key After being encapsulated into a message, it is processed and embedded. The smart contract field description for the communication method is as follows:

5. The blockchain-based cross-domain business process collaborative trusted data communication method according to claim 4, characterized in that: In step S6, verifying the identity of the business data recipient specifically involves: The sender uses national cryptographic standards. The algorithm calculates Hash value At the same time, through and Calculate the hash value calculated by the receiver. , This indicates that the message did indeed come from [the source]. Furthermore, the message was not tampered with, and the sender was able to parse the original message using their own private key. ( ), deciphering the key used for data transmission and data transmission , This indicates the encrypted message sent by the sender.

6. The blockchain-based cross-domain business process collaborative trusted data communication method according to claim 5, characterized in that: In step S7, when the business data sender generates the public-key encrypted business data by calling the smart contract and sends the public-key encrypted business data result to the business data receiver, use Encrypt the data, use As The smart contract field description for the communication method is as follows: 。 7. The blockchain-based cross-domain business process collaborative trusted data communication method according to claim 6, characterized in that: In step S8, the service data is obtained through the service data transmission key parsing result generated in step S5. Specifically, this involves obtaining the service data through the receiver's step S5... , as encryption key Use the corresponding decryption key to retrieve data. The method is to use right Decryption is required. = ( ) = ( ).

8. A blockchain-based cross-domain business process collaborative trusted data communication system, characterized in that: It includes a contract construction module, a key sending module, a message processing module, a message listening module, a message sending module, and a data storage module; The contract construction module is used to call the communication smart contract to generate a request for business data transmission; and to generate the result of public key encryption of business data by calling the smart contract. The key sending module is used to send a unique pair of asymmetric keys to each party participating in the blockchain business collaboration. The public key is publicly visible and serves as the basis for authentication of the participants, while the private key is kept by each party. The message processing module is used to call the content of the communication smart contract to generate a request for business data transmission; verify the identity of the business data sender, and parse the request content using the receiver's own private key; Use the sender's own private key to obtain the public key for business data transmission and the topic for business data transmission; The message monitoring module is used to monitor the blockchain, obtain the request content in step S3, and verify the identity of the business data sender; monitor the blockchain, obtain the response content, and verify the identity of the business data receiver; monitor the blockchain, transmit the public key through the communication smart contract content, and obtain the transmitted content. The message sending module is used to respond to the business data sender by calling the content of the communication smart contract; and to send the result of encrypting the business data with the public key to the business data receiver. The data storage module is used to receive the request content, business data, business data transmission public key, and business data transmission topic parsed by the message processing module; The smart contracts specifically include: Field 1: The subject of the message; Field 2: : Encrypted message; Field 3: : Sender's identity; Field 4: The sender's digital signature; Field 5: : Represents proof of workload; The specific steps involved in sending a unique asymmetric key pair to each party participating in the blockchain-based business collaboration are as follows: When each party involved in a business collaboration joins the blockchain, they receive a unique asymmetric key pair. The public key is publicly visible and serves as the basis for participant authentication, while the private key is kept secret by each party. The public key is denoted as... The private key is recorded as , As can be seen from all parties, only Visible on its own; for the transmitted message have: 。

Images