System and method for identity resolution across heterogeneous immutable distributed ledger networks
By establishing a unified identity resolution mechanism in the distributed ledger system, the user identity identification problem is solved, the efficiency and transparency of cross-ledger transactions are improved, and regulatory requirements are met.
Patent Information
- Application Number
- CN202110504483.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2018-04-02
- Filing Date
- 2018-10-03
- Publication Date
- 2024-11-12
- Estimated Expiration
- 2038-10-03
AI Technical Summary
In distributed ledger systems, it is difficult to accurately identify user identities, especially in cross-ledger transactions between different networks. The lack of a unified identity link mechanism leads to inefficient transactions and increased risk.
By registering the distributed ledger public keys and addresses associated with a specific business entity or individual, establishing a master identification number, summarizing multiple public keys or addresses, and using the hub server and identity resolution database lookup tables, realizing cross-ledger identity resolution and verify, ensuring transparency and efficiency of transactions.
It realizes unique identification of public keys and addresses in distributed ledger systems, reduces transaction risks, improves business transaction efficiency, and supports regulatory requirements such as "understanding customers" and "anti-money laundering" inspections.
Smart Images

Figure CN113204532B_ABST
Abstract
Description
[0001] The present invention is a divisional application with application date of October 3, 2018, application number 201880065156.4, and invention name “System and method for identity resolution across disparate immutable distributed ledger networks”. The parent application is a PCT national phase application with international application date of October 3, 2018 and application number “PCT / US2018 / 054160”, claiming priority to application number 62 / 568,128 filed with the U.S. Patent Office on October 4, 2017 and application number 62 / 651,369 filed with the U.S. Patent Office on April 2, 2018.
[0002] CROSS-REFERENCE TO RELATED APPLICATIONS
[0003] This application claims priority to U.S. Provisional Patent Application No. 62 / 568,128, filed on October 4, 2017, and U.S. Provisional Patent Application No. 62 / 651,369, filed on April 2, 2018, both of which are incorporated herein by reference in their entirety. Technical Field
[0004] In a distributed ledger system, identity is based on a cryptographic private key held by a user. This private key resolves to a public key, which is then shared to identify and allow the holder of the private key to conduct transactions on the distributed ledger. All users can generate any number of private keys for use, but users may wish to bind their roles to specific public keys.
[0005] Additionally, distributed ledgers forming different networks cannot trust actions taken on other distributed ledgers, and users may want to link their identities between distributed ledgers in order to complete transactions across competing ledgers. Background Art
[0006] A solution to the above problem is proposed in US Patent Publication US 2016 / 0330027, entitled "Identity Management Service Using Blockchain Providing Inter-Device Authentication Transactions". The document discloses logic on a first remote device, and receives a first transaction number and personal data sent from a second remote device. In response to transmitting a signed hash value and a first public key associated with a first private key on the second remote device from the second remote device, the first transaction number is received from a distributed public database. The signed hash value is created by signing the hash value using the first private key, and the hash value is generated by hashing the personal data using a hash algorithm on the second remote device. The logic retrieves the signed hash value and the first public key from the distributed public database using the first transaction number. The logic hashes the personal data using a hash algorithm to create a generated hash value, and verifies the signed hash value based on the generated hash value.
[0007] A distributed ledger is an efficient system where entities send transactions in a trusted manner based on the ledger's requirements. This interaction must be achieved through asymmetric cryptography, where the only person who can generate a valid transaction is the holder of the appropriate private key, and the ledger has the ability to trust past transactions made within its own ecosystem (i.e. its own transaction history).
[0008] There are two main drawbacks to the need to clearly identify parties when transacting on a distributed ledger for regulatory or business operations purposes. First, on most distributed ledgers, counterparties may generate any number of IDs or addresses to conduct transactions. Public keys and public addresses are non-deterministic, and in many cases, entities cannot create similar or meaningful public addresses to identify themselves. The ability to spontaneously generate valid IDs makes it difficult to identify the object to which each ID belongs, which is generally considered a best practice. Second, distributed ledgers can trust their own history, but disparate distributed ledgers cannot trust each other's history, so they cannot transact with each other without a third-party arbitrator or oracle database.
[0009] A system that links identities or addresses on a distributed ledger to a single unified ID representing a physical entity and further links that unified ID to other descriptive attributes to disambiguate transactions and accurately identify transaction counterparties would be beneficial.
[0010] The present invention also provides a number of additional advantages which will become apparent upon reading the following. Summary of the invention
[0011] The present invention generally relates to systems and methods for cross-linking identities or addresses that are part of disparate distributed ledger systems but controlled by a single entity. Distributed ledgers represent an emerging technology that can improve the efficiency of business transactions.
[0012] The present invention describes a system and method for identifying previously unknown counterparties by registering distributed ledger public keys and / or addresses associated with specific business entities and / or individuals. The system and method performs a lookup function for all public keys on various distributed ledgers (such as blockchain) networks, which are aggregated to a master identification number and associate various public keys or addresses with their associated specific company identity information. The purpose is to provide transparency, reduce risks, and improve efficiency when dealing with unknown counterparties through a centralized service.
[0013] The present invention obtains and maintains public keys or "addresses" and associates those keys with disambiguated entities. The present invention allows entities to manage their public-facing pool of distributed ledger identifiers using cryptographic proof messaging and transactions conducted on the distributed ledger. It also allows queries and lookups to discover public keys associated with an entity and allows users to link identifiers on competing distributed ledgers to disambiguated entities, thereby enabling cross-ledger transactions to occur.
[0014] Furthermore, the invention allows for the unique identification of corporate entities and their public keys, thereby enabling due diligence to be performed in the form of Know Your Customer and Anti-Money Laundering checks, which are key requirements for regulated institutions to conduct business.
[0015] In one embodiment, the present invention describes a method for a platform host, comprising:
[0016] For each of the plurality of entities, generate a data store and an entity ID of the entity;
[0017] In data storage, multiple public key distributed ledger addresses are linked to each entity ID;
[0018] In data storage, link each public key distributed ledger address to the distributed ledger network to which they belong;
[0019] providing a hub server connected to an ID resolution server, the ID resolution server including an identity resolution database lookup table;
[0020] storing the plurality of data stores in an identity resolution database lookup table; and
[0021] connecting a plurality of distributed ledger network platform nodes on each of the respective plurality of distributed ledger networks to the hub server;
[0022] The system is configured to perform identity resolution for a single entity on multiple distributed ledger networks.
[0023] The method can further include: embedding the plurality of distributed ledger network platform nodes into respective plurality of distributed ledger networks. The hub server can be connected to the business information database server.
[0024] The method can further include: receiving, at one of the platform nodes on one of the distributed ledger networks, a request for business information about a counterparty to a transaction on the distributed ledger network; sending the request from the platform node to the hub server; and identifying, at the ID resolution server, an entity ID of the counterparty to the transaction. The method can further include: automatically executing, via the platform node, a transaction to an immutable distributed ledger. The method can further include: routing the request from the hub server to a business information database server; obtaining business entity enterprise statistics about the counterparty to the transaction from the business information database server; and outputting the business entity enterprise statistics to the platform node. The business entity enterprise statistics can include business contact information. The method can further include: automatically executing, via the platform node, a transaction to an immutable distributed ledger.
[0025] In one embodiment, the method can further include: verifying, by the hub server, that a plurality of entities that are counterparties to a contract transaction on a first distributed ledger are counterparties to a contract transaction on another distributed ledger network. The method can further include:
[0026] receiving, from a platform network node on a first distributed ledger network, a request to verify that a plurality of entities that are counterparties to a contract transaction on the first distributed ledger are counterparties to a contract transaction on another distributed ledger network;
[0027] Associating, at the hub server, a contract on the first distributed ledger network with a contract on another distributed ledger network;
[0028] At a platform node on another distributed ledger network, receiving a transaction message to resolve an entity ID of a counterparty to a contract transaction on another distributed ledger network;
[0029] Receive a transaction message and instructions for resolving an entity ID from a platform node on another distributed ledger network;
[0030] At the hub server, resolve the entity ID of the contract counterparty on another distributed ledger network;
[0031] At a platform node on another distributed ledger network, receiving a transaction message indicating that the contract has been executed;
[0032] Sending a resolution message to the hub server confirming that the contract on the other distributed ledger network has been executed;
[0033] parsing, by the hub server, a request from a platform network node on a first distributed ledger network to verify that a plurality of entities that are counterparties to a contract transaction on the first distributed ledger are counterparties to a contract transaction on another distributed ledger network; and
[0034] The verification message is sent to a platform node on the first distributed ledger network. The method can further include: obtaining business entity enterprise statistics information about the transaction counterparty from a business information database server through the hub server; and outputting the business entity enterprise statistics information to a platform node on another distributed ledger network. The business entity enterprise statistics information can include business contact information.
[0035] In one embodiment, the method includes: authenticating an entity to a platform; storing a verified network ID of the entity in an entity data store; and sending a verified private key to the entity. The method can further include: receiving a message including information about a new network ID of a distributed ledger network, wherein the message is signed with a new private key; wherein the message is appended with a verified network ID message detailing the verified network IDs and a signature of the verified network ID message with a corresponding verified private key; the platform host verifies the signature of the verified private key; the platform host verifies the signature of the new key; the platform host verifies a checksum of the new ID with the distributed ledger network identified in the new network ID; and the platform host adds the new network ID to the entity's ID resolution data store.
[0036] In one embodiment, the present invention describes a system for authenticating entities on a plurality of immutable distributed ledgers, comprising a network computer comprising: a hub server; an ID resolution server comprising an identity resolution database lookup table; a memory for storing a database and program instructions; and a processor device operable to execute program instructions that enable actions, including:
[0037] For each of the plurality of entities, generate a data store and an entity ID of the entity;
[0038] In data storage, multiple public key distributed ledger addresses are linked to each entity ID;
[0039] In data storage, link each public key distributed ledger address to the distributed ledger network to which they belong;
[0040] storing a data store in an identity resolution database lookup table, the identity resolution database lookup table comprising a plurality of data stores; and
[0041] connecting a plurality of distributed ledger network platform nodes on each of the respective plurality of distributed ledger networks to the hub server;
[0042] The system is configured to perform identity resolution for a single entity on multiple distributed ledger networks.
[0043] The system can be further configured to execute program instructions for enabling actions, including: embedding multiple distributed ledger network platform nodes into respective multiple distributed ledger networks. The hub server can be connected to a business information database server. The system can be further configured to execute program instructions for enabling actions, including: receiving a request for business information about a counterparty to a transaction on the distributed ledger network at one of the platform nodes on one of the distributed ledger networks; sending the request from the platform node to the hub server; and identifying the entity ID of the counterparty to the transaction at the ID resolution server. The system can be further configured to execute program instructions for enabling actions, including: automatically executing transactions to an immutable distributed ledger through the platform node.
[0044] The system can be further configured to execute program instructions for enabling actions, including: routing the request from the hub server to a business information database server; obtaining business entity enterprise statistics information about the transaction counterparty from the business information database server; and outputting the business entity enterprise statistics information to a platform node. The business entity enterprise statistics information can include business contact information. The system can be further configured to execute program instructions for enabling actions, including: automatically executing a transaction to an immutable distributed ledger through a platform node.
[0045] In one embodiment, the system can be further configured to execute program instructions for enabling actions, including: verifying, by the hub server, that multiple entities that are counterparties to a contract transaction on a first distributed ledger are counterparties to a contract transaction on another distributed ledger network. The system can be further configured to execute program instructions for enabling actions, including:
[0046] receiving, from a platform network node on a first distributed ledger network, a request to verify that a plurality of entities that are counterparties to a contract transaction on the first distributed ledger are counterparties to a contract transaction on another distributed ledger network;
[0047] Associating, at the hub server, a contract on the first distributed ledger network with a contract on another distributed ledger network;
[0048] At a platform node on another distributed ledger network, receiving a transaction message to resolve an entity ID of a counterparty to a contract transaction on another distributed ledger network;
[0049] Receive a transaction message and instructions for resolving an entity ID from a platform node on another distributed ledger network;
[0050] At the hub server, resolve the entity ID of the contract counterparty on another distributed ledger network;
[0051] At a platform node on another distributed ledger network, receiving a transaction message indicating that the contract has been executed;
[0052] Sending a resolution message to the hub server confirming that the contract on the other distributed ledger network has been executed;
[0053] parsing, by the hub server, a request from a platform network node on a first distributed ledger network to verify that a plurality of entities that are counterparties to a contract transaction on the first distributed ledger are counterparties to a contract transaction on another distributed ledger network; and
[0054] The verification message is sent to a platform node on the first distributed ledger network. The system can be further configured to execute program instructions for enabling actions, including: obtaining business entity enterprise statistics information about the transaction counterparty from a business information database server through the hub server; and outputting the business entity enterprise statistics information to a platform node on another distributed ledger network. The business entity enterprise statistics information can include business contact information.
[0055] In one embodiment, the system can be further configured to execute program instructions for enabling actions, including: authenticating an entity to the platform; storing a verified network ID of the entity in the entity data store; and sending a verified private key to the entity. The system can be further configured to execute program instructions for enabling actions, including: receiving a message including information about a new network ID of a distributed ledger network, wherein the message is signed with a new private key; wherein the message is appended with a verified network ID message detailing the verified network IDs and a signature of the verified network ID message with the corresponding verified private key; the platform host verifies the signature of the verified private key; the platform host verifies the signature of the new key; the platform host verifies a checksum of the new ID with the distributed ledger network identified in the new network ID; and the platform host adds the new network ID to the entity's ID resolution data store.
[0056] Further objects, features and advantages of the present invention will be understood with reference to the following description of the drawings and detailed description. BRIEF DESCRIPTION OF THE DRAWINGS
[0057] Figure 1A is a data storage diagram according to the present invention, illustrating how multiple distributed ledger addresses of multiple distributed ledger networks can all be aggregated or mapped to a single entity identity;
[0058] Figure 1B Is adopted Figure 1A Instances of searching and parsing the data storage graph in;
[0059] Figure 2Ais a system architecture according to the present invention, wherein a plurality of nodes are embedded in a plurality of untrusted ledger networks and communicate with a hub server according to the present invention, the hub server communicating with an identification and resolution server;
[0060] Figure 2B An exemplary client computer according to the present invention is shown;
[0061] Figure 2C An exemplary network computer according to the present invention is shown;
[0062] Figure 3 is a block diagram illustrating authentication of an entity through a registered communication protocol according to the present invention;
[0063] Figure 4 is a block diagram illustrating authentication of an entity through communications according to the present invention;
[0064] Figure 5 is a block diagram illustrating the use of a verified identity to verify a new distributed ledger identity;
[0065] Figure 6 is a block diagram illustrating retrieval of a network identification from a system according to the present invention;
[0066] Figure 7 is a block diagram illustrating smart contract request parsing according to the present invention;
[0067] Figure 8 is a diagram illustrating the use of an immutable distributed ledger or blockchain and smart contracts in accordance with the present invention;
[0068] Fig. 9 is a diagram illustrating the benefits of an immutable distributed ledger or blockchain address registry according to the present invention;
[0069] Fig.10 is a block diagram illustrating identifying a business using its immutable distributed ledger address in accordance with the present invention. DETAILED DESCRIPTION
[0070] Various embodiments are described more fully below in conjunction with the accompanying drawings, which form a part of this specification and illustrate specific embodiments in which the invention can be practiced. However, these embodiments can be embodied in many different forms and should not be construed as limiting the invention to the embodiments set forth herein; on the contrary, the purpose of providing these embodiments is to fully and completely understand the invention and to fully convey the scope of these embodiments to those skilled in the art. Various embodiments can be, in particular, methods, systems, media or devices. Accordingly, various embodiments can take the form of hardware embodiments, software embodiments, or embodiments combining software and hardware aspects.
[0071] In the specification and claims, the following terms have the meanings expressly associated herein, unless the context clearly dictates otherwise. The term "herein" refers to the specification, claims, and drawings associated with this application. As used herein, the phrases "in at least one embodiment" or "in one embodiment" may, but do not necessarily, refer to the same embodiment. In addition, as used herein, the phrase "in another embodiment" may, but does not necessarily, refer to a different embodiment. Therefore, as described below, the various innovative embodiments described herein can be easily combined without departing from the scope or spirit of these innovations.
[0072] In addition, as used herein, the term "or" is an inclusive "or" operator and is equivalent to the term "and / or", unless the context clearly dictates otherwise. The term "based on" is not exclusive, but allows for being based on other factors not described, unless the context clearly dictates otherwise. In addition, in the specification, the meanings of the terms "a", "an", and "the" include plural references. The phrase "in..." includes "in..." and "on...".
[0073] As used in this application, the terms "component", "module" and "system" are intended to refer to a computer-related entity, which entity is hardware, a combination of hardware and software, software, or software in execution. For example, a component can be, but is not limited to, a process running on a processor, a processor, an object, an executable file, an execution thread, a program, and / or a computer. For example, an application running on a server and a server can both be components. One or more components can reside within a process and / or thread of execution, and a component can be located on one computer and / or distributed between two or more computers.
[0074] In addition, for illustrative purposes, the detailed description of the present invention describes various embodiments that include the methods and can be implemented using one or more devices (such as processing devices coupled to electronic media). The embodiments can be stored on electronic media (electronic memory, RAM, ROM, EEPROM) or programmed as computer code (such as source code, object code or any suitable programming language) for execution by one or more processors operating in conjunction with one or more electronic storage media.
[0075] One embodiment involves creating a centralized system that is capable of writing to a distributed ledger by: (a) providing a unique identifier for the business that needs to be identified, (b) appending basic company identification information provided by a trust institution, and (c) linking all known public keys in various distributed ledger networks to the unique identifier created to identify the company.
[0076] In one embodiment, a verification system is established to ensure that the public key linked to the master company identifier does in fact belong to the company. This may involve different multi-factor verification schemes, including: (a) participating in the distributed ledger network and requesting that a specific payment or data be sent as a transaction to the address of the platform or verification host, indicating that the company owns the relevant public key, (b) having the company cryptographically sign the message with the key pair they want to link and place that signature in the space under their Internet domain, proving that they own both the key and the domain, (c) sending a message owned by the company via text to a known phone and receiving a cryptographic signature in response, and (d) speaking to someone within the company at the verified company phone number.
[0077] In another embodiment, a first remote device sends a request to a server via a network protocol. The request includes an ID or distributed ledger address of a personal distributed ledger account. The ID can be, for example, a number assigned by a business entity information platform, such as a DUNS number, or the ID can be another unique identifier, or both. The server logic will perform a lookup for the ID or address, and if the ID or address is found, information associated with the ID or address will be returned to the requester, including the specific distributed ledger network to which the ID belongs, the entity to which the ID belongs, the network IDs of other distributed ledgers on the same network or other networks, the distributed ledger networks to which these IDs each belong, and business statistics or other attribute data associated with the entity that owns the ID.
[0078] In yet another exemplary embodiment, the first remote device has a request similar to the first method, but also includes information for filtering the response to retrieve only information about a specific distributed ledger network or only business statistics about an entity with an ID. The server logic can be configured to perform a lookup for the ID or address and return only the information specified by the first remote device that was found.
[0079] In yet another exemplary embodiment, if an entity wishes to add an ID or address to a lookup table on a server, they can submit a request to the server via a network protocol that includes the ID or address they wish to register as a parameter. The system is configured to provide a response including a unique data string to the requester. The requester uses a private key associated with the ID or address to generate a signature for the data and uploads the signature as a file to the domain they register to control. The requester notifies the server platform that the data is available in its domain by any means of communication. The server is configured to download and verify the signature based on the address and unique string. If the signature is verified, the ID or address is associated with the entity. Otherwise, the system is configured to reject the request and will not take any action.
[0080] In yet another exemplary embodiment, if an entity wishes to add an ID or address to the lookup table on the server, they are able to contact the owner of the server and the owner can verify and disambiguate the identity of the entity through methods such as a registered phone number, a text message to a registered mobile phone, a registered email address, or a personal visit to the entity. Once the entity is identified, the verification of the distributed ledger ID can be verified by decrypting a unique message encrypted with the associated ID or verifying the signature of a unique message signed with a private key and verifying with the ID, or the entity broadcasts a valid transaction on the distributed ledger with the unique data agreed upon with the server owner.
[0081] In another exemplary embodiment, if an entity wishes to add a new ID or address to a lookup table on a server and has already registered a verified ID in the lookup table, the entity can simultaneously verify itself and the new key they are registering by signing the instruction data piece with the new key and the previously verified key. Otherwise, they can broadcast a transaction on the new distributed ledger with a signature from the verified key included in the data payload of the transaction. This can be included as data in the smart contract, such as in the OP_RETURN portion of the transaction in one embodiment, depending on the distributed ledger approach.
[0082] In another exemplary embodiment, if a first entity wishes to automatically cause and resolve transactions on two or more disparate distributed ledgers, and wants to ensure that they are transacting with the same entity on those ledgers, or at least that they are transacting with entities that they can identify, the first entity can code certain logic in the smart contract, thereby allowing the platform host to make the necessary state changes. The platform is configured to act as an Oracle database, and if the Oracle database can verify the identity in a way that satisfies the intent of the contract, the necessary state changes to perform the smart contract are made in the transaction. These state changes can be encoded as updates to the smart contract, or the necessary signatures to make multi-signature transactions valid can be provided. The platform is configured to use a lookup table to ensure that the routing payment transaction is correctly output, and can check the smart contract state to verify that the contract party ABC on the distributed ledger XYZ is the same entity as the contract party DEF on the distributed ledger UVW.
[0083] In an exemplary embodiment, if a first entity wishes to automate business rules in transactions that are about to occur and resolve on any number of distributed ledgers, the first entity can encode the logic into a smart contract that allows the system to make the necessary state changes. The platform is configured to act as an Oracle database, providing the necessary state changes to the smart contract to be performed in the fulfillment transaction. The system is configured to use a lookup table that is linked to enterprise statistics and other attributes. The system is configured to read specifications or logic from the smart contract and determine whether to update the state through the transaction, or the system can be configured to provide data to the smart contract and allow the contract's own internal logic to determine whether the contract can proceed.
[0084] For example, in one embodiment, the smart contract is set to be discoverable by anyone in the network, and anyone in the network can join as a counterparty. When a party on the network discovers the contract and wishes to fulfill the role of a counterparty, the party will submit a transaction, declaring itself a candidate for the counterparty. The transaction changes the state of the smart contract. The state changes the event that triggers the node server to listen. The event contains information about the party that just submitted the transaction and the contract terms that the counterparty must fulfill. An example of the contract terms may be that the counterparty must have a minimum credit risk score, or that they are in good standing for a standard terrorist watch list. The contract is coded to continue until the node submits another transaction to declare that the counterparty has fulfilled the contract terms.
[0085] In another embodiment, a smart contract is established between two parties, and the contract is coded to not proceed until a contract is reviewed on another blockchain and the parties to the separate contract are verified to be the same as the parties to the first contract. The node will submit a transaction to the contract to assert the authenticity of the identities of both parties. The node is an active member of the blockchain, so the code can dictate that only the node is allowed to conduct this specific transaction.
[0086] In one embodiment, Figure 1A The logical architecture of the data store 100 according to the present invention is shown, depicting how multiple distributed ledger addresses of multiple distributed ledger networks can all be aggregated or mapped to a single entity identity.
[0087] In FIG. 1 , a unique entry as an entity ID 101 is entered into the data store to represent and identify a legal entity that can be used in a lookup table. The entity has a distributed ledger address 102a-102d that is a digital representation or public key. The data store is configured to send these public key addresses to the unique entry 101. In addition, the data store contains information about various distributed ledger networks 103a-103d, and the distributed ledger addresses 102a-102d are linked to the networks where they represent unique entries. In addition, in one embodiment, the system is configured to link the entity ID 101 to a unique business information identifier, such as a DUNS number 106 or other unique identifier. The structure of the data store 100 is configured to allow for faster and more efficient entity searches and identity resolution, and provides an implementation structure for utilizing multiple immutable distributed ledger networks as described herein.
[0088] For example, Figure 1B An exemplary graphical image for a query on a data store is shown. The query is configured to efficiently find an entity by searching for an address, and then build information about the entity, including all other addresses associated with the entity and metadata defining those addresses and networks 104. In this example, the query is formatted as RDF triples written in Turtle notation, but other exemplary formats can be used.
[0089] PREFIX dnb:<http: / / onto.dnb.com / schema#>
[0090] PREFIX blockchainId:<http: / / onto.dnb.com / blockchainId#>
[0091] PREFIX entity:<http: / / onto.dnb.com / entityId#>
[0092] PREFIX:blockchainInstance:
[0093] <http: / / onto.dnb.com / blockchainInstance#>
[0094] select? entity? companyName? duns? blockchainId? networkName? isVerified
[0095] ?networkTechType where{
[0096] ?interimBCId rdf:value'<address to search for>'.
[0097] ? entity dnb:hasBlockchainId? interimBCId.
[0098] ? entity dnb:hasBlockchainId? blockchainURI.
[0099] ? blockchainURIrdf:value? blockchainId.
[0100] ? blockchainURIdnb:isMemberOf? network.
[0101] ? blockchainURIdnb:isVerified? isVerified.
[0102] ? networkdnb:hasName? networkName.
[0103] ? networkdnb:isTechnologyType? techType.
[0104] ? techTypednb:hasName? networkTechType.
[0105] ? entitydnb:hasName? companyName.
[0106] ?entitydnb:hasDuns?duns.
[0107] As shown in this example, for the embodiments described herein, the structure of the data store 100 allows for the utilization of multiple immutable distributed ledger networks, including, inter alia, smart contract execution and entity and transaction verification as described herein. It is also configured for fast and efficient entity search and identity resolution on the immutable distributed ledger. This in turn can be used to enrich enterprise statistics, inter alia, for verifying and resolving entities via the database.
[0108] Figure 2A A system architecture 200 according to the present invention is depicted, wherein a plurality of platform nodes are embedded in a plurality of untrusted ledger networks and communicate with a hub server 112 , which communicates with an identification and resolution server 201 .
[0109] The immutable distributed ledger 203 is a public or private shared ledger for recording the history of e-commerce transactions that occur in a peer-to-peer (P2P) business network. An immutable distributed ledger is an instance of an immutable distributed transaction ledger. An immutable distributed ledger network is a decentralized system for asset exchange and transaction records. An immutable distributed ledger network can use "proof of work" or other consensus mechanisms as the basis for credibility, accountability, and transparency. However, an immutable distributed ledger network does not have a trust basis outside the network boundaries. In one embodiment, each licensed node of the network has a replica of the ledger, and within the network, all events on the ledger are synchronized and immutable across all nodes that form the network, resulting in complete transparency for all node members.
[0110] The transaction system of an immutable distributed ledger can include digital signatures, cryptographic hashes, timestamp servers, and a decentralized consensus protocol that member nodes use to reach consensus on the contents of the ledger. Integrity, privacy, and security are designed into the public ledger. For example, a blockchain ledger consists of data blocks (called packets) that are digitally recorded and cannot be altered. These digitally recorded data "blocks" are stored in a linear chain. Each block in the chain contains cryptographically hashed data (for example, for cryptocurrency transactions or smart contract executables). The hashed data block references the previous block in the chain (before it), ensuring that all data in the entire "blockchain" remains unchanged without being tampered with. The immutable distributed ledger peer-to-peer network is resilient and robust due to its decentralized topology. Messages are exchanged between network participants on a best-effort basis as member nodes dynamically join or leave the network.
[0111] Exemplary immutable distributed ledger networks include Bitcoin, Ethereum, Ripple, Hyperledger, Stellar, IBM Blockchain, and other enterprise solutions.
[0112] For example, Ethereum is a programmable, immutable distributed ledger blockchain. Ethereum allows users to create their own operations of arbitrary complexity. In this way, Ethereum's immutable distributed ledger platform is able to support many different types of decentralized blockchain applications, including but not limited to cryptocurrencies and smart contracts. Ethereum includes a set of protocols that define a platform for decentralized applications. The platform includes the Ethereum Virtual Machine ("EVM"), which is capable of executing code of arbitrary algorithmic complexity. Developers can create applications using a friendly programming language modeled after existing languages (such as JavaScript and Python) and run them on the EVM.
[0113] As another example, the IBM blockchain implementation called Hyperledger Fabric is configured for users to create their own operations of arbitrary complexity. Permissions in the Hyperledger Fabric network are inherent to the Hyperledger Fabric network. Instead of allowing anyone to participate by default, the root certificate authority must grant participation permissions to any participant in the Hyperledger Fabric network.
[0114] Hyperledger Fabric also allows transactions to be submitted through channels; users can only create and send transactions to specific parties, not to the entire network.
[0115] An immutable distributed ledger or blockchain consists of a peer-to-peer network protocol. An immutable distributed ledger database is maintained and updated by many nodes connected to the network. For example, nodes in the same network are able to run and execute the same instructions to achieve massive computational parallelism across the entire network. This maintains consensus and immutability of transactions and events on the ledger. Decentralized consensus gives blockchains additional fault tolerance, ensures zero downtime, and makes data stored on the immutable distributed ledger immutable and censorship-resistant.
[0116] Nodes can download an immutable distributed ledger application that provides a gateway to decentralized applications on the network blockchain. For example, the immutable distributed ledger application can be configured to hold and protect crypto assets built on the blockchain, and to encode, deploy and employ smart contracts, especially self-executing ones.
[0117] On the immutable distributed ledger network 203, users can set up nodes that replicate the necessary data of all nodes to reach an agreement and be compensated by the users. This allows user data to remain private and makes applications decentralized. Immutable distributed ledgers also allow developers to create particularly fully automated applications that, for example, store registries of debts or promises, send messages, and transfer funds according to predetermined instructions, including encoding those instructions given earlier (for example, a will or futures contract).
[0118] It should be appreciated that one or more embodiments of the platform as described herein are configured to utilize multiple independent private or public immutable distributed ledger networks, including those referenced herein.
[0119] The immutable distributed ledger server computers include virtually any network computer capable of sharing a ledger across a network and configured as an immutable distributed ledger node, including the client computers and network computers described herein. The immutable distributed ledger server computers are distributed across one or more different network computers in a peer-to-peer architecture. Other configurations and architectures are also contemplated by the present invention.
[0120] In one embodiment, the immutable distributed ledger network 203 can be private to the parties involved, with permission to allow only authorized parties to join, and can use encryption techniques to increase security, ensuring that participants only see what they are allowed to see. The shared ledger is replicated and distributed across network computers. Transactions are immutable (cannot be changed) and final. Computers that can be arranged to operate as immutable distributed ledger server computers include various network computers, including but not limited to personal computers, desktop computers, multiprocessor systems, microprocessor-based or programmable consumer electronics, network PCs, server computers, network appliances, and the like.
[0121] Figure 2A It is a representation of an implementation scheme of the physical architecture of a computer server. The client software "node" 205 runs on a machine that is part of a private or public network 203. Through one of the several mechanisms described herein, another party in the same network will communicate the demand for business entity information and distributed ledger identification information to the node 205. The node communicates the desired request to the centralized hub server 112 for the platform host. An exemplary request is based on the public key 102 to identify the counterparty in the transaction, and can also include a request to enrich the counterparty data using enterprise statistics or risk scoring information from the business entity information database 206. In one embodiment, a way to give a request to the node 205 is through an event system built into the distributed ledger 203. The node software 205 can be subscribed to listen for events designated as important, and the event can trigger the software 205 to communicate with the hub server 112. Requests can also be given directly to the platform node 205 through transactions. If the transaction clearly identifies the node address of the platform host on the network 203, the platform node software 205 will use it as an event, which can then trigger the software to perform necessary communications with the hub server 112.
[0122] The hub server 112 is configured to translate requests and route specific requests to subsequent correct services. The hub server 112 can include decision logic configured to read request codes and determine request information, such as how the party is sending the request via the node and requesting instructions. For example, the hub server 112 can confirm identity X, confirm that the party is looking for ID Y, and provide other request information available to the platform (such as business scores, credit scores, business statistics scores, business statistics, etc.). Trust weights can be applied to several factors, such as whether a party has verified itself or has confirmed to the platform in other ways. The hub server 112 asks who is sending, and the logic confirms the sender and searches for the rights of the company. The company confirms that they want to claim to be unique and instantiates the new company at the moment of transaction verification.
[0123] Verification of a company may be asynchronous – for example, one company verifies as a flow request (“yes you are verified”) and another company verifies as %%. In one embodiment, the platform may know about another company but not fully verify it. For example, the platform may have confirmed that another company is on one or more distributed ledgers, but the other company has not yet fully verified itself to the platform or has not yet identified itself to the requester's target distributed ledger. The distributed ledger address 102 is passed to the ID resolution server 201, which is configured to access and search the lookup table of the entity resolution data store 100 shown in Figure 1 to return the entity ID (e.g., DUN code 106), network identity 103, and other distributed ledger addresses 102a...102n to the hub server 112.
[0124] In another embodiment, trust weights can be applied to other factors, such as voluntary transparency. For example, Hyperledger allows users to hide information, while Ethereum does not. Trust weights can be applied based on this transparency and other factors, such as whether a party chooses to share ledger information that should be hidden in the platform's backbone.
[0125] With the acquired entity ID, the hub server 112 can make requests to other databases and servers (e.g., business entity data server 216) to enrich data about the found transaction counterparty. When the business entity data server has satisfied and enriched the information requested from the node 205, the hub server passes the information back to the node server 205. The platform node server 205 is configured to then create a transaction and transmit the transaction to a private or public network that satisfies the data request.
[0126] The business entity data server 216 can also include a business entity information database 206 of company / business entity robust data, as described herein, to map to counterparty entity information and enrich counterparty entity information with company business statistics from the business statistics database 206. In at least one embodiment described above, the business statistics from the business entity information database 206 can include scores or other rankings of companies. In at least one embodiment described above, the business entity information database 206 can include one or more databases linked to business entity information, such as an employee database including employee names and job titles or management codes, a contact database of company employee contacts (e.g., email, mobile device ID, phone), or a cookie database that compiles data from cookies used by business entities for digital tracking and digital marketing. Data from the database 206 can be mapped to companies using a mapping module. In at least one embodiment, if a company name is not identified in the business entity information database, the system can be configured to generate an identifier and generate one or more business statistics records for the company. In one embodiment, entity information can be enriched with company and business link information mappings, for example, linking business relationships (e.g., family tree relationships, such as parent-subsidiary, corporate family, global headquarters, branches). For non-limiting examples of some corporate entity data linking, generating corporate statistical records and scores for a company, and data integration by the business entity information database 206 and the business analysis server, see U.S. Patent No. 7,822,757, filed on February 18, 2003, entitled "System and Method for Providing Enhanced Information", U.S. Patent No. 8,346,790, filed on September 28, 2010, entitled "Data Integration Method and System", and U.S. Patent No. 8,036,907, filed on December 23, 2003, entitled "Method and System for Linking Business Entities Using Unique Identifiers", the entire text of each of which is incorporated herein by reference.
[0127] Figure 2B An embodiment of a client computer 207 that may be included in a system implementing certain embodiments is shown. The client computer 207 may include components such as Figure 2A The components shown may be more or less. However, the components shown are sufficient to disclose an illustrative embodiment for practicing the present invention. The client computer 207 may, for example, represent an embodiment of at least one client computer of a distributed ledger network party, a transaction counterparty, or a business entity using the platform.
[0128] As shown, the client computer 207 includes a processor 202 that communicates with a mass storage device 226 via a bus 234. In some embodiments, the processor 202 may include one or more central processing units (CPUs). The client computer 207 also includes a power supply 228, one or more network interfaces 236, an audio interface 238, a display 240, a keypad 242, an illuminator 244, a video interface 246, an input / output interface 248, a tactile interface 250, and a global positioning system (GPS) transceiver 232.
[0129] The power supply 228 provides power to the client computer 207. Rechargeable or non-rechargeable batteries can be used for the power supply. It can also be powered by an external power source, such as an alternating current (AC) adapter or an active docking station that replenishes and / or recharges the battery.
[0130] The client computer 207 may optionally communicate with a base station (not shown), or directly with another computer. The network interface 236 includes circuitry for coupling the client computer 207 to one or more networks and is configured to cooperate with one or more communication protocols and technologies, including but not limited to GSM, CDMA, TDMA, GPRS, EDGE, WCDMA, HSDPA, LTE, User Datagram Protocol (UDP), Transmission Control Protocol / Internet Protocol (TCP / IP), Short Message Service (SMS), WAP, Ultra-Wideband (UWB), IEEE 802.16 Worldwide Interoperability for Microwave Access (WiMax), Session Initiation Protocol / Real-time Transport Protocol (SIP / RTP), or any of a variety of other wireless communication protocols. The network interface 236 is sometimes referred to as a transceiver, a transceiver device, or a network interface card (NIC).
[0131] The audio interface 238 is arranged to generate and receive audio signals, such as human voice. For example, the audio interface 238 can be coupled to a speaker and a microphone (not shown) to enable communication with other people and / or generate audio confirmation of certain actions.
[0132] Display 240 may be a liquid crystal display (LCD), gas plasma, light emitting diode (LED), organic LED, or any other type of display used with a computer. Display 240 may also include a touch-sensitive screen arranged to receive input from an object such as a stylus or a finger of a human hand.
[0133] The keypad 242 may include any input device arranged to receive input from a user. For example, the keypad 242 may include buttons, a numeric dial, or a keypad. The keypad 242 may also include command buttons associated with selecting and sending images.
[0134] Illuminator 244 can provide status indication and / or provide illumination. Illuminator 244 can remain active for a specific period of time or in response to an event. For example, when illuminator 244 is active, it can illuminate the backlight of the buttons on keypad 242 and remain on when the client computer is powered on. Similarly, when performing a specific action, such as dialing another client computer, illuminator 244 can illuminate the backlight of these buttons in various patterns. Illuminator 244 can also cause a light source positioned within a transparent or translucent shell of the client computer to illuminate in response to an action.
[0135] The video interface 246 is arranged to capture video images, such as still photos, video clips, infrared videos, etc. For example, the video interface 246 can be coupled to a digital video camera, a webcam, etc. The video interface 246 can include a lens, an image sensor, and other electronic devices. The image sensor can include a complementary metal oxide semiconductor (CMOS) integrated circuit, a charge coupled device (CCD), or any other integrated circuit for sensing light.
[0136] The client computer 207 also includes an input / output interface 248 for communicating with external devices such as a head mounted device or Figure 2A The input / output interface 248 can utilize one or more communication technologies, such as USB, infrared, Bluetooth, etc. TM (Bluetooth), etc.
[0137] The tactile interface 250 is arranged to provide tactile feedback to the user of the client computer. For example, the tactile interface 250 may be employed to vibrate the client computer 207 in a particular manner when another user of the computer is calling. In some embodiments, the tactile interface 250 may be optional.
[0138] The client computer 207 may also include a GPS transceiver 232 to determine the physical coordinates of the client computer 207 on the surface of the earth. In some embodiments, the GPS transceiver 232 may be optional. The GPS transceiver 232 typically outputs the location as a latitude value and a longitude value. However, the GPS transceiver 232 can also use other geolocation mechanisms, including but not limited to triangulation, assisted GPS (AGPS), enhanced observed time difference (E-OTD), cell identifier (CI), service area identifier (SAI), enhanced timing advance (ETA), base station subsystem (BSS), etc., to further determine the physical location of the client computer 207 on the surface of the earth. It should be understood that under different conditions, the GPS transceiver 232 can determine the physical location of the client computer 207 within a millimeter range; while in other cases, the determined physical location may be less accurate, such as within a meter or significantly greater distances. However, in one embodiment, the client computer 207 can provide other information that can be used to determine the physical location of the computer through other components, such as a media access control (MAC) address, an IP address, etc.
[0139] The mass storage 226 includes random access memory (RAM) 204, read only memory (ROM) 222, and other storage mechanisms. The mass storage 226 illustrates an example of a computer-readable storage medium (device) for storing information such as computer-readable instructions, data structures, program modules, or other data. The mass storage 226 stores a basic input / output system (BIOS) 224 for controlling the low-level operation of the client computer 207. The mass storage also stores an operating system 256 for controlling the operation of the client computer 207. It should be appreciated that this component may include an operating system such as UNIX or LINUX. TM versions of general-purpose operating systems or such as Windows Mobile from Microsoft Corporation TM 、iOS by Apple Corporation TM 、Android by Google Corporation TM or The dedicated client of the operating system communicates with the operating system. The operating system may include or interface with a Java virtual machine module that can control hardware components and / or operating system operations through a Java application.
[0140] The mass storage 226 further includes one or more data storage areas 208 that the client computer 207 can utilize to store applications 214 and / or other data, among other things. For example, the data storage area 208 can also be used to store information describing various capabilities of the client computer 207. This information can then be provided to another computer based on any of a variety of events, including being sent as part of a header during a communication, being sent upon request, and the like. The data storage area 208 can also be used to store social network information, including address books, friend lists, aliases, user profile information, and the like. Additionally, the data storage area 208 can also store any of messages, web page content, or various user-generated content. At least a portion of this information can also be stored on another component of the client computer 207, including, but not limited to, a processor-readable storage medium 230, a disk drive, or other computer-readable storage device (not shown) within the client computer 207.
[0141] The processor-readable storage medium 230 may include volatile, non-volatile, removable and non-removable media implemented using any method or technology for storing information, such as computer-readable instructions or processor-readable instructions, data structures, program modules or other data. Examples of computer-readable storage media include RAM, ROM, electrically erasable programmable read-only memory (EEPROM), flash memory or other storage technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical disk storage, magnetic cassettes, magnetic tapes, magnetic disk storage or other magnetic storage devices, or any other physical medium that can be used to store the desired information and can be accessed by a computer. In this article, the processor-readable storage medium 230 may also be referred to as a computer-readable storage medium and / or a computer-readable storage device.
[0142] Applications 214 may include computer executable instructions that, when executed by client computer 207, send, receive, and / or otherwise process network data. Network data may include, but is not limited to, messages (e.g., SMS, Multimedia Messaging Service (MMS), Instant Messaging (IM), email, and / or other messages), audio, video, and the ability to communicate with another user of another client computer. Applications 214 may, for example, include browsers 218 and other applications 220. Other applications 220 may include, but are not limited to, calendars, search programs, map programs, email clients, IM applications, SMS applications, Voice over Internet Protocol (VOIP) applications, contact managers, task managers, transcoders, database programs, word processing programs, security applications, spreadsheet programs, games, search programs, and the like.
[0143] The browser 218 may include nearly any application configured to receive and display graphics, text, multimedia, messages, etc. using nearly any Web-based language. In one embodiment, the browser application is enabled to display and send messages using HDML, WML, WML, Script, JavaScript, SGML, HTML, XML, etc. However, any of a variety of other Web-based programming languages may be used. In one embodiment, the browser 218 may enable a user of the client computer 207 to communicate with a web application such as a web browser. Figure 2A Communicates with another network computer in the central server computer 112.
[0144] The application 214 may also include a widget controller 210 and one or more widgets 212. The widget 212 may be a collection of content that the hub server computer 112 provides to the client computer 207. The widget controller 210 may be a program that the hub server computer 112 may provide to the client computer. The widget controller 210 and the widget 212 may run as local client computer applications, or they may run as web browser-based applications in the browser 218. Moreover, the widget controller 210 and the widget 212 may be arranged to run as local applications or web browser applications or a combination thereof. In at least one embodiment, these applications and their components may be configured as widgets.
[0145] The applications 214 can also include platform applications 215. The platform applications 215 can be programs that can be provided to client computers by a platform, such as the hub server computer 112, and supported by an application server of the hub server computer 112. The platform applications 215 can run as local client computer applications, or can run in a browser 218 as a web browser-based application. The platform applications 215 can also be arranged to run as a combination of local applications and web browser applications. The platform applications 215 and their tools and modules can be implemented in a similar manner to the combination of the platform application 215 and the web browser application. Figures 1A to 2A and Figures 3 to 10 Those processes or parts of the processes described above to perform at least some of their actions.
[0146] The immutable distributed ledger application 217 is configured to provide a gateway to decentralized applications on the immutable distributed ledger platform and act as a node on the immutable distributed ledger platform. The immutable distributed ledger application 217 is configured to hold and protect crypto assets built on the platform, and to encode, deploy and employ smart contracts, especially self-executing ones.
[0147] The immutable distributed ledger application 217 can include a data management tool 256 configured to log application usage and transaction data to the immutable distributed ledger network 203. The data management tool 256 can be configured to communicate with the immutable distributed ledger computer server and the hub server computer 112 to control, share, accept and synchronize data. In one embodiment, the data management tool 256 can include a logging tool configured to log and store customer data in one or more databases (e.g., customer database 209), including customer transactions recorded on the immutable distributed ledger network 203. The logging tool can also be configured to record transactions between clients on the immutable distributed ledger 211. As described herein, in at least one embodiment, the platform includes an immutable distributed ledger application 217, which can operate as a platform node server 205, which is a computer server node of a licensed immutable distributed ledger.
[0148] The immutable distributed ledger application 217 can include a transaction interface tool 264 for entering transactions recorded on the immutable distributed ledger, including transactions such as smart contracts and / or cryptocurrency transactions.
[0149] Illustrative Network Computer
[0150] Figure 2C An embodiment of a network computer 350 according to an embodiment of the present invention is shown. The network computer 350 may include more or fewer components than those shown. However, the components shown are sufficient to disclose an illustrative embodiment for practicing the innovations described herein. The network computer 350 can be configured to operate as a server, client, peer, host, or any other computer. The network computer 350 can, for example, represent the hub server computer 112, the business entity data server 206, the node server 205, and the identity resolution server 201.
[0151] Network computer 350 includes processor 307, processor-readable storage medium 328, network interface unit 330, input / output interface 332, hard disk drive 334, video display adapter 336, and memory 326, all of which communicate with each other via bus 338. In some embodiments, processor 307 may include one or more central processing units.
[0152] like Figure 2C As shown, network computer 350 can also communicate with the Internet or some other communication network via network interface unit 330, which is constructed to cooperate with various communication protocols including TCP / IP protocol. Network interface unit 330 is sometimes called a transceiver, transceiver device or network interface card (NIC).
[0153] The network computer 350 also includes an input / output interface 332 for connecting to external devices such as a keypad or Figure 2C The input / output interface 332 can utilize one or more communication technologies, such as USB, infrared, Bluetooth, etc. TM wait.
[0154] The memory 326 typically includes RAM 340, ROM 322, and one or more permanent mass storage devices, such as a hard disk drive 334, a tape drive, an optical drive, and / or a floppy disk drive. The memory 326 stores an operating system 356 for controlling the operation of the network computer 350. Any general purpose operating system may be employed. A basic input / output system (BIOS) 324 is also provided for controlling the low-level operation of the network computer 350.
[0155] The memory 326 may include a processor-readable storage medium 328, but is shown separately in the figure. The processor-readable storage medium 328 may be referred to as and / or include a computer-readable medium, a computer-readable storage medium, and / or a processor-readable storage device. The processor-readable storage medium 328 may include volatile, non-volatile, removable and non-removable media implemented using any method or technology for storing information, such as computer-readable instructions, data structures, program modules or other data. Examples of processor-readable storage media include RAM, ROM, EEPROM, flash memory or other storage technology, CD-ROM, digital versatile disk (DVD) or other optical disk storage, magnetic cassettes, magnetic tapes, magnetic disk storage or other magnetic storage devices, or any other media that can be used to store the desired information and can be accessed by a computer.
[0156] The memory 326 further includes one or more data storage areas 308 that the network computer 350 can utilize to store applications 312 and / or other data such as content 310, etc. For example, the data storage areas 308 can also be used to store information describing various capabilities of the network computer 350. This information can then be provided to another computer based on any of a variety of events, including being sent as part of a header during a communication, being sent upon request, etc. The data storage areas 308 can also be used to store messages, web page content, etc. At least a portion of this information can also be stored on another component of the network computer 350, including but not limited to a processor-readable storage medium 328 within a client computer, a hard drive 334, or other computer-readable storage medium (not shown).
[0157] The data store 308 may include a database, text, spreadsheet, folder, file, etc., which may be configured to maintain and store user account identifiers, user profiles, email addresses, IM addresses, and / or other network addresses, etc.
[0158] In at least one embodiment, data store 208 may include a business information database 206 that can contain information analysis services (eg, scoring and ranking) as described herein.
[0159] Data storage area 308 can also include data storage 100, as described herein, including reference Figure 1A to Figure 1B As described, the data storage 100 is stored as a lookup table.
[0160] The data storage area 208 can also include immutable distributed ledger information 311 for the networks 203a...203n to which the hub server computer 112 has gained access and has nodes 205a...205n. For each immutable distributed ledger network 203a...203n, a separate server 205a, 205b...205n will be run to host the connected nodes to the network 203a...203n. These servers will be connected to the hub server computer 112 through communication on a common communication protocol. It should be appreciated that each node server is separate, but the node servers can be hosted on the same system.
[0161] The data storage area 308 may further include program code, data, algorithms, etc. for execution and action by a processor (such as processor 307). In one embodiment, at least some of the data storage area 208 may also be stored on another component of the network computer 350, including but not limited to processor-readable storage media 328, hard disk drive 334, etc.
[0162] Applications 312 may include computer executable instructions that may be loaded into mass storage and run on operating system 356. Examples of application programs may include transcoders, schedulers, calendars, database programs, word processing programs, hypertext transfer protocol (HTTP) programs, customizable user interface programs, IPSec applications, encryption programs, security programs, SMS messaging servers, IM messaging servers, email servers, account managers, etc. Applications 312 may also include website servers 314, hub server applications 112, ID resolution servers 201, node servers 205a...205n, and business entity information servers 216. Application servers may be configured to support and provide content to client applications, and may be configured for the application tools and modules described herein. Application servers may be implemented in a manner similar to that in conjunction with Figures 3 to 10 Those processes or parts of the processes described above to perform at least some of their actions.
[0163] The node server applications 205a...205n can include an immutable distributed ledger application including a data management tool configured to record application usage and transaction data to an immutable distributed ledger network 203 associated with a client business entity. The data management tool can be configured to communicate with the immutable distributed ledger computer server and the hub server computer 112 to control, share, accept and synchronize data. In one embodiment, the data management tool can include a logging tool configured to record and store data in one or more databases, including customer transactions recorded on the immutable distributed ledger network 203. The logging tool can also be configured to record transactions between clients on the immutable distributed ledger. In at least one embodiment, the license platform node server application acts as an immutable distributed ledger computer server node.
[0164] The platform node server applications 205a...205n can include a transaction interface tool 264 for entering transactions recorded on an immutable distributed ledger, including transactions such as smart contracts and / or cryptocurrency transactions.
[0165] The website server 314 may represent any of a variety of information and services configured to provide content including messages to another computer over a network. Thus, the website server 314 can include, for example, a Web server, a file transfer protocol (FTP) server, a database server, a content server, etc. The website server 314 may provide content including messages over a network using any of a variety of formats, including but not limited to WAP, HDML, WML, SGML, HTML, XML, Compressed HTML (cHTML), Extensible HTML (xHTML), etc.
[0166] Now refer to Figures 3 to 10 Describes the operation of certain aspects of the present invention. In at least one embodiment, for processes 300, 400, 500, 600, 700, 800, 900, and 1000, these processes or portions of these processes can be implemented and / or executed on multiple network computers, such as Figure 2B Client computers in Figure 2C However, these embodiments are not limited thereto, and various combinations of network computers, client computers, virtual machines, etc. may be utilized. In addition, in at least one embodiment, in combination with Figures 3 to 10 The described process can be performed in conjunction with FIG. Figure 2A Describes the logical architecture of the system in which it operates.
[0167] Figure 3 is a block diagram illustrating a process 300 for authenticating an entity in accordance with the present invention.
[0168] In box 301, an entity creates a public key pair / private key pair for an immutable distributed ledger network. In one embodiment, the platform host can act as a verification host. In box 302, the public key is sent to the hub server 112 via a verification host node 205 on the immutable distributed ledger network, or by direct communication with an Internet hosting platform that can access the hub server 112. In box 303, the verification host generates and returns a randomly generated verification message. In box 304, the entity signs the verification message with a private key.
[0169] At box 305, entity verification begins. The entity submits a signature for verification. Entity verification can include verification through a registered communication protocol or through physical communication. For example, for a registered digital communication protocol, at box 306, the system can be configured to enable an entity to submit a signature to text signature data on a domain they control or by the entity using a registered phone number. At box 307, in order to verify the entity through physical communication (e.g., verbally or in writing), the entity can, for example, visit the physical site of the verification host to confirm the signature or use a registered phone number to confirm the signature verbally. At box 308, the verification host checks the signature submitted by the entity. At box 309, the verification host records the verification network ID and stores it in the entity's ID data store 100.
[0170] Figure 4 4 is a block diagram illustrating a process 400 for verifying a new distributed ledger identity using a verified identity. In block 401, the entity creates a message including information about a distributed ledger address 102 of a distributed ledger network. In block 402, the entity generates a signature for the message using the new private key. Then, in block 403, the entity appends a message detailing the verified distributed ledger address 102. Then, in block 404, the entity generates a signature for the verified distributed ledger address 102 message using the corresponding verified private key. In block 405, the verification host verifies the signature of the verified private key generated in block 404. In block 406, the verification host verifies the signature of the new key generated in block 402. In block 407, the verification host verifies a checksum of the distributed ledger address and the network identified in the distributed ledger address. In block 408, the verification host adds the new distributed ledger address 102 to the ID resolution data store 100 of the entity.
[0171] Figure 5 is a block diagram illustrating a process 500 for retrieving an entity ID 101 from a system according to the present invention. At block 501, an entity generates and sends a search query message to an ID resolution server 201, the search query message including a distributed ledger address 102 or a unique entity ID 101 and optionally including filtering parameters. At block 502, the ID resolution server 201 runs ID lookup logic to identify a distributed ledger address 102 or a unique ID 101 that satisfies the search query parameters on the data store 100. At block 504, the ID resolution server 201 runs filtering logic (if any) of the search to filter the search results identified at block 502. At block 503, the distributed ledger address 102 and / or unique ID 101 search results identified in the search are sent to the entity.
[0172] Figure 6 6 is a block diagram illustrating a process 600 for smart contract request resolution according to the present invention. In block 601, a party enters a smart contract on network 1, triggering an information event about the smart contract, such as a request or opportunity to trade the smart contract. In block 602, entity node server 205 obtains a smart contract request via an event or other notification. In block 603, node server 205 sends the request to hub server 112. In block 604, as described with reference to Figure 5 As described above, the hub server 112 disambiguates the distributed ledger address 102 with the help of the ID resolution server 201. In block 605, the hub server obtains enterprise statistics information about the entity from the enterprise statistics information server 216, and enriches information about the entity that is a party to the smart contract. For non-limiting examples of some company entity data links, generating a company's enterprise statistics database and scoring, and data integration by the business entity information database 206 and the business analysis server, see U.S. Patent No. 7,822,757, filed on February 18, 2003, entitled "System and Method for Providing Enhanced Information", U.S. Patent No. 8,346,790, filed on September 28, 2010, entitled "Data Integration Method and System", and U.S. Patent No. 8,036,907, filed on December 23, 2003, entitled "Method and System for Linking Business Entities Using Unique Identifiers", the entire text of each of which is incorporated herein by reference. In box 606, the hub server 606 returns the enriched information to the node server. At block 607 , the node server 205 generates a transaction to the smart contract.
[0173] Figure 7 700 is a block diagram illustrating a process 700 for smart contract request parsing according to the present invention. In box 701, a smart contract is input on network 1. In box 702, a first party A deploys an offer to conduct a transaction according to the smart contract. In box 703, a second party B sends a transaction offer to the smart contract to indicate an intention to be the counterparty to the transaction. In box 704, Party B's message triggers an information event about the smart contract, namely a request to conduct a transaction according to the smart contract. In box 705, the node server 205 obtains the smart contract request via an event or other notification. As described herein, the node server 205 can be configured to listen to events of the smart contract, such as adding a counterparty, other changes in the state of the smart contract, updated contract requirements, for example, see Fig. 9 .
[0174] At block 706, node server 205 sends a request including counterparty B information and enrichment instructions to hub server 112. At block 707, hub server 112 determines whether the counterparty of the smart contract is authorized to receive enrichment data. If so, at block 708, the hub server sends the counterparty information to ID resolution server 201 to disambiguate the network ID with the help of the ID resolution server, as shown in Figure 5 . In box 709, the hub server uses the resolved ID to obtain enterprise statistics about the entity from the enterprise statistics server 216, and enriches information about the entity that is a party to the smart contract. In box 710, the hub server 112 returns the enriched information to the node server 205. In box 711, the node server 205 can use the enriched data to take action or generate a transaction to the smart contract. For example, the enriched data can be used to change or add information to the smart contract (such as state, name of the transaction party, financial terms, company and business contact information, such as linking business relationships, etc.) to allow the smart contract to be carried out or executed according to the smart contract.
[0175] Figure 8 8 is a block diagram illustrating a process 700 for smart contract request parsing according to the present invention. In box 801, a first smart contract F is input on a first distributed ledger network 203a. In box 802, Party A and Party B become counterparties of smart contract F. In box 803, smart contract F is configured to parse and verify whether the platform host signs a transaction for smart contract F. In box 804, Party A or Party B sends a transaction request message to a network node server 205a on the first distributed ledger network 203a, which contains instructions to verify that both parties are counterparties of smart contract G on different distributed ledger networks 203b. In box 805, node server 205a sends the message and instructions to hub server 112. In box 806, hub server 112 associates smart contract F with smart contract G on network 2. The instructions from node server 205a are explicit instructions. The counterparty identifies smart contract G and its network in the update of smart contract F.
[0176] At block 807, smart contract G is entered on the second distributed ledger network 203b. At block 808, party A and party B become counterparties of smart contract G. At block 809, party A or party B sends a transaction message to network node server 205a on network 1, which contains instructions for resolving entity IDs. At block 810, node server 205b on the second distributed ledger network 203b sends a message with counterparty information and enrichment instructions to hub server 112. At block 811, the hub server sends the counterparty information to ID resolution server 201 to disambiguate the network ID with the help of the ID resolution server, as shown in FIG. Figure 7 , the ID resolution server resolves the ID based on the rights and verification and instructions. In box 812, the hub server uses the resolved ID to obtain enterprise statistics about the entity from the business entity information server 216 and enrich information about the entity that is a party to the smart contract as described herein. Some non-limiting examples of corporate entity data linking, generating corporate statistics databases and scores for companies, and data integration by business entity information database 206 and business analysis servers are described in U.S. Patent No. 7,822,757, filed on February 18, 2003, entitled "System and Method for Providing Enhanced Information", U.S. Patent No. 8,346,790, filed on September 28, 2010, entitled "Data Integration Method and System", and U.S. Patent No. 8,036,907, filed on December 23, 2003, entitled "Method and System for Linking Business Entities Using Unique Identifiers", each of which is incorporated herein by reference in its entirety. At block 813, the node server sends the enriched transaction message back to smart contract G on the second distributed ledger network 203b. In box 814, smart contract G proceeds based on the verification and enrichment in the transaction message.
[0177] In box 815, the smart contract G between party A and party B is resolved. In box 816, the resolution of smart contract G triggers an event to the node server 205b on the second distributed ledger network 203b. In box 817, the node server 205b on the second distributed ledger network 203b sends a "resolved" message to the hub server 112. In box 818, the hub server 112 parses the initial request from the transaction request message of the network node server 205a on the first distributed ledger network 203a, which contains the instructions in box 805 to verify that the two parties are the counterparties of the smart contract G on different distributed ledger networks 203b. In box 819, the network node server 205a on the first distributed ledger network 203a receives confirmation from the resolution of the hub server and sends a transaction message to smart contract F to verify that its counterparties A and B are the same counterparties in smart contract G. In box 820, smart contract F receives the transaction message and proceeds based on the verification.
[0178] Fig. 9 An example of a smart contract process is shown. For a smart contract (red button) between Company A (Buttons Inc.) and Company B (Jackets Inc.) regarding product shipment and delivery, exemplary events that trigger the smart contract can include product shipment, port product, product inspection, and product delivery. In order to participate in the smart contract, Company B needs the identity resolution information and business information of the smart contract. In one embodiment, at block 902, Company A (Buttons Inc.) can participate in it through a verification process using a public address that has been approved, as shown in FIG. Figure 3 and Figure 4 At block 904 , even though Company A is not a participant, the system is configured to perform identity resolution and obtain information from the immutable distributed ledger network operator, which can be matched with enterprise demographic data from the business entity information database 206 , as described herein.
[0179] The system can then be configured to provide data to enrich enterprise statistics and cross-reference smart contracts to automatically execute. For example, at box 905, when the product shipment is confirmed to the network ledger, an automatic execution of a third-party escrow transaction (e.g., $10,000) can be triggered for Company B. At box 906, when the port product is confirmed to the network ledger, the inspection data is automatically shared with the port inspector. At box 907, the product inspection confirmation ("PASS") triggers the automatic execution of the third-party escrow release. At box 908, the product delivery message automatically executes the completion of the smart contract on the ledger.
[0180] Fig.10 An example of a network and business identification according to one embodiment is shown. In box 1001, a client device sends a request to an identity resolution server 201 via a network protocol, as described herein, for example, via a hub server 112. The request includes an entity ID 101 or an address of an individual distributed ledger account. In box 1002, the hub server 112 matches the company with a business identification number (e.g., DUNS code 106). In box 1003, the identity resolution server 201 logic performs a lookup for the entity ID or address, and if the entity ID or address is found, information associated with the entity ID 101 or address is returned to the requester in the box, including the specific distributed ledger network 203 to which the network ID 103 belongs, the entity to which the entity ID 101 belongs, other distributed ledger network IDs 103a...103n on the same network 203 or in other networks 203a...203n, and the distributed ledger network 203a...203n to which each of these IDs belongs. At block 1004, the business statistics from the business entity information database 206 are mapped to the business identification number. Some non-limiting examples of corporate entity data linking, generating a corporate statistics database and score for a company, and data integration by the business entity information database 206 and the business analysis server are described in U.S. Patent No. 7,822,757, filed on February 18, 2003, entitled "System and Method for Providing Enhanced Information", U.S. Patent No. 8,346,790, filed on September 28, 2010, entitled "Data Integration Method and System", and U.S. Patent No. 8,036,907, filed on December 23, 2003, entitled "Method and System for Linking Business Entities Using Unique Identifiers", each of which is incorporated herein by reference in its entirety. Business demographic or other attribute data associated with the entity owning the ID (such as company name, address and ranking / assessment / risk score, corporate and business association information and associated business relationships, such as parent-subsidiary companies in a family tree relationship, corporate family, global headquarters, branches, etc.) is also returned to the requester.
[0181] Although some embodiments have been illustrated and described according to various innovative methods, it should be clearly understood that it is easy to make several changes to the same embodiment, which is obvious to those skilled in the art. Therefore, the present invention is not limited to the details illustrated and described herein, but also covers all changes and modifications that fall within the scope of the appended claims.< / address>
Claims
1. A method for identity resolution across a disparate immutable distributed ledger network, comprising: receiving, from a distributed ledger network platform node on a first distributed ledger network, a request to verify that a plurality of entities that are counterparties to a contract transaction on the first distributed ledger network are counterparties to a contract transaction on another distributed ledger network; Associating, at the hub server, the contract on the first distributed ledger network with the contract on the other distributed ledger network; At the distributed ledger network platform node on the other distributed ledger network, receiving a transaction message to resolve an entity ID of a counterparty to the contract transaction on the other distributed ledger network; receiving a transaction message and an instruction for resolving the entity ID from the distributed ledger network platform node on the other distributed ledger network; At the central server, resolving the entity ID of the contract transaction counterparty on the other distributed ledger network; At the distributed ledger network platform node on the other distributed ledger network, receiving a transaction message indicating that a contract has been executed; Sending a parsed message to the hub server confirming that the contract on the other distributed ledger network has been executed; parsing, by the hub server, a request from the distributed ledger network platform node on the first distributed ledger network to verify that a plurality of entities that are counterparties to a contract transaction on the first distributed ledger network are counterparties to a contract transaction on the other distributed ledger network; and Sending a verification message to the distributed ledger network platform node on the first distributed ledger network.
2. The method according to claim 1, further comprising: Obtaining business entity enterprise statistics information about the transaction counterparty from a business information database server through the central server; as well as The business entity enterprise statistical information is output to the distributed ledger network platform node on the distributed ledger network of at least one of the transaction counterparties.
3. The method according to claim 2, wherein: The business entity enterprise statistical information includes business contact information.
4. A system for identity resolution across a disparate immutable distributed ledger network, wherein: The system includes a network computer, wherein the network computer includes: Hub server; ID resolution server; memory for storing databases and program instructions; and A processor device operable to execute program instructions enabling actions, comprising: receiving, from a distributed ledger network platform node on a first distributed ledger network, a request to verify that a plurality of entities that are counterparties to a contract transaction on the first distributed ledger network are counterparties to a contract transaction on another distributed ledger network; Associating, at the hub server, the contract on the first distributed ledger network with the contract on the other distributed ledger network; At the distributed ledger network platform node on the other distributed ledger network, receiving a transaction message to resolve an entity ID of a counterparty to the contract transaction on the other distributed ledger network; receiving a transaction message and an instruction for resolving the entity ID from the distributed ledger network platform node on the other distributed ledger network; At the central server, resolving the entity ID of the contract transaction counterparty on the other distributed ledger network; At the distributed ledger network platform node on the other distributed ledger network, receiving a transaction message indicating that a contract has been executed; Sending a parsed message to the hub server confirming that the contract on the other distributed ledger network has been executed; parsing, by the hub server, a request from the distributed ledger network platform node on the first distributed ledger network to verify that a plurality of entities that are counterparties to a contract transaction on the first distributed ledger network are counterparties to a contract transaction on the other distributed ledger network; and Sending a verification message to the distributed ledger network platform node on the first distributed ledger network.
5. The system according to claim 4, wherein: The system is further configured to execute program instructions that enable actions, including: Obtaining, through the central server, business entity enterprise statistical information about the transaction counterparty from a business information database server; and The business entity enterprise statistical information is output to the distributed ledger network platform node on the distributed ledger network of at least one of the transaction counterparties.
6. The system according to claim 5, wherein: The business entity enterprise statistical information includes business contact information.
