# US 2013/0104198 A1 · Two-factor authentication systems and methods

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

- Number: US 2013/0104198 A1
- Document ID: US20130104198A1
- Status: Published application
- Kind: A1
- Application number: 13/660,976
- Filed: 2012-10-25
- Published: 2013-04-25
- Earliest claimed: 2011-10-25
- Assignees: Toopher, Inc.
- Inventors: Evan Tyler Grim
- Web page: https://patentgrep.com/patent/US20130104198A1

## CPC

- H04L 63/08: {for authentication of entities (cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32)}
- H04W 4/023: {using mutual or relative location information between multiple location based services [LBS] targets or of distance thresholds}
- H04W 12/06: Authentication
- H04W 12/50: Secure pairing of devices
- H04L 2463/082: applying multi-factor authentication
- 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 authenticating defined user actions over a computer network. An authentication service receives an authentication request from an authenticating service to perform an action on behalf of a user. The authentication service then sends a permission request to a mobile device associated with the user, asking the user whether or not the action should be allowed. The user sends a permission response via the mobile device to the authentication service, granting or denying the action. The user may automate future similar responses so long as at least one automation criterion is met (e.g., the physical location of the mobile device), eliminating the need to manually provide a response to future permission requests. Information necessary to determine whether the automation criterion is met is stored locally on the mobile device.

## Claims

### Claim 1

A method of authentication, comprising:
receiving an authentication request from an authenticating service to perform an action on behalf of a user;
sending a permission request to a mobile device associated with said user to grant or deny permission to perform said action;
sending a permission response to said authenticating service; and
providing said user with an option to automate said permission response, wherein future permission requests meet at least one automation criterion.

### Claim 2 (depends on 1)

The method of claim 1, further comprising automating said permission response to future permission requests without prompting said user to grant or deny said future permission requests if said user has selected said option to automate.

### Claim 3 (depends on 2)

The method of claim 2, further comprising prompting said user to grant or deny said future permission requests if said at least one automation criterion is not met or if said user has not selected said option to automate.

### Claim 4 (depends on 1)

The method of claim 1, wherein information determining whether said at least one automation criterion is met is stored on said mobile device.

### Claim 5 (depends on 1)

The method of claim 1, wherein said at least one criterion comprises proximity of said mobile device to a geographic location.

### Claim 6 (depends on 1)

The method of claim 1, wherein said at least one criterion comprises proximity of said mobile device to one of a plurality of geographic locations.

### Claim 7 (depends on 1)

The method of claim 1, wherein said action comprises logging on to a web site of said authenticating service.

### Claim 8 (depends on 1)

The method of claim 1, wherein said action comprises a critical action as defined by said authenticating service.

### Claim 9 (depends on 1)

The method of claim 1, wherein said action comprises a transfer of funds.

### Claim 10 (depends on 1)

The method of claim 1, further comprising pairing said mobile device with said authenticating service.

### Claim 11 (depends on 10)

The method of claim 10, wherein said pairing comprises establishing a shared secret between said mobile device and said authenticating service.

### Claim 12 (depends on 11)

The method of claim 11, wherein permission response includes a one-time-password.

### Claim 13 (depends on 10)

The method of claim 10, wherein said pairing comprises establishing a unique pairing identifier between said mobile device and said authenticating service, said authentication request being automatically denied if said pairing identifier is not present with said authentication request.

### Claim 14 (depends on 1)

The method of claim 1, further comprising pre-seeding said permission response when said at least one automation criterion changes states.

### Claim 15 (depends on 1)

The method of claim 1, wherein said permission request comprises a designator of said authenticating service, an action description, a user name, a terminal description.

### Claim 16

A system for authentication, comprising:
at least one processor;
at least one memory element storing instructions for controlling said at least one processor to perform steps comprising:
receiving an authentication request from an authenticating service to perform an action on behalf of a user;
sending a permission request to a mobile device associated with said user to grant or deny permission to perform said action;
sending a permission response to said authenticating service;
providing said user with an option to automate said permission response, wherein future permission requests meet at least one automation criterion; and
automating said permission response to future permission requests without prompting said user to grant or deny said future permission requests if said user has selected said option to automate.

### Claim 17 (depends on 16)

The system of claim 16, wherein information determining whether said at least one automation criterion is met is stored on said mobile device.

### Claim 18

A non-transitory computer-readable medium including one or more sequences of instructions which, when executed by one or more processors, causes said one or more processors to perform the steps comprising:
receiving an authentication request from an authenticating service to perform an action on behalf of a user;
sending a permission request to a mobile device associated with said user to grant or deny permission to perform said action;
sending a permission response to said authenticating service;
providing said user with an option to automate said permission response, wherein future permission requests meet at least one automation criterion; and
automating said permission response to future permission requests without prompting said user to grant or deny said future permission requests if said user has selected said option to automate.

### Claim 19 (depends on 18)

The non-transitory computer-readable medium of claim 18, wherein information determining whether said at least one automation criterion is met is stored on said mobile device.

### Claim 20

A mobile device for authenticating a permission request from an authenticating service, said mobile device including a processor and operable to perform operations comprising:
receiving a permission request from an authentication service terminal;
presenting information related to said permission request;
receiving sensory input from a user to determine a permission response;
sending said permission response to said authentication service terminal; and
receiving sensory input from a user that selects whether to automate a permission response for future permission requests when at least one automation criterion is met, such that future permission responses do not require sensory input from said user,
wherein information necessary to determine whether said at least one automation criterion is met is stored on said mobile device.
