JP7638333B2 - User authentication system and mobile terminal - Google Patents

Description

The present invention relates to a user authentication technique in an information processing device such as a mobile terminal, and more particularly to a user authentication technique using an auxiliary authentication device.

A security protection technology that restricts the use of information processing devices such as mobile terminals by other people.
Some of them use auxiliary authentication devices other than portable terminals. For example, Patent Document 1 discloses a technology in which "a portable terminal device that performs wireless communication with another wireless communication device includes a storage means for storing identification information of a specific wireless communication device registered in advance, a wireless communication means for receiving a signal transmitted from the other wireless communication device, and a control means. The control means obtains the identification information included in the signal received by the wireless communication means, and enables a specific function of the portable terminal device when the identification information matches the identification information stored in the storage means (abstract excerpt)."

JP 2005-130008 A

According to the technology disclosed in Patent Document 1, it is possible to prevent the risk of a mobile terminal device being used by a person who does not have a specific wireless communication device without performing complicated operations. However, information for authentication, for example, identification information of the specific wireless communication device described above, is transmitted and received wirelessly. Interception or eavesdropping of this information is not taken into consideration.

The present invention has been made in consideration of the above circumstances, and has an object to provide a technique for improving security when performing user authentication on a mobile terminal using an auxiliary authentication device.

The present invention is a user authentication system for authenticating a user of a main device, the system comprising a main device and an authentication device that communicates with the main device, the main device storing authentication source information having a plurality of pairs of a first value selected for each transmission and a second value associated with the first value, selecting the first value from the authentication source information based on a predetermined rule, setting the second value stored in the authentication source information in association with the selected first value as a matching authentication code, and generating an authentication code transmission request including the selected first value,
The authentication device transmits a request to send an authentication code to the authentication device, and the authentication device stores biometric information of the person holding the authentication device, which was acquired in advance before authentication, as biometric information for matching, receives the request to send the authentication code sent from the main device, stores the original information for authentication, and in response to the request to send the authentication code, acquires the biometric information and performs biometric authentication using the biometric information for matching, and if the biometric authentication is successful, generates the second value stored in the original information for authentication in correspondence with the first value as an authentication code and transmits the authentication code to the main device, and if the authentication code sent from the authentication device includes the authentication code for matching, the main device determines that the authentication is successful, and if it determines that the authentication is successful, enables a predetermined function, and if it does not determine that the authentication is successful, transmits the request to send the authentication code to the authentication device every time a predetermined time has elapsed .

According to the present invention, security is improved when performing user authentication on a mobile terminal using an auxiliary authentication device. Problems, configurations and effects other than those described above will become apparent from the following description of the embodiments.

1 is an overall view of a user authentication system according to a first embodiment; FIG. 2 is a hardware configuration diagram of a main device according to the first embodiment. FIG. 2 is a functional block diagram of a main device according to the first embodiment. FIG. 2A is a hardware configuration diagram of an authentication device according to a first embodiment, and FIG. 2B is a functional block diagram of the authentication device according to the first embodiment. 11 is a flowchart of a user authentication process according to the first embodiment. FIG. 1A is an explanatory diagram for explaining an example of authentication source information in the first embodiment, FIG. 1B is an explanatory diagram for explaining an example of an authentication code transmission request in the first embodiment, and FIG. 1C is an explanatory diagram for explaining an example of an authentication code in the first embodiment. 1A is a hardware configuration diagram of an authentication device according to a second embodiment, and FIG. 1B is a functional block diagram of the authentication device according to the second embodiment. 13 is a flowchart of a user authentication process according to the second embodiment. 13A is an explanatory diagram for explaining an example of authentication source information in the second embodiment, FIG. 13B is an example of an authentication code transmission request in the second embodiment, and FIG. 13C and FIG. 13D are explanatory diagrams for explaining an example of an authentication code in the second embodiment. FIG. 13 is a functional block diagram of a main device according to a third embodiment. 13A is a hardware configuration diagram of an authentication device according to a third embodiment, and FIG. 13B is a functional block diagram of the authentication device according to the third embodiment. 13 is a flowchart of a user authentication process according to the third embodiment. FIG. 13A is an explanatory diagram for explaining an example of a behavior history according to the third embodiment, and FIG. 13B is an explanatory diagram for explaining an example of a normal behavior range according to a modified example of the third embodiment. 13 is a flowchart of a behavior history collection process and an authentication process according to a modified example of the third embodiment. 13A is a functional block diagram of a main body device according to a fourth embodiment, and FIG. 13B is a functional block diagram of an authentication device according to the fourth embodiment. 13A is a flowchart of an initial setting process according to a fourth embodiment, and FIG. 13B is a flowchart of a modified example of the initial setting process according to the fourth embodiment. FIG. 13 is an explanatory diagram for explaining an example of a variable output wireless communication device according to a modified example of the fourth embodiment. 13 is a flowchart of a user authentication process according to a modified example of the present invention. 13 is a flowchart of a user authentication process according to another modified example of the present invention.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Hereinafter, embodiments of the present invention will be described with reference to the drawings. In the following description, unless otherwise specified, components having the same functions are denoted by the same reference numerals and repeated explanations will be omitted.

<<First embodiment>>
First, an overview of a first embodiment of the present invention will be described below. Fig. 1 is a diagram for explaining an overview of a user authentication system 100 according to the present embodiment.

The user authentication system 100 includes a main device 200 and an authentication device 300. The authentication device 300 is an auxiliary authentication apparatus used to authenticate a user of the main device 200. That is, in this embodiment, a specific function of the main device 200 can be used only by a user who holds the authentication device 300.

In general, when using the authentication device 300, which is such an auxiliary authentication device, the authentication code is transmitted and received between the authentication device 300 and the main device 200 via wireless communication. The security of the communication is not taken into consideration. Therefore, once the authentication code is intercepted, the authentication device 300
Even a person who does not have a personal identification number can use the functions of the main device 200. In this embodiment, to avoid this, the authentication code transmitted from the authentication device 300 to the main device 200 is changed every time, thereby increasing the confidentiality of the authentication code and improving security during transmission and reception.

The following describes the user authentication system 100 of this embodiment, which realizes the above processing.

[Main device]
First, the main device 200 will be described. The main device 200 is an information processing device having a wireless communication function and an information processing function. For example, the main device 200 is a mobile phone, a smartphone, a tablet terminal, a wearable terminal such as a watch or a head mounted display, a feature phone, or other portable digital device.

2 shows the hardware configuration of the main device 200. As shown in this figure, the main device 200 includes a CPU (Central Processing Unit) 201, a system bus 202, a storage device 210, a communication processor 220, an expansion I/F 227, an operation unit 230, a video processor 240, an audio processor 250, and a sensor 26.
0.

The CPU 201 is a microprocessor unit that controls the entire main device 200. The system bus 202 is a data communication path for transmitting and receiving data between the CPU 201 and each operation block in the main device 200.

The storage device 210 includes a ROM (Read Only Memory) 211 and a RAM (
The storage device 210 includes a random access memory (RRAM) 212 and a storage 213.

The ROM 211 is a memory in which basic operation programs such as an operating system and other operation programs are stored.
Electrically Erasable and Programmable Re
A rewritable ROM such as a Read Only Memory (ROM) or a flash ROM is used.

The storage 213 stores the operation programs and operation setting values of the main device 200, as well as various programs and various data required to realize the various functions of this embodiment.

The storage 213 holds stored information even when power is not being supplied from an external source to the main device 200. For this reason, the storage 213 may include, for example, a flash ROM, an SSD (Solid State Drive), an HDD (Hard Disk Drive), or the like.
A device such as a USB 2.0 .sk Drive is used.

The RAM 212 is a work area for executing the basic operation program and other operation programs.

The ROM 211 and the RAM 212 may be integrated with the CPU 201. The ROM 211 may not be an independent configuration as shown in FIG. 2, but may use a part of the storage area in the storage 213.
All or part of the functions of OM211 may be replaced.

The operation programs stored in the ROM 211 and the storage 213 can be updated and their functions expanded, for example, by downloading from each distribution server on the network.

The communication processor 220 includes a LAN (Local Area Network) communication device 221.
The terminal 220 includes a telephone network communication device 222 , a wired communication device 223 , a close-proximity wireless communication device 224 , and a wireless communication device 225 .

The LAN communication device 221 is connected to a network via an access point (AP) device by wireless connection such as Wi-Fi (registered trademark), and transmits and receives data to and from other devices on the network.

The telephone network communicator 222 transmits and receives calls and data via wireless communication with a base station of a mobile telephone network.

The wired communication device 223 transmits and receives data to and from other devices in the vicinity of the main device 200 via a wired connection means such as a Universal Serial Bus (USB).

The close-proximity wireless communication device 224 transmits and receives data to and from other devices equipped with close-proximity wireless communication devices via wireless communication. The close-proximity wireless communication device 224 is, for example, a near field communication (NFC) device.
It is an interface for Near Field Communication (NFC) that realizes two-way communication between devices equipped with NFC chips over extremely short distances of a few centimeters to about one meter. For example, it supports services that use contactless IC chips such as electronic money equipped in the main device 200.

The wireless communication device 225 transmits and receives data to and from other devices equipped with wireless communication devices via wireless communication. For example, Bluetooth (registered trademark) or the like can be used to realize simple information exchange using radio waves between information devices at a distance of several meters to several tens of meters.

The LAN communication device 221, the telephone network communication device 222, the wired communication device 223, the close proximity wireless communication device 224, and the wireless communication device 225 each include an encoding circuit, a decoding circuit, an antenna, and the like.
Furthermore, the communication processor 220 may further include a communication device that realizes infrared communication or other communication devices.

The expansion I/F 227 is a group of interfaces for expanding the functions of the main device 200. In this embodiment, the expansion I/F 227 includes a video/audio I/F, an operation device I/F, a memory I/F, and the like.
The video/audio I/F inputs video/audio signals from external video/audio output devices, outputs video/audio signals to external video/audio input devices, etc. External operation devices such as keyboards are connected via the operation device I/F. The memory I/F connects memory cards and other memory media to send and receive data.

The operation device 230 inputs operation instructions to the main device 200. In this embodiment, the operation device 230 includes a touch panel and an operation key having button switches arranged on top of the display 241. Note that only one of them may be used. The main device 200 may be operated using a keyboard or the like connected to the expansion I/F 227. The main device 200 may be operated using a separate mobile information terminal device connected by wired or wireless communication. The display 241 may also have a touch panel function.

The video processor 240 includes a display 241 , an image signal processor 242 , and a camera 243 .

The display 241 is a display device such as a liquid crystal panel, and displays image data processed by the image signal processor 242 and provides the image data to the user of the main device 200. The image signal processor 242 includes a video RAM (not shown), and the display 241 is driven based on image data input to the video RAM.
2. Convert the format, add menus and other OSDs (On-Screen Displays) as needed.
The camera 243 performs superimposition processing of the display signal.
Coupled Device) and CMOS (Complementary Metal
It is an imaging device that captures the surroundings and objects as image data by converting light input from a lens into an electrical signal using electronic devices such as a semiconductor (oxide semiconductor) sensor.

The audio processor 250 includes a speaker 251, an audio signal processor 252, and a microphone 253. The speaker 251 provides an audio signal processed by the audio signal processor 252 to the user of the main device 200. The microphone 253 converts the user's voice, etc., into audio data and inputs it.

The sensor 260 is a group of sensors for detecting the state of the main device 200. In this embodiment, the sensor 260 includes, for example, a GPS (Global Positioning System) receiver 261, a gyro sensor 262, a geomagnetic sensor 263, an acceleration sensor 264, an illuminance sensor 265, a proximity sensor 266, and a biometric sensor 267.

These sensors detect the position, inclination, direction, and movement of the main device 200, the surrounding brightness, and the user's biological information.
The device may further include a pressure sensor or other sensors. The location information is acquired by a GPS receiver 261.
In places where GPS signals are difficult to receive, the LAN communication device 221 can be used to acquire the information via Wi-Fi.
The location information may be acquired using the location information of the Fi AP device, or similarly, the location information may be acquired by a location information acquisition method using the location information of the base station and the propagation delay of the telephone communication radio wave by the telephone network communication device 222. Also, it is not necessary to have all of these sensor groups.

2 includes many components that are not essential to this embodiment, but the effects of this embodiment are not impaired even if these components are not provided. In addition, components not shown, such as a digital broadcast receiving function and an electronic money settlement function, may be added.

[Functional configuration of the main device]
The functions realized by the main device 200 will be described with reference to Fig. 3. As described above, when a user attempts to execute a predetermined function, the main device 200 of the present embodiment requests user authentication from the authentication device, and allows the execution of the function if the authentication is successful.

To achieve this, the main device 200 includes an authentication code transmission request generating unit 271 , a matching unit 272 , an unlocking unit 273 , a transmitting/receiving unit 274 , and an operation control unit 275 .

These functions are implemented by the CPU 201 reading a program stored in the ROM 211 and executing it in the RAM.
3 shows the functions realized by the programs stored in the ROM 211.

In addition, the storage 213 (main body storage unit) stores the authentication source information 2 as reference information 280.
In the storage 212, a program 216 is stored, which includes an algorithm 218, an authentication code generation algorithm 281, an authentication code generation algorithm 282, and a transmission request generation algorithm 283. These data are stored in advance in the storage 213. When each of the above functions is executed, the CPU 201 saves and uses this data in a temporary storage area 292 of the RAM 212. The temporary storage area of the RAM 212 also stores data generated during the execution of each program stored in the ROM 211, data obtained as a result of the execution, and the like.

The transmission/reception unit 274 is connected to the communication processor 220 or the expansion I/F 227, for example, a USB
/F controls the sending and receiving of data to and from external devices.

The authentication code transmission request generating unit 271 generates an authentication code transmission request for requesting transmission of an authentication code from the authentication device 300. The authentication code transmission request is generated, for example, when an instruction to execute a function that is set to require authentication prior to execution (authentication-required function) is received. This authentication code transmission request is generated according to the transmission request generating algorithm 283. At this time, a different authentication code is generated for each request.

The generated authentication code transmission request is transmitted to the authenticated device 300 via the transmission/reception unit 274. That is, the authentication code transmission request generating unit 271 and the transmission/reception unit 274 function as an authentication code transmission request unit.

The verification unit 272 verifies the validity of the authentication code returned from the authenticated device 300 in response to the authentication code transmission request.
and the authentication code generation algorithm 282 to generate a verification authentication code. Then, the generated verification authentication code is compared (verified) with the returned authentication code to determine its validity. For example, if the authentication code sent from the authentication device 300 matches the verification authentication code, it is determined that the authentication is successful.

When the verification unit 272 determines that the authentication code is valid, the unlocking unit 273 enables (enables) the authentication-requiring functions.

The operation control unit 275 controls each unit of the main device 200 so as to realize the authentication-required functions that are permitted to be executed by the unlocking unit 273. The operation control unit 275 also functions as a reception unit that receives various instructions via the operation device 230.

[Authentication device hardware configuration]
Next, the authentication device 300 will be described.
00 is held by a user who is authorized to operate the device, and generates and returns an authentication code in response to a request from the main device 200.

The hardware configuration of an authentication device 300 that realizes this is shown in Fig. 4(a). As shown in this figure, the authentication device 300 includes a CPU 301, a system bus 302, and a storage device 303.
10 and a communication processor 320.

The CPU 301 is a microprocessor unit that controls the overall operation of the authentication device 300. The system bus 302 is a data communication path for transmitting and receiving data between the CPU 301 and each operation block in the authentication device 300.

The memory device 310 includes a ROM 311 , a RAM 312 , and a storage 313 .
These have basically the same functions and configurations as the components of the main device 200 with the same names.

The communication processor 320 includes a wired communication device 323, a close-proximity wireless communication device 324, and a wireless communication device 325.
These also have basically the same functions and configurations as the components of the main device 200 with the same names.

The authentication device 300 may have the same configuration as the main device 200. For example, the authentication device 300 may further include an expansion I/F 227.
The hardware configuration may include all of the above.

[Authentication device functional configuration]
4B, a description will be given of functions realized by the authentication device 300. As described above, the authentication device 300 of this embodiment returns an authentication code in response to a request from the main device 200.

To achieve this, the authentication device 300 includes an authentication code generating unit 371 and a transmitting/receiving unit 3
These functions are implemented by executing a program stored in the ROM 311 on the CPU 30.
1 is deployed in RAM 312 as an execution program 391 and executed.

In addition, the storage 313 (authentication storage unit) stores the authentication source information 2 as reference information 380.
The authentication code generating algorithm 281 and the authentication code generating algorithm 282 are copies of the same data stored in the main device 200.

When each of the above functions is executed, the CPU 301 stores and uses these data in a temporary storage area 392 of the RAM 312.
The program storage section 11 stores each program stored in the program memory 11, data generated during execution, and data obtained as a result of execution.

The transmission/reception unit 372 controls the transmission and reception of data to and from external devices via the communication processor 320 .

When the authentication code generating unit 371 receives an authentication code transmission request from the main device 200 via the transmitting/receiving unit 372, it generates an authentication code. The authentication code is generated using information included in the authentication code transmission request, the authentication source information 281, and the authentication code generating algorithm 282. The generation method is the same as the method used by the matching unit 272 of the main device 200 to generate a matching authentication code.

The generated authentication code is returned to the main device 200 via the transmission/reception unit 372. That is, the authentication code generation unit 371 and the transmission/reception unit 372 function as an authentication code return unit.

[User authentication process flow]
Next, the flow of the user authentication process of this embodiment will be described. Fig. 5 shows the process flow of the user authentication process of this embodiment. This process is started, for example, when an instruction to execute the above-mentioned function requiring authentication is received.

First, the transmitting/receiving unit 274 of the main device 200 sends a communication start request to the authenticated device 300 (step S1101).

When the transmission/reception unit 372 of the authenticated device 300 receives the communication start request (step S12
12, the communication establishment process is performed with the request source device (main device 200) (steps S1203, S1102).

The communication may be established, for example, by a method in which the authentication device 300 performs continuous polling to detect the main device 200 that has entered a predetermined range and establish bidirectional communication.

The authentication device 300 continues to wait until communication is established (step S12
On the other hand, in the case where communication is not established after transmitting the communication start request (step S1103), within a predetermined time, the main device 200 returns to step S1101 and transmits a communication start request again.

On the other hand, if the predetermined time has elapsed, the time is expired (step S1104), and the collation unit 2
In this case, the verification unit 272 sets an authentication failure flag (
Step S1105), and then the process ends.

When two-way communication is established (steps S1204 and S1103), first, the main device 2
The authentication code transmission request generating unit 271 of the authentication code transmission request generating unit 270 generates an authentication code transmission request (step S1
110) and transmits it to the authentication device 300 (step S1111).

On the authenticated device 300 side, when the transmitting/receiving unit 372 receives the authentication code transmission request (step S1205), the authentication code generating unit 371 generates an authentication code (step S12
06) Then, the transmitting/receiving unit 372 transmits the generated authentication code to the main device 200 (step S1207).

When the transceiver unit 274 of the main device 200 receives the authentication code (step S1112
), the verification unit 272 determines its validity (step S1113). Here, as described above, it determines whether it matches the verification authentication code generated in advance. If it matches, the verification unit 27
2 determines that the authentication has been successful, sets an authentication success flag (step S1114), and ends the process.

On the other hand, if they do not match, the collation unit 272 determines that the authentication has failed, and the process proceeds to step S1105.

The authentication failure flag and the authentication success flag are each stored in the temporary storage area 292 .

When the above-mentioned user authentication process is completed and an authentication success flag is set, the unlocking unit 273 unlocks the authentication-required function that has been instructed to be executed, making it available for use. Specifically, the unlocking unit 273 accepts an instruction from the user for the function.

In the user authentication process of this embodiment, the main device 200 and the authentication device 30
Data transmission and reception between the device 220 and the network 100 is performed, for example, by wireless communication using the wireless communication devices 225 and 325.

Next, the authentication code transmission request generation process in step S1110 and step S120
The authentication code generation process will be described in Section 6.

First, the authentication source information 281, the authentication code generation algorithm 282, and the transmission request generation algorithm 283 used at this time will be described.

The authentication source information 281 of this embodiment stores a first value and a second value different from the first value in association with each other. When a first value is specified, the associated and registered second value is returned. At this time, a different first value is specified for each authentication code transmission request. As a result, a different authentication code is returned each time.

6A is an example of the authentication base information 281 of this embodiment. As shown in this figure, the authentication base information 281 includes addresses 281a, which are first values, and codes 281b, which are second values corresponding to each address 281a. In this embodiment, the addresses 281a are specified in an authentication code transmission request. Then, the code 281b registered in association with the specified address 281a is set as the authentication code.

In this embodiment, as shown in Fig. 6(b), the main device 200 transmits one or more addresses 281a as an authentication code transmission request 285. Then, as shown in Fig. 6(c), the authenticated device 300 generates a corresponding code 281b as an authentication code 286.

The transmission request generation algorithm 283 defines a method (rule) for generating information to be transmitted as the authentication code transmission request 285. In this embodiment, a method for determining the address 281a of the authentication source information 281 to be included in the authentication code transmission request 285 is defined. For example, the last digit of the time indicated by the clock when the authentication code transmission request is generated may be used, or a random number generated by a random number generator or the like may be used. The random number generator is provided in the main device 200. Note that, as shown in FIG. 6B, when multiple addresses 281a are to be included in the authentication code transmission request 285,
The order may also be specified.

The transmission request generation algorithm 283 is not limited to the above. It is sufficient that a different address 281a or a set of different addresses 281a is set each time an authentication code transmission request is generated. In addition, the transmission request generation algorithm 283 may be arbitrarily set and changed by the user.

The authentication code transmission request generating unit 271 identifies the address 281a of the authentication source information 281 according to the transmission request generating algorithm 283. Then, the identified address 281a is used to generate the authentication code transmission request 285.
Also output to .

The authentication code generation algorithm 282 defines a method (rule) for generating the authentication code 286. In this embodiment, a process is registered in which a code registered in the authentication source information 281 in association with the address 281a included in the authentication code transmission request 285 is extracted and generated as an authentication code.

The authentication code generating unit 371 extracts a code corresponding to the address 281 a included in the authentication code transmission request 285 from the authentication source information 281 in accordance with the authentication code generating algorithm 282 , and generates the code as an authentication code 286 .

For example, when the authentication source information 281 shown in FIG. 6A is used, the authentication code transmission request 28
6B, the addresses 2, 5, 7, and 9 are specified as the address 281a in the address book 5. In this case, as shown in FIG. 6C, the authentication code 286 including the addresses 8, f, g, and 2 is generated.
is generated and returned.

As described above, the user authentication system 100 of the present embodiment includes the main device 200
and an authentication device 300. The main device 200 includes an authentication code transmission request unit that generates an authentication code transmission request including a predetermined first value and transmits the request to the authentication device 300, and generates a verification authentication code according to the first value included in the authentication code transmission request.
The authentication device 300 includes a matching unit 272 that determines that the authentication is successful when the authentication code transmitted from the authentication device 300 in response to the authentication code transmission request is included in the generated matching authentication code, and an unlocking unit 273 that enables a predetermined function when the matching unit 272 determines that the authentication is successful. The authentication device 300 also generates an authentication code according to a first value included in the authentication code transmission request, and returns the authentication code to the main device 200.

At this time, the main device 200 and the authentication device 300 share authentication original information 281 having a plurality of pairs of a first value and a second value associated with the first value, and an authentication code generation algorithm 282 that generates an authentication code from the authentication original information 281. Then, the authentication code transmission request unit selects a first value from the authentication original information 281 according to a predetermined rule, and the authentication code return unit generates, as an authentication code, the second value stored in the authentication original information 281 in association with the transmitted first value.

In this way, according to this embodiment, a different authentication code is returned every time an authentication code is requested. Therefore, even if the returned authentication code is intercepted or eavesdropped, that authentication code will not be used the next time authentication is performed. Therefore, the auxiliary authentication device (authentication device 30)
0) is used to perform authentication in the mobile terminal (main device 200), thereby achieving high security.

<Modification>
The authentication code generation algorithm 282 may be a function. In this case, the authentication source information 281 may not be provided. For example, the authentication code transmission request generating unit 271 includes a variable of the function in the authentication code transmission request and transmits it. The variable is generated according to the transmission request generating algorithm 283, for example.

In this case, the collation unit 272 uses the value returned by the function in response to the variables as the collation authentication code. The authentication code generation unit 371 also returns the value returned by the function in response to the transmitted variables as the authentication code 286.

The authentication code may be generated using a function such as a token that outputs a different authentication code for each output. In the token, a different authentication code is automatically generated depending on, for example, the timing or number of authentication code transmission requests. In this case, the authentication code generation algorithm is shared between the main device 200 and the authentication device 300.

In addition, each code in the authentication information 281 is not limited to a single alphanumeric character.
It may be a string of numbers, symbols, etc.

By applying these modified examples, the confidentiality of transmitted and received data can be further improved.

<<Second embodiment>>
Next, a second embodiment of the present invention will be described. In this embodiment, the authentication device further takes into account the result of the personal authentication, generates an authentication code, and returns it.

The overall configuration of the user authentication system 100 of this embodiment is basically the same as that of the first embodiment. Hereinafter, this embodiment will be described with a focus on the configuration that is different from the first embodiment.

In this embodiment, when communication is established between the main device 200 and the authentication device 300, the main device 200 transmits an authentication code transmission request 285 to the authentication device 300, as in the first embodiment. When the authentication device 300 receives the authentication code transmission request 285, it performs identity authentication of the user who holds the authentication device 300, and taking into account the success or failure of the authentication, generates and returns an authentication code 286.

[Main device]
The main device 200 of this embodiment has the following hardware configuration and function blocks:
Both are similar to the first embodiment.

However, as described later, the authentication device 300 performs identity authentication. The authentication result is added to the returned authentication code 286.
1 and the authentication code generation algorithm 282 are added with information that allows distinction between success and failure of personal authentication.

The collation unit 272 generates a collation authentication code using the authentication source information 281 and the authentication code generation algorithm 282. However, the collation unit 272 generates the collation authentication code so that an authentication code returned when the personal authentication is successful and an authentication code returned when the personal authentication is unsuccessful can be distinguished. Note that the collation unit 272 may only generate an authentication code returned when the personal authentication is successful.

For example, when the authentication code matches the authentication code for verification returned when the personal authentication fails, the verification unit 272 notifies the operation control unit 275. Then, the operation control unit 275 may be configured to display on the display 241 a message indicating that an unauthorized holder is holding a legitimate authentication device 300.

[Authentication Device]
The authentication device 300 of this embodiment will be described.
Then, as described above, the user authentication is performed. For this purpose, the authentication device 300 of the present embodiment is
It has functions and configurations for personal authentication.

7A is a hardware configuration diagram of the authentication device 300 of this embodiment. As shown in this figure, the authentication device 300 of this embodiment is the same as the authentication device 300 of the first embodiment.
In addition to the above configuration, a biological information sensor 367 is further provided.

The biometric information sensor 367 is a sensor that collects biometric information. For example, the authentication device 3
If the wearable terminal 00 is a wristwatch type wearable terminal, it may be a pulse wave sensor or a heart rate sensor. Alternatively, it may be an imaging device such as a camera that captures fingerprints, veins, irises, etc.
The biometric information sensor 367 functions as a biometric information acquisition unit together with a biometric authentication unit 373 described later.

7B is a functional block diagram of the authentication device 300 of this embodiment. As shown in this figure, the authentication device 300 of this embodiment further includes a biometric authentication unit 373 in addition to the configuration of the first embodiment. That is, a program for realizing the biometric authentication unit 373 is stored in the ROM 311.

In addition, the reference information 380 in the storage 313 includes the valid user (
The biometric information of the user (holder) is further registered as matching biometric information 383. The matching biometric information 383 is acquired in advance when a legitimate holder holds the authentication device 300.
For example, in the case of a wristwatch-type terminal, when the terminal is first worn, the pulse wave or heart rate is acquired for a predetermined time (for example, 10 seconds, 1 minute, etc.) by the biometric information sensor 367. The acquired result is then stored in the storage 313 as biometric information for matching 383.

The biometric authentication unit 373 of this embodiment receives an authentication code transmission request 28 via the transmission/reception unit 372.
When the ID number 361 is received, the biometric information of the holder is acquired at that point. The biometric information is acquired via the biometric information sensor 367. The acquired biometric information is then matched with the matching biometric information 383, and the matching result is output to the authentication code generation unit 371.

The authentication code generating unit 371 generates the authentication code 286 taking into account the result of the comparison.
Specific examples will be given later.

The flow of the user authentication process of this embodiment will be described below. Fig. 8 shows the process flow of the user authentication process of this embodiment. Note that the description of the same parts as in the first embodiment will be omitted.

When the two-way communication is established (steps S1204 and S1103), the authentication code transmission request generating unit 271 of the main device 200 generates an authentication code transmission request 285 (step S1
110) and transmits it to the authentication device 300 (step S1111).

On the authentication device 300 side, when the transmission/reception unit 372 receives the authentication code transmission request 285 (step S1205), the biometric authentication unit 373 performs identity authentication (step S2201).
Here, biometric information is collected for a predetermined period of time. The biometric information is collected by the biometric information sensor 367. The acquired biometric information is then compared with the biometric information for verification 383.
The comparison result is output to the authentication code generation unit 371 .

The authentication code generating unit 371 generates an authentication code (step S2202) and transmits the authentication code to the transmitting/receiving unit 3
72 transmits the generated authentication code to the main device 200 (step S1207).
A specific example of the authentication code generated here will be described later.

When the transceiver unit 274 of the main device 200 receives the authentication code (step S1112
), the verification unit 272 determines its validity (step S1113). In this embodiment, too, it determines whether it matches the verification authentication code generated in advance. If it matches, the verification unit 272
determines that the authentication has been successful, sets the authentication success flag (step S1114), and ends the process.

On the other hand, if they do not match, the collation unit 272 determines that the authentication has failed, and the process proceeds to step S1105.

When the above-mentioned user authentication process is completed and the authentication success flag is set, the unlocking unit 273 unlocks the authentication-required function that has been instructed to be executed, and makes it available. Specifically, the unlocking unit 273 accepts an instruction from the user for the function.

Next, a specific example of an authentication code generated in this embodiment will be described. First, a specific example of the authentication base information 281 prepared in this embodiment will be described. The authentication base information 281 of this embodiment stores, in association with a first value, a second value to be returned when personal authentication is successful, and a third value to be returned when personal authentication is unsuccessful.

9A shows an example of the authentication base information 281 of this embodiment. As shown in this figure, the authentication base information 281 includes addresses 281a which are first values, code 1 (281b) which are second values corresponding to each address 281a, and code 2 (281c) which is a third value.
The second value is a value that is returned if the personal authentication is successful, and the third value is a value that is returned if the personal authentication is unsuccessful.

In this embodiment, the information transmitted by the main device 200 as the authentication code transmission request 285 is one or more addresses 281a. Then, the authentication device 300 generates and returns a corresponding code 1 (281b) or code 2 (281c) as the authentication code 286 depending on whether the user authentication is successful.

In this embodiment, the matching unit 272 of the main device 200 may generate, as a matching authentication code, an authentication code using the code 1 (281b) returned when the personal authentication is successful.

For example, when the authentication source information 281 shown in FIG. 9A is used, the authentication code transmission request 28
In the example shown in Fig. 9(b) , assume that 2, 5, 7, and 9 are specified as address 281a in address 281 of 5. In this case, if biometric authentication is successful, an authentication code 286 including 8, f, g, and 2 is generated and returned as shown in Fig. 9(c) . On the other hand, if biometric authentication is unsuccessful, an authentication code 286 including t, 4, 2, and g is generated and returned as shown in Fig. 9(d) .

As described above, in addition to the configuration of the first embodiment, this embodiment has a configuration in which the authentication device 300 performs biometric authentication of the holder, generates an authentication code including the success or failure of the biometric authentication, and returns the code.

Therefore, according to the present embodiment, the main device 200 can know whether the user authentication in the authentication device 300 has been successful. That is, the main device 200 can determine not only whether the authentication device 300 is valid, but also whether the authentication device 300 is held by a valid user, based on the returned authentication code.

Therefore, according to this embodiment, even if the authentication device 300 is legitimate, if the holder is not the legitimate holder, it is possible to ascertain circumstances such as loss or theft of the authentication device 300. Since such a determination can be made, security can be ensured even if the authentication device 300 is lost or stolen.

As described above, according to this embodiment, it is possible to provide a highly secure user authentication system while maintaining high security during transmission and reception.

As with the first embodiment, various modifications are possible with this embodiment as well.

<Modification>
In addition, when the user authentication is successful in the authentication device 300, the history of the successful authentication is stored in the authentication device 30.
In this embodiment, as described above, the authentication device 300 performs user authentication every time it receives an authentication code transmission request. At this time, the success or failure of the authentication is stored in the storage 313 in association with the time when the authentication was performed.

The authentication code 286 may be returned in a manner that makes it possible to distinguish between a case where personal authentication has been successful a predetermined number of times in succession and a case where personal authentication has only been successful intermittently.

9A, for example, a fourth value (Code 3 (281d)) is stored in association with the first value as the authentication source information 281. If the personal authentication is continuously successful, the second value is returned, and if the personal authentication is only intermittently successful, the fourth value is returned.

This allows the main device 200 to know whether the authentication device 300 is still attached to the body of the original user, or has been attached to the body even once. If the situation is suspicious, such as frequent failures in personal authentication, security may be strengthened by, for example, further requesting the input of a PIN code.

<<Third embodiment>>
Next, a third embodiment of the present invention will be described. In this embodiment, both the main device 200 and the authentication device 300 record the behavior history of the holder. If the behavior histories of the two match, it is deemed that the user authentication has been successful.

A user authentication system 100 of this embodiment basically has the same configuration as that of the first embodiment. Hereinafter, this embodiment will be described with a focus on the configuration that is different from the first embodiment.

[Main device]
The hardware configuration of the main device 200 of this embodiment is basically the same as that of the first embodiment, except for the functions realized by the main device 200. Fig. 10 shows functional blocks of the main device 200 of this embodiment.

As shown in the figure, the main device 200 of this embodiment includes, in addition to the configuration of the first embodiment, a location information acquisition unit 277. Specifically, a program that realizes the location information acquisition unit 277 is stored in the ROM 211, and the CPU 201 realizes the function of the location information acquisition unit 277 by loading this program into the RAM 212 and executing it.

The location information acquisition unit 277 acquires current location information via, for example, the GPS receiver 261. The acquired location information is stored in the storage 213 as the behavior history 28 in association with the time of acquisition.
4. In this embodiment, this behavior history 284 is used as the original information for authentication.

The transmission request generation algorithm 283 of this embodiment is defined to specify, for example, a time period (period) of the behavior history 284 to be returned. The authentication code generation algorithm 282 is defined to extract location information for the specified time period (period) from the behavior history 284.

Furthermore, the matching unit 272 of the main device extracts the behavior history (location information) for the period specified in the authentication code transmission request 285 from the behavior history 284, and generates an authentication code for matching.

[Authentication Device]
Next, the authentication device 300 of this embodiment will be described. Fig. 11A is a hardware configuration diagram of the authentication device 300 of this embodiment. As shown in this figure, the authentication device 300 of this embodiment includes a GPS receiver 361 in addition to the configuration of the first embodiment.

11B is a functional block diagram of the authentication device 300 of this embodiment. As shown in this figure, the authentication device 300 of this embodiment includes a location information acquisition unit 374 in addition to the configuration of the first embodiment. Furthermore, the storage 313 further includes an action history 384 that registers the acquired location information in association with time.

When the authentication device 300 is powered on, the location information acquisition unit 374 of this embodiment calculates its own location information at a predetermined time interval according to the GPS signal received by the GPS receiver 361. Then, the calculation result is stored in the storage 313 as the behavior history 384 in association with the time.

The authentication code generation unit 371 of this embodiment extracts the behavior history (location information) for the period specified in the authentication code transmission request 285 from the behavior history 384, and generates the authentication code.

In this embodiment, the main device 200 and the authentication device 300 exchange position information as follows:
However, if this is difficult, the authentication code generation unit 371 determines the acquisition times closest to the start and end points of the period specified in the authentication code transmission request 285, extracts position information between the two acquisition times, and sets it as the authentication code 286.

Furthermore, the matching unit 272 may be configured to set a predetermined tolerance range for the matching and determine that there is a match if the match is within the tolerance range.

The flow of the user authentication process of this embodiment will be described below. Fig. 12 shows the process flow of the user authentication process of this embodiment. Note that the description of the same parts as in the first embodiment will be omitted.

When the two-way communication is established (steps S1204 and S1103), the authentication code transmission request generating unit 271 of the main device 200 generates an action history transmission request as the authentication code transmission request 285 (step S3110) and transmits it to the authenticated device 300 (step S311).
1) Here, a period to be extracted from the stored behavior history 284 is specified.

When the transmission/reception unit 372 of the authentication device 300 receives the action history transmission request (step S
3201), the authentication code generation unit 371 of the authentication device 300 extracts the behavior history (location information) for the specified period from the behavior history 384 held in the storage 313 (step S3203), and generates the authentication code 286. Then, the transmission/reception unit 372 transmits the generated authentication code 286 (behavior history) to the main device 200 (step S3204).

When the transceiver unit 274 of the main device 200 receives the authentication code (step S3102
), the collation unit 272 determines its validity (step S3103). Here, it determines whether it matches a previously generated authentication code for collation. In this embodiment, depending on the timing of collecting the location information, the authentication code transmitted and the authentication code for collation may not completely match. Therefore, as described above, a predetermined tolerance may be set to determine whether they match.

If there is a match, the collation unit 272 determines that the authentication has been successful, sets an authentication success flag (step S1114), and ends the process.

On the other hand, if they do not match, the collation unit 272 determines that the authentication has failed, and the process proceeds to step S1105.

Here, examples of the behavioral histories 284 and 384 of this embodiment are shown.
) is a representative example of the behavior history 284. As shown in this figure,
In the case of No. 4, latitude and longitude information is registered as position information 284b in association with time 284a.
FIG. 13A shows an example in which location information 284b is registered, for example, every minute.

For example, when the request for transmitting the behavior history is for location information from 8:00 to 10:00 on November 1, 2017, the authentication code generating unit 371 stores the location information corresponding to this period in the behavior history 38.
4 to obtain the authentication code 286. Note that, in consideration of accuracy, it is not necessary to use all the digits of the location information used as the authentication code.

According to this embodiment, the position information is accumulated as a behavior history in both the main device 200 and the authentication device 300. Then, the behavior history for a predetermined period is received from the authentication device 300 as an authentication code.

In this embodiment, the authentication code sent is different for each authentication, so security during transmission and reception of the authentication code is high, as in the above embodiments. Also, in this embodiment, there is no need to share authentication source information in advance between the main device 200 and the authentication device 300. For this reason,
Since there is no need to transmit and receive data for sharing this authentication source information, a more secure user authentication system can be obtained.

As with the first embodiment, various modifications are possible with this embodiment as well.

<Modification>
In the present embodiment, both the main device 200 and the authentication device 300 constantly acquire location information and record it as a behavior history, but the present invention is not limited to this method. For example,
The execution of the authentication process may be controlled depending on whether the location where the specific process is performed is within a normal range of movement or deviates from the normal range of movement.

For example, the main device 200 identifies the movement range from the collected position information based on the results of successful authentication processing associated with the identification processing.

13B, for example, the collation unit 272 stores the number of times the authentication has been determined to be successful (number of successful authentications) 284d each time the collation unit 272 determines that the authentication has been successful, in association with location information 284c at the time of the authentication. The location information 284c used is the information acquired by the location information acquisition unit 374 and stored in the behavior history 284. That is, the location information 284c used is information specified by latitude and longitude.

Then, the collation unit 272 determines the location where the number of authentication successes 284d is equal to or greater than a predetermined number as an authentication history location. Also, the range specified by the position information 284c corresponding to this authentication history location is determined as a normal behavior range 284e. Note that in FIG. 13B, for example, the location where the number of authentication successes 284d is 10 or more is determined as an authentication history location. Then, information on this normal behavior range 284e, i.e., the position information 284c of the normal behavior range 284e and the number of authentication successes 284d, are stored in the storage 213 instead of the behavior history 284. Note that, here, different locations within an allowable range are considered to be the same location.

The collation unit 272 determines whether the location of the main device 200 at the time of authentication is within the normal movement range 284e. If it is within the normal movement range 284e and the specific process is not an important process, authentication by the authentication device 300 is omitted, and if it is outside the normal movement range 284e or the specific process is an important process, authentication by the authentication device 300 is performed.

Here, the important specific process means, for example, a payment process in which the specific process is a payment of a certain amount or more.

In addition, the main device 200 stores the action history 284 in the storage 200 in association with the process.
13.

Furthermore, the normal movement range 284e is not limited to the range specified by the authentication history position. A range within a predetermined distance from the authentication history position may be the normal movement range 284e.

The flow of the behavior history collection process and authentication process of this modified example is shown in FIG. 14. As shown in this figure, the location information acquisition unit 277 determines whether the process performed by the operation control unit 275 is a specific process (step S3301). If it is not a specific process, the process is executed (step S33
09) and finish.

On the other hand, if it is a specific process, the operation control unit 275 acquires the position information (step S3302). Then, the operation control unit 275 further determines whether the specific process is an important process or not (step S3303).
If the process is important, an authentication process is performed (step S3305). If the authentication is successful (step S3306), the collation unit 272 stores the acquired location information as the behavior history 284 in association with the specified process and the acquisition time (step S3307), and executes the specified process (step S3309). At this time, the same behavior history 284 is also stored in the authentication device 300.
84 (normal activity range 284e) may be stored.

On the other hand, if the authentication is unsuccessful (step S3306), the operation control unit 275 displays an error message (step S3308) and ends the process.

In step S3303, when it is determined that the specific process is not an important process (step S3303), the collation unit 272 checks whether the position of the main device 200 is within the normal movement range 284
It is determined whether the range of movement is normal 284e (step S3304). If it is determined that the range of movement is not normal 284e, the process proceeds to step S3305, where authentication processing is performed. On the other hand, if it is determined that the range of movement is normal 284e, the process is executed (step S3309), and the process ends.

For example, the specific process may be a payment process at a store. By configuring in this way, the location information of the store that the user frequents is registered in advance. When a payment process is performed at a store other than the registered store, the lock is not automatically released. Therefore, in addition to the security of data transmission and reception, high security can be obtained with respect to the execution of the process.

The action history 284 for each process may be registered in association with a time period. The third embodiment may be combined with the first or second embodiment.

In this modification, the authentication device 300 stores the authentication result history (
The authentication code transmission request may store the same data as the authentication record history (284c, 284d) and request transmission of the past authentication record history (284c, 284d) in the authentication code transmission request. In this case, the collation unit 272 determines the legitimacy of the holder of the authentication device 300 based on whether the authentication record history (284c, 284d) of the authentication device 300 returned in response to the request is the same as the authentication record history (284c, 284d) recorded in the main device 200.

<<Fourth embodiment>>
Next, a fourth embodiment of the present invention will be described. Prior to the user authentication process described in each of the above embodiments, it is necessary to perform an initial setting in which information required for the user authentication process, such as authentication source information, is transmitted from the main device 200 to the authentication device 300. In this embodiment, security during this initial setting is improved.

In the first, second, and third embodiments, as an initial setting, the authentication source information 281 and/or the authentication code generation algorithm 282 are set in the main device 200 and transmitted to the authentication device 300. Furthermore, whenever there is a change in these, they are transmitted from the main device 200 to the authentication device 300. That is, whenever the authentication source information 281 and/or the authentication code generation algorithm 282 are newly set or updated, an initial setting is performed to be shared between the main device 200 and the authentication device 300.

In each of the above embodiments, the information transmitted from the main device 200 to the authentication device 300 during initial setup is different. Here, the first embodiment will be used as the base for the explanation, with a focus on configurations different from the first embodiment.

The hardware configurations of the main device 200 and the authentication device 300 of this embodiment are basically the same as those of the first embodiment.

[Main device]
15A shows functional blocks of the main device 200 of this embodiment. As shown in this figure, the main device 200 of this embodiment includes an initial setting unit 278 in addition to the configuration of the first embodiment.

The initial setting unit 278 transmits the authentication source information 281 and the authentication code generation algorithm 282 set in the main device 200 to the authentication device 300 at the time of initial setting. When transmitting, the initial setting unit 278 selects a communication means with a short reach or wired communication, rather than a transmission means normally used for transmitting and receiving data to and from the authentication device 300.

The authentication source information 281 and the authentication code generation algorithm 282 are registered in advance in the storage 213 by the user of the main device 200. When the initial setting unit 278 of this embodiment receives an initial setting instruction from the user, it selects a communication means for initial setting and performs initial setting processing.

As the communication means, the communication means with the highest security is selected among the communication means available for communication between the main device 200 and the authentication device 300. For example, wired communication using the wired communication device 223 is selected. In addition, in the case of wireless communication, the wireless communication with the shortest range, such as wireless communication using the close-proximity wireless communication device 224, is selected.

The priority order of these selections is, for example, preset and stored in the storage 213 or the like.
Alternatively, the communication device to be used may be specified by the user each time.

In addition, when wired communication is selected, the initial setting unit 278 prompts the user to enter the
A message prompting a wired connection between the authentication device 300 and the authentication terminal 200 may be displayed on the display 241.

In addition, when the authentication device 300 side includes a USB I/F, the USB
The SB I/F and the USB I/F of the authentication device 300 may be connected by a USB cable to transfer data.

15B is a functional block diagram of an authentication device 300 according to this embodiment. As shown in this figure, in addition to the configuration of the first embodiment, an initial setting unit 375 is provided.

The initial setting unit 375 receives the authentication source information 281 and the authentication code generation algorithm 282,
The main device 200 performs the process of receiving the data.
The communication means corresponding to the communication means set by the main device 200 is set as the receiving means, and information from the main device 200 is received.

16A is a flow diagram for explaining the flow of processing during initial setting in this embodiment. It is assumed that at the start of this processing, the authentication source information 281 and the authentication code generation algorithm 282 are registered in the main device 200. This processing is started when an instruction to start initial setting is received from the holder of the main device 200.

First, the initial setting unit 278 of the main device 200 selects a communication means (step S4
101). Then, an initial setting request for requesting establishment of communication by the selected communication means is transmitted to the authenticated device 300 (step S4102).

When the authentication device 300 receives a communication establishment request as an initial setting request (step S
The initial setting unit 375 performs a process to establish communication by the requested communication means (step S4201), and establishes communication by the communication means (step S4202).

When the communication is established, the initial setting unit 278 transmits the authentication source information 281 and the authentication code generation algorithm 282 from the main device 200 to the authentication device 300 by the communication means.
Then, the initial setting is performed to transmit the message to the server (step S4103).

The initial setting unit 375 performs initial setting to store the transmitted authentication source information 281 and authentication code generation algorithm 282 in the storage 313 (step S4203). Then, the initial setting unit 375 notifies the initial setting unit 278 that the storage has been completed, and ends the initial setting.

When the initial settings are completed, the initial setting unit 278 and the initial setting unit 375 respectively return the communication means of their own devices to the normally used communication means (steps S4104, S4204), and terminate the process.

As shown in FIG. 16(b), the process until communication is established, such as sending an initial setting request, may be performed using normal communication means (steps S4301, S4401), and after communication is established, the communication means may be selected (steps S4101, S4202).

As described above, in this embodiment, at the time of initial setup, i.e., when the authentication source information 281 from which the authentication code is generated is shared between the main device 200 and the authentication device 300, data is transmitted and received using a communication means with a lower possibility of leakage. This makes it possible to realize a more secure user authentication system.

<Modification>
In this embodiment, the wireless communication device 22 used in the user authentication process in each of the above embodiments is
5. A communication means other than the above is selected to enhance security, but is not limited to this.

For example, if the wireless communication device 225 has a variable output, the output may be reduced during the initial process compared to normal times such as during user authentication processing.

17 shows an example of the configuration of a variable output wireless communication device 225. The wireless communication device 225 includes a signal processor 225a, a variable resistor 225b, an output device 225c, and an antenna 225d.

For example, during the initial setting, the initial setting unit 278 issues an instruction to the wireless communication device 225 to reduce the output. For example, the resistance value of the variable resistor 225b is increased to suppress the output. Furthermore, when the initial setting is completed, the initial setting unit 278 issues an instruction to the wireless communication device 225 to return the resistance value of the variable resistor 225b to the original value.

In addition, according to this embodiment, the authentication source information 281 and the authentication code generation algorithm 28
After sharing ID 2, user authentication may be performed using either the method of the first embodiment or the method of the second embodiment.

In addition, during the initial processing, the authentication source information 281 and the authentication code generation algorithm 282 may be encrypted using a public key and transmitted from the main device 200 to the authentication device 300 .

<Modification>
In addition, in each of the above-described embodiments, except for the specific process of the modified example of the third embodiment, there is no particular limitation on the function of authentication using the authentication device 300. For example, the user authentication process of each of the above-described embodiments may be used for authentication when unlocking the screen of the main device 200, or may be used for authentication when executing a specific application that has been determined in advance.

<Modification>
Also, for example, the main device 200 may be configured to include a plurality of user authentication means and use them in combination. An example of the process flow in this case is shown in FIG. 18. Here, an example is described in which the screen is unlocked in a first authentication process, authentication for a specific process is performed in a second authentication process, and if the second authentication process fails, a third authentication process is performed as a backup. The screen lock state refers to a state in which the main device 200 is in a standby state and does not accept any operations other than authentication operations.

First, the operation control unit 275 performs a first authentication process (step S5101), and if the authentication is successful (step S5102), the unlocking unit 273 unlocks the screen of the main device 200 (step S5103). If the authentication is unsuccessful, the process ends or the process returns to step S5101 to perform authentication again.

When the screen lock is released and an operation instruction is received from the user via the display 241 (step S5104), the operation control unit 275 determines whether the instruction is a specific process determined in advance (step S5105). If the instruction is a specific process, the operation control unit 275 performs a second authentication process (step S5106). On the other hand, if the instruction is not a specific process, the operation control unit 275 executes the process as is (step S5108) and ends the process.

If the second authentication is successful (step S5107), the process proceeds to step S5108, where processing is executed.

On the other hand, if the second authentication fails, the operation control unit 275 displays an error message on the display 241 and also displays a message prompting the user to perform the third authentication (step S5111).
8 and execute the process. On the other hand, if the third authentication is not successful (
Step S5112: No), the operation control unit 275 displays an error (Step S5
113) and the process ends.

In this modification, the first authentication, the second authentication, and the third authentication each use a different authentication means. In this case, user authentication using the authentication device 300 may be used for any of the first authentication, the second authentication, and the third authentication.

For example, the first authentication may be authentication that directly uses biometric information such as a fingerprint, veins, or iris, the second authentication may be user authentication that uses the authentication device 300 of each of the above embodiments, and the third authentication may be authentication means such as input of a PIN code (password).

For example, in the case of the modified example of the third embodiment described in Fig. 14, if a user attempts to make a payment at a store other than his/her regular store, authentication fails and the lock is not released. In such a case, as shown in this figure, if a third authentication method is prepared to be used when authentication fails with the user authentication means of this embodiment, payment can be made at a new store as long as the password is known. In other words, convenience and security can be well balanced.

Moreover, the user may be able to set which authentication means to use for each of the first authentication, the second authentication, and the third authentication.

Furthermore, if the main device 200 is capable of using multiple authentication means, the main device 200 may be configured to execute multiple authentications in a specific process. The process may be executed only if all of the executed authentications are successful. The process may be executed only if at least one of the executed authentications is successful.

Moreover, a specific process that is executed only if all authentications using multiple authentication means are successful is, for example, a payment process. The number of authentications used may be changed according to the payment amount of the payment process. That is, the number of authentication means used increases as the payment amount increases.

<Modification>
Furthermore, the communication establishment process may be periodically attempted between the main device 200 and the authentication device 300. As shown in FIG. 19, the operation control unit 275 periodically performs step S110.
Then, if the communication establishment fails, not only is an authentication failure flag set, but the time when the communication establishment failed is also recorded (step S5
201; non-established time accumulation).

Even if communication is established in step S1103, the collation unit 272 checks the past communication non-established period before generating the authentication code transmission request (step S5202
At this time, for example, it is determined whether or not there is a period during which communication is not established continuously for a predetermined period.

If there is a continuous non-communication established period longer than the predetermined period, even if communication is established, the authentication is deemed to have failed, and the process proceeds to step S1105. On the other hand, if the non-communication established period is equal to or shorter than the predetermined time in step S5202, the user authentication process of each of the above embodiments is performed (step S5203).

<Modification>
In each of the above embodiments, the authentication device 300 is used as the auxiliary authentication device of the main device 200.
For example, the authentication device 300 also uses the main device 2.
00. The main device 200 and the authentication device 300 may be configured to perform mutual authentication between them.

For example, in the case where the two devices are a smartphone and a wearable terminal, when the smartphone executes a specific process, the smartphone functions as the main device 200, and the wearable terminal functions as the authentication device 300. In addition, when the wearable terminal executes a specific process, the wearable terminal functions as the main device 200, and the smartphone functions as the authentication device 300.

<Modification>
In the above embodiments, one authentication device 3 is connected to one main device 200.
00 is described as an example, but the present invention is not limited to this.
00, multiple authentication devices 300 may be provided. In this case, each of the multiple authentication devices 300 has the authentication source information 281 and/or the authentication code generation algorithm 282 provided in the main device 200. Then, authentication may be considered successful only when the authentication codes from all authentication devices 300 match. On the other hand, authentication may be considered successful when the authentication codes from at least one authentication device 300 match.

The present invention is not limited to the above-described embodiment, but includes various modifications.
For example, the above-described embodiments are provided to clearly explain the present invention, and are not necessarily limited to those including all of the configurations described. Also, it is possible to replace a part of the configuration of one embodiment with the configuration of another embodiment, and it is also possible to add the configuration of another embodiment to the configuration of one embodiment. Also, it is possible to add, delete, or replace a part of the configuration of each embodiment with another configuration.

In addition, the above-mentioned configurations, functions, processing units, processing means, etc. may be realized in part or in whole by hardware, for example, by designing them as integrated circuits. In addition, the above-mentioned configurations, functions, etc. may be realized in software by a processor interpreting and executing a program that realizes each function. Information such as a program, table, file, etc. that realizes each function can be stored in a memory, a recording device such as a hard disk or SSD (Solid State Drive), or a recording medium such as an IC card, SD card, or DVD.

In addition, the control lines and information lines shown are those that are considered necessary for the explanation, and not all control lines and information lines in the product are necessarily shown. In reality, it can be considered that almost all components are connected to each other.

100: User authentication system,
200: main device, 201: CPU, 202: system bus, 210: storage device,
211: ROM, 212: RAM, 213: storage, 220: communication processor, 221:
LAN communication device, 222: telephone network communication device, 223: wired communication device, 224: close-proximity wireless communication device,
225: wireless communication device, 225a: signal processor, 225b: variable resistor, 225c: output device,
225d: antenna, 227: expansion I/F, 230: operation unit, 240: video processor, 241: display, 242: image signal processor, 243: camera, 250: audio processor, 251: speaker, 252: audio signal processor, 253: microphone,
260: sensor, 261: GPS receiver, 262: gyro sensor, 263: geomagnetic sensor, 264: acceleration sensor, 265: illuminance sensor, 266: proximity sensor, 267: biometric information sensor,
271: authentication code transmission request generating unit, 272: matching unit, 273: lock release unit, 274
: Transmitting and receiving unit, 275: Operation control unit, 277: Position information acquiring unit, 278: Initial setting unit, 28
0: Reference information, 281: Authentication source information, 281a: Address, 281b: Code (1), 28
1c: Code 2, 281d: Code 3, 282: Authentication code generation algorithm, 283:
Transmission request generation algorithm, 284: behavior history, 284a: time, 284b: location information,
284c: location information, 284d: number of successful authentications, 285: authentication code transmission request, 286:
Authentication code, 291: execution program, 292: temporary storage area,
300: authentication device, 301: CPU, 302: system bus, 310: storage device,
311: ROM, 312: RAM, 313: storage, 320: communication processor, 323:
Wired communication device, 324: Near field communication device, 325: Wireless communication device, 361: GPS receiver, 3
67: Biometric information sensor, 371: authentication code generation unit, 372: transmission/reception unit, 373: biometric authentication unit, 374: location information acquisition unit, 375: initial setting unit, 380: reference information, 383: biometric information for matching, 384: behavior history, 391: execution program, 392: temporary storage area

Claims (23)

A user authentication system for authenticating a user of a main device, the system comprising: a main device; and an authentication device that communicates with the main device, the system comprising:
The main body device is
storing authentication source information having a plurality of pairs of a first value selected for each transmission and a second value associated with the first value;
selecting the first value from the authentication source information based on a predetermined rule;
the second value stored in the authentication source information in association with the selected first value is set as a verification authentication code;
generating a request for an authentication code including the selected first value;
Sending the authentication code transmission request to the authentication device;
The authentication device includes:
storing biometric information of a holder of the authentication device, which information has been acquired in advance before authentication, as biometric information for matching;
receiving the authentication code transmission request transmitted from the main device;
storing the authentication source information;
In response to the authentication code transmission request, the biometric information is acquired and biometric authentication is performed using the matching biometric information;
If the biometric authentication is successful, the second value stored in the authentication source information in association with the first value is generated as an authentication code;
Transmitting the authentication code to the main device;
The main body device is
If the authentication code transmitted from the authentication device includes the verification authentication code, the authentication is determined to be successful;
If the authentication is successful, a predetermined function is enabled.
If it is determined that the authentication is not successful, the authentication device transmits the authentication code transmission request every time a predetermined time elapses. 2. The user authentication system according to claim 1,
The user authentication system, wherein the authentication device is a wearable terminal. 2. The user authentication system according to claim 1,
The main body device is
A variable output wireless communication device;
An initial setting unit,
A user authentication system characterized in that the initial setting unit transmits the authentication source information to the authentication device via the wireless communication device before transmitting the authentication code transmission request to the authentication device, and when transmitting the authentication source information, reduces the output of the wireless communication device below the output when transmitting the authentication code transmission request. 2. The user authentication system according to claim 1,
The user authentication system according to claim 1, wherein the predetermined function is a payment function. 2. The user authentication system according to claim 1,
The main body device is
a first authentication unit that performs a first authentication different from authentication using the authentication device;
A reception unit that receives an operation instruction,
the main body device further enables acceptance of the operation instruction via the acceptance unit when the authentication by the first authentication unit is successful;
generating the authentication code transmission request when the operation instruction for executing the predetermined function is received via the reception unit. 2. The user authentication system according to claim 1,
The main body device is
a second authentication unit that performs a second authentication different from the authentication using the authentication device;
wherein the second authentication unit executes the second authentication when it is determined that the authentication has not been successful. 2. The user authentication system according to claim 1,
The main device includes a transmission/reception unit that establishes communication with the authentication device;
a main body storage unit that accumulates a non-establishment period during which the transmission/reception unit was unable to establish the communication,
The main device does not generate the authentication code transmission request when the accumulated non-establishment period exceeds a predetermined period. 2. The user authentication system according to claim 1,
a third value different from the second value is further associated with each of the first values of the authentication source information,
a user authentication device that, when the biometric authentication fails, sets the third value stored in the authentication source information in correspondence with the first value as the authentication code. A mobile terminal,
an authentication code transmission request unit that generates an authentication code transmission request including a first value selected for each transmission and transmits the authentication code transmission request to an external device;
a verification unit that determines that the authentication is successful when the authentication code transmitted from the external device in response to the authentication code transmission request is included in a verification authentication code generated in accordance with the first value;
a release unit that enables a predetermined function when the verification unit determines that the authentication is successful;
an authentication code generating unit that, when receiving the authentication code transmission request from the external device, generates the authentication code according to the first value included in the authentication code transmission request and returns the authentication code to the external device;
a storage unit configured to store authentication source information having a plurality of pairs of the first value and a second value associated with the first value;
a biometric information acquisition unit for acquiring biometric information of a person who holds the portable terminal;
A biometric authentication unit,
the authentication code transmission request unit selects the first value from the authentication source information in accordance with a predetermined rule;
the verification unit sets the second value stored in the authentication source information in association with the first value selected by the authentication code transmission request unit as the verification authentication code,
the authentication code generation unit generates, as the authentication code, the second value stored in the authentication source information in association with the first value;
The storage unit further stores the biometric information acquired in advance before authentication as biometric information for matching,
the biometric authentication unit acquires the biometric information in response to the authentication code transmission request, performs biometric authentication using the biometric information for matching, and outputs a result to the authentication code generation unit;
the authentication code generation unit, when the biometric authentication is successful, sets the second value stored in the authentication source information in association with the first value as the authentication code;
The release unit is
If the verification unit determines that the authentication is successful, a predetermined function is enabled;
If the verification unit does not determine that the authentication is successful, the portable terminal transmits the authentication code transmission request to the external device every time a predetermined time elapses. The mobile terminal according to claim 9, wherein the mobile terminal is a smartphone or a wearable terminal. 10. The mobile terminal according to claim 9,
A variable output wireless communication device;
An initial setting unit,
The mobile terminal is characterized in that the initial setting unit transmits the authentication original information to the external device via the wireless communication device before transmitting the authentication code transmission request to the external device, and when transmitting the authentication original information, reduces the output of the wireless communication device below the output when transmitting the authentication code transmission request. 10. The mobile terminal according to claim 9,
The mobile terminal, wherein the predetermined function is a payment function. 10. The mobile terminal according to claim 9,
a first authentication unit that performs a first authentication different from the authentication using the external device;
A reception unit that receives an operation instruction,
When the authentication by the first authentication unit is successful, the operation instruction can be accepted via the acceptance unit;
the mobile terminal generates the authentication code transmission request when the operation instruction for executing the predetermined function is accepted via the accepting unit. 10. The mobile terminal according to claim 9,
a second authentication unit that performs a second authentication different from the authentication using the external device;
The mobile terminal, wherein the second authentication unit executes the second authentication when it is determined that the authentication is not successful. 10. The mobile terminal according to claim 9,
A transceiver unit for establishing communication with the external device;
a main body storage unit that accumulates a non-establishment period during which the transmission/reception unit was unable to establish the communication,
The mobile terminal, wherein the authentication code transmission request unit does not generate the authentication code transmission request when the accumulated non-establishment period exceeds a predetermined period. 10. The mobile terminal according to claim 9,
a third value different from the second value is further associated with each of the first values of the authentication source information,
the authentication code generation unit sets the third value stored in the authentication source information in association with the first value as the authentication code when the biometric authentication fails. A mobile terminal,
an authentication code transmission request unit that generates an authentication code transmission request including a first value selected for each transmission and transmits the authentication code transmission request to an external device;
a verification unit that determines that the authentication is successful when the authentication code transmitted from the external device in response to the authentication code transmission request is included in a verification authentication code generated in accordance with the first value;
a release unit that enables a predetermined function when the verification unit determines that the authentication is successful;
an authentication code generating unit that, when receiving the authentication code transmission request from the external device, generates the authentication code according to the first value included in the authentication code transmission request and returns the authentication code to the external device;
a storage unit configured to store authentication source information having a plurality of pairs of the first value and a second value associated with the first value,
the authentication code transmission request unit selects the first value from the authentication source information in accordance with a predetermined rule;
the verification unit sets the second value stored in the authentication source information in association with the first value selected by the authentication code transmission request unit as the verification authentication code,
the authentication code generation unit generates, as the authentication code , the second value stored in the authentication source information in association with the first value;
The release unit is
If the verification unit determines that the authentication is successful, a predetermined function is enabled;
If the verification unit does not determine that the authentication is successful, the portable terminal transmits the authentication code transmission request to the external device every time a predetermined time elapses. 18. The mobile terminal according to claim 17,
The portable terminal, wherein the external device is a smartphone or a wearable terminal. 18. The mobile terminal according to claim 17,
The mobile terminal includes:
A variable output wireless communication device;
An initial setting unit,
The mobile terminal is characterized in that the initial setting unit transmits the authentication original information to the external device via the wireless communication device before transmitting the authentication code transmission request to the external device, and when transmitting the authentication original information, reduces the output of the wireless communication device below the output when transmitting the authentication code transmission request. 18. The mobile terminal according to claim 17,
The mobile terminal, wherein the predetermined function is a payment function. 18. The mobile terminal according to claim 17,
The mobile terminal includes:
a first authentication unit that performs a first authentication different from the authentication using the external device;
A reception unit that receives an operation instruction,
the mobile terminal further enables acceptance of the operation instruction via the acceptance unit when the authentication by the first authentication unit is successful;
the mobile terminal generates the authentication code transmission request when the operation instruction for executing the function is received via the reception unit. 18. The mobile terminal according to claim 17,
The mobile terminal includes:
a second authentication unit that performs a second authentication different from the authentication using the external device;
The mobile terminal, wherein the second authentication unit executes the second authentication when the authentication is not determined to be successful. 18. The mobile terminal according to claim 17,
The portable terminal includes a transmitting/receiving unit that establishes communication with the external device;
A storage unit,
The storage unit accumulates a non-establishment period, which is a period during which the transmission/reception unit was unable to establish the communication;
The mobile terminal, wherein the authentication code transmission request unit does not generate the authentication code transmission request when the accumulated non-establishment period exceeds a predetermined period.

Images