# US 2020/0403810 A1 · Validation data structure for decentralized identity claim

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2020/0403810 A1
- Document ID: US20200403810A1
- Status: Published application
- Kind: A1
- Application number: 16/445,103
- Filed: 2019-06-18
- Published: 2020-12-24
- Earliest claimed: 2019-06-18
- Assignees: Microsoft Technology Licensing, LLC
- Applicants: Microsoft Technology Licensing, LLC
- Inventors: Brandon MURDOCH; Sydney MORTON; Daniel Luke STROCKIS; Ankur PATEL
- Web page: https://patentgrep.com/patent/US20200403810A1

## CPC

- G06F 21/64: Protecting data integrity, e.g. using checksums, certificates or signatures
- H04L 9/3268: {using certificate validation, registration, distribution or revocation, e.g. certificate revocation list [CRL]}
- G06F 7/58: Random or pseudo-random number generators
- G06F 21/62: Protecting access to data via a platform, e.g. using keys or access control rules
- H04L 9/3236: {using cryptographic hash functions}
- H04L 67/10: in which an application is distributed across nodes in the network (software deployment G06F8/60; multiprogramming arrangements G06F9/46)
- G06F 21/42: using separate channels for security data
- H04L 9/50: {using hash chains, e.g. blockchains or hash trees}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Use of a validation data structure in order to securely communicate an encrypted claim that has a decentralized identifier as a subject. The sending system generates the validation data structure and presents the validation data structure to a user that owns the decentralized identifier. The sending system encrypts the claim using at least the validation data structure, and constructs a message that includes the encrypted claim, but which does not include the validation data structure. The relying party receives the message. However, without separately receiving the validation data structure from the user, the relying party computing system cannot decrypt the encrypted claim. If the user wishes the relying party computing system to have access to the claim, the user may communicate the validation data structure to the relying party computing system.

## Claims

### Claim 1

A 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 perform a method for sending a message that includes an encrypted claim about a decentralized identity to a relying party computing system such that the encrypted claim cannot be decrypted without a user associated with the decentralized identifier providing a validation code to the relying party computing system, the method comprising:
generating a validation data structure associated with a decentralized identifier;
causing the validation data structure to be presented to a user that owns the decentralized identifier;
encrypting a claim that has the decentralized identifier as a subject, the encryption using the validation data structure associated with the decentralized identifier such that decryption of the claim requires the validation data structure;
generating a message that includes the encrypted claim, but which does not include the validation data structure;
causing the message to be transmitted to a relying party computing system that will rely on the claim, wherein the relying party computing system cannot decrypt the claim until the user provides the validation data structure to the relying party computing system.

### Claim 2 (depends on 1)

The computing system in accordance with claim 1, the validation data structure comprising a validation code.

### Claim 3 (depends on 2)

The computing system in accordance with claim 2, the validation code being pseudo-randomly generated.

### Claim 4 (depends on 2)

The computing system in accordance with claim 2, the validation code comprising a sequence of characters.

### Claim 5 (depends on 2)

The computing system in accordance with claim 2, the validation code comprising a barcode.

### Claim 6 (depends on 5)

The computing system in accordance with claim 5, the barcode being a matrix barcode.

### Claim 7 (depends on 2)

The computing system in accordance with claim 2, the validation code comprising an audio signature.

### Claim 8 (depends on 1)

The computing system in accordance with claim 1, the validation data structure comprising a file.

### Claim 9 (depends on 1)

The computing system in accordance with claim 1, the encryption also using a public key of a relying party associated with the relying party computing system.

### Claim 10 (depends on 1)

The computing system in accordance with claim 1, the validation data structure being generated by a user agent of the decentralized identifier.

### Claim 11

A method for sending a message that includes an encrypted claim about a decentralized identity to a relying party computing system such that the encrypted claim cannot be decrypted without a user associated with the decentralized identifier providing a validation code to the relying party computing system, the method comprising:
generating a validation data structure associated with a decentralized identifier;
causing the validation data structure to be presented to a user that owns the decentralized identifier;
encrypting a claim that has the decentralized identifier as a subject, the encryption using the validation data structure associated with the decentralized identifier such that decryption of the claim requires the validation data structure;
generating a message that includes the encrypted claim, but which does not include the validation data structure;
causing the message to be transmitted to a relying party computing system that will rely on the claim, wherein the relying party computing system cannot decrypt the claim until the user provides the validation data structure to the relying party computing system.

### Claim 12 (depends on 11)

The method in accordance with claim 11, the validation data structure comprising a validation code.

### Claim 13 (depends on 12)

The method in accordance with claim 12, the validation code being pseudo-randomly generated.

### Claim 14 (depends on 11)

The method in accordance with claim 11, the encryption also using a public key of a relying party associated with the relying party computing system.

### Claim 15 (depends on 11)

The method in accordance with claim 11, the method being performed by a user agent running on a computing system in possession of the user.

### Claim 16 (depends on 11)

The method in accordance with claim 11, the method further comprising:
communicating, by the user, the validation data structure to the relying party computing system using a different communication channel that is used to communicate the message.

### Claim 17

A 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 perform a method for decrypting a claim about a decentralized identity, the method comprising:
detecting receipt of a message that includes an encrypted claim that has a decentralized identity as a subject, the encrypted claim being encrypted using a validation data structure associated with the decentralized identifier, but the message not including the validation data structure; and
detecting separate receipt of the validation code associated with the decentralized identifier from a user that owns the decentralized identifier, the validation code being received over a different communication channel than was used to receive the message that includes the encrypted claim;
using the validation data structure to decrypt the encrypted claim.

### Claim 18 (depends on 17)

The computing system in accordance with claim 17, the communication channel used to receive the message being with a first computing system in possession of the user that owns the decentralized identity, the communication channel used to receive the validation data structure being with a second computing system in possession of the user that owns the decentralized identity.

### Claim 19 (depends on 17)

The computing system in accordance with claim 17, the first computing system running a user agent of the decentralized identity.

### Claim 20 (depends on 17)

The computing system in accordance with claim 17, the decryption also using the private key of a relying party associated with the computing system.
