# US 2021/0344662 A1 · System and Method for Identity Management

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

- Number: US 2021/0344662 A1
- Document ID: US20210344662A1
- Status: Published application
- Kind: A1
- Application number: 17/330,916
- Filed: 2021-05-26
- Published: 2021-11-04
- Earliest claimed: 2013-08-23
- Assignees: MorphoTrust USA, LLC
- Applicants: MorphoTrust USA, LLC
- Inventors: Stephen Miu
- Web page: https://patentgrep.com/patent/US20210344662A1

## CPC

- H04L 63/08: {for authentication of entities (cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32)}
- G06F 21/31: User authentication
- G06F 21/44: Program or device authentication
- G06F 21/577: {Assessing vulnerabilities and evaluating computer system security}
- G06F 21/6218: {to a system of files or objects, e.g. local or distributed file system or database}
- G06Q 20/384: {using social networks}
- G06Q 20/401: {Transaction verification}
- G06Q 20/4014: {Identity check for transactions}
- G06Q 20/4016: {involving fraud or risk level assessment in transaction processing}
- H04L 63/105: {Multiple levels of security}
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- 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

Some implementations may provide a machine-assisted method for determining trustworthiness of a requested transaction, the method including: receiving, from a relying party, a request to determine a trustworthiness of a particular transaction request, the transaction request initially submitted by a user to access data managed by the relying party; based on the transaction request, summarizing the particular transaction request into transactional characteristics, the transactional characteristics devoid of source assets of the transaction, the source assets including credential information of the user, the credential information of the relying party, or information content of the requested transaction; generating first machine readable data encoding transactional characteristics of the underlying transaction as requested, the transactional characteristics unique to the particular transaction request; submitting a first inquiry at a first engine to determine an access eligibility of the user submitting the transaction request, the first inquiry including the credential information of the submitting user, as well as the summarized transactional characteristics that is applicable only once to the underlying transaction request; and receiving the access eligibility determination from the first engine.

## Claims

### Claim at position 1

-20. (canceled)

### Claim 21

A computer system comprising at least one non-transitory storage device and at least one processor coupled thereto, the computer system hosting an authenticating server and configured to perform operations of:
receiving, from a relying party, a request to determine a trustworthiness of a particular transaction request, the transaction request initially submitted by a user to access data managed by the relying party;
based on the transaction request, summarizing, by the authenticating server, the particular transaction as requested into transactional characteristics to obviate details of the particular transaction, the transactional characteristics devoid of source assets of the transaction, the source assets including credential information of the user, the credential information of the relying party, or information content of the requested transaction;
generating first machine-readable data encoding the summarized transactional characteristics of the underlying transaction as requested, the transactional characteristics unique to the particular transaction request such that the transactional characteristics provide one and only one match when used to validate an otherwise valid transaction request;
submitting a first inquiry at a first engine to determine an access eligibility of the user submitting the transaction request, the first inquiry including the credential information of the submitting user, as well as the summarized transactional characteristics that is applicable only once to the underlying transaction request; and
receiving the access eligibility determination from the first engine, wherein the access eligibility determination factors in a validity of the particular transaction request as determined, at least in part, by virtue of the summarized transactional characteristics being matched.

### Claim 22 (depends on 21)

The computer system of claim 21, wherein the operations further comprise:
causing a second inquiry to be submitted at a second engine to validate the particular transaction request, wherein the second inquiry is formed to include the summarized transactional characteristics.

### Claim 23 (depends on 21)

The computer system of claim 21, wherein the operations further comprise:
logging, at a transaction database associated with a second engine, an entry for the particular transaction request by storing the first machine-readable data encoding the transactional characteristics of the particular transaction request.

### Claim 24 (depends on 23)

The computer system of claim 23, wherein storing the first machine-readable data encoding the transactional characteristics of the particular transaction request includes receiving confirmation that the first machine-readable data has been stored at the transaction database associated with the second engine.

### Claim 25 (depends on 24)

The computer system of claim 24, wherein receiving confirmation comprises receiving the confirmation that the first machine-readable data has been stored at the transaction database associated with the second engine before submitting the first inquiry at the first engine.

### Claim 26 (depends on 23)

The computer system of claim 23, wherein storing the first machine-readable data encoding the transactional characteristics of the particular transaction request includes storing the first machine-readable data for only one retrieval query at the transaction database.

### Claim 27 (depends on 23)

The computer system of claim 23, wherein storing the first machine-readable data encoding the transactional characteristics of the particular transaction request includes storing the first machine-readable data for a retrieval query within a time window at the transaction database.

### Claim 28 (depends on 21)

The computer system of claim 21, wherein the operations further comprise:
determining the trustworthiness of the transaction request initially submitted by the user based on the determined access eligibility of the submitting user; and
notifying the relying party of the determined trustworthiness of the transaction request.

### Claim 29 (depends on 21)

The computer system of claim 21, wherein the operations further comprise:
logging, at an identity database associated with the authenticating server, an entry of the received access eligibility determination as well as the determined trustworthiness of the transaction request.

### Claim 30 (depends on 21)

The computer system of claim 21, wherein the operations further comprise:
in response to the relying party proceeding with the requested particular transaction, generating second machine-readable data encoding transactional characteristics of the particular transaction as consummated, the transactional characteristics of the particular consummated transaction devoid of source assets of the consummated transaction, the source assets including credential information of the user, the credential information of the relying party, or information content of the transaction as consummated.

### Claim 31 (depends on 30)

The computer system of claim 30, wherein the operations further comprise:
logging, at an identity database associated with the authenticating server, an entry of the particular consummated transaction by storing the second machine-readable data encoding the transactional characteristics of the particular consummated transaction such that the transactional characteristics of the particular consummated transaction provide one and only one match when used to validate a consummated transaction.

### Claim 32 (depends on 22)

The computer system of claim 22, wherein the operations further comprise:
obtaining, from the received trustworthiness determination request, credential information attesting to an identity of the submitting user; and
generating an electronic credential of the submitting user that is unique to the particular transaction request initially submitted by the user.

### Claim 33 (depends on 32)

The computer system of claim 32, wherein the operations further comprise:
causing the electronic credential to be stored at an identity database associated with a first engine.

### Claim 34 (depends on 33)

The computer system of claim 33, wherein causing the second inquiry to be submitted further comprises:
submitting data encoding the electronic credential at a second engine.

### Claim 35 (depends on 33)

The computer system of claim 33, wherein the operations further comprise:
causing the second engine to render the access eligibility determination by verifying the electronic credential at the identity database associated with the first engine.

### Claim 36 (depends on 21)

The computer system of claim 21, wherein generating the first machine-readable data further comprises: generating a bar code, an alphanumeric string, or a QR code encoding the transactional characteristics.

### Claim 37 (depends on 21)

The computer system of claim 21, wherein the operations further comprise:
prior to submitting the first inquiry, submitting an initial query at a second engine to establish a status of the relying party in processing transaction requests submitted by the user.

### Claim 38 (depends on 37)

The computer system of claim 37, wherein submitting the initial query to establish the status includes submitting the initial query to determine if the transaction request is permitted between the user and the relying party.

### Claim 39 (depends on 37)

The computer system of claim 37, wherein submitting the initial query to establish the status includes submitting the initial query to determine if the relying party is permitted to access identity databases on behalf of the user.

### Claim 40 (depends on 37)

The computer system of claim 37, wherein the operations further comprise:
in response to query results from the initial query, placing the relying party on a whitelist of the first engine.
