CN112380294B - Block chain cross-chain access method and device - Google Patents
Block chain cross-chain access method and device Download PDFInfo
- Publication number
- CN112380294B CN112380294B CN202011628016.9A CN202011628016A CN112380294B CN 112380294 B CN112380294 B CN 112380294B CN 202011628016 A CN202011628016 A CN 202011628016A CN 112380294 B CN112380294 B CN 112380294B
- Authority
- CN
- China
- Prior art keywords
- blockchain
- domain name
- chain
- target
- access information
- Prior art date
- Legal status (The legal status 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 status listed.)
- Active
Links
Images
Classifications
-
- 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
- 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/23—Updating
-
- 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/28—Databases characterised by their database models, e.g. relational or object models
- G06F16/284—Relational databases
Landscapes
- Engineering & Computer Science (AREA)
- Databases & Information Systems (AREA)
- Theoretical Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computing Systems (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
Abstract
The present specification provides a block chain cross-chain access method and apparatus, where the method may include: respectively storing the mapping relation between the node access information of the blockchain nodes contained in each blockchain system and the chain domain name of the corresponding blockchain system; responding to a domain name identification request containing a target chain domain name of a second blockchain system sent by a first blockchain system, and determining target node access information corresponding to the target chain domain name according to the mapping relation; and returning the target node access information to the first blockchain system, so that the first blockchain system performs cross-chain access on the second blockchain system according to the target node access information.
Description
Technical Field
One or more embodiments of the present disclosure relate to the field of blockchain technologies, and in particular, to a method and an apparatus for accessing a blockchain across chains.
Background
The block chain technology (also called as distributed book technology) is a decentralized distributed database technology, has the characteristics of decentralization, openness and transparency, no tampering, trustiness and the like, and is suitable for application scenes with high requirements on data reliability. With the rapid development of the blockchain technology, blockchain systems facing different application scenarios and maintaining different data are continuously present, but due to the large difference between the blockchain systems, cross-chain interaction such as data communication and the like between different blockchain systems is difficult to achieve. In the related art, in order to implement cross-chain interaction between different blockchain systems, it is usually necessary for related personnel to perform uniform configuration and development on each blockchain system online, which is tedious and prone to errors.
Disclosure of Invention
In view of this, one or more embodiments of the present disclosure provide a method and apparatus for block chain cross-chain access.
To achieve the above object, one or more embodiments of the present disclosure provide the following technical solutions:
according to a first aspect of one or more embodiments of the present specification, there is provided a blockchain cross-chain access method applied to a blockchain domain name management system, the method including:
respectively storing the mapping relation between the node access information of the blockchain nodes contained in each blockchain system and the chain domain name of the corresponding blockchain system;
responding to a domain name identification request containing a target chain domain name of a second blockchain system sent by a first blockchain system, and determining target node access information corresponding to the target chain domain name according to the mapping relation;
and returning the target node access information to the first blockchain system, so that the first blockchain system performs cross-chain access on the second blockchain system according to the target node access information.
According to a second aspect of one or more embodiments of the present specification, there is provided a blockchain cross-chain access method applied to a blockchain system, the method including:
generating a registration request, wherein the registration request comprises node access information of a blockchain node contained in the blockchain system;
sending the registration request to a blockchain domain name management system, so that the blockchain domain name management system obtains and stores a mapping relation between the node access information and a target chain domain name corresponding to the blockchain system according to the registration request, wherein the mapping relation is used by the blockchain domain name management system to determine the received node access information corresponding to the target chain domain name, and the node access information is used for performing cross-chain access on the blockchain system.
According to a third aspect of one or more embodiments of the present specification, there is provided a blockchain cross-chain access method applied to a blockchain system, the method including:
generating a domain name identification request, wherein the domain name identification request comprises a target chain domain name;
sending the domain name identification request to a blockchain domain name management system so that the blockchain domain name management system determines target node access information corresponding to the target chain domain name according to the maintained mapping relationship between the node access information of the blockchain nodes contained in each blockchain system and the chain domain name of the corresponding blockchain system;
and receiving the target node access information returned by the block chain domain name management system, and performing cross-link access on the block chain system corresponding to the target chain domain name according to the target node access information.
According to a fourth aspect of one or more embodiments of the present specification, there is provided a blockchain cross-chain access apparatus, which is applied to a blockchain domain name management system; the device comprises:
the storage unit is used for respectively storing the mapping relation between the node access information of the block chain nodes contained in each block chain system and the chain domain names of the corresponding block chain systems;
a determining unit, configured to determine, according to the mapping relationship, target node access information corresponding to a target chain domain name of a second blockchain system in response to a domain name identification request that is sent by a first blockchain system and includes the target chain domain name;
and the information sending unit is used for returning the target node access information to the first blockchain system so that the first blockchain system performs cross-chain access on the second blockchain system according to the target node access information.
According to a fifth aspect of one or more embodiments of the present specification, there is provided a blockchain cross-chain access apparatus applied to a blockchain system; the device comprises:
a first generating unit, configured to generate a registration request, where the registration request includes node access information of a blockchain node included in the blockchain system;
a first request sending unit, configured to send the registration request to a blockchain domain name management system, so that the blockchain domain name management system obtains and stores a mapping relationship between the node access information and a target chain domain name corresponding to the blockchain system according to the registration request, where the mapping relationship is used by the blockchain domain name management system to determine node access information corresponding to the received target chain domain name, and the node access information is used to perform cross-chain access on the blockchain system.
According to a sixth aspect of one or more embodiments of the present specification, there is provided a blockchain cross-chain access apparatus applied to a blockchain system; the device comprises:
the second generation unit is used for generating a domain name identification request, and the domain name identification request comprises a target chain domain name;
a second request sending unit, configured to send the domain name identification request to a blockchain domain name management system, so that the blockchain domain name management system determines, according to a mapping relationship between node access information of blockchain nodes included in each maintained blockchain system and a chain domain name of a corresponding blockchain system, target node access information corresponding to the target chain domain name;
and the receiving unit is used for receiving the target node access information returned by the blockchain domain name management system and performing cross-link access on the blockchain system corresponding to the target chain domain name according to the target node access information.
According to a seventh aspect of one or more embodiments of the present specification, there is provided an electronic device. The electronic device includes:
a processor;
a memory for storing processor-executable instructions;
wherein the processor implements the method according to the first, second or third aspect by executing the executable instructions.
According to an eighth aspect of one or more embodiments of the present description, there is provided a computer readable storage medium having stored thereon computer instructions which, when executed by a processor, implement the steps of the method according to the first, second or third aspect.
As can be seen from the above technical solutions, in this specification, a blockchain domain name management system may store a mapping relationship between node access information of a blockchain node included in each blockchain system and a chain domain name of a corresponding blockchain system, and the blockchain domain name management system may determine target node access information corresponding to a target chain domain name according to the mapping relationship in response to a domain name identification request including the target chain domain name of a second blockchain system sent by a first blockchain system, and then only the target chain domain name of the second blockchain system needs to be maintained in the first blockchain system, and no more complex node access information of the second blockchain system needs to be stored in advance, so that a storage space of the first blockchain system may be saved, and when the node access information or the chain domain name of the second blockchain system changes, only the corresponding mapping relationship stored in the blockchain domain name management system needs to be updated, the accuracy of the mapping relation stored in the block chain domain name management system is guaranteed, the block chain domain name management system can return the determined target node access information to the first block chain system, the first block chain system can perform cross-chain access on the second block chain system according to the target node access information, and therefore the first block chain system can safely and quickly access the chain data corresponding to the second block chain system without manual configuration and development, and the efficiency of cross-chain access can be improved.
Drawings
Fig. 1 is a schematic diagram of a network architecture provided in an exemplary embodiment of the present specification.
Fig. 2 is a flowchart of a method for accessing a blockchain across chains according to an exemplary embodiment of the present disclosure.
Fig. 3 is a schematic diagram of a blockchain domain name management system according to an exemplary embodiment of the present disclosure.
Fig. 4 is a flowchart of another block chain cross-chain access method provided in an exemplary embodiment of the present specification.
Fig. 5 is a flowchart of another block chain cross-chain access method provided in an exemplary embodiment of the present specification.
Fig. 6 is a flowchart of another block chain cross-chain access method provided in an exemplary embodiment of the present specification.
Fig. 7 is a schematic structural diagram of an electronic device according to an exemplary embodiment of the present disclosure.
Fig. 8 is a block diagram of a blockchain cross-chain access device according to an exemplary embodiment of the present specification.
Fig. 9 is a block diagram of another block chain cross-chain access device provided in an exemplary embodiment of the present specification.
Fig. 10 is a block diagram of another block chain cross-chain access device provided in an exemplary embodiment of the present specification.
Detailed Description
Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the following exemplary embodiments do not represent all implementations consistent with one or more embodiments of the present specification. Rather, they are merely examples of apparatus and methods consistent with certain aspects of one or more embodiments of the specification, as detailed in the claims which follow.
It should be noted that: in other embodiments, the steps of the corresponding methods are not necessarily performed in the order shown and described herein. In some other embodiments, the method may include more or fewer steps than those described herein. Moreover, a single step described in this specification may be broken down into multiple steps for description in other embodiments; multiple steps described in this specification may be combined into a single step in other embodiments.
Fig. 1 is a schematic diagram of a network architecture provided by an exemplary embodiment. As shown in fig. 1, a first blockchain system 11, a blockchain domain name management system 12, and a second blockchain system 13 may be included. The blockchain domain name management system 12 may store a mapping relationship between node access information corresponding to at least one blockchain link point in any blockchain system and a chain domain name corresponding to the blockchain system, where the node access information may include information used for representing a corresponding blockchain node, such as a node address or a node name, and the chain domain name may be used for representing the corresponding blockchain system. The first blockchain system 11 may obtain target node access information corresponding to the target chain domain name returned by the blockchain domain name management system 12 by sending a domain name identification request including the target chain domain name to the blockchain domain name management system 12, and then the first blockchain system 11 may perform cross-link access on the second blockchain system 13 corresponding to the target chain domain name according to the determined target node access information.
The first blockchain system 11 and the second blockchain system 13 both include a plurality of blockchain nodes, and by submitting corresponding blockchain transactions to the blockchain nodes in the blockchain system, the blockchain transactions can trigger execution of corresponding intelligent contracts, and complex functions can be realized by calling the intelligent contracts. While smart contracts are pre-deployed executable code on a blockchain, smart contracts allow for trusted transactions to be conducted without third parties, and which transactions are traceable and irreversible. One or more interfaces can be defined in the intelligent contract, and each interface is used for realizing corresponding functions.
The blockchain domain name management system 12 may be a server that maintains a mapping relationship between node access information of at least one blockchain node in any blockchain system and a corresponding chain domain name of the blockchain system, or may be a blockchain system that deploys a trusted authentication blockchain for storing the mapping relationship, which is not limited in this specification.
In this specification, cross-chain access between the blockchain systems may be implemented by a blockchain domain name management system. The following examples are given for illustrative purposes.
Fig. 2 is a flowchart of a method for accessing a blockchain across chains according to an exemplary embodiment. As shown in fig. 2, the method is applied to a blockchain domain name management system (e.g., blockchain domain name management system 12 shown in fig. 1); the method may comprise the steps of:
In an embodiment, the blockchain domain name management system may respectively receive a registration request sent by any one blockchain system, where the registration request may include node access information of at least one blockchain node in the corresponding blockchain system, and the blockchain domain name management system may generate a corresponding chain domain name for the blockchain system according to the registration request, so that a mapping relationship between the node access information of the blockchain node included in each blockchain system and the corresponding chain domain name may be stored in the blockchain domain name management system. The node access information can be a node address and the like, and the chain domain name is simpler and more convenient to remember than the node access information.
In an embodiment, the blockchain domain name management system may be deployed with a trusted authentication blockchain, and then the mapping relationship may be stored in the trusted authentication blockchain, so that security and reliability of the mapping relationship maintained in the blockchain domain name management system may be ensured, and the mapping relationship may be prevented from being tampered. Of course, the blockchain domain name management system may also directly store the mapping relationship locally, which is not limited in this specification.
In an embodiment, the blockchain domain name management system may include a plurality of storage areas, and the blockchain systems corresponding to different storage areas belong to different blockchain types, respectively, where the blockchain types may be divided according to the types of data maintained in the blockchain system, for example, a blockchain system maintaining education-related data may be divided into education types, a blockchain system maintaining hospital-related data may be divided into medical types, and the like, which is not limited in this specification.
When the blockchain domain name management system stores the mapping relationship between the node access information contained in each blockchain system and the chain domain name of the corresponding blockchain system, the blockchain type corresponding to each blockchain system can be determined first, and then the mapping relationship corresponding to each blockchain system can be stored in the storage area corresponding to the determined blockchain type, so that the blockchain domain name management system can conveniently and quickly inquire the node access information of the blockchain node contained in each blockchain system from the corresponding storage area, and the operation efficiency of the blockchain domain name management system can be improved.
Step 204, in response to a domain name identification request containing a target chain domain name of a second blockchain system sent by a first blockchain system, determining target node access information corresponding to the target chain domain name according to the mapping relationship.
In an embodiment, the blockchain domain name management system may receive a domain name identification request that includes a target chain domain name of the second blockchain system and is sent by the first blockchain system, and then in response to the domain name identification request, the blockchain domain name management system may determine target node access information corresponding to the target chain domain name by finding a mapping relationship that includes the target chain domain name, where at this time, the first blockchain system only needs to maintain the target chain domain name of the second blockchain system, and does not need to store more complex node access information of the second blockchain system in advance, and a storage space of the first blockchain system may be saved. When the node access information or the chain domain name of the second blockchain system changes, the content of the corresponding mapping relation stored in the blockchain domain name management system only needs to be updated, so that the timeliness of updating the node access information and the chain domain name can be ensured, and the accuracy of the mapping relation stored in the blockchain domain name management system is ensured.
In an embodiment, when the blockchain domain name management system is deployed with a trusted authentication blockchain and the mapping relationship is verified in the trusted authentication blockchain, the blockchain domain name management system may determine target node access information corresponding to a target chain domain name by executing an intelligent contract code for identifying the chain domain name, and may quickly and accurately determine the target node access information corresponding to the target chain domain name.
In an embodiment, the blockchain domain name management system may return the determined target node access information to the first blockchain system, and the first blockchain system may perform cross-chain access to the second blockchain system according to the target node access information, and the first blockchain system may safely and quickly access to the data on the chain corresponding to the second blockchain system. When the determined target node access information corresponds to a plurality of blockchain nodes in the second blockchain system, the blockchain domain name management system can return the randomly selected node access information corresponding to one blockchain node to the first blockchain system, so that the resource consumption of transmitting the target node access information can be saved, and the efficiency of transmitting the target node access information can be improved. Or, the blockchain domain name management system may select node access information corresponding to a corresponding blockchain link point according to a preset priority order of the blockchain nodes, or the blockchain domain name management system may return all the node access information to the first blockchain system, which is not limited in this specification.
In an embodiment, the blockchain domain name management system may maintain the authority credentials acquired from each blockchain system, and the blockchain domain name management system may determine the target authority credentials corresponding to the target chain domain name, and then the blockchain domain name management system may transmit the target authority credentials to the first blockchain system, where of course, the blockchain domain name management system may transmit the target authority credentials and the target node access information together to the first blockchain system, or the blockchain domain name management system may transmit the target authority credentials and the target node access information separately to the first blockchain system, which is not limited in this specification.
The first blockchain system can call an intelligent contract interface matched with the target authority certificate in the second blockchain system according to the received target authority certificate, so that limited cross-chain access to the second blockchain system can be realized, the first blockchain system can be prevented from acquiring privacy data in the second blockchain system, and the safety of related data in the second blockchain system is ensured. For example, assuming that the authority credential of the second blockchain system maintained in the blockchain domain name management system is the authority root key, after the blockchain domain name management system receives the domain name identification request sent by the first blockchain system, the blockchain domain name management system may determine the authority root key corresponding to the target chain domain name included in the domain name identification request, so that a corresponding access key may be generated for the first blockchain system according to the determined authority root key, and an intelligent contract interface that can be accessed by the access key is preset in the second blockchain system, so that the first blockchain system may invoke the corresponding intelligent contract interface in the second blockchain system according to the access key. The intelligent contract interfaces that can be accessed by different access keys generated by the same authority root key are the same, or the intelligent contract interfaces that can be accessed by different access keys generated by the same authority root key are different, and the intelligent contract interfaces matched with the access keys can be configured according to actual requirements, which is not limited in this specification.
In an embodiment, the blockchain domain name management system may further maintain a cross-link contract, and a standardized cross-link access mechanism such as a data return structure and a data request structure of the cross-link contract may be preset in the cross-link contract. The blockchain domain name management system can deploy the cross-chain contract to a first blockchain system, and the first blockchain system can generate a standard structured cross-chain access request by calling the cross-chain contract, and the cross-chain access request can be used by the first blockchain system to initiate cross-chain access to a second blockchain system.
The blockchain domain name management system may deploy the cross-chain contract to a second blockchain system, and the second blockchain system may generate cross-chain access data of a standard structure by calling the cross-chain contract, and the second blockchain system may feed the cross-chain access data back to the first blockchain system in response to the cross-chain access request. Under the condition that the on-chain data structures maintained by the first blockchain system and the second blockchain system are different, cross-chain access requests, cross-chain access data and the like of a standard structure can be generated through cross-chain contract, so that cross-chain access between the first blockchain system and the second blockchain system can be realized without carrying out a large amount of configuration and development, and the efficiency of cross-chain access can be improved.
In an embodiment, a cross-chain contract may also be deployed in the blockchain domain name management system, and then, in a case where the on-chain data structures maintained in the first blockchain system, the second blockchain system, and the blockchain domain name management system are different, the blockchain domain name management system may generate a standardized cross-chain access request, cross-chain access data, and the like through the cross-chain contract, so that normal access and interaction between the blockchain domain name management system, the first blockchain system, and the second blockchain system may be implemented.
In an embodiment, the blockchain domain name management system may implement a preset function by calling a corresponding interface in the cross-link contract, and of course, the blockchain domain name management system may also execute contract codes of other intelligent contracts deployed in the blockchain domain name management system by calling the interface of the cross-link contract. For example, as shown in fig. 3, the blockchain domain name management system may execute the contract code of root domain contract 302, root domain contract 303, guest key generation contract 304, and access interface information contract 305 by calling interfaces preset within cross-chain contract 301, respectively. The block chain domain name management system is supposed to generate a complete chain domain name by calling different root domain contracts and sub-domain contracts to corresponding block chain systems, corresponding root domain contracts 302, 303, sub-domain contracts 1-6 and the like are preset in the block chain domain name management system, and meanwhile, the root domain corresponding to the root domain contract 302 is supposed to be education, and the root domain corresponding to the root domain contract 303 is supposed to be hospital. At this time, if the blockchain domain name management system receives that the registration request of the blockchain system includes the identifier 3021, the blockchain domain name management system may execute the contract codes of the root domain contract 302 and the sub-domain contract 1 according to a preset calling rule to generate a complete chain domain name for the blockchain system: test01.education, where test01 is generated by subdomain contract 1 and education is generated by root domain contract 302; if 3034 is included in the received registration request of the blockchain system, the blockchain domain name management system may execute the contract codes of the root domain contract 303 and the sub-domain contract 4 according to a preset invoking rule to generate a complete chain domain name for the blockchain system: chain domain names including different root domains and sub-domains can be generated for block chain systems belonging to different block chain types, thereby facilitating subsequent partition storage and facilitating accurate memorization of the chain domain names of the respective block chain systems.
In addition, after the blockchain domain name management system receives the domain name identification request including the target chain domain name sent by the first blockchain system, the blockchain domain name management system may execute the contract code of the guest key generation contract 304 according to a preset calling rule, so that the first blockchain system may generate a corresponding access key for the first blockchain system, and then the first blockchain system may call a corresponding intelligent contract interface in the second blockchain system corresponding to the target chain domain name according to the access key. Meanwhile, the blockchain domain name management system can execute a contract code of the access interface information contract 305 according to a preset calling rule, so that data interface information which can be accessed in a second blockchain system corresponding to the target chain domain name can be obtained, the first blockchain system can receive data interface information returned by the blockchain domain name management system, and at the moment, the first blockchain system can pointedly call a corresponding intelligent contract interface in the second blockchain system according to the data interface information. Certainly, the blockchain domain name management system may set a corresponding invocation rule and deploy a corresponding cross-link contract and other intelligent contracts according to actual requirements, which is not limited in this specification.
In an embodiment, the blockchain domain name management system may further directly maintain data access interface information acquired from each blockchain system, where the data access interface information may be used to indicate intelligent contract interface information that can be directly called through node access information of a corresponding blockchain system, and then the blockchain domain name management system may transmit the data access interface information to the first blockchain system, so that the first blockchain system can specifically call a corresponding intelligent contract interface, thereby improving the efficiency of cross-chain access.
In one embodiment, the first blockchain system and the second blockchain system are not substantially different, and the blockchain system sending the domain name identification request including the target chain domain name to the domain name management system may be regarded as the first blockchain system, and the blockchain system corresponding to the target chain domain name may be regarded as the second blockchain system. In other words, any blockchain system may become the first blockchain system or the second blockchain system.
In an embodiment, the interaction process between the blockchain domain name management system and each blockchain system, and the interaction process between the first blockchain system and the second blockchain system may be completed through a trusted physical channel, which is not limited in this specification.
Fig. 4 is a flowchart illustrating another block chain cross-chain access method shown in this specification. As shown in fig. 4, the method is applied to a blockchain system (e.g., the second blockchain system 13 shown in fig. 1); the method may comprise the steps of:
The specific implementation process of steps 402-404 is similar to the embodiment shown in fig. 2, and is not described here again.
Fig. 5 is a flowchart illustrating another method of block chain cross-chain access shown in this specification. As shown in fig. 5, the method is applied to a blockchain system (e.g., the first blockchain system 11 shown in fig. 1); the method may comprise the steps of:
step 502, a domain name identification request is generated, wherein the domain name identification request comprises a target chain domain name.
Step 506, receiving the target node access information returned by the blockchain domain name management system, and performing cross-link access on the blockchain system corresponding to the target chain domain name according to the target node access information.
The specific implementation process of steps 502-506 is similar to the embodiment shown in fig. 2, and is not described here again.
For ease of understanding, the following describes the technical solution of the present specification with reference to fig. 6 for an interaction process between the first blockchain system a, the second blockchain system B, and the blockchain domain name management system C. Assume that the on-chain data structures maintained by the first blockchain system a and the second blockchain system B are different, and thus the blockchain domain name management system C deploys a cross-chain contract X to the first blockchain system a and the second blockchain system B in advance. Fig. 6 is a flowchart illustrating a block chain cross-chain access method according to an exemplary embodiment of the present disclosure. As shown in fig. 6, the following steps may be included:
step 601, the second blockchain system B sends a registration request to the blockchain domain name management system C.
In this embodiment, the second blockchain system B may send a registration request to the blockchain domain name management system C, where the registration request may include the node address 172.1.2.3 of the node 11 and the node address 172.1.2.4 of the node 12 in the second blockchain system B, and of course, the registration request may also include the guest access root key Y of the second blockchain system B.
In this embodiment, the blockchain domain name management system C may generate a corresponding chain domain name chain.
In step 602, the blockchain domain name management system C stores the mapping relationship corresponding to the second blockchain system B.
In step 603, the blockchain domain name management system C returns an acceptance notification message to the second blockchain system B.
In this embodiment, the blockchain domain name management system C can obtain the mapping relationship corresponding to the second blockchain system B as follows: node address 172.1.2.3 and node address 172.1.2.4-guest access root key Y-chain domain name. And the block chain domain name management system C can store the mapping relation into the deployed credible authentication block chain, so that the authenticity and reliability of the mapping relation can be ensured, and the mapping relation can be prevented from being randomly tampered.
In this embodiment, after storing the mapping relationship, the blockchain domain name management system C may return a corresponding acceptance notification message to the second blockchain system B, and then the second blockchain system B may determine that the second blockchain system B has successfully registered according to the acceptance notification message.
In step 604, the first blockchain system a sends a domain name identification request to the blockchain domain name management system C.
In step 605, the domain name management system C determines the corresponding cross-link information.
In this embodiment, the first blockchain system a may send a domain name identification request including a chain domain name chain.test.blockchain to the blockchain domain name management system C, and the blockchain domain name management system C may determine the cross-chain information corresponding to the chain domain name chain.test.blockchain, that is, the node address 172.1.2.3 and the node address 172.1.2.4, and the guest access root key Y by executing an intelligent contract code for identifying the chain domain name.
In this embodiment, the blockchain domain name management system C may further generate an access key Z for the first blockchain system a according to the guest access root key Y.
In step 606, the blockchain domain name management system C returns cross-chain information to the first blockchain system a.
In this embodiment, the blockchain domain name management system C may send the selected node address 172.1.2.3 and the access key Z to the first blockchain system a, where in the case that the chain domain name is in. Of course, the blockchain domain name management system C may send all the node addresses to the first blockchain system a, which is not limited in this specification.
In step 607, the first blockchain system a sends a cross-chain access request to the second blockchain system B.
In this embodiment, the first blockchain system a may generate a standard-structured cross-chain access request by calling the cross-chain contract X, and the first blockchain system a may transmit the cross-chain access request to the corresponding blockchain link point 11 in the second blockchain system B according to the node address 172.1.2.3, where the cross-chain access request may include the access key Z.
In step 608, the second blockchain system B returns the cross-chain access data to the first blockchain system a.
In this embodiment, assuming that a specific interface of the cross-link contract X that can be invoked and corresponds to the access key Z is preset in the second blockchain system B, the blockchain node 11 in the second blockchain system B may call the specific interface in the cross-link contract X that is deployed in advance according to the cross-link access request, acquire cross-link access data of a standard structure, and return the acquired cross-link access data to the first blockchain system a, where the cross-link access data may be an execution situation, such as an execution success or an execution failure, of a preset function corresponding to the specific interface of the cross-link contract X in the blockchain node 11, and the cross-link access data may also be queried on-link data maintained in the second blockchain system B, which is not limited in this specification.
In this embodiment, the block link node 11 may execute the contract code corresponding to the specific interface in the cross-link contract X by calling the specific interface of the cross-link contract X, or the block link node 11 may execute the intelligent contract code corresponding to the specific interface in another intelligent contract different from the cross-link contract X by calling the specific interface of the cross-link contract X, which is not limited in this specification.
Fig. 7 shows a schematic structural diagram of an electronic device according to an exemplary embodiment of the present description. Referring to fig. 7, at the hardware level, the electronic device includes a processor 702, an internal bus 704, a network interface 706, a memory 708, and a non-volatile storage 710, but may also include hardware required for other services. The processor 702 reads a corresponding computer program from the non-volatile memory 710 into the memory 708 and then runs the computer program to form a block chain cross-chain access device on a logical level. Of course, besides the software implementation, the present specification does not exclude other implementations, such as logic devices or a combination of software and hardware, and the like, that is, the execution subject of the following processing flow is not limited to each logic unit, and may be hardware or logic devices.
Referring to fig. 8, in a software implementation, the block chain cross-chain access device may include a storage unit 801, a determination unit 802, and an information sending unit 803. Wherein:
a storage unit 801, configured to store mapping relationships between node access information of a blockchain node included in each blockchain system and chain domain names of corresponding blockchain systems, respectively;
a determining unit 802, configured to determine, according to the mapping relationship, target node access information corresponding to a target chain domain name in response to a domain name identification request that is sent by a first blockchain system and includes the target chain domain name of a second blockchain system;
an information sending unit 803, configured to return the target node access information to the first blockchain system, so that the first blockchain system performs cross-chain access to the second blockchain system according to the target node access information.
Optionally, the storage unit 801 is specifically configured to:
respectively receiving registration requests sent by each block chain system, wherein the registration requests comprise the node access information;
and respectively generating chain domain names corresponding to each block chain system according to the registration request, and storing the mapping relation between the node access information and the chain domain names.
Optionally, the storage unit 801 is specifically configured to:
and storing the mapping relation into a trusted authentication blockchain deployed in the blockchain system.
Optionally, the storage unit 801 is specifically configured to:
and determining target node access information corresponding to the target chain domain name by executing an intelligent contract code for identifying the chain domain name.
Optionally, the blockchain domain name management system includes a plurality of storage areas, and the blockchain systems corresponding to different storage areas respectively belong to different blockchain types; the storage unit 801 is specifically configured to:
determining a blockchain type corresponding to each blockchain system;
and storing the mapping relation corresponding to each blockchain system into a storage area corresponding to the corresponding blockchain type.
Optionally, the method further includes:
a credential determining unit 804, configured to determine a target authority credential corresponding to the target chain domain name, where the blockchain domain name management system maintains authority credentials obtained from each blockchain system;
a transmitting unit 805, configured to transmit the target permission credential to the first blockchain system, so that the first blockchain system invokes an intelligent contract interface, which is matched to the target permission credential, in the second blockchain system, so as to implement cross-chain access to the second blockchain system.
Optionally, the method further includes:
the block chain domain name management system maintains a cross-chain contract;
a first deployment unit 806, configured to deploy the cross-chain contract to the first blockchain system, the cross-chain contract being called by the first blockchain system to generate a standard structured cross-chain access request, the cross-chain access request being used by the first blockchain system to initiate cross-chain access to the second blockchain system;
a second deployment unit 807 for deploying the cross-link contract to the second blockchain system, wherein the cross-link contract is called by the second blockchain system to obtain cross-link access data of a standard structure, and is fed back to the first blockchain system in response to the cross-link access request.
The implementation process of the functions and actions of each unit in the above device is specifically described in the implementation process of the corresponding step in the above method, and is not described herein again.
Referring to fig. 9, in a software implementation, the blockchain inter-chain access apparatus may include a first generating unit 901 and a first request sending unit 902. Wherein:
a first generating unit 901, configured to generate a registration request, where the registration request includes node access information of a blockchain node included in the blockchain system;
a first request sending unit 902, configured to send the registration request to the blockchain domain name management system, so that the blockchain domain name management system obtains and stores a mapping relationship between the node access information and a target chain domain name corresponding to the blockchain system according to the registration request, where the mapping relationship is used by the blockchain domain name management system to determine node access information corresponding to the received target chain domain name, and the node access information is used to perform cross-chain access on the blockchain system.
The implementation process of the functions and actions of each unit in the above device is specifically described in the implementation process of the corresponding step in the above method, and is not described herein again.
Referring to fig. 10, in a software implementation, the blockchain inter-chain access device may include a second generating unit 1001, a second request transmitting unit 1002, and a receiving unit 1003. Wherein:
a second generating unit 1001, configured to generate a domain name identification request, where the domain name identification request includes a target chain domain name;
a second request sending unit 1002, configured to send the domain name identification request to a blockchain domain name management system, so that the blockchain domain name management system determines, according to a mapping relationship between node access information of blockchain nodes included in each maintained blockchain system and a chain domain name of a corresponding blockchain system, target node access information corresponding to the target chain domain name;
a receiving unit 1003, configured to receive the target node access information returned by the blockchain domain name management system, and perform cross-link access on the blockchain system corresponding to the target chain domain name according to the target node access information.
The systems, devices, modules or units illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product with certain functions. A typical implementation device is a computer, which may take the form of a personal computer, laptop computer, cellular telephone, camera phone, smart phone, personal digital assistant, media player, navigation device, email messaging device, game console, tablet computer, wearable device, or a combination of any of these devices.
In a typical configuration, a computer includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
The memory may include forms of volatile 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 a computer-readable medium.
Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, 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, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.
It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present specification. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the specification, as detailed in the appended claims.
The terminology used in the description herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the description. As used in this specification and the appended claims, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items.
It should be understood that although the terms first, second, third, etc. may be used herein to describe various information, these information should not be limited to these terms. These terms are only used to distinguish one type of information from another. For example, the first information may also be referred to as second information, and similarly, the second information may also be referred to as first information, without departing from the scope of the present specification. The word "if" as used herein may be interpreted as "at … …" or "when … …" or "in response to a determination", depending on the context.
The above description is only a preferred embodiment of the present disclosure, and should not be taken as limiting the present disclosure, and any modifications, equivalents, improvements, etc. made within the spirit and principle of the present disclosure should be included in the scope of the present disclosure.
Claims (15)
1. A block chain cross-chain access method is applied to a block chain domain name management system, wherein the block chain domain name management system comprises a plurality of storage areas, and block chain systems corresponding to different storage areas respectively belong to different block chain types; the method comprises the following steps:
the method for respectively storing the mapping relationship between the node access information of the blockchain nodes contained in each blockchain system and the chain domain names of the corresponding blockchain systems comprises the following steps: determining a block chain type corresponding to each block chain system, and storing a mapping relation corresponding to each block chain system into a storage area of the corresponding block chain type;
responding to a domain name identification request containing a target chain domain name of a second blockchain system sent by a first blockchain system, and determining target node access information corresponding to the target chain domain name according to the mapping relation;
and returning the target node access information to the first blockchain system, so that the first blockchain system performs cross-chain access on the second blockchain system according to the target node access information.
2. The method according to claim 1, wherein the separately storing the mapping relationship between the node access information of the blockchain node included in each blockchain system and the chain domain name of the corresponding blockchain system comprises:
respectively receiving registration requests sent by each block chain system, wherein the registration requests comprise the node access information;
and respectively generating chain domain names corresponding to each block chain system according to the registration request, and storing the mapping relation between the node access information and the chain domain names.
3. The method according to claim 1, wherein the separately storing the mapping relationship between the node access information of the blockchain node included in each blockchain system and the chain domain name of the corresponding blockchain system comprises:
and storing the mapping relation into a trusted authentication block chain deployed in the block chain domain name management system.
4. The method according to claim 3, wherein the determining, according to the mapping relationship, target node access information corresponding to the target chain domain name includes:
and determining target node access information corresponding to the target chain domain name by executing an intelligent contract code for identifying the chain domain name.
5. The method of claim 1, the blockchain domain name management system maintains permission credentials obtained from each blockchain system; the method further comprises the following steps:
determining a target authority certificate corresponding to the target chain domain name;
and transmitting the target authority certificate to the first blockchain system, and enabling the first blockchain system to call an intelligent contract interface matched with the target authority certificate in the second blockchain system so as to realize cross-chain access to the second blockchain system.
6. The method of claim 1, the blockchain domain name management system maintains a cross-link contract; the method further comprises the following steps:
deploying the cross-chain contract to the first blockchain system, the cross-chain contract being invoked by the first blockchain system to generate a standard structured cross-chain access request used by the first blockchain system to initiate cross-chain access to the second blockchain system;
and deploying the cross-link contract to the second blockchain system, wherein the cross-link contract is called by the second blockchain system to acquire cross-link access data of a standard structure, and the cross-link contract is fed back to the first blockchain system in response to the cross-link access request.
7. A block chain cross-chain access method is applied to a block chain system; the method comprises the following steps:
generating a registration request, wherein the registration request comprises node access information of a blockchain node contained in the blockchain system;
sending the registration request to a blockchain domain name management system, so that the blockchain domain name management system determines a mapping relationship between the node access information and a target chain domain name corresponding to the blockchain system and a blockchain type corresponding to the blockchain system according to the registration request, and stores the mapping relationship to a storage area corresponding to the determined blockchain type, wherein the mapping relationship is used by the blockchain domain name management system to determine the node access information corresponding to the received target chain domain name, and the node access information is used for performing cross-chain access on the blockchain system.
8. A block chain cross-chain access method is applied to a block chain system; the method comprises the following steps:
generating a domain name identification request, wherein the domain name identification request comprises a target chain domain name;
sending the domain name identification request to a blockchain domain name management system so that the blockchain domain name management system determines target node access information corresponding to a target chain domain name according to a mapping relation between node access information of blockchain nodes contained in each maintained blockchain system and the chain domain name of the corresponding blockchain system, wherein the blockchain domain name management system comprises a plurality of storage areas, the blockchain systems corresponding to different storage areas respectively belong to different blockchain types, and the mapping relation is stored in the storage area of the blockchain type corresponding to each blockchain system by the blockchain domain name management system;
and receiving the target node access information returned by the block chain domain name management system, and performing cross-link access on the block chain system corresponding to the target chain domain name according to the target node access information.
9. A block chain cross-chain access device is applied to a block chain domain name management system, wherein the block chain domain name management system comprises a plurality of storage areas, and block chain systems corresponding to different storage areas respectively belong to different block chain types; the device comprises:
the storage unit is used for respectively storing the mapping relationship between the node access information of the blockchain nodes contained in each blockchain system and the chain domain names of the corresponding blockchain systems, and comprises the following steps: determining a block chain type corresponding to each block chain system, and storing a mapping relation corresponding to each block chain system into a storage area of the corresponding block chain type;
a determining unit, configured to determine, according to the mapping relationship, target node access information corresponding to a target chain domain name of a second blockchain system in response to a domain name identification request that is sent by a first blockchain system and includes the target chain domain name;
and the information sending unit is used for returning the target node access information to the first blockchain system so that the first blockchain system performs cross-chain access on the second blockchain system according to the target node access information.
10. A block chain cross-chain access device is applied to a block chain system; the device comprises:
a first generating unit, configured to generate a registration request, where the registration request includes node access information of a blockchain node included in the blockchain system;
a first request sending unit, configured to send the registration request to a blockchain domain name management system, so that the blockchain domain name management system determines, according to the registration request, a mapping relationship between the node access information and a target chain domain name corresponding to the blockchain system and a blockchain type corresponding to the blockchain system, and stores the mapping relationship into a storage area corresponding to the determined blockchain type, where the mapping relationship is used by the blockchain domain name management system to determine node access information corresponding to the received target chain domain name, and the node access information is used for performing cross-chain access to the blockchain system.
11. A block chain cross-chain access device is applied to a block chain system; the device comprises:
the second generation unit is used for generating a domain name identification request, and the domain name identification request comprises a target chain domain name;
a second request sending unit, configured to send the domain name identification request to a blockchain domain name management system, so that the blockchain domain name management system determines, according to a mapping relationship between node access information of blockchain nodes included in each maintained blockchain system and chain domain names of corresponding blockchain systems, target node access information corresponding to the target chain domain name, where the blockchain domain name management system includes multiple storage areas, and the blockchain systems corresponding to the different storage areas respectively belong to different blockchain types, and the mapping relationship is stored in the storage area of the blockchain type corresponding to each blockchain system by the blockchain domain name management system;
and the receiving unit is used for receiving the target node access information returned by the blockchain domain name management system and performing cross-link access on the blockchain system corresponding to the target chain domain name according to the target node access information.
12. An electronic device, comprising:
a processor;
a memory for storing processor-executable instructions;
wherein the processor implements the method of any one of claims 1-6 by executing the executable instructions.
13. A computer readable storage medium having stored thereon computer instructions which, when executed by a processor, carry out the steps of the method according to any one of claims 1 to 6.
14. An electronic device, comprising:
a processor;
a memory for storing processor-executable instructions;
wherein the processor implements the method of any one of claims 7-8 by executing the executable instructions.
15. A computer readable storage medium having stored thereon computer instructions which, when executed by a processor, carry out the steps of the method according to any one of claims 7 to 8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011628016.9A CN112380294B (en) | 2020-12-31 | 2020-12-31 | Block chain cross-chain access method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011628016.9A CN112380294B (en) | 2020-12-31 | 2020-12-31 | Block chain cross-chain access method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112380294A CN112380294A (en) | 2021-02-19 |
| CN112380294B true CN112380294B (en) | 2021-04-06 |
Family
ID=74589925
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011628016.9A Active CN112380294B (en) | 2020-12-31 | 2020-12-31 | Block chain cross-chain access method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112380294B (en) |
Families Citing this family (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113328935B (en) * | 2021-05-20 | 2022-11-11 | 福建思特电子有限公司 | Distributed safety tracing block chain system based on industrial internet |
| CN113452701B (en) * | 2021-06-28 | 2023-04-18 | 上海计算机软件技术开发中心 | Cross-chain system and distributed user identity authentication method facing cross-chain system |
| CN113726563B (en) * | 2021-08-20 | 2023-10-27 | 上海浦东发展银行股份有限公司 | Block chain service access method, device, computer equipment and storage medium |
| CN114301866B (en) * | 2021-12-24 | 2024-06-07 | 杭州趣链科技有限公司 | Alliance chain communication method, system, electronic equipment and readable storage medium |
| CN114844896B (en) * | 2022-05-07 | 2023-07-04 | 深圳嘉业产业发展有限公司 | Resource sharing method and system based on block chain |
| CN115955317B (en) * | 2023-03-03 | 2023-05-26 | 鲜明技术(北京)有限公司 | Cross-blockchain resource storage method and device |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109167811A (en) * | 2018-07-27 | 2019-01-08 | 阿里巴巴集团控股有限公司 | A kind of across chain data access method and device based on block chain |
| CN110083606A (en) * | 2019-04-25 | 2019-08-02 | 深圳市豪斯莱科技有限公司 | Across chain storage method, terminal and storage medium |
| CN110199307A (en) * | 2018-11-16 | 2019-09-03 | 阿里巴巴集团控股有限公司 | The domain name scheme across chain interaction is carried out in block catenary system |
| CN110268677A (en) * | 2018-11-16 | 2019-09-20 | 阿里巴巴集团控股有限公司 | Across chain interaction is carried out using domain name scheme in block catenary system |
| US20190340267A1 (en) * | 2018-05-01 | 2019-11-07 | International Business Machines Corporation | Blockchain implementing cross-chain transactions |
| CN111193815A (en) * | 2019-12-24 | 2020-05-22 | 腾讯科技（深圳）有限公司 | Domain name resolution method, domain name resolution device, computer readable storage medium and computer equipment |
| CN111434085A (en) * | 2018-11-16 | 2020-07-17 | 阿里巴巴集团控股有限公司 | Domain name management scheme for cross-chain interaction in blockchain systems |
| CN111769958A (en) * | 2020-09-02 | 2020-10-13 | 百度在线网络技术（北京）有限公司 | Block chain cross-chain processing method, device, equipment and storage medium |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111741026B (en) * | 2020-08-07 | 2020-12-01 | 百度在线网络技术（北京）有限公司 | Cross-chain transaction request processing method, device, equipment and storage medium |
-
2020
- 2020-12-31 CN CN202011628016.9A patent/CN112380294B/en active Active
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20190340267A1 (en) * | 2018-05-01 | 2019-11-07 | International Business Machines Corporation | Blockchain implementing cross-chain transactions |
| CN109167811A (en) * | 2018-07-27 | 2019-01-08 | 阿里巴巴集团控股有限公司 | A kind of across chain data access method and device based on block chain |
| CN110199307A (en) * | 2018-11-16 | 2019-09-03 | 阿里巴巴集团控股有限公司 | The domain name scheme across chain interaction is carried out in block catenary system |
| CN110268677A (en) * | 2018-11-16 | 2019-09-20 | 阿里巴巴集团控股有限公司 | Across chain interaction is carried out using domain name scheme in block catenary system |
| CN111434085A (en) * | 2018-11-16 | 2020-07-17 | 阿里巴巴集团控股有限公司 | Domain name management scheme for cross-chain interaction in blockchain systems |
| CN110083606A (en) * | 2019-04-25 | 2019-08-02 | 深圳市豪斯莱科技有限公司 | Across chain storage method, terminal and storage medium |
| CN111193815A (en) * | 2019-12-24 | 2020-05-22 | 腾讯科技（深圳）有限公司 | Domain name resolution method, domain name resolution device, computer readable storage medium and computer equipment |
| CN111769958A (en) * | 2020-09-02 | 2020-10-13 | 百度在线网络技术（北京）有限公司 | Block chain cross-chain processing method, device, equipment and storage medium |
Non-Patent Citations (1)
| Title |
|---|
| 基于区块链的域名系统的设计与实现;陈小康;《中国优秀硕士学位论文全文数据库 信息科技辑》;20190415(第04期);正文第41-57页 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112380294A (en) | 2021-02-19 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112380294B (en) | Block chain cross-chain access method and device | |
| CN111614656B (en) | Credible management method and device for cross-link data and electronic equipment | |
| TWI762818B (en) | Blockchain-based invoice creation method and device, electronic device | |
| CN108848119B (en) | Cross-block-chain interaction method, device, system and electronic equipment | |
| US11423473B2 (en) | Blockchain-based leasing | |
| CN112101938B (en) | Digital seal using method and device based on block chain and electronic equipment | |
| CN106878367B (en) | Method and device for realizing asynchronous call of service interface | |
| CN111651467B (en) | Block chain node interface issuing and calling method and device | |
| CN110020945B (en) | Data reading method and system based on multiple block chain networks | |
| CN112200569B (en) | Digital seal using method and device based on block chain and electronic equipment | |
| CN111815454B (en) | Data uplink method and device, electronic equipment and storage medium | |
| CN113220717B (en) | Block chain-based data verification method and device and electronic equipment | |
| CN115002228B (en) | Service cascade calling method and device, electronic equipment and storage medium | |
| CN110990456A (en) | Block chain-based information reading and converting method, device and medium | |
| CN114745133A (en) | Method and device for identifying uniqueness of equipment | |
| CN112070342B (en) | Microservice evaluation method and device, electronic equipment and computer readable storage medium | |
| CN112291321B (en) | Service processing method, device and system | |
| CN113469815A (en) | Data management method and device | |
| US20230403254A1 (en) | Decentralized identifier determination by a registry operator or registrar | |
| CN110750537A (en) | Client identity recognition method and device, equipment and medium | |
| CN112738181B (en) | Method, device and server for cluster external IP access | |
| CN113849562A (en) | Method and device for accessing external service system | |
| CN112487497A (en) | Method and device for managing off-link files based on intelligent contracts and electronic equipment | |
| CN111258873A (en) | Test method and device | |
| CN114331447B (en) | Cross-link message submitting method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| REG | Reference to a national code |
Ref country code: HK Ref legal event code: DE Ref document number: 40045509 Country of ref document: HK |