# US 2021/0342477 A1 · Systems and methods for data access control of personal user data using a short-range transceiver

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

- Number: US 2021/0342477 A1
- Document ID: US20210342477A1
- Status: Published application
- Kind: A1
- Application number: 17/307,870
- Filed: 2021-05-04
- Published: 2021-11-04
- Earliest claimed: 2020-04-30
- Assignees: Capital One Services, LLC
- Applicants: Capital One Services, LLC
- Inventors: Rajko ILINCIC; Jeffrey RULE
- Web page: https://patentgrep.com/patent/US20210342477A1

## CPC

- G06F 21/35: communicating wirelessly
- G06F 21/6245: {Protecting personal data, e.g. for financial or medical purposes}
- G06F 21/44: Program or device authentication
- G06F 21/602: {Providing cryptographic facilities or services}
- 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 9/3213: {using tickets or tokens, e.g. Kerberos (network architectures or network communication protocols for entities authentication using tickets in a packet data network H04L63/0807)}
- H04L 9/3226: {using a predetermined code, e.g. password, passphrase or PIN (network architectures or network communication protocols for supporting authentication of entities using passwords in a packet data network H04L63/083)}
- H04L 9/3234: {involving additional secure or trusted devices, e.g. TPM, smartcard, USB or software token (network architectures or network communication protocols for supporting authentication of entities using an additional device in a packet data network H04L63/0853)}
- H04L 63/0807: {using tickets, e.g. Kerberos (cryptographic mechanisms or cryptographic arrangements for entity authentication using tickets or tokens H04L9/3213)}
- H04W 12/033: of the user plane, e.g. user's traffic
- H04W 12/06: Authentication
- H04W 12/08: Access security
- H04L 2209/805: Lightweight hardware, e.g. radio-frequency identification [RFID] or sensor
- 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)

## Abstract

Systems and methods for controlling data access through the interaction of a short-range transceiver, such as a contactless card, with a client device are presented. An exemplary system and method may include establishing a database storing identifiers and keys for users and service providers, receiving from a client device of the service provider, via a network, a service provider token and a request for a data access key, the request generated in response to a tap action between a contactless card associated with a user and the client device, verifying the service provider is authorized to receive access to personal user data encrypted and stored on the contactless card, generating a data access key based on a user key, and transmitting to the service provider client device, via the network, the data access key, such that the client device may decrypt the personal user data obtained from the contactless card.

## Claims

### Claim at position 1

1-20. (canceled)

### Claim 21

A method for controlling data access, comprising:
receiving, from a first client device via a network, a user token, a service provider token, and a request for a data access key to access personal user data stored on a contactless card associated with a user;
identifying a service provider based on the service provider token;
identifying the user based on the user token;
verifying that the service provider is authorized to receive access to personal user data stored on the contactless card;
retrieving a user key associated with the user from a database;
generating the data access key based on the user key; and
transmitting the data access key to the first client device,
wherein the request is generated in response to a tap action between the contactless card and the first client device.

### Claim 22 (depends on 21)

The method of claim 21, wherein the personal user data is encrypted using the user key.

### Claim 23 (depends on 21)

The method of claim 21, wherein the database stores a user identifier associated with the user, a service provider identifier associated with the service provider, and a first service provider key associated with the service provider.

### Claim 24 (depends on 23)

The method of claim 23, wherein the first service provider key is valid for a limited period of time.

### Claim 25 (depends on 23)

The method of claim 23, wherein the data access key is generated based on the user key and the first service provider key.

### Claim 26 (depends on 25)

The method of claim 25, further comprising receiving, from a second client device via the network, a second service provider key, wherein the data access key is generated based on the user key, the first service provider key, and the second service provider key.

### Claim 27 (depends on 26)

The method of claim 26, wherein the second service provider key is transmitted by the second client device in response to a tap action between the contactless card and the second client device.

### Claim 28 (depends on 21)

The method of claim 21, wherein the user token comprises the user key, further comprising authenticating the user based on the user key.

### Claim 29 (depends on 21)

The method of claim 21, wherein the service provider token comprises the service provider key, further comprising authenticating the service provider based on the first service provider key.

### Claim 30 (depends on 21)

The method of claim 21, further comprising identifying the service provider as the sender of the data access key request based on the service provider token.

### Claim 31

A data access control system, comprising:
a server comprising a processor and a memory, the server in data communication with a database and a client device; and
a contactless card associated with a user, the contactless card comprising a processor, a memory, and a communications interface, the memory of the contactless card storing a user token and personal user data associated with the user,
wherein the server is configured to:
receive, from the client device via a network, the user token, a service provider token, and a request for a data access key to access the personal user data,
identify the user based on the user token,
verify the service provider is authorized to receive access to the personal user data,
retrieve the user key from the database,
generate the data access key based on the user key, and
transmit the data access key to the client device,
wherein the request is generated in response to a tap action between the contactless card and the client device.

### Claim 32 (depends on 31)

The data access control system of claim 31, wherein the personal user data is encrypted using the user key.

### Claim 33 (depends on 31)

The data access control system of claim 31, wherein the memory of the contactless card further stores basic user data associated with the user, the basic user data encrypted with a basic service provider key.

### Claim 34 (depends on 33)

The data access control system of claim 33, wherein the sever is further configured to:
identify the service provider based on the service provider token, and generate the basic service provider key based on the identity of the service provider.

### Claim 35 (depends on 33)

The data access control system of claim 33, wherein the basic service provider key is valid only for a predetermined period of time.

### Claim 36 (depends on 35)

The data access control system of claim 35, wherein the database stores a user identifier associated with the user, a service provider identifier associated with the service provider, the service provider key associated with the service provider, and the basic service provider key associated with the service provider.

### Claim 37 (depends on 33)

The data access control system of claim 33, wherein the server is further configured to:
receive a request for the basic service provider key,
verify that the service provider is authorized to receive the basic service provider key,
and
transmit, to the client device, the basic service provider key.

### Claim 38 (depends on 34)

The data access control system of claim 34, wherein the request for the basic service provider key is independent of the tap action between the contactless card and the client device.

### Claim 39 (depends on 33)

The data access control system of claim 33, wherein the server is further configured to log each transmission of the basic service provider key.

### Claim 40

A data access control server, comprising:
a processor; and
a memory,
wherein the processor is in data communication with a database and a first client device, and
wherein, in response to receipt of a user token, a service provider token, and a request for a data access key to access personal user data stored on a contactless card associated with a user, the processor is configured to:
identify the user based on the user token,
verify the service provider is authorized to receive access to the personal user data,
retrieve the user key from the database,
generate the data access key based on the user key, and
transmit the data access key to the first client device,
wherein the request is generated in response to a tap action between the contactless card and the first client device.
