# US 2015/0149777 A1 · Mobile terminal, terminal and authentication method using security cookie

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

- Number: US 2015/0149777 A1
- Document ID: US20150149777A1
- Status: Published application
- Kind: A1
- Application number: 14/516,141
- Filed: 2014-10-16
- Published: 2015-05-28
- Earliest claimed: 2013-11-22
- Assignees: Electronics and Telecommunications Research Institute
- Applicants: Electronics and Telecommunications Research Institute
- Inventors: Seung-Hyun KIM; Seung-Hun JIN; Jin-Man CHO; Young-Seob CHO; Sang-Rae CHO; Dae-Seon CHOI; Jong-Hyouk NOH; Soo-Hyung KIM; Seok-Hyun KIM
- Web page: https://patentgrep.com/patent/US20150149777A1

## CPC

- H04L 9/3273: {for mutual authentication (network architectures or network communication protocols for achieving mutual authentication in a packet data network H04L63/0869)}
- H04L 63/0853: {using an additional device, e.g. smartcard, SIM or a different communication terminal (cryptographic mechanisms or cryptographic arrangements for entity authentication involving additional secure or trusted devices H04L9/3234)}
- H04W 12/068: {using credential vaults, e.g. password manager applications or one time password [OTP] applications}
- H04W 12/069: using certificates or pre-shared keys
- H04L 63/0869: {for achieving mutual authentication (cryptographic mechanisms or cryptographic arrangements for mutual authentication H04L9/3273)}
- H04L 63/1466: {Active attacks involving interception, injection, modification, spoofing of data unit addresses, e.g. hijacking, packet injection or TCP sequence number attacks}
- 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: 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

An authentication method including: transmitting, by a first terminal, a security cookie to a server and making an authentication request; transmitting, by the server, session information and the security cookie to a second terminal in response to the authentication request; verifying, by the second terminal, whether the security cookie has been encoded by a session key pre-stored in the second terminal; and performing, by the second terminal and the server, mutual authentication in the case in which the security cookie is encoded by the session key pre-stored in the second terminal is disclosed.

## Claims

### Claim 1

An authentication method comprising:
transmitting, by a first terminal, a security cookie to a server and making an authentication request;
transmitting, by the server, the security cookie to a second terminal in response to session information indicating that a user of the first terminal and a user of the second terminal are the same as each other;
verifying, by the second terminal, whether the security cookie has been encoded by a session key pre-stored in the second terminal; and
performing, by the second terminal and the server, mutual authentication in the case in which the security cookie is encoded by the session key pre-stored in the second terminal.

### Claim 2 (depends on 1)

The authentication method of claim 1, wherein the security cookie includes identification information of the first terminal and a hash value capable of verifying the identification information.

### Claim 3 (depends on 2)

The authentication method of claim 2, wherein the identification information includes an Internet protocol (IP) address of the first terminal or a user ID.

### Claim 4 (depends on 3)

The authentication method of claim 3, wherein the hash value is a value by which the identification information is hashed using the pre-stored session key.

### Claim 5 (depends on 4)

The authentication method of claim 4, wherein the pre-stored session key is a session key created by the server and the second terminal when the server and the second terminal perform mutual authentication in a previous transaction.

### Claim 6 (depends on 1)

The authentication method of claim 1, wherein the performing, by the second terminal and the server, of the mutual authentication is based on authentication information that the second terminal and the server pre-share with each other.

### Claim 7 (depends on 6)

The authentication method of claim 6, wherein the authentication information is a user ID, a password, or a public key infrastructure.

### Claim 8 (depends on 7)

The authentication method of claim 7, further comprising setting, by the server, a new security cookie using a new session key when the mutual authentication succeeds.

### Claim 9 (depends on 8)

The authentication method of claim 8, further comprising transmitting, by the server, the new security cookie together with an authentication result to the first terminal.

### Claim 10

A first terminal comprising:
a security cookie storing unit configured to store a security cookie therein; and
an authentication requesting unit configured to transmit the security cookie to a server and make a request for authentication,
wherein the authentication requesting unit receives an authentication result from the server in the case in which the security cookie is encoded by a session key stored in a second terminal, such that mutual authentication between the server and the second terminal is performed.

### Claim 11 (depends on 10)

The first terminal of claim 10, wherein the authentication requesting unit receives a security cookie newly created by the server and the second terminal, together with the authentication result, after the mutual authentication.

### Claim 12

A second terminal comprising:
a second terminal identification information managing unit configured to store a session key therein;
a second terminal mutual authentication processing unit configured to receive a security cookie corresponding to session information indicating that a user of a first terminal and a user of the second terminal are the same as each other, from a server; and
a security cookie verifying unit configured to verify whether the security cookie has been encoded by the session key,
wherein the second terminal mutual authentication processing unit performs mutual authentication in the case in which the security cookie is encoded by the session key.

### Claim 13 (depends on 12)

The second terminal of claim 12, wherein the session key is a session key created by the server and the second terminal when the server and the second terminal perform mutual authentication in a previous transaction.

### Claim 14 (depends on 13)

The second terminal of claim 13, wherein the second terminal mutual authentication processing unit performs the mutual authentication based on authentication information.

### Claim 15 (depends on 14)

The second terminal of claim 14, wherein the authentication information is a user ID, a password, or a public key infrastructure.

### Claim 16 (depends on 15)

The second terminal of claim 15, wherein the security cookie includes identification information of the first terminal and a hash value capable of verifying the identification information.

### Claim 17 (depends on 16)

The second terminal of claim 16, wherein the identification information includes an IP address of the first terminal or the user ID.

### Claim 18 (depends on 17)

The second terminal of claim 17, wherein the hash value is a value by which the identification information is hashed using the session key.

### Claim 19 (depends on 12)

The second terminal of claim 12, further comprising a second terminal session information communicating unit configured to transmit or receive a link on the session information based on a personal identification number (PIN), a text, or a quick response (QR) code.
