DESC:FIELD
The present disclosure generally relates to the field of Distributed Ledger Technology (DLT). More particularly, the present disclosure relates to a system and a method for establishing communication between infrastructures of various Distributed Ledger Technology (DLT) networks.
DEFINITIONS

As used in the present disclosure, the following terms are generally intended to have the meaning as set forth below, except to the extent that the context in which they are used indicate otherwise.

Blockchain - The term ‘blockchain’ hereinafter refers a list of records called blocks, which are linked with each other, and secured using cryptographic techniques. Each block contains a cryptographic hash of a previous block, a timestamp, and transaction data.

Distributed Ledger Technology - The term ‘Distributed Ledger Technology (DLT)’ hereinafter refers to a consensus of replicated, shared, and synchronized digital data geographically spread across multiple sites, countries, or organizations. There is no central administrator or centralized data storage.
BACKGROUND
The background information herein below relates to the present disclosure but is not necessarily prior art.
Typically, an organization has multiple blockchain networks. For example, the organization may have two blockchain networks, i.e. one for financial transactions and other for inventory management. These blockchain networks may be a single blockchain platform or multiple platforms. All the nodes of each of the blockchain networks sit in a homogenous infrastructure. It is challenging to manage both the platforms separately for an administrator as the infrastructures only allow those networks to access their backend blockchain networks which exist on their cloud storage, thereby making them infrastructure dependent. Thus, these blockchain networks exist in isolation with no communication or interoperability with blockchain networks existing in other infrastructures. Therefore, it is challenging to manage multiple blockchain platforms like Ethereum, Hyperledger fabric, Corda, etc, over different infrastructures like cloud, virtual machines.
Therefore, there is felt a need to provide a system that helps in interaction of blockchain networks existing on different infrastructures.
OBJECTS
Some of the objects of the present disclosure, which at least one embodiment herein satisfies, are as follows:
Some of the objects of the present disclosure, which at least one embodiment herein satisfies, are as follows:
An object of the present disclosure is to provide a system and method for establishing communication between infrastructures of Distributed Ledger Technology (DLT) networks.
Another object of the present disclosure is to provide a system and method, which may simultaneously handle multiple DLT networks.
Yet another object of the present disclosure is to provide a system and method, which provides security over communication between heterogeneous DLT networks.
Another object of the present disclosure is to provide a system and method, which manages multiple DLT platforms over different infrastructures.
Still another object of the present disclosure is to provide a system and method for establishing communication between infrastructures of Distributed Ledger Technology (DLT) networks, which is flexible.
One of the objects of the present disclosure is to provide a system and method for establishing communication between infrastructures of Distributed Ledger Technology (DLT) networks, which is user friendly and easy to operate.
Another object of the present disclosure is to provide a system and method for establishing communication between infrastructures of Distributed Ledger Technology (DLT) networks that requires less memory and CPU footprint.
Other objects and advantages of the present disclosure will be more apparent from the following description, which is not intended to limit the scope of the present disclosure.
SUMMARY
The present disclosure envisages a system for establishing communication between infrastructures of Distributed Ledger Technology (DLT) networks, wherein each of the infrastructures has a plurality of nodes.
The system comprises an agent and a controller. The agent is embedded in each of the nodes of each of the infrastructures. The controller is configured to cooperate with each of the agents associated with each of the nodes. The controller is configured to track at least one parameter of each of the heterogeneous infrastructures, and is further configured to establish communication between the heterogeneous infrastructures based on tracking of the at least one parameter.

The controller comprises a memory and a processor. The memory is configured to store a set of pre-determined rules pertaining to blockchain network policies. The processor is capable of executing a plurality of modules stored in the memory. The processor is configured to cooperate with the memory to fetch the set of pre-determined rules to generate a plurality of system operating commands.
The plurality of modules comprises a monitoring module, an identifier module, a configuration module, an authentication module, and an interfacing module.

The monitoring module, under the set of system operating commands, is configured to track at least one parameter associated with each of the infrastructures, and is further configured to generate monitored information. The identifier module, under the set of system operating commands, is configured to cooperate with the monitoring module to receive the monitored information, and is further configured to identify at least one node, and create an identity for the identified node based on the monitored information. The configuration module, under the set of system operating commands, is configured to cooperate with the identifier module to receive the identity of the identified node, and is further configured to cooperate with the memory to set up the identified node based on the policies of each of the DLT networks, and generate a set up node data. The authentication module, under the set of system operating commands, is configured to cooperate with the configuration module to receive the set up node data, and is further configured to authenticate the set up node based on the set up node data, and generate an authenticated node. The interfacing module, under the set of system operating commands, is configured to cooperate with the authentication module to receive the authenticated node, and further configured to enable the authenticated node to communicate with the other nodes across the different infrastructures.

At least one parameter monitored by the monitoring module is selected from the group consisting of status of each of the nodes associated with each of the infrastructures, port information, peer nodes information, transactions information, and modifications or troubleshoot network related issues.

The policies include access control based policies, security policies, and usage control policies.

Each of the DLTs are enabled using virtualized docker containers. The DLTs are permissioned DLTs.
The present disclosure also envisages a method for managing multiple distributed ledger technology networks.
BRIEF DESCRIPTION OF THE ACCOMPANYING DRAWING
A system and a method for establishing communication between infrastructures of Distributed Ledger Technology networks of the present disclosure will now be described with the help of the accompanying drawing, in which:
Figure 1 illustrates a schematic block diagram of a system for establishing communication between infrastructures of Distributed Ledger Technology (DLT) networks; and
Figures 2 illustrates a flow chart of a method for establishing communication between infrastructures of various Distributed Ledger Technology (DLT) networks.
LIST OF REFERENCE NUMERALS
10a, 10b, 10c, 10d– Infrastructures
100 – Controller
102 – Memory
104 – Processor
108 – Monitoring module
110 – Identifier module
112 – Configuration module
114 – Authentication module
116 – Interfacing module
DETAILED DESCRIPTION
Embodiments, of the present disclosure, will now be described with reference to the accompanying drawing.
Embodiments are provided so as to thoroughly and fully convey the scope of the present disclosure to the person skilled in the art. Numerous details, are set forth, relating to specific components, and methods, to provide a complete understanding of embodiments of the present disclosure. It will be apparent to the person skilled in the art that the details provided in the embodiments should not be construed to limit the scope of the present disclosure. In some embodiments, well-known processes, well-known apparatus structures, and well-known techniques are not described in detail.
The terminology used, in the present disclosure, is only for the purpose of explaining a particular embodiment and such terminology shall not be considered to limit the scope of the present disclosure. As used in the present disclosure, the forms "a,” "an," and "the" may be intended to include the plural forms as well, unless the context clearly suggests otherwise. The terms "comprises," "comprising," “including,” and “having,” are open ended transitional phrases and therefore specify the presence of stated features, elements, modules, units and/or components, but do not forbid the presence or addition of one or more other features, elements, components, and/or groups thereof.
A distributed ledger, also called as shared ledger or DLT is a consensus of replicated, shared, and synchronized digital data geographically spread across multiple sites, countries, or institutons. The advantage of a DLT is that there is no central administration or central data storage. One form of distributed ledger design is the blockchain system which can be either public or private. A distributed ledger database is spread across a plurality of nodes on a peer-to-peer network. When a ledger update happens, each node constructs the new transaction, and then the nodes vote by a consensus algorithm on which copy is correct. Once a consensus is derived, all other nodes update themselves with the correct copy of ledger. There are two types of DLT networks - controlled/ permissioned DLT networks and permisionless DLT networks. Typically, the permissionless DLT networks are infrastructure agnostic and the permissioned DLT networks are infrastructure dependent.

For making the networks over the different infrastructures communicate with each other, a controller layer is added. The controller layer of the present disclosure consists of a controller.

The controller layer defines the components of the DLT networks. The components are infrastructure dependent components and infrastructure agnostic components. Each component of the blockchain has a virtualised docker container, and every container has its own role based on which it interacts with other components. By adding a controller layer, the features of the container or components of the DLT that are agnostic to infrastructure are defined and the components of the DLT that have dependency on the infrastructure are defined. The infrastructure dependent components are replicated across the multiple infrastructures and the addresses of the components are maintained. The controller layer keeps track of both dependent and agnostic components.

The controller of the present disclosure thus enables the dependent and the agnostic components of one infrastructure to communicate with dependent and the agnostic components of other infrastructure. The controller acts as a single infrastructure enabling data exchange and communication among multiple DLT network infrastructures. The blockchain has been developed in an open source technology, and due to the design of the blockchain, the blockchain has a infrastructure dependency.

The tracking of both infrastructure dependent and agnostic components is implemented by an agent. The agent is the controller implemented as a set of instructions with a low footprint that sits inside the start of each nodes of DLT’s. The nodes are the set of virtualised docker containers. The agent has different aspects related to it like security, network management, and monitoring. The network management and monitoring are the agnostic components of the network whereas the security is a dependent component.

For example, there are two heterogeneous DLT networks that wish to communicate with each other. The agent searches and deciphers the component of security in the other network to be mapped and where exactly the component is stored. The security component in each of the DLT networks is a dependent component. The agent monitors the application or the service calls that are required to be fetched from the other component of the network.

The agent thus allows multiple DLT networks to interact with each other, as homogeneous networks.
The agent has a big way to scale the blockchains of any infrastructure to a large level.
Referring to Figure 1, a system for establishing communication between infrastructures (10a, 10b, 10c, 10d) of various Distributed Ledger Technology (DLT) networks (hereinafter referred as "system"), of the present disclosure, is described. The system manages multiple blockchain networks over different infrastructures (10a, 10b, 10c, 10d), such as cloud, virtual machines, and the like. These blockchain networks can be a single blockchain platform or multiple platforms. The blockchain platforms include, but are not limited to, Ethereum, Hyperledger fabric, Corda, and the like. Each of the heterogeneous infrastructures (10a, 10b, 10c, 10d) comprise a plurality of nodes. The system comprises an agent and a controller (100). The agent is embedded in each of the nodes of each of the infrastructures (10a, 10b, 10c, 10d). The controller (100) is configured to cooperate with each of the agents associated with each of the nodes. The controller (100) is configured to track at least one parameter of each the heterogeneous infrastructures (10a, 10b, 10c, 10d), and is further configured to establish communication between the heterogeneous infrastructures (10a, 10b, 10c, 10d) based on the tracking of at least one parameter. In one embodiment, the plurality of infrastructures (10a, 10b, 10c, 10d) include, but not limited to, Unified Corporate Server (UCS), Azure, Google cloud, Amazon Web Services (AWS), and other cloud based storages. In another embodiment, each of the infrastructures (10a, 10b, 10c, 10d) includes information related to a corresponding blockchain network.
The controller (100) comprises a memory (102) and a processor (104). The memory (102) comprises a monitoring module (108), an identifier module (110), a configuration module (112), an authentication module (114), and an interfacing module (116).
The memory (102) is configured to store a set of pre-determined rules pertaining to blockchain network policies. The memory (102) includes any computer-readable medium known in the art including, for example, a volatile memory, such as static random access memory (SRAM) and dynamic random access memory (DRAM), and/or a non-volatile memory, such as read only memory (ROM), erasable programmable ROM, flash memories, hard disks, optical disks, and magnetic tapes, and/or a cloud based storage (cloud storage).

The processor (104) is configured to cooperate with the memory (102) to receive and process the pre-determined rules to obtain a set of operating commands. The processor (104) is implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, state machines, logic circuitries, and/or any device that manipulates signals based on operational instructions. Among other capabilities, the processor (104) may be configured to fetch and execute the set of predetermined rules stored in the memory (102) to control modules of the controller (100). It may be noted that the modules described herein may be implemented as software modules that may also be executed in the cloud-based computing environment of the system.
The monitoring module (108) is configured to track at least one parameter associated with each of the heterogeneous infrastructures (10a, 10b, 10c, 10d), and is further configured to generate monitored information under the set of system operating commands. The parameters monitored by the monitoring module (108) are selected from the group consisting of status of each of the nodes associated with each of the heterogeneous infrastructures (10a, 10b, 10c, 10d), port information, peer nodes information, transactions information, and modifications or troubleshoot network relates issues. In one embodiment, the monitoring module (108) is configured to monitor information, and store the monitored information in the memory (102). In an embodiment, the memory (102) includes a look-up table.
The identifier module (110) is configured to cooperate with the monitoring module (108), under the set of system operating commands, to receive the monitored information, and is further configured to identify at least one node, which is a part of multiple DLT networks running across different platforms in an organization, and create an identity for the identified node based on the monitored information.
The configuration module (112) is configured to cooperate with the identifier module (110), under the set of system operating commands, to receive the identity of the identified node. The configuration module (112) is further configured to cooperate with the memory (102) to set up the node based on policies of each of the DLT networks, and generate a set up node data. In an embodiment, the policies include, but are not limited to, access control based policies, security policies, and usage control policies.
The authentication module (114) is configured to cooperate with the configuration module (112), under the set of system operating commands, to receive the set up node data. The authentication module (114) is further configured to authenticate the set up node based on the set up node data, and generate an authenticated node. In an embodiment, the authenticated node includes remote computer's hardware, firmware, software, and/or user. In one embodiment, the authentication module (114) is configured to authenticate the set-up node using an authentication technique, which may include, but is not limited to, two-factor authentication technique, and security protocols such as cryptographic protocol or encryption protocol.
The interfacing module (116) is configured to cooperate with the authentication module (114), under the set of system operating commands, to receive the authenticated node. The interfacing module (116) is further configured to create an interface and enable the authenticated node across heterogeneous infrastructures to communicate with other nodes. In an embodiment, the interfacing module (116) provides a distributed application provisioning information received from multiple blockchain networks, which is in line with the application privileges.
In an embodiment, the controller (100) is implemented in the form of an agent (not shown in figure) that collects information for analysis and correlation, in real time. The agent is a low footprint agent program in the form of a set of instructions stored in each of the nodes. The agent requires a very small memory and CPU footprint, by default, and does not affect the controller’s usage. The agent can be configured to track health of the nodes. In another embodiment, the controller (100) is configured to provide flexibility to choose the infrastructures (10a, 10b, 10c, 10d) for provisioning.

In an embodiment, the DLTs are permissioned DLTs. Advantageously, each of the DLTs are enabled using virtualized docker containers.
Figure 2 illustrate a flow chart of a method of a controller for managing multiple DLT networks. The steps comprise:
• Step 202: embedding, by a controller (100), agents in a plurality of nodes of heterogeneous infrastructures (10a, 10b, 10c, 10d);
• Step 204: cooperating, by the controller (100), with the agents associated with the nodes;
• Step 206: tracking, by the controller (100), at least one parameter of each of the heterogeneous infrastructures (10a, 10b, 10c, 10d); and
• Step 208: establishing, by the controller (100), communication between the heterogeneous infrastructures (10a, 10b, 10c, 10d) based on tracking of the at least one parameter.

In an embodiment, establishing communication between the heterogeneous infrastructures (10a, 10b, 10c, 10d) further includes the following steps:
• Step 302: storing, in a memory (102), a set of pre-determined rules pertaining to blockchain network policies;
• Step 304: fetching, by a processor (104), the set of pre-determined rules;
• Step 306: generating, by the processor (104), a plurality of system operating commands based on the set of pre-determined rules;
• Step 308: tracking, by the processor (104), at least one parameter associated with each of the heterogeneous infrastructures (10a, 10b, 10c, 10d);
• Step 310: generating, by the processor (104), monitored information based on the tracking;
• Step 312: receiving, by the processor (104), the monitored information;
• Step 314: identifying, by the processor (104), at least one node which is a part of multiple DLT networks running across different platforms in an organization;
• Step 316: creating, by the processor (104), an identity for the identified node;
• Step 318: receiving, by the processor (104), the identity of the identified node;
• Step 320: setting up, by the processor (104), the node based on policies of each of the DLT networks;
• Step 322: generating, by the processor (104), the set up node data;
• Step 324: receiving, by the processor (104), the set up node data;
• Step 326: authenticating, by the authentication module (114), the set up node based on the set up node data;
• Step 328: generating, by the processor (104), an authenticated node;
• Step 330: receiving, by the processor (104), the authenticated node; and
• Step 332: enabling, by the processor (104), the authenticated node to communicate with the other nodes across the different infrastructures (10a, 10b, 10c, 10d).
The foregoing description of the embodiments has been provided for purposes of illustration and not intended to limit the scope of the present disclosure. Individual components of a particular embodiment are generally not limited to that particular embodiment, but, are interchangeable. Such variations are not to be regarded as a departure from the present disclosure, and all such modifications are considered to be within the scope of the present disclosure.
TECHNICAL ADVANCEMENTS
The present disclosure described herein above has several technical advantages including, but not limited to, the realization of a system and method for establishing communication between infrastructures of Distributed Ledger Technology (DLT) networks that:
• can simultaneously handle multiple DLT/ blockchain networks;
• provides security over communication between heterogeneous DLT/ blockchain networks;
• manages multiple DLT/ blockchain platforms over different infrastructure, such as cloud, virtual machines, and the like;
• is flexible;
• is user friendly and easy to operate; and
• require less memory and CPU footprint.
The embodiments herein and the various features and advantageous details thereof are explained with reference to the non-limiting embodiments in the following description. Descriptions of well-known components and processing techniques are omitted so as to not unnecessarily obscure the embodiments herein. The examples used herein are intended merely to facilitate an understanding of ways in which the embodiments herein may be practiced and to further enable those of skill in the art to practice the embodiments herein. Accordingly, the examples should not be construed as limiting the scope of the embodiments herein.
The foregoing description of the specific embodiments so fully reveal the general nature of the embodiments herein that others can, by applying current knowledge, readily modify and/or adapt for various applications such specific embodiments without departing from the generic concept, and, therefore, such adaptations and modifications should and are intended to be comprehended within the meaning and range of equivalents of the disclosed embodiments. It is to be understood that the phraseology or terminology employed herein is for the purpose of description and not of limitation. Therefore, while the embodiments herein have been described in terms of preferred embodiments, those skilled in the art will recognize that the embodiments herein can be practiced with modification within the spirit and scope of the embodiments as described herein.
The use of the expression “at least” or “at least one” suggests the use of one or more elements or ingredients or quantities, as the use may be in the embodiment of the disclosure to achieve one or more of the desired objects or results.
While considerable emphasis has been placed herein on the components and component parts of the preferred embodiments, it will be appreciated that many embodiments can be made and that many changes can be made in the preferred embodiments without departing from the principles of the disclosure. These and other changes in the preferred embodiment as well as other embodiments of the disclosure will be apparent to those skilled in the art from the disclosure herein, whereby it is to be distinctly understood that the foregoing descriptive matter is to be interpreted merely as illustrative of the disclosure and not as a limitation.
,CLAIMS:WE CLAIM:
1. A system for establishing communication between heterogeneous infrastructures (10a, 10b, 10c, 10d) of Distributed Ledger Technology (DLT) networks, wherein each of said heterogeneous infrastructures (10a, 10b, 10c, 10d) has a plurality of nodes, said system comprising:
• an agent embedded in each of said nodes of said heterogeneous infrastructures (10a, 10b, 10c, 10d); and
• a controller (100) configured to cooperate with said agents associated with said nodes, said controller configured to track at least one parameter of each said heterogeneous infrastructures (10a, 10b, 10c, 10d), and further configured to establish communication between said heterogeneous infrastructures (10a, 10b, 10c, 10d) based on tracking of said at least one parameter.

2. The system as claimed in claim 1, wherein said controller (100) comprises:
• a memory (102) configured to store a set of pre-determined rules pertaining to blockchain network policies;
• a processor (104) configured to cooperate with said memory (102) to fetch said set of pre-determined rules to generate a plurality of system operating commands, and wherein the processor (104) is capable of executing a plurality of modules stored in the memory (102), and wherein the plurality of modules comprising:
a monitoring module (108), under the set of system operating commands, configured to track at least one parameter associated with each of said infrastructures (10a, 10b, 10c, 10d), and further configured to generate monitored information;
an identifier module (110), under the set of system operating commands, configured to cooperate with said monitoring module (108) to receive said monitored information, and further configured to identify at least one node, and create an identity for said identified node based on said monitored information;
a configuration module (112), under the set of system operating commands, configured to cooperate with said identifier module (110) to receive said identity of said identified node, and further configured to cooperate with said memory (102) to set up said identified node based on said policies of each of said DLT networks, and generate a set up node data;
an authentication module (114), under the set of system operating commands, configured to cooperate with said configuration module (112) to receive said set up node data, and further configured to authenticate said set up node based on said set up node data, and generate an authenticated node; and
an interfacing module (116), under the set of system operating commands, configured to cooperate with said authentication module (114) to receive said authenticated node, and further configured to enable said authenticated node to communicate with said other nodes across said different infrastructures (10a, 10b, 10c, 10d).

3. The system as claimed in claim 1, wherein said at least one parameter monitored by said monitoring module (108) is selected from a group comprising status of each of said nodes associated with each of said infrastructures (10a, 10b, 10c, 10d), port information, peer nodes information, transactions information, and modifications or troubleshoot network related issues.

4. The system as claimed in claim 2, wherein said policies include access control based policies, security policies, and usage control policies.

5. The system as claimed in claim 1, wherein each of said DLTs are enabled using virtualized docker containers.

6. The system as claimed in claim 1, wherein said DLTs are permissioned DLTs.

7. A method for establishing communication between heterogeneous infrastructures (10a, 10b, 10c, 10d) of Distributed Ledger Technology (DLT) networks, said method comprises the following steps:

• embedding (202), by a controller (100), agents in a plurality of nodes of heterogeneous infrastructures (10a, 10b, 10c, 10d);
• cooperating (204), by said controller (100), with said agents associated with said nodes;
• tracking (206), by said controller (100), at least one parameter of each of said heterogeneous infrastructures (10a, 10b, 10c, 10d); and
• establishing (208), by said controller (100), communication between said heterogeneous infrastructures (10a, 10b, 10c, 10d) based on tracking of said at least one parameter.

8. The method as claimed in claim 7, wherein establishing communication between said heterogeneous infrastructures (10a, 10b, 10c, 10d) further includes the following steps:
• storing (302), in a memory (102), a set of pre-determined rules pertaining to blockchain network policies;
• fetching (304), by a processor (104), said set of pre-determined rules;
• generating (306), by said processor (104), a plurality of system operating commands based on said set of pre-determined rules;
• tracking (308), by said processor (104), at least one parameter associated with each of said infrastructures (10a, 10b, 10c, 10d);
• generating (310), by said processor (104), monitored information;
• receiving (312), by said processor (104), said monitored information;
• identifying (314), by said processor (104), at least one node which is a part of multiple DLT networks running across different platforms in an organization;
• creating (316), by said processor (104), an identity for said identified node;
• receiving (318), by said processor (104), said identity of said identified node;
• setting up (320), by said processor (104), said node based on policies of each of said DLT networks;
• generating (322), by said processor (104), said set up node data;
• receiving (324), by said processor (104), said set up node data;
• authenticating (326), by said processor (104), said set up node based on said set up node data;
• generating (328), by said processor (104), an authenticated node;
• receiving (330), by said processor (104), said authenticated node; and
• enabling (332), by said processor (104), said authenticated node to communicate with said other nodes across said different infrastructures (10a, 10b, 10c, 10d).