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

JP2025508555APending Publication Date: 2025-03-26GHOST PASS INC
View PDF 7 Cites 0 Cited by

Patent Information

Application Number
JP2024553386
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Priority Date
2024-01-16
Filing Date
2024-01-17
Publication Date
2025-03-26

Smart Images

  • Figure 2025508555000001_ABST
    Figure 2025508555000001_ABST
Patent Text Reader

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 collecting authentication means data, detecting one or more devices, determining a nearest device among the one or more devices, receiving device identification data from the nearest device, and transmitting the authentication means data to a device identified by the device identification data.
Need to check novelty before this filing date? Find Prior Art

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 may provide a method for requesting personal authentication, comprising steps of collecting authentication means data and detecting one or more devices, determining a closest device among the one or more devices, receiving device identification data from the closest device, and transmitting the authentication means data to a device identified by the device identification data.

[0007] A second aspect of the present disclosure can provide an 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 collects authentication means data, detects one or more devices, determines a closest device among the one or more devices, receives device identification data from the closest device, and transmits the authentication means data to a device identified by 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 authentication system that includes an authentication request device that collects authentication means data, detects one or more devices, and determines the closest device among the one or more devices, and a user terminal that transmits stored authentication data in response to being determined as the closest device, wherein the authentication request device determines whether the authentication means data and the authentication data match.

[0010] A fifth aspect of the present disclosure is a method for collecting authentication means data, detecting one or more devices, and It is possible to provide an authentication system including an authentication request device that transmits step data and determines the closest device among the one or more devices, a user terminal that transmits an identification number of an authentication-dedicated device in response to being determined as the closest device, and the authentication-dedicated device that stores authentication data received from the user terminal and determines whether the authentication means data and the authentication data match. Effect of the Invention

[0011] 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.

[0012] 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]

[0013] [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 flow chart illustrating an identity authentication process according to one 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 flow chart illustrating a process for determining the targeting of a device identification data request according to one embodiment of the present disclosure. [Diagram 5] FIG. 5 is a schematic diagram illustrating a process for calculating distance to a detected device according to one embodiment of the present disclosure. [Figure 6] FIG. 6 is a flowchart of an authentication request method according to one embodiment of the present disclosure. [Figure 7]FIG. 7 is a flowchart illustrating an identity authentication process according to yet another embodiment of the present disclosure. [Figure 8] FIG. 8 is a flowchart illustrating an identity authentication process according to yet another embodiment of the present disclosure. [Figure 9a-b] 9a and 9b are flow charts illustrating an identity authentication process according to yet another embodiment of the present disclosure. [Figure 10a-c] 10a to 10c are flowcharts illustrating an identity authentication process according to still another embodiment of the present disclosure. [Figure 11] FIG. 11 is a flowchart of an identity authentication method according to one embodiment of the present disclosure. [Figure 12] FIG. 12 is a flowchart of an authentication request method according to one embodiment of the present disclosure. [Figure 13] FIG. 13 is a block diagram of an authentication request device according to one embodiment of the present disclosure. BEST MODE FOR CARRYING OUT THEINVENTION

[0014] 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 collecting authentication means data, detecting one or more devices, determining a nearest device among the one or more devices, receiving device identification data from the nearest device, and transmitting the authentication means data to a device identified by the device identification data. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0015] 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.

[0016] 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.

[0017] 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.

[0018] 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.

[0019] 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 may include any one or more of fingerprint information, genetic (DNA) information, body skeleton 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.

[0020] 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 standard 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. ,Access to restricted procedures may be granted by authentication.

[0021] 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.

[0022] 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.

[0023] 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.

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

[0025] 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.

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

[0027] 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.

[0028] 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).

[0029] 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.

[0030] 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.

[0031] 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.

[0032] 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.

[0033] 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.

[0034] The sensor of the identity authentication device 10 may include a camera. The camera may capture still and video images. A camera may be a device capable of generating 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 a xenon lamp, etc.).

[0035] 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.

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

[0037] 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.

[0038] 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).

[0039] 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 system.

[0040] 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.

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

[0042] 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.

[0043] 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.

[0044] 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.).

[0045] 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.

[0046] 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.

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

[0048] Although not shown in FIG. 1, the personal authentication system according to an embodiment of the present disclosure may further include a dedicated personal authentication device. The dedicated personal authentication device is 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 a dedicated personal authentication device, personal authentication can be performed even when the power of the personal authentication device or the user terminal is turned off. As will be described later, the authentication dedicated device can receive and store authentication data and determine whether subsequently received authentication means data matches the authentication data. The authentication dedicated device will be described in detail below with reference to Figures 9a, 9b, and 10a-10c.

[0049] 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.

[0050] 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.

[0051] 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.

[0052] 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.

[0053] 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.

[0054] FIG. 2 is a flow chart illustrating an identity authentication process according to one embodiment of the present disclosure.

[0055] 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.

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

[0057] 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 can be face recognition, and the authentication request device 20 can collect face data as authentication means data. The user of the authentication device 10 can approach the authentication request device 20 to input face data, and interact with the authentication request device 20. It is possible.

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

[0059] 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.

[0060] 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.

[0061] 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.

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

[0063] 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.

[0064] 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.

[0065] 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 .

[0066] 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.

[0067] 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.

[0068] 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.

[0069] 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.

[0070] 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.

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

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

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

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

[0075] 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.

[0076] 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.

[0077] 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.

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

[0079] 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.

[0080] 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.

[0081] 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.

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

[0083] 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 .

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

[0085] 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 .

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

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

[0088] 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.

[0089] 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.

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

[0091] 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.

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

[0093] 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.

[0094] 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.

[0095] 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.

[0096] 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.

[0097] 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.

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

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

[0100] 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 .

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

[0102] FIG. 4 is a flow chart illustrating a process for determining the targeting of a device identification data request according to one embodiment of the present disclosure.

[0103] The process shown in FIG. 4 can be performed by authentication request device 20, specifically, by a processor included in authentication request device 20.

[0104] As described above, the authentication request device 20 of the present disclosure can request device identification data and receive device identification data. However, the number of devices detected by the authentication request device 20 may be one or more. In this case, the authentication request device 20 of the present disclosure can determine the target of the device identification data request through the process shown in FIG. 4.

[0105] In one embodiment, the authentication requester device 20 in step 410 can collect authenticator data.

[0106] Step 410 may correspond to step 201 in FIG. 2 or step 301 in FIG. 3, so a detailed description of step 410 will be omitted.

[0107] In one embodiment, the authentication request device 20 in step 420 may include one or more The position can be detected.

[0108] In one embodiment, the authentication requesting device 20 can detect one or more devices via any suitable means for detecting devices (e.g., authentication device 10) in the vicinity of the authentication requesting device 20. For example, the authentication requesting device 20 can detect one or more devices by detecting a signal generated by a peripheral device. For example, the authentication requesting device 20 can detect one or more devices by detecting that one or more devices on which an application is installed have approached the authentication requesting device 20.

[0109] In one embodiment, the authentication request device 20 can detect one or more devices by connecting to one or more devices via two-way communication. Specifically, the automatic connection function of the authentication request device 20 for a specific communication method may be in an ON state, and a specific device can connect to the authentication request device 20 by accessing the authentication request device 20, thereby allowing the authentication request device 20 to detect the specific device. In another embodiment, the authentication request device 20 can switch the automatic connection function for a specific communication method to an ON state in response to collecting authentication means data.

[0110] In one embodiment, the one or more devices detected by the authentication request device 20 may be devices that have a record of having been previously paired with the authentication request device 20 via a specific communication method. That is, when the one or more devices that have a record of having been previously paired with the authentication request device 20 via a specific communication method approach the authentication request device 20 within a specific distance, the authentication request device 20 can automatically detect the one or more devices via the specific communication method. For example, the specific communication method can include a Bluetooth method. Meanwhile, in order to detect multiple devices, the authentication request device 20 can include multiple configurations for connecting communication with a device (e.g., the authentication device 10). For example, the authentication request device 20 can include n Bluetooth channels for Bluetooth connection with n devices.

[0111] In one embodiment, the claimant device 20 in step 430 can determine the closest of the one or more detected devices.

[0112] In this embodiment, the authentication request device 20 may determine the closest device among one or more devices in order to determine the input subject of the authentication means data collected by the authentication request device 20. This is because the input subject of the authentication means data collected by the authentication request device 20 is likely to be the person closest to the authentication request device 20.

[0113] In one embodiment, the authentication requesting device 20 may determine the closest device of the one or more detected devices based on any suitable scheme.

[0114] A method for determining the closest device among one or more detected devices by the authentication requesting device 20 according to an embodiment of the present disclosure will be described in detail with reference to FIG.

[0115] In one embodiment, the claiming device 20 in step 440 may receive device identification data from a nearest neighbor device.

[0116] As described above, the purpose of the authentication request device 20 determining the closest device among one or more devices may be to determine the input subject of the authentication means data collected by the authentication request device 20. In this embodiment, the authentication request device 20 can accurately transmit the authentication means data in the subsequent step 450 by receiving device identification data from the input subject of the authentication means data who is presumed to be the same as the user of the closest device.

[0117] For personal authentication based on collected authentication means data, it is necessary to verify that the person attempting personal authentication by inputting authentication means data is the same as the owner of the personal authentication device 10. Conventionally, in order to verify this, the person attempting personal authentication (or via the administrator of the personal authentication request device 20) had to input device identification data (e.g., a telephone number) which is identification information of the personal authentication device 10. However, in the present disclosure, the process of the person attempting personal authentication directly inputting device identification data can be omitted by the authentication request device 20 determining the closest device and receiving device identification data from the closest device via steps 430 and 440. Since it is not necessary to directly input device identification data, the total time required for personal authentication for one person can be significantly reduced, and a highly satisfying experience can be provided to the user of the personal authentication system.

[0118] Prior to step 440, the authentication request device 20 can request device identification data from the nearest device. That is, step 440 can be performed by the authentication request device 20 requesting device identification data from the nearest device. In one embodiment, the authentication device 10 can transmit device identification data upon receiving additional input from the user of the authentication device 10 (e.g., input approving data transmission), and can also automatically transmit device identification data in response to the device identification data request.

[0119] In one embodiment, the authentication request device 20 in step 450 may transmit authenticator data.

[0120] 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. Alternatively, the authentication request device 20 can transmit the authentication means data to a server. Step 450 can correspond to step 204 in Fig. 2 or step 304 in Fig. 3, so a detailed description of step 450 will be omitted.

[0121] In one embodiment, the authentication claimant device 20 in step 460 may initialize its state.

[0122] In this embodiment, initializing the state of the authentication request device 20 may mean deleting the history of detecting one or more devices and switching to the initial state. In other words, since the authentication request device 20 has completed one authentication request by transmitting authentication means data, it can switch to the initial state and prepare for an authentication request for the next person. For example, the authentication request device 20 can release all connections with one or more devices. For example, the authentication request device 20 can forcefully terminate all Bluetooth connections.

[0123] 4, the order in which each step is performed may be appropriately changed. For example, step 460 may be performed after step 440. That is, when the authentication requesting device 20 receives device identification data from one device, it transmits the authentication means data (or transmits server device identification data and authentication means data) to the device identified by the device identification data, rather than transmitting the authentication means data via an existing connection, so that there is no need to maintain any more connections with one or more devices, and the authentication requesting device 20 can initialize its state in response to receiving the device identification data.

[0124] FIG. 5 is a schematic diagram illustrating a process for calculating distance to a detected device according to one embodiment of the present disclosure.

[0125] As described above, authentication requesting device 20 selects the closest device among the one or more detected devices. In one embodiment, the claimant device 20 can calculate a distance to each of one or more devices to determine the closest device. Figure 5 illustrates the process of calculating the distance to a device.

[0126] 5, the communication channel 510 included in the authentication request device 20 is configured to connect communication with a device (e.g., the authentication device 10), and can include a first node 511 and a second node 512. The first node 511 may be referred to as the left channel, and the second node 512 may be referred to as the right channel. As described above, in one embodiment, the authentication request device 20 can connect communication with multiple devices, and therefore the authentication request device 20 can include multiple communication channels. In FIG. 5, one communication channel 510 is shown for convenience of explanation.

[0127] 5, there is shown a first device 520 connected to a communication channel 510 included in the authentication request device 20. As described above, the first device 520 may be one that approaches the authentication request device 20 within a certain distance and is automatically detected by the authentication request device 20 (or the communication channel 510).

[0128] In the present disclosure, what is ultimately to be calculated is the distance D between the authentication request device 20 and the first device 520. In the present disclosure, the distance between the authentication request device 20 and the first device 520 can be considered to be equal to the distance between the communication channel 510 and the first device 520. In one embodiment, the authentication request device 20 can calculate the distance between the authentication request device 20 and the first device 520 by transmitting and receiving test data to the first device 520. Of course, the transmission and reception of the test data can be performed by a communication method that connects the authentication request device 20 and the first device 520.

[0129] Specifically, in one embodiment, the authentication requesting device 20 can transmit test data to the first device 520. In one embodiment, the first device 520 that receives the test data can return the test data to the authentication requesting device 20. That is, the first device 520 can return the received test data to the authentication requesting device 20 as is.

[0130] More specifically, each of the first node 511 and the second node 512 included in the communication channel 510 of the authentication requesting device 20 can transmit test data to the first device 520. Based on the transmission and reception of test data between each of the first node 511 and the second node 512 and the first device 520, the distance between the authentication requesting device 20 and the first device 520 can be calculated.

[0131] If the speed of the radio waves of the test data is v and the time it takes for a node to send the test data back after sending it is t, then the distance between the node and the first device 520 is (v*t) / 2.

[0132] Meanwhile, in one embodiment, the test data transmission / reception process between the authentication request device 20 and the first device 520 may be repeated a preset number of times. Since the distance between the authentication request device 20 and the first device 520 should not be far and a large error may occur in the distance calculated by one test data transmission / reception, it may be preferable to perform the test data transmission / reception process multiple times according to this embodiment.

[0133] Similarly, if the radio wave speed of the test data is v, the total time that one node transmits and receives data to the first device is T, and the preset number of times is n, then the distance between one node and the first device 520 is (v*T) / (2*n).

[0134] The preset number of times can be appropriately set depending on the speed of the radio waves of the test data and the design environment of authentication request device 20. For example, v may be 299,792,458 m / s, and n may be set to about 299,792 times.

[0135] Through the above process, the distances L1 and L2 between the first node 511 and the second node 512, respectively, and the first device 520 can be calculated.

[0136] On the other hand, w, which is the distance between first node 511 and second node 512, may be a value determined by the design of authentication request device 20 (or communication channel 510).

[0137] Since a triangle is formed with three sides of lengths w, L1, and L2, respectively, it is possible to calculate D, which is the distance between the authentication request device 20 and the first device 520, based on various properties of the triangle. For example, the cosine law can be used to calculate the angle between the side between the first node 511 and the second node 512 and the side between the first node 511 and the first device 520, and D can be calculated based on the calculated angle and L1. This is provided merely as an example, and any of a variety of triangle properties can be used to calculate the distance between the authentication request device 20 and the first device 520.

[0138] As described above, the authentication request device 20 can be connected to multiple devices for communication, and thus the authentication request device 20 can include multiple communication channels. In one embodiment, the authentication request device 20 can calculate the distance between the authentication request device 20 and the devices connected to each of the multiple communication channels included in the authentication request device 20. In one embodiment, the authentication request device 20 can determine the closest device based on the calculated distance to each of the multiple devices.

[0139] FIG. 6 is a flowchart of an authentication request method according to one embodiment of the present disclosure.

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

[0141] In step 610, the authentication requester device 20 may collect authenticator data and detect one or more devices.

[0142] In one embodiment, the one or more devices may be devices that have a record of having been previously paired via a particular communication method, and step 610 may detect the one or more devices via the particular communication method.

[0143] In step 620, the authentication requesting device 20 may determine which of the one or more devices is closest.

[0144] In one embodiment, step 620 may include calculating distances to each of the one or more devices.

[0145] In one embodiment, the step of calculating the distance to each of the one or more devices may include a step of transmitting and receiving test data to a first device included in the one or more devices, and a step of calculating the distance to the first device based on the time required to transmit and receive the test data and the speed of the radio waves of the test data.

[0146] In one embodiment, the step of transmitting and receiving test data may include repeating a preset number of times of transmitting test data to the first device and receiving test data returned from the first device.

[0147] In one embodiment, the test data may be transmitted via the first node and the second node.

[0148] In one embodiment, calculating the distance to the first device may include calculating a first distance between the first node and the first device and a second distance between the second node and the first device.

[0149] In one embodiment, calculating the distance to the first device may include calculating the distance to the first device based on a distance between the first node and the second node, the first distance, and the second distance.

[0150] In one embodiment, step 620 may include determining the device with the shortest calculated distance as the proximate device.

[0151] In step 630, the claiming device 20 may receive device identification data from the nearest device.

[0152] In step 640, the authenticator data may be transmitted to the device identified by the device identification data.

[0153] In one embodiment, step 640 may involve transmitting the authenticator data via a server to the device identified by the device identification data.

[0154] In one embodiment, after step 640, authentication requesting device 20 can receive the success or failure of the authentication and can approve or disapprove access to procedures restricted by the authentication based on the success or failure of the authentication.

[0155] In the following, an embodiment will be described in which authentication is performed by a device that is not an authentication device.

[0156] 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.

[0157] 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.

[0158] 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.

[0159] FIG. 7 is a flowchart illustrating an identity authentication process according to yet another embodiment of the present disclosure.

[0160] An authentication system in which the authentication process illustrated in FIG. 7 is carried out may include authentication request device 20 and user terminal 40.

[0161] In one embodiment, the authentication requester device 20 in step 701 can collect authenticator data.

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

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

[0164] In one embodiment, the authentication requester 20 in step 704 can be responsive to receiving the authentication data to determine whether the data matches.

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

[0166] 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.

[0167] FIG. 8 is a flowchart illustrating an identity authentication process according to yet another embodiment of the present disclosure.

[0168] Unlike Fig. 7, Fig. 8 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. 8 may include an identity authentication request device 20, a server 30, and a user terminal 40.

[0169] In one embodiment, the authentication requester device 20 in step 801 can collect authenticator data.

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

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

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

[0173] On the other hand, in another embodiment, in step 803, 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 804, 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.

[0174] In one embodiment, the authentication request device 20 in step 805 can be responsive to receiving the authentication data to determine whether the data matches.

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

[0176] 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.

[0177] 7 and 8, rather than transmitting authenticator data collected by authentication request device 20, authentication data is transmitted to authentication request device 20 to determine whether the data match. This method may significantly improve the speed of authentication.

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

[0179] An authentication system in which the authentication process described in FIGS. 9a and 9b is carried out may include an authentication request device 20, a user terminal 40, and an authentication-only device 50.

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

[0181] Steps 901 and 902 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.

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

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

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

[0185] Thereafter, in one embodiment, the authentication claimant device 20 in step 903 may collect authenticator data.

[0186] In one embodiment, the authentication request device 20 in step 904 is a user terminal 4 0 may be requested to provide a dedicated authentication device identification number.

[0187] 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.

[0188] In one embodiment, the user terminal 40 in step 905 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.

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

[0190] 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.

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

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

[0193] 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.

[0194] Meanwhile, in one embodiment, steps 904 and 905 may be optional. That is, steps 904 and 905 may be omitted in a system according to one embodiment. In the case of a system in which steps 904 and 905 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 903 or before step 903. 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 transmit authentication means data based on the input dedicated authentication device identification number.

[0195] FIG. 9b 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.

[0196] Steps 911 to 915 may be the same as steps 901 to 905, respectively.

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

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

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

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

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

[0202] 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.

[0203] 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.

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

[0205] 9a and 9b, Fig. 10a to Fig. 10c relate to an embodiment in which the server 30 mediates in the identity authentication process. Therefore, an identity authentication system capable of carrying out the identity authentication process described in Fig. 10a to Fig. 10c may include an identity authentication requesting device 20, a server 30, a user terminal 40, and an identity authentication dedicated device 50.

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

[0207] Steps 1001, 1002, and 1003 may be the same as steps 901, 902, and 903 in FIG. 9, respectively.

[0208] In one embodiment, the authentication request device 20 in step 1004 can transmit the authenticator data to the server 30 .

[0209] Alternatively, step 1004 may occur at any suitable time before step 1007, described below.

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

[0211] In one embodiment, receiving the request for the dedicated authentication device identification number in step 1006 In response, the user terminal 40 can transmit a dedicated authentication device identification number to the server 30.

[0212] In one embodiment, the server 30 in step 1007 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.

[0213] 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.

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

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

[0216] 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.

[0217] Meanwhile, in one embodiment, steps 1005 and 1006 may be optional. That is, steps 1005 and 1006 may be omitted in a system according to one embodiment. In the case of a system in which steps 1005 and 1006 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 1003 or before step 1003. 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 transmit the input dedicated authentication device identification number to the server 30. The server 30 may transmit authentication means data based on the received dedicated authentication device identification number.

[0218] FIG. 10b relates to an embodiment in which it is determined whether the data matches in an authentication requesting device in an authentication system that includes a dedicated authentication device.

[0219] Step 1011, step 1012, step 1013, step 1014 and step 1015 may be the same as step 1001, step 1002, step 1003, step 1005 and step 1006, respectively.

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

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

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

[0223] In one embodiment, authentication request device 20 in step 1018 can be responsive to receiving the authentication data to determine whether the data matches.

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

[0225] 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.

[0226] FIG. 10c 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.

[0227] 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. 10c relates to an embodiment that can solve this situation, and unlike Fig. 10a or Fig. 10b, the process of requesting the dedicated authentication device identification number or transmitting the dedicated authentication device identification number may be replaced by another process.

[0228] Steps 1021, 1022 and 1023 may be the same as steps 1011, 1012 and 1013, respectively.

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

[0230] For example, the user can input the dedicated authentication device identification number via an input interface provided in authentication request device 20 .

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

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

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

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

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

[0236] 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.

[0237] FIG. 11 is a flowchart of an identity authentication method according to one embodiment of the present disclosure.

[0238] The operation shown in Fig. 11 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. 11 may be the operation of the personal authentication request device 20 of the personal authentication system described with reference to Fig. 7 and Fig. 8. Detailed embodiments related to each step have been described above, and therefore will not be repeated.

[0239] In step 1110, the authentication requester device 20 may collect authenticator data and detect one or more devices.

[0240] In step 1120, the authentication requesting device 20 may determine which of the one or more devices is closest.

[0241] In one embodiment, the claiming device 20 can receive device identification data from a nearest neighbor device.

[0242] The authentication request device 20 can identify the device that requests transmission of authentication data based on the received device identification data. The above-mentioned embodiment regarding the device identification data can be applied analogously.

[0243] In one embodiment, authentication requesting device 20 may request that the device identified by the device identification data, i.e., the closest device, transmit the authentication data.

[0244] In one embodiment, authentication requesting device 20 may receive authentication data from a server or a nearest neighbor device.

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

[0246] FIG. 12 is a flowchart of an authentication request method according to one embodiment of the present disclosure.

[0247] The operation shown in Fig. 12 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. 12 may be the operation of the personal authentication request device 20 of the personal authentication system described with reference to Figs. 9 and 10. Detailed embodiments related to each step have been described above, and therefore will not be repeated.

[0248] In step 1210, the authentication requester device 20 may collect authenticator data and detect one or more devices.

[0249] In step 1220, the authentication requesting device 20 may determine which of the one or more devices is closest.

[0250] In one embodiment, the authentication requesting device 20 can receive device identification data from a nearest neighbor device.

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

[0252] In one embodiment, the authentication requesting device 20 can request the identification number of the authentication-only device that corresponds to the closest device.

[0253] In one embodiment, authentication requesting device 20 can receive an authentication-only device identification number.

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

[0255] In step 1230, authentication requesting device 20 may transmit the authenticator data to the authentication dedicated device corresponding to the closest device.

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

[0257] FIG. 13 is a block diagram of an authentication request device according to one embodiment of the present disclosure.

[0258] Referring to Fig. 13, the authentication request device 1300 may include a communication unit 1310, a processor 1320, and a DB 1330. Only components related to the embodiment are shown in the authentication request device 1300 in Fig. 13. 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. 13.

[0259] The communication unit 1310 may include one or more components that enable wired / wireless communication with an external server or device, For example, the communication unit 1310 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).

[0260] DB 1330 is hardware that stores various data processed in authentication request device 1300, and can store programs for processing and controlling processor 1320. DB 1330 can store payment information, user information, and the like.

[0261] The DB1330 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.

[0262] The processor 1320 controls the overall operation of the authentication request device 1300. For example, the processor 1320 executes a program stored in the DB 1330 to The processor 1320 can generally control a power supply unit (not shown), a display (not shown), a communication unit 1310, a DB 1330, etc. The processor 1320 can control the operation of the authentication request device 1300 by executing a program stored in the DB 1330.

[0263] The processor 1320 can control at least a part of the operations of the authentication request device 1300 described above with reference to FIGS.

[0264] The processor 1320 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.

[0265] In one embodiment, the authentication request device 1300 may be a mobile electronic device. For example, the authentication request device 1300 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 1300 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.

[0266] An identity authentication system according to one embodiment of the present disclosure may include an identity authentication requesting device that collects authentication means data, detects one or more devices, and determines the closest device among the one or more devices, and a user terminal that transmits stored identity authentication data in response to being determined as the closest device.

[0267] In one embodiment, the authentication request device can determine whether the authenticator data and the authentication data match.

[0268] In one embodiment, the claimant device can calculate a distance to each of one or more devices and determine the device with the shortest calculated distance as the closest device.

[0269] In one embodiment, calculating the distance to each of the one or more devices may include transmitting and receiving test data to a first device included in the one or more devices, and calculating the distance to the first device based on the time required to transmit and receive the test data and the speed of radio waves of the test data.

[0270] In one embodiment, transmitting and receiving the test data may include repeating transmitting the test data to the first device and receiving the test data returned from the first device a preset number of times.

[0271] 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.

[0272] According to another embodiment of the present disclosure, the personal authentication system collects authentication means data and performs one or more The personal authentication request device may include a user terminal that detects the device, transmits authentication means data, and determines the closest device among the one or more devices, a user terminal that transmits an identification number of a personal authentication dedicated device in response to being determined as the closest device, and a personal authentication dedicated device that stores personal authentication data received from the user terminal and determines whether the authentication means data and the personal authentication data match.

[0273] In one embodiment, the authentication claimant device can calculate a distance to each of one or more devices and determine the device with the shortest calculated distance as the closest device.

[0274] In one embodiment, calculating the distance to each of the one or more devices may include transmitting and receiving test data to a first device included in the one or more devices, and calculating the distance to the first device based on the time required to transmit and receive the test data and the speed of radio waves of the test data.

[0275] In one embodiment, transmitting and receiving the test data may include repeating transmitting the test data to the first device and receiving the test data returned from the first device a preset number of times.

[0276] 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.

[0277] 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.

[0278] On the other hand, the computer programs may be those specially designed and constructed for the present invention, or they may be those well known and available to those skilled in the computer software art. 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.

[0279] 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.

[0280] 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.

[0281] 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 for requesting personal authentication, collecting authentication means data and detecting one or more devices; determining a closest device among said one or more devices; receiving device identification data from said nearest neighbor device; transmitting said authentication means data to a device identified by said device identification data; Including, method.

2. The step of determining a nearest neighbor device comprises: calculating a distance to each of the one or more devices; determining the device with the shortest calculated distance as the closest device; Including, The method of claim 1.

3. Calculating a distance to each of the one or more devices comprises: transmitting and receiving test data to and from a first device included in the one or more devices; calculating a distance to the first device based on a time required for transmitting and receiving the test data and a radio wave speed of the test data; Including, The method of claim 2.

4. The step of transmitting and receiving test data includes: Repeating a predetermined number of times of transmitting test data to the first device and receiving the test data returned from the first device; Including, The method according to claim 3.

5. The test data is transmitted via the first node and the second node; The step of calculating a distance to the first device comprises: calculating a first distance between the first node and the first device and a second distance between the second node and the first device; calculating a distance to the first device based on a distance between the first node and the second node, the first distance, and the second distance; Including, The method according to claim 3.

6. The one or more devices include A device that has a record of being paired in the past via a specific communication method, The step of detecting the one or more devices further comprises: detecting the one or more devices via the particular communication method; The method of claim 1.

7. The step of transmitting the authentication means data to a device identified by the device identification data comprises: transmitting said authentication means data via a server to a device identified by said device identification data; The method of claim 1.

8. receiving a result of authentication; based on the success or failure of said authentication, approving or disapproving access to procedures restricted by said authentication; Further comprising: The method of claim 1.

9. In the authentication request device, a memory having at least one program stored therein; a processor operable by executing said at least one program; The processor, Collecting authentication means data and detecting one or more devices; determining a closest device among the one or more devices; receiving device identification data from said nearest neighbor device; Sending the authenticator data to a device identified by the device identification data Device.

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

Citation Information

Patent Citations

  • In-vehicle machine, mobile terminal, and in-vehicle machine system including them, and program for in-vehicle machine

    JP2008189163A

  • Data communication system for working machine

    JP2014071707A

  • Tour assist method and program therefor and storage device therefor and tour assist system

    JP2014092942A

  • Job execution device, job execution device control method, and program

    JP2017027313A

  • Information processing device, method for controlling information processing device and program

    JP2022071684A