# US 2021/0342811 A1 · Systems and methods for using information from wearable devices

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

- Number: US 2021/0342811 A1
- Document ID: US20210342811A1
- Status: Published application
- Kind: A1
- Application number: 16/864,966
- Filed: 2020-05-01
- Published: 2021-11-04
- Earliest claimed: 2020-05-01
- Assignees: Capital One Services, LLC
- Applicants: Capital One Services, LLC
- Inventors: Rajko ILINCIC; Jeffrey RULE; Daniel HERRINGTON
- Web page: https://patentgrep.com/patent/US20210342811A1

## CPC

- G06Q 20/102: {Bill distribution or payments}
- G06Q 20/321: {using wearable devices}
- A61B 5/0002: {Remote monitoring of patients using telemetry, e.g. transmission of vital signals via a communication network (endoradiosondes A61B5/07)}
- A61B 5/117: Identification of persons (methods or arrangements for recognising patterns, e.g. fingerprints, G06F18/00, G06V40/00; identification of persons by analysing their voice or speech G10L17/00)
- A61B 5/681: {Wristwatch-type devices}
- G06Q 20/204: {comprising interface for record bearing medium or carrier for electronic funds transfer or payment credit}
- G06Q 20/206: {comprising security or operator identification provisions, e.g. password entry}
- G06Q 20/40145: {Biometric identity checks}
- G06Q 20/4016: {involving fraud or risk level assessment in transaction processing}
- G06Q 20/4097: {using mutual authentication between devices and transaction partners}
- A61B 5/02438: {with portable devices, e.g. worn by the patient}
- 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
- A61B: DIAGNOSIS; SURGERY; IDENTIFICATION (usefulness limited to only animals A61D)

## Abstract

Systems and methods for the of use information from application programming interfaces on wearable devices in third party applications are provided. A system comprising a user device, data storage, an application programming interface and an application is provided. In this system, there is a user device that includes a health monitor. The health monitor includes sensors and associated software that enable it to obtain health information about the wearer of the user device. In this system, there is data storage on the user device that stores the health information as user health data. In this system, there is an application programming interface on the user device that enables the health monitor to share the user health data with other applications executing on the user device.

## Claims

### Claim 1

A system, comprising:
a user device that includes a health monitor, the health monitor including sensors and associated software that enable the health monitor to obtain health information about a wearer of the user device;
data storage on the user device that stores the health information as user health data;
an application programming interface on the user device that enables the health monitor to share the user health data with other applications executing on the user device;
an application that executes a query on the user device to obtain a user device identifier and the user health data, determines, using the user health data, the presence or absence of requisite health data, and transmits the user device identifier and a signal indicating the presence or absence of the requisite health data to a server, wherein:
upon receipt of the user device identifier and signal indicating the presence or absence of the requisite health data, the server identifies a user account based on the user device identifier and either enables transaction authentication if the signal indicates the presence of health data or disables transaction authentication if the signal indicates the absence of health data.

### Claim 2 (depends on 1)

The system of claim 1, further comprising:
a mobile device that is wirelessly connected to the user device, wherein
the user device transmits the user device identifier and signal indicating the presence or absence of the requisite health data to the mobile device, and
upon receipt of the user device identifier and signal indicating the presence or absence of the requisite health data the mobile device, the mobile device transmits the user device identifier and signal indicating the presence or absence of the requisite health data to the server.

### Claim 3 (depends on 1)

The system of claim 1, wherein the query is a long-running query that executes on an anonymous background queue on the user device, the application receives an update when the requisite health data changes, and upon receipt of the update, the application transmits the user device identifier and a change of status signal to the server.

### Claim 4 (depends on 1)

The system of claim 1, wherein the user device is a smart watch that detects and stores a vital sign of the wearer of the smart watch as health information.

### Claim 5 (depends on 4)

The system of claim 4, wherein, the health monitor includes a heart rate sensor, the user health data is sample heart rate data, the server is associated with a bank backend system, and the server approves a transaction if the user device is detecting a heart rate at the time of the transaction.

### Claim 6 (depends on 1)

The system of claim 1, wherein signal indicating the presence or absence of the requisite health data is a Boolean flag.

### Claim 7 (depends on 1)

The system of claim 1, wherein, via a user device registration process, the server stores the user device identifier at the server and thereby associates the user device with a user account of the wearer of the user device.

### Claim 8 (depends on 7)

The system of claim 7, wherein, upon receipt of the user device identifier and signal indicating the presence or absence of the requisite health data, the server compares the received user device identifier with the stored user device identifier, and, if the received and stored user identifiers are the same, either enables transaction authentication if the signal indicates the presence of health data or disables transaction authentication if the signal indicates the absence of health data.

### Claim 9 (depends on 1)

The system of claim 1, wherein the server receives a transaction request from a point of sale terminal, identifies a user account based on information received with the transaction request, determines whether transaction authentication is enabled or disabled for the user account, and either transmits a signal approving the transaction request if transaction authentication is enabled or transmits a signal denying the transaction request if transaction authentication is disabled.

### Claim 10

A method, comprising:
storing, in a database of a backend system, a plurality of user accounts, each user account including user account information that includes information to identify the account holder, an account holder wearable device identifier, and a flag that indicates whether transactions are to be approved or denied based on the respective presence or absence of a vital sign of the account holder that is detected by a wearable device identified by the account holder wearable device identifier;
providing, for execution on the wearable device that includes a health monitor, an application that:
queries, via an application programming interface to the health monitor, the wearable device to obtain a wearable device identifier and health data that indicates the presence or absence of a vital sign of the wearer of the wearable device, and
wirelessly transmits the wearer's wearable device identifier and health data that indicates the presence or absence of the wearer's vital sign to the backend system;
receiving, at the backend system, wearer's wearable device identifier and health data that indicates the presence or absence of the wearer's vital sign;
determining, using a processor at the backend system, whether the wearer's wearable device identifier matches the account holder wearable device identifier;
if the wearer's wearable device identifier matches the account holder wearable device identifier:
accessing, using the processor at the backend system, the account holder user account, and
setting, using the processor at the backend system, the flag stored in the account holder user account that indicates whether transactions are to be approved or denied based on the received health data that indicates the presence or absence of the wearer's vital sign.

### Claim 11 (depends on 10)

The method of claim 10, further comprising:
receiving, at the backend system, a transaction approval request from a point of sale terminal;
identifying, using the processor at the backend system, an account holder user account based on information received with the user account;
querying, using the processor at the backend system, the account holder user account to determine whether the flag stored in the account holder user account indicates whether to approve or deny; and
transmitting, based on the query result, a signal approving or denying the transaction to the point of sale terminal.

### Claim 12 (depends on 10)

The method of claim 10, further comprising:
providing, for execution on a mobile device wirelessly connected to the wearable device, an application that:
receives, via the wireless connection to the wearable device, the wearer's wearable device identifier and health data that indicates the presence or absence of the wearer's vital sign to the backend system, and
wirelessly transmits the received wearer's wearable device identifier and health data to the backend system.

### Claim 13 (depends on 10)

The method of claim 10, wherein the query made by the application executing on the wearable device via the application programming interface is a long-running query that executes on an anonymous background queue on the wearable device, the application receives an update when the health data changes, and upon receipt of the update, the application wirelessly transmits the wearer's wearable device identifier and a change of status signal to the backend system.

### Claim 14 (depends on 10)

The method of claim 10, further comprising:
providing to the account holder, via a network, a registration interface that receives and transmits to the backend system, via the network, the account holder wearable device identifier; and
storing, in the database of the backend system, the account holder wearable device identifier in the account holder user account.

### Claim 15 (depends on 14)

The method of claim 14, further comprising:
receiving, via the registration interface, a user preference indicator from the account holder that indicates the account holder preference to approve or deny transactions based on the respective presence or absence of a vital sign of the account holder at the time of a transaction; and
enabling the flag in the account holder user account.

### Claim 16 (depends on 10)

The method of claim 10, wherein the wearable device is a smart watch that senses the wearer's heart rate and the vital sign is the wearer's heart rate.

### Claim 17 (depends on 16)

The method of claim 16, wherein the processor at the backend system sets the flag to approve transactions when the received health data that indicates that the smart watch is sensing the wearer's heart rate.

### Claim 18 (depends on 16)

The method of claim 16, wherein the processor at the backend system sets the flag to deny transactions when the received health data that indicates that the smart watch is not sensing the wearer's heart rate.

### Claim 19 (depends on 10)

The method of claim 10, wherein the flag is a binary flag.

### Claim 20

A system, comprising:
a wireless wearable device communication interface that communicates, via a network, with a wearable device having a wearable device identifier to receive the wearable device identifier and a signal that indicates that the wearable device is detecting a vital sign of the wearer of the wearable device;
a transaction processor that approves or denies transaction requests;
a database that stores a plurality of user accounts, wherein each user account includes information that identifies the account holder, an account holder wearable device identifier, and a user preference indicator that indicates whether the transaction processor is to approve or deny a request based on the respective presence or absence of a vital sign of the account holder that is detected by the wearable device identified by the account holder wearable device identifier; and
a transaction request communication interface that receives a transaction request from a point of sale terminal, wherein:
when the transaction request communication interface receives the transaction request from the point of sale terminal, the transaction processor identifies a user account based on information received with the user account, queries the account holder user account to determine whether user preference indicator stored in the account holder user account indicates whether to approve or deny the transaction, and transmits, based on the query result, a signal, via the transaction request communication interface, approving or denying the transaction to the point of sale terminal, and
the wearable device includes an application that queries, via an application programming interface, the wearable device to obtain a wearable device identifier and signal that signal that indicates that the wearable device is detecting a vital sign of the wearer of the wearable device and wirelessly transmits the wearable device identifier and signal to the wireless wearable device communication interface.