Personal authentication request method, personal authentication request device, and personal authentication system

Abstract

The present disclosure relates to an authentication request method, an authentication request device, and an authentication system. The authentication request method according to an embodiment of the present disclosure may include transmitting a prearranged sound signal, receiving device identification data transmitted from a device that detects the prearranged sound signal, and transmitting the collected authentication means data to a device identified by the device identification data.

Description

[Technical field]

[0001] The present invention relates to an authentication request method, an authentication request device, and an authentication system. [Background technology]

[0002] In recent years, with the development of smart device technology including smartphones and network technology, it has become common to see people collecting biometric information through everyday devices such as smart devices and kiosks, authenticating their identity through their biometric information, paying for a product, or obtaining permission to enter or exit a store.

[0003] On the other hand, since identity authentication is fundamentally a procedure for preventing identity theft, security can be said to be the most important factor in identity authentication technology.

[0004] Therefore, there is a continuing demand for the development of identity authentication technology that can provide users with procedural convenience while maintaining a high level of security. Summary of the Invention [Problem to be solved by the invention]

[0005] The object of the present disclosure is to provide an authentication request method, an authentication request device, and an authentication system. The problems to be solved by the present disclosure are not limited to the problems described above, and other problems and advantages of the present disclosure not mentioned can be understood from the following description and will be more clearly understood in the embodiments of the present disclosure. Furthermore, it will be understood that the problems and advantages to be solved by the present disclosure can be implemented by the means and combinations thereof set forth in the claims. [Means for solving the problem]

[0006] A first aspect of the present disclosure can provide an identity authentication request method including the steps of transmitting a pre-agreed sound signal, receiving device identification data transmitted from a device that detects the pre-agreed sound signal, and transmitting collected authentication means data to a device corresponding to the device identification data.

[0007] A second aspect of the present disclosure can provide an identity authentication request device that includes a memory having at least one program stored therein, and a processor that operates by executing the at least one program, wherein the processor transmits a pre-arranged sound signal, receives device identification data transmitted from a device that detects the sound signal, and transmits collected authentication means data to a device corresponding to the device identification data.

[0008] A third aspect of the present disclosure can provide a computer-readable recording medium having recorded thereon a program for causing a computer to execute the method according to the first aspect.

[0009] A fourth aspect of the present disclosure can provide an identity authentication method including the steps of transmitting device identification data in response to detecting a pre-arranged sound signal, receiving authentication means data transmitted based on the transmitted device identification data, determining whether the authentication means data matches stored identity authentication data, and transmitting whether identity authentication has been successful or not based on whether the data matches.

[0010] A fifth aspect of the present disclosure is a personal authentication request device that collects authentication means data and transmits a pre-promised sound signal, and a personal authentication request device that detects the pre-promised sound signal and retrieves stored information in response to the request. and a user terminal that transmits personal authentication data, wherein the personal authentication request device receives the personal authentication data and determines whether the authentication means data and the personal authentication data match.

[0011] A sixth aspect of the present disclosure can provide an authentication system including an authentication request device that collects authentication means data, transmits a pre-agreed sound signal, and transmits the authentication means data, a user terminal that detects the pre-agreed sound signal and transmits an identification number of an authentication-dedicated device in response to a request, and the authentication-dedicated device that stores the authentication data received from the user terminal and determines whether the authentication means data and the authentication data match. Effect of the Invention

[0012] According to various embodiments of the present disclosure, it is possible to verify that the person attempting identity authentication and the owner of the identity authentication device are the same person, without the person attempting identity authentication having to directly input identification information of the identity authentication device they use, such as their telephone number.

[0013] This significantly reduces the time required for identity authentication, providing a high level of satisfaction to those who experience the identity authentication system of the present disclosure. [Brief description of the drawings]

[0014] [Figure 1] FIG. 1 is a block diagram for explaining an identity authentication system according to an embodiment of the present disclosure. [Diagram 2] FIG. 2 is a flowchart illustrating an identity authentication process according to an embodiment of the present disclosure. [Figure 3a-b] 3a and 3b are flow charts illustrating an identity authentication process according to another embodiment of the present disclosure. [Figure 4] FIG. 4 is a flowchart illustrating a process in which an authentication request device requests authentication when one device is detected according to an embodiment of the present disclosure. [Diagram 5] FIG. 5 is a flowchart illustrating a process in which an authentication request device requests authentication when multiple devices are detected according to an embodiment of the present disclosure. [Figure 6]FIG. 6 is a flowchart illustrating a process in which an authentication request device requests authentication when multiple devices are detected according to another embodiment of the present disclosure. [Figure 7] FIG. 7 is a flowchart illustrating a process in which the identity authentication device according to an embodiment of the present disclosure performs identity authentication. [Figure 8] FIG. 8 is a flowchart of an authentication request method according to an embodiment of the present disclosure. [Figure 9] FIG. 9 is a flowchart illustrating a personal authentication process according to still another embodiment of the present disclosure. [Figure 10] FIG. 10 is a flowchart illustrating a personal authentication process according to still another embodiment of the present disclosure. [Figure 11a-b] 11a and 11b are flowcharts illustrating an identity authentication process according to still another embodiment of the present disclosure. [Figure 12a-c] 12a to 12c are flowcharts illustrating an identity authentication process according to still another embodiment of the present disclosure. [Figure 13] FIG. 13 is a flowchart of an identity authentication method according to an embodiment of the present disclosure. [Figure 14] FIG. 14 is a flowchart of an authentication request method according to an embodiment of the present disclosure. [Figure 15] FIG. 15 is a block diagram of an authentication request device according to an embodiment of the present disclosure. BEST MODE FOR CARRYING OUT THEINVENTION

[0015] A method for requesting personal authentication according to one embodiment of the present disclosure may include the steps of transmitting a prearranged sound signal, receiving device identification data transmitted from a device that detects the prearranged sound signal, and transmitting collected authentication means data to a device identified by the device identification data. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0016] The advantages and features of the present invention, as well as the methods for achieving them, will become apparent from the embodiments described in detail with the accompanying drawings. However, the present invention is not limited to the embodiments described below, and may be realized in different forms, and should be understood to include all modifications, equivalents, or alternatives within the spirit and technical scope of the present invention. The embodiments described below are provided to fully disclose the present invention and fully inform those skilled in the art to which the present invention pertains of the scope of the invention. In describing the present invention, if it is determined that a detailed description of related known technology may hinder the gist of the present invention, the detailed description will be omitted.

[0017] The terms used in this application are merely used to describe certain embodiments and are not intended to limit the present invention. A singular expression includes a plural expression unless the context clearly indicates otherwise. In this application, terms such as "include" or "have" specify the presence of features, numbers, steps, operations, components, parts, or combinations thereof described herein, and should be understood not to preclude the presence or additional possibility of one or more other features, numbers, steps, operations, components, parts, or combinations thereof.

[0018] Some embodiments of the present disclosure may be represented by functional block configurations and various processing steps. Some or all of such functional blocks may be realized by various hardware and / or software configurations that perform specific functions. For example, the functional blocks of the present disclosure may be realized by one or more microprocessors, or may be realized by circuit configurations for a given function. Also, for example, the functional blocks of the present disclosure may be realized by various programming or scripting languages. The functional blocks may be realized by algorithms executed in one or more processors. Also, the present disclosure may employ conventional techniques for electronic configuration, signal processing, and / or data processing, etc. Terms such as "mechanism," "element," "means," and "configuration" may be used broadly and are not limited to mechanical and physical configurations.

[0019] Furthermore, the connecting lines or connecting members between components shown in the figures are merely exemplary of functional and / or physical or circuit connections, and in an actual device the connections between components may be represented by various alternative or additional functional, physical or circuit connections.

[0020] In this disclosure, the term "authentication means data" is used to refer to data that serves as a personal authentication means, that is data entered by a person attempting personal authentication for personal authentication, and that is collected by a specific device. A person attempting personal authentication can enter the authentication means data to access procedures restricted by personal authentication. The authentication means data may be a specific type of data that is set to be used to perform personal authentication by a user or a system. For example, the authentication means data may include biometric information of a user. In one embodiment, the biometric information is any one or more of fingerprint information, genetic (DNA) information, skeletal information, hand shape information, retina information, iris information, face information, vein information, electrocardiogram information, font information, gait information, signature information, blood vessel information, sweat gland structure information, voice information, and biomolecules. The above may include.

[0021] In this disclosure, the term "authentication data" is used to refer to data stored in the authentication device by a user of the authentication device, which is the basis for whether the authentication means data matches the data of the person attempting authentication. That is, the authentication device can perform authentication by comparing the authentication means data with the authentication data stored in the authentication device. The type of the authentication data may be the same as the type of the authentication means data. If the authentication means data and the authentication data are the same, authentication is performed successfully and access to procedures restricted by authentication may be granted.

[0022] Meanwhile, in one embodiment, the identity authentication data may be collected through the identity authentication device and stored in the identity authentication device, i.e., data input and stored by a user of the identity authentication device for use of the identity authentication device or for identity authentication through a data input device, such as a camera or a fingerprint input device, provided in the identity authentication device.

[0023] In another embodiment, the personal authentication data may be collected via the personal authentication request device and stored in the personal authentication device. Specifically, the personal authentication data may be collected via the personal authentication request device, transmitted to the personal authentication device (or via a server) and stored in the personal authentication device. The personal authentication data stored via this procedure may also be used to perform a subsequent personal authentication procedure by the system of the present disclosure. For example, for the first authentication to use the personal authentication system, the personal authentication device may collect data as the user's "personal authentication data", and then, when the user attempts personal authentication to use the personal authentication system, the personal authentication device may collect data as the user's "authentication means data". Even if the type of personal authentication data is the same (e.g., face recognition), the specifications of the sensor that collects the data may differ for each device, so that according to this embodiment, the accuracy of identity verification between the personal authentication data and the authentication means data may be improved.

[0024] In this disclosure, the term "device identification data" is used to refer to data for identifying an authentication device in the authentication system of the present disclosure. The authentication system of the present disclosure may include multiple authentication devices, and the device identification data may be used to identify the authentication device used by the person attempting authentication among the multiple authentication devices. For example, the device identification data may include any one or more of a telephone number, a membership number, and a resident registration number.

[0025] FIG. 1 is a block diagram for explaining an identity authentication system according to an embodiment of the present disclosure.

[0026] The personal authentication device 10 performs personal authentication based on the authentication means data received from the personal authentication request device 20. The personal authentication device 10 can perform personal authentication by comparing the personal authentication data stored in the personal authentication device 10 with the authentication means data collected by the personal authentication request device 20. For example, the personal authentication device 10 may be a portable electronic device of the user, and the personal authentication request device 20 may be an electronic device provided in an affiliated store of a business that provides a service that the user wants to use. The personal authentication request device 20 may be a device that allows access only if personal authentication is normally performed. As a specific example, the personal authentication request device 20 may be a device provided at an entrance that allows only those who have completed personal authentication to enter and exit. As yet another example, the personal authentication request device 20 may be a device provided at a cash register and that approves payment through personal authentication. In addition to this, the personal authentication request device 20 may be a type of device suitable for performing a personal authentication procedure to provide various services.

[0027] The identity authentication device 10 may include a communication unit, a processor, a memory, and a sensor.

[0028] In one embodiment, the identity authentication device 10 may be a mobile electronic device. For example, the identity authentication device 10 may be realized by a smartphone, a tablet PC, a PC, a smart TV, a PDA (personal digital assistant), a laptop, a media player, a navigation system, a device equipped with a camera, and other mobile electronic devices. The identity authentication device 10 may also be realized by a wearable device such as a watch, glasses, a hair band, or a ring equipped with a communication function and a data processing function.

[0029] The communication unit of the personal authentication device 10 enables the personal authentication device 10 to communicate with an external device (for example, the personal authentication request device 20 or a server).

[0030] For example, the communication performed by the communication unit of the authentication device 10 may be LTE, LTE-A (LTE Advance), CDMA (code division multiple access), WCDMA (wideband CDMA), UMTS (universal mobile telecommunications system), WiBro (Wireless Broadband), or GSM (Global System For example, the communication performed by the communication unit of the authentication device 10 may include WiFi (wireless fidelity), Bluetooth, Bluetooth Low Energy (BLE), Zigbee, NFC (near field communication), Magnetic Secure Transmission, Radio Frequency (RF), or Body Area Network (BAN). For example, the communication performed by the communication unit may include GNSS. The GNSS may be, for example, GPS (Global Positioning System), Glonass (Global Navigation Satellite System), Beidou Navigation Satellite System, or Galileo, the European global satellite-based navigation system.

[0031] The processor of the personal authentication device 10 controls the overall operation of the personal authentication device 10. For example, the processor of the personal authentication device 10 can control the overall operation of the personal authentication device 10 by executing a program stored in the memory of the personal authentication device 10.

[0032] The processor of the personal authentication device 10 may be any of ASICs (application specific integrated circuits), DSPs (digital signal processors), DSPDs (digital signal processing devices), PLDs (programmable logic devices), FPGAs (field programmable gate arrays), and the like. The invention may be implemented using at least one of the following electronic units: arrays, controllers, micro-controllers, microprocessors, and other electronic units for performing other functions.

[0033] The memory of the personal authentication device 10 is hardware that stores various data processed within the personal authentication device 10, and can store programs for processing and controlling the processor of the personal authentication device 10. The programs can include, for example, a kernel, middleware, an application program interface (API), and / or an application program (or "application"), etc. The memory of the personal authentication device 10 can store payment information, user information, etc.

[0034] The sensor of the identity authentication device 10 can convert measured or detected information into an electronic signal. The sensor of the identity authentication device 10 can include, for example, a gesture sensor, a biometric sensor, an olfactory (e-nose) sensor, a surface electromyogram (EMG) sensor, an electroencephalogram (EEG) sensor, a heart rate (ECG) sensor, an infrared (IR) sensor, an iris sensor, and / or a fingerprint sensor.

[0035] The sensor of the identity authentication device 10 may include a camera. The camera may be a device capable of generating still and video data. The camera may include one or more image sensors (e.g., front or rear sensors), a lens, an image signal processor (ISP), or a flash (e.g., an LED or xenon lamp, etc.).

[0036] The identity authentication device 10 may further include an input / output device. The input / output device of the identity authentication device 10 may receive an input from a user of the identity authentication device 10 and convert the input from the user into an electronic signal for processing, or convert an electronic signal generated by the identity authentication device 10 into a signal for providing to the user. For example, the input / output device of the identity authentication device 10 may include a touch panel, a (digital) pen sensor, a key, an ultrasonic input device, a display, or an audio module.

[0037] The authentication request device 20 may include a communication unit, a processor, a memory, and a sensor.

[0038] In one embodiment, the authentication request device 20 may be a mobile electronic device. For example, the authentication request device 20 may be a smartphone, a tablet PC, a PC, a smart TV, a PDA (personal digital assistant), a laptop, a media player, a navigation system, a device equipped with a camera, and other mobile electronic devices. The authentication request device 20 may also be a wearable device such as a watch, glasses, a hair band, or a ring that has a communication function and a data processing function.

[0039] The communication unit of the authentication requesting device 20 enables the authentication requesting device 20 to communicate with an external device (for example, the authentication device 10 or a server).

[0040] For example, the communication performed by the communication unit of the authentication request device 20 may be LTE, LTE-A (LTE Advance), CDMA (code division multiple access), WCDMA (wideband CDMA), UMTS (universal mobile telecommunications system), or the like. The communication unit may include a mobile telecommunications system, WiBro (Wireless Broadband), or GSM (Global System for Mobile Communications). For example, the communication performed by the communication unit of the authentication requesting device 20 may include WiFi (wireless fidelity), Bluetooth, Bluetooth Low Energy (BLE), Zigbee, NFC (near field communication), Magnetic Secure Transmission, Radio Frequency (RF), or Body Area Network (BAN). For example, the communication performed by the communication unit may include GNSS. The GNSS may include, for example, GPS (Global Positioning System), Glonass (Global Positioning System), or GSM (Global Positioning System). Navigation Satellite System), Beidou Navigation Satellite System, or Galileo, the European global satellite-based navigation It can be on system.

[0041] The processor of the authentication request device 20 controls the overall operation of the authentication request device 20. For example, the processor of the authentication request device 20 can control the overall operation of the authentication request device 20 by executing a program stored in the memory of the authentication request device 20.

[0042] The processor of the authentication request device 20 may be implemented using at least one of ASICs (application specific integrated circuits), DSPs (digital signal processors), DSPDs (digital signal processing devices), PLDs (programmable logic devices), FPGAs (field programmable gate arrays), controllers, micro-controllers, microprocessors, and electrical units for performing other functions.

[0043] The memory of the authentication request device 20 is hardware that stores various data processed within the authentication request device 20, and can store programs for processing and control of the processor of the authentication request device 20. The programs can include, for example, a kernel, middleware, an application program interface (API), and / or an application program (or "application"), etc. The memory of the authentication request device 20 can store payment information, user information, etc.

[0044] The sensors of the authentication request device 20 can convert measured or detected information into electronic signals. The sensors of the authentication request device 20 can include, for example, a gesture sensor, a biometric sensor, an olfactory (e-nose) sensor, a surface electromyogram (EMG) sensor, an electroencephalogram (EEG) sensor, a heart rate (ECG) sensor, an infrared (IR) sensor, an iris sensor, and / or a fingerprint sensor.

[0045] The sensor of the authentication request device 20 may include a camera. A camera may be a device capable of generating still and video data. A camera may include one or more image sensors (e.g., a front sensor or a rear sensor), a lens, an image signal processor (ISP), or a flash (e.g., an LED or xenon lamp, etc.).

[0046] The personal authentication request device 20 may further include an input / output device. The input / output device of the personal authentication request device 20 may receive an input from a user of the personal authentication request device 20 and convert the input from the user into an electronic signal for processing, or convert an electronic signal generated by the personal authentication request device 20 into a signal for providing to the user. For example, the input / output device of the personal authentication request device 20 may include a touch panel, a (digital) pen sensor, a key, an ultrasonic input device, a display, or an audio module.

[0047] Although not shown in Fig. 1, the personal authentication system according to an embodiment of the present disclosure may further include a server. For reasons of ease of data storage, data distribution, design limitations, ease of design, etc., the personal authentication system may further include a server, and in one embodiment, the personal authentication device 10 or the personal authentication request device 20 may transmit and receive some of the data to and from each other via the server, rather than directly transmitting and receiving part of the data to and from each other.

[0048] The server may include a processor, and the overall operation of the server may be controlled by the processor of the server. For example, a processor of the server may control the overall operation of the server by executing programs stored in the server's memory.

[0049] Although not shown in FIG. 1, the personal authentication system according to an embodiment of the present disclosure may further include a personal authentication dedicated device. The personal authentication dedicated device may be a device provided separately from the personal authentication device or the personal authentication request device, and may be a device provided separately for performing personal authentication without performing other functions. When the personal authentication system includes the personal authentication dedicated device, there is an advantage that personal authentication can be performed even when the power of the personal authentication device or the user terminal is turned off. As described below, the personal authentication dedicated device can receive and store personal authentication data, and determine whether the authentication means data received thereafter matches the personal authentication data. The personal authentication dedicated device will be described in detail below with reference to FIGS. 9a, 9b, and 10a to 10c.

[0050] The personal authentication dedicated device may include a processor, and the overall operation of the personal authentication dedicated device may be controlled by the processor of the personal authentication dedicated device. For example, the processor of the personal authentication dedicated device may control the overall operation of the personal authentication dedicated device by executing a program stored in the memory of the personal authentication dedicated device.

[0051] Meanwhile, the personal authentication device 10 can generate a signal continuously or periodically. Continuously or periodically generating a signal may be for the purpose of allowing access to the personal authentication system according to an embodiment of the present disclosure at any time. Specifically, the personal authentication device 10 can generate a signal continuously or periodically so that a series of personal authentication request procedures according to the present disclosure are automatically performed when the personal authentication device 10 satisfies a specific condition (e.g., accessing the personal authentication request device 20 or communicating with the personal authentication request device 20, etc.) without the user of the personal authentication device 10 or a person attempting to perform personal authentication via the personal authentication system according to an embodiment of the present disclosure intentionally disclosing (e.g., executing an application) a series of personal authentication request procedures (or personal authentication procedures) according to the present disclosure via the personal authentication device 10.

[0052] As a specific example, the identity authentication request method according to an embodiment of the present disclosure may be performed by interacting with the operation of an application installed on the identity authentication device 10 (e.g., a smartphone), and the application may be switched to a power-saving mode if it is not executed continuously, and when switched to the power-saving mode, it may be difficult to automatically start the application outside the identity authentication device 10. Therefore, the identity authentication device 10 of the present disclosure (or the application installed on the identity authentication device 10) may be realized to generate a signal continuously or periodically, thereby maintaining the application in an active state.

[0053] The signal that is continuously or periodically generated by the authentication device 10 may be transmitted to a server or the authentication request device 20. For example, the signal that is continuously or periodically generated may include location data such as GPS data.

[0054] The process of requesting and authenticating identity, which is carried out in the identity authentication system of the present disclosure, will be described in detail below.

[0055] FIG. 2 is a flowchart illustrating an identity authentication process according to an embodiment of the present disclosure.

[0056] In the present disclosure, the authentication process may be performed by transmitting and receiving data between the authentication device 10 and the authentication request device 20.

[0057] In one embodiment, the authentication request device 20 in step 201 can collect authenticator data.

[0058] In one embodiment, before step 201 is performed, a user of the authentication device 10 can interact with the authentication request device 20 to input authentication means data. For example, the authentication means may be face recognition, and the authentication request device 20 can collect face data as the authentication means data. The user of the authentication device 10 can approach and interact with the authentication request device 20 to input face data.

[0059] In one embodiment, the authentication requesting device 20 in step 202 may request device identification data.

[0060] In one embodiment, the number of people accessing the authentication request device 20 may be one or more. That is, the number of devices detected by the authentication request device 20 (e.g., a sensor or a communication unit included in the authentication request device 20) may be one or more. For example, if the authentication request device 20 is a device installed at an entrance that allows entry and exit, multiple people may be lined up to pass through the entrance, and in such a case, the number of devices detected by the authentication request device 20 may be one or more. If the number of devices detected by the authentication request device 20 is one or more, the authentication request device 20 can determine one of the one or more devices as the target of the device identification data request. An embodiment for determining the target of the device identification data request will be described in detail later with reference to FIG. 4 and FIG. 5.

[0061] In one embodiment, the authentication device 10 in step 203 may transmit device identification data to the authentication request device 20 in response to receiving the device identification data request.

[0062] In one embodiment, the identity authentication device 10 can receive additional input from the user of the identity authentication device 10 (e.g., input approving data transmission) and transmit device identification data, and can also automatically transmit device identification data in response to a device identification data request.

[0063] In one embodiment, the authentication request device 20 in step 204 can transmit authentication means data to the authentication device 10 .

[0064] The target to which the personal authentication request device 20 transmits the authentication means data can be determined based on the device identification data, not based on the target that requested the device identification data. That is, the personal authentication request device 20 can transmit the authentication means data to a device identified by the device identification data. As a result, the authentication means data transmitted by the personal authentication request device 20 is received by the personal authentication device 10 that transmitted the device identification data, which can be the result when the personal authentication process proceeds normally.

[0065] In one embodiment, the authentication request device 20 requests device identification data, and the method of receiving the device identification data and the method of transmitting the authentication means data may be different. For example, the transmission and reception of the device identification data and the transmission and reception of the authentication means data may be performed via different networks.

[0066] In one embodiment, the authentication device 10 in step 205 can determine whether the received authentication means data matches authentication data stored in the authentication device 10 .

[0067] If the received authentication means data matches the authentication data stored in the authentication device 10, it means that the authentication means data collected by the authentication request device 20 is data related to the user of the authentication device 10.

[0068] On the other hand, as described above, the personal authentication data stored in the personal authentication device 10 may be collected via the personal authentication device 10 and stored in the personal authentication device 10, or may be collected via the personal authentication request device 20 and transmitted to and stored in the personal authentication device 10.

[0069] In one embodiment, the authentication device 10 in step 206 can transmit to the authentication request device 20 the success or failure of the authentication.

[0070] Specifically, the personal authentication device 10 can transmit a signal indicating that personal authentication has been successful in response to the fact that the received authentication means data matches the personal authentication data stored in the personal authentication device 10. Conversely, the personal authentication device 10 can transmit a signal indicating that personal authentication has failed in response to the fact that the received authentication means data does not match the personal authentication data stored in the personal authentication device 10.

[0071] In one embodiment, the personal authentication request device 20 in step 207 can approve or disapprove access to a procedure restricted by personal authentication based on the received signal. For example, if the personal authentication request device 20 is a device installed at an entrance that allows entry and exit, it can approve entry and exit.

[0072] 3a and 3b are flow charts illustrating an identity authentication process according to another embodiment of the present disclosure.

[0073] A detailed description of the contents shown in FIG. 3a that overlap with the contents described with reference to FIG. 2 will be omitted.

[0074] In one embodiment, the authentication request device 20 in step 301 can collect authenticator data.

[0075] In one embodiment, the authentication requesting device 20 in step 302 may request device identification data.

[0076] In one embodiment, the authentication device 10 in step 303 may transmit device identification data to the authentication request device 20 in response to receiving the device identification data request.

[0077] Steps 301 to 303 correspond to steps 201 to 203 in FIG. 2, respectively, and therefore a detailed description of steps 301 to 303 will be omitted.

[0078] Meanwhile, in one embodiment, instead of steps 302 and 303, the server 30 may mediate the transmission and reception of the device identification data. Specifically, in one embodiment, the authentication requesting device 20 can request the device identification data from the server 30. In this case, the server 30 can request the device identification data from the authentication device 10. Also, in one embodiment, the authentication device 10 can transmit the device identification data to the server 30. In this case, the server 30 can transmit the device identification data to the authentication requesting device 20.

[0079] In one embodiment, the authentication request device 20 in step 304 may transmit the authenticator data to the server 30 .

[0080] 2, the target to which the authentication request device 20 transmits the authentication means data is the server 30. In this embodiment, compared with the case where the authentication request device 20 transmits the authentication means data to the authentication device 10, the authentication request device 20 transmits the authentication means data to the server 30, which has the advantage of strengthening security and facilitating the design process.

[0081] In one embodiment, step 304 may include the authentication request device 20 communicating device identification data to the server 30, thereby enabling the server 30 to identify the subject to which the authenticator data is to be sent.

[0082] Among the contents explained in step 204 in FIG. 2, those that can be applied to step 304 can also be realized in step 304 without any special mention.

[0083] In one embodiment, the server 30 in step 305 may communicate the authentication means data to the identity authentication device 10 .

[0084] In one embodiment, server 30 may transmit the authenticator data to a device identified in the device identification data communicated by authentication request device 20 .

[0085] In one embodiment, server 30 may perform additional processing operations on the authenticator data received in step 304 to enhance security.

[0086] In one embodiment, the authentication device 10 in step 306 can determine whether the received authentication means data matches authentication data stored in the authentication device 10 .

[0087] Step 306 can correspond to step 205 in FIG. 2, so a detailed description of step 306 will be omitted.

[0088] In one embodiment, the authentication device 10 in step 307 can transmit to the server 30 the success or failure of the authentication.

[0089] 2, the target to which the authentication request device 20 transmits the success or failure of the authentication is the server 30. In this embodiment, compared with the case where the authentication request device 20 transmits the success or failure of the authentication to the authentication device 10, the authentication request device 20 transmits the success or failure of the authentication to the server 30, which has the advantage of strengthening security and facilitating the design process.

[0090] Among the contents explained in step 206 of FIG. 2, those that can be applied to step 307 can also be realized in step 307 without any special mention.

[0091] In one embodiment, the server 30 in step 308 can inform the authentication device 10 of the success or failure of the authentication.

[0092] In one embodiment, the authentication requester 20 in step 309 can approve or disapprove access to the authentication restricted procedure based on the received signal.

[0093] Step 309 can correspond to step 207 in FIG. 2, so a detailed description of step 309 will be omitted.

[0094] FIG. 3b is a flowchart illustrating an identity authentication process according to yet another embodiment, and a detailed description of the contents shown in FIG. 3b that overlap with the contents described with reference to FIG. 3a will be omitted.

[0095] Steps 311 and 312 may correspond to steps 301 and 302 in FIG. 3a, so a detailed description of steps 311 and 312 will be omitted.

[0096] As a difference from the embodiment of FIG. 3a, in one embodiment, the authentication device 10 in step 313 may transmit device identification data to the server 30 in response to receiving the device identification data request.

[0097] As an example, communication between the authentication request device 20 and the authentication device 10 may be one-way rather than two-way, and the authentication device 10 may send device identification data to the server 30 rather than to the authentication request device 20.

[0098] In one embodiment, the personal authentication device 10 can transmit location identification data together with the device identification data to the server 30. When the personal authentication device 10 transmits the device identification data, the server 30 may have difficulty in determining which device transmitted the device identification data, so the personal authentication device 10 can also transmit location identification data to the server 30. The location identification data is data for identifying the location of the personal authentication device 10, and as an example, the server 30 can compare the location of the authentication request device 20 with the location data transmitted by the personal authentication device 10 to identify the personal authentication device 10. For example, the location identification data can be GPS data.

[0099] Step 314 may correspond to step 304 in FIG. 3a, so a detailed description of step 314 will be omitted.

[0100] In one embodiment, the server 30 in step 315 may communicate the authenticator data to the identity authentication device 10 .

[0101] In one embodiment, the server 30 can transmit the authenticator data to a device identified by the device identification data transmitted by the authentication device 10 .

[0102] Steps 316-319 can correspond to steps 306-309 in FIG. 3a, so a detailed description of steps 316-319 will be omitted.

[0103] As described above, the authentication request device 20 of the present disclosure can request device identification data and receive device identification data. However, the device from which the authentication request device 20 can request device identification data does not necessarily have to be one.

[0104] Fig. 4 is a diagram for explaining an embodiment in which one device is detected, and Fig. 5 and Fig. 6 are diagrams for explaining an embodiment in which multiple devices are detected. The process shown in Fig. 4 to Fig. 6 can be executed by the authentication request device 20, specifically, by a processor included in the authentication request device 20.

[0105] FIG. 4 illustrates an example of a case where an authentication request device is detected according to an embodiment of the present disclosure. 11 is a flowchart illustrating a process of requesting personal authentication.

[0106] The example shown in FIG. 4 relates to an embodiment in which there is a single person accessing a procedure that is restricted by authentication, such as a single person requesting access authorization.

[0107] In step 410, authentication request device 20 may detect an approaching person.

[0108] In one embodiment, the authentication request device 20 can detect the approach of a person near the authentication request device 20 via any suitable means. For example, the authentication request device 20 can detect an approaching person via a sensor of the authentication request device 20. For example, the sensor that detects an approaching person can be an infrared sensor, an ultrasonic sensor, a laser sensor, etc. Step 410 can be performed as an element that initiates a later step performed by the authentication request device 20.

[0109] In step 420, authentication requester device 20 may collect authenticator data.

[0110] Step 420 can correspond to step 201 in FIG. 2 or step 301 in FIG. 3, so a detailed description of step 420 will be omitted.

[0111] In one embodiment, step 420 may be performed independently of step 410. That is, authentication request device 20 may collect authentication means data in response to detecting an approaching person, or may collect authentication means data via authentication means data input regardless of whether an approaching person is detected.

[0112] In step 430, the claimant device 20 may transmit a prearranged sound signal.

[0113] The pre-promised sound signal may mean a sound signal that can be detected by a device (e.g., the authentication device 10) included in the authentication system of the present disclosure among devices around the authentication request device 20. That is, in the present disclosure, the authentication device 10 may be a device that can detect a sound signal and determine whether the detected sound signal is a pre-promised sound signal sent by the authentication request device 20. In other words, the authentication system of the present disclosure can identify a device that provides an authentication procedure via a pre-promised sound signal. For example, the authentication device 10 can be made to determine whether the sound signal is a pre-promised sound signal by installing an application distributed for use in the authentication system (or authentication service) of the present disclosure.

[0114] In one embodiment, the pre-promised sound signal can include a sound having any frequency. That is, the identity authentication device 10 can be designed to detect a sound of a specific frequency. For example, the pre-promised sound signal can include a sound having a frequency value included in an audible frequency (e.g., 20hz to 20,000hz). For example, the pre-promised sound signal can include a sound having a frequency value not included in an audible frequency, such as an ultrasonic wave or an infrasonic wave.

[0115] In one embodiment, the prearranged sound signal may include a sound having a specific pattern, i.e., the authentication device 10 may be designed to detect a sound having a specific pattern. For example, the specific pattern may include a high and low sound, i.e., a change in frequency. For example, the specific pattern may be a pattern having a series of beats, i.e., a pattern formed by a section in which a sound is generated. For example, the specific pattern may include both a pattern formed by a change in frequency and a pattern formed by a section in which a sound is generated.

[0116] In one embodiment, the pre-promised sound signal may include sounds having a volume below a certain volume, i.e., the pre-promised sound signal may only include sounds with an amplitude that can be detected only by devices in close proximity to the authentication request device 20.

[0117] In one embodiment, the authentication request device 20 can repeatedly transmit the pre-promised sound signal. For example, the authentication request device 20 can transmit the pre-promised sound signal continuously or periodically. Correspondingly, in one embodiment, the authentication device 10 can be designed to determine that the detected sound signal is the pre-promised sound signal only if the pre-promised sound signal has a preset continuity or periodicity. In another embodiment, the authentication device 10 can be designed to determine that the detected sound signal is the pre-promised sound signal only if the pre-promised sound signal is detected a preset number of times or more.

[0118] Alternatively, the pre-promised sound signal may include any sound designed to be detectable by the personal authentication device 10 included in the personal authentication system. The pre-promised sound signal may preferably be a sound signal that cannot be easily detected by devices not included in the personal authentication system of the present disclosure.

[0119] In step 440, the authentication requesting device 20 may receive the device identification data.

[0120] In one embodiment, the device identification data may be data transmitted by a device that detects a pre-promised sound signal, i.e., in the present disclosure, the pre-promised sound signal can serve as a tool for obtaining device identification data.

[0121] Since this embodiment is an embodiment in which only one person is attempting to access a procedure restricted by personal authentication, in this embodiment, the received device identification data may correspond to one device.

[0122] For identity authentication based on collected authentication means data, it is necessary to verify that the person attempting identity authentication by inputting authentication means data is the same as the owner of the identity authentication device 10. Conventionally, for this verification, the person attempting identity authentication (or via the administrator of the identity authentication request device 20) had to input device identification data (e.g., a phone number) that is identification information of the identity authentication device 10. However, in the present disclosure, the process of the person attempting identity authentication directly inputting the device identification data can be omitted by transmitting a pre-arranged sound signal via steps 430 and 440, that is, the identity authentication request device 20 receiving the device identification data from the device that detected the pre-arranged sound signal. Since it is not necessary to directly input the device identification data, it is possible to significantly reduce the time required for overall identity authentication for one person, and provide a highly satisfying experience to the user of the identity authentication system.

[0123] In step 450, authentication request device 20 may transmit authenticator data.

[0124] In this embodiment, as described above, the authentication request device 20 can transmit the authentication means data to a device identified by the device identification data. The device 20 can send the authenticator data to the server. Step 450 can correspond to step 204 in Fig. 2 or step 304 in Fig. 3, so a detailed description of step 450 is omitted.

[0125] In step 460, the authentication requester device 20 may initialize its state.

[0126] In this embodiment, initializing the state of the authentication request device 20 can mean deleting the device detection history or the collected authentication means data and switching to the initial state. That is, since the authentication request device 20 has completed one authentication request by transmitting the authentication means data, it can switch to the initial state and prepare for an authentication request for the next person.

[0127] 4, the order in which the steps are performed may be changed as appropriate. For example, step 420 may be performed after step 440. That is, the authentication requesting device 20 may collect the authenticator data after receiving the device identification data.

[0128] FIG. 5 is a flowchart illustrating a process in which an authentication request device requests authentication when multiple devices are detected according to an embodiment of the present disclosure.

[0129] The example shown in FIG. 5 relates to an embodiment in which several people have access to a procedure that is restricted by authentication, such as when several people are waiting to be allowed in and out.

[0130] In step 510, the claimant device 20 may detect approaching people.

[0131] Except for the fact that multiple people are detected, step 510 can correspond to step 410 in FIG. 4, so a detailed description of step 510 will be omitted.

[0132] In step 520, authentication requester device 20 may collect authenticator data.

[0133] In this embodiment, the number of detected people may be multiple, but the number of collected authentication means data may be one. For example, when requesting personal authentication during a payment process or during access control, it is common to approve access to a restricted procedure one by one, rather than simultaneously approving multiple people. Therefore, only one authentication means data may be collected until personal authentication is performed. That is, the collected one authentication means data is held until the personal authentication request device 20 transmits the authentication means data in the next step 560. Thus, what is to be solved in this embodiment is to determine which of the detected multiple people the collected authentication means data corresponds to. A solution to this problem will be described later through the explanation of steps 550 and 560.

[0134] In step 530, the authentication requesting device 20 may transmit a pre-promised sound signal.

[0135] The explanation regarding the pre-promised sound signal has been described above with reference to FIG. 4 and will be omitted here.

[0136] In this embodiment, since there are multiple people to be detected, each of the multiple people to be detected can have a device, and thus each of the multiple devices can transmit a pre-promised message. Receive and detect signals.

[0137] In step 540, authentication requesting device 20 may receive a plurality of device identification data.

[0138] In this embodiment, the plurality of device identification data can include data transmitted by each of the plurality of devices by each of the plurality of devices detecting a pre-arranged sound signal.

[0139] In step 550, the authentication requesting device 20 may select one of a plurality of device identification data.

[0140] In this embodiment, the authentication requesting device 20 can select one of the multiple device identification data via any suitable means. In this embodiment, by selecting one of the multiple device identification data, it is possible to determine which of the multiple detected persons the collected authentication means data belongs to.

[0141] In one embodiment, the authentication request device 20 can receive an input for selecting identification data and select one of a plurality of device identification data. In one embodiment, the authentication request device 20 can receive an input for selecting identification data via an input / output device. For example, the authentication request device 20 can display a plurality of device identification data received via an output device in an arranged manner, and an administrator of the authentication request device 20 or a person attempting authentication can select one of the plurality of device identification data displayed via an input device. For example, if the device identification data is a telephone number, the telephone number of the person attempting authentication is selected from the arranged plurality of telephone numbers. For example, the output device and the input device can be a touch panel or the like.

[0142] In one embodiment, the authentication requesting device 20 can select one of the plurality of device identification data as the device identification data corresponding to the closest device. The authentication requesting device 20 can determine the device identification data corresponding to the closest device among the plurality of device identification data via any suitable means.

[0143] In step 560, the authentication requesting device 20 may transmit the authenticator data to the device identified by the selected device identification data.

[0144] Similar to step 450 in Fig. 4, the authentication request device 20 can transmit the authentication means data to a device identified by the selected device identification data in step 550, since the device identification data selected in step 550 corresponds to the person attempting authentication. Alternatively, the authentication request device 20 can transmit the authentication means data and the selected device identification data to a server. In addition, step 560 can correspond to step 204 in Fig. 2 or step 304 in Fig. 3, and therefore a detailed description of step 560 will be omitted.

[0145] In step 570, the authentication claimant device 20 may initialize its state.

[0146] Step 570 can correspond to step 460 in FIG. 4, so a detailed description of step 570 will be omitted.

[0147] 5, the order in which the steps are performed may be changed accordingly. For example, step 520 may be performed after step 540. After receiving the plurality of device identification data, the authentication requesting device 20 can collect the authenticator data.

[0148] FIG. 6 is a flowchart illustrating a process in which an authentication request device requests authentication when multiple devices are detected according to another embodiment of the present disclosure.

[0149] The example shown in FIG. 6, like the example in FIG. 5, relates to an embodiment where multiple people are attempting to access a procedure that is restricted by identity authentication, such as when multiple people are waiting to obtain entry permission.

[0150] In step 610, the claimant device 20 may detect approaching people.

[0151] In step 620, authentication requester device 20 may collect authenticator data.

[0152] In step 630, the authentication requesting device 20 may transmit a pre-promised sound signal.

[0153] In step 640, authentication requesting device 20 may receive a plurality of device identification data.

[0154] Steps 610 to 640 correspond to steps 510 to 540 in FIG. 5, respectively, and therefore a detailed description of steps 610 to 640 will be omitted.

[0155] In step 650, authentication requesting device 20 may transmit authenticator data to each of a plurality of devices identified by the plurality of device identification data.

[0156] Unlike the embodiment described with reference to Fig. 5, in the embodiment of Fig. 6, instead of the process of selecting one of the plurality of device identification data, all of the plurality of received device identification data can be used. In this embodiment, the authentication requesting device 20 transmits authentication means data to each of the plurality of devices identified by the plurality of device identification data, so that the plurality of devices can receive the authentication means data. However, the authentication means data received by each of the plurality of devices is the same, and this authentication means data is data related to one person, so that authentication can be normally performed only through one device.

[0157] That is, after the personal authentication device 10 receives the authentication means data, it determines whether the received authentication means data matches the personal authentication data stored in the personal authentication device 10, and transmits whether the personal authentication has been successful to the personal authentication request device 20 (or to the personal authentication request device 20 via the server 30), but the maximum number of signals indicating that the personal authentication has been successful that the personal authentication request device 20 can receive in response to one piece of authentication means data collected is one. This solves the problem of determining which of multiple detected people the collected authentication means data corresponds to.

[0158] In step 660, the claimant device 20 may initialize its state.

[0159] Step 660 can correspond to step 570 in FIG. 5, so a detailed description of step 660 will be omitted.

[0160] FIG. 7 is a flow chart for explaining a process in which the identity authentication device according to an embodiment of the present disclosure performs identity authentication. 1 is a flowchart of the process.

[0161] The process shown in FIG. 7 can be executed by the identity authentication device 10, specifically, by a processor included in the identity authentication device 10.

[0162] In step 710, the authentication device 10 can be switched to a state in which it can receive an audio signal.

[0163] In the present disclosure, in order to detect the sound signal, the personal authentication device 10 can switch the state of the personal authentication device 10 to a state capable of receiving the sound signal in step 710. For example, the personal authentication device 10 can turn on the microphone function via an application distributed and installed on the personal authentication device 10.

[0164] In the present disclosure, the personal authentication device 10 can switch the state of the personal authentication device 10 to a state in which it can receive an audio signal when triggered by any suitable means. In one embodiment, the personal authentication device 10 can switch the state of the personal authentication device 10 in response to detecting that the personal authentication device 10 has come close to the authentication request device 20. In one embodiment, the personal authentication device 10 can detect that it has come close to the authentication request device 20 by any suitable means. For example, the personal authentication device 10 can include a GPS sensor and can detect that it has come close to the authentication request device 20 via the GPS sensor.

[0165] In step 720, the authentication device 10 may detect an audio signal.

[0166] In one embodiment, the authentication device 10 can detect the sound signal via an input / output device included in the authentication device 10 .

[0167] In step 730, the authentication device 10 can determine whether the detected sound signal is a pre-promised sound signal.

[0168] The explanation regarding the pre-promised sound signal has been described above with reference to FIG. 4 and will be omitted here.

[0169] In step 740, if the authentication device 10 determines that the detected sound signal is a pre-promised sound signal, it may transmit device identification data.

[0170] In the present disclosure, a pre-promised sound signal can be a trigger that causes a device that detects the pre-promised sound signal to transmit identification data.

[0171] Since the transmission of the device identification data has been described above, a detailed description of the transmission of the device identification data will be omitted.

[0172] In step 750, the authentication device 10 may receive the authenticator data.

[0173] In one embodiment, the authentication device 10 can receive authentication means data from the authentication request device 20 or the server 30. Since the reception of authentication means data has been described above, a detailed description of the reception of authentication means data will be omitted.

[0174] In step 760 , the authentication device 10 may determine whether the received authentication means data matches authentication data stored in the authentication device 10 .

[0175] In step 770, authentication device 10 can transmit to authentication request device 20 whether or not authentication has been successful.

[0176] Steps 760 and 770 correspond to steps 205 and 206 in FIG. 2, respectively, and therefore a detailed description of steps 760 and 770 will be omitted.

[0177] FIG. 8 is a flowchart of an authentication request method according to an embodiment of the present disclosure.

[0178] The operation shown in Fig. 8 can be executed by the above-mentioned personal authentication request device 20. Specifically, the operation shown in Fig. 8 can be executed by a processor included in the above-mentioned personal authentication request device 20.

[0179] In step 810, the authentication requesting device 20 may transmit a pre-promised sound signal.

[0180] Prior to step 810, the authentication request device 20 can detect an approaching person and collect authentication means data, and a pre-promised sound signal can be transmitted in response to collecting the authentication means data.

[0181] In step 820, authentication requesting device 20 may receive device identification data transmitted from the device that detected the pre-promised sound signal.

[0182] In one embodiment, the pre-promised sound signal may include sounds having frequency values ​​outside the audible frequencies.

[0183] In one embodiment, the device identification data may include multiple device identification data.

[0184] In one embodiment, when the device identification data includes multiple device identification data, the authentication requesting device 20 can select one of the multiple device identification data.

[0185] In one embodiment, the collected authenticator data can be sent to a device identified by a selected piece of device identification data.

[0186] In one embodiment, the step of the authentication requesting device 20 selecting one of the plurality of device identification data may include receiving an input selecting one of the plurality of device identification data.

[0187] In one embodiment, if the device identification data includes multiple device identification data, step 820 may be to send the collected authenticator data to each of the multiple devices identified by the multiple device identification data.

[0188] In step 830, authentication requester device 20 may transmit the collected authenticator data to a device identified by the device identification data.

[0189] In one embodiment, after step 830, the authentication request device 20 receives whether the authentication has been successful or not, and can approve or disapprove access to procedures restricted by the authentication based on whether the authentication has been successful or not.

[0190] In the following, an embodiment will be described in which personal authentication is performed by a device other than the personal authentication device. do.

[0191] As described above, for example, the personal authentication device may be a portable electronic device of the user, and the personal authentication request device may be an electronic device provided at an affiliated store of a business that provides a service that the user wants to use. In the above-mentioned embodiment, whether the personal authentication data and the authentication means data match is determined in the user's portable electronic device, i.e., the personal authentication device. Unlike the above-mentioned embodiment, Figs. 7 and 8 relate to an embodiment in which whether the data match is determined in an electronic device provided at an affiliated store of a business that provides a service that the user wants to use, i.e., the personal authentication request device. Also, Figs. 9a and 10a relate to an embodiment in which whether the data match is determined in an authentication-dedicated device, and Figs. 9b, 10b, and 10c relate to an embodiment in which whether the data match is determined in an authentication request device in an authentication system including an authentication-dedicated device.

[0192] In the embodiment described below, the personal authentication device 10 does not determine whether the data match, so the term "user terminal" is used instead of the personal authentication device, but in the technical field to which the present invention is actually applied, the personal authentication device described in Figures 1 to 6 and the user terminal described below may be substantially the same device. That is, the user terminal may be, for example, a portable electronic device of the user.

[0193] Some of the descriptions of the above-mentioned embodiments may be analogously applied to the embodiments described below, and therefore detailed descriptions thereof will be omitted.

[0194] FIG. 9 is a flowchart illustrating a personal authentication process according to still another embodiment of the present disclosure.

[0195] The personal authentication system in which the personal authentication process illustrated in FIG. 9 is carried out may include an authentication request device 20 and a user terminal 40.

[0196] In one embodiment, the authentication request device 20 in step 901 can collect authenticator data.

[0197] In one embodiment, the authentication request device 20 in step 902 can request authentication data from the user terminal 40 .

[0198] In one embodiment, the user terminal 40 in step 903 may transmit authentication data to the authentication request device 20 in response to receiving the request for authentication data.

[0199] In one embodiment, the authentication claimant device 20 in step 904 can be responsive to receiving the authentication data to determine whether the data matches.

[0200] That is, authentication request device 20 can determine whether the received authentication data matches the collected authentication means data.

[0201] Thereafter, depending on the decision of the authentication request device 20, the authentication request device 20 can approve or disapprove access to the procedure restricted by the authentication. For example, if the authentication request device 20 is a device installed at an entrance that allows entry and exit, it can approve entry and exit. As another example, the authentication request device 20 can transmit the result of approval or disapproval to an external device, for example, the user terminal 40.

[0202] FIG. 10 is a flowchart illustrating a personal authentication process according to still another embodiment of the present disclosure.

[0203] Unlike Fig. 9, Fig. 10 relates to an embodiment in which the server 30 mediates in the identity authentication process. Therefore, an identity authentication system capable of performing the identity authentication process described in Fig. 10 may include an identity authentication request device 20, a server 30, and a user terminal 40.

[0204] In one embodiment, the authentication request device 20 in step 1001 can collect authenticator data.

[0205] In one embodiment, the authentication request device 20 in step 1002 can request authentication data from the user terminal 40 .

[0206] In one embodiment, the user terminal 40 in step 1003 may transmit authentication data to the server 30 in response to receiving the request for authentication data.

[0207] In one embodiment, server 30 in step 1004 may transmit the authentication data to authentication request device 20 in response to receiving the authentication data.

[0208] On the other hand, in another embodiment, in step 1003, the user terminal 40 does not directly transmit the personal authentication data, but transmits only the identification number of the user terminal 40, and in step 1004, in response to receiving the identification number of the user terminal 40, the server 30 can transmit the pre-stored personal authentication data of the user terminal 40 to the personal authentication requesting device 20 based on the received identification number.

[0209] In one embodiment, authentication request device 20 in step 1005 may, in response to receiving the authentication data, determine whether the data matches.

[0210] That is, authentication request device 20 can determine whether the received authentication data matches the collected authentication means data.

[0211] Thereafter, depending on the decision of the authentication request device 20, the authentication request device 20 can approve or disapprove access to the procedure restricted by the authentication. For example, if the authentication request device 20 is a device installed at an entrance that allows entry and exit, it can approve entry and exit. As another example, the authentication request device 20 can transmit the result of approval or disapproval to an external device, for example, the user terminal 40.

[0212] 9 and 10, instead of transmitting the authenticator data collected by the authentication request device 20, the authentication data is transmitted to the authentication request device 20 to determine whether the data match. This method may significantly improve the speed of authentication.

[0213] 11a and 11b are flowcharts illustrating an identity authentication process according to still another embodiment of the present disclosure.

[0214] The personal authentication system in which the personal authentication process described in FIGS. 11 a and 11 b is carried out may include an authentication request device 20 , a user terminal 40 , and a personal authentication dedicated device 50 .

[0215] FIG. 11 shows an embodiment in which whether the data matches is determined in a dedicated authentication device. Regarding.

[0216] Steps 1101 and 1102 may correspond to a process in which a user of the user terminal 40 stores his / her personal authentication data in the user's personal authentication dedicated device 50. That is, for the personal authentication process according to this embodiment, the user can store his / her personal authentication data in the personal authentication dedicated device 50.

[0217] In one embodiment, the user terminal 40 in step 1101 can transmit personal authentication data to the personal authentication dedicated device 50 .

[0218] In one embodiment, the authentication dedicated device 50 in step 1102 may store the authentication data in response to receiving the authentication data.

[0219] The stored authentication data can be used for authentication in a later step.

[0220] Thereafter, in one embodiment, the authentication request device 20 in step 1103 may collect authenticator data.

[0221] In one embodiment, the authentication request device 20 in step 1104 can request a dedicated authentication device identification number from the user terminal 40 .

[0222] The dedicated authentication device identification number may refer to a number for identifying a device dedicated to the personal authentication of a specific user. The dedicated authentication device identification number may be provided in any format.

[0223] In one embodiment, the user terminal 40 in step 1105 may transmit the dedicated authentication device identification number to the authentication request device 20 in response to receiving the dedicated authentication device identification number request.

[0224] In one embodiment, the authentication request device 20 in step 1106 may transmit 906 authenticator data to the authentication dedicated device 50 in response to receiving the dedicated authentication device identification number.

[0225] The authentication requesting device 20 can determine the authentication dedicated device 50 to which the authentication means data should be transmitted based on the received dedicated authentication device identification number.

[0226] In one embodiment, the dedicated authentication device 50 in step 1107 can be responsive to receiving the authenticator data to determine whether the data matches.

[0227] That is, the authentication dedicated device 50 can determine whether the stored authentication data and the received authentication means data match.

[0228] Thereafter, in one embodiment, the authentication-dedicated device 50 can transmit a result of whether the data matches to the authentication request device 20. In one embodiment, the authentication request device 20 can approve or disapprove access to a procedure restricted by authentication based on the received signal. For example, if the authentication request device 20 is a device installed at an entrance that allows entry and exit, it can approve entry and exit. As another example, the authentication request device 20 can transmit a result of approval or disapproval to an external device, for example, the user terminal 40.

[0229] However, in one embodiment, steps 1104 and 1105 may be optional. That is, steps 1104 and 1105 can be omitted in a system according to an embodiment. In the case of a system in which steps 1104 and 1105 are omitted, the authentication request device 20 can receive an input of a dedicated authentication device identification number of the user of the user terminal 40 after step 1103 or before step 1103. For example, the user can input the dedicated authentication device identification number via an input interface provided in the authentication request device 20. The authentication request device 20 can transmit authentication means data based on the input dedicated authentication device identification number.

[0230] FIG. 11b relates to an embodiment in which it is determined whether the data matches in an authentication requesting device in an authentication system including a dedicated authentication device.

[0231] Steps 1111 to 1115 may be the same as steps 1101 to 1105, respectively.

[0232] In one embodiment, the authentication request device 20 in step 1116 can request authentication data from the authentication dedicated device 50 .

[0233] The authentication requesting device 20 can identify the device requesting the authentication data based on the received dedicated authentication device identification number.

[0234] In one embodiment, the authentication dedicated device 50 in step 1117 can transmit authentication data to the authentication request device 20 in response to receiving the request for authentication data.

[0235] In one embodiment, in response to receiving the authentication data, authentication request device 20 at step 1118 can determine whether the data matches.

[0236] That is, the authentication requesting device can determine whether the received authentication data matches the collected authenticator data.

[0237] Then, in one embodiment, the authentication request device 20 can approve or disapprove access to the procedure restricted by the authentication based on the result of whether the data matches. For example, if the authentication request device 20 is a device installed at an entrance that allows entry and exit, it can approve entry and exit. As another example, the authentication request device 20 can transmit the result of approval or disapproval to an external device, for example, the user terminal 40.

[0238] Meanwhile, in one embodiment, steps 914 and 915 may be optional. That is, in a system according to one embodiment, steps 914 and 915 may be omitted. In the case of a system in which steps 914 and 915 are omitted, the authentication request device 20 may receive an input of a dedicated authentication device identification number of the user of the user terminal 40 after step 913 or before step 913. For example, the user may input the dedicated authentication device identification number via an input interface provided in the authentication request device 20. The authentication request device 20 may request authentication data based on the input dedicated authentication device identification number.

[0239] 12a to 12c are flowcharts illustrating an identity authentication process according to still another embodiment of the present disclosure.

[0240] Unlike Figures 11a and 11b, Figures 12a to 12c relate to an embodiment in which the server 30 mediates the identity authentication process. An authentication system capable of carrying out the authentication process may include an authentication request device 20, a server 30, a user terminal 40, and an authentication-only device 50.

[0241] FIG. 12a relates to an embodiment in which it is determined whether the data match in a dedicated authentication device.

[0242] Step 1201, step 1202, and step 1203 may be the same as step 1101, step 1102, and step 1103 in FIG. 11, respectively.

[0243] In one embodiment, the authentication request device 20 in step 1204 may transmit the authenticator data to the server 30 .

[0244] Alternatively, step 1204 may occur at any suitable time prior to step 1207, described below.

[0245] In one embodiment, the authentication request device 20 in step 1205 can request a dedicated authentication device identification number from the user terminal 40 .

[0246] In one embodiment, in response to receiving the request for the dedicated authentication device identification number in step 1206 , the user terminal 40 may transmit the dedicated authentication device identification number to the server 30 .

[0247] In one embodiment, the server 30 in step 1207 may transmit the authentication means data to the dedicated authentication device 50 in response to receiving the authentication means data and the dedicated authentication device identification number.

[0248] The server 30 can determine the personal authentication dedicated device 50 to which the authentication means data is to be transmitted based on the received dedicated authentication device identification number.

[0249] In one embodiment, the authentication dedicated device 50 in step 1208 can be responsive to receiving the authenticator data to determine whether the data matches.

[0250] That is, the authentication dedicated device 50 can determine whether the stored authentication data matches the received authentication means data.

[0251] Thereafter, in one embodiment, the authentication-dedicated device 50 can transmit a result of whether the data matches to the authentication request device 20 via the authentication request device 20 or the server 30. In one embodiment, the authentication request device 20 can approve or disapprove access to a procedure restricted by authentication based on the received signal. For example, if the authentication request device 20 is a device installed at an entrance that allows entry and exit, it can approve entry and exit. As another example, the authentication request device 20 can transmit a result of approval or disapproval to an external device, for example, the user terminal 40.

[0252] Meanwhile, in one embodiment, steps 1205 and 1206 may be optional. That is, in a system according to one embodiment, steps 1205 and 1206 may be omitted. In the case of a system in which steps 1205 and 1206 are omitted, the authentication request device 20 may receive a dedicated authentication device identification number input from the user of the user terminal 40 after step 1203 or before step 1203. For example, the user may input the dedicated authentication device identification number via an input interface provided in the authentication request device 20. The authentication request device 20 receives the input dedicated authentication device identification number. The received dedicated authentication device identification number can be transmitted to the server 30. The server 30 can transmit authentication means data based on the received dedicated authentication device identification number.

[0253] FIG. 12b relates to an embodiment in which in an authentication system including a dedicated authentication device, it is determined whether data in an authentication request device matches.

[0254] Step 1211, step 1212, step 1213, step 1214 and step 1215 can be the same as step 1201, step 1202, step 1203, step 1205 and step 1206, respectively.

[0255] In one embodiment, the server 30 in step 1216 can request authentication data from the authentication dedicated device 50 .

[0256] The server 30 can identify the device requesting the personal authentication data based on the received dedicated authentication device identification number.

[0257] In one embodiment, in step 1217, the authentication dedicated device 50 can transmit authentication data to the authentication request device 20 in response to receiving the request for authentication data.

[0258] In one embodiment, in step 1218, authentication request device 20, in response to receiving the authentication data, can determine whether the data matches.

[0259] That is, the authentication requesting device can determine whether the received authentication data matches the collected authenticator data.

[0260] In one embodiment, the authentication request device 20 can then approve or disapprove access to procedures restricted by authentication based on the result of whether the data matches. For example, if the authentication request device 20 is a device installed at an entrance that allows entry and exit, it can approve entry and exit. As another example, the authentication request device 20 can transmit the result of approval or disapproval to an external device, such as the user terminal 40.

[0261] FIG. 12c relates to another embodiment in which it is determined whether data matches in an authentication requesting device in an authentication system including a dedicated authentication device.

[0262] In certain circumstances, it may be impossible for the personal authentication request device 20 to receive the dedicated authentication device identification number from the user terminal 40. For example, for some reason, such as the user terminal 40 not being close enough to the personal authentication request device 20, the user terminal 40 may not be able to transmit the dedicated authentication device identification number or the personal authentication request device 20 may not be able to receive the dedicated authentication device identification number. Fig. 12c relates to an embodiment that can solve this situation, and unlike Fig. 12a or Fig. 12b, the process of requesting the dedicated authentication device identification number or transmitting the dedicated authentication device identification number may be replaced by another process.

[0263] Steps 1221, 1222, and 1223 may be the same as steps 1211, 1212, and 1213, respectively.

[0264] In one embodiment, the authentication request device 20 in step 1224 can receive input of a dedicated authentication device identification number.

[0265] For example, the user may input the following via an input interface provided in the authentication request device 20: A dedicated authentication device identification number can be entered.

[0266] In one embodiment, the authentication request device 20 in step 1225 can request authentication data from the authentication dedicated device 50 .

[0267] The authentication requesting device 20 can identify the device requesting the authentication data based on the input dedicated authentication device identification number.

[0268] In one embodiment, the authentication dedicated device 50 in step 1226 may transmit authentication data to the server 30 in response to receiving the request for authentication data.

[0269] In one embodiment, server 30 in step 1227 may transmit the authentication data to authentication request device 20 in response to receiving the authentication data.

[0270] In one embodiment, the authentication claimant device 20 in step 1228 can determine whether the received authentication data and the collected authenticator data match.

[0271] In one embodiment, the authentication request device 20 can then approve or disapprove access to procedures restricted by authentication based on the result of whether the data matches. For example, if the authentication request device 20 is a device installed at an entrance that allows entry and exit, it can approve entry and exit. As another example, the authentication request device 20 can transmit the result of approval or disapproval to an external device, such as the user terminal 40.

[0272] FIG. 13 is a flowchart of an identity authentication method according to an embodiment of the present disclosure.

[0273] The operation shown in Fig. 13 can be executed by the above-mentioned personal authentication request device 20, specifically, by the processor of the personal authentication request device 20. The operation of the personal authentication request device 20 shown in Fig. 13 can be the operation of the personal authentication request device 20 of the personal authentication system described with reference to Fig. 9 and Fig. 10. Detailed embodiments related to each step have been described above and will not be repeated here.

[0274] In step 1310, the authentication claimant device 20 can collect authenticator data and transmit a pre-promised sound signal.

[0275] In one embodiment, the authentication requester device 20 can receive device identification data from the device that detected the pre-promised audio signal.

[0276] The authentication requesting device 20 can identify the device requesting transmission of authentication data based on the received device identification data. The above-mentioned embodiments relating to device identification data can be inferentially applied.

[0277] In one embodiment, authentication requesting device 20 may request that the device identified by the device identification data, ie, the device that detected the audio signal, transmits the authentication data.

[0278] In step 1320, authentication requesting device 20 may receive authentication data.

[0279] In one embodiment, authentication request device 20 may receive authentication data directly from a server or from a device that detects a pre-promised audio signal.

[0280] In step 1330, authentication requesting device 20 may determine whether the authenticator data and the received authentication data match.

[0281] FIG. 14 is a flowchart of an authentication request method according to an embodiment of the present disclosure.

[0282] The operation shown in Fig. 14 can be executed by the above-mentioned personal authentication request device 20, specifically, by the processor of the personal authentication request device 20. The operation of the personal authentication request device 20 shown in Fig. 14 can be the operation of the personal authentication request device 20 of the personal authentication system described with reference to Fig. 9 and Fig. 10. Detailed embodiments related to each step have been described above and will not be repeated here.

[0283] In step 1410, the authentication claimant device 20 can collect authenticator data and transmit a pre-promised sound signal.

[0284] In one embodiment, the authentication requester device 20 can receive device identification data from the device that detected the pre-promised audio signal.

[0285] The authentication requesting device 20 can identify the device that is requesting transmission of the authentication-dedicated device identification number based on the received device identification data. The above-mentioned embodiment regarding the device identification data can be inferentially applied.

[0286] In step 1420, authentication requesting device 20 can request the identification number of the authentication-only device corresponding to the device that detected the sound signal.

[0287] Here, the device that detected the sound signal can be a device identified by the device identification data.

[0288] In one embodiment, authentication request device 20 can receive an identification number of the authentication dedicated device from a server or a user terminal.

[0289] In step 1430, authentication requesting device 20 may transmit the authentication means data to the authentication dedicated device corresponding to the device that detected the sound signal.

[0290] In one embodiment, the authentication requesting device 20 can transmit the authenticator data via a server or directly to a dedicated authentication device.

[0291] FIG. 15 is a block diagram of an authentication request device according to an embodiment of the present disclosure.

[0292] Referring to Fig. 15, an authentication request device 1500 may include a communication unit 1510, a processor 1520, and a DB 1530. Only components related to the embodiment are shown in the authentication request device 1500 in Fig. 15. Therefore, a person skilled in the art can understand that other general-purpose components may be further included in addition to the components shown in Fig. 15.

[0293] The communication unit 1510 may include one or more components that enable wired / wireless communication with an external server or device. For example, the communication unit 1510 may include at least one of a short-range communication unit (not shown), a mobile communication unit (not shown), and a broadcast receiving unit (not shown). This can be done.

[0294] DB 1530 is hardware that stores various data processed in authentication request device 1500, and can store programs for processing and controlling processor 1520. DB 1530 can store payment information, user information, and the like.

[0295] The DB1530 supports RAM (random access memory), such as DRAM (dynamic random access memory), SRAM (static random access memory), and ROM (read-only The storage device may include an electrically erasable programmable read-only memory (EEPROM), a CD-ROM, a Blu-ray or other optical disk storage device, a hard disk drive (HDD), a solid state drive (SSD), or flash memory.

[0296] Processor 1520 controls the overall operation of authentication request device 1500. For example, processor 1520 can generally control an input unit (not shown), a display (not shown), communication unit 1510, DB 1530, etc. by executing a program stored in DB 1530. Processor 1520 can generally control the operation of authentication request device 1500 by executing a program stored in DB 1530.

[0297] The processor 1520 can control at least a part of the operations of the authentication request device 1500 described above with reference to FIGS.

[0298] The processor 1520 may be implemented using at least one of ASICs (application specific integrated circuits), DSPs (digital signal processors), DSPDs (digital signal processing devices), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), controllers, micro-controllers, microprocessors, and electrical units for performing other functions.

[0299] In one embodiment, the authentication request device 1500 may be a mobile electronic device. For example, the authentication request device 1500 may be a smartphone, a tablet PC, a PC, a smart TV, a PDA (personal digital assistant), a laptop, a media player, a navigation system, a device equipped with a camera, and other mobile electronic devices. The authentication request device 1500 may also be a wearable device such as a watch, glasses, a hair band, or a ring that has a communication function and a data processing function.

[0300] An identity authentication system according to one embodiment of the present disclosure may include an identity authentication request device that collects authentication means data and transmits a prearranged sound signal, and a user terminal that detects the prearranged sound signal and transmits stored identity authentication data in response to a request.

[0301] In one embodiment, the authentication request device is capable of receiving authentication data and determining whether the authenticator data and the authentication data match.

[0302] In one embodiment, the authentication request device can collect authentication means data in response to detecting an approaching person, and can transmit a pre-promised audio signal in response to collecting the authentication means data.

[0303] In one embodiment, the user terminal transmits device identification data in response to detecting a pre-promised sound signal, and the authentication requesting device can request that the device identified by the device identification data transmit the authentication data.

[0304] In one embodiment, when the device identification data includes multiple device identification data, the authentication requesting device can select one of the multiple device identification data and request to transmit the authentication data to the device identified by the selected one device identification data.

[0305] In one embodiment, the system further includes a server, and the user terminal can transmit authentication data to the server, and the server can transmit the authentication data transmitted from the user terminal to the authentication request device.

[0306] An identity authentication system according to one embodiment of the present disclosure may include an identity authentication request device that collects authentication means data, transmits a pre-agreed sound signal, and transmits the authentication means data, a user terminal that detects the pre-agreed sound signal and transmits an identification number of an identity authentication dedicated device in response to a request, and an identity authentication dedicated device that stores identity authentication data received from the user terminal and determines whether the authentication means data and the identity authentication data match.

[0307] In one embodiment, the authentication request device can collect authentication means data in response to detecting an approaching person, and can transmit a pre-promised audio signal in response to collecting the authentication means data.

[0308] In one embodiment, the user terminal transmits device identification data in response to detecting a pre-promised sound signal, and the authentication request device can request the device identified by the device identification data to transmit an identification number of the authentication-only device.

[0309] In one embodiment, when the device identification data includes multiple device identification data, the authentication requesting device can select one of the multiple device identification data and request the device identified by the selected one device identification data to transmit the identification number of the authentication-dedicated device.

[0310] In one embodiment, the system further includes a server, wherein the authentication request device transmits the collected authentication means data to the server, and the user terminal transmits an identification number of the authentication-dedicated device to the server, and the server transmits the authentication means data transmitted from the authentication request device to the authentication-dedicated device based on the identification number of the authentication-dedicated device.

[0311] The embodiments according to the present invention may be realized in the form of a computer program that can be executed by various components on a computer, and such a computer program may be recorded on a computer-readable medium, which may include a hardware device specially configured to store and execute program instructions, such as a magnetic medium such as a hard disk, a floppy disk, or a magnetic tape, an optical medium such as a CD-ROM or a DVD, a magneto-optical medium such as a floptical disk, a ROM, a RAM, or a flash memory.

[0312] On the other hand, the computer programs are specifically designed and constructed for the purposes of the present invention. and may be known and available to those skilled in the art of computer software. Examples of computer programs may include not only machine code, such as produced by a compiler, but also high-level language code that can be executed by a computer using an interpreter, etc.

[0313] According to one embodiment, the method according to various embodiments of the present disclosure may be provided in a computer program product. The computer program product may be traded between a seller and a buyer as a commodity. The computer program product may be distributed in the form of a machine-readable storage medium (e.g., compact disc read only memory (CD-ROM)) or distributed online (e.g., downloaded or uploaded) via an application store (e.g., Play Store™) or directly between two user devices. In the case of online distribution, at least a part of the computer program product may be at least temporarily stored or temporarily generated in a machine-readable storage medium such as a memory of a manufacturer's server, an application store server, or an intermediary server.

[0314] Unless otherwise specified or contrary to the description of the steps constituting the method according to the present invention, the steps may be performed in any suitable order. The order of the steps described above is not necessarily intended to limit the present invention. The use of all examples or exemplary terms (such as, for example, etc.) in the present invention is merely for the purpose of explaining the present invention in detail, and the scope of the present invention is not limited by the examples or exemplary terms unless otherwise limited by the claims. Furthermore, those skilled in the art will understand that various modifications, combinations and changes can be made within the scope of the claims or their equivalents according to design conditions and factors.

[0315] Therefore, the concept of the present invention should not be limited to the above-described embodiments, and all scopes equivalent to or modified equivalently to the scope of the claims, as well as the scope of the claims described below, belong to the concept of the present invention.

Claims

1. As a method of requesting personal authentication, transmitting a prearranged sound signal; receiving device identification data transmitted from a device that detects the pre-promised sound signal; and transmitting the collected authentication means data to a device identified by said device identification data. method.

2. receiving whether the authentication has been successful; approving or disapproving access to procedures restricted by authentication based on whether the authentication has been successful; Further comprising: The method of claim 1.

3. Detecting an approaching person and collecting said authentication means data. Further comprising: The pre-promised sound signal is transmitted in response to collecting said authentication means data; The method of claim 1.

4. If the device identification data includes a plurality of device identification data, The method comprises: Selecting one of the plurality of device identification data. Further comprising: The collected authentication means data includes: to a device identified by said selected one of the device identification data; The method of claim 1.

5. The step of selecting one of the plurality of device identification data includes: receiving an input selecting one of said plurality of device identification data; Further comprising: The method according to claim 4.

6. If the device identification data includes a plurality of device identification data, 4. The method of claim 3, further comprising the steps of: transmitting the collected authentication means data to a device identified by the device identification data; transmitting the collected authentication means data to each of a plurality of devices identified by the plurality of device identification data. The method of claim 1.

7. The pre-promised sound signal is Includes sounds having frequency values ​​outside the audible frequency range. The method of claim 1.

8. In the authentication request device, a memory having at least one program stored therein; a processor that operates by executing the at least one program; The processor, Send a pre-arranged sound signal, receiving device identification data transmitted from a device that detected the pre-promised sound signal; transmitting the collected authentication means data to a device identified by said device identification data; Device.

9. A computer-readable recording medium having recorded thereon a program for causing a computer to execute the method according to claim 1.

10. As a method of identity authentication, transmitting device identification data in response to detecting the pre-promised sound signal; receiving authentication means data transmitted based on the transmitted device identification data; determining whether the authentication means data matches stored authentication data; transmitting whether the authentication has been successful or not based on whether the match is true; Including, method.

Images