US 10,594,485 B2Granted

System, method, program, and recording medium storing program for authentication

AssigneeISAO Corporation

InventorsToshiki Maezawa, Takahiro Nishida, Hiroyuki Kikuchi, Hiroyuki Torii

Life of this patent

Estimating the term…

Loading patent…

Abstract

An authentication system includes first and second terminals, and an authentication subsystem. The authentication subsystem: generates a first token based on reception of a code image authentication start request, generates and stores a code image key in association with the first token, generates and stores a code image including the code image key at a URL of the storage unit, transmits the first token and the URL to the first terminal, registers the received first token as a key in an information transmitting and receiving unit, checks whether a received ID of the second terminal is a unique ID, when the received unique ID of the second terminal is the unique ID, checks whether the received code image key is stored in the storage unit, and transmits a first response code to the information transmitting and receiving unit using, as a key.

Claims26

Dependent claims

An authentication system comprising:

an authentication subsystem, the authentication subsystem comprising at least one first processor, at least one second processor and at least one storage;
a first terminal, the first terminal transmitting a code image authentication start request and authentication start trigger information to the at least one first processor in response to a trigger of an authentication start to the first terminal;
and
a second terminal, wherein
the at least one first processor:
generates a first token based on reception of the code image authentication start request;
generates a code image key and stores in the at least one storage the code image key in association with the first token;
generates a code image including the code image key and stores the code image at a predetermined URL of the at least one storage;
and
transmits the first token and the URL at which the code image is stored to the first terminal;
the first terminal accesses the URL received from the at least one first processor and acquires the code image, displays the code image on a screen of the first terminal, and transmits the received first token to the at least one first processor by asynchronous communication,
the at least one first processor registers the first token received from the first terminal as a key in the at least one second processor,
the second terminal reads the code image displayed on the screen of the first terminal, acquires the code image key, and transmits a login request, a unique ID of the second terminal, and the code image key to the at least one first processor,
the at least one first processor i) checks whether the received unique ID of the second terminal is a unique ID of the second terminal registered in advance, and ii) when the received unique ID of the second terminal is the unique ID of the second terminal registered in advance, checks whether the received code image key is stored in the at least one storage, and
when the received code image key is stored in the at least one storage,
the at least one first processor retrieves the first token stored in the at least one storage using the received code image key as a key, and transmits a first response code to the at least one second processor using the first token as a key,
the at least one second processor transmits the first response code to the at least one first processor that registers the first token as the key in the at least one second processor, and
the at least one first processor transmits the received first response code to the first terminal by the asynchronous communication.

15 more elements

An authentication subsystem comprising:

at least one first processor;
at least one second processor;
and
at least one storage;
wherein
the at least one first processor is configured to:
receive a code image authentication start request and authentication start trigger information from a first terminal;
generate a first token based on reception of the code image authentication start request;
generate a code image key and stores in the at least one storage the code image key in association with the first token;
generate a code image including the code image key and stores the code image at a predetermined URL of the at least one storage;
transmit the first token and the URL at which the code image is stored to the first terminal;
register the first token received from the first terminal, which receives the first token from the at least one first processor, as a key in the at least one second processor;
receive a login request, a unique ID of a second terminal, and the code image key from the second terminal, which reads the code image displayed on a screen of the first terminal and acquires the code image key, the first terminal accessing the received URL and acquiring the code image;
check whether the received unique ID of the second terminal is a unique ID of the second terminal registered in advance;
when the received unique ID of the second terminal is the unique ID of the second terminal registered in advance, check whether the received code image key is stored in the at least one storage;
and
when the received code image key is stored in the at least one storage, retrieve the first token stored in the at least one storage using the received code image key as a key, and transmit a first response code to the at least one second processor using, as a key, the first token retrieved from the at least one storage using the received code image key as a key;
the at least one second processor is configured to transmit the first response code to the at least one first processor that registers the first token as the key in the at least one second processor, and
the at least one first processor is configured to transmit the first response code received from the at least one second processor to the first terminal by asynchronous communication.

16 more elements

An authentication method comprising:

a step of, by a first terminal, transmitting, in response to a trigger of an authentication start to the first terminal, a code image authentication start request and authentication start trigger information to at least one first processor;
a step of, by the at least one first processor, generating a first token based on reception of the code image authentication start request;
a step of, by the at least one first processor, generating a code image key and storing in at least one storage the code image key in association with the first token;
a step of, by the at least one first processor, generating a code image including the code image key and storing the code image at a predetermined URL of the at least one storage;
a step of, by the at least one first processor, transmitting the first token and the URL at which the code image is stored to the first terminal;
a step of, by the first terminal, accessing the received URL, acquiring a code image, displaying the code image on a screen of the first terminal, and transmitting the received first token to the at least one first processor by asynchronous communication;
a step of, by the at least one first processor, registering the received first token as a key in at least one second processor;
a step of, by a second terminal, reading the code image displayed on the screen of the first terminal and acquiring the code image key;
a step of, by the second terminal, transmitting a login request, a unique ID of the second terminal, and the code image key to the at least one first processor;
a step of, by the at least one first processor, checking whether the received unique ID of the second terminal is a unique ID of the second terminal registered in advance;
a step of, when the received unique ID of the second terminal is the unique ID of the second terminal registered in advance, checking, by the at least one first processor, whether the received code image key is stored in the at least one storage;
a step of, when the received code image key is stored in the at least one storage, by the at least one first processor, retrieving the first token stored in the at least one storage using the received code image key as a key and transmitting a first response code to the at least one second processor using the retrieved first token as a key;
a step of, by the at least one second processor, transmitting the first response code to the at least one first processor that registers the first token as the key in the at least one second processor;
and
a step of, by the at least one first processor, transmitting the received first response code to the first terminal by the asynchronous communication.

12 more elements

An authentication method comprising:

a step of, by at least one first processor, receiving a code image authentication start request and authentication start trigger information from a first terminal;
a step of, by the at least one first processor, generating a first token based on reception of the code image authentication start request;
a step of, by the at least one first processor, generating a code image key and storing in at least one storage the code image key in association with the first token;
a step of, by the at least one first processor, generating a code image including the code image key and storing the code image at a predetermined URL of the at least one storage;
a step of, by the at least one first processor, transmitting the first token and the URL at which the code image is stored to the first terminal;
a step of, by the at least one first processor, registering the first token received from the first terminal, which receives the first token from the at least one first processor, as a key in at least one second processor;
a step of, by the at least one first processor, receiving a login request, a unique ID of a second terminal, and the code image key from the second terminal that reads the code image displayed on a screen of the first terminal and acquires the code image key, the first terminal accessing the received URL and acquiring the code image;
a step of, by the at least one first processor, checking whether the received unique ID of the second terminal is a unique ID of the second terminal registered in advance;
a step of, when the received unique ID of the second terminal is the unique ID of the second terminal registered in advance, checking, by the at least one first processor, whether the received code image key is stored in the at least one storage;
a step of, when the received code image key is stored in the at least one storage, retrieving, by the at least one first processor, the first token stored in the at least one storage using the received code image key as a key and transmitting a first response code to the at least one second processor using the retrieved first token as a key;
a step of, by the at least one second processor, transmitting the first response code to the at least one first processor that registers the first token as the key in the at least one second processor;
and
a step of, by the at least one first processor, transmitting the received first response code to the first terminal by asynchronous communication.

10 more elements

Dependencies are inferred from the claim text.

Facts

Application: 16/362,728Filed 25 Mar 2019 · continuation
Priority: JP 2017-25395128 Dec 2017
Published: US 2019/0222420 A118 Jul 2019
Granted: 17 Mar 2020
Term ends: Not estimatedThe source records don’t support an estimate.

Classification14 codes

H04L 9/3213
Involving a third party or a trusted authority: using tickets or tokens, e.g. Kerberos
A63F 13/48
Controlling the progress of the video game: starting a game, e.g. activating a game device or waiting for other players to join a multiplayer session
A63F 13/71
Game security or game management aspects: using secure communication between game devices and game servers, e.g. by encrypting game data or…
A63F 13/73
Game security or game management aspects: authorising game programs or game devices, e.g. checking authenticity