WO2021073096A1 - 资源数据的转移方法、装置和区块链*** - Google Patents

资源数据的转移方法、装置和区块链*** Download PDF

Info

Publication number
WO2021073096A1
WO2021073096A1 PCT/CN2020/092029 CN2020092029W WO2021073096A1 WO 2021073096 A1 WO2021073096 A1 WO 2021073096A1 CN 2020092029 W CN2020092029 W CN 2020092029W WO 2021073096 A1 WO2021073096 A1 WO 2021073096A1
Authority
WO
WIPO (PCT)
Prior art keywords
resource data
transfer
node
processed
blockchain system
Prior art date
Application number
PCT/CN2020/092029
Other languages
English (en)
French (fr)
Inventor
冷从林
王知博
Original Assignee
京东数字科技控股有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 京东数字科技控股有限公司 filed Critical 京东数字科技控股有限公司
Publication of WO2021073096A1 publication Critical patent/WO2021073096A1/zh

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
    • G06F9/5005—Allocation of resources, e.g. of the central processing unit [CPU] to service a request
    • G06F9/5027—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals

Definitions

  • the present disclosure relates to the field of data processing technology, and in particular to a method for transferring resource data, a device for transferring resource data, a blockchain system, and a computer-readable storage medium.
  • resource data transfer between users can be realized. For example, it can realize the transfer of network resources such as traffic resources and bandwidth resources among Internet users; or realize the transfer of system resources such as computing resources and storage resources among users of cloud systems or computer clusters.
  • resource data exchange the exchange of resources between users can also be realized.
  • user A can use its own traffic resources in exchange for user B's bandwidth resources
  • user B can use its own bandwidth resources in exchange for user C's traffic resources, etc., thereby forming a resource data containing users A, B, C and other multi-level resource supply users supply chain.
  • each user in the resource data supply chain directly transfers resources.
  • the inventors of the present disclosure have discovered that the above-mentioned related technologies have the following problems: the resource transfer process is easily tampered, resulting in poor reliability of the system; once the resource data is transferred, it cannot be withdrawn, resulting in poor flexibility of the system.
  • the present disclosure proposes a technical solution for resource data transfer, which can improve the reliability and flexibility of the system.
  • a method for transferring resource data including: in response to a resource data transfer request of an initiating node in a blockchain system, transferring the resource data to be processed corresponding to the resource data transfer request The transfer node of the blockchain system; generate transfer information corresponding to this transfer process, and store it in the blockchain system, and the transfer information includes the information of the initiating node during this transfer process, the The information of the designated receiving node of the resource data to be processed; according to the resource data processing request corresponding to the resource data transfer request issued by the initiating node or the current receiving node, and the transfer obtained from the blockchain system Information to determine whether to transfer the to-be-processed resource data in the transit node.
  • the corresponding resource data processing request is a transfer cancellation request issued by the initiating node or a sign rejection request issued by the designated receiving node.
  • the determining whether to transfer the to-be-processed resource data in the transit node includes: in response to a transfer cancellation request of the initiating node or a sign rejection request of the designated receiving node, transferring all The resource data to be processed is returned to the initiating node; the corresponding return information is stored in the blockchain system.
  • the determining whether to transfer the to-be-processed resource data in the transit node includes: in response to a transfer cancellation request of the initiating node or a sign rejection request of the designated receiving node, transferring all The state of the resource data to be processed is configured as a normal state, and in the normal state, the resource data to be processed can be transferred to a node other than the designated receiving node.
  • the determining whether to transfer the to-be-processed resource data in the transit node includes: in response to a resource data signing request initiated by the current receiving node in the blockchain system, transferring the to-be-processed resource data The processing resource data is transferred to the current receiving node; the transfer information corresponding to this transfer process is generated and stored in the blockchain system.
  • the determining whether to transfer the to-be-processed resource data in the transit node includes: configuring the state of the to-be-processed resource data as a locked state according to the transit information, and In the locked state, the resource data to be processed can only be transferred to the designated receiving node; in response to the resource data signing request initiated by the current receiving node in the blockchain system, according to the designated receiving node in the transfer information The information of the node determines whether to transfer the corresponding resource data to the receiving node.
  • the resource data to be processed of each initiating node is multiple batches; the generating transfer information corresponding to this transfer process and storing in the blockchain system includes: Each batch of resource data to be processed received by the transit node from each initiating node is determined as each input resource data for this transfer process; each batch of corresponding resource data transferred from the transit node to the current receiving node is determined as the original The output resource data of the second transfer process, the output resource data are respectively derived from the corresponding input resource data; the corresponding output resource data of the input resource data with the same initiation node are merged into a batch of comprehensive output resource data ; According to the relevant information of each comprehensive output resource data, the transfer information corresponding to this transfer process is generated and stored in the blockchain system.
  • the transferring to-be-processed resource data to the transfer node of the blockchain system includes: obtaining the transfer of resource data from other nodes during the historical resource data transfer process of the initiating node Quantity and type; merge the transfer-in resource data from the same other nodes and the same type to generate comprehensive transfer-in resource data; obtain the transfer-out resource data that the initiating node intends to transfer to the transfer node during this transfer process
  • the number and type of the resource data to be processed are merged; the resource data to be processed is generated by combining the exported resource data of the same type; when the number and type of the integrated resource data to be processed are the same as the number and type of resource data to be processed, Transfer the to-be-processed resource data to the transfer node of the blockchain system.
  • a device for transferring resource data including: a transfer unit for transferring to-be-processed resource data to the zone in response to a resource data transfer request of an initiating node in a blockchain system The transfer node of the blockchain system; a storage unit, used to generate transfer information corresponding to this transfer process, and store it in the blockchain system.
  • the transfer information includes the information of the initiating node during this transfer process, The information of the designated receiving node of the resource data to be processed; the transfer unit is used to process the resource data request corresponding to the resource data transfer request issued by the initiating node or the current receiving node, and from the blockchain
  • the transfer information acquired in the system determines whether to transfer the to-be-processed resource data in the transfer node.
  • the storage unit generates transfer information corresponding to this transfer process according to the relevant information of each comprehensive output resource data , Stored in the blockchain system.
  • the transfer device further includes a merging unit for determining each batch of resource data to be processed received by the transit node from each initiating node as input resource data for the current transfer process, and combining all the resource data
  • a merging unit for determining each batch of resource data to be processed received by the transit node from each initiating node as input resource data for the current transfer process, and combining all the resource data
  • Each batch of corresponding resource data transferred from the transfer node to the current receiving node is determined as each output resource data of the current transfer process, and each output resource data is derived from the corresponding input resource data and will have the same initiating node
  • the corresponding output resource data of each input resource data of are merged into a batch of comprehensive output resource data.
  • the transfer device further includes a merging unit for obtaining the quantity and type of each transferred-in resource data from other nodes in the historical resource data transfer process of the initiating node, and the merged source is the same Transfer-in resource data of other nodes with the same type, generate comprehensive transfer-in resource data, and obtain the quantity and type of the transfer-out resource data that the initiating node intends to transfer to the transfer node during this transfer process, and the merge type is the same
  • the transfer unit When the number and type of the integrated transfer-in resource data are the same as the number and type of the resource data to be processed, the transfer unit generates the to-be-processed resource data; The processing resource data is transferred to the transit node of the blockchain system.
  • the transfer unit returns the to-be-processed resource data to the initiating node in response to the transfer request of the initiating node or the rejection request of the designated receiving node; the storage unit will respond accordingly
  • the return information of is stored in the blockchain system.
  • the transfer unit configures the state of the resource data to be processed as a normal state in response to the transfer request of the initiating node or the rejection request of the designated receiving node.
  • the resource data to be processed may be transferred to a node other than the designated receiving node.
  • the transfer unit transfers the to-be-processed resource data to the current receiving node in response to a resource data signing request initiated by the current receiving node in the blockchain system; the storage unit generates and The corresponding transfer information of this transfer process is stored in the blockchain system.
  • the transfer unit configures the state of the resource data to be processed as a locked state according to the transfer information.
  • the resource data to be processed can only be transferred to the designated Receiving node; in response to a resource data signing request initiated by the current receiving node in the blockchain system, determine whether to transfer corresponding resource data to the receiving node according to the information of the designated receiving node in the transfer information.
  • an apparatus for transferring resource data including: a memory; and a processor coupled to the memory, and the processor is configured to be based on instructions stored in the memory, Execute the resource data transfer method in any of the above embodiments.
  • a computer-readable storage medium on which a computer program is stored, and when the program is executed by a processor, the method for transferring resource data in any of the above embodiments is realized.
  • a blockchain system including: the resource data transfer device in any of the above embodiments.
  • the initiator and receiver of the resource transfer are configured as nodes of the blockchain system, and the non-tamperable feature of the blockchain is used to record the resource conversion process, thereby improving the reliability of the system;
  • Figure 1 shows a flowchart of some embodiments of the resource data transfer method of the present disclosure
  • FIG. 2 shows a flowchart of some embodiments of step S10 in FIG. 1;
  • Figure 3 shows a schematic diagram of some embodiments of the resource data transfer method of the present disclosure
  • FIG. 4a shows a flowchart of some embodiments of step S30 in FIG. 1;
  • FIG. 4b shows a flowchart of other embodiments of step S30 in FIG. 1;
  • FIG. 4c shows a flowchart of still other embodiments of step S30 in FIG. 1;
  • Figure 5 shows a flowchart of other embodiments of the resource data transfer method of the present disclosure
  • Fig. 6 shows a schematic diagram of other embodiments of the resource data transfer method of the present disclosure
  • FIG. 7 shows a schematic diagram of still other embodiments of the resource data transfer method of the present disclosure.
  • FIG. 8 shows a flowchart of still other embodiments of the resource data transfer method of the present disclosure.
  • FIG. 9 shows a flowchart of some embodiments of the resource data uploading method of the present disclosure.
  • FIG. 10 shows a flowchart of some embodiments of the resource data transfer method of the present disclosure
  • FIG. 11 shows a flowchart of other embodiments of the resource data transfer method of the present disclosure.
  • FIG. 12 shows a flowchart of some embodiments of the resource data return method of the present disclosure
  • Figure 13 shows a flowchart of some embodiments of the resource data signing method of the present disclosure
  • FIG. 14 shows a block diagram of some embodiments of the resource data transfer device of the present disclosure
  • FIG. 15 shows a block diagram of other embodiments of the resource data transfer device of the present disclosure.
  • FIG. 16 shows a block diagram of still other embodiments of the resource data transfer device of the present disclosure.
  • Figure 17 shows a block diagram of some embodiments of the blockchain system of the present disclosure.
  • FIG. 1 shows a flowchart of some embodiments of the resource data transfer method of the present disclosure.
  • the method includes: step S10, the resource is transferred to a transit node; step S20, the transfer information is generated and stored; and step S30, it is determined whether to transfer the resource.
  • step S10 in response to the resource data transfer request of the initiating node in the blockchain system, the resource data to be processed is transferred to the transfer node of the blockchain system. For example, storing the to-be-processed resource data in the transit node, or transferring it to the transit node name.
  • the initiating node may be a network user, a cloud system or computing cluster user, an enterprise, a supplier at all levels, and so on.
  • resource data can be network resources such as traffic resources and bandwidth resources of network users, or system resources such as computing resources and storage resources of users of cloud systems or computing clusters, or the funds and assets of enterprises and suppliers at all levels. And other financial resources.
  • the resource data of the initiating node is transferred to the transit node by invoking the smart contract of the blockchain system.
  • the transit node may be a physical node or a non-physical node implemented by software.
  • the transit node may be an intermediate account that the initiating node and the receiving node jointly hold the private key to unlock.
  • the transfer process will be recorded in the blockchain system, and blocks will be packaged by the blockchain system.
  • step S10 may be performed through the embodiment in FIG. 2.
  • FIG. 2 shows a flowchart of some embodiments of step S10 in FIG. 1.
  • step S10 may include: step S110, obtaining the quantity and type of transferred resource data; step S120, combining the transferred resource data; step S130, obtaining the quantity and type of transferred resource data; step S140, combining Transfer the resource data; and step S150, transfer the resource data to be processed.
  • step S110 the quantity and type of each transferred resource data from other nodes in the historical resource data transfer process of the initiating node are obtained.
  • the transfer process model can be established according to the UTXO (Unspent Transaction Output) model.
  • each transfer process (or transfer process) includes at least one batch of resource data inputs (inputs) used to represent the resource data obtained before this transfer, and at least one batch of resource data from each input Output is used to represent the resource data transferred out during this transfer process.
  • the embodiment in FIG. 3 can be used to establish a transfer process model.
  • Fig. 3 shows a schematic diagram of some embodiments of the resource data transfer method of the present disclosure.
  • resource data transfer 1 As shown in Figure 3, according to the UTXO model, there are two models of resource data transfer process: resource data transfer 1 and resource data transfer 2.
  • the transfer process represented by resource data transfer 1 is that node A transfers resource data to node B and node C.
  • INPUT 11 identifies the resource data transferred by node A during the last transfer process;
  • OUTPUT 12 and OUTPUT 13 both originate from INPUT 11, and
  • OUTPUT 12 and OUTPUT 13 identify the resource data transferred from node A to node B and node C, respectively.
  • Resource data transfer 2 represents the transfer process for node B to transfer resource data to node D and node E.
  • INPUT 21 identifies the resource data transferred from node A by node B during the transfer process indicated by resource data transfer 1 (that is, from OUTPUT12);
  • INPUT 22, INPUT 23 identify the resource data transferred by node B in the last transfer process;
  • Both OUTPUT 24 and OUTPUT 25 are derived from INPUT 21, INPUT 22, or INPUT 23, and OUTPUT 24 and OUTPUT 25 identify the resource data transferred from node B to node D and node E, respectively.
  • step S120 the transfer-in resource data from the same other nodes and the same type are merged to generate comprehensive transfer-in resource data.
  • the type of resource data may be traffic resources, bandwidth resources, computing resources, storage resources, various types of capital resources, and so on.
  • step S130 the quantity and type of the transfer-out resource data that the initiating node intends to transfer to the transfer node during this transfer process are obtained.
  • step S140 the exported resource data of the same type are merged to generate resource data to be processed.
  • step S150 when the quantity and type of the comprehensively transferred resource data are the same as the quantity and type of the resource data to be processed, the resource data to be processed is transferred to the transfer node of the blockchain system. In the case of different quantities or types, you can report an error or prompt that the transfer cannot be carried out.
  • step S20 the transfer information corresponding to this transfer process is generated and stored in the blockchain system.
  • the transfer information includes the information of the initiating node during this transfer process and the information of the designated receiving node of the resource data to be processed.
  • step S30 according to the resource data processing request corresponding to the resource data transfer request issued by the initiating node or the current receiving node, and the transfer information obtained from the blockchain system, it is determined whether to transfer the resource to be processed in the transfer node Data is transferred.
  • the resource data processing request corresponding to the resource data transfer request may be a transfer cancellation instruction issued by the initiating node, a sign rejection request or a receipt request issued by the receiving node.
  • step S30 may be performed by the embodiment in FIG. 4a, FIG. 4b, or FIG. 4c.
  • Fig. 4a shows a flowchart of some embodiments of step S30 in Fig. 1.
  • step S30 may include: step S310a, the resource returning to the initiating node; and step S320a, storing the return information.
  • step S310a in response to the transfer cancellation request of the initiating node or the sign rejection request of the designated receiving node, the to-be-processed resource data is returned to the initiating node.
  • the state of the resource data to be processed in response to the transfer request of the initiating node or the sign-off request of the designated receiving node, is configured as a normal state. In the normal state, the resource data to be processed can be transferred to a node other than the designated receiving node.
  • step S320a the corresponding return information is stored in the blockchain system.
  • Fig. 4b shows a flowchart of other embodiments of step S30 in Fig. 1.
  • step S30 may include: step S310b, the resource is transferred to the receiving node; and step S320b, the transfer information is stored.
  • step S310b in response to the resource data signing request initiated by the receiving node in the blockchain system, the resource data to be processed is transferred to the receiving node.
  • step S320b the transfer information corresponding to this transfer process is generated and stored in the blockchain system.
  • Fig. 4c shows a flowchart of still other embodiments of step S30 in Fig. 1.
  • step S30 may include: step S310c, configuring the locked state; and step S320c, determining whether to perform resource transfer.
  • step S310c according to the transfer information, the state of the resource data to be processed is configured as a locked state.
  • the locked state the resource data to be processed can only be transferred to the designated receiving node.
  • step S320c in response to the resource data signing request initiated by the receiving node in the blockchain system, it is determined whether to transfer the corresponding resource data to the receiving node according to the information of the designated receiving node in the transfer information.
  • the to-be-processed resource data of each initiating node is multiple batches.
  • the transfer information can be stored in the blockchain system through the embodiment in FIG. 5.
  • Fig. 5 shows a flowchart of other embodiments of the resource data transfer method of the present disclosure.
  • the method further includes: step S51, determining input resource data; step S52, determining output resource data; step S53, combining into comprehensive output resource data; and step S54, Store transfer information.
  • step S51 each batch of to-be-processed resource data received by the transit node from each initiating node is determined as each input resource data of the current transfer process.
  • each batch of corresponding resource data of the receiving node to which the transit node is transferred is determined as each output resource data of the current transfer process.
  • Each output resource data is derived from the corresponding input resource data.
  • step S53 the corresponding output resource data of each input resource data having the same originating node are merged into a batch of comprehensive output resource data.
  • the transfer information corresponding to this transfer process is generated and stored in the blockchain system.
  • the transfer information may include: information of the initiating node of each batch of resource data to be processed, information of the designated receiving node of each batch of resource data to be processed, information of the current receiving node of each batch of resource data to be processed, and so on.
  • a pre field may be set for both input and output during the transfer process, which is used to identify the source node of the input and output during the last conversion process. In this way, outputs from the same source can be merged according to the pre field. You can also set the prepare field to identify the source node of input and output during the last two conversions.
  • the embodiment in FIG. 6 can be used to implement resource data merging.
  • Fig. 6 shows a schematic diagram of other embodiments of the resource data transfer method of the present disclosure.
  • the transfer process is for node A to transfer resource data to node B and node C.
  • INPUT 61-INPUT 66 are all resource data transferred by node A during the historical transfer process. INPUT 61-INPUT 66 are set with a pre field and a prepre field to respectively identify the last transfer source node and the last two transfer source nodes of the corresponding INPUT (such as nodes D, E, R, etc.).
  • OUTPUT 67-OUTPUT 69 is the resource data transferred out to node B or C. Both OUTPUT 67-OUTPUT 69 are provided with a pre field and a prepre field to respectively identify the last transfer source node and the last two transfer source nodes of the corresponding OUTPUT.
  • the corresponding OUTPUT can be merged. For example, if INPUT 61-INPUT 63 all originate from node D, then its corresponding OUTPUT can be merged into OUTPUT67; INPUT 64-INPUT 65 all originate from node E, then its corresponding OUTPUT can be merged into OUTPUT 68; only INPUT 66 From node R, its corresponding OUTPUT 69 does not need to be merged.
  • the 6 corresponding OUTPUTs originally generated by INPUT 61-INPUT 66 are merged into 3 OUTPUTs: OUTPUT 67-OUTPUT 69.
  • OUTPUT 67-OUTPUT 69 3 OUTPUTs.
  • the users (subjects) in the resource data supply chain are connected through the blockchain system, and the resources transferred between users are uploaded to the chain as resource data, so that resources can be split among users according to business needs ,circulation.
  • the data on the blockchain system is recorded and confirmed by multiple parties, so as to realize the traceability, non-tampering and non-repudiation of resource transfer. In this way, the purpose of transferring the credit of the initiating node between the multi-level receiving nodes can be achieved, and all of its resource data can be traced back to the initial resource data when registering on the chain.
  • FIG. 7 shows a schematic diagram of still other embodiments of the resource data transfer method of the present disclosure.
  • the resource data that the initiating node needs to be transferred is reviewed and then registered on the chain to form the resource data on the chain.
  • the level 1 receiving node After receiving this batch of resource data on the chain, the level 1 receiving node can split it arbitrarily according to needs. After splitting, multiple batches of resource data can be delivered by the initiating node after the resource delivery date expires; or it can be transferred to its upstream level 2 receiving node according to business requirements (at this time, the level 1 receiving node becomes the initiating node); or It is used to apply for resources from resource management node 1 or resource management node 2 (such as network operators, cloud system hosts).
  • resource management node 1 or resource management node 2 such as network operators, cloud system hosts.
  • the N-level receiving nodes upstream of the level 1 receiving node can freely control the resource data on the chain according to their own needs.
  • the entire life cycle of resource data can be divided into three parts: resource data on-chain, resource data transfer, and resource data off-chain.
  • Resource data on the chain is to write the resources to be transferred from the initiating node in the supply chain as resource data into the blockchain system by invoking smart contracts to generate the block record transfer history process;
  • resource data transfer is to transfer assets in different ways by invoking smart contracts Transfer between nodes, generating blocks to record the transfer history process;
  • resource data off-chain is not transferred after the resource delivery date.
  • FIG. 8 shows a flowchart of still other embodiments of the resource data transfer method of the present disclosure.
  • the initiating node goes through a series of corresponding user internal processes to upload resource data on the chain. If an audit node needs to be audited this time on the chain, the status of the corresponding resource data will be configured as a pending audit status, and the audit node will be audited by the designated audit node. In the case that the audit node confirms that the audit is passed or there is no need to audit this time on the chain, the status of the corresponding resource data is configured as the status to be signed, and the receiving node determines whether to sign.
  • the state of the corresponding resource data is configured as a normal state.
  • resource data can be transferred, obtained through an audit node, or waiting for delivery due.
  • the resource data can be rejected by the receiving node during the transfer process, and can also be revoked by the initiating node (before the receiving node confirms the reception).
  • it can be implemented by a transit node that is jointly controlled by both nodes to be transferred.
  • the resource data is first transferred to the transit node. If the receiving node agrees to sign, then transfer from the transit node to the receiving node; if the receiving node refuses to sign or the initiating node withdraws, the resource data is returned from the transit node to the initiating node.
  • the receiving node agrees to sign, it is judged whether the resource data needs to be reviewed.
  • the resource data configuration status is to be signed; if the audit is not required, the resource data configuration status is to be signed.
  • the resource data configuration status is normal; after the receiving node confirms the receipt, the resource data configuration status is set to signed; after the receiving node refuses to sign, the resource data configuration status is set to normal.
  • FIG. 9 shows a flowchart of some embodiments of the resource data uploading method of the present disclosure.
  • step S91 the code parameter processing module in the smart contract is called to process the resource data. For example, the verification of the number of parameters of the resource data, etc., so as to ensure the normal execution of the contract.
  • step S92 the state of the newly created resource default data is configured as valid by default.
  • step S93 a data model of the resource transfer process is constructed.
  • UTXO model construction can be used.
  • step S94 it is determined whether the resource data needs to be reviewed. In the case where the audit is not required, step S95 is performed; in the case where the audit is required, step S96 is performed.
  • step S95 the resource data is transferred to the transit node.
  • step S96 the audit result information is recorded.
  • step S97 the audit result information is stored, including the transfer ID (txid), the audit result (ISSUE_ADUIT_MARK), the audit node (auditor), the initiating node, and the receiving node.
  • the output of this transfer process can be generated using the structure of txid.j->output, and txid.j identifies the jth transfer.
  • FIG. 10 shows a flowchart of some embodiments of the resource data transfer method of the present disclosure.
  • step S101 the code parameter processing module in the smart contract is called to process the resource data.
  • step S102 the input and output related to this transfer process are obtained.
  • step S103 the input is detected, the inputs of the same source and type are merged, and the total amount is calculated. For example, check whether each input comes from the same node (owner); whether it is the same type of resource data; whether it is in a transferable state.
  • step S104 output is detected, outputs of the same type are combined, and the total amount is calculated. For example, check whether each output is the same type of resource data.
  • step S105 it is verified whether the total amount of input and output are the same and are the same kind of resources. If they are inconsistent or different, they cannot be transferred.
  • step S106 it is determined whether the resource data needs to be reviewed. In the case where the audit is not required, step S107 is performed; in the case where the audit is required, step S108 is performed.
  • step S107 the resource data is transferred to the transit node.
  • step S108 the status of the resource data is modified to pending review.
  • step S109 the audit result information is recorded.
  • the audit result information is stored, including the transfer ID (txid), the audit result (ISSUE_ADUIT_MARK), the audit node (auditor), the initiating node, and the receiving node.
  • the output of this transfer process can be generated using the structure of txid.j->output, and txid.j identifies the jth transfer; the input of this transfer process can be generated using the structure of txid.j->input.
  • FIG. 11 shows a flowchart of other embodiments of the resource data transfer method of the present disclosure.
  • step S111 the original (INPUT 61-INPUT 66 in Figure 6) and new UTXO data (OUTPUT 67-OUTPUT 69 in Figure 6) are recorded to the transit node in the form of txid.j->output.
  • step S112 it is judged whether to transfer or issue resource data.
  • step S113 In the case of transit, step S113 is executed; in the case of issuance, step S114 is executed.
  • step S113 the used UTXO data (INPUT 61-INPUT 66 in Fig. 6) is deleted.
  • step S114 the transfer information or issuance information is stored in the blockchain system.
  • FIG. 12 shows a flowchart of some embodiments of the resource data return method of the present disclosure.
  • step S121 the transfer information in the blockchain system is read.
  • step S122 the UTXO data (data used for the transfer) involved in the INPUT related to the transfer process is restored to the "NORMAL" state.
  • step S123 the UTXO resource data restored to the "NORMAL" state is stored in the blockchain system.
  • step S124 the message is cleared on the air.
  • FIG. 13 shows a flowchart of some embodiments of the resource data signing method of the present disclosure.
  • step S131 the transfer information in the blockchain system is read.
  • step S132 the resource type list of the receiving node is read.
  • step S133 it is determined whether the receiving node has the type of resource to be transferred. If yes, execute step S134; if not, execute step S135.
  • step S134 the UTXO data involved in the transit node OUTPUT is transferred to the receiving node.
  • step S135 a resource data type corresponding to the resource to be transferred is added for the receiving node.
  • step S136 the message is cleared on the air.
  • the initiator and receiver of the resource transfer are configured as nodes of the blockchain system, and the non-tamperable feature of the blockchain is used to record the resource conversion process, thereby improving the reliability of the system;
  • FIG. 14 shows a block diagram of some embodiments of the resource data transfer device of the present disclosure.
  • the resource data transfer device 14 includes a transfer unit 141, a storage unit 142 and a transfer unit 143.
  • the transfer unit 141 transfers the resource data to be processed to the transfer node of the blockchain system in response to the resource data transfer request of the initiating node in the blockchain system.
  • the storage unit 142 generates transfer information corresponding to this transfer process, and stores it in the blockchain system.
  • the transfer information includes the information of the initiating node in the transfer process and the information of the designated receiving node of the resource data to be processed.
  • the to-be-processed resource data of each initiating node is multiple batches.
  • the storage unit 142 generates transfer information corresponding to this transfer process according to the relevant information of each comprehensive output resource data, and stores it in the blockchain system.
  • the transfer unit 143 determines whether to process the resource data to be processed in the transfer node according to the resource data processing request corresponding to the resource data transfer request issued by the initiating node or the current receiving node, and the transfer information obtained from the blockchain system. Transfer.
  • the transfer device 14 further includes a merging unit 144 for determining each batch of resource data to be processed received by the transit node from each initiating node as input resource data for this transfer process; and transferring the transit node to Each batch of corresponding resource data of the receiving node is determined as the output resource data of this transfer process, and each output resource data is derived from the corresponding input resource data; the corresponding input resource data with the same initiating node The output resource data is merged into a batch of comprehensive output resource data.
  • a merging unit 144 for determining each batch of resource data to be processed received by the transit node from each initiating node as input resource data for this transfer process; and transferring the transit node to Each batch of corresponding resource data of the receiving node is determined as the output resource data of this transfer process, and each output resource data is derived from the corresponding input resource data; the corresponding input resource data with the same initiating node The output resource data is merged into a batch of comprehensive output resource data.
  • the merging unit 144 obtains the quantity and type of the transferred resource data from other nodes in the historical resource data transfer process of the initiating node; merges the transferred resource data from the same other node and of the same type, Generate comprehensive transfer-in resource data; obtain the number and type of transfer-out resource data that the initiating node intends to transfer to the transfer node during this transfer; merge transfer-out resource data of the same type to generate resource data to be processed.
  • the transfer unit 141 transfers the to-be-processed resource data to the transfer node of the blockchain system when the quantity and type of the comprehensively transferred-in resource data are the same as the quantity and type of the resource data to be processed.
  • the transfer unit 143 returns the to-be-processed resource data to the initiating node in response to the transfer request of the initiating node or the rejection request of the designated receiving node; the storage unit 142 stores the corresponding return information in the block Chain system.
  • the transfer unit 143 configures the state of the resource data to be processed as a normal state in response to the transfer request of the initiating node or the rejection request of the designated receiving node.
  • the normal state the resource data to be processed can be transferred to a node other than the designated receiving node.
  • the transfer unit 143 transfers the to-be-processed resource data to the receiving node in response to the resource data signing request initiated by the receiving node in the blockchain system.
  • the storage unit 142 generates transfer information corresponding to this transfer process, and stores it in the blockchain system.
  • the transfer unit 143 configures the state of the resource data to be processed as a locked state according to the transfer information.
  • the locked state the resource data to be processed can only be transferred to the designated receiving node; in response to the resource data signing request initiated by the receiving node in the blockchain system, according to the information of the designated receiving node in the transfer information, determine whether to transfer the corresponding resource data Transfer to the receiving node.
  • the initiator and receiver of the resource transfer are configured as nodes of the blockchain system, and the non-tamperable feature of the blockchain is used to record the resource conversion process, thereby improving the reliability of the system;
  • FIG. 15 shows a block diagram of other embodiments of the resource data transfer device of the present disclosure.
  • the resource data transfer device 15 of this embodiment includes a memory 151 and a processor 152 coupled to the memory 151.
  • the processor 152 is configured to execute the present disclosure based on instructions stored in the memory 151.
  • the resource data transfer method in any one of the embodiments.
  • the memory 151 may include, for example, a system memory, a fixed non-volatile storage medium, and the like.
  • the system memory for example, stores an operating system, an application program, a boot loader (Boot Loader), a database, and other programs.
  • FIG. 16 shows a block diagram of still other embodiments of the resource data transfer device of the present disclosure.
  • the resource data transfer device 16 of this embodiment includes a memory 1610 and a processor 1620 coupled to the memory 1610.
  • the processor 1620 is configured to execute any of the foregoing based on instructions stored in the memory 1610.
  • the memory 1610 may include, for example, a system memory, a fixed non-volatile storage medium, and the like.
  • the system memory stores, for example, an operating system, an application program, a boot loader (Boot Loader), and other programs.
  • the resource data transfer device 16 may also include an input/output interface 1630, a network interface 1640, a storage interface 1650, and the like. These interfaces 1630, 1640, 1650, the memory 1610 and the processor 1620 may be connected via a bus 1660, for example.
  • the input and output interface 1630 provides a connection interface for input and output devices such as a display, a mouse, a keyboard, and a touch screen.
  • the network interface 1640 provides a connection interface for various networked devices.
  • the storage interface 1650 provides connection interfaces for external storage devices such as SD cards and U disks.
  • the embodiments of the present disclosure can be provided as a method, a system, or a computer program product. Therefore, the present disclosure may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the present disclosure may take the form of a computer program product implemented on one or more computer-usable non-transitory storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program codes. .
  • Figure 17 shows a block diagram of some embodiments of the blockchain system of the present disclosure.
  • the blockchain system 17 includes the resource data transfer device 171 in any of the above embodiments.
  • the method and system of the present disclosure may be implemented in many ways.
  • the method and system of the present disclosure can be implemented by software, hardware, firmware or any combination of software, hardware, and firmware.
  • the above-mentioned order of the steps for the method is for illustration only, and the steps of the method of the present disclosure are not limited to the order specifically described above, unless specifically stated otherwise.
  • the present disclosure can also be implemented as programs recorded in a recording medium, and these programs include machine-readable instructions for implementing the method according to the present disclosure.
  • the present disclosure also covers a recording medium storing a program for executing the method according to the present disclosure.

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

本公开涉及一种资源数据的转移方法、装置和区块链***，涉及数据处理技术领域。该方法包括：响应于区块链***中发起节点的资源数据转移请求，将所述资源数据转移请求相应的待处理资源数据中转到所述区块链***的中转节点；生成与本次中转过程相应的中转信息，存储在区块链***中，中转信息包括本次中转过程中发起节点的信息、待处理资源数据的指定接收节点的信息；根据发起节点或当前接收节点发出的与所述资源数据转移请求相应的资源数据处理请求，以及从区块链***中获取的中转信息，确定是否对中转节点中的待处理资源数据进行转移。

Description

资源数据的转移方法、装置和区块链***
相关申请的交叉引用
本申请是以CN申请号为201910976320.3，申请日为2019年10月15日的申请为基础，并主张其优先权，该CN申请的公开内容在此作为整体引入本申请中。
技术领域
本公开涉及数据处理技术领域，特别涉及一种资源数据的转移方法、资源数据的转移装置、区块链***和计算机可读存储介质。
背景技术
随着互联网技术的发展，可以实现用户(个人用户或企业用户等)之间的资源数据转移。例如，可以实现互联网用户之间的流量资源、带宽资源等网络资源的转移；或者实现云***或计算机集群用户之间的计算资源、存储资源等***资源的转移。
通过资源数据交换，也可以实现用户之间资源的互换。例如，用户A可以利用自身流量资源换取用户B的带宽资源，用户B可以利用自身带宽资源换取用户C的流量资源等，从而形成一条包含用户A、B、C等多级资源供应用户的资源数据供应链。
在相关技术中，资源数据供应链上的各用户直接进行资源转移。
发明内容
本公开的发明人发现上述相关技术中存在如下问题：资源转移过程易被篡改，导致***的可靠性差；资源数据一旦转移无法撤回，导致***的灵活性差。
鉴于此，本公开提出了一种资源数据的转移技术方案，能够提高***的可靠性、灵活性。
根据本公开的一些实施例，提供了一种资源数据的转移方法，包括：响应于区块链***中发起节点的资源数据转移请求，将所述资源数据转移请求相应的待处理资源数据中转到所述区块链***的中转节点；生成与本次中转过程相应的中转信息，存储在所述区块链***中，所述中转信息包括本次中转过程中所述发起节点的信息、所述待处理资源数据的指定接收节点的信息；根据所述发起节点或当前接收节点发出的与所述资源数据转移请求相应的资源数据处理请求，以及从所述区块链***中获取的所 述中转信息，确定是否对所述中转节点中的所述待处理资源数据进行转移。
在一些实施例中，所述相应的资源数据处理请求为所述发起节点发出的撤销转移请求或者所述指定接收节点发出的拒绝签收请求。
在一些实施例中，所述确定是否对所述中转节点中的所述待处理资源数据进行转移包括：响应于所述发起节点的撤销转移请求或者所述指定接收节点的拒绝签收请求，将所述待处理资源数据退回所述发起节点；将相应的退回信息，存储在所述区块链***中。
在一些实施例中，所述确定是否对所述中转节点中的所述待处理资源数据进行转移包括：响应于所述发起节点的撤销转移请求或者所述指定接收节点的拒绝签收请求，将所述待处理资源数据的状态配置为正常状态，在所述正常状态下，所述待处理资源数据可以转移到所述指定接收节点以外的节点。
在一些实施例中，所述确定是否对所述中转节点中的所述待处理资源数据进行转移包括：响应于所述区块链***中当前接收节点发起的资源数据签收请求，将所述待处理资源数据转移到所述当前接收节点；生成与本次转移过程相应的转移信息，存储在所述区块链***中。
在一些实施例中，所述确定是否对所述中转节点中的所述待处理资源数据进行转移包括：根据所述中转信息，将所述待处理资源数据的状态配置为锁定状态，在所述锁定状态下，所述待处理资源数据只能转移到所述指定接收节点；响应于所述区块链***中当前接收节点发起的资源数据签收请求，根据所述中转信息中的所述指定接收节点的信息，确定是否将相应资源数据转移到所述接收节点。
在一些实施例中，所述发起节点为多个，各发起节点的待处理资源数据为多批；所述生成与本次转移过程相应的转移信息，存储在所述区块链***中包括：将所述中转节点从各发起节点接收的每批待处理资源数据，确定为本次转移过程的各输入资源数据；将所述中转节点转移给当前接收节点的每批相应资源数据，确定为本次转移过程的各输出资源数据，所述各输出资源数据分别来源于相应的所述各输入资源数据；将具有相同发起节点的各输入资源数据的相应输出资源数据合并为一批综合输出资源数据；根据各综合输出资源数据的相关信息，生成与本次转移过程相应的转移信息，存储在所述区块链***中。
在一些实施例中，所述将待处理资源数据中转到所述区块链***的中转节点包括：获取所述发起节点在历史资源数据转移过程中，来源于其他节点的各转入资源数据的 数量和类型；合并来源于相同其他节点且类型相同的转入资源数据，生成综合转入资源数据；获取所述发起节点在本次中转过程中，拟转给所述中转节点的转出资源数据的数量和类型；合并类型相同的转出资源数据，生成所述待处理资源数据；在所述综合转入资源数据的数量和类型与所述待处理资源数据的数量和类型相同的情况下，将所述待处理资源数据中转到所述区块链***的中转节点。
根据本公开的另一些实施例，提供一种资源数据的转移装置，包括：中转单元，用于响应于区块链***中发起节点的资源数据转移请求，将待处理资源数据中转到所述区块链***的中转节点；存储单元，用于生成与本次中转过程相应的中转信息，存储在所述区块链***中，所述中转信息包括本次中转过程中所述发起节点的信息、所述待处理资源数据的指定接收节点的信息；转移单元，用于根据所述发起节点或当前接收节点发出的与所述资源数据转移请求相应的资源数据处理请求，以及从所述区块链***中获取的所述中转信息，确定是否对所述中转节点中的所述待处理资源数据进行转移。
在一些实施例中，所述发起节点为多个，各发起节点的待处理资源数据为多批；所述存储单元根据各综合输出资源数据的相关信息，生成与本次转移过程相应的转移信息，存储在所述区块链***中。
在一些实施例中，所述的转移装置还包括合并单元，用于将所述中转节点从各发起节点接收的每批待处理资源数据，确定为本次转移过程的各输入资源数据，将所述中转节点转移给当前接收节点的每批相应资源数据，确定为本次转移过程的各输出资源数据，所述各输出资源数据分别来源于相应的所述各输入资源数据，将具有相同发起节点的各输入资源数据的相应输出资源数据合并为一批综合输出资源数据。
在一些实施例中，所述的转移装置还包括合并单元，用于获取所述发起节点在历史资源数据转移过程中，来源于其他节点的各转入资源数据的数量和类型，合并来源于相同其他节点且类型相同的转入资源数据，生成综合转入资源数据，获取所述发起节点在本次中转过程中，拟转给所述中转节点的转出资源数据的数量和类型，合并类型相同的转出资源数据，生成所述待处理资源数据；所述中转单元在所述综合转入资源数据的数量和类型与所述待处理资源数据的数量和类型相同的情况下，将所述待处理资源数据中转到所述区块链***的中转节点。
在一些实施例中，所述转移单元响应于所述发起节点的撤销转移请求或者所述指定接收节点的拒绝签收请求，将所述待处理资源数据退回所述发起节点；所述存储单 元将相应的退回信息，存储在所述区块链***中。
在一些实施例中，所述转移单元响应于所述发起节点的撤销转移请求或者所述指定接收节点的拒绝签收请求，将所述待处理资源数据的状态配置为正常状态，在所述正常状态下，所述待处理资源数据可以转移到所述指定接收节点以外的节点。
在一些实施例中，所述转移单元响应于所述区块链***中当前接收节点发起的资源数据签收请求，将所述待处理资源数据转移到所述当前接收节点；所述存储单元生成与本次转移过程相应的转移信息，存储在所述区块链***中。
在一些实施例中，所述转移单元根据所述中转信息，将所述待处理资源数据的状态配置为锁定状态，在所述锁定状态下，所述待处理资源数据只能转移到所述指定接收节点；响应于所述区块链***中当前接收节点发起的资源数据签收请求，根据所述中转信息中的所述指定接收节点的信息，确定是否将相应资源数据转移到所述接收节点。
根据本公开的又一些实施例，提供一种资源数据的转移装置，包括：存储器；和耦接至所述存储器的处理器，所述处理器被配置为基于存储在所述存储器中的指令，执行上述任一个实施例中的资源数据的转移方法。
根据本公开的再一些实施例，提供一种计算机可读存储介质，其上存储有计算机程序，该程序被处理器执行时实现上述任一个实施例中的资源数据的转移方法。
根据本公开的再一些实施例，提供一种区块链***，包括：上述任一个实施例中的资源数据的转移装置。
在上述实施例中，将资源转移的发起方和接收方都配置为区块链***的节点，利用区块链不可篡改的特性记录资源转换过程，从而提高了***的可靠性；并将待转移的资源先中转到中转节点，再根据发起方和接收方的指令确定是否进行转移，从而提高了***的灵活性。
附图说明
构成说明书的一部分的附图描述了本公开的实施例，并且连同说明书一起用于解释本公开的原理。
参照附图，根据下面的详细描述，可以更加清楚地理解本公开，其中：
图1示出本公开的资源数据的转移方法的一些实施例的流程图；
图2示出图1中步骤S10的一些实施例的流程图；
图3示出本公开的资源数据的转移方法的一些实施例的示意图；
图4a示出图1中步骤S30的一些实施例的流程图；
图4b示出图1中步骤S30的另一些实施例的流程图；
图4c示出图1中步骤S30的又一些实施例的流程图；
图5示出本公开的资源数据的转移方法的另一些实施例的流程图；
图6示出本公开的资源数据的转移方法的另一些实施例的示意图；
图7示出本公开的资源数据的转移方法的又一些实施例的示意图；
图8示出本公开的资源数据的转移方法的又一些实施例的流程图；
图9示出本公开的资源数据上链方法的一些实施例的流程图；
图10示出本公开的资源数据中转方法的一些实施例的流程图；
图11示出本公开的资源数据中转方法的另一些实施例的流程图；
图12示出本公开的资源数据退回方法的一些实施例的流程图；
图13示出本公开的资源数据签收方法的一些实施例的流程图；
图14示出本公开的资源数据中转装置的一些实施例的框图；
图15示出本公开的资源数据的转移装置的另一些实施例的框图；
图16示出本公开的资源数据的转移装置的又一些实施例的框图；
图17示出本公开的区块链***的一些实施例的框图。
具体实施方式
现在将参照附图来详细描述本公开的各种示例性实施例。应注意到：除非另外具体说明，否则在这些实施例中阐述的部件和步骤的相对布置、数字表达式和数值不限制本公开的范围。
同时，应当明白，为了便于描述，附图中所示出的各个部分的尺寸并不是按照实际的比例关系绘制的。
以下对至少一个示例性实施例的描述实际上仅仅是说明性的，决不作为对本公开及其应用或使用的任何限制。
对于相关领域普通技术人员已知的技术、方法和设备可能不作详细讨论，但在适当情况下，所述技术、方法和设备应当被视为授权说明书的一部分。
在这里示出和讨论的所有示例中，任何具体值应被解释为仅仅是示例性的，而不是作为限制。因此，示例性实施例的其它示例可以具有不同的值。
应注意到：相似的标号和字母在下面的附图中表示类似项，因此，一旦某一项在一个附图中被定义，则在随后的附图中不需要对其进行进一步讨论。
图1示出本公开的资源数据的转移方法的一些实施例的流程图。
如图1所示，该方法包括：步骤S10，资源中转到中转节点；步骤S20，生成并存储中转信息；和步骤S30，确定是否进行资源转移。
在步骤S10中，响应于区块链***中发起节点的资源数据转移请求，将待处理资源数据中转到区块链***的中转节点。例如，将待处理资源数据存储到中转节点，或中转到中转节点名下。
在一些实施例中，发起节点可以是网络用户、云***或计算集群用户、企业、各级供应商等。例如，资源数据可以是网络用户的流量资源、带宽资源等网络资源，也可以是云***或计算集群用户的计算资源、存储资源等***资源，还可以是企业与各级供应商的资金、资产等金融资源。
在一些实施例中，通过调用区块链***的智能合约，将发起节点的资源数据转移至中转节点。例如，中转节点可以是物理节点也可以是通过软件实现的非物理节点。中转节点可以是发起节点和接收节点共同持有私钥解锁的中间账户。中转过程会记录到区块链***中，由区块链***打包出块。
在一些实施例中，可以通过图2中的实施例执行步骤S10。
图2示出图1中步骤S10的一些实施例的流程图。
如图2所示，步骤S10可以包括：步骤S110，获取转入资源数据的数量和类型；步骤S120，合并转入资源数据；步骤S130，获取转出资源数据的数量和类型；步骤S140，合并转出资源数据；和步骤S150，中转待处理资源数据。
在步骤S110中，获取发起节点在历史资源数据转移过程中，来源于其他节点的各转入资源数据的数量和类型。
在一些实施例中，可以根据UTXO(Unspent Transaction Output，未花费的交易输出)模型建立转移过程模型。例如，根据UTXO模型，每次转移过程(或者中转过程)都包含至少一批资源数据输入(input)用于表示在本次转移之前获取的资源数据，和来源于各input的至少一批资源数据输出(output)用于表示在本次转移过程转移出去的资源数据。
在一些实施例中，可以采用图3中的实施例建立转移过程模型。
图3示出本公开的资源数据的转移方法的一些实施例的示意图。
如图3所示，根据UTXO模型为两个资源数据转移过程两个模型：资源数据转移1和资源数据转移2。
在一些实施例中，资源数据转移1表示的转移过程为节点A将资源数据转移到节点B和节点C。INPUT 11标识节点A在上次转移过程中转入的资源数据；OUTPUT 12和OUTPUT 13都来源于INPUT 11，OUTPUT 12和OUTPUT 13分别标识节点A转移到节点B和节点C的资源数据。
资源数据转移2表示的转移过程为节点B将资源数据转移到节点D和节点E。INPUT 21标识节点B在资源数据转移1表示的转移过程中从节点A转入的资源数据(即来源于OUTPUT12)；INPUT 22、INPUT 23标识节点B在上次转移过程中转入的资源数据；OUTPUT 24和OUTPUT 25都来源于INPUT 21、INPUT 22或者INPUT 23，OUTPUT 24和OUTPUT 25分别标识节点B转移到节点D和节点E的资源数据。
基于上述模型，可以继续利用图2中的步骤进行资源数据转移。
在步骤S120中，合并来源于相同其他节点且类型相同的转入资源数据，生成综合转入资源数据。例如，资源数据的类型可以是流量资源、带宽资源、计算资源、存储资源、各类型资金资源等。
在步骤S130中，获取发起节点在本次中转过程中，拟转给中转节点的转出资源数据的数量和类型。
在步骤S140中，合并类型相同的转出资源数据，生成待处理资源数据。
在步骤S150中，在综合转入资源数据的数量和类型与待处理资源数据的数量和类型相同的情况下，将待处理资源数据中转到区块链***的中转节点。在数量或类型不同的情况下，可以报错或提示无法进行转移。
将资源数据中转到中转节点后，就可以利用图1中的其他步骤继续实现资源数据转移了。
在步骤S20中，生成与本次中转过程相应的中转信息，存储在区块链***中，中转信息包括本次中转过程中发起节点的信息、待处理资源数据的指定接收节点的信息。
在步骤S30中，根据发起节点或当前接收节点发出的与所述资源数据转移请求相应的资源数据处理请求，以及从区块链***中获取的中转信息，确定是否对中转节点中的待处理资源数据进行转移。例如，与所述资源数据转移请求相应的资源数据处理请求可以是发起节点发出的撤销转移指令、接收节点发出的拒绝签收请求或签收请求。
在一些实施例中，可以通过图4a、图4b或图4c中的实施例执行步骤S30。
图4a示出图1中步骤S30的一些实施例的流程图。
如图4a所示，步骤S30可以包括：步骤S310a，资源退回发起节点；和步骤S320a，存储退回信息。
在步骤S310a中，响应于发起节点的撤销转移请求或者指定接收节点的拒绝签收请求，将待处理资源数据退回发起节点。
在一些实施例中，响应于发起节点的撤销转移请求或者指定接收节点的拒绝签收请求，将待处理资源数据的状态配置为正常(Normal)状态。在正常状态下，待处理资源数据可以转移到指定接收节点以外的节点。
在步骤S320a中，将相应的退回信息，存储在区块链***中。
图4b示出图1中步骤S30的另一些实施例的流程图。
如图4b所示，步骤S30可以包括：步骤S310b，资源转移到接收节点；和步骤S320b，存储转移信息。
在步骤S310b中，响应于区块链***中接收节点发起的资源数据签收请求，将待处理资源数据转移到接收节点。
在步骤S320b中，生成与本次转移过程相应的转移信息，存储在区块链***中。
图4c示出图1中步骤S30的又一些实施例的流程图。
如图4c所示，步骤S30可以包括：步骤S310c，配置锁定状态；和步骤S320c，确定是否进行资源转移。
在步骤S310c中，根据中转信息，将待处理资源数据的状态配置为锁定状态。在锁定状态下，待处理资源数据只能转移到指定接收节点。
在步骤S320c中，响应于区块链***中接收节点发起的资源数据签收请求，根据中转信息中的指定接收节点的信息，确定是否将相应资源数据转移到接收节点。
在一些实施例中，发起节点为多个，各发起节点的待处理资源数据为多批。可以通过图5中的实施例将转移信息存储在区块链***中。
图5示出本公开的资源数据的转移方法的另一些实施例的流程图。
如图5所示，相比于上述任一个实施例，该方法还包括：步骤S51，确定输入资源数据；步骤S52，确定输出资源数据；步骤S53，合并为综合输出资源数据；和步骤S54，存储转移信息。
在步骤S51中，将中转节点从各发起节点接收的每批待处理资源数据，确定为本次转移过程的各输入资源数据。
在步骤S52中，将中转节点转移给的接收节点的每批相应资源数据，确定为本次转移过程的各输出资源数据。各输出资源数据分别来源于相应的各输入资源数据。
在步骤S53中，将具有相同发起节点的各输入资源数据的相应输出资源数据合并为一批综合输出资源数据。
在步骤S54中，根据各综合输出资源数据的相关信息，生成与本次转移过程相应的转移信息，存储在区块链***中。转移信息可以包括：各批待处理资源数据的发起节点的信息、各批待处理资源数据的指定接收节点的信息、各批待处理资源数据的当前接收节点的信息等。
在一些实施例中，可以为转移过程中的input和output都设置pre字段，用于标识input和output在上一次转换过程中的来源节点。这样，就可以根据pre字段合并来源相同的output。还可以设置prepre字段，用于标识input和output在上两次转换过程中的来源节点。例如，可以采用图6中的实施例实现资源数据的合并。
图6示出本公开的资源数据的转移方法的另一些实施例的示意图。
如图6所示，转移过程为节点A将资源数据转移到节点B和节点C。
INPUT 61-INPUT 66都是节点A在历史转移过程中转入的资源数据。INPUT 61-INPUT 66都设置有pre字段和prepre字段分别标识相应的INPUT的上一次转移来源节点和上两次转移来源节点(如节点D、E、R等)。
OUTPUT 67-OUTPUT 69是转出到节点B或C的资源数据。OUTPUT 67-OUTPUT 69都设置有pre字段和prepre字段分别标识相应的OUTPUT的上一次转移来源节点和上两次转移来源节点。
根据各INPUT的pre字段，可以将相应的OUTPUT合并。例如，INPUT 61-INPUT 63都来源于节点D，则可以将其相应的OUTPUT合并为OUTPUT67；INPUT 64-INPUT 65都来源于节点E，则可以将其相应的OUTPUT合并为OUTPUT 68；只有INPUT 66来源于节点R，其相应的OUTPUT 69无需合并。
在上述实施例中，将INPUT 61-INPUT 66本来会产生的6条相应OUTPUT合并为3条OUTPUT：OUTPUT 67-OUTPUT 69。这样，可以避免随着资源数据的转移不断进行，导致需要存储OUTPUT越来越多(即UTXO膨胀)的问题。而且，pre字段和prepre字段可以使得资源数据的转移可以被有效追溯，从而提高***可靠性。
在上述实施例中，通过区块链***连接资源数据供应链中的各用户(主体)，将用户之间转移的资源作为资源数据上链，从而可以根据业务需要将资源在各用户间拆 分、流转。区块链***上的数据经多方记录确认，从而实现资源转移可追溯、不可篡改、不可抵赖。这样，可以达到在多级接收节点之间传递发起节点信用的目的，其所有的资源数据均可追溯至登记上链时的初始资源数据。
图7示出本公开的资源数据的转移方法的又一些实施例的示意图。
如图7所示，以发起节点(如核心企业用户)与其1级接收节点的真实资源数据转移为基础，对发起节点需要转移的资源数据进行审核后登记上链形成链上资源数据。
1级接收节点拿到这批链上资源数据后，能够将其根据需求进行任意拆分。拆分后的多批资源数据既可以等待资源交付日期到期后由发起节点交付；也可以根据业务需求转移给其上游的2级接收节点(此时1级接收节点变为发起节点)；或者用来向资源管理节点1或资源管理节点2(如网络运营商、云***主机)申请获取资源。
1级接收节点上游的N级接收节点，都可以按照自己的需求自由支配的链上资源数据。
在一些实施例中，整个资源数据的生命周期可以分为三部分：资源数据上链，资源数据转移，资源数据离链。资源数据上链是通过调用智能合约将供应链中发起节点的待转移资源作为资源数据写入区块链***，生成区块记录转移历史过程；资源数据转移是通过调用智能合约将资产在不同的节点之间转移，生成区块记录转移历史过程；资源数据离链是到资源交付日期之后不再转移。
图8示出本公开的资源数据的转移方法的又一些实施例的流程图。
如图8所示，由发起节点经过一系列相应用户内部流程后进行资源数据上链。如果此次上链需要审核节点进行审核，则将相应的资源数据的状态配置为待审核状态，并由指定的审核节点进行审核。在审核节点确认审核通过或此次上链无需审核的情况下，将相应的资源数据的状态配置为待签收状态，由接收节点确定是否签收。
在接收节点确认签收的情况下，将相应的资源数据的状态配置为正常状态。在正常状态下，资源数据可以转移、通过审核节点获取或者等待到期交付。
资源数据在转移过程中可以被接收节点拒收，也可以被发起节点撤销(在接收节点确认接收之前)。例如，可以通过被转移双方节点共同控制的中转节点实现。在资源数据转移过程中，资源数据首先被转让进入中转节点。如果接收节点同意签收，再从中转节点转入接收节点；如果接收节点拒绝签收或者发起节点撤回，则资源数据从中转节点退回发起节点。
在接收节点同意签收的情况下，判断资源数据是否需要审核。在需要审核的情况 下，审核节点进行审核通过后，将资源数据配置状态为待签收；在不需要审核的情况下，将资源数据配置状态为待签收。
审核节点进行审核拒绝通过后，将资源数据配置状态为正常；接收节点确认签收后，将资源数据配的状态置为已签收；接收节点拒绝签收后，将资源数据配的状态置为正常。
图9示出本公开的资源数据上链方法的一些实施例的流程图。
如图9所示，在步骤S91中，调用智能合约中的代码参数处理模块对资源数据进行处理。例如，对资源数据的参数个数的校验等，从而保证合约能正常执行。
在步骤S92中，将新建的资源默认数据的状态默认配置为有效。
在步骤S93中，构造资源转移过程的数据模型。例如，可以利用UTXO模型构建。
在步骤S94中，判断资源数据是否需要审核。在不需要审核的情况下，执行步骤S95；在需要审核的情况下，执行步骤S96。
在步骤S95中，将资源数据转至中转节点。
在步骤S96中，记录审核的结果信息。
在步骤S97中，存储审核的结果信息，包括转移ID(txid)、审核结果(ISSUE_ADUIT_MARK)、审核节点(auditor)、发起节点、接收节点。例如，本次转移过程的output可以采用txid.j->output的结构生成，txid.j标识第j次转移。
图10示出本公开的资源数据中转方法的一些实施例的流程图。
如图10所示，在步骤S101中，调用智能合约中的代码参数处理模块对资源数据进行处理。
在步骤S102中，获取本次转移过程相关的input、output。
在步骤S103中，检测input，合并同来源、同类型的input，并计算总量。例如，检测各input是否来源于同一节点(owner)；是否为同类型资源数据；是否为可转移状态。
在步骤S104中检测output，合并同类型的output，并计算总量。例如，检测各output是否为同类型资源数据。
在步骤S105中，验证input和output的总量是否一致且为同种资源。如果不一致或不同种，则无法转移。
在步骤S106中，判断资源数据是否需要审核。在不需要审核的情况下，执行步骤S107；在需要审核的情况下，执行步骤S108。
在步骤S107中，将资源数据转至中转节点。
在步骤S108中，修改资源数据状态为待审核。
在步骤S109中，记录审核的结果信息。
在步骤S1010中，存储审核的结果信息，包括转移ID(txid)、审核结果(ISSUE_ADUIT_MARK)、审核节点(auditor)、发起节点、接收节点。例如，本次转移过程的output可以采用txid.j->output的结构生成，txid.j标识第j次转移；本次转移过程的input可以采用txid.j->input的结构生成。
图11示出本公开的资源数据中转方法的另一些实施例的流程图。
如图11所示，在步骤S111中，将原有(如图6中的INPUT 61-INPUT 66)及新生UTXO数据(如图6中的OUTPUT 67-OUTPUT 69)记录至中转节点，形式可以为txid.j->output。
在步骤S112中，判断中转还是发行资源数据。在中转的情况下，执行步骤S113；在发行的情况下，执行步骤S114。
在步骤S113中，删除已使用的UTXO数据(如图6中的INPUT 61-INPUT 66)。
在步骤S114中，在区块链***中存储中转信息或发行信息。
图12示出本公开的资源数据退回方法的一些实施例的流程图。
如图12所示，在步骤S121中，读取区块链***中的中转信息。
在步骤S122中，将此次转移过程相关的INPUT中涉及到的UTXO数据(用于转移使用的数据)恢复为“NORMAL”状态。
在步骤S123中，在区块链***中，存储恢复为“NORMAL”状态的UTXO资源数据。
在步骤S124中，清空中转信息。
图13示出本公开的资源数据签收方法的一些实施例的流程图。
如图13所示，在步骤S131中，读取区块链***中的中转信息。
在步骤S132中，读取接收节点的资源类型列表。
在步骤S133中，判断接收节点是否已有待转移资源的类型。在有的情况下，执行步骤S134；在没有的情况下，执行步骤S135。
在步骤S134中，将中转节点OUTPUT中涉及到的UTXO数据转移到接收节点。
在步骤S135中，为接收节点新增与待转移资源相应的资源数据类型。
在步骤S136中，清空中转信息。
在上述实施例中，将资源转移的发起方和接收方都配置为区块链***的节点，利用区块链不可篡改的特性记录资源转换过程，从而提高了***的可靠性；并将待转移的资源先中转到中转节点，再根据发起方和接收方的指令确定是否进行转移，从而提高了***的灵活性。
图14示出本公开的资源数据中转装置的一些实施例的框图。
如图14所示，资源数据的转移装置14包括中转单元141、存储单元142和转移单元143。
中转单元141响应于区块链***中发起节点的资源数据转移请求，将待处理资源数据中转到所述区块链***的中转节点。
存储单元142生成与本次中转过程相应的中转信息，存储在区块链***中。中转信息包括本次中转过程中发起节点的信息、待处理资源数据的指定接收节点的信息。
在一些实施例中，发起节点为多个，各发起节点的待处理资源数据为多批。存储单元142根据各综合输出资源数据的相关信息，生成与本次转移过程相应的转移信息，存储在所述区块链***中。
转移单元143根据发起节点或当前接收节点发出的与所述资源数据转移请求相应的资源数据处理请求，以及从区块链***中获取的中转信息，确定是否对中转节点中的待处理资源数据进行转移。
在一些实施例中，转移装置14还包括合并单元144，用于将中转节点从各发起节点接收的每批待处理资源数据，确定为本次转移过程的各输入资源数据；将中转节点转移给的接收节点的每批相应资源数据，确定为本次转移过程的各输出资源数据，各输出资源数据分别来源于相应的所述各输入资源数据；将具有相同发起节点的各输入资源数据的相应输出资源数据合并为一批综合输出资源数据。
在一些实施例中，合并单元144获取发起节点在历史资源数据转移过程中，来源于其他节点的各转入资源数据的数量和类型；合并来源于相同其他节点且类型相同的转入资源数据，生成综合转入资源数据；获取发起节点在本次中转过程中，拟转给中转节点的转出资源数据的数量和类型；合并类型相同的转出资源数据，生成待处理资源数据。
中转单元141在综合转入资源数据的数量和类型与待处理资源数据的数量和类型相同的情况下，将待处理资源数据中转到区块链***的中转节点。
在一些实施例中，所述转移单元143响应于发起节点的撤销转移请求或者指定接 收节点的拒绝签收请求，将待处理资源数据退回发起节点；存储单元142将相应的退回信息，存储在区块链***中。
在一些实施例中，转移单元143响应于发起节点的撤销转移请求或者指定接收节点的拒绝签收请求，将待处理资源数据的状态配置为正常状态。在正常状态下，待处理资源数据可以转移到指定接收节点以外的节点。
在一些实施例中，转移单元143响应于区块链***中接收节点发起的资源数据签收请求，将待处理资源数据转移到接收节点。存储单元142生成与本次转移过程相应的转移信息，存储在区块链***中。
在一些实施例中，转移单元143根据中转信息，将待处理资源数据的状态配置为锁定状态。在锁定状态下，待处理资源数据只能转移到指定接收节点；响应于区块链***中接收节点发起的资源数据签收请求，根据中转信息中的指定接收节点的信息，确定是否将相应资源数据转移到接收节点。
在上述实施例中，将资源转移的发起方和接收方都配置为区块链***的节点，利用区块链不可篡改的特性记录资源转换过程，从而提高了***的可靠性；并将待转移的资源先中转到中转节点，再根据发起方和接收方的指令确定是否进行转移，从而提高了***的灵活性。
图15示出本公开的资源数据的转移装置的另一些实施例的框图。
如图15所示，该实施例的资源数据的转移装置15包括：存储器151以及耦接至该存储器151的处理器152，处理器152被配置为基于存储在存储器151中的指令，执行本公开中任意一个实施例中的资源数据的转移方法。
其中，存储器151例如可以包括***存储器、固定非易失性存储介质等。***存储器例如存储有操作***、应用程序、引导装载程序(Boot Loader)、数据库以及其他程序等。
图16示出本公开的资源数据的转移装置的又一些实施例的框图。
如图16所示，该实施例的资源数据的转移装置16包括：存储器1610以及耦接至该存储器1610的处理器1620，处理器1620被配置为基于存储在存储器1610中的指令，执行前述任意一个实施例中的资源数据的转移方法。
存储器1610例如可以包括***存储器、固定非易失性存储介质等。***存储器例如存储有操作***、应用程序、引导装载程序(Boot Loader)以及其他程序等。
资源数据的转移装置16还可以包括输入输出接口1630、网络接口1640、存储接 口1650等。这些接口1630、1640、1650以及存储器1610和处理器1620之间例如可以通过总线1660连接。其中，输入输出接口1630为显示器、鼠标、键盘、触摸屏等输入输出设备提供连接接口。网络接口1640为各种联网设备提供连接接口。存储接口1650为SD卡、U盘等外置存储设备提供连接接口。
本领域内的技术人员应当明白，本公开的实施例可提供为方法、***、或计算机程序产品。因此，本公开可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本公开可采用在一个或多个其中包含有计算机可用程序代码的计算机可用非瞬时性存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
图17示出本公开的区块链***的一些实施例的框图。
如图17所示，区块链***17包括上述任一个实施例中的资源数据的转移装置171。
至此，已经详细描述了根据本公开的资源数据的转移方法、资源数据的转移装置、区块链***和计算机可读存储介质。为了避免遮蔽本公开的构思，没有描述本领域所公知的一些细节。本领域技术人员根据上面的描述，完全可以明白如何实施这里公开的技术方案。
可能以许多方式来实现本公开的方法和***。例如，可通过软件、硬件、固件或者软件、硬件、固件的任何组合来实现本公开的方法和***。用于所述方法的步骤的上述顺序仅是为了进行说明，本公开的方法的步骤不限于以上具体描述的顺序，除非以其它方式特别说明。此外，在一些实施例中，还可将本公开实施为记录在记录介质中的程序，这些程序包括用于实现根据本公开的方法的机器可读指令。因而，本公开还覆盖存储用于执行根据本公开的方法的程序的记录介质。
虽然已经通过示例对本公开的一些特定实施例进行了详细说明，但是本领域的技术人员应该理解，以上示例仅是为了进行说明，而不是为了限制本公开的范围。本领域的技术人员应该理解，可在不脱离本公开的范围和精神的情况下，对以上实施例进行修改。本公开的范围由所附权利要求来限定。

Claims (13)

  1. 一种资源数据的转移方法，包括：
    响应于区块链***中发起节点的资源数据转移请求，将所述资源数据转移请求相应的待处理资源数据中转到所述区块链***的中转节点；
    生成与本次中转过程相应的中转信息，存储在所述区块链***中，所述中转信息包括本次中转过程中所述发起节点的信息、所述待处理资源数据的指定接收节点的信息；
    根据所述发起节点或当前接收节点发出的与所述资源数据转移请求相应的资源数据处理请求，以及从所述区块链***中获取的所述中转信息，确定是否对所述中转节点中的所述待处理资源数据进行转移。
  2. 根据权利要求1所述的转移方法，其中，
    所述相应的资源数据处理请求为所述发起节点发出的撤销转移请求或者所述指定接收节点发出的拒绝签收请求；
    所述确定是否对所述中转节点中的所述待处理资源数据进行转移包括：
    响应于所述发起节点发出的撤销转移请求或者所述指定接收节点发出的拒绝签收请求，将所述待处理资源数据退回所述发起节点；
    将相应的退回信息，存储在所述区块链***中。
  3. 根据权利要求1所述的转移方法，其中，
    所述相应的资源数据处理请求为所述发起节点发出的撤销转移请求或者所述指定接收节点发出的拒绝签收请求；
    所述确定是否对所述中转节点中的所述待处理资源数据进行转移包括：
    响应于所述发起节点发出的撤销转移请求或者所述指定接收节点发出的拒绝签收请求，将所述待处理资源数据的状态配置为正常状态，在所述正常状态下，所述待处理资源数据可以转移到所述指定接收节点以外的节点。
  4. 根据权利要求1所述的转移方法，其中，
    所述相应的资源数据处理请求为所述当前接收节点发起的资源数据签收请求；
    所述确定是否对所述中转节点中的所述待处理资源数据进行转移包括：
    响应于所述区块链***中当前接收节点发起的资源数据签收请求，将所述待处理资源数据转移到所述当前接收节点；
    生成与本次转移过程相应的转移信息，存储在所述区块链***中。
  5. 根据权利要求1所述的转移方法，其中，
    所述相应的资源数据处理请求为所述当前接收节点发起的资源数据签收请求；
    所述确定是否对所述中转节点中的所述待处理资源数据进行转移包括：
    根据所述中转信息，将所述待处理资源数据的状态配置为锁定状态，在所述锁定状态下，所述待处理资源数据只能转移到所述指定接收节点；
    响应于所述区块链***中所述当前接收节点发出的资源数据签收请求，根据所述中转信息中的所述指定接收节点的信息，确定是否将相应资源数据转移到所述当前接收节点。
  6. 根据权利要求4所述的转移方法，其中，
    所述发起节点为多个，各发起节点的资源数据转移请求对应的待处理资源数据为多批；
    所述生成与本次转移过程相应的转移信息，存储在所述区块链***中包括：
    将所述中转节点从各发起节点接收的每批待处理资源数据，确定为本次转移过程的各输入资源数据；
    将所述中转节点转移给当前接收节点的每批相应资源数据，确定为本次转移过程的各输出资源数据，所述各输出资源数据分别来源于相应的输入资源数据；
    将具有相同发起节点的各输入资源数据的相应的输出资源数据合并为一批综合输出资源数据；
    根据各综合输出资源数据的相关信息，生成与本次转移过程相应的转移信息，存储在所述区块链***中。
  7. 根据权利要求1-6任一项所述的转移方法，其中，所述将待处理资源数据中转到所述区块链***的中转节点包括：
    获取所述发起节点在历史资源数据转移过程中，来源于其他节点的各转入资源数据的数量和类型；
    合并来源于相同其他节点且类型相同的转入资源数据，生成综合转入资源数据；
    获取所述发起节点在本次中转过程中，拟转给所述中转节点的转出资源数据的数量和类型；
    合并类型相同的转出资源数据，生成所述待处理资源数据；
    在所述综合转入资源数据的数量和类型与所述待处理资源数据的数量和类型相 同的情况下，将所述待处理资源数据中转到所述区块链***的中转节点。
  8. 一种资源数据的转移装置，包括：
    中转单元，用于响应于区块链***中发起节点的资源数据转移请求，将所述资源数据转移请求相应的待处理资源数据中转到所述区块链***的中转节点；
    存储单元，用于生成与本次中转过程相应的中转信息，存储在所述区块链***中，所述中转信息包括本次中转过程中所述发起节点的信息、所述待处理资源数据的指定接收节点的信息；
    转移单元，用于根据所述发起节点或当前接收节点发出的与所述资源数据转移请求相应的资源数据处理请求，以及从所述区块链***中获取的所述中转信息，确定是否对所述中转节点中的所述待处理资源数据进行转移。
  9. 根据权利要求8所述的转移装置，其中，
    所述发起节点为多个，各发起节点的资源数据转移请求对应的待处理资源数据为多批；
    所述存储单元根据各综合输出资源数据的相关信息，生成与本次转移过程相应的转移信息，存储在所述区块链***中；
    还包括：
    合并单元，用于将所述中转节点从各发起节点接收的每批待处理资源数据，确定为本次转移过程的各输入资源数据，将所述中转节点转移给当前接收节点的每批相应资源数据，确定为本次转移过程的各输出资源数据，所述各输出资源数据分别来源于相应的输入资源数据，将具有相同发起节点的各输入资源数据的相应的输出资源数据合并为一批综合输出资源数据。
  10. 根据权利要求8所述的转移装置，还包括：
    合并单元，用于获取所述发起节点在历史资源数据转移过程中，来源于其他节点的各转入资源数据的数量和类型，合并来源于相同其他节点且类型相同的转入资源数据，生成综合转入资源数据，获取所述发起节点在本次中转过程中，拟转给所述中转节点的转出资源数据的数量和类型，合并类型相同的转出资源数据，生成所述待处理资源数据；
    其中，所述中转单元在所述综合转入资源数据的数量和类型与所述待处理资源数据的数量和类型相同的情况下，将所述待处理资源数据中转到所述区块链***的中转节点。
  11. 一种资源数据的转移装置，包括：
    存储器；和
    耦接至所述存储器的处理器，所述处理器被配置为基于存储在所述存储器中的指令，执行权利要求1-7任一项所述资源数据的转移方法。
  12. 一种计算机可读存储介质，其上存储有计算机程序，该程序被处理器执行时实现权利要求1-7任一项所述资源数据的转移方法。
  13. 一种区块链***，包括：
    权利要求8-11任一项所述资源数据的转移装置。
PCT/CN2020/092029 2019-10-15 2020-05-25 资源数据的转移方法、装置和区块链*** WO2021073096A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910976320.3 2019-10-15
CN201910976320.3A CN110704196B (zh) 2019-10-15 2019-10-15 资源数据的转移方法、装置和区块链***

Publications (1)

Publication Number Publication Date
WO2021073096A1 true WO2021073096A1 (zh) 2021-04-22

Family

ID=69199588

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/092029 WO2021073096A1 (zh) 2019-10-15 2020-05-25 资源数据的转移方法、装置和区块链***

Country Status (2)

Country Link
CN (1) CN110704196B (zh)
WO (1) WO2021073096A1 (zh)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110704196B (zh) * 2019-10-15 2021-03-30 京东数字科技控股有限公司 资源数据的转移方法、装置和区块链***
CN111309711A (zh) * 2020-03-13 2020-06-19 财付通支付科技有限公司 跨区块链的数据迁移方法、装置、设备及存储介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109146681A (zh) * 2018-07-26 2019-01-04 百度在线网络技术（北京）有限公司 一种区块链的元素处理方法、装置、设备和存储介质
CN110210732A (zh) * 2019-05-20 2019-09-06 平安银行股份有限公司 资源转移方法、装置、计算机设备和存储介质
CN110704196A (zh) * 2019-10-15 2020-01-17 京东数字科技控股有限公司 资源数据的转移方法、装置和区块链***

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105427169B (zh) * 2014-09-17 2021-05-11 ***股份有限公司 用于资源转移的安全性信息交互方法
CN105847308A (zh) * 2015-01-12 2016-08-10 阿里巴巴集团控股有限公司 一种资源信息的转移处理方法和装置
CN107292688A (zh) * 2016-03-31 2017-10-24 阿里巴巴集团控股有限公司 一种业务处理方法及装置
CN109285069B (zh) * 2017-07-19 2022-11-15 腾讯科技（深圳）有限公司 资源转移方法、装置及服务器
US10643202B2 (en) * 2017-07-25 2020-05-05 Bank Of America Corporation Real-time processing distributed ledger system
US20190188706A1 (en) * 2017-12-18 2019-06-20 Apple Inc. Transference tracking
CN109064145A (zh) * 2018-07-25 2018-12-21 中国农业银行股份有限公司 一种基于区块链的资产转移方法及装置
CN109102299A (zh) * 2018-08-01 2018-12-28 腾讯科技（深圳）有限公司 资源转移数据管理方法、装置及存储介质

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109146681A (zh) * 2018-07-26 2019-01-04 百度在线网络技术（北京）有限公司 一种区块链的元素处理方法、装置、设备和存储介质
CN110210732A (zh) * 2019-05-20 2019-09-06 平安银行股份有限公司 资源转移方法、装置、计算机设备和存储介质
CN110704196A (zh) * 2019-10-15 2020-01-17 京东数字科技控股有限公司 资源数据的转移方法、装置和区块链***

Also Published As

Publication number Publication date
CN110704196A (zh) 2020-01-17
CN110704196B (zh) 2021-03-30

Similar Documents

Publication Publication Date Title
TWI705346B (zh) 基於中心化結算與區塊鏈存證的交易方法及系統
US20230004537A1 (en) Extracting data from a blockchain network
CN107395353B (zh) 一种区块链共识方法及装置
US11281457B2 (en) Deployment of infrastructure in pipelines
CN110597925B (zh) 一种基于区块链的跨链数据处理方法及装置
CN108595157B (zh) 区块链数据的处理方法、装置、设备和存储介质
US20190116185A1 (en) Access authority management method, access authority management system, and access authority management apparatus
US20210406798A1 (en) Business process decomposition and modular reusable process automation system
US8620713B2 (en) Mechanism to control delegation and revocation of tasks in workflow system
US9483386B2 (en) Information interaction test device and method based on automatic generation of associated test cases
US20200274712A1 (en) Ledger-independent token service
US9613330B2 (en) Identity and access management
CN110874739A (zh) 实现高完整性、高带宽、低延迟、安全处理的分布式计算和存储网络
WO2021082340A1 (zh) 数据处理方法、装置、***和存储介质
US9697042B2 (en) Extensibility of business process and application logic
US11151122B2 (en) Distributed ledger data linkage management
WO2021073096A1 (zh) 资源数据的转移方法、装置和区块链***
US20200402031A1 (en) Systems and methods for generating smart contracts to manage escrow transactions
WO2020238250A1 (zh) 资金链信息追溯方法、***、服务器和可读存储介质
GB2586470A (en) Systems and methods for generating smart contracts to manage escrow transactions
US20140380267A1 (en) Lifecycle management system with conditional approvals and corresponding method
US10809992B1 (en) Method and apparatus for continuous delivery of permissioned blockchain application
KR102431835B1 (ko) 토큰 모델링 장치 및 이를 포함하는 데이터 무결성 검증 시스템 및 방법
CN112181599A (zh) 模型训练方法、装置及存储介质
JP7460348B2 (ja) ブロックチェーンの拡張を可能にするトランザクション処理システムおよび方法

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: 20877013

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 09.08.2022)

122 Ep: pct application non-entry in european phase

Ref document number: 20877013

Country of ref document: EP

Kind code of ref document: A1