Patent Description:
<CIT> describes a closed-loop system operatively connected with a block chain distributed network for using the block chain distributed network for facilitating operation of a transaction record sharing system between member institutions comprising a host system and a source system. Host and source institutions function to share the transaction records from member institutions such that a host institution that is a member of the block chain may obtain the transaction records of all source institutions of the block chain. The transaction records are validated on the block chain such that the transaction records are secure represent a source of truth.

<CIT> describes a method for distribution and transfer of entitlement certificates including: storing account profiles, each account including an account identifier, primary account number, and account balance; receiving an entitlement request from a computing device including a specific account identifier, entitlement balance, and usage controls; identifying a specific account profile that includes the specific account identifier; generating an entitlement certificate that includes the entitlement balance and usage controls; generating an entitlement identifier for the entitlement certificate; placing a hold associated with the entitlement certificate on the account balance included in the specific account profile for the entitlement balance; and transmitting the entitlement certificate to the computing device.

<CIT> describes a method for authorization of a blockchain transaction including: storing account profiles, each profile including an account identifier, fiat amount, and blockchain amount; receiving a transaction message, the transaction message being formatted based on transaction message standards and including a first data element that includes a specific account identifier and a second data element reserved for private use that includes a network identifier and transaction amount; identifying a specific account profile that includes the specific account identifier; identifying a risk value based on the transaction amount and at least one of: the fiat amount and blockchain amount; determining authorization of a transaction based on the identified risk value; modifying the transaction message based on the authorization determination; and transmitting the modified transaction message.

A computing system according to the invention includes: at least one server; at least one client communicatively coupled to the at least one server; at least one broker-dealer database storing personally identifiable information for accounts; and at least one distributed ledger communicatively coupled to the at least one server. The at least one server is configured to receive a request to obtain the personally identifiable information regarding public transaction information for a first account from a first user of a first client of the at least one client. The at least one server is configured to determine that a broker-dealer database of the at least one broker-dealer database includes the personally identifiable information for the first account. The at least one server is configured to determine whether the first user has permission to obtain the personally identifiable information for the first account from the broker-dealer database that includes the personally identifiable information for the first account. The at least one server is configured to receive the public transaction information for the first account from a distributed ledger when the first user has permission to obtain the personally identifiable information for the first account from the broker-dealer database that includes the personally identifiable information for the first account. The at least one server is configured to map the personally identifiable information from the broker-dealer database that includes the personally identifiable information for the first account with the public transaction information received from the at least one distributed ledger to generate mapped information.

Understanding that the drawings depict only exemplary embodiments and are not therefore to be considered limiting in scope, the exemplary embodiments will be described with additional specificity and detail through the use of the accompanying drawings, in which:.

In accordance with common practice, the various described features are not drawn to scale but are drawn to emphasize specific features relevant to the exemplary embodiments.

In the following detailed description, reference is made to the accompanying drawings that form a part hereof, and in which is shown by way of illustration specific illustrative embodiments. However, it is to be understood that other embodiments may be utilized and that logical, mechanical, and electrical changes may be made. Furthermore, the method presented in the drawing figures and the specification is not to be construed as limiting the order in which the individual steps may be performed. The following detailed description is, therefore, not to be taken in a limiting sense.

A distributed ledger is an electronic ledger that is distributed across multiple interconnected network nodes, where more than one of the network nodes stores a copy of the ledger. In some embodiments, distributed ledgers implement blockchains to validate the data stored within the distributed ledger.

A blockchain is a verifiable permanent ledger constructed one block at a time with a proof-of-work seal (such as a hash) affixed to each block that validates that block. In any blockchain, the hash of the previous block is included in the current block, and therefore by recursion the current hash also validates all previous blocks back to the original genesis block. Inserting a hash into a blockchain permanently records that hash and acts as a notary verifying the time stamped proof-of-existence of the hashed data at the moment in time that block is added to the chain. Any future blocks add a layer of protection from manipulation of the data stored in the chain or a chain re-org and therefore provide additional certainty that no changes can be made to blocks earlier in the chain.

In exemplary embodiments, a distributed ledger (such as a blockchain) is used to store information regarding public trades for at least one exchange/market. In exemplary embodiments, the distributed ledger is publically accessible, though it does not include personally identifiable information. In exemplary embodiments, the information stored on the chain may include public addresses for accounts participating in the trade (such as a sending account and a receiving account) and an indication of the asset being traded and the quantity of the asset being traded. In exemplary embodiments, this could be used as an alternative to traditional public exchanges/markets, such as those used for securities, currency, commodities, etc. There are benefits to not including personally identifiable information (PII) on a publicly accessible distributed ledger, including but not limited to increased privacy for individuals and entities engaging in trades, security of personally identifiable information (PII), and speed of the blockchain. That said, it may be beneficial for some individuals or entities to have access to more than just public addresses, asset types, and quantities of trades listed on the public distributed ledger (such as a blockchain). Described herein are embodiments of enabling mapping of personally identifiable information (PII) from external sources, such as broker databases, with anonymized data from a public distributed ledger.

<FIG> is a block diagram of an example federated personally identifiable information (PII) service system <NUM>. Federated PII service system <NUM> includes at least one federated PII service platform <NUM> connected to at least one broker dealer database <NUM> (such as broker-dealer database <NUM>-<NUM> and any quantity of optional broker dealer databases <NUM> such as optional broker dealer database <NUM>-<NUM> through optional broker dealer database <NUM>-A), at least one computing device <NUM> (such as any of computing device <NUM>-<NUM> through <NUM>-B), and at least one distributed ledger <NUM> by at least one network <NUM> (such as network <NUM>-<NUM> and any quantity of networks <NUM> through network <NUM>-C). In exemplary embodiments, each broker-dealer database <NUM> stores personally identifiable information <NUM> (such as personally identifiable information <NUM>-<NUM> and any quantity of optional personally identifiable information <NUM> such as optional personally identifiable information <NUM>-<NUM> through personally identifiable information <NUM>-A). In exemplary embodiments, the federated PII service system <NUM> and/or at least one federated PII service platform <NUM> are implemented at at least one of the trading venues for efficiency.

In exemplary embodiments, at least one network <NUM> includes separate networks between various components of the federated PII service system <NUM>. In other exemplary embodiments, the at least one network <NUM> includes a single network between all the various components of the federated PII service system <NUM>. In exemplary embodiments, the at least one network <NUM> includes at least one wired network and/or at least one wireless network. In exemplary embodiments, any combination of wired and wireless networks can be used for at least one network <NUM> (such as but not limited to at least one of at least one local area network (LAN), at least one wide area network (WAN), and the Internet). In exemplary embodiments, any combination of local area networks, wide area networks, and the Internet is used for the at least one network <NUM>. In exemplary embodiments, the at least one computing device <NUM> are each communicatively coupled to the federated PII service platform <NUM> through at least one network <NUM>. In exemplary embodiments, any quantity of intermediary devices are positioned in the communication path between a computing device <NUM> and the federated PII service platform <NUM>, where the intermediary devices perform forwarding, relay, and/or routing of messages between the computing device <NUM> and the federated PII service platform <NUM>. In exemplary embodiments, the at least one broker-dealer database <NUM> are each communicatively coupled to the federated PII service platform <NUM> through at least one network <NUM>. In exemplary embodiments, any quantity of intermediary devices are positioned in the communication path between a broker-dealer database <NUM> and the federated PII service platform <NUM>, where the intermediary devices perform forwarding, relay, and/or routing of messages between the broker-dealer database <NUM> and the federated PII service platform <NUM>. In exemplary embodiments, the at least one distributed ledger <NUM> is coupled to the federated PII service platform <NUM> through at least one network <NUM>. In exemplary embodiments, any quantity of intermediary devices are positioned in the communication path between the at least one distributed ledger <NUM> and the federated PII service platform <NUM>, where the intermediary devices perform forwarding, relay, and/or routing of messages between the distributed ledger <NUM> and the federated PII service platform <NUM>.

In exemplary embodiments, the federated PII service platform <NUM> and/or computing devices <NUM> can be any of a mobile computing device (such as a mobile phone, tablet computer, mobile media device, mobile gaming device, laptop computer, vehicle-based computer, etc.) or a non-mobile device (such as a dedicated terminal, a public terminal, a kiosk, a server, or a desktop computer). In exemplary embodiments, each computing device <NUM> can have similar components to exemplary federated PII service platform <NUM> shown in <FIG> and described below. In exemplary embodiments, each computing device <NUM> includes at least one memory, at least one processor, at least one network interface, at least one optional display device, at least one optional input device, and at least one power source. While the federated PII service platform <NUM> is shown as a distinct component from computing devices <NUM> within federated PII service system <NUM>, in exemplary embodiments the federated PII service platform <NUM> is implemented on at least one of the computing devices <NUM>, such that the computing device <NUM> implements the federated PII service platform <NUM> rather than it being implemented on a separated device.

In exemplary embodiments, the trading history is a trade history for any assets, including but not limited to, securities, bonds, currencies, funds (such as exchange traded funds ("ETFs"), mutual funds, index funds, open-end funds, closed-end funds, high yield bond funds, corporate bond funds, municipal bond funds, government bond funds, bond funds, money market funds, balanced funds, equity funds, fixed income funds, global funds, international funds, specialty funds, index funds, commodity funds, currency funds, and/or real estate funds), and/or other assets. In exemplary embodiments, a user of a computing device <NUM> connects to the federated PII service platform <NUM> in order to map/overlay personally identifiable information (PII) over publicly available anonymized data from at least one distributed ledger <NUM>. In exemplary embodiments, the computing device <NUM> connects to the federated PII service platform <NUM> using credentials which allow it to have access to PII information from at least one broker-dealer database <NUM>. In exemplary embodiments, the computing device <NUM> transmits a first request from a first user to the federated PII service platform <NUM> to obtain personally identifiable information regarding a trading history for a first account. The federated PII service platform <NUM> then determines which of a plurality of broker-dealer databases <NUM> includes the personally identifiable information <NUM> for the first account. In exemplary embodiments, the federated PII service platform <NUM> determines which of the plurality of broker-dealer databases <NUM> includes the personally identifiable information <NUM> for the first account based on information received from one or more of the at least one broker-dealer database <NUM>. In exemplary embodiments, the federated PII service platform <NUM> determines which of the plurality of broker-dealer databases <NUM> includes the personally identifiable information <NUM> for the first account at least in part by being configured to: (<NUM>) query one or more of the at least one broker-dealer database <NUM>; (<NUM>) receive information back from the one or more of the at least one broker-dealer database <NUM> indicative of whether the one or more of the at least one broker-dealer database <NUM> includes the personally identifiable information <NUM> for the first account. ; and (<NUM>) determine which broker-dealer database <NUM> of the at least one broker-dealer database <NUM> includes the personally identifiable information for the first account based on the information received back from the one or more of the at least one broker-dealer database <NUM> indicative of whether the at least one broker-dealer database <NUM> includes the personally identifiable information for the first account.

The federated PII service platform <NUM> then determines whether the first user has permission to obtain the personally identifiable information <NUM> regarding the trading history for the first account. When the first user has permission to obtain the personally identifiable information <NUM> regarding the trading history for the first account, the federated PII service platform <NUM> provides mapping data to the communication portal enabling mapping of the personally identifiable information <NUM> regarding the trading history for the first account. In exemplary embodiments, the federated PII service platform <NUM> requests public trading information from the at least one distributed ledger <NUM>. In exemplary embodiments, the personally identifiable information <NUM> from the broker-dealer database <NUM> is mapped with the public transaction information from the at least one distributed ledger <NUM>.

<FIG> is a block diagram of federated PII service platform <NUM> included within the federated PII service system <NUM>. Federated PII service platform <NUM> includes at least one memory <NUM>, at least one processor <NUM>, at least one PII mapping module <NUM>, at least one network interface <NUM>, at least one optional display device <NUM>, at least one optional input device <NUM>, and at least one optional power source <NUM>.

In exemplary embodiments, the at least one memory <NUM> can be any device, mechanism, or populated data structure used for storing information. In exemplary embodiments, the at least one memory <NUM> can be or include any type of volatile memory, nonvolatile memory, and/or dynamic memory. For example, the at least one memory <NUM> can be random access memory, memory storage devices, optical memory devices, magnetic media, floppy disks, magnetic tapes, hard drives, erasable programmable read-only memories (EPROMs), electrically erasable programmable read-only memories (EEPROMs), optical media (such as compact discs, DVDs, Blu-ray Discs) and/or the like. In accordance with some embodiments, the at least one memory <NUM> may include one or more disk drives, flash drives, one or more databases, one or more tables, one or more files, local cache memories, processor cache memories, relational databases, flat databases, and/or the like. In addition, those of ordinary skill in the art will appreciate many additional devices and techniques for storing information which can be used as the at least one memory <NUM>. The at least one memory <NUM> may be used to store instructions for running one or more applications or modules on the at least one processor <NUM>. For example, the at least one memory <NUM> could be used in one or more embodiments to house all or some of the instructions needed to execute the functionality of the at least one PII mapping module <NUM> and/or the optional at least one PII mapping module <NUM>. In exemplary embodiments, the at least one processor <NUM> can be any known processor, such as a general purpose processor (GPP) or special purpose (such as a field-programmable gate array (FPGA), application-specific integrated circuit (ASIC) or other integrated circuit or circuitry), or any programmable logic device. In exemplary embodiments, the at least one PII mapping module <NUM> is implemented by the at least one processor <NUM> and the at least one memory <NUM>.

In exemplary embodiments, the optional at least one display device <NUM> includes at least one of a light emitting diode (LED), a liquid crystal display (LCD), a light emitting diode (LED) display, an organic light emitting diode (OLED) display, an e-ink display, a field emission display (FED), a surface-conduction electron-emitter display (SED), and a plasma display. In exemplary embodiments, the optional at least one input device <NUM> include at least one of a touchscreen (including capacitive and resistive touchscreens), a touchpad, a capacitive button, a mechanical button, a switch, a dial, a keyboard, a mouse, a camera, a biometric sensor/scanner, etc. In exemplary embodiments, the optional at least one display device <NUM> and the optional at least one input device <NUM> are combined into a human machine interface (HMI) for user interaction with the computing device <NUM>.

In exemplary embodiments, the at least one optional network interface <NUM> is a cabled network interface configured for connection with a cabled media (such as but not limited to an Ethernet cable, a fiber optic cable, twisted pair, Category cabling, or other conductive or optical media). In exemplary embodiments, the at least one optional network interface <NUM> is a wireless network interface and includes or is coupled to at least one optional antenna for communication with a network. In exemplary embodiments, the at least one optional network interface <NUM> includes at least one of an Ethernet interface, a cellular radio access technology (RAT) radio, a WiFi radio, a Bluetooth radio, and a near field communication (NFC) radio. In exemplary embodiments, the at least one optional network interface <NUM> includes a cellular radio access technology radio configured to establish a cellular data connection (mobile internet) of sufficient speeds with a remote server using a local area network (LAN) or a wide area network (WAN). In exemplary embodiments, the cellular radio access technology includes at least one of Personal Communication Services (PCS), Specialized Mobile Radio (SMR) services, Enhanced Special Mobile Radio (ESMR) services, Advanced Wireless Services (AWS), Code Division Multiple Access (CDMA), Global System for Mobile Communications (GSM) services, Wideband Code Division Multiple Access (W-CDMA), Universal Mobile Telecommunications System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX), 3rd Generation Partnership Projects (3GPP) Long Term Evolution (LTE), High Speed Packet Access (HSPA), third generation (<NUM>) fourth generation (<NUM>), fifth generation (<NUM>), etc. or other appropriate communication services or a combination thereof. In exemplary embodiments, the at least one optional network interface <NUM> includes a WiFi (IEEE <NUM>) radio configured to communicate with a wireless local area network that communicates with the remote server, rather than a wide area network. In exemplary embodiments, the at least one optional network interface <NUM> includes a near field radio communication device that is limited to close proximity communication, such as a passive near field communication (NFC) tag, an active near field communication (NFC) tag, a passive radio frequency identification (RFID) tag, an active radio frequency identification (RFID) tag, a proximity card, or other personal area network device. In exemplary embodiments, the same at least one optional network interface <NUM> is also used for communication with an external gateway device to a network (such as an NFC payment terminal).

In exemplary embodiments, at least one optional power source <NUM> is used to provide power to the various components of the federated PII service platform <NUM>.

In exemplary embodiments, the PII mapping module <NUM> is implemented by the at least one processor <NUM>, at least one memory <NUM>, and/or other components within the federated PII service platform <NUM>. In exemplary embodiments, the PII mapping module <NUM> is configured to receive a request from a computing device <NUM> for a user to connect to the federated PII service platform <NUM> using credentials which allow it to have access to PII information from at least one broker-dealer database <NUM>. In exemplary embodiments, the PII mapping module <NUM> is configured to receive a request from a first user to obtain personally identifiable information regarding a trading history for a first account. The PII mapping module <NUM> then determines which of the plurality of broker-dealer databases <NUM> includes the personally identifiable information <NUM> for the first account. The PII mapping module <NUM> then determines which of the broker-dealer databases <NUM> includes the personally identifiable information <NUM> for the first account. In exemplary embodiments, the PII mapping module <NUM> determines which of the plurality of broker-dealer databases <NUM> includes the personally identifiable information <NUM> for the first account based on information received from one or more of the at least one broker-dealer database <NUM>. In exemplary embodiments, the PII mapping module <NUM> determines which of the plurality of broker-dealer databases <NUM> includes the personally identifiable information <NUM> for the first account at least in part by being configured to: (<NUM>) query one or more of the at least one broker-dealer database <NUM>; (<NUM>) receive information back from the one or more of the at least one broker-dealer database <NUM> indicative of whether the one or more of the at least one broker-dealer database <NUM> includes the personally identifiable information <NUM> for the first account. ; and (<NUM>) determine which broker-dealer database <NUM> of the at least one broker-dealer database <NUM> includes the personally identifiable information for the first account based on the information received back from the one or more of the at least one broker-dealer database <NUM> indicative of whether the at least one broker-dealer database <NUM> includes the personally identifiable information for the first account.

The PII mapping module <NUM> then determines whether the first user has permission to obtain the personally identifiable information <NUM> regarding the trading history for the first account. When the first user has permission to obtain the personally identifiable information <NUM> regarding the trading history for the first account, the broker-dealer database <NUM> provides mapping data to the PII mapping module <NUM> enabling mapping of the personally identifiable information <NUM> regarding the trading history for the first account. In exemplary embodiments, the PII mapping module <NUM> requests public transaction information from the at least one distributed ledger <NUM>. In exemplary embodiments, the personally identifiable information <NUM> from the broker-dealer database <NUM> is mapped by the PII mapping module <NUM> with the public transaction information from the at least one distributed ledger <NUM>. The mapped data is then provided by the PII mapping module <NUM> back to the computing device <NUM> that requested the information.

<FIG> is flow diagram of an exemplary method <NUM> for implementing a federated personally identifiable information (PII) service system (such as federated PII service system <NUM>). Exemplary method <NUM> begins at block <NUM> with receiving a request from a user through a communication portal to obtain personally identifiable information regarding a trading history for an account. Exemplary method <NUM> proceeds to block <NUM> with determining which broker-dealer database includes personally identifiable information for the account. Exemplary method <NUM> proceeds to block <NUM> with determining whether the user has permission to obtain personally identifiable information regarding a trading history for the account. When the user has permission to obtain the personally identifiable information regarding the trading history for the account at block <NUM>, exemplary method <NUM> proceeds to block <NUM> with providing mapping data to the communication portal enabling mapping of personally identifiable information regarding the trading history for the account. Exemplary method <NUM> proceeds to block <NUM> with requesting public trading information from a distributed ledger. Exemplary method <NUM> proceeds to block <NUM> with mapping personally identifiable information with the public trading information using the mapping data. In exemplary embodiments, when the user does not have permission to obtain the personally identifiable information regarding the trading history for the account at block <NUM>, exemplary method <NUM> proceeds to optional block <NUM> with providing feedback to the user regarding a lack of permission.

<FIG> is a flow diagram of an exemplary method <NUM> for implementing a federated personally identifiable information (PII) service system (such as federated PII service system <NUM>). Blocks <NUM> and <NUM> of exemplary method <NUM> illustrate what happens when an issuer issuing an asset for trading. Specifically, exemplary method <NUM> begins at block <NUM> with an issuer issuing an asset having a symbol. Exemplary method <NUM> proceeds to block <NUM> with the federated service collecting the symbol of the asset to register the symbol of the asset with the federated service. In exemplary embodiments, the issuer also registers the symbol of the asset with a trading venue.

Blocks <NUM> and <NUM> of exemplary method <NUM> illustrate what happens when a broker dealer starts allowing trades on a particular symbol and a trading venue. Specifically, exemplary method <NUM> proceeds to block <NUM> with the broker dealer (BD) registering PII information for the owner of a particular symbol for an asset. Exemplary method <NUM> proceeds to block <NUM> with the federated PII service collecting the API server information for the owner of PII for the particular asset symbol to register the API server information for the owner of PII for the particular asset symbol with the federated service. In exemplary embodiments, the issuer also registers the PII information for the owner of the particular symbol of the asset with a trading venue. In exemplary embodiments, each trading venue also acts as a federated service, which may be more efficient.

Blocks <NUM>, <NUM>, <NUM>, and <NUM> of exemplary method <NUM> illustrate user onboarding for a new trading account for a new trading user. Specifically, exemplary method <NUM> begins at block <NUM> with receiving a trader registration request for a new trading account for a new trading user. Exemplary method <NUM> proceeds to block <NUM> with collecting personally identifiable information (PII) for the new trading user. Exemplary method <NUM> proceeds to block <NUM> with performing checks of know your customer (KYC) / anti-money laundering (AML) for the new trading user. If the user passes the KYC/AML checks at block <NUM>, exemplary method <NUM> proceeds to block <NUM> with onboarding the new trading user and/or creating a new trading account.

Blocks <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, and <NUM> of exemplary method <NUM> illustrate a trading history request for a particular trading account and/or trading user from a portal user using a communication portal. Specifically, exemplary method <NUM> proceeds to block <NUM> with receiving a request from a portal user at a communication portal for a trading history for a particular trading account and/or trading user. Exemplary method <NUM> proceeds to block <NUM> with generating a query to obtain personally identifiable information (PII) regarding a trading history for the particular trading account and/or trading user. Exemplary method <NUM> proceeds to block <NUM> with determining which broker dealer(s) (BD(s)) trades an asset for the particular trading account and/or trading user. Exemplary method <NUM> proceeds to block <NUM> with sending an inquiry to the broker dealer(s) who trades the asset for the particular trading account and/or trading user. Exemplary method <NUM> proceeds to block <NUM> with determining whether the portal user has permission to obtain PII data for the particular trading account and/or trading user based on access rules.

Exemplary method <NUM> proceeds to block <NUM> with obtaining the blockchain trade identifier to the PII mapping data for the particular trading account and/or trading user. Exemplary method <NUM> proceeds to block <NUM> with receiving PII and mapping information from broker dealer(s) for the particular trading account and/or trading user. Exemplary method <NUM> proceeds to block <NUM> with requesting public trading information <NUM> relating to the particular trading account and/or trading user. Exemplary method <NUM> proceeds to block <NUM> with looking up the public trading record <NUM> of the particular trading account and/or trading user. Exemplary method <NUM> proceeds to block <NUM> with mapping PII and public trading records for the particular trading account and/or trading user using the PII and mapping information received from the broker dealer(s). Exemplary method <NUM> proceeds to block <NUM> with displaying the trading records for the particular trading account and/or trading user with the PII mapped onto the trading records.

The techniques introduced here can be embodied as special-purpose hardware (such as circuitry), as programmable circuitry appropriately programmed with software and/or firmware, or as a combination of special-purpose and programmable circuitry. Hence, embodiments may include a machine-readable medium having stored thereon instructions that may be used to program a computer (or other electronic devices) to perform a process. The machine-readable medium may include, for example, floppy diskettes, optical disks, compact disc read-only memories (CD-ROMs), magneto-optical disks, read-only memories (ROMs), random access memories (RAMs), erasable programmable read-only memories (EPROMs), electrically erasable programmable read-only memories (EEPROMs), magnetic or optical cards, flash memory, or other type of media/machine-readable medium suitable for storing electronic instructions.

Embodiments of the present disclosure include various steps and operations, which have been described above. A variety of these steps and operations may be performed by hardware components or may be embodied in machine-executable instructions, which may be used to cause a general-purpose or special-purpose processor programmed with the instructions to perform the steps. Alternatively, the steps may be performed by a combination of hardware, software, and/or firmware. As such, <FIG> is an example of a computer system <NUM> with which embodiments of the present disclosure may be utilized. According to the present example, the computer system <NUM> includes an interconnect <NUM>, at least one processor <NUM>, at least one communication port <NUM>, at least one main memory <NUM>, at least one removable storage media <NUM>, at least one read only memory <NUM>, and at least one mass storage device <NUM>.

The at least one processor <NUM> can be any known processor. The at least one communication port <NUM> can be or include, for example, any of an RS-<NUM> port for use with a modem-based dialup connection, a <NUM>/<NUM> Ethernet port, or a Gigabit port using copper or fiber. The nature of the at least one communication port <NUM> may be chosen depending on a network such a Local Area Network (LAN), Wide Area Network (WAN), or any network to which the computer system <NUM> connects. The at least one main memory <NUM> can be Random Access Memory (RAM), or any other dynamic storage device(s) commonly known in the art. The at least one read only memory <NUM> can be any static storage device(s) such as Programmable Read Only Memory (PROM) chips for storing static information such as instructions for the at least one processor <NUM>.

The at least one mass storage device <NUM> can be used to store information and instructions. For example, hard disks such as the Adaptec® family of SCSI drives, an optical disc, an array of disks such as RAID, such as the Adaptec family of RAID drives, or any other mass storage devices may be used. Interconnect <NUM> can be or include one or more buses, bridges, controllers, adapters, and/or point-to-point connections. Interconnect <NUM> communicatively couples the at least one processor <NUM> with the other memory, storage, and communication blocks. Interconnect <NUM> can be a PCI/PCI-X or SCSI based system bus depending on the storage devices used. The at least one removable storage media <NUM> can be any kind of external hard-drives, floppy drives, Compact Disc-Read Only Memory (CD-ROM), Compact Disc-Re-Writable (CD-RW), Digital Video Disc-Read Only Memory (DVD-ROM).

The components described above are meant to exemplify some types of possibilities. In no way should the aforementioned examples limit the disclosure, as they are only exemplary embodiments.

Brief definitions of terms, abbreviations, and phrases used throughout this application are given below.

The terms "connected", "coupled", and "communicatively coupled" and related terms are used in an operational sense and are not necessarily limited to a direct physical connection or coupling. Thus, for example, two devices may be coupled directly, or via one or more intermediary media or devices. As another example, devices may be coupled in such a way that information can be passed there between, while not sharing any physical connection with one another. Based on the disclosure provided herein, one of ordinary skill in the art will appreciate a variety of ways in which connection or coupling exists in accordance with the aforementioned definition.

The phrases "in exemplary embodiments", "in example embodiments", "in some embodiments," "according to some embodiments," "in the embodiments shown," "in other embodiments," "embodiments," and the like generally mean the particular feature, structure, or characteristic following the phrase is included in at least one embodiment of the present disclosure, and may be included in more than one embodiment of the present disclosure. In addition, such phrases do not necessarily refer to the same embodiments or different embodiments.

If the specification states a component or feature "may," "can," "could," or "might" be included or have a characteristic, that particular component or feature is not required to be included or have the characteristic.

The term "responsive" includes completely or partially responsive.

The term "module" refers broadly to a software, hardware, or firmware (or any combination thereof) component. Modules are typically functional components that can generate useful data or other output using specified input(s). A module may or may not be self-contained. An application program (also called an "application") may include one or more modules, or a module can include one or more application programs.

Claim 1:
A computing system (<NUM>) comprising:
at least one server (<NUM>);
at least one client (<NUM>) communicatively coupled to the at least one server (<NUM>);
at least one broker-dealer database (<NUM>) storing personally identifiable information (<NUM>) for accounts;
at least one distributed ledger (<NUM>) communicatively coupled to the at least one server (<NUM>);
wherein the at least one server (<NUM>) is configured to receive (<NUM>) a request to obtain the personally identifiable information (<NUM>) regarding public transaction information for a first account from a first user of a first client (<NUM>) of the at least one client (<NUM>);
wherein the at least one server (<NUM>) is configured to determine (<NUM>) that a broker-dealer database (<NUM>) of the at least one broker-dealer database (<NUM>) includes the personally identifiable information (<NUM>) for the first account;
wherein the at least one server (<NUM>) is configured to determine (<NUM>) whether the first user has permission to obtain the personally identifiable information (<NUM>) for the first account from the broker-dealer database (<NUM>) that includes the personally identifiable information (<NUM>) for the first account;
wherein the at least one server (<NUM>) is configured to receive (<NUM>, <NUM>) the public transaction information for the first account from the at least one distributed ledger (<NUM>) when the first user has permission to obtain the personally identifiable information (<NUM>) for the first account from the broker-dealer database (<NUM>) that includes the personally identifiable information (<NUM>) for the first account; and
wherein the at least one server (<NUM>) is configured to (<NUM>) map (<NUM>) the personally identifiable information (<NUM>) from the broker-dealer database (<NUM>) that includes the personally identifiable information (<NUM>) for the first account with (<NUM>) the public transaction information received from the at least one distributed ledger (<NUM>) to generate mapped information.