CN114362956B - Cross-link communication architecture and method of alliance chains - Google Patents
Cross-link communication architecture and method of alliance chains Download PDFInfo
- Publication number
- CN114362956B CN114362956B CN202111591651.9A CN202111591651A CN114362956B CN 114362956 B CN114362956 B CN 114362956B CN 202111591651 A CN202111591651 A CN 202111591651A CN 114362956 B CN114362956 B CN 114362956B
- Authority
- CN
- China
- Prior art keywords
- chain
- cross
- communication
- distributed communication
- task
- 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
- 238000004891 communication Methods 0.000 title claims abstract description 280
- 238000000034 method Methods 0.000 title claims abstract description 25
- 238000012795 verification Methods 0.000 claims abstract description 19
- 230000003993 interaction Effects 0.000 claims abstract description 9
- 239000003999 initiator Substances 0.000 claims abstract description 4
- 238000012545 processing Methods 0.000 claims description 21
- 230000006870 function Effects 0.000 claims description 14
- 230000002159 abnormal effect Effects 0.000 claims description 9
- 230000004044 response Effects 0.000 claims description 2
- 238000005516 engineering process Methods 0.000 description 8
- 230000008901 benefit Effects 0.000 description 4
- 238000012986 modification Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 238000006467 substitution reaction Methods 0.000 description 3
- 238000003491 array Methods 0.000 description 2
- 238000011161 development Methods 0.000 description 2
- 238000010586 diagram Methods 0.000 description 2
- 239000000463 material Substances 0.000 description 2
- 230000007246 mechanism Effects 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 230000008569 process Effects 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000009434 installation Methods 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
Landscapes
- Computer And Data Communications (AREA)
Abstract
The application discloses a cross-link communication architecture and method of a alliance chain, wherein the framework comprises: a source alliance chain as an initiator of cross-chain communication; a target alliance chain as a responder for cross-chain communication; the source alliance chain and the target alliance chain realize cross-chain communication through interaction between a source distributed communication cluster and a target distributed communication cluster; the cross-link communication is that a source distributed communication cluster obtains a cross-link communication task in a source alliance chain, interacts with a target distributed communication cluster corresponding to a target alliance chain according to task content, and obtains required information in the target alliance chain, wherein the required information is written into the source alliance chain after verification to be inquired by a source alliance chain user. The application innovatively deploys corresponding distributed communication clusters for the alliance chains needing cross-chain communication respectively, and achieves the goal of cross-chain communication among the alliance chains through interaction among the distributed communication clusters. The method can be widely applied to the technical field of block chains.
Description
Technical Field
The application relates to the technical field of blockchains, in particular to a cross-chain communication architecture and method of a alliance chain.
Background
In the technical system of the blockchain, the public chain has the problems of low throughput, transaction delay, privacy protection and the like. When the block chain technology is applied, the requirements of management cost, system performance, privacy protection and the like are considered by enterprises, and the actual items on the ground are mainly alliance chains. The alliance chain is a blockchain which is jointly participated and managed by a plurality of institutions or organizations, and compared with a public chain, the node quantity is relatively stable, an admission mechanism and an efficient consensus algorithm are adopted, and the system has higher transaction processing efficiency. Based on the characteristics, the alliance chain has remarkable advantages in the aspects of processing performance, transaction cost, convenience in supervision and the like, and meets the actual needs of enterprises better.
The blockchain technology has the advantages of decentralization, non-tampering, traceability and the like, and meanwhile different blockchains are mutually isolated, so that a plurality of information islands are formed, and further development and application of the blockchain technology are prevented. To solve the problem of "island" of information, a cross-link technology has been developed, and the existing mainstream cross-link technology includes: notary mechanisms, side chain/relay, hash locking, and distributed private key control, but these existing techniques all suffer from certain drawbacks.
Disclosure of Invention
In order to solve at least one of the technical problems existing in the prior art to a certain extent, the application aims to provide a cross-link communication architecture and method of a alliance link so as to solve the problem of 'island' of information.
The technical scheme adopted by the application is as follows:
a cross-chain communication architecture of a federated chain, comprising:
a source alliance chain as an initiator of cross-chain communication, comprising a source distributed communication cluster;
a target alliance chain, which is used as a response party of cross-chain communication and comprises a target distributed communication cluster;
the source alliance chain and the target alliance chain realize cross-chain communication through interaction between the source distributed communication cluster and the target distributed communication cluster;
the cross-link communication is that a source distributed communication cluster acquires a cross-link communication task in a source alliance chain, interacts with a target distributed communication cluster corresponding to a target alliance chain according to task content, and acquires required information in the target alliance chain, wherein the required information is written into the source alliance chain after verification for inquiring by a source alliance chain user;
the distributed communication clusters are formed by a plurality of distributed communication nodes, and each distributed communication node corresponds to a node of the alliance chain one by one, namely, the distributed communication clusters have a corresponding relation with the alliance chain.
Further, the distributed communication node accesses the federation chain by invoking an intelligent contract of the federation chain; the intelligent contract is code deployed in the federation chain to provide access to federation chain ledger functions for federation chain users and distributed communication nodes.
Further, the distributed communication node may send requests to other distributed communication nodes and respond to requests from other distributed communication nodes;
the cross-link communication task includes:
task ID, which is used to identify the task number of the cross-link communication task;
the targetClusterid is used for identifying the cluster number of the target distributed communication cluster;
the TaskKey is used for inquiring the inquiry key value of the information required in the target alliance chain;
flag, a Flag bit for marking completion or non-completion of a task;
TargetInfo for storing information bits of desired information;
consensu, for Consensus of the information endorsement required by the bit.
The application adopts another technical scheme that:
a method of cross-link communication for a federated chain, comprising the steps of:
source alliance chain users submit cross-chain communication tasks;
the source distributed communication node acquires a cross-chain communication task;
the source distributed communication node sends the cross-link communication task to a leader of the source distributed communication cluster;
the leader builds a pre-scheduling instruction according to the cross-link communication task and agrees with the pre-scheduling instruction in the source distributed communication cluster;
the leader builds a scheduling instruction according to the agreed pre-scheduling instruction, and schedules a task execution group to execute a cross-chain communication task;
the task execution group sends a request to the target distributed communication cluster according to the scheduling instruction so as to acquire the required information;
the task execution group sends the acquired required information and the digital signature thereof to the source distributed communication node;
the source distributed communication node constructs consensus on the required information, and writes the required information and the consensus information into the source alliance chain for the source alliance chain user to inquire.
Further, the source federation chain user submitting a cross-chain communication task, comprising:
the source alliance chain user submits a cross-chain communication task by calling an intelligent contract;
the source distributed communication node obtaining a cross-link communication task, comprising:
the source distributed communication node obtains the cross-chain communication task by invoking the intelligent contract.
Further, the leader is a distributed communication node responsible for task scheduling in a distributed communication cluster;
after receiving the cross-link communication task sent by the distributed communication node, the leader verifies the identity of the distributed communication node and the content of the cross-link communication task, and if the verification is passed, the leader carries out the next step, otherwise, the leader carries out corresponding processing according to an exception handling strategy.
Further, the prescheduling instruction comprises cross-chain communication tasks, task execution groups and task allocation information;
the leader broadcasts the prescheduling instruction in the distributed communication cluster, the distributed communication node verifies the identity of the leader and the prescheduling instruction after receiving the prescheduling instruction broadcast by the leader, if the verification is passed, the digital signature of the leader on the prescheduling instruction is provided for the leader, otherwise, the digital signature is correspondingly processed according to an abnormal processing strategy; the leader builds consensus according to the digital signatures provided by the distributed communication nodes, and the consensus is explained to be achieved when the number of the digital signatures exceeds a preset threshold value;
wherein the preset threshold is determined according to the number of distributed communication nodes.
Further, the scheduling instruction is composed of a pre-scheduling instruction and a consensus;
the task execution group consists of a plurality of source distributed communication nodes, and is designated by a leader in a prescheduling instruction; the leader sends the dispatching instruction to the task execution group to dispatch the task, the task execution group verifies the identity of the leader and the dispatching instruction after receiving the dispatching instruction of the leader, if the verification is passed, the leader is provided with a digital signature of the leader on the dispatching instruction, otherwise, the task execution group carries out corresponding processing according to an abnormal processing strategy.
Further, the task execution group sends a request to the target distributed communication cluster according to a scheduling instruction, including:
the task execution group sends a cross-link request to the target distributed communication node according to the scheduling instruction, the target distributed communication node verifies the identity of the sender and the content of the cross-link request when receiving the cross-link request, if the verification is passed, the target alliance chain is inquired about the required information, the required information and the digital signature thereof are returned to the sender, and otherwise, the corresponding processing is carried out according to the exception handling strategy.
Further, after the step of sending the acquired required information and the digital signature thereof to the source distributed communication node, the task execution group includes:
the source distributed communication node verifies the identity, the required information and the digital signature of the task execution group, if the verification is passed, the next step is carried out, otherwise, corresponding processing is carried out according to an exception handling strategy.
The beneficial effects of the application are as follows: according to the cross-link communication architecture of the alliance chains, corresponding distributed communication clusters are innovatively deployed for the alliance chains needing cross-link communication, and the goal of cross-link communication among the alliance chains is achieved through interaction among the distributed communication clusters; the distributed communication nodes correspond to the alliance chain link points, so that the application has the advantage of decentralization; the distributed communication clusters and the alliance chains are mutually independent, the specific technology of the bottom layer implementation of the alliance chains is not required to be considered, and the deployment is only required to be properly configured, so that the applicability is strong.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the following description is made with reference to the accompanying drawings of the embodiments of the present application or the related technical solutions in the prior art, and it should be understood that the drawings in the following description are only for convenience and clarity of describing some embodiments in the technical solutions of the present application, and other drawings may be obtained according to these drawings without the need of inventive labor for those skilled in the art.
FIG. 1 is a schematic diagram of a cross-chain communication architecture of a federated chain in an embodiment of the present application;
fig. 2 is a flow chart of a method for cross-link communication of a federated chain in an embodiment of the present application.
Detailed Description
Embodiments of the present application are described in detail below, examples of which are illustrated in the accompanying drawings, wherein like or similar reference numerals refer to like or similar elements or elements having like or similar functions throughout. The embodiments described below by referring to the drawings are illustrative only and are not to be construed as limiting the application. The step numbers in the following embodiments are set for convenience of illustration only, and the order between the steps is not limited in any way, and the execution order of the steps in the embodiments may be adaptively adjusted according to the understanding of those skilled in the art.
In the description of the present application, it should be understood that references to orientation descriptions such as upper, lower, front, rear, left, right, etc. are based on the orientation or positional relationship shown in the drawings, are merely for convenience of description of the present application and to simplify the description, and do not indicate or imply that the apparatus or elements referred to must have a particular orientation, be constructed and operated in a particular orientation, and thus should not be construed as limiting the present application.
In the description of the present application, a number means one or more, a number means two or more, and greater than, less than, exceeding, etc. are understood to not include the present number, and above, below, within, etc. are understood to include the present number. The description of the first and second is for the purpose of distinguishing between technical features only and should not be construed as indicating or implying relative importance or implicitly indicating the number of technical features indicated or implicitly indicating the precedence of the technical features indicated.
In the description of the present application, unless explicitly defined otherwise, terms such as arrangement, installation, connection, etc. should be construed broadly and the specific meaning of the terms in the present application can be reasonably determined by a person skilled in the art in combination with the specific contents of the technical scheme.
As shown in fig. 1, an embodiment of the present application provides a cross-link communication architecture of a federated chain, including the following:
the source alliance chain and the target alliance chain are respectively provided with a corresponding source distributed communication cluster and a corresponding target distributed communication cluster, and cross-chain communication is realized between the source alliance chain and the target alliance chain through interaction between the source distributed communication clusters and the target distributed communication clusters.
The source and target federation chains are initiator and responder, respectively, of cross-chain communications.
The distributed communication clusters are formed by a plurality of distributed communication nodes, each distributed communication node corresponds to nodes of the alliance chain one by one, an owner of each alliance chain node deploys the corresponding distributed communication node, namely, the distributed communication clusters have a corresponding relation with the alliance chain, and interaction among the distributed communication clusters realizes mutual trust by adopting a consensus method.
The distributed communication nodes may access the federation chain by invoking an intelligent contract of the federation chain and may send requests to and respond to requests from other distributed communication nodes.
The intelligent contract is code deployed in the federation chain to provide access to federation chain ledger functions for federation chain users and distributed communication nodes.
The intelligent contracts are deployed in the alliance chain, and include intelligent contracts for recording cross-chain communication tasks, intelligent contracts for recording distributed communication cluster information, intelligent contracts for recording correspondence between the alliance chain and the distributed communication clusters, and the like.
The cross-link communication task includes TaskID, targetClusterID, taskKey, flag, targetInfo, consensus, which is a task number for identifying the cross-link communication task, a cluster number for identifying the target distributed communication cluster, a query key value for querying the required information in the target alliance chain, a flag bit for marking whether the task is completed or not, an information bit for storing the required information, and a consensus bit for endorsing the required information.
The distributed communication cluster information includes ClusterID, membersList, publicKeyList, IPandPortList, which is a cluster number for identifying different distributed communication clusters, a list for storing all distributed communication node numbers, a list for storing all distributed communication node public keys, and a list for storing all distributed communication nodes IP and communication ports, wherein the public keys of the distributed communication nodes included in the distributed communication cluster information provide a trust basis for communication between the distributed communication nodes.
The corresponding relation between the alliance chain and the distributed communication cluster comprises a Member ID and a PeerID, which are respectively used for identifying node numbers of different distributed communication nodes and node numbers of different alliance chain nodes, and the identity of a node owner is determined to be processed correspondingly when the distributed communication nodes are wrongly operated through the corresponding relation.
The owner of the alliance chain node configures information such as public and private keys, communication ports and the like for determining identities for the corresponding distributed communication nodes, calls intelligent contracts, writes corresponding information into the alliance chain account book, and is ready for starting the distributed communication nodes.
The cross-link communication is to acquire a cross-link communication task in a source alliance chain through a source distributed communication cluster and to acquire required information in a target alliance chain through interaction with a target distributed communication cluster corresponding to the target alliance chain according to task content, wherein the required information is written into the source alliance chain after verification to provide source alliance chain users for inquiry.
Starting a distributed communication cluster, and calling an intelligent contract by a distributed communication node to acquire the corresponding relation between a alliance chain and the distributed communication cluster, wherein the intelligent contract is used for determining the corresponding relation between the alliance chain node and the distributed communication node; the distributed communication node calls an intelligent contract to acquire information of a distributed communication cluster, and the information is used for establishing communication with other distributed communication nodes; the distributed communication node invokes an intelligent contract to acquire a cross-link communication task for interacting with the target distributed communication cluster.
The distributed communication cluster elects a leader of the distributed communication cluster to be responsible for scheduling work of cross-chain communication tasks in a random competition mode of the distributed communication nodes.
As shown in fig. 2, an embodiment of the present application provides a method for cross-link communication of a federated chain, including the steps of:
s1: the source federation chain user submits the cross-chain communication task by invoking an intelligent contract.
S2: the source distributed communication node obtains the cross-chain communication task by invoking the intelligent contract.
S3: the source distributed communication node sends the cross-chain communication task to a leader of the source distributed communication cluster.
S4: the leader builds a prescheduling instruction according to the cross-chain communication task and agrees with the prescheduling instruction in the source distributed communication cluster.
S5: the leader builds a scheduling instruction according to the agreed pre-scheduling instruction, and schedules the task execution group to execute the cross-chain communication task.
S6: and the task execution group sends a request to the target distributed communication cluster according to the scheduling instruction so as to acquire the required information.
S7: the task execution group sends the acquired required information and the digital signature thereof to the source distributed communication node.
S8: the source distributed communication node constructs consensus on the required information, and writes the required information and the consensus information into the source alliance chain for the source alliance chain user to inquire.
The leader is a distributed communication node responsible for task scheduling in the distributed communication cluster, verifies the identity of the distributed communication node and the content of the cross-link communication task after receiving the cross-link communication task sent by the distributed communication node, and performs the next step if the verification is passed, otherwise, performs corresponding processing according to an exception handling strategy.
The pre-scheduling instruction comprises a cross-link communication task, a task execution group and task allocation information, a leader broadcasts the pre-scheduling instruction in a distributed communication cluster, a distributed communication node verifies the identity of the leader and the pre-scheduling instruction after receiving the pre-scheduling instruction broadcast by the leader, the digital signature of the pre-scheduling instruction is provided for the leader after the verification is passed, and otherwise, corresponding processing is carried out according to an abnormal processing strategy; the leader builds a consensus, i.e. a list of digital signatures, from the digital signatures provided by the distributed communication nodes, and the consensus is explained to be reached when the number of digital signatures exceeds half the number of distributed communication nodes.
The scheduling instruction consists of the pre-scheduling instruction and the consensus in the step S4, the task execution group consists of a plurality of source distributed communication nodes, and the task execution group is designated by a leader in the pre-scheduling instruction; the leader sends the dispatching instruction to the task execution group to dispatch the task, the task execution group verifies the identity of the leader and the dispatching instruction after receiving the dispatching instruction of the leader, if the verification is passed, the leader is provided with a digital signature of the leader on the dispatching instruction, otherwise, the task execution group carries out corresponding processing according to an abnormal processing strategy.
In step S6, the task execution group sends a cross-link request to the target distributed communication node according to the scheduling instruction, the target distributed communication node verifies the identity of the sender and the content of the cross-link request when receiving the cross-link request, and if the verification is passed, the target distributed communication node queries the required information in the target alliance chain and returns the required information and the digital signature thereof to the sender, otherwise, the target distributed communication node carries out corresponding processing according to the exception handling strategy.
In step S7, the source distributed communication node verifies the identity, the required information and the digital signature of the task execution group, if the verification is passed, the next step is performed, otherwise, corresponding processing is performed according to the exception handling policy.
In step S8, the source distributed communication node constructs a consensus, i.e. a digital signature list, according to the digital signature of the target distributed communication node for the required information, and when the number of digital signatures exceeds half of the number of the target distributed communication nodes, the consensus is explained, and at this time, the next step is performed.
The exception handling strategy comprises the following exceptions and handling methods:
1. the distributed communication node is offline. The offline state of the distributed communication node is marked as offline in the distributed communication cluster, and a normal distributed communication node does not communicate with an offline distributed communication node.
2. The leader goes offline. Firstly, marking the state of an offline leader as offline in a distributed communication cluster, and then reselecting a new leader according to election rules to ensure the normal operation of a task scheduling function.
3. The task execution group members are offline. Firstly, marking the state of an offline task execution group member as offline in a distributed communication cluster, then re-executing the offline task execution group member from the step S4 by a leader, and scheduling a corresponding cross-link communication task to ensure that the cross-link communication task is successfully completed.
4. The target distributed communication cluster is offline. The cross-link communication task is suspended, offline information is written into the alliance chain account book, and the corresponding cross-link communication task is refused to be submitted before the target distributed communication cluster resumes service.
5. The distributed communication node transmits spurious information. The state of the distributed communication node sending false information is marked as abnormal in the distributed communication cluster, the distributed communication node is isolated from the distributed communication cluster, and the normal distributed communication node does not communicate with the distributed communication node any more until the distributed communication node returns to normal.
6. The leader sends false information. And sending false information to process according to the distributed communication nodes, and reselecting a new leader according to election rules to ensure the normal operation of a task scheduling function.
7. The task execution group members send false information. And (3) sending false information to process according to the distributed communication nodes, re-executing the false information from the step S4 by the leader, and scheduling corresponding cross-link communication tasks to ensure that the cross-link communication tasks are successfully completed.
8. The leader denies service. Firstly, marking the state of a leader refusing service as abnormal in a distributed communication cluster, isolating the leader refusing service from the distributed communication cluster, and then, reselecting a new leader according to an election rule to ensure the normal operation of a task scheduling function.
9. Task execution group members refuse services. Firstly, marking the state of a task execution group member refusing service as abnormal in a distributed communication cluster and isolating the task execution group member refusing service from the distributed cluster, and then, re-executing the task execution group member from the distributed cluster by a leader from the step S4, and scheduling corresponding cross-link communication tasks to ensure that the cross-link communication tasks are successfully completed.
In summary, in this embodiment, corresponding distributed communication clusters are innovatively introduced for each coalition chain requiring cross-chain communication, and cross-chain communication between coalition chains is implemented through interaction between the distributed communication clusters corresponding to the coalition chains, so that the problem of "island" of information between the coalition chains is solved, and further development and application of blockchain technology are promoted. Wherein, the distributed communication nodes forming the distributed communication cluster correspond to the alliance chain link points, so that the application has the advantage of decentralization; the distributed communication clusters and the alliance chains are mutually independent, and the specific technical applicability of the bottom implementation of the alliance chains is strong without consideration.
In some alternative embodiments, the functions/acts noted in the block diagrams may occur out of the order noted in the operational illustrations. For example, two blocks shown in succession may in fact be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the functionality/acts involved. Furthermore, the embodiments presented and described in the flowcharts of the present application are provided by way of example in order to provide a more thorough understanding of the technology. The disclosed methods are not limited to the operations and logic flows presented herein. Alternative embodiments are contemplated in which the order of various operations is changed, and in which sub-operations described as part of a larger operation are performed independently.
Furthermore, while the application is described in the context of functional modules, it should be appreciated that, unless otherwise indicated, one or more of the described functions and/or features may be integrated in a single physical device and/or software module or one or more functions and/or features may be implemented in separate physical devices or software modules. It will also be appreciated that a detailed discussion of the actual implementation of each module is not necessary to an understanding of the present application. Rather, the actual implementation of the various functional modules in the apparatus disclosed herein will be apparent to those skilled in the art from consideration of their attributes, functions and internal relationships. Accordingly, one of ordinary skill in the art can implement the application as set forth in the claims without undue experimentation. It is also to be understood that the specific concepts disclosed are merely illustrative and are not intended to be limiting upon the scope of the application, which is to be defined in the appended claims and their full scope of equivalents.
The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art or in a part of the technical solution, in the form of a software product stored in a storage medium, comprising several instructions for causing a computer device (which may be a personal computer, a server, a network device, etc.) to perform all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (RAM, random Access Memory), a magnetic disk, or an optical disk, or other various media capable of storing program codes.
Logic and/or steps represented in the flowcharts or otherwise described herein, e.g., a ordered listing of executable instructions for implementing logical functions, can be embodied in any computer-readable medium for use by or in connection with an instruction execution system, apparatus, or device, such as a computer-based system, processor-containing system, or other system that can fetch the instructions from the instruction execution system, apparatus, or device and execute the instructions. For the purposes of this description, a "computer-readable medium" can be any means that can contain, store, communicate, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device.
More specific examples (a non-exhaustive list) of the computer-readable medium would include the following: an electrical connection (electronic device) having one or more wires, a portable computer diskette (magnetic device), a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber device, and a portable compact disc read-only memory (CDROM). In addition, the computer readable medium may even be paper or other suitable medium on which the program is printed, as the program may be electronically captured, via, for instance, optical scanning of the paper or other medium, then compiled, interpreted or otherwise processed in a suitable manner, if necessary, and then stored in a computer memory.
It is to be understood that portions of the present application may be implemented in hardware, software, firmware, or a combination thereof. In the above-described embodiments, the various steps or methods may be implemented in software or firmware stored in a memory and executed by a suitable instruction execution system. For example, if implemented in hardware, as in another embodiment, may be implemented using any one or combination of the following techniques, as is well known in the art: discrete logic circuits having logic gates for implementing logic functions on data signals, application specific integrated circuits having suitable combinational logic gates, programmable Gate Arrays (PGAs), field Programmable Gate Arrays (FPGAs), and the like.
In the foregoing description of the present specification, reference has been made to the terms "one embodiment/example", "another embodiment/example", "certain embodiments/examples", and the like, means that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the application. In this specification, schematic representations of the above terms do not necessarily refer to the same embodiments or examples. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples.
While embodiments of the present application have been shown and described, it will be understood by those of ordinary skill in the art that: many changes, modifications, substitutions and variations may be made to the embodiments without departing from the spirit and principles of the application, the scope of which is defined by the claims and their equivalents.
While the preferred embodiment of the present application has been described in detail, the present application is not limited to the above embodiments, and various equivalent modifications and substitutions can be made by those skilled in the art without departing from the spirit of the present application, and these equivalent modifications and substitutions are intended to be included in the scope of the present application as defined in the appended claims.
Claims (9)
1. A cross-link communication architecture for a federated chain, comprising:
a source alliance chain as an initiator of cross-chain communication, comprising a source distributed communication cluster;
a target alliance chain, which is used as a response party of cross-chain communication and comprises a target distributed communication cluster;
the source alliance chain and the target alliance chain realize cross-chain communication through interaction between the source distributed communication cluster and the target distributed communication cluster;
the cross-link communication is that a source distributed communication cluster acquires a cross-link communication task in a source alliance chain, interacts with a target distributed communication cluster corresponding to a target alliance chain according to task content, and acquires required information in the target alliance chain, wherein the required information is written into the source alliance chain after verification for inquiring by a source alliance chain user;
the distributed communication cluster consists of a plurality of distributed communication nodes, and each distributed communication node corresponds to a node of the alliance chain respectively, namely the distributed communication cluster has a corresponding relation with the alliance chain; the distributed communication node may send requests to other distributed communication nodes and respond to requests from other distributed communication nodes;
the cross-link communication task includes:
task ID, which is used to identify the task number of the cross-link communication task;
the targetClusterid is used for identifying the cluster number of the target distributed communication cluster;
the TaskKey is used for inquiring the inquiry key value of the information required in the target alliance chain;
flag, a Flag bit for marking completion or non-completion of a task;
TargetInfo for storing information bits of desired information;
and the Consensus is used for storing the Consensus position of the required information endorsement.
2. The federation chain cross-chain communications architecture of claim 1, wherein the distributed communications nodes access the federation chain by invoking intelligent contracts for the federation chain; the intelligent contract is code deployed in the federation chain to provide access to federation chain ledger functions for federation chain users and distributed communication nodes.
3. A method of cross-link communication for a federated chain, comprising the steps of:
source alliance chain users submit cross-chain communication tasks;
the source distributed communication node acquires a cross-chain communication task;
the source distributed communication node sends the cross-link communication task to a leader of the source distributed communication cluster;
the leader builds a pre-scheduling instruction according to the cross-link communication task and agrees with the pre-scheduling instruction in the source distributed communication cluster;
the leader builds a scheduling instruction according to the agreed pre-scheduling instruction, and schedules a task execution group to execute a cross-chain communication task;
the task execution group sends a request to the target distributed communication cluster according to the scheduling instruction so as to acquire the required information;
the task execution group sends the acquired required information and the digital signature thereof to the source distributed communication node;
the source distributed communication node constructs consensus on the required information, and writes the required information and the consensus information into the source alliance chain for the source alliance chain user to inquire.
4. A method of cross-chain communication of federated chains as claimed in claim 3, wherein said source federated chain user submitting cross-chain communication tasks comprising:
the source alliance chain user submits a cross-chain communication task by calling an intelligent contract;
the source distributed communication node obtaining a cross-link communication task, comprising:
the source distributed communication node obtains the cross-chain communication task by invoking the intelligent contract.
5. A method of cross-chain communication of a federated chain as claimed in claim 3 wherein the leader is a distributed communication node responsible for task scheduling in a distributed communication cluster;
after receiving the cross-link communication task sent by the distributed communication node, the leader verifies the identity of the distributed communication node and the content of the cross-link communication task, and if the verification is passed, the leader carries out the next step, otherwise, the leader carries out corresponding processing according to an exception handling strategy.
6. A method of cross-link communication of a federated chain as claimed in claim 3 wherein said prescheduling instructions include cross-link communication tasks, task execution groups and task allocation information;
the leader broadcasts the prescheduling instruction in the distributed communication cluster, the distributed communication node verifies the identity of the leader and the prescheduling instruction after receiving the prescheduling instruction broadcast by the leader, if the verification is passed, the digital signature of the leader on the prescheduling instruction is provided for the leader, otherwise, the digital signature is correspondingly processed according to an abnormal processing strategy; the leader builds consensus according to the digital signatures provided by the distributed communication nodes, and the consensus is explained to be achieved when the number of the digital signatures exceeds a preset threshold value;
wherein the preset threshold is determined according to the number of distributed communication nodes.
7. The method of claim 6, wherein the scheduling instruction is composed of a pre-scheduling instruction and a consensus;
the task execution group consists of a plurality of source distributed communication nodes, and is designated by a leader in a prescheduling instruction; the leader sends the dispatching instruction to the task execution group to dispatch the task, the task execution group verifies the identity of the leader and the dispatching instruction after receiving the dispatching instruction of the leader, if the verification is passed, the leader is provided with a digital signature of the leader on the dispatching instruction, otherwise, the task execution group carries out corresponding processing according to an abnormal processing strategy.
8. A method of cross-chain communication of federated chains as claimed in claim 3, wherein said task execution group sends a request to a target distributed communication cluster according to a scheduling instruction, comprising:
the task execution group sends a cross-link request to the target distributed communication node according to the scheduling instruction, the target distributed communication node verifies the identity of the sender and the content of the cross-link request when receiving the cross-link request, if the verification is passed, the target alliance chain is inquired about the required information, the required information and the digital signature thereof are returned to the sender, and otherwise, the corresponding processing is carried out according to the exception handling strategy.
9. A method of cross-link communication of a federated chain as claimed in claim 3 wherein, after the step of the task execution group sending the acquired required information and its digital signature to the source distributed communication node, it comprises:
the source distributed communication node verifies the identity, the required information and the digital signature of the task execution group, if the verification is passed, the next step is carried out, otherwise, corresponding processing is carried out according to an exception handling strategy.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111591651.9A CN114362956B (en) | 2021-12-23 | 2021-12-23 | Cross-link communication architecture and method of alliance chains |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111591651.9A CN114362956B (en) | 2021-12-23 | 2021-12-23 | Cross-link communication architecture and method of alliance chains |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114362956A CN114362956A (en) | 2022-04-15 |
| CN114362956B true CN114362956B (en) | 2023-08-18 |
Family
ID=81100836
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111591651.9A Active CN114362956B (en) | 2021-12-23 | 2021-12-23 | Cross-link communication architecture and method of alliance chains |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114362956B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114841702B (en) * | 2022-07-05 | 2022-09-13 | 国网数字科技控股有限公司 | Side chain technology-based intelligent energy multi-microgrid system |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111090661A (en) * | 2019-12-10 | 2020-05-01 | 北京海益同展信息科技有限公司 | Block chain cross-chain data access method, device, adapter and system |
| CN111654465A (en) * | 2020-04-17 | 2020-09-11 | 全球能源互联网研究院有限公司 | Power service cross-domain credible authentication system and method based on block chain |
| CN113328997A (en) * | 2021-05-10 | 2021-08-31 | 东软集团股份有限公司 | Alliance chain cross-chain system and method |
| CN113489671A (en) * | 2021-05-11 | 2021-10-08 | 深圳前海移联科技有限公司 | Cross-alliance-link communication method and device, computer equipment and storage medium |
-
2021
- 2021-12-23 CN CN202111591651.9A patent/CN114362956B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111090661A (en) * | 2019-12-10 | 2020-05-01 | 北京海益同展信息科技有限公司 | Block chain cross-chain data access method, device, adapter and system |
| CN111654465A (en) * | 2020-04-17 | 2020-09-11 | 全球能源互联网研究院有限公司 | Power service cross-domain credible authentication system and method based on block chain |
| CN113328997A (en) * | 2021-05-10 | 2021-08-31 | 东软集团股份有限公司 | Alliance chain cross-chain system and method |
| CN113489671A (en) * | 2021-05-11 | 2021-10-08 | 深圳前海移联科技有限公司 | Cross-alliance-link communication method and device, computer equipment and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114362956A (en) | 2022-04-15 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP1648118B1 (en) | Bridge node with MAC address table overflow protection | |
| CN111526186A (en) | Distributed server cluster configuration method based on Raft | |
| CN110147684A (en) | For realizing the method and apparatus of block chain data-privacy protection | |
| CN103427995B (en) | User authentication method, SSL (security socket layer) VPN (virtual private network) server and SSL VPN system | |
| CN114363352B (en) | Cross-chain interaction method of Internet of things system based on block chain | |
| CN113850599B (en) | Cross-link transaction method and system applied to alliance link | |
| CN112672357B (en) | Method and device for processing user account in service system and computer equipment | |
| CN113806699B (en) | Cross-blockchain identity verification method and system in inter-cloud computing environment | |
| CN114401091B (en) | Device cross-domain authentication management method and device based on block chain | |
| CN114362956B (en) | Cross-link communication architecture and method of alliance chains | |
| CN110266763A (en) | Block chain network implementation method, system and the storage medium of cross-network segment interconnection | |
| CN109669955A (en) | A kind of digital asset inquiry system and method based on block chain | |
| CN111899019A (en) | Method and system for cross validation and sharing of blacklist and multiple parties | |
| CN112950201B (en) | Node management method and related device applied to block chain system | |
| CN116523518B (en) | Cross-channel data access method, system and storage medium based on blockchain | |
| CN110493323B (en) | Block chain-based fairness file distribution method, system and storage medium | |
| CN110162274A (en) | A kind of data processing method based on block chain, device and equipment | |
| CN101998377A (en) | Method and device for protecting IMSI (International Mobile Subscriber Identity) and communication system | |
| CN115829731A (en) | Transaction information processing method and device | |
| CN110071966B (en) | Block chain networking and data processing method based on cloud platform | |
| CN112037055A (en) | Transaction processing method and device, electronic equipment and readable storage medium | |
| CN111222989A (en) | Transaction method of multi-channel block chain, electronic device and storage medium | |
| CN110808841A (en) | Communication system based on block chain network and communication method thereof | |
| CN113055886B (en) | Terminal authentication method, system, server and medium in edge computing network | |
| CN111695902A (en) | Block chain-based interconnection method and device and computer storage medium |
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 |