WO2021217928A1 - 基于区块链网络的资源请求交易验证方法、装置、电子设备及计算机可读存储介质 - Google Patents
基于区块链网络的资源请求交易验证方法、装置、电子设备及计算机可读存储介质 Download PDFInfo
- Publication number
- WO2021217928A1 WO2021217928A1 PCT/CN2020/105545 CN2020105545W WO2021217928A1 WO 2021217928 A1 WO2021217928 A1 WO 2021217928A1 CN 2020105545 W CN2020105545 W CN 2020105545W WO 2021217928 A1 WO2021217928 A1 WO 2021217928A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- transaction
- endorsement
- resource
- resource request
- parties
- Prior art date
Links
- 238000000034 method Methods 0.000 title claims abstract description 73
- 238000012795 verification Methods 0.000 title claims abstract description 54
- 238000012545 processing Methods 0.000 claims description 59
- 230000008569 process Effects 0.000 claims description 22
- 230000005856 abnormality Effects 0.000 claims description 6
- 230000002159 abnormal effect Effects 0.000 claims description 5
- 238000004088 simulation Methods 0.000 claims 3
- 230000000737 periodic effect Effects 0.000 claims 1
- 230000004044 response Effects 0.000 description 6
- 238000010586 diagram Methods 0.000 description 4
- 230000003287 optical effect Effects 0.000 description 4
- 238000011144 upstream manufacturing Methods 0.000 description 3
- 230000003044 adaptive effect Effects 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 230000006870 function Effects 0.000 description 2
- 230000000977 initiatory effect Effects 0.000 description 2
- 230000000644 propagated effect Effects 0.000 description 2
- 238000012546 transfer Methods 0.000 description 2
- 230000001133 acceleration Effects 0.000 description 1
- 238000003491 array Methods 0.000 description 1
- 230000003139 buffering effect Effects 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 238000013524 data verification Methods 0.000 description 1
- 230000003111 delayed effect Effects 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 230000007474 system interaction Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/06—Buying, selling or leasing transactions
- G06Q30/0601—Electronic shopping [e-shopping]
- G06Q30/0633—Lists, e.g. purchase orders, compilation or processing
- G06Q30/0635—Processing of requisition or of purchase orders
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
- G06Q20/401—Transaction verification
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/56—Provisioning of proxy services
- H04L67/568—Storing data temporarily at an intermediate stage, e.g. caching
Definitions
- This application relates to the field of blockchain technology, and in particular to a method, device, electronic equipment, and computer-readable storage medium for resource request transactions based on a blockchain network.
- resource transaction activities when the user selects a certain resource transaction product and fills in the transaction-related information required by all parties to the resource transaction, the resource requesting party saves the resource request order, and then real-time or batch (not real-time) ) Request orders for resource transfer from business related parties. For example, in some cases, business partners will transfer user loan orders to other partners (fund suppliers).
- the inventor realizes that in the process of resource request order circulation (resource transaction process), there may be system instability, system abnormality, or network instability on both sides, which may lead to loss of order information.
- resource transaction process it is necessary to manually check the abnormality in the order flow process, check the system log, and consume a lot of resources to perform the verification work, and it is inevitable that there will be omissions and errors, resulting in the resource request transaction not being stable enough and the reliability is low.
- one purpose of this application is to provide a resource request transaction method, device, electronic device, and computer-readable storage medium based on a blockchain network.
- a resource request transaction method based on a blockchain network.
- the blockchain network includes endorsement nodes, ledger nodes, ordering nodes of all parties to the resource transaction, and the resource transaction parties connected to each of the nodes.
- the service terminal the method is executed by the service terminal of the resource requester, the method includes: caching the identifier of the resource request order, the resource request order is the resource request order sent by the resource requester to the service related party through the service system, so The resource request order is sequentially transferred among the business related parties; the resource request order identifier is used to initiate an endorsement proposal to the endorsing node of each business related party on a regular basis to receive the endorsement returned by the endorsing node of the business related party according to the order flow Proposal results until the endorsement proposal results returned by the endorsement nodes of all business related parties are obtained; after the transaction-related data based on the resource request order is encapsulated as transaction book record information, it is submitted to the ordering node of the resource requester for sorting to obtain a simulated transaction
- a resource request transaction device based on a blockchain network.
- the blockchain network includes endorsement nodes, ledger nodes, ordering nodes of all parties to the resource transaction, and the resource transaction parties connected to each of the nodes.
- the service terminal the device is located in the service terminal of the resource requester, the device includes: a cache module for buffering the identifier of the resource request order, the resource request order is sent by the resource requester to the service related party through the service system
- the resource request order is transferred among the business related parties in turn;
- the proposal module is used to periodically use the resource request order identifier to initiate an endorsement proposal to the endorsement node of each business related party to receive the business relationship
- the endorsement node of the party returns the results of the endorsement proposal according to the order flow, until the endorsement proposal results returned by the endorsement nodes of all business related parties are obtained;
- the verification module is used to encapsulate the transaction-related data based on the resource request order as a transaction ledger record After the information, it is submitted to the ordering node of the resource
- an electronic device includes: a processor; and a memory for storing computer-readable instructions of the processor; wherein the processor is configured to execute the following by executing the computer-readable instructions method:
- the resource request order is the resource request order sent by the resource requester to the business related party through the business system, and the resource request order circulates among the business related parties in turn;
- the resource request order is used regularly Identifies the initiation of endorsement proposals to the endorsement nodes of each of the business related parties to receive the endorsement proposal results returned by the endorsement nodes of the business related parties according to the order flow, until the endorsement proposal results returned by the endorsement nodes of all business related parties are obtained;
- the transaction-related data of the resource request order is encapsulated as transaction ledger record information, it is submitted to the sorting node of the resource requester for sorting to obtain simulated transaction data blocks, so that the endorsing nodes of the parties to the resource transaction use the simulated transaction data
- the block performs transaction verification, and after the verification is passed, the transaction-related data is respectively saved to the ledger nodes of the parties to the resource transaction.
- a computer-readable storage medium has computer-readable instructions stored thereon, and when the computer-readable instructions are executed by a processor, the following method is implemented:
- the resource request order is the resource request order sent by the resource requester to the business related party through the business system, and the resource request order circulates among the business related parties in turn;
- the resource request order is used regularly Identifies the initiation of endorsement proposals to the endorsement nodes of each of the business related parties to receive the endorsement proposal results returned by the endorsement nodes of the business related parties according to the order flow, until the endorsement proposal results returned by the endorsement nodes of all business related parties are obtained;
- the transaction-related data of the resource request order is encapsulated as transaction ledger record information, it is submitted to the sorting node of the resource requester for sorting to obtain simulated transaction data blocks, so that the endorsing nodes of the parties to the resource transaction use the simulated transaction data
- the block performs transaction verification, and after the verification is passed, the transaction-related data is respectively saved to the ledger nodes of the parties to the resource transaction.
- the transaction-related data of the resource transaction is abstracted as a blockchain transaction ledger, and then the simulated transaction data block is obtained through sorting, so that the endorsing nodes of all parties to the resource transaction automatically verify the transaction process, and realize the order-based
- the automatic reconciliation and verification of data in upstream and downstream resource transactions can save a lot of time and resources that are required for manual reconciliation and verification. In turn, the overall stability and reliability of resource request transactions are effectively improved.
- Fig. 1 schematically shows a flowchart of a resource request transaction method based on a blockchain network.
- Fig. 2 schematically shows an example diagram of an application scenario of a resource request transaction method based on a blockchain network.
- Fig. 3 schematically shows a flowchart of another resource request transaction method based on a blockchain network.
- Fig. 4 schematically shows a block diagram of a resource request transaction device based on a blockchain network.
- Fig. 5 schematically shows an example block diagram of an electronic device for implementing the above-mentioned blockchain network-based resource request transaction method.
- Fig. 6 schematically shows a computer-readable storage medium for implementing the resource request transaction method based on the blockchain network.
- This example embodiment first provides a resource request transaction method based on a blockchain network.
- the resource request transaction method based on a blockchain network can be run on a server, a server cluster or a cloud server, etc.
- the field Technicians can also run the method of the present invention on other platforms as required, which is not particularly limited in this exemplary embodiment.
- the blockchain network includes endorsement nodes of all parties to the resource transaction, ledger nodes, ordering nodes, and business terminals of all parties to the resource transaction connected to each node. This method can be executed by the business terminal of the resource requester, as shown in Figure 1.
- the resource request transaction method based on the blockchain network may include the following steps:
- Step S110 Cache the identifier of the resource request order.
- the resource request order is a resource request order sent by the resource requester to the business related party through the business system, and the resource request order is transferred among the business related parties in turn;
- Step S120 Periodically use the resource request order identifier to initiate an endorsement proposal to the endorsing nodes of each of the business related parties, so as to receive the endorsement proposal results returned by the endorsing nodes of the business related parties according to the order flow, until endorsements from all business related parties are obtained The endorsement proposal result returned by the node;
- Step S130 After encapsulating the transaction-related data based on the resource request order as transaction ledger record information, it is submitted to the sorting node of the resource requester for sorting to obtain simulated transaction data blocks, so that the endorsing nodes of the resource transaction parties can use
- the simulated transaction data block performs transaction verification, and after the verification is passed, the transaction-related data are respectively saved to the ledger nodes of all parties to the resource transaction.
- the identifier of the resource request order is cached.
- the resource request order is the resource request order sent by the resource requester to the business related party through the business system.
- the resource request order is in turn Circulation between business-related parties; realizes that the resource requester caches the identifier of the resource request order that is circulated among the business-related parties, and then can obtain the identifier as needed in the subsequent steps.
- the resource request order identifier to initiate an endorsement proposal to the endorsing nodes of each of the business related parties to receive the endorsement proposal results returned by the endorsing nodes of the business related parties according to the order flow, until the endorsement nodes of all the business related parties are obtained
- the returned endorsement proposal result using the secure storage and unchangeable features of the distributed ledger of the blockchain, the reliability of transaction data is ensured by the endorsement node, and the identifier of the resource request order is regularly used to initiate endorsement proposals to the endorsing node of the business related party, The time difference and tracking omissions caused by the transaction data of all parties in the transaction process are avoided, and the reliable tracking of transaction data in the transaction process is realized.
- the transaction-related data is submitted to the sorting node of the resource requester for sorting to obtain simulated transaction data blocks, so that the endorsing nodes of the resource transaction parties can use all the transaction data.
- the simulated transaction data block performs transaction verification, and after the verification is passed, the transaction-related data is respectively saved to the ledger nodes of all parties to the resource transaction.
- step S110 the identifier of the resource request order is cached.
- the resource request order is a resource request order sent by the resource requester to the service related party through the service system, and the resource request order is sequentially transferred among the service related parties.
- the blockchain network 204 in the system architecture is Including the blockchain nodes of all parties to the resource transaction, including: the blockchain node 2011 of the resource requester (including endorsement nodes, ledger nodes, and ordering nodes) and the blockchain node 2021 of the business related party 1 (including endorsement nodes, ledger nodes) Nodes, ordering nodes) and the second blockchain node 2031 of the business related party (including endorsement nodes, ledger nodes, and ordering nodes), and also include the business terminals of the resource transaction parties connected to the blockchain nodes of each resource transaction party (Including the service terminal 201 of the resource requester, the service terminal 202 of the service related party 1 and the service terminal 203 of the service related party 2), the resource request transaction method based on the blockchain network can be used by the service terminal 201 of the resource requester Implementation, it can be understood that, according to requirements, there may be multiple or
- there are five business related parties that is, five business related parties’ respective service terminals are included.
- Three or more parties of resource request transactions establish a blockchain network for reconciliation, and build endorsement nodes, ledger nodes, and ordering nodes for each business party based on blockchain technology. These nodes are logically divided and can be physically deployed on one server.
- the service terminal 201 of the resource requester can cache the identifier of the resource request order.
- the resource request order means that the resource requester directly sends to each service related party through the service system (in this example, the service terminal 202 of service related party 1 and the service related party 2
- the resource request order sent by the service terminal 203) the resource request order circulates among the service related parties in turn (in this example, the service terminal 202 of the service related party 1 first receives the resource request order, and then the service terminal 202 will process it. It is sent to the service terminal 203 of the service related party 2 through the service system to realize sequential circulation).
- the business terminal can be various terminal devices with processing functions such as computers and mobile phones, which are not specifically limited here
- the blockchain node can be a server node corresponding to each business party, which is not specifically limited here.
- the parties to the resource request transaction store the transaction order based on the resource request order in the business system, including the order identification, processing status, processing time and other necessary information for reconciliation,
- a resource request order is an order created by a resource requester, and the identifier of the order can be an order number, etc.
- a business system is a system that can transmit detailed information about a resource request order, such as user-related information, and each business party in the business system transmits order-related information.
- the identifier of the cache resource request order can be stored in the delay queue after the resource requester creates the resource request order.
- the resource requester can cache the identifier of the resource request order circulating among the business related parties, and then the identifier can be obtained as needed in the subsequent steps.
- the application of the business system includes business party A (resource requester), business party B, and business party C (business related party).
- business party A is the entity that obtains the user's loan order (resource request order).
- the user selects the loan product (resource) provided by business party B through the business system through the app of business party A, and business party A ( Resource requester) submit a user loan order (resource request order) including user information in the app of business party A, that is, business party A creates a user loan intention order
- business party B can be the loan product operator
- business party C It can be the provider of loan funds, and can be regarded as the downstream loan product operator of business party B.
- the source business party A creates an order and the order is passed to business party B for processing in turn, and business party B is then passed to business party C for processing.
- the identifier of the cache resource request order includes:
- the identifier of the resource request order is cached in the order list of the delay queue, and the delay queue is set with endorsement proposal delay times corresponding to different business related parties.
- the order list of the delay queue is a list of storage order identifications. Different business parties can set different endorsement proposal delay times through careful control. For example, the time for B’s endorsement proposal is 3 minutes, and the time for C’s endorsement proposal is 5 Minutes can reduce redundant system interactions and avoid repeated endorsement proposals by nodes that have already returned endorsement response results.
- step S120 the resource request order identifier is periodically used to initiate an endorsement proposal to the endorsing node of each of the business related parties, so as to receive the endorsement proposal result returned by the endorsing node of the business related party according to the order flow situation, until all the business related parties are obtained.
- the endorsement proposal result returned by the endorsement node is periodically used to initiate an endorsement proposal to the endorsing node of each of the business related parties, so as to receive the endorsement proposal result returned by the endorsing node of the business related party according to the order flow situation, until all the business related parties are obtained.
- the resource requester of the service creates a service resource request order, and can store the identifier of the resource request order in the delay queue, and the identifier can be periodically encapsulated as a parameter of the endorsement proposal through the delay queue.
- the endorsement node of the business related party of the business initiates the endorsement proposal; the endorsement node can be used as a node in the chain that verifies the transaction and declares that the transaction is legal (or illegal).
- the endorsement node can also be the accounting node.
- the endorsement node of the blockchain can store the order details uploaded by each business party or obtained from the business system to meet the reconciliation needs of the resource request process, as well as information related to the order flow such as the information received and processed by the business related parties.
- the resource requester can periodically use the identifier of the resource request order to initiate an endorsement proposal to the endorsement node of each business related party to receive the endorsement node of the business related party according to the order flow situation (for example, the business related party receives and processes the order demand Situation)
- the returned endorsement proposal results until the endorsement proposal results returned by all business-related parties' endorsement nodes are obtained.
- detailed information about the order is transmitted through the business system.
- the regular setting can be to set a delay time of 3 minutes, 5 minutes, etc. to initiate an endorsement proposal.
- Endorsement proposal results such as order information has not been received, order information has been received but business system verification is abnormal or processing abnormality, etc.
- Set different endorsement proposal time to different business parties through careful control. For example, the endorsement proposal time for B is 3 minutes, and the endorsement proposal time for C is 5 minutes, reducing system redundant interactions and avoiding nodes that have returned endorsement response results Repeat the endorsement proposal.
- the endorsement proposal result of a certain node when the endorsement proposal result of a certain node is successfully processed by the business system, it means that the business party has successfully processed the order, and then the next business party can receive the order transmitted by the previous business party through the business system, and get The endorsement proposal results returned by the endorsement nodes of all business related parties indicate the end of the order flow.
- the secure storage and unchangeable characteristics of the distributed ledger of the blockchain can be used to ensure the reliability of transaction data through the endorsement node, and regularly use the identifier of the resource request order to initiate an endorsement proposal to the endorsing node of the business related party, avoiding the transaction process
- the regular use of the resource request order identifier to initiate an endorsement proposal to the endorsing node of each of the business related parties to cache the endorsement proposal result returned by the endorsing node of the business related party according to the order flow situation includes:
- the delay queue periodically scans the order list to, when the order list is not empty, encapsulate the identifiers in the order list into the parameters of the endorsement proposal, according to the delay time corresponding to each of the business related parties Initiate an endorsement proposal to the endorsement node of each of the business related parties.
- the delayed queue scans the order list periodically.
- an order identifier can be taken out, but not deleted from the queue.
- the identifier in the order list is encapsulated into the parameters of the endorsement proposal to initiate the endorsement proposal.
- the order identifier can be deleted from the delay queue when the endorsement proposal results of all business parties are obtained or the business of the business order is completed.
- the source business party A creates a user loan order in the business system, and then stores the order number in the delay queue.
- the queue scans the order list regularly.
- the order number is encapsulated into the parameters of the endorsement proposal, and the endorsement proposal is initiated to the endorsing nodes of the business related party B and the business related party C.
- step S310 after receiving the resource request order, the business related party performs resource transaction processing based on the resource request order to obtain the processing result; in step S320, if all When the processing result is that the processing is successful, the transaction record of the resource transaction processing is saved to the ledger node of the business related party, and the transaction record includes the identifier of the resource request order.
- the stored transaction records are actually the flow status of the order, including record information such as the source order number and other order identification, processing results and processing time of each business party.
- the endorsement proposal result returned by the endorsement node of the business related party according to the order flow situation includes:
- the endorsement node of the business-associated party queries the last transaction record of the ledger node of the business-associated party, and if the resource request order identifier in the transaction record is consistent with the resource request order identifier in the endorsement proposal, it returns that the process is successful The result of the first endorsement proposal;
- the endorsement node of the business related party can determine the parameters of the endorsement proposal (the identifier of the resource request order in the endorsement proposal) and the identifier in the record of the current transaction (the last transaction record) by querying the records of the state database (the ledger node) Whether they are consistent; if they are consistent, the processing is successful. If they are inconsistent, it means that they have not been processed. Then the business system will be called back according to the contract to query the current status of resource transaction processing based on the resource request order (for example, whether the order information in the endorsement proposal has been received), and the second endorsement proposal result will be obtained. return. Among them, the result of the second endorsement proposal, for example, the business system does not respond for timeout processing.
- the second endorsement proposal result includes:
- the order information has not been received, the business system verifies the abnormality or the processing is abnormal, the business system responds successfully, and the business system does not respond to one of the timeout processing.
- the endorsement proposal initiated by the source business party A is used to query the business parties B and C (business related parties) about the processing result status of the transaction corresponding to the order number contained in the endorsement proposal.
- business parties B and C receive the proposal, they will query and return the transaction result status corresponding to the order number in their respective business systems.
- a initiates an endorsement proposal to B the endorsement proposal encapsulates the order number, the time when A initiates the transaction, and the current order status.
- These three parameters are encrypted with B’s public key, and business party B receives the proposal to decrypt it with its own private key. With these three parameters, call the B business system api to obtain the order status, determine whether the received transaction time is correct, and return the result to A.
- A receives the result of B’s proposal, and then initiates an endorsement proposal to C, which is encapsulated in the endorsement proposal Order number, the transaction time returned by B to A in the last proposal result is the time when B initiates the transaction to C and the current order status of B.
- These three parameters are encrypted with C’s public key, and the endorsement proposal is initiated to C. Then decrypt the private key and return the proposal result like class B.
- step S130 after the transaction-related data based on the resource request order is encapsulated as transaction book record information, it is submitted to the sorting node of the resource requester for sorting to obtain a simulated transaction data block, so that the endorsement of all parties to the resource transaction
- the node uses the simulated transaction data block to perform transaction verification, and after the verification is passed, the transaction-related data is respectively saved to the ledger nodes of the parties to the resource transaction.
- the transaction-related data based on the resource request order is the transaction-related data corresponding to the endorsement proposal results of all business parties obtained through the endorsement proposal, including the processing results and processing time of the resource requester and the related business parties. Relevant data such as order number information required for reconciliation.
- the resource requester receives the endorsement response result from the business related party, knows that the flow of the order has ended, simulates the blockchain transaction, and encapsulates the order number information required for reconciliation, the processing result and processing time of the business party into a transaction ledger record Information, and submit this information to the blockchain sorting node for sorting.
- the source business party A receives the endorsement response results from business parties B and C, knows that the flow of the order has ended, simulates a blockchain transaction, and will reconcile the required order number information, A, B, and C processing results And processing time is encapsulated into transaction book record information, and this information is submitted to the blockchain sorting node for sorting.
- the ordering method of the blockchain ordering node can be based on the Kafka queue.
- the source business party A submits transaction data to the kafka message queue, where the source business party A can have multiple servers submit concurrently, and the kafka message queue receives the transaction data by the ledger node Sort by time sequence, and then send the sorted transaction data to the ledger nodes of A, B, and C through the broadcast mechanism for status submission. It may not be sorted by actual order end time.
- a pre-sequencer is added to the sorting node.
- the pre-sequencer caches a certain number of transaction records, and sorts the cached records according to the order end time through a timer, and then batches, for example, the previous 30 seconds
- the data is pressed into the Kafka queue, so that the transaction data blocks in the Kafka queue are sorted according to the order end time.
- the endorsement nodes of each business party respectively verify the received transaction data information and store it in the ledger node.
- the legality of the submitted data can be verified, that is, whether the simulated transaction data block submitted by the judgment section is consistent with the endorsement response result returned to the resource requester during the endorsement process. If the inconsistency indicates that the data has been modified, the data will be ignored and the data will be consistent. Finally, it is submitted to the ledger node of all parties to the resource transaction.
- the transaction-related data based on the resource request order is encapsulated as transaction ledger record information, it is submitted to the sorting node of the resource requester for sorting to obtain a simulated transaction data block, so that the endorsement nodes of all parties to the resource transaction use the simulated transaction data block to perform The transaction is verified, and after the verification is passed, the transaction-related data is saved to the ledger nodes of the parties to the resource transaction.
- the endorsement nodes of the parties to the resource transaction use the simulated transaction data block to perform transaction verification, and after the verification is passed, the transaction-related data are respectively saved to the ledger nodes of the parties to the resource transaction, including :
- the endorsement nodes of the parties to the resource transaction perform transaction verification according to the simulated transaction data block and the endorsement proposal results returned by the endorsement nodes of each of the business related parties to obtain the verification results of the parties to the resource transaction;
- the parties to the resource transaction respectively save the transaction-related data to the ledger nodes of the parties to the resource transaction.
- the endorsement nodes of each business party respectively verify the received transaction data information and store it in the ledger node.
- the legality of the submitted data can be verified, that is, whether the simulated transaction data block submitted by the judgment section is consistent with the endorsement response result returned to the resource requester during the endorsement process. If the inconsistency indicates that the data has been modified, the data will be ignored and the data will be consistent. Finally, it is submitted to the ledger node of all parties to the resource transaction.
- This application also provides a resource request transaction device based on the blockchain network.
- the blockchain network includes endorsement nodes of all parties to the resource transaction, ledger nodes, ordering nodes, and service terminals of all parties to the resource transaction connected to each of the nodes.
- the device is located at the service terminal of the resource requester.
- the resource request transaction device based on the blockchain network includes a cache module 410, a proposal module 420, and a verification module 430. in:
- the caching module 410 may be used to cache the identifier of a resource request order, the resource request order being a resource request order sent by a resource requester to a business related party through a business system, and the resource request order is in turn circulated among the business related parties;
- the proposal module 420 can be used to periodically use the resource to request an order identifier to initiate an endorsement proposal to the endorsing node of each business related party, so as to receive the endorsement proposal result returned by the endorsing node of the business related party according to the order flow, until all business related parties are obtained.
- the verification module 430 may be used to encapsulate the transaction-related data based on the resource request order into transaction ledger record information, and submit it to the sorting node of the resource requester for sorting to obtain simulated transaction data blocks, so that all parties to the resource transaction
- the endorsement node uses the simulated transaction data block to perform transaction verification, and after the verification is passed, the transaction-related data are respectively saved to the ledger nodes of the parties to the resource transaction.
- an electronic device capable of implementing the above method is also provided.
- the electronic device 500 according to this embodiment of the present invention will be described below with reference to FIG. 5.
- the electronic device 500 shown in FIG. 5 is only an example, and should not bring any limitation to the function and application scope of the embodiment of the present invention.
- the electronic device 500 is represented in the form of a general-purpose computing device.
- the components of the electronic device 500 may include, but are not limited to: the aforementioned at least one processing unit 510, the aforementioned at least one storage unit 520, and a bus 530 connecting different system components (including the storage unit 520 and the processing unit 510).
- the storage unit stores program code, and the program code can be executed by the processing unit 510, so that the processing unit 510 executes the various exemplary methods described in the "Exemplary Method" section of this specification. Steps of implementation.
- the processing unit 510 may perform the steps shown in FIG. 1.
- step S110 the identifier of the resource request order is cached, and the resource request order is a resource request sent by the resource requester to the business related party through the business system. Orders, the resource request orders are sequentially transferred among the business related parties.
- step S120 the resource request order identifier is periodically used to initiate an endorsement proposal to the endorsing node of each of the business related parties, so as to receive the endorsement proposal result returned by the endorsing node of the business related party according to the order flow situation, until all the business related parties are obtained.
- the endorsement proposal result returned by the endorsement node is periodically used to initiate an endorsement proposal to the endorsing node of each of the business related parties, so as to receive the endorsement proposal result returned by the endorsing node of the business related party according to the order flow situation, until all the business related parties are obtained.
- step S130 after the transaction-related data based on the resource request order is encapsulated as transaction book record information, it is submitted to the sorting node of the resource requester for sorting to obtain a simulated transaction data block, so that the endorsement of all parties to the resource transaction
- the node uses the simulated transaction data block to perform transaction verification, and after the verification is passed, the transaction-related data is respectively saved to the ledger nodes of the parties to the resource transaction.
- the storage unit 520 may include a readable medium in the form of a volatile storage unit, such as a random access storage unit (RAM) 5201 and/or a cache storage unit 5202, and may further include a read-only storage unit (ROM) 5203.
- RAM random access storage unit
- ROM read-only storage unit
- the storage unit 520 may also include a program/utility tool 5204 having a set of (at least one) program module 5205.
- program module 5205 includes but is not limited to: an operating system, one or more application programs, other program modules, and program data, Each of these examples or some combination may include the implementation of a network environment.
- the bus 530 may represent one or more of several types of bus structures, including a storage unit bus or a storage unit controller, a peripheral bus, a graphics acceleration port, a processing unit, or a local area using any bus structure among multiple bus structures. bus.
- the electronic device 500 can also communicate with one or more external devices 700 (such as keyboards, pointing devices, Bluetooth devices, etc.), and can also communicate with one or more devices that enable customers to interact with the electronic device 500, and/or communicate with Any device (such as a router, modem, etc.) that enables the electronic device 500 to communicate with one or more other computing devices. Such communication may be performed through an input/output (I/O) interface 550, and may also include a display unit 540 connected to the input/output (I/O) interface 550.
- the electronic device 500 may also communicate with one or more networks (for example, a local area network (LAN), a wide area network (WAN), and/or a public network, such as the Internet) through the network adapter 560.
- networks for example, a local area network (LAN), a wide area network (WAN), and/or a public network, such as the Internet
- the network adapter 560 communicates with other modules of the electronic device 500 through the bus 530.
- other hardware and/or software modules can be used in conjunction with the electronic device 500, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives And data backup storage system, etc.
- the example embodiments described here can be implemented by software, or can be implemented by combining software with necessary hardware. Therefore, the technical solution according to the embodiments of the present application can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (which can be a CD-ROM, U disk, mobile hard disk, etc.) or on the network , Including several instructions to make a computing device (which can be a personal computer, a server, a terminal device, or a network device, etc.) execute the method according to the embodiment of the present application.
- a computing device which can be a personal computer, a server, a terminal device, or a network device, etc.
- a computer-readable storage medium is also provided.
- the computer-readable storage medium may be non-volatile or volatile, and stored thereon Program products that can implement the above-mentioned methods in this specification.
- various aspects of the present invention may also be implemented in the form of a program product, which includes program code.
- the program product runs on a terminal device, the program code is used to enable the The terminal device executes the steps according to various exemplary embodiments of the present invention described in the above-mentioned "Exemplary Method" section of this specification.
- a program product 600 for implementing the above method according to an embodiment of the present invention is described. It can adopt a portable compact disk read-only memory (CD-ROM) and include program code, and can be installed in a terminal device, For example, running on a personal computer.
- the program product of the present invention is not limited to this.
- the readable storage medium can be any tangible medium that contains or stores a program, and the program can be used by or combined with an instruction execution system, device, or device.
- the program product can use any combination of one or more readable media.
- the readable medium may be a readable signal medium or a readable storage medium.
- the readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or device, or a combination of any of the above. More specific examples (non-exhaustive list) of readable storage media include: electrical connections with one or more wires, portable disks, hard disks, random access memory (RAM), read only memory (ROM), erasable Type programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination of the above.
- the computer-readable signal medium may include a data signal propagated in baseband or as a part of a carrier wave, and readable program code is carried therein. This propagated data signal can take many forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the foregoing.
- the readable signal medium may also be any readable medium other than a readable storage medium, and the readable medium may send, propagate, or transmit a program for use by or in combination with the instruction execution system, apparatus, or device.
- the program code contained on the readable medium can be transmitted by any suitable medium, including but not limited to wireless, wired, optical cable, RF, etc., or any suitable combination of the foregoing.
- the program code used to perform the operations of the present invention can be written in any combination of one or more programming languages.
- the programming languages include object-oriented programming languages—such as Java, C++, etc., as well as conventional procedural styles. Programming language-such as "C" language or similar programming language.
- the program code can be executed entirely on the client computing device, partly executed on the client device, executed as an independent software package, partly executed on the client computing device and partly executed on the remote computing device, or entirely on the remote computing device or server Executed on.
- the remote computing device can be connected to a client computing device through any kind of network, including a local area network (LAN) or a wide area network (WAN), or it can be connected to an external computing device (for example, using Internet service providers). Business to connect via the Internet).
- LAN local area network
- WAN wide area network
- Internet service providers for example, using Internet service providers
Landscapes
- Engineering & Computer Science (AREA)
- Business, Economics & Management (AREA)
- Accounting & Taxation (AREA)
- Theoretical Computer Science (AREA)
- Finance (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- General Business, Economics & Management (AREA)
- Strategic Management (AREA)
- Databases & Information Systems (AREA)
- Data Mining & Analysis (AREA)
- Computer Security & Cryptography (AREA)
- General Engineering & Computer Science (AREA)
- Computing Systems (AREA)
- Signal Processing (AREA)
- Computer Networks & Wireless Communication (AREA)
- Development Economics (AREA)
- Economics (AREA)
- Marketing (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
一种基于区块链网络的资源请求交易验证方法装置、电子设备及计算机可读存储介质,属于区块链技术领域,所述区块链网络包括资源交易各方的背书节点、账本节点、排序节点及与各所述节点连接的资源交易各方的业务终端,所述方法由资源请求方的业务终端执行,所述方法包括:缓存资源请求订单的标识,定期利用资源请求订单的标识向各所述业务关联方的背书节点发起背书提议;将基于所述资源请求订单的交易相关数据提交到资源请求方的排序节点进行排序得到模拟交易数据块,以使得背书节点进行交易验证,并在验证通过后,分别将交易相关数据保存至资源交易各方的账本节点。本方法可有效提升资源请求交易的稳定性及可靠性。
Description
本申请要求于2020年4月28日提交中国专利局、申请号为202010349691.1,发明名称为“基于区块链网络的资源请求交易方法及相关装置”的中国专利申请的优先权,其全部内容通过引用结合在本申请中。
本申请涉及区块链技术领域,具体而言,涉及一种基于区块链网络的资源请求交易方法、装置、电子设备及计算机可读存储介质。
一般地,在资源交易活动中,当用户选择好某种资源交易产品,填写好资源交易各方需要的交易相关信息之后,在资源请求方保存好资源请求订单,然后需要实时或批量(非实时)向各业务关联方流转资源请求订单。例如,有些情况业务合作方会将用户贷款订单流转给其它合作方(资金供应方)。
发明人意识到在资源请求订单的流转过程中(资源交易过程),可能会出现双方的系统不稳定,系统异常,或者网络不稳定等原因从而导致订单信息丢失,在我方和各合作方的交易中,需要人工检查订单流转过程中的异常,检验系统日志,消耗大量资源来进行验证工作,而且难免会有遗漏失误,导致资源请求交易不够稳定,可靠性较低。
为了解决上述技术问题,本申请的一个目的在于提供一种基于区块链网络的资源请求交易方法、装置、电子设备及计算机可读存储介质。
其中,本申请所采用的技术方案为:
第一方面,一种基于区块链网络的资源请求交易方法,所述区块链网络包括资源交易各方的背书节点、账本节点、排序节点及与各所述节点连接的资源交易各方的业务终端,所述方法由资源请求方的业务终端执行,所述方法包括:缓存资源请求订单的标识,所述资源请求订单为资源请求方通过业务系统向业务关联方发送的资源请求订单,所述资源请求订单依次在各业务关联方之间流转;定期利用资源请求订单的标识向各所述业务关联方的背书节点发起背书提议,以接收业务关联方的背书节点根据订单流转情况返回的背书提议结果,直到得到所有业务关联方的背书节点返回的背书提议结果;将基于所述资源请求订单的交易相关数据封装为交易账本记录信息后,提交到资源请求方的排序节点进行排序得到模拟交易数据块,以使得所述资源交易各方的背书节点利用所述模拟交易数据块进行交易验证,并在验证通过后,分别将所述交易相关数据保存至资源交易各方的所述账本节点。
第二方面,一种基于区块链网络的资源请求交易装置,所述区块链网络包括资源交易各方的背书节点、账本节点、排序节点及与各所述节点连接的资源交易各方的业务终端,所述装置位于所述资源请求方的业务终端,所述装置包括:缓存模块,用于缓存资源请求订单的标识,所述资源请求订单为资源请求方通过业务系统向业务关联方发送的资源请求订单,所述资源请求订单依次在各业务关联方之间流转;提议模块,用于定期利用资源请求订单的标识向各所述业务关联方的背书节点发起背书提议,以接收业务关联方的背书节点根据订单流转情况返回的背书提议结果,直到得到所有业务关联方的背书节点返回的背书提议结果;验证模块,用于将基于所述资源请求订单的交易相关数据封装为交易账本记录信息后,提交到资源请求方的排序节点进行排序得到模拟交易数据块,以使得所述资源交易各方的背书节点利用所述模拟交易数据块进行交易验证,并在验证通过后,分别将所述交易相关数据保存至资源交易各方的所述账本节点。
第三方面,一种电子设备,包括:处理器;以及存储器,用于存储所述处理器的计算机可读指令;其中,所述处理器配置为经由执行所述计算机可读指令来执行如下的方法:
缓存资源请求订单的标识,所述资源请求订单为资源请求方通过业务系统向业务关联方发送的资源请求订单,所述资源请求订单依次在各业务关联方之间流转;定期利用资源请求订单的标识向各所述业务关联方的背书节点发起背书提议,以接收业务关联方的背书节点根据订单流转情况返回的背书提议结果,直到得到所有业务关联方的背书节点返回的背书提议结果;将基于所述资源请求订单的交易相关数据封装为交易账本记录信息后,提交到资源请求方的排序节点进行排序得到模拟交易数据块,以使得所述资源交易各方的背书节点利用所述模拟交易数据块进行交易验证,并在验证通过后,分别将所述交易相关数据保存至资源交易各方的所述账本节点。
第四方面,一种计算机可读存储介质,其上存储有计算机可读指令,当所述计算机可读指令被处理器执行时,实现如下的方法:
缓存资源请求订单的标识,所述资源请求订单为资源请求方通过业务系统向业务关联方发送的资源请求订单,所述资源请求订单依次在各业务关联方之间流转;定期利用资源请求订单的标识向各所述业务关联方的背书节点发起背书提议,以接收业务关联方的背书节点根据订单流转情况返回的背书提议结果,直到得到所有业务关联方的背书节点返回的背书提议结果;将基于所述资源请求订单的交易相关数据封装为交易账本记录信息后,提交到资源请求方的排序节点进行排序得到模拟交易数据块,以使得所述资源交易各方的背书节点利用所述模拟交易数据块进行交易验证,并在验证通过后,分别将所述交易相关数据保存至资源交易各方的所述账本节点。
在上述技术方案中,实现,将资源交易的交易相关数据抽象为区块链交易账本,进而通过排序得到模拟交易数据块,使得资源交易各方的背书节点自动验证交易过程,实现了基于订单的数据在上下游资源交易各方的自动化对账验证,可以节省大量人工对账验证需要消耗的时间和资源。进而总体上有效提升资源请求交易的稳定性及可靠性。
应当理解的是,以上的一般描述和后文的细节描述仅是示例性和解释性的,并不能限制本申请。
图1示意性示出一种基于区块链网络的资源请求交易方法的流程图。
图2示意性示出一种基于区块链网络的资源请求交易方法的应用场景示例图。
图3示意性示出又一种基于区块链网络的资源请求交易方法流程图。
图4示意性示出一种基于区块链网络的资源请求交易装置的方框图。
图5示意性示出一种用于实现上述基于区块链网络的资源请求交易方法的电子设备示例框图。
图6示意性示出一种用于实现上述基于区块链网络的资源请求交易方法的计算机可读存储介质。
本示例实施方式中首先提供了基于区块链网络的资源请求交易方法,该基于区块链网络的资源请求交易方法可以运行于服务器,也可以运行于服务器集群或云服务器等,当然,本领域技术人员也可以根据需求在其他平台运行本发明的方法,本示例性实施例中对此不做特殊限定。该区块链网络包括资源交易各方的背书节点、账本节点、排序节点及与各节点连接的资源交易各方的业务终端,该方法可以由资源请求方的业务终端执行,参考图1所示,该基于区块链网络的资源请求交易方法可以包括以下步骤:
步骤S110,缓存资源请求订单的标识,所述资源请求订单为资源请求方通过业务系统向业务关联方发送的资源请求订单,所述资源请求订单依次在各业务关联方之间流转;
步骤S120,定期利用资源请求订单的标识向各所述业务关联方的背书节点发起背书提议,以接收业务关联方的背书节点根据订单流转情况返回的背书提议结果,直到得到所有业务关联方的背书节点返回的背书提议结果;
步骤S130,将基于所述资源请求订单的交易相关数据封装为交易账本记录信息后,提交到资源请求方的排序节点进行排序得到模拟交易数据块,以使得所述资源交易各方的背书节点利用所述模拟交易数据块进行交易验证,并在验证通过后,分别将所述交易相关数据保存至资源交易各方的所述账本节点。
上述基于区块链网络的资源请求交易方法,首先,缓存资源请求订单的标识,所述资源请求订单为资源请求方通过业务系统向业务关联方发送的资源请求订单,所述资源请求订单依次在各业务关联方之间流转;实现资源请求方将在各业务关联方之间流转的资源请求订单的标识缓存,进而可以在后续步骤根据需要获取该标识。
然后,定期利用资源请求订单的标识向各所述业务关联方的背书节点发起背书提议,以接收业务关联方的背书节点根据订单流转情况返回的背书提议结果,直到得到所有业务关联方的背书节点返回的背书提议结果;利用区块链分布式账本的安全存储和不可更改特性,通过背书节点保证交易数据的可靠性,且定期利用资源请求订单的标识向业务关联方的背书节点发起背书提议,避免了交易过程的各方的交易数据产生的时差及跟踪遗漏问题,实现交易过程的交易数据可靠跟踪。
其次,将基于所述资源请求订单的交易相关数据封装为交易账本记录信息后,提交到资源请求方的排序节点进行排序得到模拟交易数据块,以使得所述资源交易各方的背书节点利用所述模拟交易数据块进行交易验证,并在验证通过后,分别将所述交易相关数据保存至资源交易各方的所述账本节点。实现,将资源交易的交易相关数据抽象为区块链交易账本,进而通过排序得到模拟交易数据块,使得资源交易各方的背书节点自动验证交易过程,实现了基于订单的数据在上下游资源交易各方的自动化对账验证,可以节省大量人工对账验证需要消耗的时间和资源。进而总体上有效提升资源请求交易的稳定性及可靠性。
下面,将结合附图对本示例实施方式中上述基于区块链网络的资源请求交易方法中的各步骤进行详细的解释以及说明。
在步骤S110中,缓存资源请求订单的标识,所述资源请求订单为资源请求方通过业务系统向业务关联方发送的资源请求订单,所述资源请求订单依次在各业务关联方之间流转。
在本示例的实施方式中,参考图2所示,提供了一种可以应用本申请基于区块链网络的资源请求交易方法的实施例的系统架构图,该系统架构中的区块链网络204包括资源交易各方的区块链节点,包括:资源请求方的区块链节点2011(包括背书节点、账本节点、排序节点)及业务关联方一的区块链节点2021(包括背书节点、账本节点、排序节点)和业务关联方二的区块链节点2031(包括背书节点、账本节点、排序节点),还包括与各资源交易各方的区块链节点连接的资源交易各方的业务终端(包括资源请求方的业务终端201,业务关联方一的业务终端202和业务关联方二的业务终端203),该基于区块链网络的资源请求交易方法方法可以由资源请求方的业务终端201执行,可以理解,根据需求,业务关联方可以为多个或者1个,例如,再其他实施例中包括5个业务关联方,也就是包括5个业务关联方各自的业务终端。资源请求交易的三方或多方建立对账的区块链网络,基于区块链技术分别构建各业务方的背书节点、账本节点、排序节点。这些节点是逻辑上的分割,物理上可以部署在一台服务器上。
资源请求方的业务终端201可以缓存资源请求订单的标识,资源请求订单为资源请求方通过业务系统直接向各业务关联方(本示例中为业务关联方一的业务终端202和业务关联方二的业务终端203)发送的资源请求订单,该资源请求订单依次在各业务关联方之间流转(本示例中为业务关联方一的业务终端202先接收资源请求订单,再处理完后由业务终端202通过业务系统发送给业务关联方二的业务终端203,实现依次流转)。其中,业务终端可以是电脑、手机等各种具有处理功能的终端设备,在此不做特殊限定,区块链节点可以是各业务方对应的服务器节点,在此不做特殊限定。
资源请求交易的各方在业务系统中存储基于资源请求订单的交易订单,包括订单标识、处理状态、处理时间等用于对账必须的信息,
资源请求订单为资源请求方创建的订单,订单的标识可以是订单号等。业务系统是可以传输例如用户相关信息等资源请求订单的详细信息的系统,通过业务系统各业务方进行订单相关信息的传输。
缓存资源请求订单的标识,可以在资源请求方创建资源请求订单后,然后将该订单号存放于延时队列。
这样可以实现资源请求方将在各业务关联方之间流转的资源请求订单的标识缓存,进而可以在后续步骤根据需要获取该标识。
例如,业务系统的应用包括业务方A(资源请求方)、业务方B 和业务方C(业务关联方)。其中,业务方A(资源请求方)是获取用户贷款订单(资源请求订单)的实体,用户通过业务方A的app通过业务系统选择由业务方B提供的贷款产品(资源),业务方A(资源请求方)在业务方A的app中提交包括用户信息的用户贷款订单(资源请求订单),也即,业务方A创建用户贷款意向订单,业务方B可以是贷款产品运营方,业务方C可以是贷款资金提供方,可以看作业务方B的下游贷款产品运营方。其中源业务方A创建订单以及订单依次传递到业务方B进行处理,业务方B再传递到业务方C进行处理,这是需要一定的流转时间的,所以可以设置延时队列缓存订单号,以在后续步骤进行资源请求过程中与业务方B、C进行延时对账。
一种实施例中,所述缓存资源请求订单的标识,包括:
将所述资源请求订单的标识缓存于延时队列的订单列表,所述延时队列设置了对应于不同业务关联方的背书提议延时时间。
延时队列的订单列表是存储订单标识的列表,通过细致控制向不同业务方设置不同的背书提议延时时间,比如对B的背书提议的时间为3分钟,对C的背书提议的时间为5分钟,可以减少系统冗余交互,避免已经返回过背书响应结果的节点重复进行背书提议。
在步骤S120中, 定期利用资源请求订单的标识向各所述业务关联方的背书节点发起背书提议,以接收业务关联方的背书节点根据订单流转情况返回的背书提议结果,直到得到所有业务关联方的背书节点返回的背书提议结果。
在本示例的实施方式中,业务的资源请求方创建业务资源请求订单,并可以将资源请求订单的标识存放于延时队列,可以通过延时队列定期将该标识封装为背书提议的参数,向业务的业务关联方的背书节点发起背书提议;背书节点可以作为验证交易并声明此交易合法(或不合法)的链中节点,一个示例中背书节点也可以作为记账节点。区块链的背书节点中可以存储各业务方上传的或者从业务系统获取用于满足资源请求过程的对账需要的订单详细信息、以及业务关联方接收处理订单的信息等订单流转情况的相关信息,进而,资源请求方可以定期利用资源请求订单的标识向各业务关联方的背书节点发起背书提议,以接收业务关联方的背书节点根据订单流转情况(例如,业务关联方接收并处理订单需求的情况)返回的背书提议结果,直到得到所有业务关联方的背书节点返回的背书提议结果。特别地,订单的详细信息比如用户相关信息是通过业务系统进行传输。
根据业务实际情况,定期的设置可以是设置3分钟、5分钟等延时时间来发起背书提议。背书提议结果例如尚未收到订单信息、收到订单信息但业务系统验证异常或处理异常等。通过细致控制向不同业务方设置不同的背书提议时间,比如对B的背书提议时间为3分钟,对C的背书提议时间为5分钟,减少系统冗余交互,避免已经返回过背书响应结果的节点重复进行背书提议。订单再依次流转过程中,当某个节点的背书提议结果为业务系统成功处理时,说明该业务方成功处理订单,而后下一个业务方可以接收到上一个业务方通过业务系统传输的订单,得到所有业务关联方的背书节点返回的背书提议结果,说明订单流转结束。
这样可以利用区块链分布式账本的安全存储和不可更改特性,通过背书节点保证交易数据的可靠性,且定期利用资源请求订单的标识向业务关联方的背书节点发起背书提议,避免了交易过程的各方的交易数据产生的时差及跟踪遗漏问题,实现交易过程的交易数据可靠跟踪。
一种实施例中,所述定期利用资源请求订单的标识向各所述业务关联方的背书节点发起背书提议,以缓存业务关联方的背书节点根据订单流转情况返回的背书提议结果,包括:
所述延时队列定期扫描所述订单列表,以在所述订单列表不为空时,将所述订单列表中的标识封装成背书提议的参数,根据各所述业务关联方对应的延时时间向各所述业务关联方的背书节点发起背书提议。
延时队列定期扫描订单列表,可以在订单列表不为空时,取出一条订单标识,但不从队列中删除,将订单列表中的标识封装成背书提议的参数发起背书提议。可以在得到所有业务方的背书提议结果或者业务订单的业务完成时从延时队列中删除订单的标识。例如,源业务方A(资源请求方)在业务系统创建一个用户贷款订单,然后将该订单号存放于延时队列,该队列定时扫描订单列表,如果队列不为空,取出一条订单号,但不从队列中删除,将订单号封装成背书提议的参数,向业务关联方B 和业务关联方C的背书节点发起背书提议。
一种实施例中,参考图3所示,步骤S310中,业务关联方在接收到所述资源请求订单后,基于所述资源请求订单进行资源交易处理,得到处理结果;步骤S320中,如果所述处理结果为处理成功时,将资源交易处理的交易记录保存至所述业务关联方的账本节点,所述交易记录包括所述资源请求订单的标识。
存储的交易记录实际上是订单的流转状态,包含源订单号等订单标识,各业务方处理结果和处理时间等记录信息。
一种实施例中,业务关联方的背书节点根据订单流转情况返回的背书提议结果,包括:
业务关联方的背书节点查询所述业务关联方的账本节点的最后一条交易记录,如果该交易记录中的资源请求订单的标识和所述背书提议中的资源请求订单的标识一致,则返回处理成功的第一背书提议结果;
如果该交易记录中的资源请求订单的标识和所述背书提议中的资源请求订单的标识不一致,则回调所述业务系统查询基于所述资源请求订单进行资源交易处理状态,得到第二背书提议结果进行返回。
业务关联方的背书节点可以通过查询状态数据库(账本节点)的记录,确定所述背书提议的参数(背书提议中的资源请求订单的标识)与当前交易的记录(最后一条交易记录)中的标识是否一致;如果一致,说明成功处理。如果不一致,说明尚未处理过,那么就会根据合约去回调业务系统查询基于资源请求订单进行资源交易处理的当前状态(例如,是否接收到背书提议中的订单信息),得到第二背书提议结果进行返回。其中,第二背书提议结果例如业务系统没有响应做超时处理。
一种实施例中,第二背书提议结果,包括:
尚未收到订单信息、收到订单信息但业务系统验证异常或处理异常、业务系统响应成功及业务系统没有响应做超时处理中一种。
业务系统向背书节点返回的查询结果有几种情况,一是尚未收到订单信息,二是收到信息但业务系统验证异常或处理异常,三 业务系统响应成功,四是业务系统没有响应做超时处理。可以给这四种情况分别定义字符标识,例如分别为NOT_RECEIVE, VALID_ERROR,PROCESS_ERROR,SUCCESS, TIMEOUT。
一个示例中,源业务方A(资源请求方)发起的背书提议,是用来询问业务方B和C(业务关联方)该背书提议中包含的订单号对应的交易的处理结果状态的。业务方B和C收到提议,将会查询各自的业务系统中对订单号对应的交易结果状态并返回。当A向B发起背书提议,背书提议中封装订单号、A发起交易的时间、当前订单状态,将这三个参数用B的公钥进行加密,业务方B收到提议用自己的私钥解密这三个参数,调用B业务系统api获取订单状态,判断收到的发起交易时间是否正确,并将结果返回给A,A收到B的提议结果,再向C发起背书提议,背书提议中封装订单号,上一个提议结果中B返回给A的交易时间是B向C发起交易的时间和B的当前订单状态,将这三个参数用C的公钥进行加密,向C发起背书提议,C再进行私钥解密和类B一样返回提议结果。
在步骤S130中,将基于所述资源请求订单的交易相关数据封装为交易账本记录信息后,提交到资源请求方的排序节点进行排序得到模拟交易数据块,以使得所述资源交易各方的背书节点利用所述模拟交易数据块进行交易验证,并在验证通过后,分别将所述交易相关数据保存至资源交易各方的所述账本节点。
在本示例的实施方式中,基于资源请求订单的交易相关数据即通过背书提议得到的所有业务方的背书提议结果对应的交易相关数据,包括资源请求方、关联业务方的处理结果和处理时间,对账需要的订单号信息等相关数据。
资源请求方收到业务关联方的背书响应结果,获知该订单的流转过程已经结束,模拟区块链交易,将对账需要的订单号信息、业务方的处理结果和处理时间封装成交易账本记录信息,并将此信息提交到区块链排序节点进行排序。例如,源业务方A收到业务方B和C的背书响应结果,获知该订单的流转过程已经结束,模拟区块链交易,将对账需要的订单号信息、A、B、C的处理结果和处理时间封装成交易账本记录信息,并将此信息提交到区块链排序节点进行排序。
区块链排序节点排序方式可以是基于Kafka队列,例如,源业务方A提交交易数据到kafka消息队列,这里源业务方A可以有多台服务器并发提交,kafka消息队列以账本节点接收交易数据的时间顺序来排序,再通过广播机制将排序后的交易数据发送给A、B、C的账本节点进行状态提交。可以不是以实际订单结束时间来排序。一个实施例中,在排序节点上增加前置排序器,前置排序器缓存一定数量的交易记录,并通过定时器定时将缓存的记录按照订单结束时间来排序,再批量将比如前30秒的数据压入kafka队列中,这样kafka队列中的交易数据块即是按订单结束时间进行排序过的。
各业务方的背书节点分别各自进行验证接收到的交易数据信息并存储到账本节点。可以验证提交数据的合法性,即判段提交的模拟交易数据块是否和背书过程中返回给资源请求方的背书响应结果是否一致,如果不一致说明数据发生攥改则忽略该条数据,一致才进行最终提交至资源交易各方的账本节点。
将基于资源请求订单的交易相关数据封装为交易账本记录信息后,提交到资源请求方的排序节点进行排序得到模拟交易数据块,以使得资源交易各方的背书节点利用所述模拟交易数据块进行交易验证,并在验证通过后,分别将交易相关数据保存至资源交易各方的账本节点。实现,将资源交易的交易相关数据抽象为区块链交易账本,进而通过排序得到模拟交易数据块,使得资源交易各方的背书节点自动验证交易过程,实现了基于订单的数据在上下游资源交易各方的自动化对账验证,可以节省大量人工对账验证需要消耗的时间和资源。进而总体上有效提升资源请求交易的稳定性及可靠性。
一种实施例中,资源交易各方的背书节点利用所述模拟交易数据块进行交易验证,并在验证通过后,分别将所述交易相关数据保存至资源交易各方的所述账本节点,包括:
所述资源交易各方的背书节点,根据所述模拟交易数据块及各所述业务关联方的背书节点返回的背书提议结果进行交易验证,得到所述资源交易各方的验证结果;
当所述资源交易各方的验证结果都为验证通过时,所述资源交易各方分别将所述交易相关数据保存至资源交易各方的所述账本节点。
各业务方的背书节点分别各自进行验证接收到的交易数据信息并存储到账本节点。可以验证提交数据的合法性,即判段提交的模拟交易数据块是否和背书过程中返回给资源请求方的背书响应结果是否一致,如果不一致说明数据发生攥改则忽略该条数据,一致才进行最终提交至资源交易各方的账本节点。
本申请还提供了一种基于区块链网络的资源请求交易装置。该区块链网络包括资源交易各方的背书节点、账本节点、排序节点及与各所述节点连接的资源交易各方的业务终端,所述装置位于所述资源请求方的业务终端,参考图4所示,该基于区块链网络的资源请求交易装置包括缓存模块410、提议模块420、验证模块430。其中:
缓存模块410可以用于缓存资源请求订单的标识,所述资源请求订单为资源请求方通过业务系统向业务关联方发送的资源请求订单,所述资源请求订单依次在各业务关联方之间流转;
提议模块420可以用于定期利用资源请求订单的标识向各所述业务关联方的背书节点发起背书提议,以接收业务关联方的背书节点根据订单流转情况返回的背书提议结果,直到得到所有业务关联方的背书节点返回的背书提议结果;
验证模块430可以用于将基于所述资源请求订单的交易相关数据封装为交易账本记录信息后,提交到资源请求方的排序节点进行排序得到模拟交易数据块,以使得所述资源交易各方的背书节点利用所述模拟交易数据块进行交易验证,并在验证通过后,分别将所述交易相关数据保存至资源交易各方的所述账本节点。
上述基于区块链网络的资源请求交易装置中各模块的具体细节已经在对应的基于区块链网络的资源请求交易方法中进行了详细的描述,因此此处不再赘述。
在本申请的示例性实施例中,还提供了一种能够实现上述方法的电子设备。
下面参照图5来描述根据本发明的这种实施方式的电子设备500。图5显示的电子设备500仅仅是一个示例,不应对本发明实施例的功能和使用范围带来任何限制。
如图5所示,电子设备500以通用计算设备的形式表现。电子设备500的组件可以包括但不限于:上述至少一个处理单元510、上述至少一个存储单元520、连接不同系统组件(包括存储单元520和处理单元510)的总线530。
其中,所述存储单元存储有程序代码,所述程序代码可以被所述处理单元510执行,使得所述处理单元510执行本说明书上述“示例性方法”部分中描述的根据本发明各种示例性实施方式的步骤。例如,所述处理单元510可以执行如图1中所示的步骤,在步骤S110中,缓存资源请求订单的标识,所述资源请求订单为资源请求方通过业务系统向业务关联方发送的资源请求订单,所述资源请求订单依次在各业务关联方之间流转。在步骤S120中, 定期利用资源请求订单的标识向各所述业务关联方的背书节点发起背书提议,以接收业务关联方的背书节点根据订单流转情况返回的背书提议结果,直到得到所有业务关联方的背书节点返回的背书提议结果。在步骤S130中,将基于所述资源请求订单的交易相关数据封装为交易账本记录信息后,提交到资源请求方的排序节点进行排序得到模拟交易数据块,以使得所述资源交易各方的背书节点利用所述模拟交易数据块进行交易验证,并在验证通过后,分别将所述交易相关数据保存至资源交易各方的所述账本节点。
存储单元520可以包括易失性存储单元形式的可读介质,例如随机存取存储单元(RAM)5201和/或高速缓存存储单元5202,还可以进一步包括只读存储单元(ROM)5203。
存储单元520还可以包括具有一组(至少一个)程序模块5205的程序/实用工具5204,这样的程序模块5205包括但不限于:操作系统、一个或者多个应用程序、其它程序模块以及程序数据,这些示例中的每一个或某种组合中可能包括网络环境的实现。
总线530可以为表示几类总线结构中的一种或多种,包括存储单元总线或者存储单元控制器、外围总线、图形加速端口、处理单元或者使用多种总线结构中的任意总线结构的局域总线。
电子设备500也可以与一个或多个外部设备700(例如键盘、指向设备、蓝牙设备等)通信,还可与一个或者多个使得客户能与该电子设备500交互的设备通信,和/或与使得该电子设备500能与一个或多个其它计算设备进行通信的任何设备(例如路由器、调制解调器等等)通信。这种通信可以通过输入/输出(I/O)接口550进行,还可以包括与输入/输出(I/O)接口550连接的显示单元540。并且,电子设备500还可以通过网络适配器560与一个或者多个网络(例如局域网(LAN),广域网(WAN)和/或公共网络,例如因特网)通信。如图所示,网络适配器560通过总线530与电子设备500的其它模块通信。应当明白,尽管图中未示出,可以结合电子设备500使用其它硬件和/或软件模块,包括但不限于:微代码、设备驱动器、冗余处理单元、外部磁盘驱动阵列、RAID系统、磁带驱动器以及数据备份存储系统等。
通过以上的实施方式的描述,本领域的技术人员易于理解,这里描述的示例实施方式可以通过软件实现,也可以通过软件结合必要的硬件的方式来实现。因此,根据本申请实施方式的技术方案可以以软件产品的形式体现出来,该软件产品可以存储在一个非易失性存储介质(可以是CD-ROM,U盘,移动硬盘等)中或网络上,包括若干指令以使得一台计算设备(可以是个人计算机、服务器、终端装置、或者网络设备等)执行根据本申请实施方式的方法。
在本申请的示例性实施例中,参考图6所示,还提供了一种计算机可读存储介质,该计算机可读存储介质可以是非易失性,也可以是易失性,其上存储有能够实现本说明书上述方法的程序产品。在一些可能的实施方式中,本发明的各个方面还可以实现为一种程序产品的形式,其包括程序代码,当所述程序产品在终端设备上运行时,所述程序代码用于使所述终端设备执行本说明书上述“示例性方法”部分中描述的根据本发明各种示例性实施方式的步骤。
参考图6所示,描述了根据本发明的实施方式的用于实现上述方法的程序产品600,其可以采用便携式紧凑盘只读存储器(CD-ROM)并包括程序代码,并可以在终端设备,例如个人电脑上运行。然而,本发明的程序产品不限于此,在本文件中,可读存储介质可以是任何包含或存储程序的有形介质,该程序可以被指令执行系统、装置或者器件使用或者与其结合使用。
所述程序产品可以采用一个或多个可读介质的任意组合。可读介质可以是可读信号介质或者可读存储介质。可读存储介质例如可以为但不限于电、磁、光、电磁、红外线、或半导体的系统、装置或器件,或者任意以上的组合。可读存储介质的更具体的例子(非穷举的列表)包括:具有一个或多个导线的电连接、便携式盘、硬盘、随机存取存储器(RAM)、只读存储器(ROM)、可擦式可编程只读存储器(EPROM或闪存)、光纤、便携式紧凑盘只读存储器(CD-ROM)、光存储器件、磁存储器件、或者上述的任意合适的组合。
计算机可读信号介质可以包括在基带中或者作为载波一部分传播的数据信号,其中承载了可读程序代码。这种传播的数据信号可以采用多种形式,包括但不限于电磁信号、光信号或上述的任意合适的组合。可读信号介质还可以是可读存储介质以外的任何可读介质,该可读介质可以发送、传播或者传输用于由指令执行系统、装置或者器件使用或者与其结合使用的程序。
可读介质上包含的程序代码可以用任何适当的介质传输,包括但不限于无线、有线、光缆、RF等等,或者上述的任意合适的组合。
可以以一种或多种程序设计语言的任意组合来编写用于执行本发明操作的程序代码,所述程序设计语言包括面向对象的程序设计语言—诸如Java、C++等,还包括常规的过程式程序设计语言—诸如“C”语言或类似的程序设计语言。程序代码可以完全地在客户计算设备上执行、部分地在客户设备上执行、作为一个独立的软件包执行、部分在客户计算设备上部分在远程计算设备上执行、或者完全在远程计算设备或服务器上执行。在涉及远程计算设备的情形中,远程计算设备可以通过任意种类的网络,包括局域网(LAN)或广域网(WAN),连接到客户计算设备,或者,可以连接到外部计算设备(例如利用因特网服务提供商来通过因特网连接)。
此外,上述附图仅是根据本发明示例性实施例的方法所包括的处理的示意性说明,而不是限制目的。易于理解,上述附图所示的处理并不表明或限制这些处理的时间顺序。另外,也易于理解,这些处理可以是例如在多个模块中同步或异步执行的。
本领域技术人员在考虑说明书及实践这里公开的发明后,将容易想到本申请的其他实施例。本申请旨在涵盖本申请的任何变型、用途或者适应性变化,这些变型、用途或者适应性变化遵循本申请的一般性原理并包括本申请未公开的本技术领域中的公知常识或惯用技术手段。说明书和实施例仅被视为示例性的,本申请的真正范围和精神由权利要求指出。
Claims (20)
- 一种基于区块链网络的资源请求交易方法,其中,所述区块链网络包括资源交易各方的背书节点、账本节点、排序节点及与各所述节点连接的资源交易各方的业务终端,所述方法由资源请求方的业务终端执行,所述方法包括:缓存资源请求订单的标识,所述资源请求订单为资源请求方通过业务系统向业务关联方发送的资源请求订单,所述资源请求订单依次在各业务关联方之间流转;定期利用资源请求订单的标识向各所述业务关联方的背书节点发起背书提议,以接收业务关联方的背书节点根据订单流转情况返回的背书提议结果,直到得到所有业务关联方的背书节点返回的背书提议结果;将基于所述资源请求订单的交易相关数据封装为交易账本记录信息后,提交到资源请求方的排序节点进行排序得到模拟交易数据块,以使得所述资源交易各方的背书节点利用所述模拟交易数据块进行交易验证,并在验证通过后,分别将所述交易相关数据保存至资源交易各方的所述账本节点。
- 根据权利要求1所述的方法,其中,所述缓存资源请求订单的标识,包括:将所述资源请求订单的标识缓存于延时队列的订单列表,所述延时队列设置了对应于不同业务关联方的背书提议延时时间。
- 根据权利要求2所述的方法,其中,所述定期利用资源请求订单的标识向各所述业务关联方的背书节点发起背书提议,以缓存业务关联方的背书节点根据订单流转情况返回的背书提议结果,包括:所述延时队列定期扫描所述订单列表,以在所述订单列表不为空时,将所述订单列表中的标识封装成背书提议的参数,根据各所述业务关联方对应的延时时间向各所述业务关联方的背书节点发起背书提议。
- 根据权利要求1所述的方法,其中,所述方法还包括:业务关联方在接收到所述资源请求订单后,基于所述资源请求订单进行资源交易处理,得到处理结果;如果所述处理结果为处理成功时,将资源交易处理的交易记录保存至所述业务关联方的账本节点,所述交易记录包括所述资源请求订单的标识。
- 根据权利要求4所述的方法,其中,所述业务关联方的背书节点根据订单流转情况返回的背书提议结果,包括:业务关联方的背书节点查询所述业务关联方的账本节点的最后一条交易记录,如果该交易记录中的资源请求订单的标识和所述背书提议中的资源请求订单的标识一致,则返回处理成功的第一背书提议结果;如果该交易记录中的资源请求订单的标识和所述背书提议中的资源请求订单的标识不一致,则回调所述业务系统查询基于所述资源请求订单进行资源交易处理状态,得到第二背书提议结果进行返回。
- 根据权利要求5所述的方法,其中,所述第二背书提议结果,包括:尚未收到订单信息、收到订单信息但业务系统验证异常或处理异常、业务系统响应成功及业务系统没有响应做超时处理中一种。
- 根据权利要求1所述的方法,其中,所述资源交易各方的背书节点利用所述模拟交易数据块进行交易验证,并在验证通过后,分别将所述交易相关数据保存至资源交易各方的所述账本节点,包括:所述资源交易各方的背书节点,根据所述模拟交易数据块及各所述业务关联方的背书节点返回的背书提议结果进行交易验证,得到所述资源交易各方的验证结果;当所述资源交易各方的验证结果都为验证通过时,所述资源交易各方分别将所述交易相关数据保存至资源交易各方的所述账本节点。
- 一种基于区块链网络的资源请求交易装置,其中,所述区块链网络包括资源交易各方的背书节点、账本节点、排序节点及与各所述节点连接的资源交易各方的业务终端,所述装置位于所述资源请求方的业务终端,所述装置包括:缓存模块,用于缓存资源请求订单的标识,所述资源请求订单为资源请求方通过业务系统向业务关联方发送的资源请求订单,所述资源请求订单依次在各业务关联方之间流转;提议模块,用于定期利用资源请求订单的标识向各所述业务关联方的背书节点发起背书提议,以接收业务关联方的背书节点根据订单流转情况返回的背书提议结果,直到得到所有业务关联方的背书节点返回的背书提议结果;验证模块,用于将基于所述资源请求订单的交易相关数据封装为交易账本记录信息后,提交到资源请求方的排序节点进行排序得到模拟交易数据块,以使得所述资源交易各方的背书节点利用所述模拟交易数据块进行交易验证,并在验证通过后,分别将所述交易相关数据保存至资源交易各方的所述账本节点。
- 一种电子设备,其与区块链网络中包括的资源交易各方的背书节点、账本节点、排序节点连接,该电子设备包括:处理器;以及存储器,用于存储所述处理器的计算机可读指令;其中,所述处理器配置为经由执行所述计算机可读指令来执行以下方法:缓存资源请求订单的标识,所述资源请求订单为资源请求方通过业务系统向业务关联方发送的资源请求订单,所述资源请求订单依次在各业务关联方之间流转;定期利用资源请求订单的标识向各所述业务关联方的背书节点发起背书提议,以接收业务关联方的背书节点根据订单流转情况返回的背书提议结果,直到得到所有业务关联方的背书节点返回的背书提议结果;将基于所述资源请求订单的交易相关数据封装为交易账本记录信息后,提交到资源请求方的排序节点进行排序得到模拟交易数据块,以使得所述资源交易各方的背书节点利用所述模拟交易数据块进行交易验证,并在验证通过后,分别将所述交易相关数据保存至资源交易各方的所述账本节点。
- 根据权利要求9所述的电子设备,其中,所述缓存资源请求订单的标识,包括:将所述资源请求订单的标识缓存于延时队列的订单列表,所述延时队列设置了对应于不同业务关联方的背书提议延时时间。
- 根据权利要求10所述的电子设备,其中,所述定期利用资源请求订单的标识向各所述业务关联方的背书节点发起背书提议,以缓存业务关联方的背书节点根据订单流转情况返回的背书提议结果,包括:所述延时队列定期扫描所述订单列表,以在所述订单列表不为空时,将所述订单列表中的标识封装成背书提议的参数,根据各所述业务关联方对应的延时时间向各所述业务关联方的背书节点发起背书提议。
- 根据权利要求9所述的电子设备,其中,所述方法还包括:业务关联方在接收到所述资源请求订单后,基于所述资源请求订单进行资源交易处理,得到处理结果;如果所述处理结果为处理成功时,将资源交易处理的交易记录保存至所述业务关联方的账本节点,所述交易记录包括所述资源请求订单的标识。
- 根据权利要求12所述的电子设备,其中,所述业务关联方的背书节点根据订单流转情况返回的背书提议结果,包括:业务关联方的背书节点查询所述业务关联方的账本节点的最后一条交易记录,如果该交易记录中的资源请求订单的标识和所述背书提议中的资源请求订单的标识一致,则返回处理成功的第一背书提议结果;如果该交易记录中的资源请求订单的标识和所述背书提议中的资源请求订单的标识不一致,则回调所述业务系统查询基于所述资源请求订单进行资源交易处理状态,得到第二背书提议结果进行返回。
- 根据权利要求13所述的电子设备,其中,所述第二背书提议结果,包括:尚未收到订单信息、收到订单信息但业务系统验证异常或处理异常、业务系统响应成功及业务系统没有响应做超时处理中一种。
- 根据权利要求9所述的电子设备,其中,所述资源交易各方的背书节点利用所述模拟交易数据块进行交易验证,并在验证通过后,分别将所述交易相关数据保存至资源交易各方的所述账本节点,包括:所述资源交易各方的背书节点,根据所述模拟交易数据块及各所述业务关联方的背书节点返回的背书提议结果进行交易验证,得到所述资源交易各方的验证结果;当所述资源交易各方的验证结果都为验证通过时,所述资源交易各方分别将所述交易相关数据保存至资源交易各方的所述账本节点。
- 一种计算机可读存储介质,其上存储有计算机可读指令,其中,所述计算机可读指令被处理器执行时执行以下方法:缓存资源请求订单的标识,所述资源请求订单为资源请求方通过业务系统向业务关联方发送的资源请求订单,所述资源请求订单依次在各业务关联方之间流转;定期利用资源请求订单的标识向各所述业务关联方的背书节点发起背书提议,以接收业务关联方的背书节点根据订单流转情况返回的背书提议结果,直到得到所有业务关联方的背书节点返回的背书提议结果;将基于所述资源请求订单的交易相关数据封装为交易账本记录信息后,提交到资源请求方的排序节点进行排序得到模拟交易数据块,以使得所述资源交易各方的背书节点利用所述模拟交易数据块进行交易验证,并在验证通过后,分别将所述交易相关数据保存至资源交易各方的所述账本节点。
- 根据权利要求16所述的计算机可读存储介质,其中,所述缓存资源请求订单的标识,包括:将所述资源请求订单的标识缓存于延时队列的订单列表,所述延时队列设置了对应于不同业务关联方的背书提议延时时间。
- 根据权利要求17所述的计算机可读存储介质,其中,所述定期利用资源请求订单的标识向各所述业务关联方的背书节点发起背书提议,以缓存业务关联方的背书节点根据订单流转情况返回的背书提议结果,包括:所述延时队列定期扫描所述订单列表,以在所述订单列表不为空时,将所述订单列表中的标识封装成背书提议的参数,根据各所述业务关联方对应的延时时间向各所述业务关联方的背书节点发起背书提议。
- 根据权利要求16所述的计算机可读存储介质,其中,所述方法还包括:业务关联方在接收到所述资源请求订单后,基于所述资源请求订单进行资源交易处理,得到处理结果;如果所述处理结果为处理成功时,将资源交易处理的交易记录保存至所述业务关联方的账本节点,所述交易记录包括所述资源请求订单的标识。
- 根据权利要求19所述的计算机可读存储介质,其中,所述业务关联方的背书节点根据订单流转情况返回的背书提议结果,包括:业务关联方的背书节点查询所述业务关联方的账本节点的最后一条交易记录,如果该交易记录中的资源请求订单的标识和所述背书提议中的资源请求订单的标识一致,则返回处理成功的第一背书提议结果;如果该交易记录中的资源请求订单的标识和所述背书提议中的资源请求订单的标识不一致,则回调所述业务系统查询基于所述资源请求订单进行资源交易处理状态,得到第二背书提议结果进行返回。
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202010349691.1A CN111598650A (zh) | 2020-04-28 | 2020-04-28 | 基于区块链网络的资源请求交易方法及相关装置 |
CN202010349691.1 | 2020-04-28 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2021217928A1 true WO2021217928A1 (zh) | 2021-11-04 |
Family
ID=72183822
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2020/105545 WO2021217928A1 (zh) | 2020-04-28 | 2020-07-29 | 基于区块链网络的资源请求交易验证方法、装置、电子设备及计算机可读存储介质 |
Country Status (2)
Country | Link |
---|---|
CN (1) | CN111598650A (zh) |
WO (1) | WO2021217928A1 (zh) |
Cited By (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN114331440A (zh) * | 2021-12-31 | 2022-04-12 | 北京江融信科技有限公司 | 一种冲突检测及性能优化方法和装置 |
CN114418695A (zh) * | 2022-01-20 | 2022-04-29 | 中国工商银行股份有限公司 | 基于区块链网络的订单处理方法、装置、设备及介质 |
CN116029829A (zh) * | 2023-03-30 | 2023-04-28 | 中国信息通信研究院 | 基于工业互联网的交易系统、设备和介质 |
CN116128641A (zh) * | 2022-12-07 | 2023-05-16 | 申万宏源证券有限公司 | 一种竞价交易与非竞价交易分离的分布式证券交易系统 |
WO2023142226A1 (en) * | 2022-01-28 | 2023-08-03 | Hong Kong Applied Science and Technology Research Institute Company Limited | Method and apparatus for exchanging data between blockchain system and non-blockchain system |
CN116775772A (zh) * | 2022-03-10 | 2023-09-19 | 腾讯科技(深圳)有限公司 | 一种数据处理方法、装置、设备及可读存储介质 |
Families Citing this family (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN112199732B (zh) * | 2020-09-01 | 2024-04-05 | 东方航空物流股份有限公司 | 一种基于区块链的航空物流电子运单管理方法 |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN108256864A (zh) * | 2018-02-13 | 2018-07-06 | 中链科技有限公司 | 一种区块链之间的跨链联盟的建立及通信方法、系统 |
CN108376368A (zh) * | 2018-03-07 | 2018-08-07 | 物数(上海)信息科技有限公司 | 背书策略确定方法、装置、电子设备、存储介质 |
CN108595126A (zh) * | 2018-04-27 | 2018-09-28 | 腾讯科技(深圳)有限公司 | 数据存储系统、查询方法、查询装置、服务器及存储介质 |
CN108810137A (zh) * | 2018-06-11 | 2018-11-13 | 西安纸贵互联网科技有限公司 | 一种联盟区块链系统 |
CN108833081A (zh) * | 2018-06-22 | 2018-11-16 | 中国人民解放军国防科技大学 | 一种基于区块链的设备组网认证方法 |
Family Cites Families (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US11188920B2 (en) * | 2018-05-23 | 2021-11-30 | International Business Machines Corporation | Autocommit transaction management in a blockchain network |
US11521202B2 (en) * | 2018-08-30 | 2022-12-06 | International Business Machines Corporation | Distributed computing and storage network implementing high integrity, high bandwidth, low latency, secure processing |
CN109493204B (zh) * | 2018-10-16 | 2023-04-18 | 平安科技(深圳)有限公司 | 基于区块链的业务记账方法及终端设备 |
CN110555769A (zh) * | 2019-07-25 | 2019-12-10 | 深圳壹账通智能科技有限公司 | 区块链交易数据处理方法、装置、计算机设备和存储介质 |
CN111046037A (zh) * | 2019-11-18 | 2020-04-21 | 远光软件股份有限公司 | 区块链的交易处理方法、电子设备和存储介质 |
-
2020
- 2020-04-28 CN CN202010349691.1A patent/CN111598650A/zh active Pending
- 2020-07-29 WO PCT/CN2020/105545 patent/WO2021217928A1/zh active Application Filing
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN108256864A (zh) * | 2018-02-13 | 2018-07-06 | 中链科技有限公司 | 一种区块链之间的跨链联盟的建立及通信方法、系统 |
CN108376368A (zh) * | 2018-03-07 | 2018-08-07 | 物数(上海)信息科技有限公司 | 背书策略确定方法、装置、电子设备、存储介质 |
CN108595126A (zh) * | 2018-04-27 | 2018-09-28 | 腾讯科技(深圳)有限公司 | 数据存储系统、查询方法、查询装置、服务器及存储介质 |
CN108810137A (zh) * | 2018-06-11 | 2018-11-13 | 西安纸贵互联网科技有限公司 | 一种联盟区块链系统 |
CN108833081A (zh) * | 2018-06-22 | 2018-11-16 | 中国人民解放军国防科技大学 | 一种基于区块链的设备组网认证方法 |
Cited By (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN114331440A (zh) * | 2021-12-31 | 2022-04-12 | 北京江融信科技有限公司 | 一种冲突检测及性能优化方法和装置 |
CN114418695A (zh) * | 2022-01-20 | 2022-04-29 | 中国工商银行股份有限公司 | 基于区块链网络的订单处理方法、装置、设备及介质 |
WO2023142226A1 (en) * | 2022-01-28 | 2023-08-03 | Hong Kong Applied Science and Technology Research Institute Company Limited | Method and apparatus for exchanging data between blockchain system and non-blockchain system |
US11789937B2 (en) | 2022-01-28 | 2023-10-17 | Hong Kong Applied Science and Technology Research Institute Company Limited | Method and apparatus for exchanging data between blockchain system and non-blockchain system |
CN116775772A (zh) * | 2022-03-10 | 2023-09-19 | 腾讯科技(深圳)有限公司 | 一种数据处理方法、装置、设备及可读存储介质 |
CN116128641A (zh) * | 2022-12-07 | 2023-05-16 | 申万宏源证券有限公司 | 一种竞价交易与非竞价交易分离的分布式证券交易系统 |
CN116128641B (zh) * | 2022-12-07 | 2023-10-17 | 申万宏源证券有限公司 | 一种竞价交易与非竞价交易分离的分布式证券交易系统 |
CN116029829A (zh) * | 2023-03-30 | 2023-04-28 | 中国信息通信研究院 | 基于工业互联网的交易系统、设备和介质 |
Also Published As
Publication number | Publication date |
---|---|
CN111598650A (zh) | 2020-08-28 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2021217928A1 (zh) | 基于区块链网络的资源请求交易验证方法、装置、电子设备及计算机可读存储介质 | |
CN111176858A (zh) | 一种数据请求处理方法及装置 | |
US20230052935A1 (en) | Asynchronous accounting method and apparatus for blockchain, medium and electronic device | |
CN113793139B (zh) | 支付异常的处理方法、处理装置、存储介质及电子设备 | |
WO2023207146A1 (zh) | Esop系统的服务模拟方法、装置、设备及存储介质 | |
US11997216B2 (en) | Systems and methods for maintaining secure, encrypted communications across distributed computer networks by linking cryptography-based digital repositories in order to perform blockchain operations in decentralized applications | |
US20230306128A1 (en) | Systems and methods for using secure, encrypted communications across distributed computer networks to provide variable resiliency when indexing blockchain states for performing blockchain operations in decentralized applications using cryptography-based digital repositories | |
US20250106053A1 (en) | Blockchain Network Management Method and Related Device | |
US11093309B1 (en) | Communication hub for information technology (IT) services | |
KR102680150B1 (ko) | 거래 시스템을 구현하는 네트워크 노드들의 서브세트 내의 컨텍스트 기반 필터링 | |
CN111694620A (zh) | 第三方业务的交互方法、装置、设备及计算机存储介质 | |
WO2023193572A1 (zh) | 一种数据管理方法、装置、服务器和存储介质 | |
CN113992352B (zh) | 一种消息推送方法、装置、电子设备及存储介质 | |
US20230267430A1 (en) | Data processing method and device, and computer-readable storage medium | |
US12244722B2 (en) | Systems and methods for selecting secure, encrypted communications across distributed computer networks for cryptography-based digital repositories in order to perform blockchain operations in decentralized | |
US12219068B2 (en) | Systems and methods for using secure, encrypted communications across distributed computer networks to efficiently index blockchain states for performing blockchain operations in decentralized applications using cryptography-based digital repositories | |
US12206788B2 (en) | Systems and methods for using secure, encrypted communications across distributed computer networks to efficiently update cryptography-based digital repositories for performing blockchain operations in decentralized applications | |
CN114881789A (zh) | 手机银行碳交易方法及装置 | |
CN116185806A (zh) | 一种数字货币系统的测试方法和装置 | |
CN111737262A (zh) | 一种数据处理方法及装置 | |
US20240104558A1 (en) | Blockchain transaction execution method and apparatus, program product, device, and medium | |
CN111159585A (zh) | 自动提交数据的方法、装置、设备及介质 | |
CN117667024A (zh) | 一种业务处理方法、装置及电子设备 | |
US20230082711A1 (en) | Efficient initiation of automated processes | |
CN116996532A (zh) | 基于区块链的虚拟资源交易方法、装置、设备和可读介质 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 20933999 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
32PN | Ep: public notification in the ep bulletin as address of the adressee cannot be established |
Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 16.02.2023) |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 20933999 Country of ref document: EP Kind code of ref document: A1 |