Decentralized identity management for web3

US12407685B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-12407685-B2
Application numberUS-202218076651-A
CountryUS
Kind codeB2
Filing dateDec 7, 2022
Priority dateAug 10, 2022
Publication dateSep 2, 2025
Grant dateSep 2, 2025

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

Systems and methods for identity management can leverage a blockchain to securely store and access personal data. Third party computing systems can request access to the personal data to obtain biometric data, medical history data, and/or other biological data associated with the user. The systems and methods can determine whether to provide access to the data and can generate log data to be logged in a view log based on the access provided.

First claim

Opening claim text (preview).

What is claimed is: 1. A computing system, the computing system comprising: one or more processors; and one or more non-transitory computer-readable media that collectively store instructions that, when executed by the one or more processors, cause the computing system to perform operations, the operations comprising: receiving an access request from a third party computing system, wherein the access request is descriptive of a request to access biological data for a particular user, wherein the biological data is stored on a blockchain, and wherein the biological data is associated with biological characteristics of the particular user; determining a particular entity associated with the third party computing system; transmitting a notification to a particular user computing system, wherein the particular user computing system is associated with the particular user, wherein the notification is descriptive of the access request and the particular entity; receiving user input data from a particular user computing system, wherein the user input data is descriptive of a user response to the access request; determining an access action based on the user input data, wherein the access action is descriptive of a level of access to be provided to the third party computing system to the biological data on the blockchain; adjusting a view log based on the access action, wherein the view log is descriptive of one or more viewers associated with the biological data, wherein adjusting the view log comprises updating the blockchain to include log data comprising a type of access and the particular entity and updating an authorization list on the blockchain based on the particular entity and the access action; and facilitating the type of access to the biological data by the third party computing system based on the authorization list stored on the blockchain, wherein the type of access comprises at least one of: view access, write access, copy access, edit access, or delete access. 2. The computing system of claim 1 , wherein the operations further comprise: causing the access action to occur; determining a view time of the access action; and wherein adjusting the viewer log comprises logging the view time associated with the access action. 3. The computing system of claim 1 , wherein the operations further comprise: determining the particular entity is associated with a medical service provider; and wherein the access action comprises providing the biological data to the medical service provider. 4. The computing system of claim 1 , wherein the access action comprises a read call without write access. 5. The computing system of claim 1 , wherein the access action comprises at least one of: providing the biological data to the third party computing system; or providing a subset of the biological data to the third party computing system. 6. The computing system of claim 1 , wherein the access action comprises: accessing a blockchain node based on the access request; and identifying blockchain data associated with the particular user. 7. The computing system of claim 1 , wherein the biological data comprises biometric data associated with the particular user. 8. The computing system of claim 7 , wherein the biometric data comprises iris data associated with the particular user, wherein the iris data is descriptive of one or more identifying features of an iris of the particular user. 9. The computing system of claim 7 , wherein the biometric data comprises face data associated with the particular user, wherein the face data is descriptive of one or more identifying features of a face of the particular user. 10. The computing system of claim 7 , wherein the biometric data comprises fingerprint data associated with the particular user, wherein the fingerprint data is descriptive of one or more identifying features of a fingerprint of the particular user. 11. The computing system of claim 1 , wherein the particular entity is associated with a web platform. 12. A computer-implemented method, the method comprising: receiving, by a computing system comprising one or more processors, an access request from a third party computing system, wherein the access request is descriptive of a request to access personal data associated with a particular user, wherein the personal data is stored on a blockchain, and wherein the personal data comprises biometric data associated with the particular user; determining, by the computing system, a particular entity associated with the third party computing system, wherein the particular entity is associated with a third party service provider; determining one or more authorized entities associated with the particular user based on one or more user inputs, wherein the one or more authorized entities are determined based on: transmitting a notification to a particular user computing system associated with the particular user, wherein the notification is descriptive of the access request and the particular entity; and receiving user input data from a particular user computing system, wherein the user input data is descriptive of a user response to the access request; determining, by the computing system, an access action based on whether the particular entity is associated with the one or more authorized entities, wherein the one or more authorized entities are determined based on one or more user inputs; adjusting, by the computing system, a view log associated with the personal data based on the access action, wherein adjusting the view log comprises adding log data associated with the particular entity and the access request to the view log, wherein adjusting the view log comprises updating the blockchain to include log data comprising a type of access and the particular entity and updating an authorization list on the blockchain based on the particular entity and the access action, wherein the type of access comprises at least one of: view access, write access, copy access, edit access, or delete access; and providing, by the computing system, blockchain data associated with the particular user based on access action stored on the authorization list on the blockchain, wherein the blockchain data comprises the personal data. 13. The method of claim 12 , wherein the biometric data is descriptive of one or more identifying features associated with the particular user. 14. The method of claim 12 , wherein the view log comprises a plurality of entries, wherein each entry comprises identification data associated with a viewer of the personal data. 15. The method of claim 12 , further comprising: determining, by the computing system, the particular entity is associated with a medical service provider; and wherein the access action comprises providing write access to the medical service provider; and determining, by the computing system, to transmit the notification based on the particular entity being associated with a medical service provider. 16. The method of claim 15 , further comprising: obtaining, by the computing system, additional personal data from the medical service provider; and adding, by the computing system, the additional personal data to the blockchain. 17. One or more non-transitory computer-readable media that collectively store instructions that, when executed by one or more computing devices, cause the one or more computing devices to perform operations, the operations comprising: receiving an access request from a third party computing system to provide personal data to the third party computing system, wherei

Assignees

Inventors

Classifications

  • Entity profiles · CPC title

  • using biometrical features, e.g. fingerprint, retina-scan (cryptographic mechanisms or cryptographic arrangements for entity authentication using biological data H04L9/3231) · CPC title

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US12407685B2 cover?
Systems and methods for identity management can leverage a blockchain to securely store and access personal data. Third party computing systems can request access to the personal data to obtain biometric data, medical history data, and/or other biological data associated with the user. The systems and methods can determine whether to provide access to the data and can generate log data to be lo…
Who is the assignee on this patent?
Google Llc
What technology area does this patent fall under?
Primary CPC classification H04L63/0861. Mapped technology areas include Electricity.
When was this patent published?
Publication date Tue Sep 02 2025 00:00:00 GMT+0000 (Coordinated Universal Time) (B2). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 5 related publications on this page (citations in our corpus or others sharing the same primary CPC).