DESC:RESERVATION OF RIGHTS
A portion of the disclosure of this patent document contains material, which is subject to intellectual property rights such as, but are not limited to, copyright, design, trademark, IC layout design, and/or trade dress protection, belonging to Jio Platforms Limited (JPL) or its affiliates (hereinafter referred as owner). The owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent files or records, but otherwise reserves all rights whatsoever. All rights to such intellectual property are fully reserved by the owner. Further, the patent document also proposes techniques that may contribute to the 3GPP Technical Specification (TS) for current and future generation network technologies (i.e., 5G/6G networks).

TECHNICAL FIELD
[0001] The present disclosure relates to the field of blockchain platforms. More particularly, the present disclosure relates to system for emulating quantum entanglement in microservices-based realizations of blockchain platforms.

BACKGROUND
[0002] Background description includes information that may be useful in understanding the present invention. It is not an admission that any of the information provided herein is prior art or relevant to the presently claimed invention, or that any publication specifically or implicitly referenced is prior art.
[0003] “Quantum entanglement” is a phenomenon in physics where two photons or electrons can become entangled as they interact with each other. Subsequently, even as these entangled photons or electrons are separated from each other, they remain entangled until a measurement is made on one of the particles. Each photon or electron can be in a superposition of states until the photon is observed, or an observation leads to a wave function collapse to one of the possible states.
[0004] When the quantum entangled state of the two directly entangled particles is observed, then state of one of the particle collapses to either |0> or |1>, and the state of the other particle also collapses to the same identical state |0> or |1> respectively. Alternatively, if the quantum entangled state of two inversely entangled particles is observed, then the state of one of the particles collapses to either |0> or |1>, and the state of the other particle collapses to the opposite state |1> or |0> respectively. This is possible for example, when particles of opposite spins are created, so that their entanglement has an opposite correlation.
[0005] Emerging microservices-based blockchain platforms have not leveraged the benefits of quantum physics and particularly quantum entanglement owing to practical limitations, for example, in terms of the speeds associated with the speed of quantum particles. In addition, there are no tools available for satisfactory emulation of emerging communication networks and blockchain platforms for modelling based on principles of quantum entanglement.
[0006] There is, therefore, a need for a system for satisfactorily implementing and emulating quantum entanglement in microservices-based realizations of blockchain platforms and emerging communication networks.

OBJECTS OF THE INVENTION
[0007] Some of the objects of the present disclosure, which at least one embodiment herein satisfy are as listed herein below.
[0008] In a general aspect, the present disclosure provides a system and a method to virtually emulate quantum entanglement in software on a microservices-based blockchain platform.
[0009] In another aspect, the present disclosure provides a blockchain system that could leverage the state of real-entangled quantum particles.
[0010] In yet another aspect, the present disclosure provides a system and a method that enables a blockchain platform and emerging communication networks to reap the benefits associated with quantum entanglement.
[0011] In a still further aspect, the present disclosure enables use of quantum entanglement to provide support for fast “spooky action-at-a-distance” in emerging networks supporting fast synchronized state updates across nodes, and quantum-random-fairness in selection in emerging blockchain systems.
[0012] In another aspect, the present disclosure introduces the concept of quantum particle/quantum state in blockchain systems and emerging communication networks by representing the quantum particle/quantum state by an equivalent Quantum-particle State Variable (QSV) in the respective software implementations.
[0013] In yet another aspect, the present disclosure provides faster, better, and efficient solutions to real world problems of fair-selection and optimum resource management/allocation in a distributed computing environment and also in an edge computing environment.
[0014] In another aspect, the present disclosure uses a distributed QS for a distributed execution of a smart contract on Quantum Entangled Blockchain System (QEBS).

SUMMMARY OF THE INVENTION
[0015] Embodiments of a blockchain platform are disclosed. In an embodiment, the blockchain platform includes a plurality of blockchain nodes in communication with each other, wherein each of the plurality of blockchain nodes comprises a processor coupled to a memory, the memory storing one or more instructions executable by the processor. The processor is configured to execute one or more microservices to create a quantum entanglement network (QEN) comprising a plurality of entangled Quantum State Variables (QSVs) associated with respective ones of the plurality of blockchain nodes. The plurality of QSVs are in an entanglement in such manner that a collapse of a QSV in the plurality of QSVs triggers the collapse of one or more other QSVs in the plurality of QSVs. The plurality of blockchain nodes communicate data amongst each other using the QEN.
[0016] In an embodiment, to create the QEN, the processor is further configured to: generate the plurality of QSVs, each of the plurality of QSVs corresponding to a block chain node and establish the entanglement of the plurality of QSVs.
[0017] In an embodiment, the processor is further configured to: execute a first smart contract microservice for selection of a blockchain node from the plurality of blockchain nodes to perform the QSV collapse and execute a second smart contract microservice for performing the QSV collapse at the selected blockchain node.
[0018] In an embodiment, the processor is further configured to: execute a third microservice for resolution of one or more conflicts between the plurality of blockchain nodes, record the execution of the second smart contract microservice and the QSV collapse of the plurality of QSVs in a blockchain ledger, and update in the blockchain ledge, a state of the plurality of QSVs whenever there is a change in the state of any of the plurality of QSVs.
[0019] In an embodiment, the execution of the second smart contract microservice triggers a measurement/observation of a state of the QSV in such a manner that the QSV collapses to a first state out of a plurality of states, wherein the first state lies in a predetermined range. In an embodiment, the QSV collapse is triggered based at least in part on a random number generated by the processor.
[0020] Embodiments of a method for communication in a blockchain platform are disclosed. In an embodiment, the method includes, in a blockchain node in the blockchain platform comprising a plurality of blockchain nodes in communication with each other, executing one or more microservices to: create, by a processor, a quantum entanglement network (QEN) comprising a plurality of entangled Quantum State Variables (QSVs) associated with respective ones of the plurality of blockchain nodes, wherein the plurality of QSVs are in an entanglement in such manner that a collapse of a QSV in the plurality of QSVs triggers the collapse of one or more other QSVs in the plurality of QSVs, and enable, by the processor, communication of data amongst the plurality of blockchain nodes using the QEN.
[0021] In an embodiment, the method further includes, to create the QEN: generating, by the processor the plurality of QSVs, each of the plurality of QSVs corresponding to a block chain node and establishing, by the processor, the entanglement of the plurality of QSVs.
[0022] In an embodiment, the method further includes: executing, by the processor, a first smart contract microservice for selection of a blockchain node from the plurality of blockchain nodes to perform the QSV collapse; and executing, by the processor, a second smart contract microservice for performing the QSV collapse at the selected blockchain node.
[0023] In an embodiment, the method further includes: executing, by the processor, a third microservice for resolution of one or more conflicts between the plurality of blockchain nodes; recording, by the processor, the execution of the second smart contract microservice and the QSV collapse of the plurality of QSVs in a blockchain ledger; and updating, by the processor, in the blockchain ledge, a state of the plurality of QSVs whenever there is a change in the state of any of the plurality of QSVs.
[0024] In an embodiment, the method further includes: triggering, by the processor, based at least in part on the execution of the second smart contract microservice, a measurement/observation of a state of the QSV in such a manner that the QSV collapses to a first state out of a plurality of states, wherein the first state lies in a predetermined range. In an embodiment, the method further includes triggering, by the processor, the QSV collapse based at least in part on a random number generated by the processor.

BRIEF DESCRIPTION OF DRAWINGS
[0025] The accompanying drawings are included to provide a further understanding of the present disclosure, and are incorporated in and constitute a part of this specification. The drawings illustrate exemplary embodiments of the present disclosure and, together with the description, serve to explain the principles of the present disclosure. The diagrams are for illustration only, which thus is not a limitation of the present disclosure.
[0026] In the figures, similar components and/or features may have the same reference label. Further, various components of the same type may be distinguished by following the reference label with a second label that distinguishes among the similar components. If only the first reference label is used in the specification, the description is applicable to any one of the similar components having the same first reference label irrespective of the second reference label.
[0027] FIG. 1 illustrates a block diagram representing a Quantum Entanglement Network (QEN) across blockchain nodes, in accordance with an embodiment of the present disclosure;
[0028] FIG. 2 illustrates a block diagram representing QEN realization in 5G/6G networks, in accordance with an embodiment of the present disclosure;
[0029] FIG. 3 illustrates exemplary embodiment of a block diagram representing a process involved in an event/signal flow for QSV collapse in a microservices-based blockchain platform, in accordance with an embodiment of the present disclosure;
[0030] FIG. 4 illustrates exemplary embodiment of a block diagram representing 5G/6G network access node selection amongst multiple gNodeBs/DUs/APs, in accordance with an embodiment of the present disclosure;
[0031] FIG. 5 illustrates exemplary embodiment of a block diagram representing 5G/6G network access coordination amongst multiple UEs, in accordance with an embodiment of the present disclosure; and
[0032] FIG. 6 illustrates exemplary embodiment of a block diagram representing a leader selection in blockchain networks, in accordance with an embodiment of the present disclosure.

DETAILED DESCRIPTION
[0033] In the following description, for the purposes of explanation, various specific details are set forth in order to provide a thorough understanding of embodiments of the present disclosure. It will be apparent, however, that embodiments of the present disclosure may be practiced without these specific details. Several features described hereafter can each be used independently of one another or with any combination of other features. An individual feature may not address all of the problems discussed above or might address only some of the problems discussed above. Some of the problems discussed above might not be fully addressed by any of the features described herein.
[0034] The ensuing description provides exemplary embodiments only, and is not intended to limit the scope, applicability, or configuration of the disclosure. Rather, the ensuing description of the exemplary embodiments will provide those skilled in the art with an enabling description for implementing an exemplary embodiment. It should be understood that various changes may be made in the function and arrangement of elements without departing from the spirit and scope of the invention as set forth.
[0035] Specific details are given in the following description to provide a thorough understanding of the embodiments. However, it will be understood by one of ordinary skill in the art that the embodiments may be practiced without these specific details. For example, circuits, systems, networks, processes, and other components may be shown as components in block diagram form in order not to obscure the embodiments in unnecessary detail. In other instances, well-known circuits, processes, algorithms, structures, and techniques may be shown without unnecessary detail in order to avoid obscuring the embodiments.
[0036] Also, it is noted that individual embodiments may be described as a process which is depicted as a flowchart, a flow diagram, a data flow diagram, a structure diagram, or a block diagram. Although a flowchart may describe the operations as a sequential process, many of the operations can be performed in parallel or concurrently. In addition, the order of the operations may be re-arranged. A process is terminated when its operations are completed but could have additional steps not included in a figure. A process may correspond to a method, a function, a procedure, a subroutine, a subprogram, etc. When a process corresponds to a function, its termination can correspond to a return of the function to the calling function or the main function.
[0037] The word “exemplary” and/or “demonstrative” is used herein to mean serving as an example, instance, or illustration. For the avoidance of doubt, the subject matter disclosed herein is not limited by such examples. In addition, any aspect or design described herein as “exemplary” and/or “demonstrative” is not necessarily to be construed as preferred or advantageous over other aspects or designs, nor is it meant to preclude equivalent exemplary structures and techniques known to those of ordinary skill in the art. Furthermore, to the extent that the terms “includes,” “has,” “contains,” and other similar words are used in either the detailed description or the claims, such terms are intended to be inclusive—in a manner similar to the term “comprising” as an open transition word—without precluding any additional or other elements.
[0038] Reference throughout this specification to “one embodiment” or “an embodiment” or “an instance” or “one instance” means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the present invention. Thus, the appearances of the phrases “in one embodiment” or “in an embodiment” in various places throughout this specification are not necessarily all referring to the same embodiment. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.
[0039] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. As used herein, the singular forms “a”, “an”, and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof. As used herein, the term “and/or” includes any and all combinations of one or more of the associated listed items.
[0040] The present disclosure relates to the field of blockchain platforms. More particularly, the present disclosure relates to system for quantum entanglement in microservices-based realizations of blockchain platforms. Aspects of disclosure also relate to emerging communication networks and emulation of quantum entanglement to realize benefits thereof.
[0041] Multiple entangled photons can be used to create an entangled state across photons. In addition, a hybrid combination of direct or inverse correlated states could be represented for multiple entangled photons in general if desired. Such entangled photons can be emulated in emerging communication networks across a plurality of nodes to represent data associated with each of the plurality of nodes. Using a plurality of micro-services executing at the plurality of nodes, the proposed systems and methods provides for a satisfactory emulation to realize “virtual quantum entanglement” in communication networks. The proposed emulation has numerous benefits and applications. For example, such emulation can support for fast “spooky action-at-a-distance” in emerging communication networks supporting fast synchronized state updates across nodes, and quantum-random-fairness in selection in emerging blockchain systems. The disclosed embodiments of system and method for emulating the quantum entanglement phenomenon achieves faster speeds (near real time) of communication of quantum state collapse events by using Low latency URLLC or Sidelink-based communications thereby making the application of such a Quantum Entangled Network (QEN) possible for different use cases in the 5G and 6G networks.
[0042] Particularly, the disclosed embodiments can be applied in fair network slice subnet selection when multiple slice subnets are available for selection, or for fair network slice selection when multiple network slices are available for selection. In yet another scenario, a certain required product in a supply-chain may have multiple potential suppliers. In such scenarios, the proposed approach can help in a fair selection of a potential supplier. Similarly, a fair selection of a shipper or an insurance company or a bank, can also be performed utilizing the proposed virtual Quantum Entangled Blockchain System (vQEBS). In yet another scenario of a bidding system on a blockchain, a vQEBS system can be utilized for fair selection of a winner, when there are multiple candidates for selection. In a still further scenario of a hiring system at an organization, a vQEBS system can be utilized for fair selection of a candidate when there are multiple equally suitable candidates for selection.
[0043] FIG. 1 illustrates a block diagram representing a Quantum Entanglement Network (QEN) realized in a blockchain platform (also referred to hereinafter as “blockchain network” or “Quantum Entangled Blockchain System” or “QEBS”), in accordance with an embodiment of the present disclosure. As used herein, the term ‘quantum entanglement’ is defined as a phenomenon in physics where two particles (photons or electrons) can become entangled as they interact with each other. Subsequently, even as these entangled photons or electrons are separated from each other, they remain entangled until a measurement is made on one of the particles. Each photon or electron can be in a superposition of states until it is observed, and such an observation leads to a wave function collapse to one of the possible states.
[0044] Furthermore, as described earlier, when the quantum entangled state of the two directly entangled particles is observed, then state of one of the particle collapses to a first state out of a plurality of states (for example), and the state of the other particle also collapses to the same identical state (the first state) respectively. Alternatively, if the quantum entangled state of two inversely entangled particles is observed, then the state of one of the particles collapses to a second state out of the plurality of states (for example), and the state of the other particle collapses to the opposite state (a third state, for example) respectively.
[0045] The disclosed embodiments of systems and methods emulates this correlation of directly or inversely quantum entangled particles and their respective collapsed states. Accordingly, the Quantum Entanglement Network (QEN) architecture in FIG. 1 emulates in the blockchain platform 100 such that the QEN 110 includes a plurality of directly or inversely entangled quantum particles. In an embodiment, each of the plurality of quantum entangled particles can be emulated in each node of the blockchain platform or the communication network. In an exemplary embodiment, the QEN 110 refers to a network of quantum entangled particles in which a quantum particle is represented by an equivalent Quantum-particle State Variable (QSV) in the blockchain platform (and its software implementation).
[0046] Therefore, in the QEN 110, if an observation/measurement is performed on the QSV at a node, then the state of the QSV collapses (equivalent to collapse of quantum entangled particle) to one of the available states of the QSV, then correspondingly, the state of the entangled QSVs on the other nodes collapses as well based on the nature of the entanglement between the nodes. For example, as shown in FIG. 1, a first node (blockchain node 102), a second node (blockchain node 104), a third node (blockchain node 106), and an Nth node (blockchain node 108) are all communicatively coupled to the QEN 110 and emulate the proposed concept of QSV. In an exemplary embodiment, the realization of QEN 110 in the blockchain platform 100 is achieved by a plurality of microservices that can be executed in each of the plurality of blockchain nodes. In an embodiment, specific microservices may be executed at designated nodes for realizing a specific function or role at the node based on the particular application or use case scenario.
[0047] Embodiments of a blockchain platform are disclosed. In an embodiment, the blockchain platform 100 includes a plurality of blockchain nodes (e.g., the blockchain node 102, the blockchain node 104) in communication with each other. Each of the plurality of blockchain nodes includes a processor coupled to a memory, the memory storing one or more instructions executable by the processor. The processor is configured to execute one or more microservices to create the QEN 110. As described above, the QEN 110 includes a plurality of entangled Quantum State Variables (QSVs) associated with respective ones of the plurality of blockchain nodes. The plurality of QSVs are in an entanglement (e.g., direct, inverse) in such manner that a collapse of a QSV in the plurality of QSVs triggers the collapse of one or more other QSVs in the plurality of QSVs. The plurality of blockchain nodes communicate data amongst each other using the QEN 110.
[0048] In an embodiment, to create the QEN 110, the processor is further configured to generate the plurality of QSVs as described later in the description. Each of the plurality of QSVs corresponds to a blockchain node. The processor is further configured to establish the entanglement of the generated plurality of QSVs. In an embodiment, the processor is further configured to: execute a first smart contract microservice for selection of a blockchain node from the plurality of blockchain nodes to perform the QSV collapse and execute a second smart contract microservice for performing the QSV collapse (described later) at the selected blockchain node.
[0049] In an embodiment, the processor is further configured to: execute a third microservice for resolution of one or more conflicts between the plurality of blockchain nodes (as described later). The processor is further configured to record the execution of the second smart contract microservice and the QSV collapse of the plurality of QSVs in a blockchain ledger. The processor is further configured to update in the blockchain ledge, a state of the plurality of QSVs whenever there is a change in the state of any of the plurality of QSVs.
[0050] In an embodiment, the execution of the second smart contract microservice triggers a measurement/observation of a state of the QSV in such a manner that the QSV collapses to a first state (for example) out of a plurality of states. In an embodiment, the first state lies in a predetermined range. In an embodiment, the QSV collapse is triggered based at least in part on a random number generated by the processor (as described later).
[0051] To implement the QEN, a composite data structure for a QSV is defined that will require a representation of all possible states and corresponding probabilities/amplitudes. In an exemplary embodiment, a QSV that represents two states |0> and |1> with corresponding equiprobable amplitudes of may be represented as:
{
“QSV”:{
“ID”: 12345,
“creation timestamp”: xyz,
“node”: 3,
“numstates”: 2,
“states”: {
“state0”: “|0>|”,
“amplitude0”: 0.7071,
“state1”: “|1>”,
“amplitude1”: 0.7071
}
}
}

[0052] In one embodiment, the quantum entangled state of two directly entangled particles may be represented as:
?1 |00> + ?2 |11>, where + = 1.
This may imply that if the state of any one of the two entangled particles is observed, then state of that particle collapses to either |0> or |1>, and the state of the other particle also collapses to the same identical state |0> or |1> respectively.
[0053] In another embodiment, if the two particles become inversely entangled, then their quantum entangled state can be represented as:
?1 |01> + ?2 |10>, where + = 1.
This implies that if the state of any one of the particles is observed, then the state of that particle collapses to either |0> or |1>, and the state of the other particle collapses to the opposite state |1> or |0> respectively. This is possible for example, when particles of opposite spins are created, so that their entanglement has an opposite correlation.
[0054] In yet another embodiment, multiple entangled particles (more than two) can be used to create an entangled state across these particles. For example, a quantum entangled state of four directly entangled particles may be represented as:
?1 |0000> + ?2 |1111> where, + = 1,
such that after observation all the four particles collapse to either the |0> state or the |1> state. In yet another embodiment, a hybrid combination of direct or inverse correlated (or entangled) states could be represented for multiple entangled particles if desired.
[0055] The “collapsed state” of the blockchain nodes in communication with the QEN can correspond to one or more parameters or may indicate a status of the nodes in the context of a blockchain platform or a communication network.
[0056] Further, turning to FIG. 2, in an embodiment, QEN realization can be achieved in a blockchain platform or in a communication network via a publish-subscribe approach. For example, shown in FIG. 2, gNodeB 202 may function as a publisher and User Equipment (e.g., UE1, UE2, UE3) may function as a subscriber. It may be appreciated that FIG. 2 may be an example implementation of publish-subscribe process for realizing the blockchain platform 100 of FIG. 1.
[0057] However, the publish-subscribe messaging pattern may result in delays in exchanging information amongst the participating nodes (e.g., gNodeB and UE1, UE2, UE3). In an exemplary embodiment, to reduce such delays, dedicated TCP-based network connections between nodes may be utilized to exchange or communicate information associated with one or more of publish messages, subscribe messages, QSV collapse events, and the like.
[0058] In an embodiment, the QSV collapse events may correspond to one or more of: a change in status (active/inactive) of the one or more nodes, a change in value or entries in ledger stored in the one or more nodes, a failure event or breakdown of a link between two or more nodes, and the like. In an embodiment, a predetermined and customizable threshold can be provided for each of the one or more nodes. Each of the one or more nodes may be configured to generate, either periodically or infrequently, a random number that can be compared with the predetermined threshold. Depending upon whether the random number exceeds the threshold or not, the one or more nodes can be configured to trigger or consider a QSV collapse event and to communicate the information of such a QSV collapse (event) to other networks in the QEN. In an embodiment, a mapping or association of QSV collapse events to one or more aspects of the nodes can be realized so that the QSV collapse events generate meaningful information for the overall QEN 110. Furthermore, a “node” as referred to herein may correspond to gNodeBs (gNBs), eNodeBs, 6G access nodes, Wi-Fi Access Points (APs), Central Units (CUs), Radio Units (RUs), Distributed Units (DUs), UEs, blockchain nodes, edge computing devices, centralized computing devices, server, Open Radio Access Network (O-RAN), or any entity in the emerging communication networks and/or blockchain platforms 100.
[0059] A QSV collapse in the blockchain platform 100 may be desired to occur almost instantaneously or at very fast speeds to closely mimic the behavior of true physical quantum entangled photons or electrons (for which state collapse is instantaneous). To this end, to minimize delays, the blockchain platform 100 (also referred to herein as Quantum Entangled Blockchain Systems or QEBSs) can be realized at the edge of a communication network in accordance with an embodiment. Accordingly, edge communications can be utilized to result in very low latency QEN realizations.
[0060] In one embodiment, the communication network may be any emerging network such as, but not limited to 5G network, 6G network, or the like. To minimize delays in communication of QSV collapse information, low-latency URLLC paths can be utilized to exchange or communicate QSV collapse information in 5G or 6G networks. For example, 5G URLLC technology enables a reduced TTI (Transmission Time Interval) of 0.125ms relative to a TTI of 1ms for LTE to reduce round-trip latency for communications with wider sub-carrier spacing. As shown in FIG. 2, a virtual Quantum Entangled Blockchain System (vQEBS) node (e.g., UE1, UE2, UE3) can communicate with a 5G gNodeB 202 with lower RTTs (round trip times) using 5G URLLC, and report its QSV state update. In addition, the 5G gNodeB 202 can allocate Sidelink resources for vQEBS nodes to directly communicate with each other to realize the QEN communications. The 5G gNodeB 202 may be communicatively coupled to UE1 204, UE2 206 and UE3 208. The sidelinks between the nodes may be allocated via the 5G gNodeB 202 as shown in FIG. 2.
[0061] In an embodiment, the nodes (e.g., blockchain node 102, UE1 204) connected to the blockchain platform execute the same smart contract code and consensus. The system 100 applies a non-deterministic approach, so that a different outcome (i.e., QSV collapse information) can be obtained on each node based on a randomized processing. In one embodiment, each node may be configured to locally generate a random number in a certain range, for example, in the closed interval [0,1]. The node can be configured to determine a QSV collapse event that may trigger the communication of QSV collapse update or information to other nodes. For example, if the node determines that the generated random number exceeds a certain threshold value, or falls below a certain threshold value, then the node may be configured to treat such a determination as a QSV collapse at the node, leading to a QSV collapse across the other nodes connected via the QEN.
[0062] In one embodiment, if the threshold needs to be exceeded to determine a QSV collapse, then, for example, for random number generation ?i in a [0,1] real interval at node i, a threshold t needs to be exceeded where 0 = t = 1, for the QSV collapse determination. Therefore, if ?i = t , then this can be implemented as the trigger for a measurement/observation event leading to a QSV collapse at the node. In an embodiment, t can be chosen to be a high value such as 0.95 or 0.98 for example, if it is desirable to reduce the likelihood of success for a QSV collapse at a node.
[0063] Moreover, if a QSV collapse event is determined, then a different random number “µi” can be generated in the interval [0,1] to determine the collapsed state at a given node. If the QSV can take one of ‘m’ states |s1>, |s2>, …., |sm> then the collapsed state can be determined to be |sk> , where is the probability associated with state |si>. Further, once a QSV collapse event occurs at a given node in the blockchain network, this event is communicated via the QEN to other nodes in the blockchain network. The values for the corresponding entangled QSV at other nodes collapse to a value as determined by the nature of the entanglement across the QSVs. In one embodiment, the QSVs are all directly entangled. Furthermore, in an embodiment, a pseudo-random number generator can be used for random number generation at each of the nodes. To improve fairness in the network architecture implementing the blockchain platform 100, previously measured qubit states from a quantum computer (not shown) could also be utilized to seed a random number generator in the blockchain platform 100.
[0064] In an embodiment, the disclosed approach enables a node selection using quantum entanglement in the blockchain network/platform. For example, if there are N nodes in a blockchain network where N , then k pairs of directly quantum entangled particles (where each particle can take a |0> state or a |1> state) can be utilized for the N nodes to select a node across the N nodes.
[0065] For example, if there are N = 4 nodes, then = 2 pairs of directly entangled quantum particles will be required, so that the 2 pairs take on a collapsed state given by the values (|00>, |00>) or (|00>, |11>) or (|11>, |00>) or (|11>, |11>). Here, the first element in the 2-tuple is the collapsed state for the first entangled pair, and the second element in the 2-tuple is the collapsed state for the second entangled pair. This can be mapped to a one-hot encoded value for the 4 nodes to select one of the 4 nodes such as the value:
(|00>, |00>) selects 0001 (Node 0),
(|00>, |11>) selects 0010 (Node 1),
(|11>, |00>) selects 0100 (Node 2), and
(|11>, |11>) selects 1000 (Node 3).
[0066] In one exemplary embodiment, in the absence of the availability of true quantum entangled particles, 2 pairs of QSVs interacting across a QEN can be used to select a node amongst the 4 nodes in the blockchain network in the above example.
[0067] Furthermore, there may be an example scenario in the emulation of QEBS that results in the QSVs on two or more different nodes being simultaneously triggered for measurement or collapse at the same time or around the same time. In such a scenario, both QSV collapse requests will be submitted to the QEN. However, this scenario may require conflict resolution across the two or more QSVs sending such requests. In an embodiment, an “orderer” (which may be a microservice) can help in resolving such a conflict. One or more nodes may be configured as an ‘orderer’, which can be implemented as a distributed microservice (distributed across the one or more nodes). In an embodiment, a designated node (e.g., a leader node in a leader-follower scenario) may be configured as an “orderer”. The disclosed embodiments of the “orderer” may or may not be a part of the communication network. One or more of gNodeb/CU’s/local or remote servers/any subset of one or more nodes in the communication network can be designated as an “orderer”.
[0068] In an embodiment, the blockchain platform 100 can utilize a common “orderer” across the blockchain nodes in the blockchain network, so that the arrival timestamp associated with each QSV request can be used to select the winning blockchain node when such a conflict arises. Subsequently, once the winning node is determined by the orderer, then the corresponding QSV collapse can be completed at the other blockchain nodes in the blockchain network.
[0069] In an alternative embodiment, the blockchain network 100 implements or designates a master/leader node (from amongst the plurality of nodes) that may be configured to (decide and) initiate a QSV collapse across nodes. The implementation of the master/leader node eliminates the requirement of any conflict resolution across the plurality of nodes. In addition, a probabilistic determination of which node triggers the QSV collapse (using the threshold “t” described above) may not be required in this approach. Consequently, based on an application executing on the blockchain platform 100, when the need arises, the (designated) master node may trigger a QSV collapse on its local QSV, and subsequently may trigger the corresponding QSV collapse in the remaining nodes via the QEN 110.
[0070] In an embodiment, in order to achieve the realization of QEN 110, the blockchain platform 100 may require different capabilities for vQEBS support in virtualized 5G or 6G infrastructure. Accordingly, embodiments of a method for providing vQEBS support in virtualized 5G or 6G infrastructure are disclosed. In an embodiment, the method includes creating QSVs and entanglement of the created QSVs. In one embodiment, the nature of entanglement may be one of direct or inverse for a two-particle entanglement, and direct or hybrid entanglement for a multi-particle entanglement. In an embodiment, the creation of QSVs and the corresponding entanglement may be performed by a QSV creation and entanglement microservice or a blockchain application executing in a designated node.
[0071] The method further includes selecting a node for QSV collapse. In an embodiment, a smart contract microservice (e.g., a first smart contract microservice) can be configured/executed in one or more of the nodes for selecting a node for QSV collapse. In one embodiment, the smart contract may determine if the node on which the microservice is executing will perform a QSV collapse measurement or not. In one embodiment, the same or another smart contract microservice (e.g., a second smart contract microservice) may execute to collapse the QSV after the node selection, which may further determine the collapsed state of the QSV after the QSV collapse.
[0072] The method may further include resolving any conflict between nodes. In an embodiment, a conflict resolution mechanism (e.g., a third microservice) may be implemented to enable the resolution of any conflict between nodes. The conflict resolution approach may involve generating/determining topics (e.g., Kafka topics) for “publish and subscribe” of QSV collapse events. The method further includes realizing QEN implementation. For example, the QEN implementation realization is achieved in software through Kafka, or through dedicated TCP network paths, and further optimized 5G gNodeB URLLC/Sidelink communications for delay minimization.
[0073] The method further includes recording of QSV collapse processing in a blockchain ledger, and updating the corresponding QSV state in the blockchain platform 100. In an embodiment, final recording of QSV collapse processing in a blockchain ledger, and corresponding QSV state update in the blockchain platform is performed by a designated node or any of the one or more nodes.
[0074] FIG. 3 illustrates an exemplary embodiment of a block diagram representing a signal flow between various participating entities for QSV Collapse in the blockchain platform 100, in accordance with an embodiment of the present disclosure. The entities involved in the system 300 include a blockchain application 302, node selection smart contract microservice 304, QSV collapse smart contract microservice 306, conflict resolution system or the orderer 308, QEN system 310, a blockchain transactions recording microservice 312, and the QSV state database update 314. One or more of the above entities may reside locally in a single node or may reside in a distributed fashion in a plurality of nodes. In an embodiment, certain entities may reside in a designated node (e.g., master or leader node) selected based on a microservice executing in one or all of the entities. The entities described herein may correspond to a software engine or a microservice or a hardware executing a set of instructions or the microservice itself.
[0075] In operation, QSV processing request is communicated from the blockchain application 302 to the QSV collapse smart contract microservice 306 in step 316. Further, QSV Processing Request may be communicated from the blockchain application 302 to the node selection smart contract microservice 304 in step 318. Consequently, a node selection trigger is communicated from the node selection smart contract microservice 304 to the QSV collapse smart contract microservice 306 in step 320. The QSV collapse outcome is generated based on communication between the QSV collapse smart contract microservice 306 and the orderer 308 in step 322. QSV collapse submission to QEN may be generated by the orderer 308 and communicated to the QEN system 310 in step 324. Further, a conflict resolution (if required) is achieved based on communication between the QSV collapse smart contract microservice 306 and the orderer 308 which may be on of a “success” or a “failure” in step 326.
[0076] Consequently, the conflict resolution is communicated between the blockchain application 302 and the QSV collapse smart contract microservice 306 in step 328. The QEN communication system update is communicated between the orderer 308 and the QEN system 310 in step 330. Further, the QEN communication system update is communicated between the orderer 308 and the QSV collapse smart contract microservice 306 in step 332. Furthermore, a blockchain ledger update may be performed based on communication between the QSV collapse smart contract microservice 306 and the blockchain transactions recording microservice 312 in step 334. Subsequently, a blockchain QSV state update may be generated and communicated between the QSV collapse smart contract microservice 306 and the QSV state database update 314 in step 336. Consequently, a final status update for the QSV processing request may be generated and communicated between the blockchain application 302 and the QSV collapse smart contract microservice 306 in step 338.
[0077] FIG. 4 illustrates exemplary embodiment of a block diagram 400 representing 5G/6G network access node selection, in accordance with an embodiment of the present disclosure. It may be noted that the ongoing description for FIG. 4 is an example implementation of the node selection smart contract microservice 304 executing in one or more nodes shown in FIG. 4.
[0078] A plurality of gNodeBs 402-1, 402-2, and 402-3 (collectively referred to as gNodeBs 402 hereinafter) is operatively coupled to UE 404. More specifically, consider a scenario in which a single mobile device (or the UE 404) may be connected to N nearby gNodeBs 402 (or Distributed Units (DUs) or APs in a 5G/6G network) and all gNodeBs 402 (or DUs or APs) may be good candidates to serve the UE 404. In an embodiment, a vQEBS-based blockchain network 100 may determine which of the N nodes will serve the UE 404 by collapsing QSVs across the N nodes. In one embodiment, each node in the QEN may represent the gNodeB 402. In an embodiment, the blockchain network 100 may be realized across the gNodeBs 402 in a given geographical region/area and can be managed at a 5G/6G network edge small data center. In an embodiment, decisions taken for network access node selection as can be recorded in a blockchain ledger that may be centrally located in the 5G/6G network edge small data center or may be stored in a distributed fashion in the plurality of nodes in the blockchain network 100.
[0079] FIG. 5 shows a block diagram 500 depicting a coordination of the network access post network access node selection, in accordance with an embodiment. The participating entities are UE1 502, UE2 504, UE3 506 and gNodeB 508, wherein all the entities are communicatively coupled to each other. The UEs may be one of any mobile devices or an IoT device which are connected to a single gNodeB in a 5G/6G network.
[0080] In an embodiment, a vQEBS based blockchain network across the UEs may be used to determine which of the devices or UEs will communicate with a given gNodeB by collapsing QSVs across the N nodes (i.e., UEs) in the vQEBS network. This implementation can mitigate the overload of the control channel for access requests in the communication network across the devices/UEs. In an embodiment, the outcome of such processing can be recorded at a blockchain ledger at a local 5G or 6G small data center. In an embodiment, if multiple low latency decisions are taken over wireless links, then these decisions can be aggregated and recorded at a blockchain ledger at the network edge.
[0081] FIG. 6 shows a blockchain network 600 for selection of a leader in accordance with an embodiment of the present disclosure. Furthermore, one or more ledgers may be optimally selected from a plurality of ledgers in the blockchain network 600. It may be desirable in a blockchain network to perform a fair leader selection. To this end, the blockchain network 600 determines which of the N nodes in the vQEBS-based blockchain network is the new “leader” by collapsing QSVs across the N nodes in an exemplary embodiment. In an embodiment, the leader selection can be performed periodically or randomly (infrequently) across the nodes. For example, N nodes may include blockchain node1 602, blockchain node2 604, blockchain node3 606 and blockchain node4 608 which may be communicatively coupled to each other.
[0082] Various embodiments of the present disclosure enable a communication network to realize a virtual Quantum Entanglement Blockchain System (vQEBS). Quantum-particle state variables (QSVs) are realized in a blockchain platform using the disclosed approaches. Further, a Quantum Entanglement Network (QEN) is realized across nodes to enable a QSV collapse across nodes in a blockchain platform 100. In an embodiment, the blockchain network 100 may utilize recorded qubits from a quantum computer for fair random number generation in the nodes for triggering QSV collapse events. In an embodiment, a non-deterministic microservice may be implemented for blockchain node selection for QSV collapse. In an embodiment, microservice for QSV collapse with randomized QSV state selection can also be achieved.
[0083] Furthermore, the proposed approach enables applications to 5G and 6G network access node selection, 5G and 6G network access coordination, 5G and 6G network slice subnet and slice selection, winner selection for bidding applications, fair selection in supply chains, fair candidate hiring for HR, leader selection in blockchain networks. The disclosed system also enables fast realization of quantum entanglement networks (QENs) in 5G and 6G edge systems using URLLC or the Sidelink communications across edge vQEBS nodes.
[0084] For instance, the disclosed embodiments has application in fair network slice subnet selection when multiple slice subnets are available for selection, or for fair network slice selection when multiple network slices are available for selection.
[0085] In another example, a certain required good or product in a supply-chain may have multiple potential suppliers, in such scenarios, the proposed approach can help in a fair selection of a potential supplier. Similarly, a fair selection of a shipper or an insurance company or a bank, can also be performed utilizing a vQEBS system. In a bidding system on a blockchain, a vQEBS system can be utilized for fair selection of a winner, when there are multiple candidates for selection. Furthermore, in a hiring system at an organization, a vQEBS system can be utilized for fair selection of a candidate when there are multiple equally suitable candidates for selection. In addition, Low latency URLLC or Sidelink-based communications are implemented for realizations of quantum entanglement networks and can be useful for different use cases at the 5G and 6G network edge.
[0086] Embodiments of a method for communication in a blockchain platform are disclosed. In an embodiment, the method includes, in a blockchain node in the blockchain platform comprising a plurality of blockchain nodes in communication with each other, executing one or more microservices to: create, by a processor, a quantum entanglement network (QEN) comprising a plurality of entangled Quantum State Variables (QSVs) associated with respective ones of the plurality of blockchain nodes, wherein the plurality of QSVs are in an entanglement in such manner that a collapse of a QSV in the plurality of QSVs triggers the collapse of one or more other QSVs in the plurality of QSVs, and enable, by the processor, communication of data amongst the plurality of blockchain nodes using the QEN.
[0087] In an embodiment, the method further includes, to create the QEN: generating, by the processor the plurality of QSVs, each of the plurality of QSVs corresponding to a block chain node and establishing, by the processor, the entanglement of the plurality of QSVs.
[0088] In an embodiment, the method further includes: executing, by the processor, a first smart contract microservice for selection of a blockchain node from the plurality of blockchain nodes to perform the QSV collapse; and executing, by the processor, a second smart contract microservice for performing the QSV collapse at the selected blockchain node.
[0089] In an embodiment, the method further includes: executing, by the processor, a third microservice for resolution of one or more conflicts between the plurality of blockchain nodes; recording, by the processor, the execution of the second smart contract microservice and the QSV collapse of the plurality of QSVs in a blockchain ledger; and updating, by the processor, in the blockchain ledge, a state of the plurality of QSVs whenever there is a change in the state of any of the plurality of QSVs.
[0090] In an embodiment, the method further includes: triggering, by the processor, based at least in part on the execution of the second smart contract microservice, a measurement/observation of a state of the QSV in such a manner that the QSV collapses to a first state out of a plurality of states, wherein the first state lies in a predetermined range. In an embodiment, the method further includes triggering, by the processor, the QSV collapse based at least in part on a random number generated by the processor.
[0091] Moreover, in interpreting the specification, all terms should be interpreted in the broadest possible manner consistent with the context. In particular, the terms “comprises” and “comprising” should be interpreted as referring to elements, components, or steps in a non-exclusive manner, indicating that the referenced elements, components, or steps may be present, or utilized, or combined with other elements, components, or steps that are not expressly referenced. Where the specification claims refer to at least one of something selected from the group consisting of A, B, C ….and N, the text should be interpreted as requiring only one element from the group, not A plus N, or B plus N, etc.
[0092] While the foregoing describes various embodiments of the invention, other and further embodiments of the invention may be devised without departing from the basic scope thereof. The scope of the invention is determined by the claims that follow. The invention is not limited to the described embodiments, versions or examples, which are included to enable a person having ordinary skill in the art to make and use the invention when combined with information and knowledge available to the person having ordinary skill in the art.
,CLAIMS:1. A blockchain platform comprising:
a plurality of blockchain nodes in communication with each other, wherein each of the plurality of blockchain nodes comprises a processor coupled to a memory, the memory storing one or more instructions executable by the processor, wherein the processor is configured to execute one or more microservices to:
create a quantum entanglement network (QEN) comprising a plurality of entangled Quantum State Variables (QSVs) associated with respective ones of the plurality of blockchain nodes, wherein the plurality of QSVs are in an entanglement in such manner that a collapse of a QSV in the plurality of QSVs triggers the collapse of one or more other QSVs in the plurality of QSVs, and wherein the plurality of blockchain nodes communicate data amongst each other using the QEN.
2. The blockchain platform of claim 1, wherein, to create the QEN, the processor is further configured to:
generate the plurality of QSVs, each of the plurality of QSVs corresponding to a block chain node; and
establish the entanglement of the plurality of QSVs.
3. The blockchain platform of claim 1, wherein the processor is further configured to:
execute a first smart contract microservice for selection of a blockchain node from the plurality of blockchain nodes to perform the QSV collapse; and
execute a second smart contract microservice for performing the QSV collapse at the selected blockchain node.
4. The blockchain platform of claim 3, wherein the processor is further configured to:
execute a third microservice for resolution of one or more conflicts between the plurality of blockchain nodes;
record the execution of the second smart contract microservice and the QSV collapse of the plurality of QSVs in a blockchain ledger; and
update in the blockchain ledge, a state of the plurality of QSVs whenever there is a change in the state of any of the plurality of QSVs.
5. The blockchain platform of claim 3, wherein the execution of the second smart contract microservice triggers a measurement/observation of a state of the QSV in such a manner that the QSV collapses to a first state out of a plurality of states, wherein the first state lies in a predetermined range.
6. The blockchain platform of claim 1, wherein the QSV collapse is triggered based at least in part on a random number generated by the processor.
7. A method for communication in a blockchain platform, the method comprising:
in a blockchain node in the blockchain platform comprising a plurality of blockchain nodes in communication with each other, executing one or more microservices to;
create, by a processor, a quantum entanglement network (QEN) comprising a plurality of entangled Quantum State Variables (QSVs) associated with respective ones of the plurality of blockchain nodes, wherein the plurality of QSVs are in an entanglement in such manner that a collapse of a QSV in the plurality of QSVs triggers the collapse of one or more other QSVs in the plurality of QSVs, and
enable, by the processor, communication of data amongst the plurality of blockchain nodes using the QEN.
8. The method of claim 7, further comprising, to create the QEN:
generating, by the processor the plurality of QSVs, each of the plurality of QSVs corresponding to a block chain node; and
establishing, by the processor, the entanglement of the plurality of QSVs.
9. The method of claim 8, further comprising:
executing, by the processor, a first smart contract microservice for selection of a blockchain node from the plurality of blockchain nodes to perform the QSV collapse; and
executing, by the processor, a second smart contract microservice for performing the QSV collapse at the selected blockchain node.
10. The method of claim 9, further comprising:
executing, by the processor, a third microservice for resolution of one or more conflicts between the plurality of blockchain nodes;
recording, by the processor, the execution of the second smart contract microservice and the QSV collapse of the plurality of QSVs in a blockchain ledger; and
updating, by the processor, in the blockchain ledge, a state of the plurality of QSVs whenever there is a change in the state of any of the plurality of QSVs.
11. The method of claim 9, further comprising:
triggering, by the processor, based at least in part on the execution of the second smart contract microservice, a measurement/observation of a state of the QSV in such a manner that the QSV collapses to a first state out of a plurality of states, wherein the first state lies in a predetermined range.
12. The method of claim 7, further comprising:
triggering, by the processor, the QSV collapse based at least in part on a random number generated by the processor.