Client, server, method and identity verification system
US-2017310653-A1 · Oct 26, 2017 · US
US12235979B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-12235979-B2 |
| Application number | US-202418411495-A |
| Country | US |
| Kind code | B2 |
| Filing date | Jan 12, 2024 |
| Priority date | Jan 25, 2017 |
| Publication date | Feb 25, 2025 |
| Grant date | Feb 25, 2025 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
Methods and systems for managing and/or processing a blockchain to maintain data security for confidential and/or personal data are provided. According to certain aspects, the disclosed data security techniques may enable access sharing functionality utilizing the blockchain. For example, access sharing may be utilized to file documents, share policy information, and/or comply with an audit. The data security techniques disclosed herein also enable the use of smart contracts to transfer funds associated with payment obligations and/or other forms of blockchain based payments, comply with anti-money laundering requirements, report industry data, validate interest payments and/or maintain agent sales data. Data security may be achieved through the use of public key/private key encryption techniques.
Opening claim text (preview).
What is claimed: 1. A computer-implemented method of providing access to encrypted data stored in a blockchain relating to a plurality of smart contracts, the method comprising: receiving, from a requesting node, a request to provide access to encrypted data associated with a smart contract to a particular node of the blockchain upon being directed by the smart contract; determining, by one or more processors, that permissions associated with the requesting node indicate that the requesting node is permitted to request access to the encrypted data associated with the smart contract; determining, by the one or more processors, that an access level associated with the particular node indicates that the particular node is permitted to access the encrypted data associated with the smart contract; and in response to the determinations, transmitting, by the one or more processors, a private key for the smart contract to the particular node via a communication channel other than the blockchain. 2. The computer-implemented method of claim 1 , wherein determining the permissions associated with the requesting node comprises: decrypting, using a public key for the requesting node, a digital signature included in the request by the requesting node to verify authenticity of the digital signature. 3. The computer-implemented method of claim 2 , wherein decrypting the digital signature comprises: querying, by the one or more processors, a database of public keys using an indication of the requesting node to retrieve a public key for the requesting node. 4. The computer-implemented method of claim 1 , further comprising: receiving, at the one or more processors, a request from the particular node to become a node of the blockchain. 5. The computer-implemented method of claim 4 , further comprising: generating, by the one or more processors, a public key and a private key for the particular node. 6. The computer-implemented method of claim 5 , further comprising: adding, by the one or more processors, the public key for the particular node to a database of public keys. 7. The computer-implemented method of claim 4 , further comprising: assigning, by the one or more processors, permissions for the particular node, the permissions being associated with one or more types of data the particular node is permitted to access. 8. A computer system for providing access to encrypted data stored in a blockchain relating to a plurality of smart contracts, the computer system comprising: one or more processors; one or more transceivers adapted to communicate with a plurality of nodes; and a non-transitory program memory coupled to the one or more processors and storing executable instructions that, when executed by the one or more processors, cause the computer system to: receive, from a requesting node, a request to provide access to encrypted data associated with a smart contract to a particular node of the blockchain upon being directed by the smart contract; determine that permissions associated with the requesting node indicate that the requesting node is permitted to request access to the encrypted data associated with the smart contract; determine that an access level associated with the particular node indicates that the particular node is permitted to access the encrypted data associated with the smart contract; and in response to the determinations, transmit, via the one or more transceivers, a private key for the smart contract to the particular node via a communication channel other than the blockchain. 9. The computer system of claim 8 , wherein to determine the permissions associated with the requesting node, the instructions, when executed, cause the computer system to: decrypt, using a public key for the requesting node, a digital signature included in the request by the requesting node to verify authenticity of the digital signature. 10. The computer system of claim 9 , wherein to decrypt the digital signature, the instructions, when executed, cause the computer system to: query a database of public keys using an indication of the requesting node to retrieve the public key for the requesting node. 11. The computer system of claim 8 , wherein the instructions, when executed, cause the computer system to: receive a request from the particular node to become a node of the blockchain. 12. The computer system of claim 10 , wherein the instructions, when executed, cause the computer system to: generate a public key and a private key for the particular node. 13. The computer system of claim 12 , wherein the instructions, when executed, cause the computer system to: add the public key for the particular node to a database of public keys. 14. The computer system of claim 12 , wherein the instructions, when executed, cause the computer system to: assign permissions for the particular node, the permissions being associated with one or more types of data the particular node is permitted to access. 15. A non-transitory computer readable storage medium storing processor-executable instructions, that, when executed, cause one or more processors to: receive, from a requesting node, a request to provide access to encrypted data associated with a smart contract to a particular node of a blockchain upon being directed by the smart contract; determine that permissions associated with the requesting node indicate that the requesting node is permitted to request access to the encrypted data associated with the smart contract; determine that an access level associated with the particular node indicates that the particular node is permitted to access the encrypted data associated with the smart contract; and in response to the determinations, transmit a private key for the smart contract to the particular node via a communication channel other than the blockchain. 16. The non-transitory computer readable storage medium of claim 15 , wherein to determine the permissions associated with the requesting node, the instructions, when executed, cause the one or more processors to: decrypt, using a public key for the requesting node, a digital signature included in the request by the requesting node to verify authenticity of the digital signature. 17. The non-transitory computer readable storage medium of claim 16 , wherein to decrypt the digital signature, the instructions, when executed, cause the one or more processors to: query a database of public keys using an indication of the requesting node to retrieve a public key for the requesting node. 18. The non-transitory computer readable storage medium of claim 15 , wherein the instructions, when executed, cause the one or more processors to: receive a request from the particular node to become a node of the blockchain. 19. The non-transitory computer readable storage medium of claim 15 , wherein the instructions, when executed, cause the one or more processors to: generate a public key and a private key for the particular node. 20. The non-transitory computer readable storage medium of claim 19 , wherein the instructions, when executed, cause the one or more processors to: assign permissions for the particular node, the permissions being associated with one or more types of data the particular node is permitted to access.
Protecting data integrity, e.g. using checksums, certificates or signatures · CPC title
specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems · CPC title
using hash chains, e.g. blockchains or hash trees · CPC title
Financial cryptography, e.g. electronic payment or e-cash · CPC title
Transaction verification · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.