Blockchain-based data processing method, apparatus, device, and readable storage medium

Abstract

An embodiment of the present application discloses a data processing method, device, equipment, and readable storage medium based on a blockchain. The method includes: a management node receives invoicing information sent by a first service node through a first blockchain account in a first blockchain; the invoicing information carries first bill information and user geographical information of the user to which the first bill information belongs; the node geographical information to which the first service node belongs is different from the user geographical information; the first blockchain is the blockchain to which the node geographical information belongs; according to the invoicing information, query a second blockchain account in a second blockchain corresponding to the user geographical information; the second blockchain is the blockchain to which the user geographical information belongs; send the first bill information to a second service node in the second blockchain through the second blockchain account, and receive second bill information returned by the second service node, and chain the second bill information to the second blockchain. By using the present application, the generation of cross-region bills can be supported in the blockchain.

Description

Technical Field

[0001] This application relates to the field of computer technologies, and in particular, to a data processing method, apparatus, device, and readable storage medium based on a blockchain. Background Art

[0002] With the popularization of electronic invoices, the usage frequency of electronic invoices in daily life has exceeded that of paper invoices. More and more invoice issuers choose to use relevant systems to issue electronic invoices and then deliver the electronic invoices to the invoice recipients. In order to more conveniently deliver electronic invoices to invoice recipients and store electronic invoices more securely, blockchain technology has been introduced. Since the application of blockchain technology in all walks of life has become increasingly mature, electronic invoices stored in the blockchain can have characteristics such as traceability and information immutability, which can ensure the authenticity of electronic invoices.

[0003] However, currently, for the application of blockchain in electronic invoices, one blockchain corresponds to one province. That is to say, there is one blockchain in a province to store and manage the electronic invoices of this province. If users from other provinces come to this province and need to handle invoice issuance business, this province cannot handle it. That is to say, the prior art cannot support cross-region invoice issuance in the blockchain.

[0004] Application Content

[0005] The embodiments of this application provide a data processing method, apparatus, device, and readable storage medium based on a blockchain, which can support the generation of cross-region bills in the blockchain.

[0006] On the one hand, the embodiments of this application provide a data processing method based on a blockchain, including:

[0007] The management node receives the invoice issuance information sent by the first service node through the first blockchain account; the invoice issuance information carries the first bill information and the user's original regional information of the user to which the first bill information belongs; the node regional information of the first service node is different from the user's original regional information; the first blockchain account is the account of the management node in the first blockchain, and the first blockchain is the blockchain to which the node regional information belongs;

[0008] According to the first blockchain account and the invoice issuance information, query the second blockchain account corresponding to the user's original regional information; the second blockchain account is the account of the management node in the second blockchain, and the second blockchain is the blockchain to which the user's original regional information belongs; the first blockchain and the second blockchain are different from each other;

[0009] Send the above first bill information to the second business node in the above second blockchain through the above second blockchain account, so that the above second business node generates second bill information according to the above first bill information;

[0010] Receive the above second bill information returned by the above second business node through the above second blockchain account, and chain the above second bill information to the above second blockchain.

[0011] On the one hand, an embodiment of the present application provides another blockchain-based data processing method, including:

[0012] The second business node receives the first bill information sent by the management node; the invoicing information to which the above first bill information belongs is sent by the first business node to the above management node through the first blockchain account of the above management node, and the above invoicing information also carries the user's original regional information of the user to which the above first bill information belongs; the node regional information of the above first business node is different from the above user's original regional information; the above first blockchain account is the account of the above management node in the first blockchain, and the above first blockchain is the blockchain to which the above node regional information belongs; the above first business node is the business node in the above first blockchain;

[0013] Generate second bill information according to the above first bill information, and return the above second bill information to the above management node through the second blockchain account of the above management node, so that the above management node chains the above second bill information to the second blockchain to which the above second blockchain account belongs; the above second blockchain account is the account of the above management node in the second blockchain; the above second blockchain is the blockchain to which the above user's original regional information belongs; the above first blockchain is different from the above second blockchain; the above second business node is the business node in the above second blockchain.

[0014] On the one hand, an embodiment of the present application provides a blockchain-based data processing device, including:

[0015] An invoicing information receiving module, configured to receive, by the management node through the first blockchain account, invoicing information sent by the first business node; the above invoicing information carries the first bill information and the user's original regional information of the user to which the above first bill information belongs; the node regional information of the above first business node is different from the above user's original regional information; the above first blockchain account is the account of the above management node in the first blockchain, and the above first blockchain is the blockchain to which the above node regional information belongs;

[0016] An account query module, configured to query a second blockchain account corresponding to the above-mentioned original user geographical information according to the above-mentioned first blockchain account and the above-mentioned invoicing information; the second blockchain account is the account of the management node in the second blockchain, and the second blockchain is the blockchain to which the above-mentioned original user geographical information belongs; the first blockchain is different from the second blockchain;

[0017] A bill information sending module, configured to send the above-mentioned first bill information to a second service node in the above-mentioned second blockchain through the above-mentioned second blockchain account, so that the second service node generates second bill information according to the above-mentioned first bill information;

[0018] A bill information blockchain module, configured to receive the above-mentioned second bill information returned by the above-mentioned second service node through the above-mentioned second blockchain account, and chain the above-mentioned second bill information to the above-mentioned second blockchain.

[0019] Wherein, it further includes:

[0020] A geographical information acquisition module, configured to acquire the node geographical information to which the above-mentioned first service node belongs, and the jurisdiction geographical scope of the above-mentioned first blockchain;

[0021] An invoicing information blockchain module, configured to chain the above-mentioned invoicing information to the above-mentioned first blockchain if the above-mentioned node geographical information belongs to the jurisdiction geographical scope of the above-mentioned first blockchain.

[0022] Wherein, the above-mentioned account query module includes:

[0023] A selection task generation unit, configured to generate an account selection task according to the above-mentioned first blockchain account and the above-mentioned original user geographical information;

[0024] An account determination unit, configured to trigger a smart contract in the blockchain to which the above-mentioned management node belongs according to the above-mentioned account selection task, and determine a second blockchain account that matches the above-mentioned original user geographical information through the above-mentioned smart contract.

[0025] Wherein, the above-mentioned account determination unit includes:

[0026] A block consensus subunit, configured to encapsulate the above-mentioned account selection task, the above-mentioned original user geographical information, and a contract call function into a block, and perform consensus on the above-mentioned block;

[0027] A mapping table acquisition subunit, configured to call the above-mentioned smart contract according to the contract call function in the above-mentioned block during the consensus period, and acquire an account mapping table in the blockchain to which the above-mentioned original user geographical information belongs from the above-mentioned smart contract according to the above-mentioned account selection task; each account in the above-mentioned account mapping table has a one-to-one mapping relationship with the blockchain jurisdiction geographical scope;

[0028] An account acquisition subunit, configured to acquire the account mapped by the jurisdiction area scope of the first blockchain from the above-mentioned account mapping table;

[0029] An account determination subunit, configured to, when the above-mentioned block consensus is passed, determine the account mapped by the jurisdiction area scope of the first blockchain as the second blockchain account.

[0030] Wherein, it further includes:

[0031] A registration request sending module, configured to send a first account registration request to a first account opening service node in the first blockchain; the above-mentioned first account registration request carries the management area information of the above-mentioned management node;

[0032] An account information receiving module, configured to receive the first account information returned by the above-mentioned first account opening service node as the first blockchain account; the above-mentioned first account information is generated by the above-mentioned first account opening service node according to the account registration standard format of the above-mentioned first blockchain, the above-mentioned management node, and the above-mentioned management area information;

[0033] An account on-chain module, configured to chain the above-mentioned first blockchain account to the above-mentioned first blockchain;

[0034] The above-mentioned registration request sending module is further configured to send a second account registration request to a second account opening service node in the second blockchain; the above-mentioned second account registration request carries the above-mentioned management area information of the above-mentioned management node;

[0035] The above-mentioned account information receiving module is further configured to receive the second account information returned by the above-mentioned second account opening service node as the second blockchain account; the above-mentioned second account information is generated by the above-mentioned second account opening service node according to the account registration standard format of the above-mentioned second blockchain, the above-mentioned management node, and the above-mentioned management area information; the account registration standard format of the above-mentioned first blockchain is different from that of the above-mentioned second blockchain;

[0036] The above-mentioned account on-chain module is further configured to chain the above-mentioned second blockchain account to the above-mentioned first blockchain.

[0037] On the one hand, the present application provides a computer device, including: a processor, a memory, and a network interface;

[0038] The above-mentioned processor is connected to the memory and the network interface. Among them, the network interface is used to provide a data communication function, the above-mentioned memory is used to store a computer program, and the above-mentioned processor is used to call the above-mentioned computer program to execute the method in the above-mentioned aspect in the embodiment of the present application.

[0039] On the one hand, the present application provides a computer-readable storage medium. The computer-readable storage medium stores a computer program. The computer program includes program instructions. When the program instructions are executed by a processor, the method in the above-mentioned aspect in the embodiments of the present application is executed.

[0040] On the one hand, an embodiment of the present application provides another blockchain-based data processing device, including:

[0041] A bill information receiving module, configured to receive, by a second service node, first bill information sent by a management node; the invoicing information to which the first bill information belongs is sent by a first service node to the management node through the first blockchain account of the management node, and the invoicing information further carries the original regional information of the user to which the first bill information belongs; the node regional information to which the first service node belongs is different from the original regional information of the user; the first blockchain account is the account of the management node in the first blockchain, and the first blockchain is the blockchain to which the node regional information belongs; the first service node is a service node in the first blockchain;

[0042] A bill information generating module, configured to generate second bill information according to the first bill information, and return the second bill information to the management node through the second blockchain account of the management node, so that the management node uploads the second bill information to the second blockchain to which the second blockchain account belongs; the second blockchain account is the account of the management node in the second blockchain; the second blockchain is the blockchain to which the original regional information of the user belongs; the first blockchain is different from the second blockchain; the second service node is a service node in the second blockchain.

[0043] Among them, the bill information generating module includes:

[0044] A bill content information obtaining unit, configured to obtain the bill initiator information, business content information in the first bill information, and user information of the user to which the first bill information belongs;

[0045] A regional information determining unit, configured to determine the initiator regional information to which the bill initiator belongs according to the bill initiator information;

[0046] A standard format obtaining unit, configured to obtain the bill generation standard format corresponding to the second blockchain;

[0047] A bill information generating unit, configured to generate the second bill information according to the bill initiator information, business content information, the user information, the initiator regional information, and the bill generation standard format.

[0048] On the one hand, the present application provides a computer device, including: a processor, a memory, and a network interface;

[0049] The above-mentioned processor is connected to the memory and the network interface. Among them, the network interface is used to provide data communication functions, the above-mentioned memory is used to store computer programs, and the above-mentioned processor is used to call the above-mentioned computer programs to execute the method in the above-mentioned aspect in the embodiments of the present application.

[0050] On the one hand, the present application provides a computer-readable storage medium. The above-mentioned computer-readable storage medium stores a computer program. The above-mentioned computer program includes program instructions. When the above-mentioned program instructions are executed by a processor, the method in the above-mentioned aspect in the embodiments of the present application is executed.

[0051] In the embodiments of the present application, the management node has blockchain accounts on both the first blockchain and the second blockchain. The two blockchains are different from each other and belong to different geographical information. The management node can receive the first bill information from the first blockchain through the first blockchain account, and then send the first bill information to the second blockchain through the second blockchain account, so that the nodes in the second blockchain generate the second bill information. It can be seen that the management node can realize cross-regional invoicing between the region to which the first blockchain belongs and the region to which the second blockchain belongs through the first blockchain account and the second blockchain account, and further support the generation of off-site bills in the blockchain. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0053] Figure 1 It is a schematic diagram of a system architecture provided by the embodiments of the present application;

[0054] Figure 2 It is a schematic flowchart of a data processing method based on a blockchain provided by the embodiments of the present application;

[0055] Figure 3 It is a schematic diagram of a scenario for generating the second bill information provided by the embodiments of the present application;

[0056] Figure 4 It is a schematic diagram of a scenario for uploading the invoicing information and the second bill information to the blockchain provided by the embodiments of the present application;

[0057] Figure 5It is a schematic flowchart of a process for a management node to register a blockchain account provided by an embodiment of the present application;

[0058] Figure 6 It is a schematic diagram of a scenario for a management node to register a blockchain account provided by an embodiment of the present application;

[0059] Figure 7 It is a timing flowchart of a data processing method based on blockchain provided by an embodiment of the present application;

[0060] Figure 8 It is a schematic structural diagram of a data processing device based on blockchain provided by an embodiment of the present application;

[0061] Figure 9 It is a schematic diagram of a computer device provided by an embodiment of the present application;

[0062] Figure 10 It is a schematic structural diagram of a data processing device based on blockchain provided by an embodiment of the present application;

[0063] Figure 11 It is a schematic diagram of a computer device provided by an embodiment of the present application;

[0064] Figure 12 It is a schematic structural diagram of a data processing system based on blockchain provided by an embodiment of the present application. Detailed implementation manners

[0065] Next, the technical solutions in the embodiments of the present application will be clearly and completely described in conjunction with the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the protection scope of the present application.

[0066] Please refer to Figure 1, is a schematic diagram of a system architecture provided by an embodiment of the present application. Blockchain is essentially a decentralized database, and each node in this database stores an identical blockchain. The blockchain network classifies nodes into core nodes, data nodes, and light nodes. Among them, the core nodes are responsible for the consensus of the entire blockchain network. That is to say, the core nodes are the consensus nodes in the blockchain network. For the process of transaction data in the blockchain network being written into the ledger, it can be as follows: First, the client sends to the data node or light node connected to the blockchain network. Subsequently, the transaction data is transmitted in the blockchain network (that is, the nodes transmit in the way of a relay baton) until the consensus node receives the transaction data. The consensus node then packs the transaction data into a block, performs consensus execution, and writes the transaction data into the ledger after the consensus is completed, and then returns to the client. Due to the immutability of blockchain technology, once the transaction data is written into the ledger, it cannot be changed anymore, which can ensure the security and authenticity of the transaction data. When subsequent users obtain transaction data through the blockchain, they can get real and unmodified transaction data. As Figure 1 shown, the system architecture of the present application may include a management node 1000, a first blockchain 1001,..., and a second blockchain 1002. Among them, both the first blockchain 1001 and the second blockchain 1002 may include at least two nodes. As Figure 1 shown, the first blockchain 1001 may specifically include nodes 100a, 100b,..., 100n, and the second blockchain 1002 may specifically include nodes 100c, 100d,..., 100m. The nodes in the first blockchain 1001 and the second blockchain 1002 can both send transaction data to the management node 1000, and the management node 1000 can also send transaction data to the nodes in the first blockchain 1001 and the second blockchain 1002. It can be seen that the first blockchain 1001 and the second blockchain 1002 are different blockchains and are not network-connected, but data interaction is achieved through the management node 1000. For example, if a node in the first blockchain 1001 needs to send transaction data to a node in the second blockchain, it can first send it to the management node 1000, and the management node 1000 then sends the transaction data to the nodes in the second blockchain 1002 so that the nodes in the second blockchain 1002 can receive the transaction data and make corresponding processing (this processing can be, for example, on-chain, generating data information corresponding to the transaction data, etc.).

[0067] As Figure 1As shown, nodes 100a, 100b, …, 100n can be respectively network-connected to the management node 1000 so that the first blockchain 1001 can interact with the management node 1000 for data; nodes 100a, 100b, …, 100n are interconnected so that nodes in the first blockchain 1001 can interact with each other for data; nodes 100c, 100d, …, 100m can be respectively network-connected to the management node 1000 so that the second blockchain 1002 can interact with the management node 1000 for data; nodes 100c, 100d, …, 100m are interconnected so that nodes in the second blockchain 1002 can interact with each other for data.

[0068] Taking the example that node 100a in the first blockchain 1001 needs to send transaction data (such as bill information) to node 100c in the second blockchain 1002, the method flow of this application can be specifically as follows: Node 100a (such as the first business node) can send invoicing information to the management node 1000 through the first blockchain account of the management node 1000 in the first blockchain 1001; where the invoicing information carries the first bill information and the original regional information of the user to whom the first bill information belongs, the regional information of the node to which node 100a belongs is different from the original regional information of the user, the first blockchain account refers to the account of the management node 1000 in the first blockchain 1001, and the first blockchain is the blockchain to which the regional information of the node belongs; according to the first blockchain account and the invoicing information, the management node 1000 can query the second blockchain account corresponding to the original regional information of the user; where the second blockchain account is the account of the management node 1000 in the second blockchain 1002, the second blockchain 1002 is the blockchain to which the original regional information of the user belongs, and the first blockchain 1001 is different from the second blockchain 1002; through the second blockchain account, the management node 1000 can send the first bill information to node 100c (such as the second business node) in the second blockchain 1002 so that node 100c can generate second bill information based on the first bill information; the management node 1000 can receive the second bill information returned by node 100c through the second blockchain account and chain the second bill information to the above-mentioned second blockchain 1002.

[0069] It can be understood that if the geographical information to which the first blockchain 1001 belongs is Province A and the geographical information to which the second blockchain 1002 belongs is Province B, then the node geographical information to which the node 100a belongs is Province A, and the management node 1000 can uniformly manage the first blockchain 1001 and the second blockchain 1002. The original user geographical information to which User B belongs is Province B. That is to say, User B is from Province B. User B goes to Hospital A in Province A to see a doctor, and Hospital A needs to issue a medical bill to User B. Since Hospital A and User B are in different regions, it is unable to issue a medical bill. Then Hospital A can issue a cross-region bill through the blockchain. Hospital A can send the bill-issuing information to the management node 1000 through the node 100a in the first blockchain 1001 in Province A (here, the node 100a sends the bill-issuing information to the management node 1000 through the first blockchain account of the management node 1000 in the first blockchain 1001). The bill-issuing information includes the first medical bill issued by Hospital A to User B (which can include that the bill initiator is Hospital A, the bill recipient is User B, and the medical expenses, etc.) and the original user geographical information of User B (such as Province B); after receiving the bill-issuing information, the management node 1000 can, through the first blockchain account and the bill-issuing information, query the second blockchain account corresponding to the geographical information of Province B of User B. This second blockchain account is the account of the management node 1000 in the second blockchain 1002 in Province B; through this second blockchain account, the management node 1000 can send the first medical bill to the node 100c in the second blockchain 1002 in Province B. After receiving the first medical bill, the node 100c can generate a second medical bill based on the first medical bill and return the second medical bill to the management node 1000. The management node 1000 can chain the second medical bill to the second blockchain 1002 in Province B. The node 100c can send the second medical bill to User B, and User B can perform subsequent processing in Province B based on the second medical bill (such as reimbursing expenses by virtue of the second medical bill).

[0070] It can be understood that the method provided in the embodiments of the present invention can be executed by a computer device, and the computer device includes but is not limited to a terminal or a server. The nodes in the embodiments of the present invention can be computer devices.

[0071] Please refer to Figure 2 , which is a schematic flowchart of a data processing method based on a blockchain provided by an embodiment of the present application. As Figure 2 shown, the process of the method can include:

[0072] Step S101, the management node receives the invoicing information sent by the first service node through the first blockchain account; the invoicing information carries the first bill information and the original user geographical information of the user to whom the first bill information belongs; the node geographical information to which the first service node belongs is different from the original user geographical information; the first blockchain account is the account of the management node in the first blockchain, and the first blockchain is the blockchain to which the node geographical information belongs.

[0073] In this application, the node geographical information can be used to represent the responsible area of a service node (such as the first service node), and this area can be a provincial or municipal area (such as Guangdong Province, Chongqing City), a district or county area (such as Nanan District of Chongqing City, Shenzhen City of Guangdong Province, Youxi Town of Jiangjin District of Chongqing City, etc.). One node geographical information corresponds to one blockchain, and there is one or at least two nodes on one blockchain. Different node geographical information corresponds to different blockchains. The management node can be a node used to uniformly manage these different blockchains. The management node can act as an intermediate transmitter and can interact with these blockchains respectively through the blockchain accounts in these blockchains (the management node can receive messages sent by the blockchain and can also send messages to the blockchain). Thus, these blockchains in different regions can achieve data interaction through the management node.

[0074] The user to whom the first bill information in this application belongs may refer to the payee of the first bill information, and the user's original geographical information may be the residential geographical information to which the user belongs (such as the place of household registration). If the user handles relevant affairs in other regions outside the original geographical scope (such as the node geographical information of the first service node), and relevant institutions in other regions need to issue bills, the relevant institutions in other regions can send the invoicing information to the management node through the blockchain corresponding to the local region (such as the first blockchain). The invoicing information here needs to include the first bill information issued by the relevant institution to the user and the user's original geographical information; the invoicing information is sent by the node (such as the first service node) in the local blockchain to the management node through the blockchain account of the management node in the local blockchain. Among them, the management node has at least two blockchain accounts in each blockchain (such as the first blockchain), and each blockchain account corresponds to another node geographical information different from the node geographical information of this blockchain. For example, the blockchains managed by the management node include Blockchain 1, Blockchain 2, and Blockchain 3. Among them, the node geographical information corresponding to Blockchain 1 is A, the node geographical information corresponding to Blockchain 2 is B, and the node geographical information corresponding to Blockchain 3 is C. Then the accounts of the management node in Blockchain 1 can include Account 1 and Account 2, where the other node geographical information corresponding to Account 1 is B, and the other node geographical information corresponding to Account 2 is C. The significance of Account 1 corresponding to the node geographical information B is that if the node in Blockchain 1 hopes to send information to the node in Blockchain 2 through the management node, the node in Blockchain 1 can select Account 1 from the accounts of the management node in Blockchain 1 (including Account 1 and Account 2) and send the information to the management node through Account 1. In this way, the management node can know through Account 1 that the information is expected to be sent to Blockchain 2 corresponding to the node geographical information B, and the management node can send the information to the node in Blockchain 2. That is to say, the blockchain accounts of the management node in the blockchain all have geographical directivity, and one blockchain account points to one geographical information. Therefore, the first blockchain account here can refer to the account of the management node in the first blockchain with the geographical direction being the user's original geographical information.

[0075] It can be understood that there are a total of 4 provinces (4 node geographical information), including Province A, Province B, Province C, and Province D. Province A has Blockchain A, Province B has Blockchain B, Province C has Blockchain C, and Province D has Blockchain D. The management node has Account 12, Account 13, and Account 14 in Blockchain A. Among them, Account 12 corresponds to Blockchain B, Account 13 corresponds to Blockchain C, and Account 14 corresponds to Blockchain D; User B in Province B goes to the hospital in Province A to see a doctor, and the hospital needs to issue an invoice to User B. Since the hospital belongs to Province A and User B belongs to Province B, at this time, the hospital issuing the invoice is an inter-provincial invoice issuance. Then the hospital can send the invoice information to the management node through the node in Blockchain A. Because Account 12 of the management node in Blockchain A corresponds to Province B, the node in Blockchain A can send the invoice information to the management node through Account 12.

[0076] Optionally, it can be understood that in order to record the relevant institutions in the geographical information of the first business node and issue invoices for users in other regions, the invoice information can be uploaded to the first blockchain, that is, the invoice information is saved to the blockchain to which the first business node belongs. The specific process of uploading to the chain can be that the management node obtains the node geographical information to which the first business node belongs and the jurisdiction scope of the first blockchain. If the node geographical information belongs to the jurisdiction scope of the first blockchain, the management node can obtain the public key of the first business node, the first bill information, and the digital signature of the first bill information. Among them, the digital signature is carried by the first bill information and is obtained by signing the first bill information based on the private key of the first business node; the management node can verify the digital signature of the first bill information based on the public key of the first business node. If the verification passes, it can prove that the digital signature is a legal signature, and then the management node can generate a block according to the first bill information and the original geographical information of the user. After the block is consensus by the consensus node, the block can be added to the first blockchain.

[0077] Step S102, query the second blockchain account corresponding to the original geographical information of the user according to the first blockchain account and the invoice information; the second blockchain account is the account of the management node in the second blockchain, and the second blockchain is the blockchain to which the original geographical information of the user belongs; the first blockchain is different from the second blockchain.

[0078] In this application, the user's original geographical information here is within the jurisdiction scope of the second blockchain. Based on the above first blockchain account and the user's original geographical information, the management node can generate an account selection task. According to this account selection task, it can trigger the smart contract in the blockchain to which the management node belongs. Through this smart contract, a second blockchain account matching the user's original geographical information can be determined. The specific process of determining the second blockchain account through the smart contract can be as follows: encapsulate the account selection task here, the above user's original geographical information, and the contract call function into a block, and then conduct consensus on this block; during the consensus period, call the smart contract according to the contract call function in this block, and obtain the account mapping table in the blockchain to which the user's original geographical information belongs according to this account selection task; among them, each account in this account mapping table has a one-to-one mapping relationship with the blockchain jurisdiction scope; according to this account mapping table, the account mapped by the jurisdiction scope of the above first blockchain can be obtained from this account mapping table; when the consensus of this block is passed, the account mapped by the jurisdiction scope of the first blockchain can be determined as the second blockchain account. Among them, the mapping relationship between the accounts in this account mapping table and the blockchain jurisdiction scope is a one-to-one correspondence relationship, which can be understood as each account having a geographical reference. Here, the geographical reference can be the blockchain jurisdiction scope, that is, one account points to one blockchain jurisdiction scope (one account corresponds to one blockchain jurisdiction scope). For example, the first blockchain account 1 is the account of the management node in blockchain A. If the geographical information pointed to by the first blockchain account 1 is the user's original geographical information, then based on this user's original geographical information, the management node can determine the corresponding blockchain B; because the management node also has at least two accounts in blockchain B (such as account 21 and account 23). Among them, the geographical reference of account 21 is the geographical information of blockchain A (here, the geographical information of the blockchain is also the blockchain jurisdiction scope), that is, account 21 has a one-to-one mapping relationship with the jurisdiction scope of blockchain A; the geographical reference of account 23 is the geographical information of blockchain C, that is, account 23 has a one-to-one mapping relationship with the jurisdiction scope of blockchain C. Then, through the geographical information (the geographical information of blockchain A) of the first blockchain account 1 (which is the account of the management node in blockchain A), account 21 can be selected as the second blockchain account from account 21 and account 23. Because the geographical reference of this account 21 is the geographical information of blockchain A, that is, among account 21 and account 23, the account mapped by the geographical information of blockchain A is account 21, then account 21 matches the user's original geographical information (because account 21 is the account of the management node in the blockchain to which the user's original geographical information belongs, that is, blockchain B), and the geographical reference of account 21 is the geographical information of blockchain A, corresponding to the first blockchain account 1.

[0079] Step S103: Send the above first bill information to the second business node in the above second blockchain through the above second blockchain account, so that the second business node generates second bill information according to the above first bill information.

[0080] In this application, the management node can send the above first bill information to the second business node in the second blockchain through the second blockchain account queried above. After receiving the first bill information, the second business node in the second blockchain can obtain the bill initiator information, business content information, and user information of the user to whom the first bill information belongs in the first bill information. Among them, the bill initiator can refer to the user or institution that issues the bill, the user to whom the first bill information belongs can refer to the payee (the user to whom the bill is issued), and the business content information can refer to the business content handled by the user at the bill initiator. For example, a user in Province B goes to Hospital A in Province A to see a doctor, and Hospital A issues a bill for the user in Province B. Then Hospital A is the bill initiator, the user in Province B is the user to whom the bill belongs, and the business content information may include the drugs prescribed by the hospital for the user in Province B and the drug costs. According to the bill initiator information, the second business node can determine the initiator regional information to which the bill initiator belongs. The second business node can obtain the bill generation standard format corresponding to the second blockchain to which the second business node belongs. According to the bill initiator information, business content information, the user information, the initiator regional information, and the bill generation standard format, the second business node can generate second bill information and return the second bill information to the management node. The second business node can send the second bill information to the user to whom the first bill information belongs, so that the user can go to the original user regional information (such as the user's household registration location) and perform subsequent business processing (such as reimbursing expenses with the bill) according to the second bill information.

[0081] Optionally, it can be understood that the management node receives the first bill information and sends the first bill information to the second business node, which are all spontaneously completed by the management node through its own accounts in the two blockchains. To avoid the first bill information from being re-forwarded and ensure the security and uniqueness of the first bill information, after sending the first bill information to the second business node, the management node can lock the first bill information (it cannot be forwarded again after being locked).

[0082] Step S104: Receive the above second bill information returned by the second business node through the above second blockchain account, and chain the above second bill information to the above second blockchain.

[0083] In this application, after receiving the second bill information returned by the second service node, the management node can generate a block based on the second bill information. After the block passes consensus, the block is added to the second blockchain. After the second bill information is uploaded to the blockchain, the second bill information cannot be modified anymore, which can make it have extremely high security and authenticity.

[0084] In the embodiment of this application, the management node has blockchain accounts on both the first blockchain and the second blockchain. The two blockchains are different from each other and belong to different geographical information. The management node can receive the first bill information from the first blockchain through the first blockchain account, and then send the first bill information to the second blockchain through the second blockchain account, so that the nodes in the second blockchain generate the second bill information. It can be seen that the management node can use the first blockchain account and the second blockchain account to achieve cross-regional invoicing between the region to which the first blockchain belongs and the region to which the second blockchain belongs, and thus support the generation of off-site bills in the blockchain.

[0085] Further, for easy understanding, please refer to Figure 3 , which is a schematic diagram of a scenario for generating the second bill information provided by the embodiment of this application. As Figure 3 shown, the node geographical information of the first service node 301 is Province A, and the node geographical information of the second service node 302 is Province B. The blockchain to which the first service node 301 belongs is the first blockchain, and the blockchain to which the second service node 302 belongs is the second blockchain. The blockchain accounts of the management node 3000 in the first blockchain include Account 1, Account 2, and Account 3. Among them, the geographical orientation of Account 1 is Province B, the geographical orientation of Account 2 is Province C, and the geographical orientation of Account 3 is Province D. After user B in Province B sees a doctor at Hospital A in Province A, Hospital A issues a receipt 300a (the first bill information) for user B. As Figure 3 shown, the receipt 300a includes the bill initiator (Hospital A in Province A), the bill recipient (user B), and the service content information (including traditional Chinese medicine, western medicine, examination fees, injection fees, etc.). Since Province A where Hospital A is located and Province B where user B is located are different provinces and cities, the receipt 300a is not valid. Then, Hospital A can send the receipt 300a to the management node through the first service node 301 in the blockchain of Province A (the first blockchain), so that the management node 3000 sends the receipt 300a to the blockchain nodes in Province B, and the blockchain nodes in Province B perform bill invoicing. As Figure 3As shown in the figure, among the accounts of the management node 3000 in the first blockchain (including Account 1, Account 2, and Account 3), the geographical location pointed to by Account 1 is Province B because the original geographical information of User B is Province B (User B is a user belonging to Province B). Then, the first service node 301 can send the invoicing information to the management node 3000 through Account 1 of the management node 3000 in the first blockchain. The invoicing information includes the charge bill 300a and the original geographical information of User B. After receiving the charge bill 300a through this Account 1, the management node 3000 can determine the second blockchain account based on this Account 1 and the original geographical information of User B (Province B). As Figure 3 As shown in the figure, the accounts of the management node 3000 in the second blockchain include Account 3, Account 4, and Account 5. Among them, the geographical location pointed to by Account 3 is Province A, the geographical location pointed to by Account 4 is Province C, and the geographical location pointed to by Account 5 is Province D. Since this first blockchain account is Account 1 (pointing from Province A to Province B), the management node 3000 can determine that the bill initiator of the charge bill 300a belongs to Province A. Then, the management node 3000 can determine, among Account 3, Account 4, and Account 5, the account whose geographical location points to Province A, that is, Account 3 (that is to say, among Account 3, Account 4, and Account 5, Account 3 has a one-to-one mapping relationship with Province A), and use this Account 3 as the second blockchain account. The management node 3000 can send the charge bill 300a to the second service node 302 in the second blockchain through Account 3. After receiving the charge bill 300a, the second service node 302 can generate a second bill 300b with the standard format of the bill generation in Province B and return the second bill 300b to the management node 3000. The specific implementation method for the management node 3000 to query the second blockchain account can refer to the description in step S102 of the corresponding embodiment above Figure 2 and will not be elaborated here; the specific implementation method for the second service node 302 to generate the second bill 300b can refer to the description of generating the second bill information in step S103 of the corresponding embodiment above Figure 2 and will not be elaborated here either.

[0086] Furthermore, for the convenience of understanding, please also refer to Figure 4 , which is a schematic diagram of the scenario of uploading the invoicing information and the second bill information provided by the embodiment of the present application. As Figure 4As shown in the figure, the first service node 301 sends the invoicing information to the management node 3000. The invoicing information includes the above-mentioned payment receipt 300a and the original regional information of user B (Province B). The payment receipt 300a includes the digital signature obtained by the first service node 301 signing the payment receipt 300a based on the private key. After receiving the invoicing information, the management node can obtain the public key of the first service node 301, and verify the digital signature based on the public key. When the verification passes, it can be determined that the digital signature is a legal signature, and then a block 4001 can be generated according to the invoicing information and the block 4001 can be chained to the first blockchain 400, where the first blockchain 400 is the blockchain to which the first service node 301 belongs. After receiving the invoicing information sent by the first service node 301, the management node 3000 can obtain the payment receipt 300a carried in the invoicing information and send the payment receipt to the second service node 302. The second service node 302 can generate a second receipt 300b according to the payment receipt 300a, and generate a block 401 according to the second receipt 300b and chain the block 401 to the second blockchain 40, where the second blockchain 40 is the blockchain to which the second service node 302 belongs.

[0087] Further, please refer to Figure 5 , which is a schematic diagram of the process for a management node to register a blockchain account provided by an embodiment of the present application. As Figure 5 shown, the process may include:

[0088] Step S201, sending a first account registration request to the first account opening service node in the first blockchain; the first account registration request carries the management regional information of the management node.

[0089] In the present application, the first account opening service node is the node in the first blockchain used for account registration. If the management node hopes to have a blockchain account in the first blockchain, it can send a first account registration request to the first account opening service node. In the first account registration request, the management regional information of the management node needs to be carried. The management regional information refers to the regional information where the management node conducts management (such as Province A, Province B, City C, District D County), and the management regional information is used for the first account opening service node to add a regional pointer to the account when registering the account. For example, the jurisdiction scope of the first blockchain is Province A, and the management node sends an account registration request to the first account opening service node. The account registration request carries the management regional information of the management node as Province C, and account 1 is registered. The regional pointer of account 1 is Province C, that is, account 1: A -> C.

[0090] Step S202: Receive the first account information returned by the above-mentioned first account opening service node as the first blockchain account. The above-mentioned first account information is generated by the above-mentioned first account opening service node according to the account registration standard format of the above-mentioned first blockchain, the above-mentioned management node, and the above-mentioned management region information.

[0091] In this application, when the first account opening service node generates an account according to the management region information of the above-mentioned management node, it will generate the account according to the account registration standard format of the blockchain to which the first account opening service node belongs (the first blockchain), and this account registration standard format is a unique format of the first blockchain.

[0092] Step S203: Upload the above-mentioned first blockchain account to the above-mentioned first blockchain.

[0093] In this application, to enable the service nodes in the first blockchain to know the account of the management node in the first blockchain, the first blockchain account can be uploaded to the first blockchain.

[0094] Step S204: Send a second account registration request to the second account opening service node in the second blockchain. The above-mentioned second account registration request carries the above-mentioned management region information of the above-mentioned management node.

[0095] Step S205: Receive the second account information returned by the above-mentioned second account opening service node as the second blockchain account. The above-mentioned second account information is generated by the above-mentioned second account opening service node according to the account registration standard format of the above-mentioned second blockchain, the above-mentioned management node, and the above-mentioned management region information. The account registration standard format of the above-mentioned first blockchain is different from that of the above-mentioned second blockchain.

[0096] Step S206: Upload the above-mentioned second blockchain account to the above-mentioned first blockchain.

[0097] Among them, for the specific implementation manners of steps S204 - S206, reference can be made to the descriptions of the above-mentioned steps S201 - 203, and details will not be elaborated here.

[0098] In the embodiments of this application, the management node has blockchain accounts on both the first blockchain and the second blockchain. The two blockchains are different from each other and belong to different region information. The management node can receive the first bill information from the first blockchain through the first blockchain account, and then send the first bill information to the second blockchain through the second blockchain account, so that the nodes in the second blockchain can generate the second bill information. It can be seen that the management node can realize cross-region invoicing between the region to which the first blockchain belongs and the region to which the second blockchain belongs through the first blockchain account and the second blockchain account, and thus support the generation of off-site bills in the blockchain.

[0099] Further, for better understanding, please also refer to Figure 6 , which is a schematic diagram of a scenario for a management node to register a blockchain account provided by an embodiment of the present application. As Figure 6 shown, the management node 6000 sends an account registration request to the account opening service node 601. The jurisdiction area of the blockchain to which the account opening service node belongs is Province A, and the management area information of the management node carried in the account registration request is Province C. After receiving the account registration request, the account opening service node 601 can obtain the standard format for account registration of the blockchain in Province A. According to the standard format for account registration, the management node 6000, and the management area information of the management node 6000, the account opening service node 601 can generate Account C. As Figure 6 shown, the geographical location of Account C points to Province C. The account opening service node 601 can return Account C to the management node 6000. The management node 6000 can generate block 6001 based on Account C and upload block 6001 to the blockchain 600 in Province A. Account C is a blockchain account of the management node 6000 in the blockchain 600 of Province A.

[0100] Further, please refer to Figure 7 , which is a timing flowchart of a data processing method based on blockchain provided by an embodiment of the present application. As Figure 7 shown, the process may include:

[0101] Step S501, the first service node sends invoicing information to the management node.

[0102] Specifically, it can be understood that the invoicing information carries the first bill information and the original geographical location information of the user to whom the first bill information belongs.

[0103] Step S502, the management node queries the second blockchain account according to the above invoicing information.

[0104] Specifically, it can be understood that the management node queries the second blockchain account according to the above invoicing information, which may mean that the management node queries the second blockchain account according to the first bill information carried in the above invoicing information.

[0105] Step S503, the management node sends the first bill information to the second service node through the second blockchain account.

[0106] Specifically, it can be understood that the second blockchain account is the account of the management node in the second blockchain, and the geographical location of the second blockchain account points to the node geographical location information of the first service node. The purpose of the management node sending the first bill information to the second service node through the second blockchain account is to hope that the second service node generates the second bill information according to the first bill information.

[0107] Among them, for the specific implementation processes of steps S501 - S503, reference can be made to the descriptions of steps S101 - S104 in the corresponding embodiments above, and details will not be elaborated here. Figure 2

[0108] Step S504: The second service node generates second bill information based on the above first bill information.

[0109] Specifically, it can be understood that the second service node can generate second bill information based on the above first bill information, and this second bill information has the bill standard format corresponding to the node geographical information to which the second service node belongs.

[0110] Among them, for the specific implementation manner of the second service node generating second bill information based on the first bill information, reference can be made to the description in step S103 of the corresponding embodiment above, and details will not be elaborated here. Figure 2

[0111] Step S505: The second service node returns the second bill information.

[0112] Specifically, it can be understood that after generating the second bill information, the second service node can return this second bill information to the management node, and the management node can chain this second bill information to the second blockchain.

[0113] In the embodiments of the present application, the management node has blockchain accounts on both the first blockchain and the second blockchain. The two blockchains are different from each other and belong to different geographical information. The management node can receive the first bill information from the first blockchain through the first blockchain account, and then send this first bill information to the second blockchain through the second blockchain account, so that the nodes in the second blockchain generate second bill information. It can be seen that the management node can realize cross - regional invoicing between the region to which the first blockchain belongs and the region to which the second blockchain belongs through the first blockchain account and the second blockchain account, and further support the generation of off - site bills in the blockchain.

[0114] Furthermore, please refer to Figure 8 , which is a schematic structural diagram of a blockchain - based data processing device provided by the embodiments of the present application. The above blockchain - based data processing device can be a computer program (including program code) running in a computer device. For example, this blockchain - based data processing device is an application software; this device can be used to execute the corresponding steps in the method provided by the embodiments of the present application. This data processing device 1 can be applied to the management node, and this data processing device 1 can include: an invoicing information receiving module 11, an account query module 12, a bill information sending module 13, and a bill information chaining module 14.

[0115] The invoicing information receiving module 11 is used for the management node to receive the invoicing information sent by the first service node through the first blockchain account; the invoicing information carries the first bill information and the original regional information of the user to which the first bill information belongs; the node regional information of the first service node is different from the original regional information of the user; the first blockchain account is the account of the management node in the first blockchain, and the first blockchain is the blockchain to which the node regional information belongs;

[0116] The account query module 12 is used to query the second blockchain account corresponding to the original regional information of the user according to the first blockchain account and the invoicing information; the second blockchain account is the account of the management node in the second blockchain, and the second blockchain is the blockchain to which the original regional information of the user belongs; the first blockchain is different from the second blockchain;

[0117] The bill information sending module 13 is used to send the first bill information to the second service node in the second blockchain through the second blockchain account, so that the second service node generates the second bill information according to the first bill information;

[0118] The bill information blockchain module 14 is used to receive the second bill information returned by the second service node through the second blockchain account and chain the second bill information to the second blockchain.

[0119] Among them, the specific implementation manners of the invoicing information receiving module 11, the account query module 12, the bill information sending module 13, and the bill information blockchain module 14 can refer to the descriptions of steps S101 - S104 in the corresponding embodiments above, and will not be elaborated here. Figure 2

[0120] Figure 8 Please refer to , the data processing device 1 may include an invoicing information receiving module 11, an account query module 12, a bill information sending module 13, and a bill information blockchain module 14, and may also include: a regional information acquisition module 15 and an invoicing information blockchain module 16.

[0121] The regional information acquisition module 15 is used to acquire the node regional information of the first service node and the jurisdiction scope of the first blockchain;

[0122] The invoicing information blockchain module 16 is used to chain the invoicing information to the first blockchain if the node regional information belongs to the jurisdiction scope of the first blockchain.

[0123] ​Among them, the specific implementation manners of the geographical information acquisition module 15 and the invoicing information on-chain module 16 can be referred to the description of step S101 in the corresponding embodiment above, which will not be elaborated here. Figure 2 The description of step S101 in the corresponding embodiment above, which will not be elaborated here.

[0124] Please refer to Figure 8 The above-mentioned account query module 12 may include: a selection task generation unit 121 and an account determination unit 122.

[0125] The selection task generation unit 121 is configured to generate an account selection task according to the above-mentioned first blockchain account and the above-mentioned original user geographical information.

[0126] The account determination unit 122 is configured to trigger a smart contract in the blockchain to which the above-mentioned management node belongs according to the above-mentioned account selection task, and determine a second blockchain account that matches the above-mentioned original user geographical information through the above-mentioned smart contract.

[0127] Among them, the specific implementation manners of the selection task generation unit 121 and the account determination unit 122 can be referred to the description of step S102 in the corresponding embodiment above, which will not be elaborated here. Figure 2 The description of step S102 in the corresponding embodiment above, which will not be elaborated here.

[0128] Please refer to Figure 8 The above-mentioned account determination unit 122 may include: a block consensus subunit 1221, a mapping table acquisition subunit 1222, an account acquisition subunit 1223, and an account determination subunit 1224.

[0129] The block consensus subunit 1221 is configured to encapsulate the above-mentioned account selection task, the above-mentioned original user geographical information, and a contract call function into a block, and perform consensus on the above-mentioned block.

[0130] The mapping table acquisition subunit 1222 is configured to call the above-mentioned smart contract according to the contract call function in the above-mentioned block during the consensus period, and obtain an account mapping table in the blockchain to which the above-mentioned original user geographical information belongs from the above-mentioned smart contract; each account in the above-mentioned account mapping table has a one-to-one mapping relationship with the blockchain jurisdiction scope.

[0131] The account acquisition subunit 1223 is configured to obtain the accounts mapped by the jurisdiction scope of the above-mentioned first blockchain from the above-mentioned account mapping table.

[0132] The account determination subunit 1224 is configured to, when the above-mentioned block consensus passes, determine the accounts mapped by the jurisdiction scope of the above-mentioned first blockchain as the above-mentioned second blockchain accounts.

[0133] Among them, for the specific implementation manners of the block consensus subunit 1221, the mapping table acquisition subunit 1222, the account acquisition subunit 1223, and the account determination subunit 1224, reference can be made to the description of step S102 in the corresponding embodiment above, which will not be elaborated here. Figure 2 The description of step S102 in the corresponding embodiment will not be elaborated here.

[0134] Please refer to Figure 8 , the data processing device 1 may include an invoicing information receiving module 11, an account query module 12, a bill information sending module 13, a bill information blockchain module 14, a geographical information acquisition module 15, and an invoicing information blockchain module 16, and may further include: a registration request sending module 17, an account information receiving module 18, and an account blockchain module 19.

[0135] The registration request sending module 17 is configured to send a first account registration request to a first account opening service node in the first blockchain; the first account registration request carries the management geographical information of the management node;

[0136] The account information receiving module 18 is configured to receive the first account information returned by the first account opening service node as the first blockchain account; the first account information is generated by the first account opening service node according to the account registration standard format of the first blockchain, the management node, and the management geographical information;

[0137] The account blockchain module 19 is configured to blockchain the first blockchain account into the first blockchain;

[0138] The registration request sending module 17 is further configured to send a second account registration request to a second account opening service node in the second blockchain; the second account registration request carries the management geographical information of the management node;

[0139] The account information receiving module 18 is further configured to receive the second account information returned by the second account opening service node as the second blockchain account; the second account information is generated by the second account opening service node according to the account registration standard format of the second blockchain, the management node, and the management geographical information; the account registration standard format of the first blockchain is different from that of the second blockchain;

[0140] The account blockchain module 19 is further configured to blockchain the second blockchain account into the first blockchain.

[0141] Among them, for the specific implementation manners of the registration request sending module 17, the account information receiving module 18, and the account blockchain module 19, reference can be made to the description of steps S201 - S206 in the corresponding embodiment above, which will not be elaborated here. Figure 5 The description of steps S201 - S206 in the corresponding embodiment will not be elaborated here.

[0142] The management node in the embodiment of the present application has blockchain accounts on both the first blockchain and the second blockchain. The two blockchains are different from each other and belong to different regional information. The management node can receive the first bill information from the first blockchain through the first blockchain account, and then send the first bill information to the second blockchain through the second blockchain account, so that the node in the second blockchain generates the second bill information. It can be seen that the management node can use the first blockchain account and the second blockchain account to realize cross-regional invoicing between the region to which the first blockchain belongs and the region to which the second blockchain belongs, and thus can support the generation of off-site bills in the blockchain.

[0143] For further information, see Figure 9 , is a schematic diagram of a computer device provided in an embodiment of the present application. Figure 9 As shown, the computer device 9000 may be Figure 3 Corresponding to the management node in the embodiment, the above-mentioned computer device 9000 may include: at least one processor 9001, such as a CPU, at least one network interface 9004, a user interface 9003, a memory 9005, and at least one communication bus 9002. Among them, the communication bus 9002 is used to realize the connection and communication between these components. Among them, the user interface 9003 may include a display screen (Display), a keyboard (Keyboard), and the network interface 9004 may optionally include a standard wired interface, a wireless interface (such as a WI-FI interface). The memory 9005 may be a high-speed RAM memory, or it may be a non-volatile memory (non-volatile memory), such as at least one disk storage. The memory 9005 may optionally also be at least one storage device located away from the aforementioned processor 9001. Figure 9 As shown, the memory 9005 as a computer storage medium may include an operating system, a network communication module, a user interface module, and a device control application program.

[0144] exist Figure 9 In the computer device 9000 shown, the network interface 9004 is mainly used for network communication with the service server; the user interface 9003 is mainly used for providing an input interface for the user; and the processor 9001 can be used to call the device control application stored in the memory 9005 to achieve:

[0145] The management node receives the invoicing information sent by the first service node through the first blockchain account; the invoicing information carries the first bill information and the original geographical information of the user to which the first bill information belongs; the node geographical information of the first service node is different from the original geographical information of the user; the first blockchain account is the account of the management node in the first blockchain, and the first blockchain is the blockchain to which the node geographical information belongs;

[0146] According to the first blockchain account and the invoicing information, query the second blockchain account corresponding to the original geographical information of the user; the second blockchain account is the account of the management node in the second blockchain, and the second blockchain is the blockchain to which the original geographical information of the user belongs; the first blockchain and the second blockchain are different from each other;

[0147] Send the first bill information to the second service node in the second blockchain through the second blockchain account, so that the second service node generates second bill information according to the first bill information;

[0148] Receive the second bill information returned by the second service node through the second blockchain account, and upload the second bill information to the second blockchain.

[0149] It should be understood that the computer device 9000 described in the embodiments of the present application can execute the description of the data processing method based on the blockchain in the corresponding embodiments mentioned above, and can also execute the description of the data processing device 1 in the corresponding embodiments mentioned above, which will not be elaborated here. In addition, the description of the beneficial effects of using the same method will not be elaborated either. Figures 2 to 7 The description of the data processing method based on the blockchain in the corresponding embodiments mentioned above, and can also execute the description of the data processing device 1 in the corresponding embodiments mentioned above, which will not be elaborated here. In addition, the description of the beneficial effects of using the same method will not be elaborated either. Figure 8 In addition, it should be pointed out here that: the embodiments of the present application also provide a computer-readable storage medium, and the computer-readable storage medium stores a computer program executed by the computer device 9000 for data processing mentioned above, and the computer program includes program instructions. When the processor executes the program instructions, it can execute the description of the data processing method based on the blockchain in the corresponding embodiments mentioned above. Therefore, it will not be elaborated here. In addition, the description of the beneficial effects of using the same method will not be elaborated either. For the technical details not disclosed in the embodiments of the computer-readable storage medium involved in the present application, please refer to the description of the method embodiments of the present application.

[0150] In addition, it should be pointed out here that: the embodiments of the present application also provide a computer-readable storage medium, and the computer-readable storage medium stores a computer program executed by the computer device 9000 for data processing mentioned above, and the computer program includes program instructions. When the processor executes the program instructions, it can execute the description of the data processing method based on the blockchain in the corresponding embodiments mentioned above. Therefore, it will not be elaborated here. In addition, the description of the beneficial effects of using the same method will not be elaborated either. For the technical details not disclosed in the embodiments of the computer-readable storage medium involved in the present application, please refer to the description of the method embodiments of the present application. Figures 2 to 7 In addition, it should be pointed out here that: the embodiments of the present application also provide a computer-readable storage medium, and the computer-readable storage medium stores a computer program executed by the computer device 9000 for data processing mentioned above, and the computer program includes program instructions. When the processor executes the program instructions, it can execute the description of the data processing method based on the blockchain in the corresponding embodiments mentioned above. Therefore, it will not be elaborated here. In addition, the description of the beneficial effects of using the same method will not be elaborated either. For the technical details not disclosed in the embodiments of the computer-readable storage medium involved in the present application, please refer to the description of the method embodiments of the present application.

[0151] Please refer to Figure 10, which is a schematic structural diagram of a data processing device based on a blockchain provided by an embodiment of the present application. The above data processing device based on a blockchain may be a computer program (including program code) running in a computer device. For example, the data processing device based on a blockchain is an application software; the device may be used to execute corresponding steps in the method provided by an embodiment of the present application. The data processing device 2 may be applied to a second service node, and the data processing device 2 may include: a bill information receiving module 21 and a bill information generating module 22.

[0152] The bill information receiving module 21 is used for the second service node to receive the first bill information sent by the management node; the invoicing information to which the above first bill information belongs is sent by the first service node to the above management node through the first blockchain account of the above management node, and the above invoicing information also carries the user's original regional information of the user to which the above first bill information belongs; the node regional information to which the above first service node belongs is different from the above user's original regional information; the above first blockchain account is the account of the above management node in the first blockchain, and the above first blockchain is the blockchain to which the above node regional information belongs; the above first service node is a service node in the above first blockchain;

[0153] The bill information generating module 22 is used to generate second bill information according to the above first bill information, and return the above second bill information to the above management node through the second blockchain account of the above management node, so that the above management node uploads the above second bill information to the second blockchain to which the above second blockchain account belongs; the above second blockchain account is the account of the above management node in the second blockchain; the above second blockchain is the blockchain to which the above user's original regional information belongs; the above first blockchain is different from the above second blockchain; the above second service node is a service node in the above second blockchain.

[0154] Among them, for the specific implementation manners of the bill information receiving module 21 and the bill information generating module 22, reference may be made to the description of step S103 in the corresponding embodiment above, Figure 2 which will not be elaborated here.

[0155] Please refer to Figure 10 , the above bill information generating module 22 may include: a bill content information obtaining unit 221, a regional information determining unit 222, a standard format obtaining unit 223, and a bill information generating unit 224.

[0156] The bill content information obtaining unit 221 is used to obtain the bill initiator information, business content information in the above first bill information, and the user information of the user to which the above first bill information belongs;

[0157] A region information determination unit 222, configured to determine the region information of the initiator to which the initiator belongs according to the initiator information;

[0158] The standard format acquisition unit 223 is used to acquire the standard format of bill generation corresponding to the second blockchain;

[0159] The ticket information generating unit 224 is used to generate the second ticket information according to the ticket initiator information, the service content information, the user information, the initiator region information and the ticket generation standard format.

[0160] The specific implementation of the ticket content information acquisition unit 221, the regional information determination unit 222, the standard format acquisition unit 223 and the ticket information generation unit 224 can be found in the above Figure 2 The description of step S103 in the corresponding embodiment will not be repeated here.

[0161] The management node in the embodiment of the present application has blockchain accounts on both the first blockchain and the second blockchain. The two blockchains are different from each other and belong to different regional information. The management node can receive the first bill information from the first blockchain through the first blockchain account, and then send the first bill information to the second blockchain through the second blockchain account, so that the node in the second blockchain generates the second bill information. It can be seen that the management node can use the first blockchain account and the second blockchain account to realize cross-regional invoicing between the region to which the first blockchain belongs and the region to which the second blockchain belongs, and thus can support the generation of off-site bills in the blockchain.

[0162] For further information, see Figure 11 , is a schematic diagram of a computer device provided in an embodiment of the present application. Figure 11 As shown, the computer device 8000 may be Figure 3 Corresponding to the second business node in the embodiment, the above-mentioned computer device 8000 may include: at least one processor 8001, such as a CPU, at least one network interface 8004, a user interface 8003, a memory 8005, and at least one communication bus 8002. Among them, the communication bus 8002 is used to realize the connection and communication between these components. Among them, the user interface 8003 may include a display screen (Display), a keyboard (Keyboard), and the network interface 8004 may optionally include a standard wired interface, a wireless interface (such as a WI-FI interface). The memory 8005 may be a high-speed RAM memory, or it may be a non-volatile memory (non-volatile memory), such as at least one disk storage. The memory 8005 may optionally also be at least one storage device located away from the aforementioned processor 8001.Figure 11 As shown, in the memory 8005 which is a computer storage medium, an operating system, a network communication module, a user interface module, and a device control application program may be included.

[0163] In Figure 11 In the computer device 8000 shown, the network interface 8004 is mainly used for network communication with a user terminal; the user interface 8003 is mainly used to provide an input interface for the user; and the processor 8001 may be used to call the device control application program stored in the memory 8005 to implement:

[0164] The second service node receives the first bill information sent by the management node; the invoicing information to which the first bill information belongs is sent by the first service node to the management node through the first blockchain account of the management node, and the invoicing information also carries the original geographical information of the user to which the first bill information belongs; the node geographical information of the first service node is different from the original geographical information of the user; the first blockchain account is the account of the management node in the first blockchain, and the first blockchain is the blockchain to which the node geographical information belongs; the first service node is a service node in the first blockchain;

[0165] Generate second bill information according to the first bill information, and return the second bill information to the management node through the second blockchain account of the management node, so that the management node uploads the second bill information to the second blockchain to which the second blockchain account belongs; the second blockchain account is the account of the management node in the second blockchain; the second blockchain is the blockchain to which the original geographical information of the user belongs; the first blockchain and the second blockchain are different from each other; the second service node is a service node in the second blockchain.

[0166] It should be understood that the computer device 8000 described in the embodiments of the present application may execute the descriptions of the blockchain-based data processing method in the corresponding embodiments mentioned above Figure 2 and Figure 7 and may also execute the descriptions of the data processing device 2 in the corresponding embodiments mentioned above Figure 10 and details are not described herein again. In addition, the beneficial effects of using the same method are not described again.

[0167] In addition, it should be pointed out here that: the embodiments of the present application also provide a computer-readable storage medium, and the computer-readable storage medium stores a computer program executed by the computer device 8000 for data processing mentioned above, and the computer program includes program instructions. When the processor executes the program instructions, it can execute the above Figures 2 to 7The description of the above-mentioned blockchain-based data processing method in the corresponding embodiment will not be repeated here. In addition, the description of the beneficial effects of the same method will not be repeated. For technical details not disclosed in the computer-readable storage medium embodiment involved in this application, please refer to the description of the method embodiment of this application.

[0168] For further information, see Figure 12 , is a schematic diagram of a data processing system based on blockchain provided in an embodiment of the present application. The data processing system 3 may include a data processing device 1a and a data processing device 2a. The data processing device 1a may be the data processing device 2a. Figure 8 The data processing device 1 in the corresponding embodiment can be understood that the data processing device 1a can be integrated in the above Figure 3 The data processing device 2a may be the management node in the embodiment described above. Figure 10 The data processing device 2 in the corresponding embodiment can be understood that the data processing device 2a can be integrated in the above Figure 3 The second service node in the corresponding embodiment is not described in detail here. In addition, the description of the beneficial effects of the same method is not described in detail. For technical details not disclosed in the data processing system embodiment involved in this application, please refer to the description of the method embodiment of this application.

[0169] The terms "first", "second", etc. in the description, claims, and drawings of the embodiments of the present application are used to distinguish different objects, rather than to describe a specific order. In addition, the term "comprising" and any of their variations are intended to cover non-exclusive inclusions. For example, a process, method, device, product, or equipment that includes a series of steps or units is not limited to the listed steps or modules, but optionally includes steps or modules that are not listed, or optionally includes other step units inherent to these processes, methods, devices, products, or equipment.

[0170] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the composition and steps of each example have been generally described in terms of function in the above description. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0171] The method and related devices provided by the embodiments of the present application are described with reference to the method flowcharts and / or structural schematic diagrams provided by the embodiments of the present application. Specifically, each process and / or block in the method flowchart and / or structural schematic diagram, and the combination of processes and / or blocks in the flowchart and / or block diagram can be implemented by computer program instructions. These computer program instructions can be provided to the processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing devices to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing devices generate a device for implementing the functions specified in Figure 1 one process or multiple processes and / or structural schematic Figure 1 one block or multiple blocks. These computer program instructions can also be stored in a computer-readable memory that can direct a computer or other programmable data processing device to work in a specific manner, so that the instructions stored in the computer-readable memory generate a manufactured article including an instruction device, and the instruction device implements the functions specified in Figure 1 one process or multiple processes and / or structural schematic Figure 1 one block or multiple blocks. These computer program instructions can also be loaded onto a computer or other programmable data processing device, so that a series of operation steps are executed on the computer or other programmable device to generate a computer-implemented process. Thus, the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in Figure 1 one process or multiple processes and / or structural schematic one block or multiple blocks.

[0172] The above-disclosed are only the preferred embodiments of the present application. Of course, the scope of the rights of the present application cannot be limited thereby. Therefore, equivalent changes made according to the claims of the present application still fall within the scope covered by the present application.

Claims

1. A data processing method based on blockchain, characterized in that, Including: The management node receives the invoicing information sent by the first business node through the first blockchain account; The invoicing information carries the first bill information and the original geographical information of the user to whom the first bill information belongs; The node geographical information to which the first business node belongs is different from the original geographical information of the user; The first blockchain account is the account of the management node in the first blockchain, and the first blockchain is the blockchain to which the node geographical information belongs; Generate an account selection task according to the first blockchain account and the original geographical information of the user; Encapsulate the account selection task, the original geographical information of the user, and the contract call function into a block, and perform consensus on the block; During the consensus period, call the smart contract in the blockchain to which the management node belongs according to the contract call function in the block, and obtain the account mapping table in the second blockchain according to the account selection task; the second blockchain is the blockchain to which the original geographical information of the user belongs, the first blockchain is different from the second blockchain, and each account in the account mapping table has a one-to-one mapping relationship with the blockchain jurisdiction area; Obtain the account mapped by the jurisdiction area of the first blockchain from the account mapping table; when the block consensus passes, determine the account mapped by the jurisdiction area of the first blockchain as the second blockchain account; the second blockchain account is the account of the management node in the second blockchain; Send the first bill information to the second business node in the second blockchain through the second blockchain account, so that the second business node generates the second bill information according to the first bill information; Receive the second bill information returned by the second business node through the second blockchain account, and chain the second bill information to the second blockchain.

2. The method according to claim 1, characterized in that, Also including: Obtain the node geographical information to which the first business node belongs, and the jurisdiction area of the first blockchain; If the node geographical information belongs to the jurisdiction area of the first blockchain, chain the invoicing information to the first blockchain.

3. The method according to claim 1, characterized in that, Also including: Send a first account registration request to the first account opening business node in the first blockchain; The first account registration request carries the management geographical information of the management node; Receive the first account information returned by the first account opening business node as the first blockchain account; The first account information is generated by the first account opening business node according to the account registration standard format of the first blockchain, the management node, and the management geographical information; Chain the first blockchain account to the first blockchain; Send a second account registration request to the second account opening business node in the second blockchain; The second account registration request carries the management geographical information of the management node; Receive the second account information returned by the second account opening business node as the second blockchain account; The second account information is generated by the second account opening service node according to the account registration standard format of the second blockchain, the management node, and the management region information; the account registration standard format of the first blockchain is different from that of the second blockchain; Link the second blockchain account to the first blockchain.

4. A data processing method based on blockchain, characterized in that, It includes: The second service node receives the first bill information sent by the management node; The invoicing information to which the first bill information belongs is sent by the first service node to the management node through the first blockchain account of the management node, and the invoicing information also carries the user's original region information of the user to which the first bill information belongs; The node region information of the first service node is different from the user's original region information; the first blockchain account is the account of the management node in the first blockchain, and the first blockchain is the blockchain to which the node region information belongs; the first service node is a service node in the first blockchain; Generate second bill information according to the first bill information, and return the second bill information to the management node through the second blockchain account of the management node, so that the management node links the second bill information to the second blockchain to which the second blockchain account belongs; The second blockchain account is the account of the management node in the second blockchain; The second blockchain is the blockchain to which the user's original region information belongs; The first blockchain is different from the second blockchain; the second service node is a service node in the second blockchain.

5. The method according to claim 4, wherein The generating the second bill information according to the first bill information includes: Obtain the bill initiator information, service content information in the first bill information, and the user information of the user to which the first bill information belongs; Determine the initiator region information to which the bill initiator belongs according to the bill initiator information; Obtain the bill generation standard format corresponding to the second blockchain; Generate the second bill information according to the bill initiator information, service content information, the user information, the initiator region information, and the bill generation standard format.

6. A data processing device based on a blockchain, characterized in that, It includes: An invoicing information receiving module, configured to receive, by the management node through the first blockchain account, the invoicing information sent by the first service node; The invoicing information carries the first bill information and the user's original region information of the user to which the first bill information belongs; The node region information of the first service node is different from the user's original region information; The first blockchain account is the account of the management node in the first blockchain, and the first blockchain is the blockchain to which the node region information belongs; An account query module, configured to generate an account selection task according to the first blockchain account and the user's original region information; Encapsulate the account selection task, the user's original region information, and the contract call function into a block, and perform consensus on the block; During the consensus period, call the smart contract in the blockchain to which the management node belongs according to the contract call function in the block, and obtain the account mapping table in the second blockchain according to the account selection task; the second blockchain is the blockchain to which the original geographical information of the user belongs, the first blockchain is different from the second blockchain, and each account in the account mapping table has a one-to-one mapping relationship with the blockchain jurisdiction geographical scope; Obtain the accounts mapped by the jurisdiction geographical scope of the first blockchain from the account mapping table; when the block consensus is passed, determine the accounts mapped by the jurisdiction geographical scope of the first blockchain as the second blockchain accounts; the second blockchain accounts are the accounts of the management node in the second blockchain; A bill information sending module, configured to send the first bill information to the second service node in the second blockchain through the second blockchain account, so that the second service node generates second bill information according to the first bill information; A bill information chain-uploading module, configured to receive the second bill information returned by the second service node through the second blockchain account, and chain-upload the second bill information to the second blockchain.

7. A computer device, characterized in that, Including: A processor and a memory; The memory stores a computer program, and when the computer program is executed by the processor, the processor is caused to execute the steps of the method according to any one of claims 1 to 5.

8. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program, the computer program includes program instructions, and when the program instructions are executed by a processor, the method according to any one of claims 1 to 5 is executed.

Images