WO2020155832A1 - 跨链用权***及方法、装置、电子设备、存储介质 - Google Patents

跨链用权***及方法、装置、电子设备、存储介质 Download PDF

Info

Publication number
WO2020155832A1
WO2020155832A1 PCT/CN2019/122127 CN2019122127W WO2020155832A1 WO 2020155832 A1 WO2020155832 A1 WO 2020155832A1 CN 2019122127 W CN2019122127 W CN 2019122127W WO 2020155832 A1 WO2020155832 A1 WO 2020155832A1
Authority
WO
WIPO (PCT)
Prior art keywords
blockchain
cross
chain
attribution data
relay
Prior art date
Application number
PCT/CN2019/122127
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 阿里巴巴集团控股有限公司
Priority to SG11202104281TA priority Critical patent/SG11202104281TA/en
Priority to EP19912920.6A priority patent/EP3859648A4/en
Publication of WO2020155832A1 publication Critical patent/WO2020155832A1/zh
Priority to US17/245,730 priority patent/US20210248605A1/en

Links

Images

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
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/382—Payment protocols; Details thereof insuring higher security of transaction
    • G06Q20/3825—Use of electronic signatures
    • 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/04—Payment circuits
    • G06Q20/06—Private payment circuits, e.g. involving electronic currency used among participants of a common payment scheme
    • G06Q20/065—Private payment circuits, e.g. involving electronic currency used among participants of a common payment scheme using e-cash
    • G06Q20/0658—Private payment circuits, e.g. involving electronic currency used among participants of a common payment scheme using e-cash e-cash managed locally
    • 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
    • G06Q20/4014—Identity check for transactions
    • 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
    • G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/04—Trading; Exchange, e.g. stocks, commodities, derivatives or currency exchange
    • 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
    • G06Q50/00—Information and communication technology [ICT] specially adapted for implementation of business processes of specific business sectors, e.g. utilities or tourism
    • G06Q50/10—Services
    • G06Q50/18—Legal services
    • G06Q50/184—Intellectual property management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
    • H04L9/3236—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials using cryptographic hash functions
    • H04L9/3239—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials using cryptographic hash functions involving non-keyed hash functions, e.g. modification detection codes [MDCs], MD5, SHA or RIPEMD
    • 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
    • G06Q2220/00—Business processing using cryptography
    • G06Q2220/10—Usage protection of distributed data files
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L2209/00—Additional information or applications relating to cryptographic mechanisms or cryptographic arrangements for secret or secure communication H04L9/00
    • H04L2209/56—Financial cryptography, e.g. electronic payment or e-cash
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/50—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols using hash chains, e.g. blockchains or hash trees

Definitions

  • One or more embodiments of this specification relate to the field of blockchain technology, and in particular to a cross-chain usage right system and method, device, electronic equipment, and storage medium.
  • Blockchain technology (also known as distributed ledger technology) is a de-neutralized distributed database technology, which has the characteristics of decentralization, openness and transparency, non-tampering, trustworthiness, etc., and is suitable for many In application scenarios with high demand for data reliability.
  • one or more embodiments of this specification provide a cross-chain usage right system, method, device, electronic device, and storage medium.
  • a cross-chain usage rights system including:
  • One or more certificate deposit blockchains where the certificate deposit blockchain is used to deposit the right attribution data;
  • One or more usage rights blockchains which are used to process rights application services
  • At least one cross-chain relay and each cross-chain relay is respectively connected to at least one deposit blockchain and at least one right-use blockchain; the cross-chain relay reads the right attribution data on the deposit blockchain, In response to the use of the right block chain to initiate a right confirmation request, the right use block chain will process the corresponding right application business according to the response result.
  • a method for cross-chain usage rights is proposed, which is applied to cross-chain relays, and the cross-chain relays are respectively connected to at least one evidence block chain and at least one usage right.
  • Right blockchain the method includes:
  • a cross-chain right-use method is proposed, which is applied to blockchain nodes on the right-use blockchain, and the right-use blockchain is connected to the cross-chain Then, the cross-chain relay is also connected to at least one attestation block chain; the method includes:
  • the right application service is processed according to the response result returned by the cross-chain relay.
  • a cross-chain right-use device which is applied to cross-chain relays, and the cross-chain relays are respectively connected to at least one evidence-based blockchain and at least one Right blockchain; the device includes:
  • the receiving unit receives the right-use block chain to initiate a right confirmation request for the right application business
  • the reading unit reads the right attribution data of the deposit certificate on the deposit blockchain
  • the response unit responds to the right confirmation request according to the right attribution data, so that the right use blockchain processes the right application service according to the response result.
  • a cross-chain right-use device which is applied to a blockchain node on a right-use block chain, and the right-use block chain is connected to the cross-chain Then, the cross-chain relay is also connected to at least one attestation block chain; the device includes:
  • the requesting unit initiates a right confirmation request to the cross-chain relay for the right application service, so that the cross-chain relay can read the right attribution data stored on the attribution block chain and compare the right attribution data according to the right attribution data. Respond to the right confirmation request;
  • the processing unit processes the right application service according to the response result returned by the cross-chain relay.
  • an electronic device including:
  • a memory for storing processor executable instructions
  • the processor executes the executable instruction to implement the method according to the second or third aspect.
  • a computer-readable storage medium which stores computer instructions, which when executed by a processor, implements the method described in the second or third aspect step.
  • Fig. 1 is a schematic diagram of an example environment provided by an example embodiment.
  • Fig. 2 is a schematic diagram of a conceptual architecture provided by an exemplary embodiment.
  • Fig. 3 is a flowchart of a method for cross-chain usage rights provided by an exemplary embodiment.
  • Fig. 4 is a flowchart of another method for cross-chain usage rights provided by an exemplary embodiment.
  • Fig. 5 is a schematic structural diagram of a cross-chain usage rights system provided by an exemplary embodiment.
  • Fig. 6 is a schematic structural diagram of a device provided by an exemplary embodiment.
  • Fig. 7 is a block diagram of a device for cross-chain usage rights provided by an exemplary embodiment.
  • Fig. 8 is a schematic structural diagram of another device provided by an exemplary embodiment.
  • Fig. 9 is a block diagram of another cross-chain usage right device provided by an exemplary embodiment.
  • the steps of the corresponding method may not be executed in the order shown and described in this specification.
  • the method includes more or fewer steps than described in this specification.
  • a single step described in this specification may be decomposed into multiple steps for description in other embodiments; and multiple steps described in this specification may also be combined into a single step in other embodiments. description.
  • Fig. 1 is a schematic diagram of an example environment provided by an example embodiment.
  • the example environment 100 allows entities to participate in the blockchain network 102.
  • the blockchain network 102 may be a public, private, or consortium blockchain network.
  • the example environment 100 may include computing devices 104, 106, 108, 110, 112, and a network 114; in an embodiment, the network 114 may include a local area network (LAN), a wide area network (Wide Area Network, WAN), the Internet, or It is combined and connected to websites, user devices (such as computing devices) and back-end systems.
  • the network 114 may be accessed through wired and/or wireless communication.
  • the computing devices 106, 108 may be nodes of a cloud computing system (not shown), or each computing device 106, 108 may be a separate cloud computing system, including being interconnected by a network and acting as a distributed processing system Multiple computers at work.
  • the computing devices 104-108 can run any appropriate computing system to enable them to serve as nodes in the blockchain network 102; for example, the computing devices 104-108 can include, but are not limited to, servers, desktop computers, and notebooks. Computers, tablet computing devices and smartphones.
  • the computing devices 104 to 108 may be attributed to related entities and used to implement corresponding services. For example, the service may be used to manage transactions between a certain entity or multiple entities.
  • the computing devices 104-108 respectively store the blockchain ledger corresponding to the blockchain network 102.
  • the computing device 104 may be (or include) a web server for providing a browser function, and the web server may provide visual information related to the blockchain network 102 based on the network 114.
  • the computing device 104 may not participate in block verification, but monitor the blockchain network 102 to determine when other nodes (for example, computing devices 106-108 may include) reached a consensus, and generate corresponding blocks accordingly Chain visual user interface.
  • the computing device 104 may receive a request initiated by a client device (such as the computing device 110 or the computing device 112) for the blockchain visualization user interface.
  • a client device such as the computing device 110 or the computing device 112
  • the nodes of the blockchain network 102 can also serve as client devices.
  • a user of the computing device 108 can use a browser running on the computing device 108 to send the aforementioned request to the computing device 104.
  • the computing device 104 may generate a blockchain visual user interface (such as a web page) based on the stored blockchain ledger, and send the generated blockchain visual user interface to the requesting client device.
  • the request for the blockchain visualization user interface may include user authorization information, before generating the blockchain visualization user interface and sending it to the requesting client device ,
  • the computing device 104 may verify the user authorization information, and return to the corresponding blockchain visual user interface after the verification is passed.
  • the blockchain visual user interface may be displayed on the client device (for example, it may be displayed in the user interface 116 shown in FIG. 1).
  • the display content of the user interface 116 can also be updated accordingly.
  • the user's interaction with the user interface 116 may result in requests for other user interfaces, such as displaying block list, block details, transaction list, transaction details, account list, account details, contract list, contract details, or user requests for blocks
  • the search result page generated by the implementation of the search on the chain network, etc.
  • Fig. 2 is a schematic diagram of a conceptual architecture provided by an exemplary embodiment.
  • the conceptual architecture 200 includes a physical layer 202, a managed service layer 204 and a blockchain network layer 206.
  • the entity layer 202 may include three entities: entity 1, entity 2 and entity 3, and each entity has its own transaction management system 208.
  • the managed service layer 204 may include an interface 210 corresponding to each transaction management system 208.
  • each transaction management system 208 uses a protocol (such as Hypertext Transfer Protocol Security (HTTPS), etc.) to communicate with the respective interface 210 through a network (such as the network 114 in FIG. 1).
  • HTTPS Hypertext Transfer Protocol Security
  • each interface 210 may provide a communication connection between its corresponding transaction management system 208 and the blockchain network layer 206; more specifically, the interface 210 may be connected to the blockchain network of the blockchain network layer 206 212 communications.
  • the communication between the interface 210 and the blockchain network layer 206 may be implemented using remote procedure calls (RPCs).
  • the interface 210 may provide the transaction management system 208 with an API interface for accessing the blockchain network 212.
  • the blockchain network 212 is provided in the form of a peer-to-peer network.
  • the peer-to-peer network includes a plurality of nodes 214, each of which is used to persist the blockchain ledger 216 formed by the blockchain data; Wherein, only one block chain ledger 216 is shown in FIG. 2, but there may be multiple block chain ledger 216 or copies thereof in the block chain network 212.
  • each node 214 can maintain a block chain separately Ledger 216 or a copy thereof.
  • a transaction in a narrow sense refers to a transfer of value issued by a user to the blockchain; for example, in a traditional Bitcoin blockchain network, a transaction can be a transfer initiated by the user in the blockchain.
  • a transaction refers to a piece of business data with business intent released by a user to the blockchain; for example, an operator can build a consortium chain based on actual business needs, and rely on the consortium chain to deploy some other types that are not related to value transfer Online business (for example, renting business, vehicle scheduling business, insurance claims business, credit service, medical service, etc.), and in this kind of alliance chain, the transaction can be a business with business intent issued by the user in the alliance chain Message or business request.
  • value transfer Online business for example, renting business, vehicle scheduling business, insurance claims business, credit service, medical service, etc.
  • Fig. 3 is a flowchart of a method for cross-chain usage rights provided by an exemplary embodiment. As shown in Fig. 3, this method is applied to cross-chain relays, which are respectively connected to at least one deposit block chain and at least one right block chain; the method may include the following steps:
  • Step 302 Receive a right confirmation request initiated by the right-use blockchain for the right application service.
  • the cross-chain relay is used to implement a relay function between the right-use block chain and the attestation blockchain, so that the right-use blockchain can communicate with the attestation blockchain through the cross-chain relay. Access, thereby realizing the docking between the right-use block chain and the deposit block chain.
  • the right-use block chain and the deposit certificate block chain are respectively connected to the cross-chain relay, instead of between the right-use block chain and the deposit block chain. Direct docking can increase or decrease the right-use block chain and the certificate block chain connected to the cross-chain relay according to actual needs, so the entire system has excellent scalability.
  • the blockchain client can send a request instruction to at least one blockchain node on the right-using blockchain based on the user's instruction, so that the at least one blockchain node can initiate a corresponding confirmation request to the cross-chain relay ;
  • the blockchain client can submit a transaction proposal to at least one blockchain node on the right-use blockchain, so that the transaction proposal can initiate the above to the cross-chain relay when the transaction proposal is passed through consensus and executed Confirmation request;
  • the blockchain client can submit a transaction proposal to at least one blockchain node on the rights-using blockchain, so that the transaction proposal can call the smart contract when the transaction proposal passes consensus and is executed ,
  • the smart contract can be used to automatically initiate the above confirmation request to the cross-chain relay, and the smart contract can further determine whether to perform related operations based on the
  • Step 304 Read the right attribution data of the deposit certificate on the deposit blockchain.
  • the deposit blockchain is used to deposit the right ownership data, and the right ownership data is used to record the ownership of related rights; taking book copyright as an example, it can record the relationship between the book copyright and the owner. Mapping relationship, for example, a certain user A owns the copyright of book B, and a certain enterprise C owns the copyright of book D, etc.
  • the deposit certificate blockchain adopts distributed database technology, that is, several blockchain nodes jointly maintain a unified blockchain ledger, and the blocks contained in the blockchain ledger are realized as a content-related blockchain structure. It makes the blockchain ledger of the deposit blockchain have the characteristics of being open and non-tamperable, so as to realize the safe and reliable deposit function.
  • the rights in this specification may also include other types, such as song copyright, movie copyright, software copyright, patent right, real property rights, etc. This specification does not limit this.
  • Step 306 Respond to the right confirmation request according to the right attribution data, so that the right-using blockchain processes the right application service according to the response result.
  • the cross-chain relay may determine whether the target right indicated in the right confirmation request belongs to the target object according to the right attribution data, and return the judgment result to the right-use blockchain.
  • the response result received by the right-use block link contains the above-mentioned judgment result, so that the right-use block chain can process the rights application business accordingly.
  • the cross-chain relay can obtain the right attribution data and return the right attribution data to the right-use blockchain, so that the right-use blockchain can determine whether the target right belongs to the target.
  • the right-use blockchain can obtain the right attribution data, so that the blockchain node on the right-use blockchain can determine whether the target right belongs to the target object based on the right attribution data, and the cross-chain relay is only used to obtain The rights attribution data are provided to the usage rights blockchain.
  • FIG. 4 is a flowchart of another method for cross-chain usage rights provided by an exemplary embodiment. As shown in Figure 4, this method is applied to a blockchain node on a right-use block chain.
  • the right-use block chain is connected to a cross-chain relay, and the cross-chain relay is also connected to at least one proof block Chain; the method may include the following steps:
  • Step 402 Initiate a right confirmation request to the cross-chain relay for the right application service, so that the cross-chain relay can read the right attribution data stored on the attribution blockchain and compare the right attribution data based on the right attribution data. Respond to the right confirmation request.
  • the cross-chain relay is used to implement a relay function between the right-use block chain and the attestation blockchain, so that the right-use blockchain can communicate with the attestation blockchain through the cross-chain relay. Access, thereby realizing the docking between the right-use block chain and the deposit block chain.
  • the right-use block chain and the deposit certificate block chain are respectively connected to the cross-chain relay, instead of between the right-use block chain and the deposit block chain. Direct docking can increase or decrease the right-use block chain and the certificate block chain connected to the cross-chain relay according to actual needs, so the entire system has excellent scalability.
  • the blockchain client can send a request instruction to at least one blockchain node on the right-using blockchain based on the user's instruction, so that the at least one blockchain node can initiate a corresponding confirmation request to the cross-chain relay ;
  • the blockchain client can submit a transaction proposal to at least one blockchain node on the right-use blockchain, so that the transaction proposal can initiate the above to the cross-chain relay when the transaction proposal is passed through consensus and executed Confirmation request;
  • the blockchain client can submit a transaction proposal to at least one blockchain node on the rights-using blockchain, so that the transaction proposal can call the smart contract when the transaction proposal passes consensus and is executed ,
  • the smart contract can be used to automatically initiate the above confirmation request to the cross-chain relay, and the smart contract can further determine whether to perform related operations based on the
  • the deposit blockchain is used to deposit the right ownership data, and the right ownership data is used to record the ownership of related rights; taking book copyright as an example, it can record the relationship between the book copyright and the owner. Mapping relationship, for example, a certain user A owns the copyright of book B, and a certain enterprise C owns the copyright of book D, etc.
  • the deposit certificate blockchain adopts distributed database technology, that is, several blockchain nodes jointly maintain a unified blockchain ledger, and the blocks contained in the blockchain ledger are realized as a content-related blockchain structure. It makes the blockchain ledger of the deposit blockchain have the characteristics of being open and non-tamperable, so as to realize the safe and reliable deposit function.
  • the rights in this specification may also include other types, such as song copyright, movie copyright, software copyright, patent right, real property rights, etc. This specification does not limit this.
  • Step 404 Process the rights application service according to the response result returned by the cross-chain relay.
  • the cross-chain relay may determine whether the target right indicated in the right confirmation request belongs to the target object according to the right attribution data, and return the judgment result to the right-use blockchain.
  • the response result received by the right block link includes the above judgment result, so that the right block chain can process the rights application business accordingly.
  • the cross-chain relay can obtain the right attribution data and return the right attribution data to the right-use blockchain, so that the right-use blockchain can determine whether the target right belongs to the target.
  • the right-use blockchain can obtain the right attribution data, so that the blockchain node on the right-use blockchain can determine whether the target right belongs to the target object based on the right attribution data, and the cross-chain relay is only used to obtain The rights attribution data are provided to the usage rights blockchain.
  • the blockchain node on the right-using blockchain can generate confirmation information according to the response result, and the confirmation information indicates that the target right belongs to the target object; then, the blockchain node can report The right-using blockchain submits a blockchain transaction corresponding to the right application service, and the blockchain transaction includes the right confirmation information.
  • a blockchain transaction that does not contain confirmation information will not be able to pass consensus;
  • the confirmation information is used as a prerequisite for the successful execution of the blockchain transaction One; for another example, by including the confirmation information in the blockchain transaction, it can be used as one of the validity proofs of the blockchain transaction, and the blockchain transaction that does not contain the confirmation information will be determined as an invalid transaction.
  • the blockchain node of the right-using blockchain can submit a blockchain transaction corresponding to the right application service to the right-using blockchain, and the blockchain transaction includes a call to a smart contract Information to execute the blockchain transaction through the smart contract; accordingly, the blockchain node can initiate the confirmation request to the cross-chain relay by invoking the smart contract; and, the zone The block chain node can provide the response result to the smart contract, so that the smart contract executes the blockchain transaction according to the response result.
  • the smart contract can be executed when the response result indicates that the target right belongs to the target object.
  • the transaction operation indicated by the blockchain exchange otherwise avoid executing the transaction operation.
  • the transaction described in this manual refers to a piece of data created by a user through the client of the blockchain and need to be finally released to the distributed database of the blockchain.
  • transactions in the blockchain are divided into narrow transactions and broad transactions.
  • a transaction in a narrow sense refers to a transfer of value issued by a user to the blockchain; for example, in a traditional Bitcoin blockchain network, a transaction can be a transfer initiated by the user in the blockchain.
  • a transaction refers to a piece of business data with business intent released by a user to the blockchain; for example, an operator can build a consortium chain based on actual business needs, and rely on the consortium chain to deploy some other types that are not related to value transfer Online business (for example, copyright business, rental business, vehicle dispatch business, insurance claims business, credit service, medical service, etc.), and in this kind of alliance chain, the transaction can be a transaction issued by the user in the alliance chain. Intent business message or business request.
  • Fig. 5 is a schematic structural diagram of a cross-chain usage rights system provided by an exemplary embodiment.
  • the system may include: one or more deposit blockchains, one or more usage rights blockchains, and at least one cross-chain relay.
  • the deposit blockchain may include blockchain 511 , 512, 513, and 514
  • the right block chain can include block chains 531, 532, and 533
  • the cross-chain relay can include relays 521, 522.
  • Blockchains 511-514 are used to store the rights attribution data; in the book copyright scenario, the rights attribution data is used to indicate the attribution of the book copyright, for example, a certain book copyright T1 belongs to the user UA and another book copyright T2 belongs to enterprise UB, etc.
  • These rights attribution data may be due to privacy requirements (for example, different blockchains are used to store rights attribution data of different privacy requirements), business isolation (for example, personal business and company business, educational book business and Science and technology book business, etc.), alliances of participants (for example, different alliances adopt different deposit blockchains, and each deposit blockchain only stores the rights attribution data provided by the participants of the corresponding alliance). Proof in different deposit blockchains.
  • the blockchain nodes on the blockchains 511 to 514 can respectively agree on the submitted copyright data, and use the consensus copyright data in any form such as key-value pairs or other arbitrary forms not limited by this manual. Save as the corresponding right attribution data, so that the right attribution data is recorded in the blockchain ledger of the corresponding blockchain, so that the right attribution data can be stored. Therefore, when the cross-chain relay 521 or 522 reads the rights attribution data from the blockchain ledgers of the blockchains 511 to 514, it can ensure that the attribution of the book copyright described by the rights attribution data is true and effective, so that the right to use Blockchain can process related rights application business accordingly.
  • the cross-chain relay 521-522 is used to realize the data connection between the blockchain 511-514 and the blockchain 531-533, so that the blockchain 531-533 can pass through the cross-chain relay 521-522 Access to the rights attribution data stored in the blockchains 511 to 514 to determine the processing methods for the related rights application services.
  • the blockchains 531-533, etc., as the right-use blockchain are used to access the rights attribution data stored in the blockchains 511-514 through the cross-chain relay 521-522 according to actual business needs.
  • the number of right-to-use blockchains can be as many as shown in Figure 5 (such as blockchains 531 to 533). Of course, this manual is incorrect. This is limited.
  • the staff on the UX side of the enterprise can operate the computing device 540 so that the computing device 540 can submit a transaction proposal to the blockchain node 532a in the blockchain 532, and the transaction proposal is for the paintings held by the user UA It is initiated by K and used to pay the user UA an asset certificate of amount i after confirming that the user UA owns the book copyright of the painting K.
  • the blockchain node 532a can publish the transaction proposal in the blockchain 532 so that the transaction proposal can be executed in the blockchain 532. Since the transaction proposal needs to complete two steps: the first step is to verify that the user UA owns the book copyright of the painting K, and the second step is to use the enterprise UX to pay the user UA an asset certificate with an amount of i, then a smart contract can be predefined And make the transaction proposal call the smart contract, so that the smart contract can automatically and efficiently complete the above two-step operation without external influence.
  • the smart contract may initiate a right confirmation request to the cross-chain relay 521 or 522, and the right confirmation request is used to request to verify whether the user UA owns the book copyright of the painting K.
  • the smart contract sends the confirmation request to the cross-chain relay 521, then the cross-chain relay 521 can be based on the cross-chain technology in related technologies (such as side-chain technology, notary technology, etc., which is not restricted in this specification), Read the right attribution data stored in the blockchains 511-514 to verify whether the user UA owns the book copyright of the painting K according to the right attribution data.
  • the cross-chain The relay 521 can directly read the ownership data of the rights deposited in the blockchain 511-512, and verify whether the user UA owns the book copyright of the painting K; when the ownership of the book copyright of the painting K is recorded in the blockchain 513 or 514
  • the cross-chain relay 521 can read through the data channel between the cross-chain relay 522 and The right attribution data of the blockchain 513-514 is used to verify whether the user UA owns the book copyright of the painting K.
  • the cross-chain relay 522 can also verify whether the user UA owns the book copyright of the painting K and inform the cross-border of the verification result.
  • Chain relay 521 since the cross-chain relay 521 in Figure 5 is directly connected to the blockchain 511-512, the cross-chain The relay 521 can directly read the ownership data of the rights deposited in the blockchain 511-512, and verify whether the user UA owns the book copyright of the painting K; when the ownership of the book copyright of the painting K is recorded in the blockchain 513 or 5
  • the cross-chain relay 521 can obtain the corresponding verification result and send it to the above
  • the smart contract returns the corresponding verification result.
  • the smart contract can complete the second step of the above operation when the verification result shows that the user UA owns the book copyright of the painting K, that is, the enterprise UX pays the user UA the asset certificate with the amount i, for example, the area corresponding to the enterprise UX
  • the blockchain account reduces the asset certificate with the amount i, so that the blockchain account corresponding to the user UA increases the asset certificate with the amount i.
  • the smart contract can refuse to perform the second step above, for example, it can be determined that the second step has failed.
  • Fig. 6 is a schematic structural diagram of a device provided by an exemplary embodiment.
  • the device includes a processor 602, an internal bus 604, a network interface 606, a memory 608, and a non-volatile memory 610, and of course, it may also include hardware required for other services.
  • the processor 602 reads the corresponding computer program from the non-volatile memory 610 to the memory 608 and then runs it to form a cross-chain right-use device at the logical level.
  • one or more embodiments of this specification do not exclude other implementations, such as logic devices or a combination of software and hardware, etc. That is to say, the execution subject of the following processing flow is not limited to each
  • the logic unit can also be a hardware or logic device.
  • the cross-chain right-use device is applied to cross-chain relays, and the cross-chain relays are respectively connected to at least one attestation block chain and at least one right block chain;
  • the device may include:
  • the receiving unit 71 receives a right-use block chain to initiate a right confirmation request for the right application business
  • the reading unit 72 reads the right attribution data of the certificate on the deposit blockchain
  • the response unit 73 responds to the right confirmation request according to the right attribution data, so that the right use blockchain processes the right application service according to the response result.
  • the response unit 73 is specifically configured to:
  • the right attribution data determine whether the target right indicated in the right confirmation request belongs to the target object
  • the response unit 73 is specifically configured to:
  • the right attribution data is returned to the right block chain, so that the right block chain determines whether the target right belongs to the target object.
  • Fig. 8 is a schematic structural diagram of a device provided by an exemplary embodiment. Please refer to FIG. 8.
  • the device includes a processor 802, an internal bus 804, a network interface 806, a memory 808, and a non-volatile memory 810.
  • the processor 802 reads the corresponding computer program from the non-volatile memory 810 to the memory 808 and then runs it to form a cross-chain right-use device on a logical level.
  • one or more embodiments of this specification do not exclude other implementations, such as logic devices or a combination of software and hardware, etc. That is to say, the execution subject of the following processing flow is not limited to each
  • the logic unit can also be a hardware or logic device.
  • the cross-chain right-use device is applied to the blockchain node on the right-use block chain, and the right-use block chain is connected to the cross-chain relay.
  • At least one depository blockchain is further connected; the device may include:
  • the requesting unit 91 initiates a right confirmation request to the cross-chain relay for the right application service, so that the cross-chain relay can read the right attribution data stored on the attribution blockchain and pair according to the right attribution data Respond to the right confirmation request;
  • the processing unit 92 processes the rights application service according to the response result returned by the cross-chain relay.
  • processing unit 92 is specifically configured to:
  • a submission unit 93 which submits a blockchain transaction corresponding to the rights application service to the right-use blockchain, the blockchain transaction including call information to a smart contract to be executed by the smart contract The blockchain transaction;
  • the request unit 91 is specifically configured to: initiate the right confirmation request to the cross-chain relay by invoking the smart contract;
  • the processing unit 92 is specifically configured to provide the response result to the smart contract, so that the smart contract executes the blockchain transaction according to the response result.
  • the response result includes: a judgment result generated by the cross-chain relay according to the right attribution data, and the judgment result is used to indicate whether the target right belongs to the target object.
  • processing unit 92 is specifically configured to:
  • a typical implementation device is a computer.
  • the specific form of the computer can be a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email receiving and sending device, and a game control A console, a tablet computer, a wearable device, or a combination of any of these devices.
  • a computer includes one or more processors (CPU), input/output interfaces, network interfaces, and memory.
  • processors CPU
  • input/output interfaces network interfaces
  • memory volatile and non-volatile memory
  • the memory may include non-permanent memory in a computer readable medium, random access memory (RAM) and/or non-volatile memory, such as read-only memory (ROM) or flash memory (flash RAM). Memory is an example of computer readable media.
  • RAM random access memory
  • ROM read-only memory
  • flash RAM flash memory
  • Computer-readable media includes permanent and non-permanent, removable and non-removable media, and information storage can be realized by any method or technology.
  • the information can be computer-readable instructions, data structures, program modules, or other data.
  • Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, CD-ROM, digital versatile disc (DVD) or other optical storage, Magnetic cassettes, disk storage, quantum memory, graphene-based storage media or other magnetic storage devices or any other non-transmission media can be used to store information that can be accessed by computing devices. According to the definition in this article, computer-readable media does not include transitory media, such as modulated data signals and carrier waves.
  • first, second, third, etc. may be used to describe various information in one or more embodiments of this specification, the information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other.
  • first information may also be referred to as second information, and similarly, the second information may also be referred to as first information.
  • word “if” as used herein can be interpreted as "when” or “when” or "in response to determination”.

Landscapes

  • Engineering & Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Theoretical Computer Science (AREA)
  • Accounting & Taxation (AREA)
  • General Physics & Mathematics (AREA)
  • Physics & Mathematics (AREA)
  • Strategic Management (AREA)
  • Finance (AREA)
  • General Business, Economics & Management (AREA)
  • Computer Security & Cryptography (AREA)
  • Databases & Information Systems (AREA)
  • Technology Law (AREA)
  • Economics (AREA)
  • Tourism & Hospitality (AREA)
  • Marketing (AREA)
  • General Engineering & Computer Science (AREA)
  • Data Mining & Analysis (AREA)
  • Computing Systems (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Operations Research (AREA)
  • Primary Health Care (AREA)
  • Health & Medical Sciences (AREA)
  • Entrepreneurship & Innovation (AREA)
  • General Health & Medical Sciences (AREA)
  • Human Resources & Organizations (AREA)
  • Development Economics (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

一种跨链用权***及方法、装置、电子设备、存储介质，该***可以包括：一条或多条存证区块链（511，512，513，514），所述存证区块链（511，512，513，514）用于对权利归属数据进行存证；一条或多条用权区块链（531，532，533），所述用权区块链（531，532，533）用于处理权利应用业务；至少一个跨链中继（521，522），每一跨链中继（521，522）分别连接至少一条存证区块链（511，512，513，514）、至少一条用权区块链（531，532，533）；所述跨链中继（521，522）读取存证区块链（511，512，513，514）上的权利归属数据，以响应于用权区块链（531，532，533）发起的确权请求，使得用权区块链（531，532，533）根据响应结果对相应的权利应用业务进行处理。

Description

跨链用权***及方法、装置、电子设备、存储介质 技术领域
本说明书一个或多个实施例涉及区块链技术领域，尤其涉及一种跨链用权***及方法、装置、电子设备、存储介质。
背景技术
区块链技术(也被称之为，分布式账本技术)是一种去中性化的分布式数据库技术，具有去中心化、公开透明、不可篡改、可信任等多种特点，适用于诸多对数据可靠性具有高需求的应用场景中。
发明内容
有鉴于此，本说明书一个或多个实施例提供一种跨链用权***及方法、装置、电子设备、存储介质。
为实现上述目的，本说明书一个或多个实施例提供技术方案如下：
根据本说明书一个或多个实施例的第一方面，提出了一种跨链用权***，包括：
一条或多条存证区块链，所述存证区块链用于对权利归属数据进行存证；
一条或多条用权区块链，所述用权区块链用于处理权利应用业务；
至少一个跨链中继，每一跨链中继分别连接至少一条存证区块链、至少一条用权区块链；所述跨链中继读取存证区块链上的权利归属数据，以响应于用权区块链发起的确权请求，使得用权区块链根据响应结果对相应的权利应用业务进行处理。
根据本说明书一个或多个实施例的第二方面，提出了一种跨链用权方法，应用于跨链中继，所述跨链中继分别连接至少一条存证区块链、至少一条用权区块链；所述方法包括：
接收用权区块链针对权利应用业务发起的确权请求；
读取存证区块链上存证的权利归属数据；
根据所述权利归属数据对所述确权请求进行响应，以使所述用权区块链根据响应结果对所述权利应用业务进行处理。
根据本说明书一个或多个实施例的第三方面，提出了一种跨链用权方法，应用于用权区块链上的区块链节点，所述用权区块链连接至跨链中继，所述跨链中继还连接至少一条存证区块链；所述方法包括：
针对权利应用业务向所述跨链中继发起确权请求，以使所述跨链中继读取存证区块链上存证的权利归属数据并根据所述权利归属数据对所述确权请求进行响应；
根据所述跨链中继返回的响应结果，对所述权利应用业务进行处理。
根据本说明书一个或多个实施例的第四方面，提出了一种跨链用权装置，应用于跨链中继，所述跨链中继分别连接至少一条存证区块链、至少一条用权区块链；所述装置包括：
接收单元，接收用权区块链针对权利应用业务发起的确权请求；
读取单元，读取存证区块链上存证的权利归属数据；
响应单元，根据所述权利归属数据对所述确权请求进行响应，以使所述用权区块链根据响应结果对所述权利应用业务进行处理。
根据本说明书一个或多个实施例的第五方面，提出了一种跨链用权装置，应用于用权区块链上的区块链节点，所述用权区块链连接至跨链中继，所述跨链中继还连接至少一条存证区块链；所述装置包括：
请求单元，针对权利应用业务向所述跨链中继发起确权请求，以使所述跨链中继读取存证区块链上存证的权利归属数据并根据所述权利归属数据对所述确权请求进行响应；
处理单元，根据所述跨链中继返回的响应结果，对所述权利应用业务进行处理。
根据本说明书一个或多个实施例的第六方面，提出了一种电子设备，包括：
处理器；
用于存储处理器可执行指令的存储器；
其中，所述处理器通过运行所述可执行指令以实现如第二或第三方面所述的方法。
根据本说明书一个或多个实施例的第七方面，提出了一种计算机可读存储介质，其上存储有计算机指令，该指令被处理器执行时实现如第二或第三方面所述方法的步骤。
附图说明
图1是一示例性实施例提供的一种示例环境的示意图。
图2是一示例性实施例提供的一种概念架构的示意图。
图3是一示例性实施例提供的一种跨链用权方法的流程图。
图4是一示例性实施例提供的另一种跨链用权方法的流程图。
图5是一示例性实施例提供的一种跨链用权***的示意结构图。
图6是一示例性实施例提供的一种设备的结构示意图。
图7是一示例性实施例提供的一种跨链用权装置的框图。
图8是一示例性实施例提供的另一种设备的结构示意图。
图9是一示例性实施例提供的另一种跨链用权装置的框图。
具体实施方式
这里将详细地对示例性实施例进行说明，其示例表示在附图中。下面的描述涉及附图时，除非另有表示，不同附图中的相同数字表示相同或相似的要素。以下示例性实施例中所描述的实施方式并不代表与本说明书一个或多个实施例相一致的所有实施方式。相反，它们仅是与如所附权利要求书中所详述的、本说明书一个或多个实施例的一些方面相一致的装置和方法的例子。
需要说明的是：在其他实施例中并不一定按照本说明书示出和描述的顺序来执行相应方法的步骤。在一些其他实施例中，其方法所包括的步骤可以比本说明书所描述的更多或更少。此外，本说明书中所描述的单个步骤，在其他实施例中可能被分解为多个步骤进行描述；而本说明书中所描述的多个步骤，在其他实施例中也可能被合并为单个步骤进行描述。
图1是一示例性实施例提供的一种示例环境的示意图。如图1所示，示例环境100允许实体参与区块链网络102。区块链网络102可以为公有类型、私有类型或联盟类型的区块链网络。示例环境100可以包括计算设备104、106、108、110、112和网络114；在一实施例中，网络114可以包括局域网(Local Area Network，LAN)、广域网(Wide Area Network，WAN)、因特网或其组合，并连接至网站、用户设备(例如计算设备) 和后端***。在一实施例中，可以通过有线和/或无线通信方式访问网络114。
在某些情况下，计算设备106、108可以是云计算***的节点(未显示)，或者每个计算设备106、108可以是单独的云计算***，包括由网络互连并作为分布式处理***工作的多台计算机。
在一实施例中，计算设备104～108可以运行任何适当的计算***，使其能够作为区块链网络102中的节点；例如，计算设备104～108可以包括但不限于服务器、台式计算机、笔记本电脑、平板电脑计算设备和智能手机。在一实施例中，计算设备104～108可以归属于相关实体并用于实现相应的服务，例如该服务可以用于对某一实体或多个实体之间的交易进行管理。
在一实施例中，计算设备104～108分别存储有区块链网络102对应的区块链账本。计算设备104可以是(或包含)用于提供浏览器功能的网络服务器，该网络服务器可基于网络114提供与区块链网络102相关的可视化信息。在一些情况下，计算设备104可以不参与区块验证，而是监控区块链网络102以确定其他节点(譬如可以包括计算设备106-108)何时达成共识，并据此生成相应的区块链可视化用户界面。
在一实施例中，计算设备104可接收客户端设备(例如计算设备110或计算设备112)针对区块链可视化用户界面发起的请求。在一些情况下，区块链网络102的节点也可以作为客户端设备，比如计算设备108的用户可以使用运行在计算设备108上的浏览器向计算设备104发送上述请求。
响应于上述请求，计算设备104可以基于存储的区块链账本生成区块链可视化用户界面(如网页)，并将生成的区块链可视化用户界面发送给请求的客户端设备。如果区块链网络102是私有类型或联盟类型的区块链网络，对区块链可视化用户界面的请求可以包括用户授权信息，在生成区块链可视化用户界面并发送给请求的客户端设备之前，可以由计算设备104对该用户授权信息进行验证，并在验证通过后返回相应的区块链可视化用户界面。
区块链可视化用户界面可以显示在客户端设备上(例如可显示在图1所示的用户界面116中)。当区块链账本发生更新时，用户界面116的显示内容也可以随之发生更新。此外，用户与用户界面116的交互可能导致对其他用户界面的请求，例如显示区块列表、区块详情、交易列表、交易详情、账户列表、账户详情、合约列表、合约详情或者用户对区块链网络实施搜索而产生的搜索结果页面等。
图2是一示例性实施例提供的一种概念架构的示意图。如图2所示，该概念架构200包括实体层202、托管服务层204和区块链网络层206。例如，实体层202可以包括三个实体：实体1、实体2和实体3，每个实体都有各自的交易管理***208。
在一实施例中，托管服务层204可以包括每个事务管理***208对应的接口210。例如，各个事务管理***208使用协议(例如超文本传输协议安全(HTTPS)等)通过网络(例如图1中的网络114)与各自的接口210通信。在一些例子中，每个接口210可以提供各自对应的交易管理***208与区块链网络层206之间的通信连接；更具体地，接口210可与区块链网络层206的区块链网络212通信。在一些例子中，接口210和区块链网络层206之间的通信可以使用远程过程调用(Remote Procedure Calls，RPCs)而实现。在一些例子中，接口210可以向交易管理***208提供用于访问区块链网络212的API接口。
如本文所述，区块链网络212以对等网络的形式提供，该对等网络包括多个节点214，这些节点214分别用于对块链数据所形成的区块链账本216进行持久化；其中，图2中仅示出了一份区块链账本216，但区块链网络212中可以存在多份区块链账本216或其副本，比如每一节点214可以分别维护一份区块链账本216或其副本。
需要指出的是：在本说明书中所描述的交易(transaction)，是指用户通过区块链的客户端创建，并需要最终发布至区块链的分布式数据库中的一笔数据。其中，区块链中的交易，存在狭义的交易以及广义的交易之分。狭义的交易是指用户向区块链发布的一笔价值转移；例如，在传统的比特币区块链网络中，交易可以是用户在区块链中发起的一笔转账。而广义的交易是指用户向区块链发布的一笔具有业务意图的业务数据；例如，运营方可以基于实际的业务需求搭建一个联盟链，依托于联盟链部署一些与价值转移无关的其它类型的在线业务(比如，租房业务、车辆调度业务、保险理赔业务、信用服务、医疗服务等)，而在这类联盟链中，交易可以是用户在联盟链中发布的一笔具有业务意图的业务消息或者业务请求。
图3是一示例性实施例提供的一种跨链用权方法的流程图。如图3所示，该方法应用于跨链中继，所述跨链中继分别连接至少一条存证区块链、至少一条用权区块链；所述方法可以包括以下步骤：
步骤302，接收用权区块链针对权利应用业务发起的确权请求。
在一实施例中，跨链中继用于在用权区块链与存证区块链之间实现中继功能，使得 用权区块链能够通过该跨链中继对存证区块链进行访问，从而实现了用权区块链与存证区块链之间的对接。同时，基于跨链中继所实现的中继功能，使得用权区块链、存证区块链分别与跨链中继对接，而并非由用权区块链与存证区块链之间直接对接，可以根据实际需求对接入跨链中继的用权区块链、存证区块链进行增加或减少，因而整个***具有极佳的可扩展性。
在一实施例中，当用权区块链向跨链中继发起确权请求时，具体应当为该用权区块链上的至少一个区块链节点向跨链中继发起该确权请求。例如，区块链客户端可以基于用户指示而向用权区块链上的至少一个区块链节点发送请求指令，使得该至少一个区块链节点可以向跨链中继发起相应的确权请求；再例如，区块链客户端可以向用权区块链上的至少一个区块链节点提交一笔交易提案，使得该交易提案在通过共识并被执行时，可以向跨链中继发起上述的确权请求；又例如，区块链客户端可以向用权区块链上的至少一个区块链节点提交一笔交易提案，使得该交易提案在通过共识并被执行时，可以调用智能合约，该智能合约可用于自动向跨链中继发起上述的确权请求，且该智能合约可以进一步根据存证区块链反馈的权利归属数据而确定是否执行相关操作，比如在权利归属数据表明目标权利归属于目标对象时，才允许相关操作顺利执行，否则终止相关操作。
步骤304，读取存证区块链上存证的权利归属数据。
在一实施例中，存证区块链用于对权利归属数据进行存证，该权利归属数据用于记录相关权利的归属情况；以图书版权为例，可以记录图书版权与所有者之间的映射关系，比如某一用户A拥有图书B的版权、某一企业C拥有图书D的版权等。由于存证区块链采用分布式数据库技术，即若干区块链节点共同维护统一的区块链账本，并且区块链账本所含的区块之间实现为具有内容相关性的块链结构，使得存证区块链的区块链账本具有公开、不可篡改的特性，以便于实现安全可靠的存证功能。
在一实施例中，除了上述的图书版权之外，本说明书中的权利还可以包含其他类型，比如歌曲版权、电影版权、软件著作权、专利权、不动产权等，本说明书并不对此进行限制。
步骤306，根据所述权利归属数据对所述确权请求进行响应，以使所述用权区块链根据响应结果对所述权利应用业务进行处理。
在一实施例中，跨链中继可以根据所述权利归属数据，判断所述确权请求中指示的目标权利是否归属于目标对象，并将判断结果返回所述用权区块链。换言之，用权区块 链接收到的响应结果包含上述的判断结果，使得用权区块链可以据此对权利应用业务进行处理。
在一实施例中，跨链中继可以获取所述权利归属数据，并将所述权利归属数据返回所述用权区块链，以由所述用权区块链判定目标权利是否归属于目标对象。换言之，用权区块链可以获得权利归属数据，使得该用权区块链上的区块链节点可以基于该权利归属数据确定目标权利是否归属于目标对象，而跨链中继仅用于获取权利归属数据并提供至用权区块链。
相应的，图4是一示例性实施例提供的另一种跨链用权方法的流程图。如图4所示，该方法应用于用权区块链上的区块链节点，所述用权区块链连接至跨链中继，所述跨链中继还连接至少一条存证区块链；所述方法可以包括以下步骤：
步骤402，针对权利应用业务向所述跨链中继发起确权请求，以使所述跨链中继读取存证区块链上存证的权利归属数据并根据所述权利归属数据对所述确权请求进行响应。
在一实施例中，跨链中继用于在用权区块链与存证区块链之间实现中继功能，使得用权区块链能够通过该跨链中继对存证区块链进行访问，从而实现了用权区块链与存证区块链之间的对接。同时，基于跨链中继所实现的中继功能，使得用权区块链、存证区块链分别与跨链中继对接，而并非由用权区块链与存证区块链之间直接对接，可以根据实际需求对接入跨链中继的用权区块链、存证区块链进行增加或减少，因而整个***具有极佳的可扩展性。
在一实施例中，当用权区块链向跨链中继发起确权请求时，具体应当为该用权区块链上的至少一个区块链节点向跨链中继发起该确权请求。例如，区块链客户端可以基于用户指示而向用权区块链上的至少一个区块链节点发送请求指令，使得该至少一个区块链节点可以向跨链中继发起相应的确权请求；再例如，区块链客户端可以向用权区块链上的至少一个区块链节点提交一笔交易提案，使得该交易提案在通过共识并被执行时，可以向跨链中继发起上述的确权请求；又例如，区块链客户端可以向用权区块链上的至少一个区块链节点提交一笔交易提案，使得该交易提案在通过共识并被执行时，可以调用智能合约，该智能合约可用于自动向跨链中继发起上述的确权请求，且该智能合约可以进一步根据存证区块链反馈的权利归属数据而确定是否执行相关操作，比如在权利归属数据表明目标权利归属于目标对象时，才允许相关操作顺利执行，否则终止相关操作。
在一实施例中，存证区块链用于对权利归属数据进行存证，该权利归属数据用于记录相关权利的归属情况；以图书版权为例，可以记录图书版权与所有者之间的映射关系，比如某一用户A拥有图书B的版权、某一企业C拥有图书D的版权等。由于存证区块链采用分布式数据库技术，即若干区块链节点共同维护统一的区块链账本，并且区块链账本所含的区块之间实现为具有内容相关性的块链结构，使得存证区块链的区块链账本具有公开、不可篡改的特性，以便于实现安全可靠的存证功能。
在一实施例中，除了上述的图书版权之外，本说明书中的权利还可以包含其他类型，比如歌曲版权、电影版权、软件著作权、专利权、不动产权等，本说明书并不对此进行限制。
步骤404，根据所述跨链中继返回的响应结果，对所述权利应用业务进行处理。
在一实施例中，跨链中继可以根据所述权利归属数据，判断所述确权请求中指示的目标权利是否归属于目标对象，并将判断结果返回所述用权区块链。换言之，用权区块链接收到的响应结果包含上述的判断结果，使得用权区块链可以据此对权利应用业务进行处理。
在一实施例中，跨链中继可以获取所述权利归属数据，并将所述权利归属数据返回所述用权区块链，以由所述用权区块链判定目标权利是否归属于目标对象。换言之，用权区块链可以获得权利归属数据，使得该用权区块链上的区块链节点可以基于该权利归属数据确定目标权利是否归属于目标对象，而跨链中继仅用于获取权利归属数据并提供至用权区块链。
在一实施例中，用权区块链上的区块链节点可以根据所述响应结果生成确权信息，所述确权信息表明目标权利归属于目标对象；然后，该区块链节点可以向所述用权区块链提交对应于所述权利应用业务的区块链交易，所述区块链交易中包含所述确权信息。例如，未包含确权信息的区块链交易将无法通过共识；再例如，通过在区块链交易中包含确权信息，使得该确权信息被作为该区块链交易能够成功执行的先决条件之一；又例如，通过在区块链交易中包含确权信息，可以作为该区块链交易的有效性证明之一，而未包含确权信息的区块链交易将被确定为无效交易。
在一实施例中，用权区块链的区块链节点可以向该用权区块链提交对应于所述权利应用业务的区块链交易，所述区块链交易包含对智能合约的调用信息，以通过所述智能合约执行所述区块链交易；相应地，该区块链节点可以通过调用所述智能合约，向所述 跨链中继发起所述确权请求；以及，该区块链节点可以向所述智能合约提供所述响应结果，以由所述智能合约根据所述响应结果执行所述区块链交易，比如智能合约可以在响应结果表明目标权利归属于目标对象时执行区块链交易所指示的交易操作，否则避免执行该交易操作。
需要说明的是：在本说明书中所描述的交易(transaction)，是指用户通过区块链的客户端创建，并需要最终发布至区块链的分布式数据库中的一笔数据。其中，区块链中的交易，存在狭义的交易以及广义的交易之分。狭义的交易是指用户向区块链发布的一笔价值转移；例如，在传统的比特币区块链网络中，交易可以是用户在区块链中发起的一笔转账。而广义的交易是指用户向区块链发布的一笔具有业务意图的业务数据；例如，运营方可以基于实际的业务需求搭建一个联盟链，依托于联盟链部署一些与价值转移无关的其它类型的在线业务(比如，版权业务、租房业务、车辆调度业务、保险理赔业务、信用服务、医疗服务等)，而在这类联盟链中，交易可以是用户在联盟链中发布的一笔具有业务意图的业务消息或者业务请求。
为了便于理解，下面以图书版权的用权场景为例，结合图5对本说明书的技术方案进行详细说明。
图5是一示例性实施例提供的一种跨链用权***的示意结构图。如图5所示，该***可以包括：一条或多条存证区块链、一条或多条用权区块链和至少一个跨链中继，例如存证区块链可以包括区块链511、512、513和514，用权区块链可以包括区块链531、532和533，跨链中继可以包括中继521、522。
区块链511～514用于对权利归属数据进行存证；在图书版权的场景中，权利归属数据用于表明图书版权的归属情况，比如某一图书版权T1归属于用户UA、另一图书版权T2归属于企业UB等，这些权利归属数据可能由于隐私要求(譬如不同区块链用于存证不同隐私需求级别的权利归属数据)、业务隔离(譬如个人业务与公司业务、教育类图书业务与科技类图书业务等)、参与方联盟(譬如不同联盟分别采用不同的存证区块链，每一存证区块链仅存储相应联盟的参与方所提供的权利归属数据)等原因而分别存证于不同的存证区块链。区块链511～514上的区块链节点可以分别对被提交的版权数据进行共识，并将通过共识的版权数据以诸如键值对(key-value)或本说明书并不限制的其他任意形式保存为相应的权利归属数据，使得权利归属数据被记录于相应区块链的区块链账本中，从而对权利归属数据进行存证。因此，当跨链中继521或522从区块链511～514的区块链账本中读取权利归属数据时，可以确保该权利归属数据所描述的图书 版权的归属情况真实有效，使得用权区块链可以据此处理相关权利应用业务。
如上文所述，跨链中继521-522用于实现区块链511～514与区块链531～533之间的数据连接，使得区块链531～533可以经由跨链中继521-522对区块链511～514所存证的权利归属数据进行访问，以用于确定对相关权利应用业务的处理方式。而作为用权区块链的区块链531～533等，用于根据实际业务需求而通过跨链中继521-522对区块链511～514所存证的权利归属数据进行访问。其中，取决于隐私需求、业务需求、参与方隔离需求等原因，使得用权区块链的数量可以为如图5所示的多个(如区块链531～533)，当然本说明书并不对此进行限制。
举例而言，假定企业UX与用户UA约定：由企业UX向用户UA支付一定的资产凭证，以获得对用户UA绘制的画作K的图书版权的使用授权。譬如企业UX侧的工作人员可以对计算设备540进行操作，使得该计算设备540可以向区块链532中的区块链节点532a提交一笔交易提案，该交易提案针对用户UA所持有的画作K而发起，用于在确定用户UA拥有画作K的图书版权后，向用户UA支付数额为i的资产凭证。
区块链节点532a可以在区块链532中发布该交易提案，使得该交易提案在区块链532中得以执行。由于交易提案需要完成2步操作：第一步用于验证用户UA拥有画作K的图书版权，第二步用于由企业UX向用户UA支付数额为i的资产凭证，那么可以预先定义一智能合约并使得该交易提案对该智能合约进行调用，使得该智能合约可以自动高效、不受外界影响地完成上述2步操作。
例如，智能合约可以向跨链中继521或522发起确权请求，该确权请求用于请求验证用户UA是否拥有画作K的图书版权。如果智能合约将确权请求发送至跨链中继521，那么跨链中继521可以根据相关技术中的跨链技术(如侧链技术、公证人技术等，本说明书并不对此进行限制)，读取区块链511～514所存证的权利归属数据，从而根据该权利归属数据来验证用户UA是否拥有画作K的图书版权。其中，当画作K的图书版权的归属情况被记录于区块链511或512的区块链账本时，由于图5中的跨链中继521与区块链511-512直接连接，因而跨链中继521可以直接读取区块链511-512存证的权利归属数据、验证用户UA是否拥有画作K的图书版权；当画作K的图书版权的归属情况被记录于区块链513或514的区块链账本时，由于图5中的跨链中继521并未与区块链513-514直接连接，因而跨链中继521可以通过与跨链中继522之间的数据通道，读取区块链513-514存证的权利归属数据，以验证用户UA是否拥有画作K的图书版权，当然也可以由跨链中继522验证用户UA是否拥有画作K的图书版权并将验证结果告知 跨链中继521。
无论是读取权利归属数据并据此验证用户UA是否拥有画作K的图书版权，或者直接获得跨链中继522返回的验证结果，总之跨链中继521可以获得相应的验证结果，并向上述的智能合约返回相应的验证结果。相应的，智能合约可以在验证结果表明用户UA拥有画作K的图书版权时，完成上述的第二步操作，即由企业UX向用户UA支付数额为i的资产凭证，譬如使得企业UX对应的区块链账户减少数额为i的资产凭证、使得用户UA对应的区块链账户增加数额为i的资产凭证。当然，如果验证结果表明用户UA未拥有画作K的图书版权，智能合约可以拒绝执行上述的第二步操作，比如可以判定该第二步操作执行失败。
可见，由于采用如图5所示“存证区块链-跨链中继-用权区块链”的***结构，使得存证区块链、用权区块链仅需分别考虑与跨链中继之间的连接，而无需考虑存证区块链与用权区块链之间的直接对接，因而当存证区块链或用权区块链需要发生增减变化时，能够便捷地实施相应的配置操作，使得***具有极大的可扩展性。
图6是一示例性实施例提供的一种设备的示意结构图。请参考图6，在硬件层面，该设备包括处理器602、内部总线604、网络接口606、内存608以及非易失性存储器610，当然还可能包括其他业务所需要的硬件。处理器602从非易失性存储器610中读取对应的计算机程序到内存608中然后运行，在逻辑层面上形成跨链用权装置。当然，除了软件实现方式之外，本说明书一个或多个实施例并不排除其他实现方式，比如逻辑器件抑或软硬件结合的方式等等，也就是说以下处理流程的执行主体并不限定于各个逻辑单元，也可以是硬件或逻辑器件。
请参考图7，在软件实施方式中，该跨链用权装置，应用于跨链中继，所述跨链中继分别连接至少一条存证区块链、至少一条用权区块链；所述装置可以包括：
接收单元71，接收用权区块链针对权利应用业务发起的确权请求；
读取单元72，读取存证区块链上存证的权利归属数据；
响应单元73，根据所述权利归属数据对所述确权请求进行响应，以使所述用权区块链根据响应结果对所述权利应用业务进行处理。
可选的，所述响应单元73具体用于：
根据所述权利归属数据，判断所述确权请求中指示的目标权利是否归属于目标对象；
将判断结果返回所述用权区块链。
可选的，所述响应单元73具体用于：
获取所述权利归属数据；
将所述权利归属数据返回所述用权区块链，以由所述用权区块链判定目标权利是否归属于目标对象。
图8是一示例性实施例提供的一种设备的示意结构图。请参考图8，在硬件层面，该设备包括处理器802、内部总线804、网络接口806、内存808以及非易失性存储器810，当然还可能包括其他业务所需要的硬件。处理器802从非易失性存储器810中读取对应的计算机程序到内存808中然后运行，在逻辑层面上形成跨链用权装置。当然，除了软件实现方式之外，本说明书一个或多个实施例并不排除其他实现方式，比如逻辑器件抑或软硬件结合的方式等等，也就是说以下处理流程的执行主体并不限定于各个逻辑单元，也可以是硬件或逻辑器件。
请参考图9，在软件实施方式中，该跨链用权装置应用于用权区块链上的区块链节点，所述用权区块链连接至跨链中继，所述跨链中继还连接至少一条存证区块链；所述装置可以包括：
请求单元91，针对权利应用业务向所述跨链中继发起确权请求，以使所述跨链中继读取存证区块链上存证的权利归属数据并根据所述权利归属数据对所述确权请求进行响应；
处理单元92，根据所述跨链中继返回的响应结果，对所述权利应用业务进行处理。
可选的，所述处理单元92具体用于：
根据所述响应结果生成确权信息，所述确权信息表明目标权利归属于目标对象；
向所述用权区块链提交对应于所述权利应用业务的区块链交易，所述区块链交易中包含所述确权信息。
可选的，
还包括：提交单元93，向所述用权区块链提交对应于所述权利应用业务的区块链交易，所述区块链交易包含对智能合约的调用信息，以通过所述智能合约执行所述区块链交易；
所述请求单元91具体用于：通过调用所述智能合约，向所述跨链中继发起所述 确权请求；
所述处理单元92具体用于：向所述智能合约提供所述响应结果，以由所述智能合约根据所述响应结果执行所述区块链交易。
可选的，所述响应结果包括：所述跨链中继根据所述权利归属数据生成的判断结果，所述判断结果用于表明目标权利是否归属于目标对象。
可选的，所述处理单元92具体用于：
获取所述响应结果包含的所述权利归属数据；
判定目标权利是否归属于目标对象，以根据判定结果对所述权利应用业务进行处理。
上述实施例阐明的***、装置、模块或单元，具体可以由计算机芯片或实体实现，或者由具有某种功能的产品来实现。一种典型的实现设备为计算机，计算机的具体形式可以是个人计算机、膝上型计算机、蜂窝电话、相机电话、智能电话、个人数字助理、媒体播放器、导航设备、电子邮件收发设备、游戏控制台、平板计算机、可穿戴设备或者这些设备中的任意几种设备的组合。
在一个典型的配置中，计算机包括一个或多个处理器(CPU)、输入/输出接口、网络接口和内存。
内存可能包括计算机可读介质中的非永久性存储器，随机存取存储器(RAM)和/或非易失性内存等形式，如只读存储器(ROM)或闪存(flash RAM)。内存是计算机可读介质的示例。
计算机可读介质包括永久性和非永久性、可移动和非可移动媒体可以由任何方法或技术来实现信息存储。信息可以是计算机可读指令、数据结构、程序的模块或其他数据。计算机的存储介质的例子包括，但不限于相变内存(PRAM)、静态随机存取存储器(SRAM)、动态随机存取存储器(DRAM)、其他类型的随机存取存储器(RAM)、只读存储器(ROM)、电可擦除可编程只读存储器(EEPROM)、快闪记忆体或其他内存技术、只读光盘只读存储器(CD-ROM)、数字多功能光盘(DVD)或其他光学存储、磁盒式磁带、磁盘存储、量子存储器、基于石墨烯的存储介质或其他磁性存储设备或任何其他非传输介质，可用于存储可以被计算设备访问的信息。按照本文中的界定，计算机可读介质不包括暂存电脑可读媒体(transitory media)，如调制的数据信号和载波。
还需要说明的是，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、商品或者设备不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、商品或者设备所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括所述要素的过程、方法、商品或者设备中还存在另外的相同要素。
上述对本说明书特定实施例进行了描述。其它实施例在所附权利要求书的范围内。在一些情况下，在权利要求书中记载的动作或步骤可以按照不同于实施例中的顺序来执行并且仍然可以实现期望的结果。另外，在附图中描绘的过程不一定要求示出的特定顺序或者连续顺序才能实现期望的结果。在某些实施方式中，多任务处理和并行处理也是可以的或者可能是有利的。
在本说明书一个或多个实施例使用的术语是仅仅出于描述特定实施例的目的，而非旨在限制本说明书一个或多个实施例。在本说明书一个或多个实施例和所附权利要求书中所使用的单数形式的“一种”、“所述”和“该”也旨在包括多数形式，除非上下文清楚地表示其他含义。还应当理解，本文中使用的术语“和/或”是指并包含一个或多个相关联的列出项目的任何或所有可能组合。
应当理解，尽管在本说明书一个或多个实施例可能采用术语第一、第二、第三等来描述各种信息，但这些信息不应限于这些术语。这些术语仅用来将同一类型的信息彼此区分开。例如，在不脱离本说明书一个或多个实施例范围的情况下，第一信息也可以被称为第二信息，类似地，第二信息也可以被称为第一信息。取决于语境，如在此所使用的词语“如果”可以被解释成为“在……时”或“当……时”或“响应于确定”。
以上所述仅为本说明书一个或多个实施例的较佳实施例而已，并不用以限制本说明书一个或多个实施例，凡在本说明书一个或多个实施例的精神和原则之内，所做的任何修改、等同替换、改进等，均应包含在本说明书一个或多个实施例保护的范围之内。

Claims (20)

  1. 一种跨链用权***，包括：
    一条或多条存证区块链，所述存证区块链用于对权利归属数据进行存证；
    一条或多条用权区块链，所述用权区块链用于处理权利应用业务；
    至少一个跨链中继，每一跨链中继分别连接至少一条存证区块链、至少一条用权区块链；所述跨链中继读取存证区块链上的权利归属数据，以响应于用权区块链发起的确权请求，使得用权区块链根据响应结果对相应的权利应用业务进行处理。
  2. 根据权利要求1所述的***，多个跨链中继之间相连；其中，当第一跨链中继收到任一用权区块链发起的与任一存证区块链相关的确权请求，且所述第一跨链中继未连接至所述任一存证区块链时，所述第一跨链中继将所述确权请求转发至与所述任一存证区块链相连的第二跨链中继，使所述第二跨链中继读取所述任一存证区块链上的权利归属数据，以响应于所述任一用权区块链发起的确权请求。
  3. 一种跨链用权方法，应用于跨链中继，所述跨链中继分别连接至少一条存证区块链、至少一条用权区块链；所述方法包括：
    接收用权区块链针对权利应用业务发起的确权请求；
    读取存证区块链上存证的权利归属数据；
    根据所述权利归属数据对所述确权请求进行响应，以使所述用权区块链根据响应结果对所述权利应用业务进行处理。
  4. 根据权利要求3所述的方法，所述根据所述权利归属数据对所述确权请求进行响应，包括：
    根据所述权利归属数据，判断所述确权请求中指示的目标权利是否归属于目标对象；
    将判断结果返回所述用权区块链。
  5. 根据权利要求3所述的方法，所述根据所述权利归属数据对所述确权请求进行响应，包括：
    获取所述权利归属数据；
    将所述权利归属数据返回所述用权区块链，以由所述用权区块链判定目标权利是否归属于目标对象。
  6. 一种跨链用权方法，应用于用权区块链上的区块链节点，所述用权区块链连接至跨链中继，所述跨链中继还连接至少一条存证区块链；所述方法包括：
    针对权利应用业务向所述跨链中继发起确权请求，以使所述跨链中继读取存证区块链上存证的权利归属数据并根据所述权利归属数据对所述确权请求进行响应；
    根据所述跨链中继返回的响应结果，对所述权利应用业务进行处理。
  7. 根据权利要求6所述的方法，所述根据所述跨链中继返回的响应结果，对所述权利应用业务进行处理，包括：
    根据所述响应结果生成确权信息，所述确权信息表明目标权利归属于目标对象；
    向所述用权区块链提交对应于所述权利应用业务的区块链交易，所述区块链交易中包含所述确权信息。
  8. 根据权利要求6所述的方法，
    还包括：向所述用权区块链提交对应于所述权利应用业务的区块链交易，所述区块链交易包含对智能合约的调用信息，以通过所述智能合约执行所述区块链交易；
    所述针对权利应用业务向所述跨链中继发起确权请求，包括：通过调用所述智能合约，向所述跨链中继发起所述确权请求；
    所述根据所述跨链中继返回的响应结果，对所述权利应用业务进行处理，包括：向所述智能合约提供所述响应结果，以由所述智能合约根据所述响应结果执行所述区块链交易。
  9. 根据权利要求6所述的方法，所述响应结果包括：所述跨链中继根据所述权利归属数据生成的判断结果，所述判断结果用于表明目标权利是否归属于目标对象。
  10. 根据权利要求6所述的方法，所述根据所述跨链中继返回的响应结果，对所述权利应用业务进行处理，包括：
    获取所述响应结果包含的所述权利归属数据；
    判定目标权利是否归属于目标对象，以根据判定结果对所述权利应用业务进行处理。
  11. 一种跨链用权装置，应用于跨链中继，所述跨链中继分别连接至少一条存证区块链、至少一条用权区块链；所述装置包括：
    接收单元，接收用权区块链针对权利应用业务发起的确权请求；
    读取单元，读取存证区块链上存证的权利归属数据；
    响应单元，根据所述权利归属数据对所述确权请求进行响应，以使所述用权区块链根据响应结果对所述权利应用业务进行处理。
  12. 根据权利要求11所述的装置，所述响应单元具体用于：
    根据所述权利归属数据，判断所述确权请求中指示的目标权利是否归属于目标对象；
    将判断结果返回所述用权区块链。
  13. 根据权利要求11所述的装置，所述响应单元具体用于：
    获取所述权利归属数据；
    将所述权利归属数据返回所述用权区块链，以由所述用权区块链判定目标权利是否归属于目标对象。
  14. 一种跨链用权装置，应用于用权区块链上的区块链节点，所述用权区块链连接至跨链中继，所述跨链中继还连接至少一条存证区块链；所述装置包括：
    请求单元，针对权利应用业务向所述跨链中继发起确权请求，以使所述跨链中继读取存证区块链上存证的权利归属数据并根据所述权利归属数据对所述确权请求进行响应；
    处理单元，根据所述跨链中继返回的响应结果，对所述权利应用业务进行处理。
  15. 根据权利要求14所述的装置，所述处理单元具体用于：
    根据所述响应结果生成确权信息，所述确权信息表明目标权利归属于目标对象；
    向所述用权区块链提交对应于所述权利应用业务的区块链交易，所述区块链交易中包含所述确权信息。
  16. 根据权利要求14所述的装置，
    还包括：提交单元，向所述用权区块链提交对应于所述权利应用业务的区块链交易，所述区块链交易包含对智能合约的调用信息，以通过所述智能合约执行所述区块链交易；
    所述请求单元具体用于：通过调用所述智能合约，向所述跨链中继发起所述确权请求；
    所述处理单元具体用于：向所述智能合约提供所述响应结果，以由所述智能合约根据所述响应结果执行所述区块链交易。
  17. 根据权利要求14所述的装置，所述响应结果包括：所述跨链中继根据所述权利归属数据生成的判断结果，所述判断结果用于表明目标权利是否归属于目标对象。
  18. 根据权利要求14所述的装置，所述处理单元具体用于：
    获取所述响应结果包含的所述权利归属数据；
    判定目标权利是否归属于目标对象，以根据判定结果对所述权利应用业务进行处理。
  19. 一种电子设备，包括：
    处理器；
    用于存储处理器可执行指令的存储器；
    其中，所述处理器通过运行所述可执行指令以实现如权利要求3-10中任一项所述的方法。
  20. 一种计算机可读存储介质，其上存储有计算机指令，该指令被处理器执行时实现如权利要求3-10中任一项所述方法的步骤。
PCT/CN2019/122127 2019-01-31 2019-11-29 跨链用权***及方法、装置、电子设备、存储介质 WO2020155832A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
SG11202104281TA SG11202104281TA (en) 2019-01-31 2019-11-29 Cross-chain right usage systems, methods, apparatuses, electronic devices, and storage media
EP19912920.6A EP3859648A4 (en) 2019-01-31 2019-11-29 Cross-chain usage-rights system and method, device, eletronic apparatus and storage medium
US17/245,730 US20210248605A1 (en) 2019-01-31 2021-04-30 Cross-chain right usage systems, methods, apparatuses, electronic devices, and storage media

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910098527.5 2019-01-31
CN201910098527.5A CN110046998B (zh) 2019-01-31 2019-01-31 跨链用权***及方法、装置、电子设备、存储介质

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/245,730 Continuation US20210248605A1 (en) 2019-01-31 2021-04-30 Cross-chain right usage systems, methods, apparatuses, electronic devices, and storage media

Publications (1)

Publication Number Publication Date
WO2020155832A1 true WO2020155832A1 (zh) 2020-08-06

Family

ID=67274203

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/122127 WO2020155832A1 (zh) 2019-01-31 2019-11-29 跨链用权***及方法、装置、电子设备、存储介质

Country Status (6)

Country Link
US (1) US20210248605A1 (zh)
EP (1) EP3859648A4 (zh)
CN (1) CN110046998B (zh)
SG (1) SG11202104281TA (zh)
TW (1) TW202030656A (zh)
WO (1) WO2020155832A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113434883A (zh) * 2021-06-29 2021-09-24 北京百度网讯科技有限公司 跨链处理方法、装置、电子设备及可读存储介质
CN113468268A (zh) * 2021-06-29 2021-10-01 北京百度网讯科技有限公司 跨链处理方法、装置、电子设备及可读存储介质

Families Citing this family (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110046998B (zh) * 2019-01-31 2020-04-14 阿里巴巴集团控股有限公司 跨链用权***及方法、装置、电子设备、存储介质
US11995647B2 (en) * 2019-04-30 2024-05-28 Salesforce, Inc. System and method of providing interoperable distributed and decentralized ledgers using consensus on consensus and delegated consensus
CN110609868B (zh) * 2019-09-03 2022-01-07 中国人民大学 一种基于同区块链平台的跨链协同工作方法及***
CN111090661B (zh) * 2019-12-10 2024-03-01 京东科技信息技术有限公司 一种区块链跨链数据访问方法、装置、适配器及***
CN112994892B (zh) * 2020-12-17 2023-06-09 中国工商银行股份有限公司 跨链交互方法、装置、***和电子设备
CN112699136B (zh) * 2020-12-29 2023-04-14 杭州趣链科技有限公司 一种跨链存证方法及相关装置
CN112561407B (zh) * 2021-02-20 2021-06-22 支付宝(杭州)信息技术有限公司 基于区块链的资产管理方法、***及装置
CN113467888B (zh) * 2021-06-29 2024-02-23 网易（杭州）网络有限公司 智能合约的跨链调用方法及装置、电子设备、存储介质
CN113626850B (zh) * 2021-10-13 2022-03-11 北京百度网讯科技有限公司 基于联盟链的请求处理方法、装置、设备和存储介质
CN114006911B (zh) * 2021-12-31 2022-04-26 杭州趣链科技有限公司 数据处理方法、装置、终端设备及存储介质
CN114463006A (zh) * 2022-01-26 2022-05-10 蚂蚁区块链科技(上海)有限公司 基于联盟链的地理标志处理方法及装置
CN115001712A (zh) * 2022-06-10 2022-09-02 上海万向区块链股份公司 区块链间的价值通讯传输方法、***及介质
CN115801344A (zh) * 2022-10-31 2023-03-14 蚂蚁区块链科技(上海)有限公司 基于区块链的多实例组网方法及装置和电子设备
CN115955317B (zh) * 2023-03-03 2023-05-26 鲜明技术(北京)有限公司 跨区块链的资源存储方法及装置

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018032890A1 (zh) * 2016-08-15 2018-02-22 华为技术有限公司 在对等网络中分发数字内容的方法和***
CN107784604A (zh) * 2017-10-28 2018-03-09 北京安妮全版权科技发展有限公司 版权存证方法、装置、存储介质和电子设备
CN108269190A (zh) * 2018-01-17 2018-07-10 深圳四方精创资讯股份有限公司 基于跨链中继平台的跨链方法及其***
CN108932410A (zh) * 2018-08-17 2018-12-04 腾讯科技（深圳）有限公司 一种数字资源版权鉴权方法、装置、***和存储介质
CN109035012A (zh) * 2018-06-11 2018-12-18 西安纸贵互联网科技有限公司 一种区块链***的跨链处理方法和计算机可读存储介质
CN110046998A (zh) * 2019-01-31 2019-07-23 阿里巴巴集团控股有限公司 跨链用权***及方法、装置、电子设备、存储介质

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11258587B2 (en) * 2016-10-20 2022-02-22 Sony Corporation Blockchain-based digital rights management
CN108881290B (zh) * 2018-07-17 2021-04-23 深圳前海微众银行股份有限公司 基于区块链的数字证书使用方法、***及存储介质
CN109286632B (zh) * 2018-10-25 2021-01-15 中国信息通信研究院 一种基于区块链的大数据授权存证方法和***

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018032890A1 (zh) * 2016-08-15 2018-02-22 华为技术有限公司 在对等网络中分发数字内容的方法和***
CN107784604A (zh) * 2017-10-28 2018-03-09 北京安妮全版权科技发展有限公司 版权存证方法、装置、存储介质和电子设备
CN108269190A (zh) * 2018-01-17 2018-07-10 深圳四方精创资讯股份有限公司 基于跨链中继平台的跨链方法及其***
CN109035012A (zh) * 2018-06-11 2018-12-18 西安纸贵互联网科技有限公司 一种区块链***的跨链处理方法和计算机可读存储介质
CN108932410A (zh) * 2018-08-17 2018-12-04 腾讯科技（深圳）有限公司 一种数字资源版权鉴权方法、装置、***和存储介质
CN110046998A (zh) * 2019-01-31 2019-07-23 阿里巴巴集团控股有限公司 跨链用权***及方法、装置、电子设备、存储介质

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3859648A4 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113434883A (zh) * 2021-06-29 2021-09-24 北京百度网讯科技有限公司 跨链处理方法、装置、电子设备及可读存储介质
CN113468268A (zh) * 2021-06-29 2021-10-01 北京百度网讯科技有限公司 跨链处理方法、装置、电子设备及可读存储介质

Also Published As

Publication number Publication date
TW202030656A (zh) 2020-08-16
CN110046998B (zh) 2020-04-14
US20210248605A1 (en) 2021-08-12
EP3859648A1 (en) 2021-08-04
EP3859648A4 (en) 2021-12-29
CN110046998A (zh) 2019-07-23
SG11202104281TA (en) 2021-05-28

Similar Documents

Publication Publication Date Title
WO2020155832A1 (zh) 跨链用权***及方法、装置、电子设备、存储介质
US11449476B2 (en) Extracting data from a blockchain network
WO2021017444A1 (zh) 基于区块链的数据授权方法及装置
WO2020258851A1 (zh) 采用环签名的机密区块链交易的实现方法及装置
EP3560143B1 (en) Data isolation in a blockchain network
TW202107458A (zh) 基於智慧合約的資料授權方法及裝置
WO2020134699A1 (zh) 基于区块链的***报销方法、装置及电子设备
US20190013933A1 (en) Blockchain object deployment and synchronization across blockchains
US11582043B2 (en) Systems, apparatus and methods for backing up and auditing distributed ledger data within a network and securely without using private keys
WO2021239070A1 (zh) 在联盟链网络中创建节点组、基于节点组的交易方法
US11233660B2 (en) Confidential blockchain transactions
TWI731569B (zh) 基於環簽名的匿名交易方法及裝置
TWI727284B (zh) 基於區塊鏈的隱私交易方法、裝置及其電腦設備、基於區塊鏈內的隱私交易的應用方法及其電腦設備
WO2022008996A1 (en) Privacy preserving architecture for permissioned blockchains
EP3808028A1 (en) Services platform for managing a verifiable permissioned ledger in a distributed database management system
WO2021017425A1 (zh) 区块链网络中实现机密交易的方法及装置
TWI727642B (zh) 區塊鏈中實現機密交易的方法及裝置
Martins et al. Recoverable token: Recovering from intrusions against digital assets in Ethereum
CN116975918A (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: 19912920

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2019912920

Country of ref document: EP

Effective date: 20210427

NENP Non-entry into the national phase

Ref country code: DE