Method, Controller, and Computer-Readable Medium of a Distributed Ledger Network for Initiating a Net Transmission Among a Plurality of Clients of the Distributed Ledger Network

This application is a continuation of U.S. patent application Ser. No. 18/325,505, filed May 30, 2023, which is a continuation-in-part of U.S. patent application Ser. No. 17/722,171, filed Apr. 15, 2022, which claims priority to U.S. Provisional Application No. 63/306,378, filed Feb. 3, 2022, the disclosures of which are hereby incorporated by reference in their entirety.

The present disclosure generally relates to computer-based platforms and/or systems for asynchronous and parallel network operations, including parallel initiation and execution of a blockchain operation in parallel with a corresponding network operation where the network operation is performed asynchronously with the blockchain operation for batch processing.

In some aspects, the present disclosure relates to a method executed by one or more computing devices of a controller of a distributed ledger network for initiating a net transmission among a plurality of clients of the distributed ledger network, the method including: receiving, by the controller, a plurality of instructions to perform a plurality of transmissions, each transmission comprising instruction parameters for movement of a first quantity of first entity-specific tokens corresponding to a first entity that is a client of the distributed ledger network to a second quantity of second entity-specific tokens corresponding to a second entity that is a client of the distributed ledger network, wherein the first entity-specific tokens are stored on a first entity-specific blockchain and the second entity-specific tokens are stored on a second entity-specific blockchain; writing, by the controller, one or more transmissions in the plurality of transmissions to one or more new blocks on a transmission blockchain of the distributed ledger network, each new block storing a subset of the plurality of transmissions; storing, by the controller, a net entity asset differential between each entity in the plurality of entities that are clients of the distributed ledger network and the distributed ledger network, each net entity asset differential being determined based at least in part on quantities of tokens transferred between a corresponding entity and the plurality of entities during the one or more transmissions; storing, by the controller, a current block height corresponding to a quantity of new blocks added to the transmission blockchain since a previous net transmission process; storing, by the controller, a duration value corresponding to a time elapsed since the previous net transmission process; determining, by the controller, a required transmission quantity indicating a quantity of transmissions necessary to complete a net transmission process between the plurality of entities that are clients of the distributed ledger network; determining, by the controller, one or more predicted required transmission quantities corresponding to one or more time intervals, each predicted required transmission quantity indicating a predicted quantity of transmissions necessary to complete a net transmission process between the plurality of entities that are clients of the distributed ledger network after a corresponding time interval; and initiating, by the controller, a net transmission process between a plurality of entities that are clients of the distributed ledger network based at least in part on detection of one or more conditions in a plurality of conditions, the plurality of conditions comprising: the duration value exceeding a threshold duration value; the current block height meeting or exceeding a threshold block height; the net entity asset differential exceeding a threshold entity asset differential; and the required transmission quantity matching or exceeding the one or more predicted required transmission quantities.

The step of initiating a net transmission process between a plurality of entities that are clients of the distributed ledger network based at least in part on detection of one or more conditions in a plurality of conditions can include initiating the net transmission process between the plurality of entities that are clients of the distributed ledger network based at least in part on a determination that at least one net entity asset differential exceeds the threshold entity asset differential.

The step of determining one or more predicted transfer quotients corresponding to one or more time intervals can include determining a plurality of predicted required transmission quantities corresponding to a plurality of time intervals.

The step of initiating a net transmission process between a plurality of entities that are clients of the distributed ledger network based at least in part on detection of one or more conditions in a plurality of conditions can include: determining whether that the plurality of predicted required transmission quantities are less than the required transmission quantity; and initiating the net transmission process between the plurality of entities that are clients of the distributed ledger network based at least in part on a determination that the plurality of predicted required transmission quantities are not less than the required transmission quantity.

The step of initiating a net transmission process between a plurality of entities that are clients of the distributed ledger network based at least in part on detection of one or more conditions in a plurality of conditions can include: determining whether that the plurality of predicted required transmission quantities are less than the required transmission quantity; initiating a delay of the net transmission process for a variable time period based at least in part on a determination that at least one predicted required transmission quantity in the plurality of predicted required transmission quantities is less than the required transmission quantity; and initiating the net transmission process between the plurality of entities that are clients of the distributed ledger network after the delay.

The method can further include the step of storing, by the controller, at least one net entity-pair asset differential between at least one pair of entities in a plurality of entities that are clients of the distributed ledger network, the at least one net entity-pair asset differential being determined based at least in part on quantities of tokens transferred between at least two or more entities in the plurality of entities during the one or more transmissions; wherein the plurality of conditions further comprise the at least one net entity-pair asset differential exceeding a threshold entity-pair asset differential.

The step of storing at least one net entity-pair asset differential between at least one pair of entities in a plurality of entities that are clients of the distributed ledger network can include storing a plurality of net entity-pair asset differentials between all pairs of entities in the plurality of entities that are clients of the distributed ledger network.

The step of initiating a net transmission process between a plurality of entities that are clients of the distributed ledger network based at least in part on detection of one or more conditions in a plurality of conditions can include initiating the net transmission process between the plurality of entities that are clients of the distributed ledger network based at least in part on a determination that at least one net entity-pair asset differential in the plurality of net entity-pair asset differentials exceeds a threshold entity-pair asset differential.

In some aspects, the present disclosure relates to a controller of a distributed ledger network for initiating a net transmission among a plurality of clients of the distributed ledger network. The controller includes one or more processors; and one or more memories operatively coupled to at least one of the one or more processors and having instructions stored thereon that, when executed by at least one of the one or more processors, cause at least one of the one or more processors to perform any of the methods described above.

In some aspects, the present disclosure relates to at least one non-transitory computer-readable medium storing computer-readable instructions for initiating a net transmission among a plurality of clients of a distributed ledger network that, when executed by one or more computing devices of a controller of the distributed ledger network, cause the controller to perform any of the methods described above.

Various detailed embodiments of the present disclosure, taken in conjunction with the accompanying figures, are disclosed herein; however, it is to be understood that the disclosed embodiments are merely illustrative. In addition, each of the examples given in connection with the various embodiments of the present disclosure is intended to be illustrative, and not restrictive.

Throughout the specification, the following terms take the meanings explicitly associated herein, unless the context clearly dictates otherwise. The phrases “in one embodiment” and “in some embodiments” as used herein do not necessarily refer to the same embodiment(s), though it may. Furthermore, the phrases “in another embodiment” and “in some other embodiments” as used herein do not necessarily refer to a different embodiment, although it may. Thus, as described below, various embodiments may be readily combined, without departing from the scope or spirit of the present disclosure.

In addition, the term “based on” is not exclusive and allows for being based on additional factors not described, unless the context clearly dictates otherwise. In addition, throughout the specification, the meaning of “a,” “an,” and “the” include plural references. The meaning of “in” includes “in” and “on.”

As used herein, the terms “and” and “or” may be used interchangeably to refer to a set of items in both the conjunctive and disjunctive in order to encompass the full description of combinations and alternatives of the items. By way of example, a set of items may be listed with the disjunctive “or”, or with the conjunction “and.” In either case, the set is to be interpreted as meaning each of the items singularly as alternatives, as well as any combination of the listed items.

illustrate systems and methods of tokenized item operations using parallel networks of a blockchain network and a computer network. The following embodiments provide technical solutions and technical improvements that overcome technical problems, drawbacks and/or deficiencies in the technical fields involving item operation efficiency over a computer network when paired with a corresponding blockchain operation with a tokenized item. As explained in more detail, below, technical solutions and technical improvements herein include aspects of improved reconciliation between each blockchain of a multitude of blockchain operations with each item operation over a parallel network of a multitude of item operations such that the item operations are performed using intelligent batching to improve the efficiency of the network operations while ensuring reconciliation with blockchain operations of corresponding tokenized items. Based on such technical features, further technical benefits become available to users and operators of these systems and methods. Moreover, various practical applications of the disclosed technology are also described, which provide further practical benefits to users and operators that are also new and useful improvements in the art.

is a block diagram of a network of platforms associated with distributed segregated data structures for network-wide net transmissions of assets to satisfy aggregates of tokenized asset transfers between each platform in accordance with one or more embodiments of the present disclosure.

In some embodiments, a distributed asset networkincludes a common platformin communication with a network of segregated data structures including segregated data structureA, segregated data structureB, segregated data structureC, segregated data structureD through segregated data structureN (hereinafter, collectively referred to as “segregated data structuresA throughN”). In some embodiments, the segregated data structuresA throughN may be nodes in the distributed asset networkassociated with the common platform.

In some embodiments, the common platformmay include hardware components such as a processor, which may include local or remote processing components. In some embodiments, the processormay include any type of data processing capacity, such as a hardware logic circuit, for example an application specific integrated circuit (ASIC) and a programmable logic, or such as a computing device, for example, a microcomputer or microcontroller that include a programmable microprocessor. In some embodiments, the processormay include data-processing capacity provided by the microprocessor. In some embodiments, the microprocessor may include memory, processing, interface resources, controllers, and counters. In some embodiments, the microprocessor may also include one or more programs stored in memory.

Similarly, the common platformmay include a datastore, such as one or more local and/or remote data storage solutions such as, e.g., local hard-drive, solid-state drive, flash drive, database or other local data storage solutions or any combination thereof, and/or remote data storage solutions such as a server, mainframe, database or cloud services, distributed database or other suitable data storage solutions or any combination thereof. In some embodiments, the datastoremay include, e.g., a suitable non-transient computer readable medium such as, e.g., random access memory (RAM), read only memory (ROM), one or more buffers and/or caches, among other memory devices or any combination thereof.

In some embodiments, the common platformmay implement computer engines for initiating a net transmission to satisfy one or more batches of tokenized asset transfer operations using a net transmission engine, executing each individual tokenized asset transfer operation using an execution engine, and administer a distributed crypto-ledgerto record and execute each individual tokenized asset transfer of each individual tokenized asset transfer operation. In some embodiments, the terms “computer engine” and “engine” identify at least one software component and/or a combination of at least one software component and at least one hardware component which are designed/programmed/configured to manage/control other software and/or hardware components (such as the libraries, software development kits (SDKs), objects, etc.).

Examples of hardware elements may include processors, microprocessors, circuits, circuit elements (e.g., transistors, resistors, capacitors, inductors, and so forth), integrated circuits, application specific integrated circuits (ASIC), programmable logic devices (PLD), digital signal processors (DSP), field programmable gate array (FPGA), logic gates, registers, semiconductor device, chips, microchips, chip sets, and so forth. In some embodiments, the one or more processors may be implemented as a Complex Instruction Set Computer (CISC) or Reduced Instruction Set Computer (RISC) processors; x86 instruction set compatible processors, multi-core, or any other microprocessor or central processing unit (CPU). In various implementations, the one or more processors may be dual-core processor(s), dual-core mobile processor(s), and so forth.

Examples of software may include software components, programs, applications, computer programs, application programs, system programs, machine programs, operating system software, middleware, firmware, software modules, routines, subroutines, functions, methods, procedures, software interfaces, application program interfaces (API), instruction sets, computing code, computer code, code segments, computer code segments, words, values, symbols, or any combination thereof. Determining whether an embodiment is implemented using hardware elements and/or software elements may vary in accordance with any number of factors, such as desired computational rate, power levels, heat tolerances, processing cycle budget, input data rates, output data rates, memory resources, data bus speeds and other design or performance constraints.

In some embodiments, entity platformA, entity platformB, entity platformC, entity platformD through entity platformN (hereinafter, collectively referred to as “entity platformsA throughN”) may include a respective segregated data structureA throughN of the distributed asset network. In some embodiments, the segregated data structuresA throughN provide a schema for storing assets on behalf of a remote platform and/or system and/or entity. Each segregated data structureA throughN may also be a node of the distributed asset networkin communication with the common platform. Thus, the segregated data structuresA throughN provide a distributed network of nodes for moving both assets and tokenized assets across the distributed asset network.

In some scenarios, local or internal asset movements are more efficient than asset movements to and/or from an external entity, system and/or platform. For example, transferring funds between accounts of a single banking system is faster and more efficient than transferring funds between an account of one banking system to an account of another banking system. Similarly, transferring data files between accounts and/or storage locations of a single database system uses fewer computational and network resources than transferring the same data files to and/or from an external or remote account/storage location.

Therefore, pairing each entity platformA throughN with a respective segregated data structureA throughN enables a data structure dedicated to external/remote transfers to be implemented locally to each entity platformA throughN. By configuring the segregated data structureA throughN to be a part of the distributed asset network, each entity platformA throughN may initiate transfers to external or remote platforms by transferring assets to the distribute asset networkvia the segregated data structureA throughN. In some embodiments, in parallel, each entity platformA throughN may access the common platformvia the segregated data structuresA throughN to transfer tokenized assets associated with each asset being transferred.

In some embodiments, platforms may be linked for communication across multiple networks. In some embodiments, the common platformprovides a parallel network for interoperability between entity platformsA throughC. The common platformmay include an interoperability layer than can interface with each entity platformsA throughC of member entities, e.g., a first entity platformsA throughC of a first member entity, a second entity platformsA throughC of a second member entity, among other entity platformsA throughC of additional member entities. Communications over a traditional network between the entity platformsA throughC may be slow, costly, resource intensive, or otherwise deficient for continuous and/or real-time interactions between users on different entity platformsA throughC. For example, if a first user intends to perform an operation with a second user, and the first user in the first entity platformsA throughC while the second user is on the second-entity specific platform, the operation may face technical hurdles such as slow communication between the entity platformsA throughC, incompatibilities between data on the first entity platformsA throughC and on the second entity platformsA throughC, third-party operations for facilitating, regulating and performing fraud/security checks on the operation, among other hurdles. Such technical hurdles make performing the operation inefficient and unreliable and with lag between initiating the operation and completion of the operation.

Accordingly, in some embodiments, the first entity platformsA throughC and the second entity platformsA throughC may interface with the common platformto perform parallel real-time operations over a distributed crypto-ledger. The distributed crypto-ledgermay employ encrypted storage for each entity to effectuate token-based operations between the entities via the use of crypto-tokens that represent the data of the operation between the users.

In some embodiments, the exemplary distributed crypto-ledgermay be configured interact and/or to store data in one or more private and/or private-permissioned cryptographically-protected, distributed databased such as, without limitation, a blockchain (distributed ledger technology), Ethereum (Ethereum Foundation, Zug, Switzerland), and/or other similar distributed data management technologies. For example, as utilized herein, the distributed database(s), such as distributed ledgers ensure the integrity of data by generating a chain of data blocks linked together by cryptographic hashes of the data records in the data blocks. For example, a cryptographic hash of at least a portion of data records within a first block, and, in some cases, combined with a portion of data records in previous blocks is used to generate the block address for a new digital identity block succeeding the first block. As an update to the data records stored in the one or more data blocks, a new data block is generated containing respective updated data records and linked to a preceding block with an address based upon a cryptographic hash of at least a portion of the data records in the preceding block. In other words, the linked blocks form a blockchain that inherently includes a traceable sequence of addresses that can be used to track the updates to the data records contained therein. The linked blocks (or blockchain) may be distributed among multiple network nodes within a computer network such that each node may maintain a copy of the blockchain. Malicious network nodes attempting to compromise the integrity of the database must recreate and redistribute the blockchain faster than the honest network nodes, which, in most cases, is computationally infeasible. In other words, data integrity is guaranteed by the virtue of multiple network nodes in a network having a copy of the same blockchain. In some embodiments, as utilized herein, a central trust authority for sensor data management may not be needed to vouch for the integrity of the distributed database hosted by multiple nodes in the network.

In some embodiments, the exemplary distributed blockchain-type ledger implementations of the present disclosure with associated devices may be configured to affect transactions involving Bitcoins and other cryptocurrencies into one another and also into (or between) so-called FIAT money or FIAT currency and vice versa.

In some embodiments, the exemplary distributed blockchain-type ledger implementations of the present disclosure with associated devices are configured to utilize self-executing programming objects, e.g., smart contracts, that are computer processes that facilitate, verify and/or enforce negotiation and/or performance of one or more particular activities among users/parties. For example, an exemplary smart contract may be configured to be partially or fully self-executing and/or self-enforcing. In some embodiments, the exemplary inventive asset-tokenized distributed blockchain-type ledger implementations of the present disclosure may utilize smart contract architecture that can be implemented by replicated asset registries and contract execution using cryptographic hash chains and Byzantine fault tolerant replication. For example, each node in a peer-to-peer network or blockchain distributed network may act as a title registry and escrow, thereby executing changes of ownership and implementing sets of predetermined rules that govern transactions on the network. For example, each node may also check the work of other nodes and in some cases, as noted above, function as miners or validators.

In some embodiments, the operation may include a transfer of data, such as, e.g., an internet message communication, an SMS/MMS/RCS message, a file transfer, an electronic financial transfer (e.g., a money wire via, e.g., ACH or FedWire, etc.), among other transfers. Accordingly, the entity platformsA throughC may use the common platformto perform parallel transfers of tokenizations of the data for secure, immutable, and real-time transfer between the entity platformsA throughN.

In some embodiments, the common platformallows users of a member entity to send confirmed real-time data to users of other member entities. The common platformmay convey the data via a tokens or tokenized data representing the data between the member entities. For example, for payment operations, the common platformmay use tokens representing currency, such as, e.g., any suitable crypto-tokens, including bitcoin, Ether, Dogecoin, a stablecoin, or other suitable crypto-token or any suitable combination thereof.

Upon transferring the tokens and/or tokenized data between the member entities, the transfer of the original data may be reconciled with the transfer of the tokens and/or tokenized data to verify the completion and integrity of the operation.

In some embodiments, where the operation is a financial monetary transfer, the transfer of the original data may include a physical and/or digital transfer of the currency. Reconciliation of the transfer of the tokens and/or tokenized data and the transfer of the currency may take the form of settlement, e.g., via FedWire. FedWire may be a slow, computationally expensive, and financially expensive such that each operation cannot be feasibly performed in real-time. Thus, common platformprovides the real-time transfer which may then be settled after the fact with the transfer of the currency. Accordingly, the transfer of the currency may be performed at any suitable time after the real-time transfer of tokens representing the currency. As a result, currency transfers may be batched based on aggregated amounts between entities to consolidate many transfers into one operation over the network between the entity platformsA throughC.

In some embodiments, the common platformmay convey payment instructions between member entities for currency settlement (e.g., US Dollar settlement, or other currency or combination of currencies) between member entities may be performed over FedWire or other suitable wiring service. In some embodiments, the distributed crypto-ledgerthe common platformutilizes a private permissioned blockchain. In some embodiments, the common platformmay issue payment instructions and may utilize tokens that include or do not include stablecoins. In some embodiments, the common platformpermits permissioned self-executing programming objects, such as, e.g., smart contracts, and documentation to be attached to the instructions. In some embodiments, the common platformarchitecture allows third parties to develop permissioned applications (e.g., for vertical markets, healthcare, receivables, mortgages, trade) that benefit from utilizing the common platforminfrastructure.

In some embodiments, access to the common platformis limited to regulated member entities. Thus, in some embodiments, every member entity on the common platformis approved by an administrator or group of administrators (such as a Board of Directors) of the common platformand is subject to the governance requirements set by the common platform. In some embodiments, every member entity may be required to meet all requirements set by the common platform, e.g., regulatory compliance, solvency, transparency, KYC, etc. Additionally, in some embodiments, the common platformwill be able to provide Regulators with access to all necessary data for transparency, compliance and regulatory purpose as requested and agreed by the common platformand regulators.

In some embodiments, the regulators may be provided with transparency into the common platformoperations as well as operations between the entity platformsA throughC. Thus, regulators are provided with total transparency on all transactions as well as the tokens in the common platformsystems, and the assets (e.g., funds) held in the digital inter-entity common platformsegregated accounts (“segregated accounts”) across member entities and associated entity platformsA throughN of the common platform. Accordingly, permissions on the common platformmay include requirements of member entities regarding the regulators, such as being in good standing with applicable regulators, submitting to oversight of the requirements for all member entities, including KYC/AML policies, procedures and protocols, ensuring minimum KYC requirements are provided through parameters defined by the administrators of the common platformand the regulators, among other requirements or any combination thereof.

In some embodiments, a user may trigger a transfer instruction, such as a payment instruction, message instruction, data transfer instruction, etc. The transfer instruction may be originated through a member entity's core system (e.g., FIS, Fiserv), or through an approved and permissioned platform, including an approved and permissioned payments platform or other platform for performing transfers. In some embodiments, the member entity's platform communicates instructions to the common platformto effectuate the transfer via a token transfer on the distributed crypto-ledger. Such an arrangement may enable the member entities to have total transparency into the tokens and the dollars held in segregated accounts across the common platform. The transfer may then be settled via batch transfers in parallel, for example using FedWire or other suitable service.

In some embodiments, at regular intervals, there is an automated net settlement between the segregated accounts at member entities. In some embodiments, the common platformmay use predictive analytics based on machine learning/AI that include information such as risk tolerance of each member first member entity and transaction history for intraday settlement instruction. In addition, the system may trigger close of day “true-up” settlement instructions that also optimize for parallel network blackouts, so there is no disruption of the common platformservice during afterhours/weekends/etc. In some embodiments, in the context of financial transfer, real-time reconciliation of summed segregated accounts to blockchain balance may prove constant 1:1 US Dollar backing.

In some embodiments, every token minted on the distributed crypto-ledgeris backed by a corresponding asset unit (e.g., US dollars, corresponding files and/or messages, etc.) in a segregated account at the originating member entity. In some embodiments, receiving member entities (and regulators) have assurance through real-time reporting that every Transfer Token is backed 100% by the asset on deposit in a segregated account at the originating member entity.

In some embodiments, when deposits are made into the segregated account, Transfer Tokens are minted (upon instruction by the system) on the distributed crypto-ledgerand the corresponding the asset backing the Transfer Tokens are blocked in the segregated account. Upon receipt of the asset at the receiving entity (e.g., through FedWire for financial transfers) the common platform's system may burn (extinguishment) the equivalent number of Transfer Token in the receiving member entity's wallet.

In some embodiments, the distributed crypto-ledgerof the common platformmay employ distributed crypto-ledger-specific crypto-tokens (e.g., “Transfer Tokens”) that represent payment instructions. In some embodiments, one transfer token may represent one data item being transferred. For example, 1 transfer token may be equivalent to 1 US dollar. However, other equivalencies may be employed, such as, e.g., 100 transfer tokens may be equivalent to 1 US dollar, or other suitable equivalency. In some embodiments, the transfer tokens only exist at participant member entities within the distributed crypto-ledger. Thus, the member entities are not permissioned to self-custody the transfer tokens. Rather, the common platformallows for backing funds in legal tender.

Therefore, in some embodiments, the common platformmay use the execution engineto transfer tokenized assets between entity platformsA throughN across the distributed asset networkof the segregated data structuresA throughN. Thus, tokenized assets may be transferred in real-time across the distributed asset networkusing distributed storage and operations, e.g., using the distributed crypto-ledger.

In some embodiments, a sending entity platform may use a respective sending segregated data structure to instruct an asset to be transferred to a receiving entity platform. The common platformmay use the execution engineto access and/or create a tokenized asset associated with the asset to be transferred and execute a transfer of the tokenized asset to a receiving segregated data structure of the receiving entity platform. For example, the execution enginemay write, in real-time in response to the instruction to transfer the asset, a cryptographic immutable entry to the distributed crypto-ledger, thus reassigning the tokenized asset to the receiving segregated data structure.

In some embodiments, the common platformmay implement the execution engineand the distributed crypto-ledgerto enable real-time execution of each transfer instructed by each segregated data structureA throughN on the distributed asset network. Thus, secure transfer of the tokenized assets can be efficiently performed.

In some embodiments, the associated assets of the tokenized assets transferred across the distributed asset networkmay be transferred separately. In some embodiments, a separate net transmission execution systemmay be employed to transfer assets between entity platformsA throughN. Because the transfer of assets is less efficient and slower than the transfer of tokenized assets using the common platform, the transfer of assets can be performed in batches, e.g., at periodic, predetermined and/or dynamically determined intervals of time to satisfy the transfer of tokenized assets representing each asset. In some embodiments, the net transmission engineof the common platformmay interface with the segregated data structuresA throughN and a net transmission execution system.

In some embodiments, the net transmission enginemay aggregate the transfers of tokenized assets between each entity platformA throughN for a given interval of time and trigger a net transmission to satisfy the transfers with one or more transfers of associated assets or equivalents of the associated assets. For example, in transfers of monetary funds, the tokenized assets may include cryptographic tokens (“crypto-tokens” or “tokens”) which are transferred across the distributed asset networkin real-time via the distributed crypto-ledger. The value of monetary funds may be performed in bulk settlement operations with the net transmission execution systemincluding a monetary settlement system such as, e.g., FedWire or other suitable system.

In some embodiments, the net transmission enginemay determine a net quantity, value, amount, magnitude, or other attribute of the transfers of tokenized assets between any two entity platformsA throughN to determine the aggregate assets to transfer between the two entity platformsA throughN. The segregated data structuresA throughN of the entity platformsA throughN may communicate with the net transmission execution systemaccording to instructions by the net transmission engineto execute a net transmission the moves the aggregate assets between the two entity platformsA throughN.