KR101639794B1 - Authentication method and system for user confirmation and user authentication - Google Patents

Authentication method and system for user confirmation and user authentication Download PDF

Info

Publication number
KR101639794B1
KR101639794B1 KR1020150099887A KR20150099887A KR101639794B1 KR 101639794 B1 KR101639794 B1 KR 101639794B1 KR 1020150099887 A KR1020150099887 A KR 1020150099887A KR 20150099887 A KR20150099887 A KR 20150099887A KR 101639794 B1 KR101639794 B1 KR 101639794B1
Authority
KR
South Korea
Prior art keywords
authentication
server
user information
otp
usim
Prior art date
Application number
KR1020150099887A
Other languages
Korean (ko)
Inventor
이동근
김근묵
이병영
Original Assignee
유한회사 실릭스
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 유한회사 실릭스 filed Critical 유한회사 실릭스
Priority to KR1020150099887A priority Critical patent/KR101639794B1/en
Application granted granted Critical
Publication of KR101639794B1 publication Critical patent/KR101639794B1/en

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/32Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
    • H04L9/3234Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials involving additional secure or trusted devices, e.g. TPM, smartcard, USB or software token
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/30Public key, i.e. encryption algorithm being computationally infeasible to invert or user's encryption keys not requiring secrecy
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/32Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
    • H04L9/3226Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials using a predetermined code, e.g. password, passphrase or PIN
    • H04L9/3228One-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
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W12/00Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/06Authentication

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computing Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Telephone Function (AREA)
  • Telephonic Communication Services (AREA)

Abstract

The present invention relates to authentication method and system, which perform authentication using a USIM user identification applet or a trust zone technology-based trust application by means of a USIM-based UICC authentication function provided by a telecommunications company, and to an authentication service registration method. The authentication method comprises the steps of: receiving, by an authentication server, an authentication request from a mobile terminal or a user PC; generating, by the authentication server, a public key and a private key in response to the authentication request; transferring, by the authentication server, an authentication request, including the public key, to a mobile terminal; collecting, by the mobile terminal, user information from a USIM by using a USIM user identification applet; encoding, by the USIM user identification applet which is driven in the mobile terminal, the user information by using the public key; transmitting the encoded user information to the authentication server; decoding, by the authentication server, the user information by using the private key; verifying, by the authentication server, the decoded user information via a server of a telecommunications company; and receiving an authentication result from the server of the telecommunications company.

Description

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to an authentication method,

The present invention relates to an authentication method and system for identity verification and authentication, and more particularly, to an authentication method and system for collecting authentication information stored in a mobile terminal and performing authentication in cooperation with a mobile communication company server.

With the increasing use of digital devices such as computers and smart phones, electronic commerce using such digital devices has been widely used in various fields. In particular, mobile terminals such as smart phones have advantages that users always carry around, and various financial related applications are released to facilitate users' convenience.

In financial transactions such as online payment or Internet banking, the user is essentially required to undergo the authentication process. In the past, various methods such as an authentication number using SMS, CAPTCHA (virtual keyboard), OTP, However, existing authentication methods cause inconvenience and hassle to the user, and mobile OTP authentication methods have a problem in that they are vulnerable to security such as hacking and data forgery when copying mobile phones.

As an effort to solve this problem, Korean Patent Registration No. 10-1210260 entitled " Mobile OTP Authentication Device and Authentication Method Based on Wisdom Chip Using Integrated Center "in Korean Patent No. 10-1210260 discloses an OTP generation program installed in a mobile phone, When the hacker replicates the OTP generation program stored in the mobile phone and requests the worm chip to generate the OTP number by adopting the configuration in which the OTP generation information and the program are stored, the terminal is different and the user key is different. . The prior art document is merely used for authentication by using the key and time value after storing the encrypted information and the key in mind, and there is no owner identification process for the USIM / smart phone, whereas the present invention is provided based on the USIM The encryption of the user information is supported by applying the encryption scheme proposed by the present invention to the proprietary authentication technology to secure the security of the transmission end and the USIM and the subscriber information (information such as ICCID) in the USIM are linked with the communication company It is possible to confirm the authenticity of the user and to utilize the existing system by ensuring the integrity and security of the data by checking whether the user is possessed and performing the operation in the secure area TZ.

Korean Registered Patent No. 10-1210260 (disclosed on July 17, 2012)

In order to solve the above problems, the present invention provides a method and system for authenticating authentication using a USIM authentication applet or trust zone based TA (Trust Application) using a USIM-based UICC authentication function provided by a communication company .

According to a first aspect of the present invention, there is provided an authentication method comprising the steps of: an authentication server receiving an authentication request from a mobile terminal or a user PC; Generating, by the authentication server, a public key and a private key according to the authentication request; The authentication server transmitting an authentication request including the public key to the mobile terminal; Collecting user information from the USIM using the USIM identity verification applet; Encrypting the user information with the public key by the USIM identity verification applet running on the mobile terminal; Transmitting the encrypted user information to the authentication server; The authentication server decrypting the user information using the private key; Performing verification of the user information decrypted by the authentication server through the communication company server; And receiving an authentication result from the communication company server.

According to a second aspect of the present invention, there is provided an authentication server which receives an authentication request from a user PC or a mobile terminal, generates and stores a public key and a private key corresponding to the authentication request, An identity verification server transmitting the encrypted user information to the mobile terminal, decrypting the encrypted user information using the private key, and verifying the decrypted user information with a communication company server; And an OTP server for requesting the mobile terminal to generate an OTP according to a verification result of the identity verification server and receiving and verifying the generated office at the mobile terminal.

According to the authentication method and system of the present invention, since the authentication is performed by utilizing the USIM-based authentication technology supported by the communication company, the verification is facilitated and the security and security are secured by using the encryption technology of the authentication server. In addition, by implementing authentication and OTP serial and key issuance through a communication company server at the time of initial registration, there is an advantage in that the actual authentication process can be simplified, the processing speed can be increased, and the processing load can be reduced.

Existing identity verification was limited to confirming the information about the person himself, but it was impossible to confirm whether the person who owns the smartphone which is the medium used for confirmation and confirms the identity of the person himself. The present invention has an advantage in that impersonation can be blocked at its source by checking whether the user who owns the smartphone currently matches the identity verification information (name, date of birth, phone number, etc.) of the user via the communication company.

In particular, since the present invention performs identity verification based on the TZ OTP registered through the identity verification of the communication company and the terminal confirmation, it is possible to identify and authenticate the identity of the user without checking the identity of the user every time the identity is authenticated, . In addition, by solving problems such as smuggling and theft by simply verifying the identity using SMS, the company provides a solution to the problem of the existing authentication service through the UICC technology of the communication company and the TZ OTP. The present invention is an asymmetric key method that is evaluated in the most secure way of public key / private key. It has a security authentication effect similar to that of a public key certificate. Even if a separate medium such as an authorized certificate is not present, There is an advantage that it can be conveniently authenticated. In addition, there is an advantage that the identity verification service can be used even without a separate membership, and the number of services required to authenticate the identity of a non-face-to-face mobile card issuer, an Internet professional bank, In the current market situation, there is an advantage that the needs of the market and customers can be met when a security-enhanced identity verification service is needed.

Further, when the authentication process according to the present invention is used, it is not necessary to have a separate device such as a separate hardware OTP device. By using the portable terminal of a user, it is possible to recognize and report quickly even if it is lost, It is advantageous in that it is economical, practical, and scalable because it can utilize the existing infrastructure without using it. In addition, the authentication method of the present invention can replace various means such as a security card, a USB security key, an SMS OTP, a CAPTCHA (Virtual Keyboard), an SMS, or a public certificate used in the existing authentication method, Convenience is provided.

1 is a block diagram for explaining an authentication server according to an embodiment of the present invention.
2 is a flowchart for explaining an authentication method according to an embodiment of the present invention.
3 is a block diagram illustrating an authentication method using a USIM of a mobile terminal according to an embodiment of the present invention.
4 is a block diagram illustrating an authentication method using a TZ technology of a mobile terminal according to another embodiment of the present invention.
5 is a block diagram specifically illustrating a configuration of a mobile terminal according to an embodiment of the present invention.
6 illustrates an operating system of a mobile terminal according to an embodiment of the present invention.
FIG. 7A shows a general operation of a mobile terminal according to an embodiment of the present invention, FIG. 7B shows a comparison of operations of a mobile terminal according to another embodiment of the present invention, and FIG. c) illustrates an implementation of a security UI according to an embodiment of the present invention.
8 is a flowchart for explaining an authentication service registration method according to an embodiment of the first embodiment of the present invention.
9 is a flowchart for explaining an authentication service registration method according to another embodiment of the first embodiment of the present invention.
10 is a flowchart for explaining an OTP authentication method according to an embodiment of the present invention.
FIG. 11 is a flowchart for explaining a method of authenticating a personal identity and an authentication method according to a second embodiment of the present invention.
12 is a flowchart illustrating an authentication service registration method according to a third embodiment of the present invention.
FIG. 13 is a flowchart for explaining a method for identifying and authenticating a principal according to a third embodiment of the present invention.
In the various drawings, the same reference numerals and symbols denote the same elements.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings. It should be noted that, in adding reference numerals to the constituent elements of the drawings, the same constituent elements are denoted by the same reference numerals whenever possible, even if they are shown in different drawings. In the following description of the embodiments of the present invention, a detailed description of known functions and configurations incorporated herein will be omitted when it may make the difference that the embodiments of the present invention are not conclusive. In this specification, when it is mentioned that a certain element includes an element, it means that it may further include other elements.

The present invention proposes a method and service system for carrying out identity verification using occupancy authentication (or proprietary authentication) using a value capable of identifying a mobile terminal and user information (e.g., real name, date of birth) in cooperation with a communication company .

1 is a block diagram for explaining an authentication server according to an embodiment of the present invention. The authentication service of the present invention includes a user's PC 10, a mobile terminal 20, an authentication server 30, and a mobile communication company server 40. The components may be interconnected via a network and the network may be implemented in any form or medium of digital data communication (e.g., a communication network), and examples of communication networks include a local area network (LAN), a wide area network The Internet, and the like, and can be used in various mobile networks including various forms of wireless communication such as 3G, WiFi, and LTE.

The user's PC 10 is a device capable of accessing the authentication server 30 for on-line financial transactions, and is a computing device equipped with hardware and software capable of financial transactions and commerce. PC 10 refers to a variety of digital computers, such as laptops, desktops, workstations, or other suitable computers, including, but not limited to, a variety of mobile forms, such as computing devices, such as personal digital assistants Mobile devices, and digital devices capable of communication such as IPTV using internet protocols.

The mobile terminal 20 is a mobile computing device capable of driving an authentication application that has a securely separated hardware domain, such as a USIM or a Trust Zone (TZ) for user authentication, and implements an authentication process, , And smart pads.

The mobile terminal 20 may include at least one of a USIM identity verification applet, a USIM OTP applet, a TZ OTP TA (Trusted Application) and an authentication app. The USIM identity verification applet provides a function to inquire USIM user information using a UICC (Universal IC Card) standard in a communication company, provides a function of encrypting USIM user information using a public key received from an authentication app, One can safely forward the data to the authentication app. The USIM OTP applet is an applet that performs OTP basic functions such as OTP issuance, generation and authentication, and can be installed in a terminal that does not support TZ. TZ OTP TA is an application that performs OTP basic functions such as TZ-based OTP issuance, generation, and authentication on terminals supporting TZ.

The authentication application is an application that provides a function to install and operate the TZ OTP TA on a terminal supporting TZ, and can be implemented in the same or integrated form as the above-mentioned authentication application, or in a form of a separate application or interworking. A function of safely storing the public key received from the authentication server 30 in the USIM, and a function of installing and running the USIM OTP applet in a terminal that does not support TZ. Also, it provides basic functions including OTP issuance and authentication by communicating with the USIM and TZ OTP, provides a UI (user interface) for implementing the identity verification service of the present invention, authenticates the input identification information and the encrypted authentication information Server, and store the authentication result.

The present invention is not limited to the above-described embodiment. The present invention is not limited to the above-described embodiment, Authentication information transfer may be performed.

The authentication server 30 is a service server for providing the authentication service of the present invention. The authentication server 30 transmits the authentication information in cooperation with the OTP server 310 and the communication company server 40 that support OTP generation and management according to the authentication request And an identity verification server 320 that receives the results. The OTP server 310 and the identity verification server 320 are shown as separate but may be implemented in an integrated form. The authentication server 30 generates a pair of a public key and a private key for the user's mobile terminal 10, performs a function of securely storing and managing the same, and transmits the public key to the mobile terminal 10 securely.

A mobile communication company server 40 (hereinafter, referred to as a "communication company server") is a server that provides an authentication technique using a USIM, receives authentication information, and transmits a result of authentication processing. And performs verification of information.

The authentication service of the present invention provides the authentication request to the mobile terminal 20 by the authentication server 30 when the PC 10 sends an authentication request. The authentication server 30 may provide the mobile terminal 20 with a mobile application (hereinafter referred to as "authentication app") for implementing the authentication service. The authentication request transmitted to the mobile terminal 20 may be transmitted in the form of a push message. The mobile terminal 20 can receive an authentication request and execute the authentication application automatically or manually, and can collect user information and terminal information from the USIM 220 through the authentication application. The authentication application encrypts the collected information and transmits it to the authentication server 30. The authentication server 30 transmits the decrypted information to the communication company server 40. [ The communication company server 40 performs verification according to a predefined criterion and returns the authentication result to the authentication server 30. [ The authentication server 30 can transmit the authentication result to the PC 10 and / or the mobile terminal 20. [ The authentication application receiving the authentication result can complete the identity authentication process by generating the USIM-OTP and inputting the OTP value to the PC 10.

The authentication service of the present invention collects user information and terminal information using a UICC technology provided by a mobile communication company, and the authentication server 30 supports encrypted transmission of user information and terminal information, The service can be implemented in all online / mobile service sites or mobile apps requiring identification, such as merchants, financial companies, and portals.

2 is a flowchart for explaining the authentication method of the present invention. First, the PC 10 can display a guidance or a progress screen for authentication at the start of the user authentication process, and can transmit an authentication request to the authentication server 30 according to the user's selection (steps 230 and 232) . When the authentication server 30 receives the authentication request, it transmits an authentication request to the mobile terminal 20 (Step 234). As an example, the authentication request may be sent in a push message manner, and may include an authenticated app executable code to automatically launch the authenticated app on the mobile terminal 20.

After receiving the authentication request, the mobile terminal 20 proceeds to the user confirmation procedure. The user confirmation may be implemented in a manner of inputting user information (e.g., name, communication company, date of birth, contract agreement, etc.) or confirming previously input information (operation 240). As an embodiment, the identity verification procedure can be implemented by inputting a user identification PIN (Personal Identification Number). The input of information such as user information or password can be inputted automatically or manually.

When the user confirmation is completed on the authentication app of the mobile terminal 20, at least one of user information, USIM information, and terminal information is collected for authentication (step 250). Here, the authentication application may be a USIM identity confirmation applet provided to the USIM. That is, the USIM identity confirmation applet for collecting USIM information and information may be provided for each mobile communication company, and may be included in the USIM chip embedded in the mobile terminal 30. The USIM is a combination of a subscriber identity module (SIM) card with subscriber information and a universal IC card (UICC), and performs various functions such as user authentication, global roaming, and electronic commerce. The USIM also functions as a general purpose IC card (UICC) that can carry the functions of a SIM that performs subscriber authentication and a traffic card or a credit card. The generic IC card ensures the integrity and security of all personal data through the support of various multi-application security. The USIM consists of a small CPU and memory. The CPU identifies the user with the encryption / decryption function, and the memory is used as storage space for additional services.

The authentication application encrypts the authentication information including at least one of the collected user information, USIM information, and terminal information, and transmits the encrypted authentication information to the authentication server (30). At this time, the authentication information may generate authentication information and authentication request information through the API provided by the mobile communication company, and may transmit the authentication information and authentication request information to the communication company server 40. The authentication information may be encrypted using the public key provided by the communication company server 40 can do. The authentication server 30 receives the collected information, decrypts the received information using the private key stored in advance in the identity verification server 320, and transmits the decrypted information to the communication company server 40 (270, Step 280).

The communication company server 40 performs authentication by comparing the received information with previously registered information (e.g., subscriber information, terminal information, USIM information, etc.) (Step 290). The communication company server 40 returns the authentication result to the authentication server (step 292). The authentication server 30 transmits the authentication result to the PC 10 (step 294). The authentication result may be transmitted to both the mobile terminal 20 and the PC 10 as another embodiment.

If the authentication is successful, the USIM-OTP is generated automatically or manually on the authentication application of the mobile terminal 20 (step 296). The USIM-OTP can be generated by a hash algorithm, a random function or another OTP generation method, and can be implemented so that an OTP is generated on a security area in a logically separated USIM.

The user inputs the generated USIM-OTP value to the PC 10 and the PC 10 can complete the identity verification procedure by requesting the Web server or the authentication server 30 to verify the inputted OTP value (Step 298 ).

According to the authentication service method, the authentication using the USIM-based information is enabled in the mobile communication company, and the authentication application collects the information stored in the USIM through the USIM identity authentication applet, encrypts the collected information and transmits it to the communication company server, And the communication company server, and it is possible to prevent forgery and falsification of the authentication information and deodorization of the authentication information.

3 is a block diagram illustrating an authentication method using the USIM 220 of the mobile terminal 20 according to an embodiment of the present invention.

First, the USIM 220 installed in the mobile terminal 210 includes a USIM authentication applet (for example, an authentication application) provided by a mobile communication company and includes a public key or a private key required for the authentication service of the present invention, Lt; / RTI >

When the PC 10 transmits an authentication request to the authentication server (310), the authentication server (30) transmits an authentication request to the mobile terminal (320). The mobile terminal 210 may access the USIM identity verification applet 330 via a user verification procedure such as PIN entry. The USIM identity verification applet collects authentication information including at least one of user information, telephone number, Mobile Equipment Identifier (MEID), or USIM information (ICCID) The authentication information is encrypted using the public key (340). As an embodiment, the public key may be shared with the communication company server 40 or accessed by downloading to the directory of the communication company server 40. [

Here, the authentication information may be generated using the API provided by the mobile communication company, and transmitted to the communication company server through the authentication server 30 (350, 370). The identity verification server 320 of the authentication server 30 holds the private key, receives the authentication information from the mobile terminal 20, and proceeds to decryption with the private key (360). The authentication server 30 transmits the decrypted authentication information to the communication company server 40. The communication company server 40 verifies the authentication information through comparison verification with previously stored information (e.g., subscriber information, terminal information, USIM information) (380). When the communication company server 40 completes the verification, it transmits an authentication message to the mobile terminal 20 (394) and transmits the authentication result to the authentication server 30. The authentication server 30 transmits the received authentication result to the PC 10 (392).

In this embodiment, the communication company server 40 can configure the communication server authentication server 70 in cooperation with the TSM server 50. [ The Trusted Service Manager (TSM) server 50 may also be referred to as another name such as Trusted Application Manager (TAM) as a server supporting the management of a trust zone, It has the feature that it restricts the installation and use of the application, operates completely separately in a separate area, and has priority over the general OS at boot. In this way, secure storage is possible even when storing the E2E key, private key, etc. through the implementation of the completely separated security zone. The TSM server 50 may also support sharing a static key with the USIM 220 or TA 225 of the mobile terminal with the OTP server 310 using a key personalization function .

The communication company server 40 can transmit the verification result to the authentication server 30 using the authentication information 470 and the authentication server 30 transmits the received authentication result to the PC 10 in operation 485.

When the user authentication process is completed, the OTP generation process is performed on the mobile terminal 20, and the financial transaction can be performed using the OTP input to the PC 10.

4 is a block diagram illustrating an authentication method using a TZ technology of a mobile terminal according to another embodiment of the present invention. In the embodiment described with reference to FIG. 3, the authentication application encrypts the authentication information stored in the USIM 220 loaded in the mobile terminal 10 through the USIM identity authentication applet to proceed authentication. However, The embodiment relates to an example in which TA is used to extract user information and authentication information encryption on the mobile terminal 10 with TZ support.

When the PC 10 transmits an authentication request to the authentication server 30, the authentication server 30 transmits an authentication request to the mobile terminal 20 (steps 410, 420). The mobile terminal 20 may access the TA through a user identification procedure such as PIN entry 430. [ Here, TA is a security application that runs only in a security area. When a user executes a general application and selects a menu requiring security such as OTP registration, identity verification, etc. through a general UI screen executed in a normal area (Normal World) Execute TA by calling (or linking) TA in a general application. The mobile terminal 210 collects authentication information including at least one of user information, a telephone number, a mobile equipment identifier (MEID), or USIM information (Integrated Circuit Card ID (ICCID)) stored in advance The authentication information is encrypted using the public key previously held or downloaded (440). As an embodiment, the public key may be shared with the communication company server 40 or accessed by downloading to the directory of the communication company server 40. [

The mobile terminal 20 transmits the encrypted authentication information to the authentication server 320 of the authentication server 30 and the authentication server 320 decrypts the authentication information using the private key held in operation 460. And transmits authentication information decrypted by the authentication server 30 to the communication company authentication server 70 (470).

The communication company server 40 can transmit the verification result to the authentication server 30 using the authentication information 470 and the authentication server 30 transmits the received authentication result to the PC 10 in operation 485. The TSM server 50 may communicate the authentication result to the TA 225 in association with the authentication server 30 (490). Thereafter, the TA 225 may proceed with the OTP generation process.

5 is a block diagram specifically illustrating a configuration included in the mobile terminal 20. As shown in FIG. The mobile terminal 20 may include an authentication app 222, a USIM identity verification applet 220, a USIM or TZ OTP applet 225, as described with reference to FIG. 1, and may include a communication company authentication application 223, An app 227, a merchant application 228, and a web browser 226 program. The present invention is not limited to the program shown here and may further include a program necessary for realizing the basic function and authentication service of the mobile terminal 20 in addition to the program shown.

In the embodiment described later, the authentication application 222 can perform an authentication service that operates in conjunction with the communication company authentication application 223 provided by the communication company.

The USIM identity verification applet 220 provides a function of inquiring USIM user information using a UICC (Universal IC Card) standard in a communication company, and provides a function of encrypting USIM user information by using a public key received from an authentication application And the encrypted data can be securely transmitted to the authentication application. The USIM identity confirmation applet 220 may transmit information required for authentication to the communication company server 40 and receive the authentication result from the communication company server 40. [ The USIM or TZ OTP applet 225 is an applet that performs OTP basic functions such as OTP issuance, generation, and authentication. In the case of a terminal that does not support TZ, a USIM OTP applet, a TZ-based OTP issuance, , A TZ OTP applet that performs OTP basic functions such as authentication can be installed.

The authentication application 222 provides an authentication service through communication with the authentication server 30 and provides a function of installing and operating a TZ OTP TA in a terminal supporting TZ. The authentication application 222 is connected to the communication company authentication application 223 As shown in FIG. A function of safely storing the public key received from the authentication server 30 in the USIM, and a function of installing and running the USIM OTP applet in a terminal that does not support TZ. Also, it provides basic functions including OTP issuance and authentication by communicating with the USIM and TZ OTP, provides a UI (user interface) for implementing the identity verification service of the present invention, authenticates the input identification information and the encrypted authentication information Server, and store the authentication result.

The user can access the financial company web page through the web browser 226 of the mobile terminal 20 or execute the financial service application 227 to perform the financial service at the time of the financial transaction and the web browser 226 at the transaction with the merchant The user can access the merchant's web page or execute the merchant's app 228 to proceed with the transaction. The authentication service of the present invention can support an authentication process in cooperation with a communication company server in a financial transaction and a procedure in which identity verification or authentication is required in commercial transactions. In particular, the present invention is characterized in that authentication is performed in cooperation with the communication company server 40 using the USIM identity confirmation applet 220, thereby performing authentication of ownership of the mobile terminal 20 as well as basic identity verification . Various embodiments of the authentication service of the present invention will be described with reference to Figs. 8 to 13 through the following first, second, and third embodiments.

6 and 7 illustrate a trust zone technique applied to the mobile terminal 20 of the present invention. The mobile terminal 10 of the present invention includes a general OS 114 and a general application 112 And a security zone (Trust Zone) 130 having an environment (Normal World) 110 and operating independently of the environment. In the trust zone 130, which is a secure environment, a secure OS (OS) 134 and a secure application (TA) 132 are operated independently of the general OS 114 and the general application 112, As shown in FIG. 6, some or all of the user interface 120 may be shared. The client terminal 10 also includes an ARM processor 150 based on a trust zone technology capable of selectively operating the trust zone 130 and the general environment 110.

The trust zone 130 is configured to divide the processor core into two virtual cores, one to run in a normal environment and the other to perform an operation in a secure area. A secure OS 134 supporting a secure environment, and a secure application 132 operated by a secure OS. The trust zone 130 is a hardware-based security execution environment (TEE) that logically separates a mobile CPU (AP) of a mobile terminal such as a smart device into a general area and a security area and then implements access to the security area, Technology. The security area is logically separated from the general environment 110 and can be communicated only through a predefined interface by implementing it so that it can not access each other except for the predefined interface 120 and the shared memory, Access is blocked. In addition, the trust zone 130 restricts installation and use of applications only by a service provider authorized by the Trusted Service Manager (TSM), and operates in a completely separated manner in a separate area, . In this way, secure storage is possible even when storing the E2E key, private key, etc. through the implementation of the completely separated security zone.

In one embodiment, data stored using the secure application 132 in the trust zone 130 may be stored in the general environment 110 as an encrypted form, but it is not decryptable in a normal environment, It is implemented so that decoding is not possible in the application. As another embodiment, even if an application of the same kind as that of the security application 132 is used, it can not be decrypted by another device.

As such, the trust zone 130 is logically completely separated and driven independently, so that it is possible to safely store and process financial-related information and financial-related information using the client terminal 10.

In particular, the trust zone-based security application 132 implements the security UI (Trust UI (TUI)) to implement secure authentication and secure login, thereby realizing the creation of a secure transaction-linked OTP in the security domain, Can securely process information that requires security. The security UI will be described in more detail with reference to FIG.

In one embodiment, the security application 132 of the present invention can perform login or authentication processing that requires security in general commerce as well as financial transactions. Further, the security application 132 of the present invention can generate a transaction-linked OTP using transaction information, and the transaction-linked OTP can be a security card, a general OTP token, a USB security key, an SMS OTP, a CAPTCHA It is possible to replace a variety of security measures such as a public certificate and a public certificate so that it is possible to conduct a simple and safe transaction and can be utilized as an authentication means in an Internet of things (IOT). Since the OTP proposed in the present invention is generated substantially without a physical medium, there is an advantage that a user can be easily issued online without visiting a bank or the like (for example, utilizing an online institution such as an Internet professional bank) And issuing it).

FIG. 7A shows a general operation in the client terminal 10 according to an embodiment of the present invention. FIG. 7B shows an operation in the trust zone 130 according to another embodiment of the present invention. (C) shows an implementation example of the security UI.

6, the general environment 110 and the trust zone 130 are logically separated, and when the general application 112 is executed, the general OS 114 supports the operation, and the display unit 170 displays, (UI) 116 (FIG. 7 (a)).

On the other hand, when the security application 132 is executed, the security OS 134 supports the operation thereof and displays the security UI 136 (Trusted User Interface) through the display unit 170 b)). As shown in FIG. 7C, since the security UI 136 is displayed with higher priority than the general UI, the security UI 136 can not be accessed in the normal environment 110 and the screen touch coordinates and the like are displayed in the general environment 110 It is possible to secure the safety of financial transaction or commerce executed through the trust zone 130. [

Particularly, when the security UI 136 is activated, all input / output information can not be captured outside. When the security screen is activated, the security zone uses the CPU exclusively. Therefore, all operations and operations of the general area are suspended, and the application of the trust zone based on the separate OS (ie, security OS) It blocks access itself. At this time, it is possible to prevent hardware data transmission such as capturing and recording by implementing not to execute even hardware operation keys such as home button and back button except input keypad. In order to return to the normal environment, It can be implemented only through the SW Back button. For example, if a smartphone with a trust zone is connected to a PC and the PC screen is displayed through a projector, if the smartphone is running TZ OTP, the screen changes on the smartphone from the moment when the security UI screen is executed, The output port is blocked and nothing is displayed on the PC and projector screen.

When the security UI is executed, all rights of the screen input / output can be acquired by the security area, and data input / output can be blocked. Capture or recording of the output screen is also impossible. For example, there is no way to block the screen capture by a hardware capture method (for example, a method of capturing a screen by pressing the home key and the power key at the same time) even if a security screen is implemented through an existing software security method. However, when the security UI 136 implemented in the present invention is operated, it is prevented from capturing or recording by a screen capture action, thereby completing the weakness of the existing security method. In addition, all coordinate values input on the screen can not be deodorized from the outside, and data forgery can be prevented. When the security UI according to the present invention is driven, additional security devices such as a virtual keyboard are unnecessary. Therefore, it is possible to prevent forgery and falsification without a separate security solution, and also to provide a keyboard and coordinate value security.

The security UI 136 is used in the identity verification and OTP PIN number input screen and the OTP generation result screen of the present invention and can securely protect the OTP generation value after the PIN number authentication from the security UI screen against the risk of hacking.

Using the TA and TUI based on the trust zone technology, the authentication process and the OTP generation process can be implemented as in the embodiment shown in FIG. First, a normal region (Normal World) includes basic hardware 511 of a mobile terminal and may include an OTP generation app 512. The secure domain (Secure World) may include an OTP generation engine 513. The OTP generation application 512 requests the TSM server 520 to authenticate the OTP generation app and the TSM server 520 that has received the authentication request transmits the authentication request to the MI system 530 ). The MI system 530 sends the authenticated smart app to the mobile terminal 10 to install or activate 542 a push message. The mobile terminal inputs the password and transmits it to the MI system 530. The MI system 530 transmits the authentication result to the OTP generation app 512 via the TSM server 520 after confirming the authentication (545).

The OTP generation app 512 performs TEE authentication according to the authentication result, and accesses the security area via TEE (547). The Trusted Ececution Environment (TEE) is a software platform composed of hardware functions (trust zones) that support general areas and logical separation, and software that provides security services using the hardware functions (trust zones) To provide security services to processors, peripherals, and storage devices. The OTP generation engine 513 included in the secure area generates an OTP on the trust zone and allocates an OTP to the OTP generation app 512 (548).

The OTP generated as an embodiment can be output through the OTP generation app 512 operating in the general area. The OTP generated as an alternative embodiment may be output using the TUI via the TA operating in the trust zone in the secure environment.

The user can enter the generated OTP into the PC 10 or enter the OTP into the mobile terminal 20 during the mobile financial transaction to perform the identity authentication.

As described above, it is possible to collect user information, USIM information, and terminal information stored in the TA operating in the security zone using the trust zone, and to perform identity verification and occupancy authentication by encrypting in the TA.

The embodiments described with reference to FIG. 2 to FIG. 7 perform identity verification and occupancy authentication in cooperation with a communication company every time a person identification is required (for example, every financial transaction) using authentication information held in a USIM or a trust zone Process.

On the other hand, the embodiments described with reference to FIGS. 8 to 13 are a process of performing an identity verification process in cooperation with a communication company server at the time of initial registration, and performing OTP verification through an authentication server without verification of a communication company server at the time of actual transaction . The load on the communication company server can be reduced by interlocking with the communication company server only at the time of initial registration, and the processing load of the authentication server is lowered even in the actual transaction and the processing speed is improved.

In the following embodiments, a new subscriber of the mobile terminal 20 may be implemented such that the USIM identity verification applet 220 and the authentication application 222 of the present invention are pre-loaded in a USIM provided by a communication company, The authentication application 222 for confirming the identity of the user can be activated by using the designated API in the case of card identification, banking, and other applications or when the identity verification is required on the web. If the authentication app is not installed, it can be downloaded and installed from the application store (or market) such as Android Market and App Store by OTA method. When the authentication app is installed for the first time, the authenticated app can be used through the identity verification and TZ OTP registration procedures described in FIGS. 8 and 9.

As an embodiment, in the case of a TZ non-supported terminal, a separate USIM OTP applet can be installed and used in place of TZ OTP TA that performs OTP functions such as OTP issuance, generation, and authentication.

8 is a flowchart for explaining the identity verification and TZ OTP registration procedures according to an embodiment of the first embodiment of the present invention. The present embodiment is characterized in that the authentication server 30 is the entity that generates and stores the public key and the private key.

The mobile terminal 20 may include a web or separate application 227 for accessing a financial institution, a USIM 220, a TZ 225 including a TUI and a TA, and an authentication app 222. When the authentication application 222 providing the authentication service of the present invention is activated, the authentication server 30 can generate and store the public key and the private key corresponding to the corresponding mobile terminal 10 (steps 810 and 815). The authentication server 30 generates a pair of a public key and a private key at the time of initial connection of each mobile terminal 20 or the PC 10, and manages the pair securely. The authentication server 30 transmits the generated public key to the mobile terminal 20 (step 820).

The user inputs registration information on the authentication application 222. [ The registration information may include name, phone number, carrier, date of birth, gender, foreigner, and whether to agree to the terms. When the entry of the registration information is completed, the authentication application 222 can request the customer profile while transmitting the public key to the USIM 220 using the predefined USIM identity verification applet API. The USIM identity verification applet inquires the user information stored in the USIM using the UICC specification of the communication company, encrypts the USIM user information using the public key received from the authentication application 222, and transmits the encrypted data to the authentication application 222 (Steps 845 and 850). Here, the user information includes user information, a telephone number, a mobile equipment identifier (MEID), an IC card ID (ICCID) number, and the like.

The authentication application 222 transmits a registration application including the encrypted customer user information and registration information to the authentication server 30 (step 855). The authentication server 30 decrypts the encrypted customer user information using the stored private key (private key) (step 860). The authentication server 30 requests the communication company server 40 to confirm the identity of the communication company server 40 in step 865 and the communication company server 40 performs verification and returns the result after confirming the identity of the user step). The authentication server 30 stores the identity verification result received from the communication company server 40 and transmits a TZ OTP use authentication including the usage authentication key to the mobile terminal 20 in step 880.

The mobile terminal 20 may receive the TZ OTP use authentication and the authentication app 222 may access the TZ (Trust Zone) (e.g., access using TA) and store the result of the identity verification in the TZ ). Using the TUI implemented by the TZ, the customer can set the PIN number (Step 887). When the PIN setting is completed, the TA transmits an OTP key issue request to the authentication server (step 890). At this time, the TZ can directly communicate with the authentication server 30 using the TA, or can communicate with the authentication server 30 using the authentication application 222. [

The authentication server 30 generates and stores an OTP serial and a secret key according to the request (Step 892). The authentication server 30 transmits the generated OTP serial and secret key to the mobile terminal 20 and stores the same in the TZ (step 894). The mobile terminal stores the received information in the security area and completes the registration (steps 896 and 898). After performing the registration process, the authentication application stores the OTP serial, key value, company code and PIN in the USIM or TZ area.

9 is a flowchart for explaining the identity verification and TZ OTP registration procedures according to another embodiment of the first embodiment of the present invention. The present embodiment is characterized in that the main server for generating and storing the public key and the private key is the communication company server 40. [

The authentication application 222 runs the application and transmits a registration application including the telephone number to the authentication server 30 (steps 910 and 912). The authentication server 30 requests the customer user information corresponding to the received telephone number, and the communication company server 40 receives the information and generates and stores a public key and a private key corresponding to the customer (or telephone number) ( 914 and 916). The communication company server 40 transmits the generated public key to the mobile terminal (step 918).

The authentication application 222 stores the received public key, and receives registration information from the user using the authentication application 222 (steps 920 and 930). The registration information may include name, phone number, carrier, date of birth, gender, foreigner, and whether to agree to the terms. The authentication application 222 encrypts the registration information with the public key and transmits the encrypted registration information to the authentication server 30. The authentication server transmits the encrypted registration information to the communication company server 40 to request the identity confirmation (steps 945 and 950). The communication company server 40 decrypts the encrypted registration information with the private key, extracts the user information, and performs identity verification through comparison verification with previously held information (steps 955 and 960).

The authentication server 30 receives and stores the authentication result from the communication company server 40 in step 965 and sends the TZ OTP use authentication including the user authentication key to the mobile terminal 20 in step 970. The authentication application 222 of the mobile terminal 20 transmits the TZ OTP use authentication to the TZ, and the TZ stores the identity verification result (step 975). The TZ 225 performs the PIN setting step using the TA and the TUI (step 980), and requests the authentication server 30 to issue the OTP key (step 985).

The authentication server 30 generates and stores an OTP serial and a secret key according to the request (step 990). The authentication server 30 transmits the generated OTP serial and secret key to the mobile terminal 20 and stores the same in the TZ (step 992). The mobile terminal stores the received information in the security area and completes registration (steps 994 and 996). After performing the registration process, the authentication application stores the OTP serial, key value, company code and PIN in the USIM or TZ area.

It is possible to encrypt authentication information (user information) using the public key and the private key generated by the authentication server 30 or the communication company server 40 as in the embodiment described with reference to FIG. 8 or 9, And security can be guaranteed. Once the identity verification and the TZ OTP registration procedure are completed, the user authentication using the TZ OTP becomes possible.

The mobile terminal 20 can drive a web or an application 227 provided by a financial company and can request an OTP input using the UI provided by the web page or application in operation 1005. Here, in the case of a web service, a user is requested to input an OTP using a designated API, and in the case of an application, a user is requested to input an OTP number using a designated SDK. When the OTP input is requested, the authentication application 222 of the mobile terminal 20 is automatically or manually operated (step 1010).

The authentication application 222 calls TZ OTP to the TZ 225 (step 1020), and the TZ requests input of the PIN 6 digits using the TUI (step 1030). If the subscriber inputs the PIN 6 digits, the PIN authentication is performed in cooperation with the USIM or TZ OTP module (step 1040). If the PIN authentication is successful, the authentication application 222 receives the OTP number in cooperation with the USIM or TZ OTP module, and outputs the received OTP securely (e.g., using the TUI) (step 1050).

In the case of the web service, the user inputs the OTP value displayed in the authentication application 222 in the web input window, and in step 1060, the output OTP value is automatically input into the input window of the application through the SDK. When the authentication button is clicked, an authentication request is transmitted to the authentication server 30 (Step 1070), and the authentication server 30 verifies the OTP value (Step 1080). The authentication server 30 may transmit the authentication result to the mobile terminal 20 and display the authentication result on the financial company web or the application 227 in operation 1090.

In the case of using the identity verification process, only verification is performed using the authentication server 30 without interlocking with the communication company server 40 in the case of performing identity verification and TZ OTP authentication only at the time of initial registration, The processing data is reduced and the processing speed is improved.

11 is a flowchart for explaining a method of authenticating an authentication service according to a second embodiment of the present invention. In the second embodiment, the authentication service of the present invention can be used by downloading and installing an authentication app without a separate registration process in the authentication app 222, ).

The user can execute the financial transaction or the commerce transaction by executing the web browser 226, the financial company application 227 or the merchant application 228, and can perform the authentication service of the present invention when the identity verification and authentication are required . Hereinafter, the case of performing the identity verification through the merchant's application 228 will be described. However, the present invention is not limited thereto and the identity verification and the identity verification can be performed in various situations.

In step 1110, the user executes the merchant application 228 and selects 'security authentication' among the various identification methods presented through the merchant application 228 when the user authentication is required. The security authentication is a temporary name of the authentication service proposed by the present invention and may be referred to as an authentication service of the present invention in another name. The merchant application 228 outputs UI for inputting a phone number to the identity confirmation window and receives user information such as a name (for example, real name), date of birth, gender, communication company, phone number, (Step 1120). The merchant application 228 transmits the received user information to the authentication server 30 and the authentication server 30 transmits the push message to the authentication application 222 based on the user's phone number in steps 1130 and 1140, . When the user receives and confirms the push message, the authentication application 222 can be executed automatically or manually (Step 1150). For example, it can be implemented to be automatically executed by including the authentication application execution code in the push message, or manually executed by the user including the link address of the authentication application in the push message.

When the authentication application 222 is executed, the user performs PIN or fingerprint authentication (step 1160). As an embodiment, in the case of PIN authentication, the authentication application 222 performs authentication using a PIN stored in a secure area (e.g., KeyStore, KeyChain or TZ). In the case of fingerprint authentication, fingerprint authentication can be performed according to the method provided by the Android API. When the authentication is completed, the authentication application 222 can receive user information for identifying the user in cooperation with the communication company authentication application 223 (step 1170). The communication company authentication application 223 can transmit the identity verification information through the secure channel communication with the USIM identity verification applet 220 of the communication company. The USIM identity verification applet 220 encrypts the received information and the user information in the USIM, And may transmit the authentication request by transmitting to the authentication platform (steps 1175 and 1180). The communication company authentication platform operated by the communication company server 40 decrypts the received information, performs identity verification and ownership authentication, and transmits (returns) the result to the USIM identity confirmation applet 220 (steps 1182 and 1184) . The communication company authentication application 223 transmits the result to the authentication application 222 in step 1186 and the authentication application 222 outputs the authentication result and sends the result to the authentication server 30 in steps 1188 and 1190 ). The authentication server 30 may also transmit the received authentication result to the affiliate store application 228 and output the authentication result (steps 1192 and 1194).

As described above, the second embodiment of the present invention is an embodiment in which the communication company server 40 (e.g., a communication company authentication platform) performs identity verification through the communication company authentication application 223 and the USIM identity confirmation applet 220 of the communication company, The authentication server (30) and the authentication application (222) support intermediation of the merchant and the communication company server to perform the authentication process.

When the user selects the security authentication as the authentication means on the merchant application 228, the authentication application verifies the authentication information in cooperation with the communication company authentication application 223 through the PIN authentication, similarly to the identity verification . The verification result can be shared by the authentication application 222 and the authentication server 30 via the communication company authentication application 223 and can also be transmitted to the merchant application 228 through the authentication server 30. [

However, in the identity authentication process, the user authentication and the ownership authentication are performed using only the telephone number without inputting the user information inputted when the identity is confirmed. When the merchant application 228 receives the telephone number and executes the authentication application 222 through the push message, the communication company authentication application 223 encrypts only the user information in the USIM through the USIM identity confirmation applet 220, And the communication company authentication platform verifies the received information. That is, there is no information received from the user other than the telephone number when authenticating the user, and a simplified authentication process can be implemented separately from the identity verification procedure by implementing only the user information in the USIM when the communication company is authenticated.

As described above, according to the second embodiment, since the authentication using the communication company UICC is implemented, there is an advantage that anyone can easily use the service without joining a separate service. Unlike the other embodiments, there is a difference in not using the OTP.

12 is a flowchart illustrating an authentication service registration method according to a third embodiment of the present invention. Unlike the public key / private key method of the first embodiment, the third embodiment is an embodiment for performing identity verification and personal authentication using an OTP, and is similar to the authentication application provided by the authentication server 30 (222).

First, the user can download and install the authentication application 222. The user executes the authentication application 222 to input whether or not to agree to the agreement, and inputs user information such as a name, date of birth, gender, communication company selection, telephone number, step). When the confirmation button is pressed for the input information after the completion of the user information input, the authentication application 222 communicates with the communication company authentication application 223 to transmit the user information (operation 1220). At this time, the user information can be encrypted and transmitted to provide security. The communication company authentication application 223 communicates with the USIM authentication applet 220 on a secure channel basis and the communication company authentication application 223 transmits the user information to the USIM identity authentication applet 220 in step 1230. The USIM identity verification applet 220 encrypts the received values, USIM and user information in the USIM, and transmits the encrypted information to the communication company server 40 in step 1250. The communication company server 40 decrypts the received information, performs identity verification and proprietary authentication, and transmits the result to the USIM identity confirmation applet 220 (step 1260). The USIM identity confirmation applet 1270 delivers the authentication result to the communication company authentication application 223, and the communication company authentication application 223 transmits the authentication result to the authentication application 222 (steps 1270 and 1280).

Upon completion of the identity verification and the ownership authentication through the communication company, the authentication application 222 sets and registers a fingerprint or PIN for using the authentication application 222. [ The PIN can be stored in a secure area if the PIN is registered, and the PIN can be stored in a safe area according to the manner provided by the smartphone manufacturer.

Next, the authentication application 222 confirms that the TZ-enabled mobile terminal is available. If the TZ-OTP applet is available, you can check if the TZ-OTP applet is installed. If not, you can connect to the remote TAM to download and install the TZ-OTP applet. If TZ is not available, you can download and install the USIM-OTP applet in conjunction with the remote telecommunications company TSM.

After the USIM or TZ OTP applet 225 is installed, the OTP registration process is performed using the provider information and the user information (step 1290). Transmits an OTP registration request to an OTP server (or a separate OTP server) in the authentication server 30, stores an OTP serial number (serial) and key value issued from the OTP server in a secure TZ or USIM. When the registration is completed, the USIM information (ICCID) of the user mobile terminal is encrypted and transmitted to the authentication server 30 (step 1295), and the authentication server 30 securely stores the received USIM information (ICCID) of the subscriber.

FIG. 13 is a flowchart for explaining a method for identifying and authenticating a principal according to a third embodiment of the present invention. If the user authentication or authentication procedure is required in the merchant application 228, the user can select security authentication as the authentication means (step 1310). For example, a franchisee includes an affiliate shop operated by various entities such as a portal, a financial service, a card service, or an individual business operator.

The merchant application 228 receives the user information through the identity confirmation window (step 1320). The user information includes at least one of a name, a date of birth, a sex, a communication company, a telephone number, whether the user is a foreigner or a foreigner, whether to agree to the agreement, and an OTP serial value. The user executes the authentication application 222 to perform PIN or fingerprint authentication (steps 1330 and 1340). In case of PIN authentication, authentication is performed using a secure area (e.g., KeyStore, KeyChain or TZ). In the case of fingerprint authentication, fingerprint authentication is performed according to the method provided to the Android API.

When the authentication is completed, the authentication application 222 generates and outputs the first OTP by linking the telephone number, the USIM information (ICCID) and the time value of the mobile terminal 20 with the TZ / USIM-OTP as parameters (Step 1350 ). Here, the telephone number, the USIM information (ICCID), and the time value of the mobile terminal 20 are used for confirming the information of the communication company or the OTP holder. The user inputs the generated first OTP into the OTP input field of the identity confirmation request page of the merchant application 228 (step 1355). For example, the first OTP may be implemented to be input at the time of inputting user information (operation 1320), or may be implemented to receive input through a separate input page.

The merchant's app 228 delivers the information input through the merchant's server to the authentication server 30 (step 1360). The authentication server 30 can determine whether the information is consistent by interworking with the communication company the information (e.g., name, date of birth, sex, communication company, telephone number, (Step 1370).

When the user information matches the user information, the USIM information (ICCID) value stored in the authentication server 30 is inquired with the telephone number of the user, and the second OTP is generated using the value and the time value as parameters And verifies whether the received first OTP value matches the received first OTP value (steps 1380 and 1390).

After the verification, the authentication server 30 transmits the identity verification result to the merchant application 228, and the merchant application 228 outputs the identity verification result (step 1398)

The authentication process according to the third embodiment can be performed through the authentication application 222 in the same manner as the identity authentication process described above. Hereinafter, the authentication procedure according to the third embodiment will be described. First, the user can select security authentication in the merchant's app 228, and input the phone number, agreement agreement status, and OTP value into the identity authentication window. Unlike the identity verification procedure, the user enters a telephone number without inputting detailed user information and proceeds with the authentication procedure. When the user executes authentication application 222, PIN or fingerprint authentication is performed. Next, the authentication application 222 generates and outputs a first OTP value by linking the telephone number, the USIM information (ICCID), and the time value with the TZ / USIM-OTP as a parameter. The user inputs the first OTP to the merchant application 228 and presses an OK button to transmit the input information to the authentication server 30. [ The authentication server 30 inquires USIM information (ICCID) stored in the authentication server 30 with the phone number of the user, and generates a second OTP value using the value and the time value as parameters. The authentication server 30 verifies whether the second OTP is matched with the first OTP received, performs verification, and transmits the authentication result to the merchant application 228.

The above-described third embodiment is advantageous in that it is simple and safe since the identity verification and authentication are performed using the OTP registered through the identity verification process through the communication company. Particularly, in the case of the authentication of the user, the response speed is fast and the processing cost is reduced because the authentication is not performed at every authentication.

While the present invention has been described in detail in the foregoing for the purpose of illustration, it is to be understood that the components, their connections and relationships, and their functions are merely exemplary. In the present invention, each component may be implemented as a physically separated form or as an integrated form of one or more components as needed.

The present invention is not necessarily limited to these embodiments, as all the constituent elements constituting the embodiment of the present invention are described as being combined or operated in one operation. That is, within the scope of the present invention, all of the components may be selectively coupled to one or more of them.

Furthermore, the terms "comprises", "comprising", or "having" described above mean that a component can be implanted unless otherwise specifically stated, But should be construed as including other elements. All terms, including technical and scientific terms, have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs, unless otherwise defined. Commonly used terms, such as predefined terms, should be interpreted to be consistent with the contextual meanings of the related art, and are not to be construed as ideal or overly formal, unless expressly defined to the contrary.

The foregoing description is merely illustrative of the technical idea of the present invention, and various changes and modifications may be made by those skilled in the art without departing from the essential characteristics of the present invention. Therefore, the embodiments disclosed in the present invention are intended to illustrate rather than limit the scope of the present invention, and the scope of the technical idea of the present invention is not limited by these embodiments. The scope of protection of the present invention should be construed according to the following claims, and all technical ideas within the scope of equivalents should be construed as falling within the scope of the present invention.

10: PC
20: Mobile terminal
30: Authentication server
40:

Claims (24)

delete delete delete delete delete delete delete delete delete The authentication server receiving an authentication request from a mobile terminal or a user PC;
Generating, by the authentication server, a public key and a private key according to the authentication request;
The authentication server transmitting an authentication request including the public key to the mobile terminal;
Collecting user information from the USIM using the USIM identity verification applet;
Encrypting the user information with the public key by the USIM identity verification applet running on the mobile terminal;
Transmitting the encrypted user information to the authentication server;
The authentication server decrypting the encrypted user information using the private key;
Performing verification of the user information decrypted by the authentication server through a communication company server; And
And receiving an authentication result from the communication company server,
Wherein the mobile terminal comprises an authentication app,
The authentication app receives the public key from the authentication server and stores it in the USIM through the USIM identity verification applet,
The collecting step may include collecting user information and terminal information using a universal IC card (UICC) standard provided by a communication company,
The mobile terminal registering user information in an authentication service using an authentication application;
The mobile terminal requesting an OTP input on a predetermined app or web;
The mobile terminal activating the authentication app;
Performing the PIN authentication in cooperation with the USIM or the TZ Authenticate applet;
The authentication server generating an OTP using a USIM or a TZ authenticator applet;
The mobile terminal inputs an OTP on the application or the web and requests an authentication server to perform OTP verification; And
Wherein the mobile terminal receives an OTP authentication result from the authentication server and outputs the OTP authentication result to the application or the web,
The step of registering user information in the authentication service comprises:
Storing the authentication result by the authentication server;
The authentication server transmitting a TZ OTP use authentication to the mobile terminal;
Receiving the TZ OTP use authentication from the authentication application of the mobile terminal and transmitting the authentication to the TZ;
Setting a PIN number in the TZ;
Requesting the TZ to issue an OTP key to the authentication server through the authentication app;
Generating and storing an OTP serial and a secret key according to the request; And
And the authentication server transmitting and storing the OTP serial and the secret key to the TZ through the authentication app.
11. The method of claim 10,
The step of registering user information in the authentication service comprises:
Transmitting an authentication request to the authentication server through the authentication app on the mobile terminal;
Generating, by the authentication server, a public key and a private key according to the authentication request;
Receiving the public key from the authentication server and storing the public key;
Requesting user information by the authentication app including the public key in a USIM identity verification applet;
Encrypting user information collected from a USIM using the public key by the USIM identity verification applet;
Receiving the encrypted user information and transmitting a registration request including encrypted user information to the authentication server;
The authentication server decrypting the user information with the private key;
Performing verification of the user information decrypted by the authentication server through a communication company server; And
And receiving an authentication result from the communication company server.
11. The method of claim 10,
The step of registering user information in the authentication service comprises:
Transmitting an authentication request to an authentication server through an authentication app on a mobile terminal;
The authentication server transmitting the authentication request to a communication company server;
Generating a public key and a private key by the communication company server according to the authentication request;
Receiving the public key from the communication company server and storing the public key;
Receiving the user information from the authentication app;
Encrypting the user information using the public key;
Transmitting, by the authentication app, a registration request including the encrypted user information to the communication company server;
Decrypting and verifying the user information with the private key by the communication company server; And
And the authentication server receiving the authentication result from the communication company server.
delete delete 11. The method of claim 10,
The step of registering user information in the authentication service comprises:
The authentication app calls the TZ OTP to the TZ;
Receiving and verifying PIN from the TZ;
Generating and outputting the TZ OTP in the TZ;
Inputting the TZ OTP on a financial web or an app of the mobile terminal; And
Further comprising the step of the mobile terminal authenticating the TZ OTP via the authentication server.
13. The method according to claim 11 or 12,
Wherein the user information includes at least one of a name, a telephone number, a communication company, a date of birth, sex, an alien, and whether or not to agree to a term.
11. The method of claim 10,
Selecting an authentication means on an application (App) or a web (Web) in which the mobile terminal proceeds the identity verification service;
Receiving the unencrypted user information from the merchant application and transmitting the unencrypted user information to the authentication server; And
Further comprising the step of the mobile terminal executing the authentication application using the push message received from the authentication server,
The authentication app works in cooperation with the communication company authentication app,
Wherein the step of verifying the user information decrypted by the authentication server through the communication company server comprises the steps of: requesting the communication company authentication application to perform authentication of own authentication and ownership to the authentication platform of the communication company through the USIM identity authentication applet; An authentication step of receiving an authentication result through the authentication application, the authentication application transmitting the authentication result to the authentication application, and the authentication application transmitting the authentication result to the authentication server.
delete 18. The method of claim 17,
Wherein the non-encrypted user information includes a telephone number,
Wherein the USIM identity verification applet encrypts the non-encrypted user information stored in the USIM and transmits the encrypted user information to the communication company authentication platform.
delete 11. The method of claim 10,
Wherein the user information includes at least one of a name, a birth date, a sex, a communication company, a telephone number, a foreigner's presence, an OTP serial, and a condition agreement.
11. The method of claim 10,
The step of registering user information in the authentication service comprises:
Installing and executing the authentication application by the mobile terminal;
Inputting user information into the authentication application;
Transmitting the user information encrypted by the authentication app to a communication company authentication application and transmitting the user information to the user authentication application via a secure channel;
Encrypting the user information and the USIM information to the communication server, transmitting the encrypted user information and the USIM information, and requesting identity verification and proprietary authentication;
The USIM identity confirmation applet receiving the identity verification and ownership authentication result from the communication company server; And
And the USIM identity confirmation applet transmitting the authentication result to the authentication application through the communication company authentication application.
23. The method of claim 22,
The step of registering user information in the authentication service comprises:
Registering a PIN or a fingerprint authentication when the authentication application receives the authentication result and the authentication is successful;
Supporting the TZ OTP applet to install the TZ OTP applet if the TZ usage is available, and installing the USIM OTP applet if the TZ usage is not available;
Storing the user information and the OTP information using the TZ OTP applet or the USIM OTP applet; And
Further comprising encrypting the USIM information and transmitting the encrypted USIM information to an authentication server.
24. The method of claim 23,
Wherein the USIM information is ICCID information.
KR1020150099887A 2015-07-14 2015-07-14 Authentication method and system for user confirmation and user authentication KR101639794B1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
KR1020150099887A KR101639794B1 (en) 2015-07-14 2015-07-14 Authentication method and system for user confirmation and user authentication

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
KR1020150099887A KR101639794B1 (en) 2015-07-14 2015-07-14 Authentication method and system for user confirmation and user authentication

Related Child Applications (1)

Application Number Title Priority Date Filing Date
KR1020160027299A Division KR101656458B1 (en) 2016-03-07 2016-03-07 Authentication method and system for user confirmation and user authentication

Publications (1)

Publication Number Publication Date
KR101639794B1 true KR101639794B1 (en) 2016-07-14

Family

ID=56499368

Family Applications (1)

Application Number Title Priority Date Filing Date
KR1020150099887A KR101639794B1 (en) 2015-07-14 2015-07-14 Authentication method and system for user confirmation and user authentication

Country Status (1)

Country Link
KR (1) KR101639794B1 (en)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20190054280A (en) * 2017-11-13 2019-05-22 주식회사 하나은행 Method and mobile terminal unit for providing asset management service
CN116916310A (en) * 2023-07-07 2023-10-20 中移互联网有限公司 Verification code generation and verification method and device and electronic equipment
KR20240075374A (en) 2022-11-22 2024-05-29 김명환 System and method for financial transaction service based on authentication using portable device

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20010000738A (en) * 2000-10-17 2001-01-05 안병엽 Provably secure public key encryption scheme based on computational diffie-hellman assumption
KR20050055814A (en) * 2003-12-09 2005-06-14 주식회사 팬택앤큐리텔 System and method of servicing automatically fare settlement by using the mobile communication terminal
KR20120108599A (en) * 2011-03-25 2012-10-05 주식회사 스마트솔루션 Credit card payment service using online credit card payment device
KR101210260B1 (en) 2011-01-07 2012-12-18 사단법인 금융보안연구원 OTP certification device
KR101502997B1 (en) * 2014-05-14 2015-03-24 유한회사 실릭스 Payment system and payment method using one time password

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20010000738A (en) * 2000-10-17 2001-01-05 안병엽 Provably secure public key encryption scheme based on computational diffie-hellman assumption
KR20050055814A (en) * 2003-12-09 2005-06-14 주식회사 팬택앤큐리텔 System and method of servicing automatically fare settlement by using the mobile communication terminal
KR101210260B1 (en) 2011-01-07 2012-12-18 사단법인 금융보안연구원 OTP certification device
KR20120108599A (en) * 2011-03-25 2012-10-05 주식회사 스마트솔루션 Credit card payment service using online credit card payment device
KR101502997B1 (en) * 2014-05-14 2015-03-24 유한회사 실릭스 Payment system and payment method using one time password

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20190054280A (en) * 2017-11-13 2019-05-22 주식회사 하나은행 Method and mobile terminal unit for providing asset management service
KR102577560B1 (en) * 2017-11-13 2023-09-11 주식회사 하나은행 Method and mobile terminal unit for providing asset management service
KR20240075374A (en) 2022-11-22 2024-05-29 김명환 System and method for financial transaction service based on authentication using portable device
CN116916310A (en) * 2023-07-07 2023-10-20 中移互联网有限公司 Verification code generation and verification method and device and electronic equipment

Similar Documents

Publication Publication Date Title
US12022282B2 (en) Anonymous authentication and remote wireless token access
US20220417230A1 (en) Managing credentials of multiple users on an electronic device
TWI667585B (en) Method and device for safety authentication based on biological characteristics
KR101621254B1 (en) Payment method, computer readable recording medium and system using virtual number based on otp
US20190364032A1 (en) Method for carrying out a two-factor authentication
US20150310427A1 (en) Method, apparatus, and system for generating transaction-signing one-time password
KR101656458B1 (en) Authentication method and system for user confirmation and user authentication
US20190087814A1 (en) Method for securing a payment token
JP2023508317A (en) contactless card personal identification system
CA2879910C (en) Terminal identity verification and service authentication method, system and terminal
JP2019530265A (en) Method and apparatus for providing and acquiring graphic code information and terminal
JP2012507900A (en) Remote user authentication using NFC
KR20180013710A (en) Public key infrastructure based service authentication method and system
JP2024099827A (en) Multi-factor authentication providing credential via contactless card for secure messaging
US11405782B2 (en) Methods and systems for securing and utilizing a personal data store on a mobile device
KR101659847B1 (en) Method for two channel authentication using smart phone
KR20220167366A (en) Cross authentication method and system between online service server and client
KR101639794B1 (en) Authentication method and system for user confirmation and user authentication
KR101799517B1 (en) A authentication server and method thereof
KR20170042392A (en) Method for Providing Mobile Payment Service by Using Account Information
WO2015162276A2 (en) Secure token implementation
KR101835718B1 (en) Mobile authentication method using near field communication technology
KR101502999B1 (en) Authentication system and method using one time password
KR101604459B1 (en) Method, apparatus and system for generating transaction related otp
GB2525423A (en) Secure Token implementation

Legal Events

Date Code Title Description
AMND Amendment
AMND Amendment
AMND Amendment
X701 Decision to grant (after re-examination)
GRNT Written decision to grant