# US 2017/0286957 A1 · Mutual Authentication of a User and Service Provider

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

- Number: US 2017/0286957 A1
- Document ID: US20170286957A1
- Status: Published application
- Kind: A1
- Application number: 15/631,598
- Filed: 2017-06-23
- Published: 2017-10-05
- Earliest claimed: 2010-03-31
- Assignees: Kachyng, Inc.
- Applicants: Kachyng, Inc.
- Inventors: Resh Wallaja
- Web page: https://patentgrep.com/patent/US20170286957A1

## CPC

- G06Q 20/40975: {using encryption therefor}
- G06Q 20/00: Payment architectures, schemes or protocols (apparatus for performing or posting payment transactions G07F7/08, G07F19/00; electronic cash registers G07G1/12)
- G06Q 20/20: Point-of-sale [POS] network systems
- 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/0861: {Generation of secret information including derivation or calculation of cryptographic keys or passwords}
- H04L 9/14: using a plurality of keys or algorithms
- H04L 9/321: {involving a third party or a trusted authority}
- 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/3228: {One-time or temporary data, i.e. information which is sent for every authentication or authorization, e.g. one-time-password, one-time-token or one-time-key}
- H04L 63/0869: {for achieving mutual authentication (cryptographic mechanisms or cryptographic arrangements for mutual authentication H04L9/3273)}
- H04L 63/18: {using different networks or channels, e.g. using out of band channels (cryptographic mechanisms or cryptographic arrangements for key distribution involving distinctive intermediate devices or communication paths H04L9/0827; cryptographic mechanisms or cryptographic arrangements for authentication using a plurality of channels H04L9/3215)}
- H04L 2209/56: Financial cryptography, e.g. electronic payment or e-cash
- 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
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

The present invention relates to a method and system for mutual authentication of a user and service provider, said method comprising acts of: authenticating an event by a key generation module (KGM), said event is generated on a computing device by a user, sending a shared secret of registered user for the event by an authentication server to the key generation module (KGM), generating one time key by the KGM for the event, transmitting the one time key by appending the shared secret to registered user mobile device, and performing at least one of: authenticating the user for said event by the KGM when a registered user enters the one-time key on the computing device within a predetermined time period, or terminating the event upon receipt of predefined key sequence from the mobile device.

## Claims

### Claim 1

A computer-implemented method for authentication of an event, the method comprising:
receiving, at a key generation module (KGM), a notification of an event generated at a computing device;
transmitting the notification of the event to an authentication server;
receiving, at the KGM, from the authentication server, a shared secret provided by a user previously registered for the event;
generating, by the KGM, a one-time key for the event;
appending the shared secret to the one-time key to generate an appended key;
causing the appended key to be transmitted to a mobile device associated with the user previously registered for the event; and
authenticating the event in response to receiving a notification from the computing device within a predetermined time period indicating the one-time key was entered at the computing device.

### Claim 2 (depends on 1)

The method of claim 1, wherein the appended key is transmitted using at least one of Single Data Message Format (SDMF), Multiple Data Message Format (MDMF), Unstructured Supplementary Services Data (USSD), 3G video over voice, interactive voice response (IVR), placed telephone call and general packet radio service (GPRS).

### Claim 3 (depends on 1)

The method of claim 1, wherein the computing device is a point of sale terminal (POS) and the event is initiated in response to a credit card being read by the POS.

### Claim 4 (depends on 1)

The method of claim 1, wherein transmitting the appended key to the mobile device comprises invoking automatically a mobile application on the mobile device to render the appended key.

### Claim 5 (depends on 1)

The method of claim 1, wherein the shared secret is at least one of an image, a sound, a word, a phrase, a video, a number, and an alphanumeric word.

### Claim 6 (depends on 1)

The method of claim 1, wherein the one-time key is at least one of a symbol, an alphanumeric word, and a number.

### Claim 7 (depends on 1)

The method of claim 1, further comprising terminating the event responsive to receiving a notification from the computing device indicating that an invalid key was entered at the computing device, wherein the invalid key is different from the one-time key.

### Claim 8 (depends on 7)

The method of claim 7, wherein the invalid key includes a predefined key sequence known to the user previously registered for the event.

### Claim 9 (depends on 8)

The method of claim 8, further comprising receiving the predefined key sequence from the mobile device associated with the user previously registered for the event.

### Claim 10 (depends on 7)

The method of claim 7, further comprising locking an account associated with the user previously registered for the event.

### Claim 11

A method for authentication of an event, the method comprising:
receiving, at a key generation module (KGM), a notification of an event generated at a computing device;
transmitting the notification of the event to an authentication server;
receiving, at the KGM, from the authentication server, a shared secret provided by a user previously registered for the event;
generating, by the KGM, a one-time key for the event;
appending the shared secret to the one-time key to generate an appended key;
causing the appended key to be transmitted to a mobile device associated with the user previously registered for the event; and
responsive to receiving a notification within a predetermined time period indicating the one-time key was entered at the computing device, authenticating the event.

### Claim 12 (depends on 11)

The method of claim 11, wherein the appended key is transmitted using at least one of Single Data Message Format (SDMF), Multiple Data Message Format (MDMF), Unstructured Supplementary Services Data (USSD), 3G video over voice, interactive voice response (IVR), placed telephone call and general packet radio service (GPRS).

### Claim 13 (depends on 11)

The method of claim 11, wherein the computing device is a point of sale terminal (POS) and the event is initiated in response to a credit card being read by the POS.

### Claim 14 (depends on 11)

The method of claim 11, wherein transmitting the appended key to the mobile device comprises invoking automatically a mobile application on the mobile device to render the appended key.

### Claim 15 (depends on 11)

The method of claim 11, wherein the shared secret is at least one of an image, a sound, a word, a phrase, a video, a number, and an alphanumeric word.

### Claim 16 (depends on 11)

The method of claim 11, wherein the one-time key is at least one of a symbol, an alphanumeric word, and a number.

### Claim 17 (depends on 11)

The method of claim 11, further comprising terminating the event responsive to receiving a notification from the computing device indicating that an invalid key was entered at the computing device, wherein the invalid key is different from the one-time key.

### Claim 18 (depends on 17)

The method of claim 17, wherein the invalid key includes a predefined key sequence known to the user previously registered for the event.

### Claim 19 (depends on 18)

The method of claim 18, further comprising receiving the predefined key sequence from the mobile device associated with the user previously registered for the event.

### Claim 20 (depends on 17)

The method of claim 17, further comprising locking an account associated with the user previously registered for the event.
