Inter-ledger messaging in a blockchain
US-2018113752-A1 · Apr 26, 2018 · US
US10680828B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-10680828-B2 |
| Application number | US-201916390494-A |
| Country | US |
| Kind code | B2 |
| Filing date | Apr 22, 2019 |
| Priority date | Nov 16, 2018 |
| Publication date | Jun 9, 2020 |
| Grant date | Jun 9, 2020 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
Implementations of the present disclosure include obtaining, by a computing system, a unified blockchain domain name (a UBCDN) message of a blockchain instance, wherein the UBCDN message includes a UBCDN of the blockchain instance, a digital signature of an owner of the UBCDN of the blockchain instance (a UBCDN owner) on the UBCDN, and a domain certificate of the UBCDN; verifying whether the domain certificate of the UBCDN is issued by a trusted certificate authority (CA) using a public key of the CA; and verifying whether the UBCDN is issued by the UBCDN owner using a public key of the UBCDN owner. The UBCDN message includes a blockchain domain name and a chain identifier of the blockchain instance uniquely corresponding to the blockchain domain name.
Opening claim text (preview).
The invention claimed is: 1. A computer-implemented method comprising: obtaining, by a computing system, a unified blockchain domain name (UBCDN) message of a blockchain instance in a unified blockchain network, wherein the unified blockchain network comprises a plurality of blockchain instances that are communicatively linked by two or more relays, and each of the plurality of blockchain instances comprises an implementation of a blockchain based on a respective blockchain platform or technology, wherein the UBCDN message comprises: a UBCDN of the blockchain instance, wherein the UBCDN of the blockchain instance is recognizable globally by all the plurality of blockchain instances in the unified blockchain network, and the UBCDN of the blockchain instance comprises: a blockchain domain name of the blockchain instance, wherein the blockchain domain name is a unique identifier of the blockchain instance in the unified blockchain network, and wherein the blockchain domain name comprises a human-readable label, and a chain identifier of the blockchain instance uniquely corresponding to the blockchain domain name, wherein the chain identifier of the blockchain instance indicates a blockchain network configuration of the blockchain instance and allows access to the blockchain instance based on the blockchain network configuration; a digital signature of an owner of the UBCDN of the blockchain instance (a UBCDN owner) on the UBCDN; and a domain certificate of the UBCDN; verifying whether the domain certificate of the UBCDN is issued by a trusted certificate authority (CA) using a public key of the CA; and verifying whether the UBCDN is issued by the UBCDN owner using a public key of the UBCDN owner. 2. The method of claim 1 , wherein the computing system serves as a third party of the unified blockchain network. 3. The method of claim 1 , wherein the computing system serves as a client node of a second blockchain instance different from the blockchain instance in the unified blockchain network, and the method further comprises: in response to verifying that the UBCDN is issued by the UBCDN owner; and verifying that the domain certificate of the UBCDN is issued by a trusted CA, performing cross-chain transactions between the blockchain instance and the second blockchain instance based on the blockchain domain name of the blockchain instance. 4. The method of claim 1 , wherein the domain certificate of the UBCDN comprises: the blockchain domain name of the blockchain instance; the public key of the UBCDN owner; and a digital signature of the CA on the blockchain domain name of the blockchain instance and the public key of the UBCDN owner. 5. The method of claim 4 , wherein the digital signature of the CA is obtained by the CA signing on the blockchain domain name of the blockchain instance and the public key of the UBCDN owner using a private key of the CA corresponding to the public key of the CA; and wherein verifying whether the domain certificate of the UBCDN is issued by a trusted CA using a public key of the CA comprises verifying that the domain certificate of the UBCDN is issued by the CA using the domain certificate, the digital signature of the CA, and the public key of the CA. 6. The method of claim 4 , wherein the digital signature of the owner of the UBCDN is obtained by the owner of the UBCDN signing the UBCDN using a private key corresponding to the public key of the owner of the UBCDN; and wherein verifying whether the UBCDN of the blockchain instance is issued by the UBCDN owner using a public key of the owner of the UBCDN comprises verifying that the UBCDN is issued by the owner of the UBCDN using the UBCDN, the digital signature of the owner of the UBCDN, and the public key of the owner of the UBCDN. 7. A non-transitory, computer-readable medium storing one or more instructions executable by a computer system to perform operations comprising: obtaining, by a computing system, a unified blockchain domain name (UBCDN) message of a blockchain instance in a unified blockchain network, wherein the unified blockchain network comprises a plurality of blockchain instances that are communicatively linked by two or more relays, and each of the plurality of blockchain instances comprises an implementation of a blockchain based on a respective blockchain platform or technology, wherein the UBCDN message comprises: a UBCDN of the blockchain instance, wherein the UBCDN of the blockchain instance is recognizable globally by all the plurality of blockchain instances in the unified blockchain network, and the UBCDN of the blockchain instance comprises: a blockchain domain name of the blockchain instance, wherein the blockchain domain name is a unique identifier of the blockchain instance in the unified blockchain network, and wherein the blockchain domain name comprises a human-readable label, and a chain identifier of the blockchain instance uniquely corresponding to the blockchain domain name, wherein the chain identifier of the blockchain instance indicates a blockchain network configuration of the blockchain instance and allows access to the blockchain instance based on the blockchain network configuration; a digital signature of an owner of the UBCDN of the blockchain instance (a UBCDN owner) on the UBCDN; and a domain certificate of the UBCDN; verifying whether the domain certificate of the UBCDN is issued by a trusted certificate authority (CA) using a public key of the CA; and verifying whether the UBCDN is issued by the UBCDN owner using a public key of the UBCDN owner. 8. The non-transitory, computer-readable medium of claim 7 , wherein the computing system serves as a third party of the unified blockchain network. 9. The non-transitory, computer-readable medium of claim 7 , wherein the computing system serves as a client node of a second blockchain instance different from the blockchain instance in the unified blockchain network, and the operations further comprise: in response to verifying that the UBCDN is issued by the UBCDN owner; and verifying that the domain certificate of the UBCDN is issued by a trusted CA, performing cross-chain transactions between the blockchain instance and the second blockchain instance based on the blockchain domain name of the blockchain instance. 10. The non-transitory, computer-readable medium of claim 7 , wherein the domain certificate of the UBCDN comprises: the blockchain domain name of the blockchain instance; the public key of the UBCDN owner; and a digital signature of the CA on the blockchain domain name of the blockchain instance and the public key of the UBCDN owner. 11. The non-transitory, computer-readable medium of claim 10 , wherein the digital signature of the CA is obtained by the CA signing on the blockchain domain name of the blockchain instance and the public key of the UBCDN owner using a private key of the CA corresponding to the public key of the CA; and wherein verifying whether the domain certificate of the UBCDN is issued by a trusted CA using a public key of the CA comprises verifying that the domain certificate of the UBCDN is issued by the CA using the domain certificate, the digital signature of the CA, and the public key of the CA. 12. The non-transitory, computer-readable medium of claim 10 , wherein the digital signature of the owner of the UBCDN is obtained by the owner of the UBCDN signing the UBCDN using a private key corresponding to the public key of the owner of the UBCDN; and wherein verifying whether the UBCDN of the blockchain instance is issued by the UBCDN owner using a public key of the owner of the UBCDN comprises verifying that the UBCDN is issued by the owner
involving certificates, e.g. public key certificate [PKC] or attribute certificate [AC]; Public key infrastructure [PKI] arrangements (network architectures or network communication protocols for supporting authentication of entities using certificates in a packet data network H04L63/0823) · CPC title
involving non-keyed hash functions, e.g. modification detection codes [MDCs], MD5, SHA or RIPEMD · CPC title
using certificate validation, registration, distribution or revocation, e.g. certificate revocation list [CRL] · CPC title
using asymmetric-key encryption or public key infrastructure [PKI], e.g. key signature or public key certificates · CPC title
using certificate chains, trees or paths; Hierarchical trust model · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.