# US 12,216,800 B2 · Systems and methods for use in imposing a common domain

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

- Number: US 12,216,800 B2
- Document ID: US12216800B2
- Status: Granted
- Kind: B2
- Application number: 18/079,798
- Filed: 2022-12-12
- Published: 2023-07-13
- Granted: 2025-02-04
- Earliest claimed: 2022-01-07
- Assignees: Mastercard International Incorporated
- Applicants: Mastercard International Incorporated
- Inventors: Tomasz Blachowicz; Harjender Singh; Edward Neil Livingston; Holger Kunkat; Ryan Watkins; Michael D. McCarthy; Maurice David Liscia
- Web page: https://patentgrep.com/patent/US12216800B2

## CPC

- G06F 21/6263: {during internet communication, e.g. revealing personal data from cookies}
- H04L 63/0807: {using tickets, e.g. Kerberos (cryptographic mechanisms or cryptographic arrangements for entity authentication using tickets or tokens H04L9/3213)}
- H04L 63/0815: {providing single-sign-on or federations}
- H04L 63/102: {Entity profiles}
- 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

Systems and methods are provided for use in implementing a common domain to provide recognition of users. One example computer-implemented method includes receiving a recognition token associated with a profile and setting, via a browser accessing a common domain, a cookie in the browser where the cookie includes a recognition token. The method also includes, in response to a request for a service, via a user, through the browser accessing an entity domain associated with an entity, accessing the common domain and accessing, via the browser accessing the common domain, the cookie and submitting the cookie to a common domain server. The method further includes receiving, from the common domain server, a federated ID token associated with the recognition token for the service and retrieving, via the browser, the profile associated with the user based on the federated ID token.

## Claims

### Claim 1

A computer-implemented method for use in implementing a common domain for user recognition in a browser, the method comprising:
receiving, by a computing device, a recognition token associated with a profile;
setting, by the computing device, via a browser accessing a common domain, a cookie in the browser, the cookie including the recognition token;
in response to a request for a service, via a user, through the browser accessing an entity domain associated with an entity, accessing, by the computing device, the common domain;
accessing, by the computing device, via the browser accessing the common domain, the cookie and submitting the cookie to a common domain server;
receiving, from the common domain server, a federated ID token associated with the recognition token for the service; and
retrieving, by the computing device, via the browser, the profile associated with the user based on the federated ID token, thereby permitting the computing device to initiate an interaction with the entity, via the browser accessing the entity domain, based on a credential included in the profile.

### Claim 2 (depends on 1)

The computer-implemented method of claim 1, wherein the browser is restricted from permitting access to cookies by a domain other than the common domain.

### Claim 3 (depends on 1)

The computer-implemented method of claim 1, wherein the service includes a secure remote commerce (SRC) service; and
wherein the profile includes a SRC profile specific to a provider of said service.

### Claim 4 (depends on 3)

The computer-implemented method of claim 3, wherein the cookie includes a name of the common domain and/or an expiration date for the recognition token.

### Claim 5 (depends on 3)

The computer-implemented method of claim 3, further comprising initiating the interaction by submitting at least part of the SRC profile to the provider.

### Claim 6 (depends on 1)

The computer-implemented method of claim 1, wherein the common domain is associated with a common domain server; and
wherein the method further comprises:
receiving, by the common domain server, the cookie from the computing device;
identifying a provider based on the cookie;
retrieving, by the common domain server, the federated ID token from the identified provider based on the recognition token included in the cookie; and
returning, by the common domain server, the federated ID token to the computing device.

### Claim 7 (depends on 1)

The computer-implemented method of claim 1, wherein the service is associated with a sub-domain of the common domain.

### Claim 8

A system for use in implementing a common domain for user recognition in a browser, the system comprising a computing device configured to:
receive a recognition token associated with a profile;
set, via a browser accessing a common domain, a cookie in the browser, the cookie including a recognition token;
in response to a request for a service, via a user, through the browser accessing an entity domain associated with an entity, access the common domain;
access, via the browser accessing the common domain, the cookie and submit the cookie to a common domain server;
receive, from the common domain server, a federated ID token associated with the recognition token for the service; and
retrieve, via the browser, the profile associated with the user based on the federated ID token, thereby permitting the computing device to initiate an interaction with the entity, via the browser accessing the entity domain, based on a credential included in the profile.

### Claim 9 (depends on 8)

The system of claim 8, wherein the browser is restricted from permitting access to cookies by a domain other than the common domain.

### Claim 10 (depends on 9)

The system of claim 9, wherein the service includes a secure remote commerce (SRC) service; and
wherein the profile includes a SRC profile specific to a provider of said service.

### Claim 11 (depends on 10)

The system of claim 10, wherein the computing device is configured to initiate the interaction by submitting at least part of the SRC profile to the provider.

### Claim 12 (depends on 9)

The system of claim 9, wherein the cookie includes a name of the common domain and/or an expiration date for the recognition token.

### Claim 13 (depends on 8)

The system of claim 8, further comprising a common domain server associated with the common domain, the common domain server configured to:
receive the cookie from the computing device;
identify a provider based on the cookie;
retrieve the federated ID token from the identified provider based on the recognition token included in the cookie; and
return the federated ID token to the computing device.

### Claim 14 (depends on 8)

The system of claim 8, wherein the service is associated with a sub-domain of the common domain.

### Claim 15

A non-transitory computer-readable storage medium comprising executable instructions, which when executed by at least one processor of a computing device, cause the at least one processor to:
receive a recognition token associated with a profile;
set, via a browser accessing a common domain, a cookie in the browser, the cookie including a recognition token;
in response to a request for a service, via a user, through the browser accessing an entity domain associated with an entity, access the common domain;
access, via the browser accessing the common domain, the cookie and submit the cookie to a common domain server;
receive, from the common domain server, a federated ID token associated with the recognition token for the service; and
retrieve, via the browser, the profile associated with the user based on the federated ID token, thereby permitting the computing device to initiate an interaction with the entity, via the browser accessing the entity domain, based on a credential included in the profile.