Data processing method based on blockchain network and related product
US-2024419537-A1 · Dec 19, 2024 · US
US2020342136A1 · US · A1
| Field | Value |
|---|---|
| Publication number | US-2020342136-A1 |
| Application number | US-201916397746-A |
| Country | US |
| Kind code | A1 |
| Filing date | Apr 29, 2019 |
| Priority date | Apr 29, 2019 |
| Publication date | Oct 29, 2020 |
| Grant date | — |
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.
Embodiments disclosed herein are related to computing systems and methods for localizing how a user will receive and view received DID-related data. The computing system and methods are implemented in the decentralized network that implements a distributed ledger that backs one or more decentralized identities (DID) for one or more users of the computing system. Various sets of rule are accessed. The sets of rules specify how a DID owner will receive and view DID-related data received from a third party entity. The sets of rules are applied to the DID-related data received from the third party entity. The received DID-related data is modified such that the received DID-related data conforms to the one or more sets of rules. The modified DID-related data is provided to the DID owner so that the DID owner is able to view the modified DID-related data according to the applied sets of rules.
Opening claim text (preview).
What is claimed is: 1 . A computing system that is implemented in a decentralized network that implements a distributed ledger, the distributed ledger being configured to back one or more decentralized identities (DID) for one or more users of the computing system, the computing system comprising: one or more processors; and one or more computer-readable media having thereon computer-executable instructions that are structured such that, when executed by the one or more processors, cause the computing system to: access one or more sets of rules, the one or more sets of rules specifying how a DID owner will receive and view DID-related data received from a third party entity; apply the one or more sets of rules to the DID-related data received from the third party entity; modify the received DID-related data such that the received DID-related data conforms to the one or more sets of rules; and provide the modified DID-related data to the DID owner such that the DID owner is able to view the modified DID-related data according to the applied one or more sets of rules. 2 . The computing system according to claim 1 , wherein the DID-related data comprises one of a DID-related intent or a DID-related attestation. 3 . The computing system according to claim 1 , wherein the one or more sets of rules includes a user defined set of rules that specifies parameters desired by the owner of the DID. 4 . The computing system according to claim 1 , wherein the one or more sets of rules includes one or more sets of local rules that are specific to a particular location. 5 . The computing system according claim 4 , wherein the one or more sets of local rules are based on a location of where the DID owned by the DID owner was generated or where a management module controlled by the DID owner was implemented. 6 . The computing system of claim 4 , wherein the wherein the one or more sets of local rules are based on a current location of the owner of the DID owner. 7 . The computing system of claim 1 , wherein accessing the one or more sets of rules comprises: accessing a first set of local rules based on a first location of the DID owner when the DID owned by the DID owner was generated or where a management module controlled by the DID owner was implemented; detecting that the DID owner has moved to a second location that is different from the first location; and accessing a second set of local rules that are based the second location. 8 . The computing system of claim 1 , wherein applying the one or more sets of rules to the DID-related data received from the third party entity comprises: receiving input from DID owner that selects a particular one of the one or more sets of rules to be applied; and applying the selected particular one of the sets of rules to the to the DID-related data received from the third party entity. 9 . The computing system of claim 1 , wherein applying the one or more sets of rules to the DID-related data received from the third party entity comprises: automatically selecting a particular one of the one or more sets of rules to be applied; and applying the selected particular one of the sets of rules to the to the DID-related data received from the third party entity. 10 . In a computing system that is implemented in a decentralized network that implements a distributed ledger, the distributed ledger being configured to back one or more decentralized identities (DID) for one or more users of the computing system, a method of localizing how a user will receive and view received DID-related data, the method comprising: accessing one or more sets of rules, the one or more sets of rules specifying how a DID owner will receive and view DID-related data received from a third party entity; applying the one or more sets of rules to the DID-related data received from the third party entity; modifying the received DID-related data such that the received DID-related data conforms to the one or more sets of rules; and providing the modified DID-related data to the DID owner such that the DID owner is able to view the modified DID-related data according to the applied one or more sets of rules. 11 . The method according to claim 10 , wherein the DID-related data comprises one of a DID-related intent or a DID-related attestation. 12 . The method according to claim 10 , wherein the one or more sets of rules includes a user defined set of rules that specifies parameters desired by the owner of the DID. 13 . The method according to claim 10 , wherein the one or more sets of rules includes one or more sets of local rules that are specific to a particular location. 14 . The method according to claim 13 , wherein the one or more sets of local rules are based on a location of where the DID owned by the DID owner was generated or where a management module controlled by the DID owner was implemented. 15 . The method according to claim 13 , wherein the wherein the one or more sets of local rules are based on a current location of the owner of the DID owner. 16 . The method according to claim 10 , wherein accessing the one or more sets of rules comprises: accessing a first set of local rules based on a first location of the DID owner when the DID owned by the DID owner was generated or where a management module controlled by the DID owner was implemented; detecting that the DID owner has moved to a second location that is different from the first location; and accessing a second set of local rules that are based the second location. 17 . The method according to claim 16 , where a location finder of a device associated with the DID owner detects that the DID owner has moved to the second location. 18 . The method according to claim 10 , wherein applying the one or more sets of rules to the DID-related data received from the third party entity comprises: receiving input from DID owner that selects a particular one of the one or more sets of rules to be applied; and applying the selected particular one of the sets of rules to the to the DID-related data received from the third party entity. 19 . The method according to claim 10 , wherein applying the one or more sets of rules to the DID-related data received from the third party entity comprises: automatically selecting a particular one of the one or more sets of rules to be applied; and applying the selected particular one of the sets of rules to the to the DID-related data received from the third party entity. 20 . A computer program product comprising one or more computer-readable storage media having thereon computer-executable instructions that are structured such that, when executed by one or more processors of a computing system, cause the computing system to perform a method for localizing how a user will receive and view received DID-related data, the method comprising: accessing one or more sets of rules, the one or more sets of rules specifying how a DID owner will receive and view DID-related data received from a third party entity; applying the one or more sets of rules to the DID-related data received from the third party entity; modifying the received DID-related data such that the received DID-related data conforms to the one or more sets of rules; and providing the modified DID-related data to the DID owner such that the DID owner is able to view the modified DID-related data according to the applied one or more sets of rules.
using hash chains, e.g. blockchains or hash trees · CPC title
involving time stamps, e.g. generation of time stamps · CPC title
involving non-keyed hash functions, e.g. modification detection codes [MDCs], MD5, SHA or RIPEMD · CPC title
Network architectures or network communication protocols for network security (cryptographic mechanisms or cryptographic arrangements for secret or secure communication H04L9/00; network architectures or network communication protocols for wireless network security H04W12/00; security arrangements for protecting computers or computer systems against unauthorised activity G06F21/00) · CPC title
Protecting personal data, e.g. for financial or medical purposes · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.