# US 12,111,896 B2 · Digital identity sign-up

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

- Number: US 12,111,896 B2
- Document ID: US12111896B2
- Status: Granted
- Kind: B2
- Application number: 18/474,520
- Filed: 2023-09-26
- Published: 2024-03-21
- Granted: 2024-10-08
- Earliest claimed: 2019-06-21
- Assignees: Early Warning Services, LLC
- Applicants: Early Warning Services, LLC
- Inventors: Gregory Slowiak; Eric Woodward; Philip Lam; Jeff Shultz
- Web page: https://patentgrep.com/patent/US12111896B2

## CPC

- G06F 21/31: User authentication
- G06F 21/6209: {to a single file or object, e.g. in a secure envelope, encrypted and accessed using a key, or with access control rules appended to the object itself}
- G06F 21/6263: {during internet communication, e.g. revealing personal data from cookies}
- H04L 9/0819: {Key transport or distribution, i.e. key establishment techniques where one party creates or otherwise obtains a secret value, and securely transfers it to the other(s) (network architectures or network communication protocols for key distribution in a packet data network H04L63/062)}
- H04L 63/0807: {using tickets, e.g. Kerberos (cryptographic mechanisms or cryptographic arrangements for entity authentication using tickets or tokens H04L9/3213)}
- H04L 63/0823: {using certificates (cryptographic mechanisms or cryptographic arrangements for entity authentication involving certificates H04L9/3263)}
- H04L 63/0884: {by delegation of authentication, e.g. a proxy authenticates an entity to be authenticated on behalf of this entity vis-à-vis an authentication entity}
- H04W 12/06: Authentication
- H04W 12/068: {using credential vaults, e.g. password manager applications or one time password [OTP] applications}
- G06F 9/445: Program loading or initiating (bootstrapping G06F9/4401; security arrangements for program loading or initiating G06F21/57)
- G06F 21/305: {by remotely controlling device operation}
- G06Q 40/03: Credit; Loans; Processing thereof
- H04L 41/147: for predicting network behaviour
- H04L 63/0815: {providing single-sign-on or federations}
- H04L 63/0876: {based on the identity of the terminal or configuration, e.g. MAC address, hardware or software configuration or device fingerprint}
- H04L 63/126: {the source of the received data}
- H04L 67/535: {Tracking the activity of the user (network monitoring arrangements H04L43/00; recording of computer activity G06F11/34)}
- 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)
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR

## Abstract

Disclosed herein is an identity network that can provide a universal, digital identity for users that can be used to authenticate the user by an identity provider for relying parties to utilize for confirming the identity of the user during sign-up. The identity network receives a request from a relying party that includes deep linking to an identity provider selected by the user. The request specifies the user and any other information about the user the relying party is requesting. A service of the identity network launches the application for the identity provider on the user's device and the user logs into the identity provider's application, which provides the user authentication/validation and information about the user to the identity network. The identity network can then provide the information to the relying party, which the relying party can rely on for creating an account with the relying party for the user.

## Claims

### Claim 1

A method for using an authenticated digital identity in account creation, the method comprising:
receiving, at an identity network, a sign-up request for a user from a relying party, wherein the sign-up request includes requested information;
in response to receiving the sign-up request, providing, by the identity network to the relying party, a session identifier for the sign-up request;
receiving, by the identity network, a request for details of the sign-up request and the session identifier from an identity provider mobile application associated with an identity provider;
in response to receiving the request for details of the sign-up request, providing, by the identity network, the details of the sign-up request and the session identifier to the identity provider mobile application;
receiving, by the identity network from the identity provider mobile application, the session identifier and consent of the user to provide the requested information to the relying party;
in response to receiving the consent of the user, sending, by the identity network, a request for the requested information to the identity provider, wherein the request for the requested information comprises a device identifier associated with a user device used by the user to provide the consent of the user;
receiving, by the identity network from the identity provider, at least a portion of the requested information and the session identifier; and
transmitting, by the identity network, the at least the portion of the requested information and the session identifier to the relying party.

### Claim 2 (depends on 1)

The method of claim 1, wherein:
the details of the sign-up request comprise at least a portion of the sign-up request.

### Claim 3 (depends on 1)

The method of claim 1, further comprising:
validating, by the identity network, the user; and
transmitting, by the identity network to the relying party, the validation with the at least the portion of the requested information and the session identifier.

### Claim 4 (depends on 3)

The method of claim 3, wherein:
validating the user comprises calculating a confidence score of the user.

### Claim 5 (depends on 1)

The method of claim 1, further comprising:
identifying suspicious activity associated with the user device; and
sending an alert to the identity provider about the suspicious activity, wherein the alert comprises the device identifier.

### Claim 6 (depends on 5)

The method of claim 5, wherein:
identifying the suspicious activity associated with the user device comprises applying one or both of a suspicious activity model and a normal activity model to activity associated with the device identifier.

### Claim 7 (depends on 6)

The method of claim 6, further comprising:
receiving, by the identity network, the activity associated with the device identifier from the identity provider.

### Claim 8

An identity network, comprising:
one or more processors; and
a memory having stored thereon instructions that, upon execution by the one or more processors, cause the one or more processors to:
receive a sign-up request for a user from a relying party, wherein the sign-up request includes requested information;
in response to receiving the sign-up request, provide a session identifier for the sign-up request to the relying party;
receive a request for details of the sign-up request and the session identifier from an identity provider mobile application associated with an identity provider;
in response to receiving the request for details of the sign-up request, provide the details of the sign-up request and the session identifier to the identity provider mobile application;
receive, from the identity provider mobile application, the session identifier and consent of the user to provide the requested information to the relying party;
in response to receiving the consent of the user, send a request for the requested information to the identity provider, wherein the request for the requested information comprises a device identifier associated with a user device used by the user to provide the consent of the user;
receive from the identity provider at least a portion of the requested information and the session identifier; and
transmit the at least the portion of the requested information and the session identifier to the relying party.

### Claim 9 (depends on 8)

The identity network of claim 8, wherein:
the requested information received from identity provider is encrypted using a known encryption key between the identity provider and the identity network; and
the instructions comprise further instructions that, upon execution by the one or more processors, cause the one or more processors to decrypt the requested information prior to transmitting the at least the portion of the requested information and the session identifier to the relying party.

### Claim 10 (depends on 8)

The identity network of claim 8, wherein the instructions comprise further instructions that, upon execution by the one or more processors, cause the one or more processors to:
encrypt the at least the portion of the requested information with a cryptographic key prior to transmitting the at least the portion of the requested information and the session identifier to the relying party.

### Claim 11 (depends on 10)

The identity network of claim 10, wherein the instructions comprise further instructions that, upon execution by the one or more processors, cause the one or more processors to:
transmit the cryptographic key and the session identifier to the relying party.

### Claim 12 (depends on 8)

The identity network of claim 8, wherein the instructions comprise further instructions that, upon execution by the one or more processors, cause the one or more processors to:
identify suspicious activity associated with the user device; and
send an alert to the identity provider about the suspicious activity, wherein the alert comprises the device identifier.

### Claim 13 (depends on 12)

The identity network of claim 12, wherein:
identifying the suspicious activity associated with the user device comprises applying one or both of a suspicious activity model and a normal activity model to activity associated with the device identifier.

### Claim 14 (depends on 13)

The identity network of claim 13, wherein the instructions comprise further instructions that, upon execution by the one or more processors, cause the one or more processors to:
receive the activity associated with the device identifier from the identity provider.

### Claim 15

A non-transitory, computer-readable medium having stored thereon instructions that, upon execution by one or more processors, cause the one or more processors to:
receive a sign-up request for a user from a relying party, wherein the sign-up request includes requested information;
in response to receiving the sign-up request, provide a session identifier for the sign-up request to the relying party;
receive a request for details of the sign-up request and the session identifier from an identity provider mobile application associated with an identity provider;
in response to receiving the request for details of the sign-up request, provide the details of the sign-up request and the session identifier to the identity provider mobile application;
receive, from the identity provider mobile application, the session identifier and consent of the user to provide the requested information to the relying party;
in response to receiving the consent of the user, send a request for the requested information to the identity provider, wherein the request for the requested information comprises a device identifier associated with a user device used by the user to provide the consent of the user;
receive from the identity provider at least a portion of the requested information and the session identifier; and
transmit the at least the portion of the requested information and the session identifier to the relying party.

### Claim 16 (depends on 15)

The non-transitory, computer-readable medium of claim 15, wherein the instructions comprise further instructions that, upon execution by the one or more processors, cause the one or more processors to:
calculate a confidence score of the user based at least in part on the other information; and
transmit the confidence score with the at least the portion of the requested information and the session identifier to the relying party.

### Claim 17 (depends on 15)

The non-transitory, computer-readable medium of claim 15, wherein the instructions comprise further instructions that, upon execution by the one or more processors, cause the one or more processors to:
obtain other information regarding the user from a third party; and
transmit the other information to the relying party.

### Claim 18 (depends on 15)

The non-transitory, computer-readable medium of claim 15, wherein the instructions comprise further instructions that, upon execution by the one or more processors, cause the one or more processors to:
identify suspicious activity associated with the user device; and
send an alert to the identity provider about the suspicious activity, wherein the alert comprises the device identifier.

### Claim 19 (depends on 18)

The non-transitory, computer-readable medium of claim 18, wherein:
identifying the suspicious activity associated with the user device comprises applying one or both of a suspicious activity model and a normal activity model to activity associated with the device identifier.

### Claim 20 (depends on 19)

The non-transitory, computer-readable medium of claim 19, wherein the instructions comprise further instructions that, upon execution by the one or more processors, cause the one or more processors to:
receive the activity associated with the device identifier from the identity provider.