JP2017130011A - Organism authentication method and biometric authentication apparatus - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide an organism authentication method of a terminal apparatus capable of reducing influences of changes such as body conditions of a user in an organism authentication of the user.SOLUTION: The organism authentication method includes the steps of: acquiring a piece of first biological information of a user with a first unit; receiving a piece of second biological information acquired from the user with a second unit which is connected to the first unit in a mode collatable with the first biological information; and comparing the first biological information and the second biological information.SELECTED DRAWING: Figure 7B

Description

  The present invention relates to a biometric authentication method and a biometric authentication device.

  In recent years, a terminal called a wearable terminal, which is supposed to be worn on the body and used, has become widespread. Various types of wearable devices have been developed, such as a watch type, glasses type, a neck strap type that hangs around the neck, and a type that is attached directly to the body.

  In order to prevent unauthorized operation, wearable devices are locked so that they will not accept operations if there is no operation from the user for a specified period of time, and will be authenticated and locked when the user resumes use. There is something to cancel. As an authentication method, for example, an authentication method using biological information such as a fingerprint, a face, an iris, and a heart sound is known. User authentication based on biometric information is performed by comparison with biometric information registered in advance (for example, Patent Document 1 and Patent Document 2).

JP 2005-71225 A International Publication No. 2005/058160

  The biological information detected by the wearable terminal may fluctuate under the influence of the physical condition or state of the user wearing the wearable terminal. For example, when a heartbeat waveform is registered in advance as biometric information in a wearable terminal, the heart rate increases immediately after exercise, and therefore a waveform different from the heartbeat waveform registered in advance may be detected. As described above, the user authentication may not be normally performed in comparison with the biometric information registered in advance.

  An object of this invention is to provide the technique which suppresses the influence of a change of a user's physical condition etc. in the biometric authentication of the user of a terminal device.

  One aspect of the present invention is a mode in which the first device can acquire the first biological information of the user and can collate with the first biological information by the second device connected to the first device. Is a biometric authentication method for receiving the second biometric information acquired from the user and comparing the first biometric information and the second biometric information.

  According to one aspect of the present invention, in the biometric authentication of a user of a terminal device, the influence of changes in the user's physical condition and the like can be suppressed.

It is a figure which shows the example of operation which cancels | releases the lock | wear of a wearable terminal from a smart phone. It is a figure which shows an example of the hardware constitutions of a wearable terminal. It is a figure which shows an example of the hardware constitutions of a smart phone. It is a figure which shows the example in which the period of a heartbeat waveform corresponds and a user is authenticated. It is a figure which shows the example in which the period of a heartbeat waveform does not correspond and a user is not authenticated. It is a figure which shows the example in which the timing of the location which shows the peak of a heartbeat waveform corresponds, and a user is authenticated. It is a figure which shows the example in which the timing of the location which shows the peak of a heartbeat waveform does not correspond, and a user is not authenticated. It is a figure which illustrates the waveform detected at the time of wearable terminal wearing. It is a figure which illustrates the waveform detected at the time of wearable terminal non-wearing. It is a sequence diagram which shows the operation example of a user authentication process. It is a sequence diagram which shows the operation example of a user authentication process. It is a sequence diagram which shows the operation example of the wearing state confirmation process of a wearable terminal. It is a flowchart which shows the example of the user authentication process in a wearable terminal. It is a flowchart which shows the example of the mounting state confirmation process in a wearable terminal. It is a flowchart which shows the example of the process regarding the user authentication of the wearable terminal in a smart phone. It is a flowchart which shows the example of the process regarding the user authentication of the wearable terminal in a smart phone. It is a figure which shows an example of the hardware constitutions of the wearable terminal in Embodiment 2. FIG. 10 is a sequence diagram illustrating an operation example of user authentication processing in the second embodiment.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings. The configuration of the following embodiment is an exemplification, and the present invention is not limited to the configuration of the embodiment.

<Embodiment 1>
In the first embodiment, the wearable terminal compares the user's heartbeat waveform detected by its own terminal with the user's heartbeat waveform detected by another device such as a smartphone, thereby determining whether or not the user can be authenticated. to decide. When the user is authenticated, the wearable terminal unlocks the wearable terminal.

  Note that, for example, an optical sensor such as a heart rate sensor is used to detect the heart rate waveform in the wearable terminal. In addition, for example, an electrostatic sensor included in a touch panel, an image sensor mounted on a camera, or an optical sensor built in a smartphone is used to detect a heartbeat waveform on the smartphone.

  FIG. 1 is a diagram illustrating an example of an operation for unlocking the wearable terminal 1 from the smartphone 2. In the first embodiment, the wearable terminal 1 has a wristwatch type as an example. The user performs a predetermined operation for unlocking the wearable terminal 1 attached to the arm on the touch panel of the smartphone 2.

  The smartphone 2 acquires the heartbeat waveform data of the user and transmits the acquired heartbeat waveform data to the wearable terminal 1 by wireless communication. The wireless communication means is, for example, Bluetooth (BT) (registered trademark), WiFi, or Near Field Communication (NFC). The wearable terminal 1 and the smartphone 2 are examples of wireless terminals that perform wireless communication together.

The wearable terminal 1 acquires heart rate waveform data in its own terminal, and compares the acquired heart rate waveform data with the heart rate waveform data received from the smartphone 2. The heartbeat waveform repeats the same waveform periodically according to the movement of the heart.

  If the heartbeat waveform of the wearable terminal 1 and the heartbeat waveform of the smartphone 2 match the period or timing of the characteristic part, the wearable terminal 1 authenticates the user and releases the lock. The characteristic portion is, for example, a portion (hereinafter also referred to as a peak) showing the highest value in one cycle of the heartbeat waveform.

  The wearable terminal 1 stops wireless communication with the smartphone 2 when the lock is released by user authentication. On the other hand, the wearable terminal 1 continues to acquire heartbeat waveform data in its own terminal in order to confirm whether or not it has been removed from the user. The acquisition of the heartbeat waveform data may be repeated intermittently at a predetermined interval. When the wearable terminal 1 detects the heartbeat waveform, the wearable terminal 1 remains in the unlocked state. Wearable terminal 1 sets a lock when the user removes wearable terminal 1 and no heartbeat waveform is detected.

<Hardware configuration>
FIG. 2 is a diagram illustrating an example of a hardware configuration of the wearable terminal 1. The wearable terminal 1 includes an application large-scale integration (LSI) 10a, a random access memory (RAM) 12a, an auxiliary storage device 13a, a network integrated circuit (IC) 14a, an antenna 15a, and a heart rate sensor 16. These are connected to each other by a bus.

  The Application LSI 10a is an application specific integrated circuit (ASIC) that is designed to execute various functions of the wearable terminal 1. The application LSI 10a includes a central processing unit (CPU) 11a.

  The CPU 11a loads a computer program such as an operating system (Operating System, OS) and an unlock application held in the auxiliary storage device 13a into the RAM 12a and executes the program. The CPU 11a executes unlocking and lock setting of the wearable terminal 1, authentication processing by comparing heartbeat waveform data, and the like by a computer program. However, a part of the processing by the computer program may be executed by a hardware circuit. The CPU 11a may be, for example, a digital signal processor (DSP) that is a microprocessor specialized in digital signal processing. The CPU 11a is an example of an “authentication unit”.

  The RAM 12a provides the CPU 11a with a storage area for loading a computer program stored in the auxiliary storage device 13a and a work area for executing the computer program. The RAM 12a is used as a buffer for holding data. The RAM 12a is a semiconductor memory such as a static RAM (SRAM) or a dynamic RAM (DRAM).

The auxiliary storage device 13a stores various computer programs and data used by the CPU 11a when executing each computer program. The auxiliary storage device 13a is, for example, a non-volatile memory such as an Erasable Programmable Read Only Memory (EPROM), a flash memory, a Solid State Drive (SSD), or a hard disk drive (Hard Disk Drive, HDD). The auxiliary storage device 13a holds various application programs such as an OS and an unlock application.

  The network IC 14a is an integrated circuit module that inputs and outputs information to and from the network. The network IC 14a is connected to a wireless network through the antenna 15a. The network IC 14a is, for example, a wireless local area network (LAN) module or a BT module. Data received by the network IC 14a is output to the CPU 11a. The network IC 14a and the antenna 15a are examples of the “receiving unit”.

  The heart rate sensor 16 is, for example, an optical sensor that measures a heart rate by measuring a change in blood flow with an infrared sensor. The heart rate sensor 16 may be an electrocardiographic sensor that is provided in training wear or the like and directly measures the heart rate by placing it on the chest. The heart rate sensor 16 is an example of a “sensor”.

  For example, in the wearable terminal 1, the CPU 11a loads the lock release application held in the auxiliary storage device 13a into the RAM 12a and executes it. Note that the hardware configuration of wearable terminal 1 is an example, and is not limited to the above, and components can be omitted, replaced, or added as appropriate according to the embodiment.

  FIG. 3 is a diagram illustrating an example of a hardware configuration of the smartphone 2. The smartphone 2 includes an Application LSI 10b, a RAM 12b, an auxiliary storage device 13b, a network IC 14b, an antenna 15b, a touch panel 17, a display 18, a camera 19, an audio IC 20b, and a microphone 21b. These are connected to each other by a bus.

  The Application LSI 10b is an application specific integrated circuit (ASIC), and is a circuit designed to execute various functions of the smartphone 2. The application LSI 10b includes a CPU 11b.

  The CPU 11b loads the OS and various computer programs held in the auxiliary storage device 13b to the RAM 12a and executes them. The CPU 11b executes various processes such as a request for starting an unlock application to the wearable terminal 1 and transmission of heartbeat waveform data to the wearable terminal 1 by a computer program. However, a part of the processing by the computer program may be executed by a hardware circuit. The CPU 11b may be, for example, a DSP that is a microprocessor specialized in digital signal processing.

  The RAM 12b provides the CPU 11b with a storage area for loading a computer program stored in the auxiliary storage device 13b and a work area for executing the computer program. The RAM 12b is used as a buffer for holding data. The RAM 12b is a semiconductor memory such as SRAM or DRAM, for example.

  The auxiliary storage device 13b stores various computer programs and data used by the CPU 11b when executing each computer program. The auxiliary storage device 13b is a non-volatile memory such as an EPROM, a flash memory, an SSD, or a hard disk drive. The auxiliary storage device 13b holds an OS and various other application programs.

The network IC 14b is an integrated circuit module that inputs and outputs information to and from the network. The network IC 14b is connected to a wireless network through the antenna 15b. The network IC 14b is, for example, a wireless LAN module or a BT module. Data received by the network IC 14b is output to the CPU 11b.

  The touch panel 17 is one of position input devices, and is disposed on the surface of the display 18. The touch panel 17 inputs the coordinates of the touch position of the finger corresponding to the screen of the display 18. The touch panel 17 includes an electrostatic sensor 171.

  The electrostatic capacitance detected by the electrostatic sensor 171 varies according to the minute movement of the finger linked to the pulse or the change in blood flow. Therefore, when the user touches the touch panel 17 for a predetermined period, the electrostatic sensor 171 detects the heartbeat waveform by measuring the capacitance value in time series and processing the waveform of the measurement result. Can do.

  The display 18 is, for example, a liquid crystal display (LCD). The display 18 displays screen data in accordance with a signal input from the CPU 11b.

  The camera 19 is one of imaging devices including an optical sensor 191. The optical sensor 191 is, for example, an image sensor of a complementary metal oxide semiconductor (CMOS) or a charge coupled device (CCD). By touching the lens of the camera 19 for a predetermined period, the optical sensor 191 measures the heart rate by measuring the amount of light absorption that changes in accordance with the speed of blood flow and the amount of blood due to the heartbeat.

  The audio IC 20b is connected to a microphone 21b as a voice input device. The audio IC 20b is a circuit for converting a signal such as sound input from the microphone 21b into an electric signal and outputting the electric signal to the CPU 11b. The microphone 21b is an example of a “voice input device”.

  Note that the hardware configuration of the smartphone 2 is an example, and is not limited to the above, and components can be appropriately omitted, replaced, or added according to the embodiment. In addition, the smartphone 2 has a configuration (apparatus, device, sensor, etc.) for acquiring biological information such as the touch panel 17, the camera 19, and the microphone 21b in advance. For this reason, it is not necessary to newly install a device for acquiring desired biological information.

  The wearable terminal 1 is an example of a “first device” or a “biometric authentication device”. The smartphone 2 is an example of a “second device”. The first device authenticates the user of the first device by comparing the heartbeat waveform data acquired by the first device with the heartbeat waveform data acquired by the second device.

  Note that the first device and the second device may be devices other than those described above. For example, the first device may be the smartphone 2 and the second device may be the wearable terminal 1. In this case, the smartphone 2 authenticates the user of the smartphone 2 by comparing the heartbeat waveform data acquired by the smartphone 2 with the heartbeat waveform data acquired by the wearable terminal 1.

<Authentication method using heart rate waveform data>
In the authentication process using the heartbeat waveform data, the wearable terminal 1 receives the heartbeat waveform data measured by the smartphone 2 and compares it with the heartbeat waveform data measured by the wearable terminal 1.

  The wearable terminal 1 authenticates that the user of the wearable terminal 1 is the same as the user of the smartphone 2 if the data of the two heartbeat waveforms to be compared match within a range of a predetermined allowable value. Wearable terminal 1 determines that authentication of the user of wearable terminal 1 has failed if the data of the two heartbeat waveforms to be compared do not match.

  Whether the heartbeat waveform data match can be determined by, for example, the following two methods. The first method is a method for determining whether or not the period of the heartbeat waveform, that is, the interval between the peaks of the heartbeat waveform matches. The second method is a method for determining whether or not the timings at the peak of the heartbeat waveform match.

  4A and 4B are explanatory diagrams of the first method. FIG. 4A shows an example in which the periods of the heartbeat waveforms in wearable terminal 1 and smartphone 2 match and the user is authenticated. FIG. 4B shows an example in which the period of the heartbeat waveform does not match and the user is not authenticated.

  4A and 4B, a graph of a heartbeat waveform detected by the wearable terminal 1 is shown. A graph of a heartbeat waveform detected by the smartphone 2 is shown in the lower part. The horizontal axis of each graph indicates time, and the vertical axis indicates potential.

  The heartbeat waveform is a waveform that repeats a waveform showing three rises and falls as one cycle in accordance with the motion of the heart. Assuming that the peak rise and fall due to the contraction of the heart is the first time, the amplitude of the second rise and fall that occurs next is about one third of the peak. After the second rise and fall, the heartbeat waveform shows a substantially constant value for a predetermined period. The third rise and fall amplitude that occurs after exhibiting a substantially constant value is even smaller than the second rise and fall amplitude. After the third rise and fall, the heartbeat waveform is peaked and the next cycle begins.

  In the graph of the wearable terminal 1 in FIG. 4A, from the time when a peak interval, that is, a threshold for measuring a period (hereinafter also referred to as a period measurement threshold) is exceeded, until the potential exceeds the period measurement threshold next time. The time is 520 ms. Similarly, in the graph of the smartphone 2, the time from when the potential exceeds the period measurement threshold to when the next potential exceeds the period measurement threshold is 520 ms. Since the cycles of wearable terminal 1 and smartphone 2 match, the heartbeat waveform detected by wearable terminal 1 is determined to be the same heartbeat waveform of the user as the heartbeat waveform detected by smartphone 2. Therefore, the user is authenticated.

  In the example of FIG. 4A, the cycles of the wearable terminal 1 and the smartphone 2 are determined within the allowable value range of the 1 ms order. This allowable value may be determined by, for example, the measurement accuracy of the heart rate of the wearable terminal 1 and the smartphone 2, and 0.1%, 1%, etc. of a typical pulse period (for example, 1 second) are allowable values. May be set as Allowable values such as 0.1% and 1% are examples of “predetermined allowable error”.

  On the other hand, in the graph of wearable terminal 1 in FIG. 4B, the time from when the peak potential exceeds the period measurement threshold to the next time the potential exceeds the period measurement threshold is 510 ms. Further, in the graph of the smartphone 2, the time from when the potential exceeds the period measurement threshold to when the potential exceeds the period measurement threshold is 535 ms. Since the cycles of the wearable terminal 1 and the smartphone 2 do not match, it is determined that the heartbeat waveform detected by the wearable terminal 1 is not the same heartbeat waveform of the user as the heartbeat waveform detected by the smartphone 2. Therefore, the user is not authenticated.

  5A and 5B are explanatory diagrams of the second method. FIG. 5A shows an example in which the user is authenticated because the timings of the portions indicating the peak of the heartbeat waveform coincide with each other. FIG. 5B shows an example in which the timing of the portion showing the peak of the heartbeat waveform does not match and the user is not authenticated.

  The heartbeat waveform in the wearable terminal 1 is shown in the upper part of FIGS. 5A and 5B. In the lower part, a graph of the heartbeat waveform on the smartphone 2 is shown. The horizontal axis of each graph indicates time, and the vertical axis indicates potential.

  In the second method, when the heartbeat waveform data is acquired in the wearable terminal 1 and the smartphone 2, time information is also acquired. In each graph of the wearable terminal 1 and the smartphone 2, the peak time is shown.

  The peak time in the graph of the wearable terminal 1 in FIG. 5A is compared with the peak time in the smartphone 2 graph. The first peak times of the wearable terminal 1 and the smartphone 2 are the same at 12 minutes, 10 seconds, and 0.00 milliseconds (time is omitted, and is expressed as 12: 10: 00.00). . The subsequent three peak times also coincide, and the heartbeat waveform detected by the wearable terminal 1 is determined to be the same heartbeat waveform of the user as the heartbeat waveform detected by the smartphone 2. Therefore, the user is authenticated.

  In the example of FIG. 5A, the peak times of the wearable terminal 1 and the smartphone 2 are determined within a range of allowable values on the order of 1 millisecond. This allowable value may be determined by, for example, the measurement accuracy of the heartbeats of the wearable terminal 1 and the smartphone 2, and 0.1%, 1%, etc. of typical peak intervals (for example, 1 second) are allowable values. May be set as The wearable terminal 1 may collect a difference in peak times between the wearable terminal 1 and the smartphone 2 and set an allowable value based on the collected difference value. The set allowable value is an example of “predetermined allowable error”.

  Moreover, the peak time in the graph of the wearable terminal 1 in FIG. 5B is compared with the peak time in the smartphone 2 graph. The first peak time at the wearable terminal 1 is 12: 09: 09.80, and the first peak time at the smartphone 2 is 12: 10: 00.00, and the timings do not match. In the wearable terminal 1, the subsequent peak times are 12: 10: 05.20, 12: 10: 10.40, and 12: 10: 15.60. In the smartphone 2, the subsequent peak times are 12: 10: 04.80, 12: 10: 10.15, and 12: 10: 15.90. Therefore, the peak times of the wearable terminal 1 and the smartphone 2 do not match. For this reason, it is determined that the heartbeat waveform detected by the wearable terminal 1 is not the same heartbeat waveform of the user as the heartbeat waveform detected by the smartphone 2. Therefore, the user is not authenticated.

<Determination of wearing state of wearable terminal>
When the user is authenticated in the wearable terminal 1, the wearable terminal 1 is unlocked. While the user is wearing the wearable terminal 1, the unlocked state continues. When the user removes the wearable terminal 1, the wearable terminal 1 is locked. The wearing state of whether or not the wearable terminal 1 is worn is determined based on the heartbeat waveform detected by the wearable terminal 1.

6A and 6B are diagrams for explaining a method of determining the wearing state of the wearable terminal 1. Whether or not it is in a wearing state is determined by whether or not the amplitude of the potential of the heartbeat waveform detected by the wearable terminal 1 exceeds a predetermined threshold (hereinafter also referred to as a wearing determination threshold). For example, the wearing determination threshold value can be set to a value within a range from a potential at the next highest value in the peak to a potential at the peak in one cycle. FIG. 6A is a diagram illustrating a waveform detected when the wearable terminal is mounted. FIG. 6B is a diagram illustrating a waveform detected when the wearable terminal is not attached.

  FIG. 6A shows a graph of a waveform detected by wearable terminal 1 at the time of wearing. The horizontal axis of the graph indicates time, and the vertical axis indicates potential. The amplitude of the potential at the peak exceeds the wearing judgment threshold. Therefore, it is determined that wearable terminal 1 is in the wearing state.

  On the other hand, FIG. 6B shows a graph of a waveform detected by wearable terminal 1 when not worn. The horizontal axis of the graph indicates time, and the vertical axis indicates potential. The waveform shown in FIG. 6B repeats a slight increase and decrease with an amplitude smaller than the attachment determination threshold. Since the amplitude of the detected waveform does not exceed the wearing determination threshold, the wearable terminal 1 is determined to be in a non-wearing state.

  In the example of FIGS. 6A and 6B, the wearable terminal 1 determines whether or not the wearable terminal 1 is in the mounted state depending on whether or not the amplitude of the detected waveform may exceed the mounting determination threshold, but the potential value is determined in advance. The determination may be made based on whether or not there is a case of deviating from the range of the given value. At this time, the wearable terminal 1 can determine that the wearable terminal 1 is in the mounted state if a potential that deviates from a predetermined value range is detected. Wearable terminal 1 can determine that the wearable terminal 1 is not attached unless a potential that deviates from a predetermined range of values is detected.

<Operation example>
7A, 7B, and 7C show an operation example of processing related to user authentication in the wearable terminal 1 and the smartphone 2. FIG. The processing illustrated in FIGS. 7A to 7C is started, for example, when the user uses the wearable terminal 1.

  FIG. 7A is a sequence diagram illustrating an operation example of user authentication processing. In S1, wearable terminal 1 and smartphone 2 are in a standby state and a locked state. The standby state is a state where the operating state of the wearable terminal 1 is stored in the RAM 12a and the operation is stopped while the power is on. In the standby state, power consumption is suppressed as compared to during startup.

  In S2, the user wears wearable terminal 1. The user first releases the wearable terminal 1 from the standby state. In S3, the user presses the standby release key of the wearable terminal 1. Release of the standby state in the wearable terminal 1 is not limited to pressing a specific standby release key. The standby state of the wearable terminal 1 may be canceled by an operation of touching the touch panel or the like of the wearable terminal 1.

  In S4, the wearable terminal 1 detects pressing of the standby release key. When the standby state is canceled by a method other than pressing the standby cancellation key, the wearable terminal 1 may detect a user operation for canceling the standby state. In accordance with the detection result of the user's operation for canceling the standby state, in S5, the wearable terminal 1 cancels the standby state.

  Next, the user cancels the standby state of the smartphone 2. In S6, the user presses the standby release key of the smartphone 2. The cancellation of the standby state in the smartphone 2 is not limited to pressing a specific standby cancellation key. The standby state of the smartphone 2 may be canceled by a user operation exemplified by pressing an operation button (not shown) included in the smartphone 2 or touching the touch panel 17.

  In S7, the smartphone 2 detects pressing of the standby release key. When the standby state is canceled by a method other than pressing of the standby cancellation key, the smartphone 2 may detect a user operation for canceling the standby state. According to the detection result of the user's operation for canceling the standby state, in S8, the smartphone 2 cancels the standby state.

  In S <b> 9, the user performs an activation operation of an unlock application (hereinafter also referred to as an unlock application) on the smartphone 2. The unlock application includes a plurality of modules executed on the smartphone 2 and the wearable terminal 1. In the smartphone 2, the unlock application receives an operation for unlocking from the user, for example. Moreover, the lock release application sets or releases the lock of the wearable terminal 1 in the wearable terminal 1 according to the authentication result based on the acquired biometric information, for example. In S10, the smartphone 2 activates the unlock application.

  Wearable terminal 1 and smart phone 2 establish mutual BT communication by processing from S11 to S16. In S11, the wearable terminal 1 and the smartphone 2 start the BT communication establishment process by starting the unlock application of the smartphone 2 in S10.

  In S12, the smartphone 2 starts a BT standby state. In S13, the wearable terminal 1 starts detecting a paired device of BT. Pairing is a process of registering each other in advance so that wirelessly connected devices are connected one-on-one.

  The wearable terminal 1 and the smartphone 2 may hold, for example, registered paired device information in the auxiliary storage device 13a and the auxiliary storage device 13b, respectively. When the wearable terminal 1 detects the smartphone 2 within the wireless communication range, the wearable terminal 1 transmits the device ID of the wearable terminal 1 to the smartphone 2.

  In S <b> 14, the smartphone 2 determines whether the wearable terminal 1 has been paired with BT based on the device ID received from the wearable terminal 1. When the smartphone 2 determines that the wearable terminal 1 has been paired with the BT, the smartphone 2 transmits the device ID of the smartphone 2 to the wearable terminal 1.

  In S <b> 15, the wearable terminal 1 determines whether or not the wearable terminal 1 has been paired with the BT based on the device ID received from the smartphone 2. When the wearable terminal 1 determines that the smartphone 2 has been paired with the BT, the wearable terminal 1 establishes BT communication with the smartphone 2. In S16, the BT communication establishment process is completed.

  FIG. 7B is a sequence diagram illustrating an operation example of a user authentication process following the process illustrated in FIG. 7A. In S20, the user authentication process of the wearable terminal 1 is started. In S <b> 21, the smartphone 2 transmits an activation request for the unlock application to the wearable terminal 1.

  In S22, the wearable terminal 1 activates the unlock application. In S <b> 23, wearable terminal 1 transmits an activation completion notification of the unlock application to smartphone 2.

In S24, the smartphone 2 displays a user authentication screen for the unlock application. In S25, the user starts a heartbeat authentication operation in accordance with an instruction on the user authentication screen. The heartbeat authentication operation is an operation for causing the wearable terminal 1 and the smartphone 2 to detect a user's heartbeat waveform. For example, the user can cause the smartphone 2 to detect a heartbeat waveform by touching the touch panel 17 of the smartphone 2 or the lens of the camera 19. The wearable terminal 1 can detect a heartbeat waveform from the heartbeat sensor 16 even when there is no user operation in the wearing state.

  In S <b> 26, the smartphone 2 transmits a heartbeat waveform data acquisition start notification to the wearable terminal 1. In S27, wearable terminal 1 and smart phone 2 acquire heart rate waveform data.

  In S <b> 28, when the smartphone 2 acquires the heartbeat waveform data for a predetermined period, the smartphone 2 transmits a data acquisition completion notification to the wearable terminal 1. The predetermined period may be a period in which the heartbeat waveform data includes at least one cycle, for example.

  In S <b> 29, when the wearable terminal 1 receives the data acquisition completion notification, the wearable terminal 1 transmits a heartbeat waveform data transmission request to the smartphone 2. In S <b> 30, the smartphone 2 transmits the acquired heartbeat waveform data to the wearable terminal 1.

  In S31, the wearable terminal 1 compares the heartbeat waveform data acquired by its own terminal with the heartbeat waveform data received from the smartphone 2, and determines whether or not the user can be authenticated. In S <b> 32, the wearable terminal 1 transmits a determination result on whether or not authentication is possible to the smartphone 2. If the user is not authenticated in S31, the processing from S25 to S31 is repeated (S33).

  The heartbeat waveform data acquired by its own terminal (wearable terminal 1) is an example of “first biological information”. The heartbeat waveform data received from the smartphone 2 is an example of “second biological information”. The first biological information and the second biological information are not limited to heartbeat waveform data. The first biological information acquired by the first device is in a form that can be collated with the second biological information acquired by the second device, and may be biological information that can identify the user.

  In S34, the smartphone 2 displays that the user authentication is completed on the user authentication screen of the unlock application. In S35, the wearable terminal 1 releases the lock of the wearable terminal 1. The process of S35 should just be implemented after a user is authenticated in S31, and the process before and after the process of S34, S36, and S37 is not ask | required.

  In S36, the user ends the heartbeat authentication operation. The heartbeat authentication operation may be continued until the wearable terminal 1 and the smartphone 2 complete the acquisition of heartbeat waveform data in S27, and the process of S36 is not limited to the process from S28 to S35.

  In S37, the smartphone 2 ends wireless communication with the wearable terminal 1 and turns off the BT function. In S38, the smartphone 2 ends the unlock application. With the termination of the unlock application, the user authentication process of the wearable terminal 1 is completed in S39.

  FIG. 7C is a sequence diagram illustrating an operation example of the wearing state confirmation process of the wearable terminal 1 subsequent to the process illustrated in FIG. 7B. In S40, the smartphone 2 shifts to a standby state. After shifting to the standby state, the power consumption of the smartphone 2 is suppressed.

In S41, the wearable terminal 1 wearing state confirmation process is started. In S42, the wearable terminal 1 acquires the user's heartbeat waveform data. In S43, the wearable terminal 1 determines whether or not a heartbeat waveform is detected based on whether or not the acquired heartbeat waveform data is within a predetermined threshold range. The wearable terminal 1 determines that the heartbeat waveform has not been detected when the acquired heartbeat waveform data is within a predetermined threshold range. On the other hand, the wearable terminal 1 determines that a heartbeat waveform has been detected when the acquired heartbeat waveform data is not within a predetermined threshold range. Wearable terminal 1 determines that it is in a worn state when a heartbeat waveform is detected, and repeats the processes of S42 and S43 for each predetermined period.

  In S44, the user removes the wearable terminal 1. The wearable terminal 1 is in a non-wearing state. In S45, wearable terminal 1 acquires a user's heartbeat waveform data. In S46, since the wearable terminal 1 is not worn, the heartbeat waveform is not detected.

  In S <b> 47, the wearable terminal 1 determines that the wearable terminal 1 is not attached, and sets the wearable terminal 1 to be locked. In S48, the wearing state confirmation process of the wearable terminal 1 ends. In S49, wearable terminal 1 shifts to a standby state. The processing shown in FIGS. 7A to 7C ends.

<Process flow>
8A and 8B are flowcharts illustrating an example of processing related to user authentication in the wearable terminal 1. FIG. 9A and FIG. 9B are flowcharts showing an example of processing related to user authentication of the wearable terminal 1 in the smartphone 2.

  FIG. 8A is a flowchart illustrating an example of user authentication processing in the wearable terminal 1. The user authentication process in the wearable terminal 1 is started, for example, when the user wears the wearable terminal 1. In the process of FIG. 8A, the time-out process by the timer is omitted, but in OP10, OP18, OP20, etc., the timer is appropriately set and the time-out process is executed.

  In OP10, wearable terminal 1 determines whether or not the user has pressed a key to cancel the standby state. If the key is pressed (OP10: Yes), the process proceeds to OP11. If the key is not pressed (OP10: No), the process of OP10 is executed again. The operation for canceling the standby state is not limited to pressing a key, and may be an operation by other input means provided in the wearable terminal 1. For example, in the wearable terminal 1 including a touch panel, the standby state may be canceled by touching the touch panel. In OP11, the wearable terminal 1 cancels the standby state.

  In OP12, the wearable terminal 1 reads information on the paired device from the auxiliary storage device 13a. In OP13, the wearable terminal 1 starts detecting a paired device of BT. The wearable terminal 1 transmits the device ID of the wearable terminal 1 to the detected smartphone 2.

  In OP <b> 14, the wearable terminal 1 determines whether or not the smartphone 2 has notified BT communication authentication permission. When there is a notification of authentication permission for BT communication from the smartphone 2 (OP14: Yes), the process proceeds to OP15. When there is no notification of authentication permission of BT communication from the smartphone 2 (OP14: No), the waiting time is measured by a timer, and there is no notification of permission of authentication of BT communication from the smartphone 2 even if a predetermined period elapses. In the case, the process proceeds to OP27.

In OP <b> 15, the wearable terminal 1 determines whether or not there is a request to activate the unlock application from the smartphone 2. If there is an unlock application launch request from the smartphone 2 (OP15: Yes), the process proceeds to OP16. When there is no unlocking application activation request from the smartphone 2 (OP15: No), the waiting time is measured by the timer, and when there is no unlocking application activation request from the smartphone 2 even after a predetermined period has elapsed, The process proceeds to OP27. The process of OP15 is an example of a process of “performing the user authentication process when receiving a notification that a predetermined operation has been performed on the second apparatus”.

  In OP16, the wearable terminal 1 activates the unlock application. In OP <b> 17, the wearable terminal 1 transmits a lock release application activation completion notification to the smartphone 2.

  In OP <b> 18, the wearable terminal 1 determines whether or not there is a heartbeat waveform data acquisition start notification from the smartphone 2. When the heartbeat waveform data acquisition start notification is received from the smartphone 2 (OP18: Yes), the process proceeds to OP19. When there is no heartbeat waveform data acquisition start notification from the smartphone 2 (OP18: No), the process of OP18 is executed again. In OP19, the wearable terminal 1 acquires heartbeat waveform data at its own terminal. The acquired data is stored in the RAM 12a. The process of OP19 is an example of a process of “acquiring first user biometric information”.

  In OP20, the wearable terminal 1 determines whether or not a notification of completion of heartbeat waveform data acquisition has been received from the smartphone 2. If there is a notification of completion of heartbeat waveform data acquisition from the smartphone 2 (OP20: Yes), the process proceeds to OP21. If there is no notification of completion of heartbeat waveform data acquisition from the smartphone 2 (OP20: No), the process of OP20 is executed again. The process of OP20 is an example of a process of “receiving notification that the acquisition of the second biometric information has been completed from the second apparatus”.

  In OP <b> 21, wearable terminal 1 transmits a heartbeat waveform data transmission request to smartphone 2. The process of OP21 is an example of a process of “requesting the second apparatus to transmit the second biological information”.

  In OP <b> 22, the wearable terminal 1 receives heartbeat waveform data from the smartphone 2. The received heartbeat waveform data is stored in the RAM 12a. The process of OP22 is an example of a process of “receiving the second biological information acquired from the user in a form that can be collated with the first biological information”.

  In OP23, the wearable terminal 1 compares the data acquired in its own terminal with the heartbeat waveform data received from the smart phone 2, and determines whether or not the user can be authenticated. In OP24, the wearable terminal 1 determines whether or not the user is authenticated by comparing the heartbeat waveform data. If the user is authenticated (OP24: Yes), the process proceeds to OP25. If the user is not authenticated (OP24: No), the process proceeds to OP27. The processes of OP23 and OP24 are an example of a process of “comparing the first biological information and the second biological information”.

  If the user is not authenticated, wearable terminal 1 may repeat the process of comparing heartbeat waveform data from OP18 to OP24 for a predetermined period or a predetermined number of times. If the user is not authenticated even after repeating the process of comparing the heartbeat waveform data, the process proceeds to OP27.

  In OP25, the wearable terminal 1 transmits an authentication result indicating that the user is authenticated to the smartphone 2. In OP26, the wearable terminal 1 releases the lock. Processing continues to OP40 in FIG. 8B.

  In OP27, the wearable terminal 1 requests the smartphone 2 to start an authentication screen by a touch panel operation. For example, the smartphone 2 receives a password input from a user on an authentication screen by a touch panel operation. The wearable terminal 1 acquires the authentication result in the smartphone 2. However, the wearable terminal 1 may include a touch panel or the like, activate an authentication screen by touch panel operation, and accept a password input from a user. As described above, when the user is not authenticated by comparison with the heartbeat waveform data in the smartphone 2, the wearable terminal 1 performs user authentication by using an existing method such as password entry in the terminal or the smartphone 2. May be. The process of OP27 is a process of “presenting means for prompting the user to input authentication information when the user is not authenticated by comparing the first biometric information and the second biometric information”. It is an example.

  In OP28, the wearable terminal 1 determines whether or not the user is authenticated by inputting the user's password or the like. If the user is authenticated (OP28: Yes), the process proceeds to OP26. If the user is not authenticated (OP28: No), the process continues to OP43 in FIG. 8B.

  FIG. 8B is a flowchart illustrating an example of the wearing state confirmation process in the wearable terminal 1. The process shown in FIG. 8B is a process following OP26 in FIG. 8A. In OP40, the wearable terminal 1 acquires heart rate waveform data at its own terminal for a predetermined period. The predetermined period may be a period in which the heartbeat waveform data includes at least one cycle, for example.

  In OP41, the wearable terminal 1 determines whether or not a heartbeat waveform having a potential equal to or higher than the wearing determination threshold is detected from the acquired heartbeat waveform data. For example, the wearing determination threshold value can be set to a value within a range from a potential at the next highest value in a cycle to a potential at the peak. If a heartbeat waveform whose potential is equal to or higher than the wearing determination threshold is detected (OP41: Yes), the process returns to OP40. If a heartbeat waveform whose potential is greater than or equal to the wearing determination threshold is not detected (OP41: No), the process proceeds to OP42.

  In OP42, the wearable terminal 1 sets the lock of the wearable terminal 1. The processing of OP41 and OP42 is an example of processing for “setting a lock on the first device when the signal amplitude obtained as the acquired first biological information is smaller than a predetermined threshold”. In OP43, the wearable terminal 1 shifts to the standby mode. The process related to user authentication in the wearable terminal 1 ends.

  FIG. 9A is a flowchart illustrating an example of processing related to user authentication of the wearable terminal 1 in the smartphone 2. The process related to user authentication of the wearable terminal 1 in the smartphone 2 is started, for example, when the user wears the wearable terminal 1. In the processing of FIGS. 9A and 9B, the time-out process by the timer is omitted, but the timer is appropriately set in OP50, OP52, OP58, OP60, OP64 in FIG. 9A, OP70 in FIG. 9B, and the like. , Timeout processing is executed.

  In OP50, the smartphone 2 determines whether the user has pressed a key to cancel the standby state. If the key is pressed (OP50: Yes), the process proceeds to OP51. If the key is not pressed (OP50: No), the process of OP50 is executed again. The operation for canceling the standby state is not limited to pressing a key, and may be an operation of touching a touch panel or the like. In OP51, the smartphone 2 cancels the standby state.

  In OP52, the smartphone 2 determines whether or not the user has performed an activation operation of the unlock application. When the activation operation of the unlock application is performed by the user (OP52: Yes), the process proceeds to OP53. If the unlock application is not activated by the user (OP52: No), the process of OP52 is executed again.

  In OP53, the smartphone 2 activates the unlock application. In OP54, the smartphone 2 starts a BT standby state. In OP55, the smartphone 2 determines whether or not the wearable terminal 1 can be authenticated with respect to the process of detecting the BT paired device from the wearable terminal 1. For example, the smartphone 2 can determine that authentication is possible when the wearable terminal 1 is present in the paired device information held in the auxiliary storage device 13b. If the wearable terminal 1 can be authenticated (OP55: Yes), the process proceeds to OP56. If the wearable terminal 1 is not authenticated (OP55: No), the process continues to OP74 in FIG. 9B.

  In OP56, the smartphone 2 transmits a notification to the wearable terminal 1 that the wearable terminal 1 is a pair-linked device and can be authenticated. In OP57, the smartphone 2 transmits an activation request for the unlock application to the wearable terminal 1.

  In OP <b> 58, the smartphone 2 determines whether or not the unlockable app activation completion notification has been received from the wearable terminal 1. When the wearable terminal 1 receives a notification of activation completion of the unlock application (OP58: Yes), the process proceeds to OP59. If there is no notification of completion of activation of the unlock application from the wearable terminal 1 (OP58: No), the process of OP58 is executed again.

  In OP59, the smartphone 2 displays a user authentication screen for the unlock application. The user starts the heart rate authentication operation according to the instruction on the user authentication screen. In OP60, the smartphone 2 determines whether or not there is a heartbeat authentication operation by the user. If there is a heartbeat authentication operation by the user (OP60: Yes), the process proceeds to OP61. If there is no heartbeat authentication operation by the user (OP60: No), the process of OP60 is executed again.

  In OP61, the smartphone 2 transmits a heartbeat waveform data acquisition start notification to the wearable terminal 1. In OP62, the smartphone 2 acquires heartbeat waveform data for a predetermined period. The predetermined period may be a period in which the heartbeat waveform data includes at least one cycle, for example. In OP63, the smartphone 2 transmits a data acquisition completion notification to the wearable terminal 1.

  In OP64, the smartphone 2 determines whether or not the wearable terminal 1 has requested transmission of heartbeat waveform data. If there is a request for transmission of heartbeat waveform data from the wearable terminal 1 (OP64: Yes), the process proceeds to OP65. If there is no transmission request for heartbeat waveform data from the wearable terminal 1 (OP64: No), the process of OP64 is executed again. In OP65, the smartphone 2 transmits the acquired heartbeat waveform data to the wearable terminal 1. Processing continues to OP70 of FIG. 9B.

  FIG. 9B is a flowchart illustrating an example of processing related to user authentication of the wearable terminal 1 in the smartphone 2. The process shown in FIG. 9B is a process following OP65 in FIG. 9A.

In OP <b> 70, the smartphone 2 determines whether or not the authentication result is notified from the wearable terminal 1. When the authentication result is notified from the wearable terminal 1 (OP70: Yes), the process proceeds to OP71. If there is no notification of the authentication result from the wearable terminal 1 (OP70: No), the processing of OP70 is executed again.

  In OP71, the smartphone 2 determines whether or not the user has been authenticated based on the authentication result notified from the wearable terminal 1. If the user is authenticated (OP71: Yes), the process proceeds to OP72. If the user is not authenticated (OP71: No), the process proceeds to OP73.

  In OP72, the smartphone 2 displays that the user has been authenticated. In OP73, the smartphone 2 displays that the user has not been authenticated. In OP74, the smartphone 2 displays that there is no device to be authenticated.

  In OP75, the smartphone 2 ends the unlock application. In OP76, the smartphone 2 sets the lock of the smartphone 2. In OP76, the smartphone 2 shifts to the standby mode. The process related to user authentication of the wearable terminal 1 in the smartphone 2 ends.

<Effect of Embodiment 1>
In the first embodiment, the wearable terminal 1 determines whether or not the user can be authenticated by comparing the heartbeat waveform data acquired by the wearable terminal 1 with the heartbeat waveform data acquired by another device such as the smartphone 2. . As a result, even if the user's state changes, such as immediately after exercise, the wearable terminal 1 is compared with the heartbeat waveform data acquired in the changed state in another device. The influence of can be suppressed.

  Peaks in each cycle of the heartbeat waveform data are observed at specific intervals according to the user's condition. For this reason, the wearable terminal 1 compares the heartbeat waveform peak interval acquired by the wearable terminal 1 with the heartbeat waveform peak interval acquired by another device such as the smartphone 2, thereby performing user authentication. The influence of the state change can be suppressed.

  When the heartbeat waveform data is acquired in association with the time information, by comparing the peak time of the heartbeat waveform acquired by the wearable terminal 1 and the heartbeat waveform acquired by another device such as the smartphone 2 It is possible to determine whether or not the user can be authenticated. For this reason, the wearable terminal 1 can perform user authentication accurately by considering the time information.

  The wearable terminal 1 requests the smartphone 2 to transmit heartbeat waveform data when receiving notification that the acquisition of the heartbeat waveform data is completed from the smartphone 2. Thereby, the wearable terminal 1 can recognize the timing of the transmission request of the heartbeat waveform data to the smartphone 2.

  The wearable terminal 1 can determine that the user has removed the wearable terminal 1 when the amplitude of the heartbeat waveform acquired by the terminal is smaller than the wearing determination threshold. Thereby, when the user removes the wearable terminal 1, the wearable terminal 1 determines that the wearable terminal 1 is not attached and can set the lock without performing a specific operation.

  Moreover, in user authentication, in order to respond to a change in the state of the user, it is conceivable to relax the conditions for the heartbeat waveform data acquired by the wearable terminal 1 and other devices to match. However, relaxed conditions may reduce the level of security. In the first embodiment, the wearable terminal 1 acquires the heartbeat waveform data to be compared from another device in accordance with the change in the user's state, so that the user can be authenticated without lowering the security level. it can.

  If the lock is released after the wearable terminal 1 is mounted, the unlocked state of the wearable terminal 1 continues until the user removes the wearable terminal 1. For this reason, after the lock is released, the wearable terminal 1 does not communicate with other devices for the authentication process, and wasteful power consumption is suppressed.

  Moreover, in other apparatuses, such as the smart phone 2, when the user is authenticated as the owner of the other apparatus, the wearable terminal 1 is also authenticated as the owner himself / herself. . Therefore, it is possible to reduce the risk that both wearable terminal 1 and other devices are used by others.

  In addition, the user can unlock the wearable terminal 1 by a simple operation of touching the lens of the touch panel 17 or the camera 19 on another device such as the smartphone 2. For this reason, the convenience in the authentication process of the wearable terminal 1 is improved.

  Other devices can acquire heart rate waveform data using the existing touch panel 17 or camera 19. For this reason, there is no cost for installing a new device for acquiring heartbeat waveform data.

<Embodiment 2>
In the first embodiment, the wearable terminal 1 determines whether or not a user can be authenticated by comparing heartbeat waveforms. In the second embodiment, the wearable terminal determines whether or not the user can be authenticated by comparing voice data such as a heart sound waveform, a voice sound waveform, and a respiratory sound waveform.

  That is, in the second embodiment, as biometric authentication information by cooperation between the wearable terminal and the smartphone, voice data such as a heart waveform, a voice waveform, and a respiratory waveform can be used in addition to a heartbeat waveform.

  Specifically, the wearable terminal compares the voice data such as the user's heart sound waveform acquired by the terminal with the voice data of the user acquired by another device such as a smartphone, thereby Judgment of whether authentication is possible When the user is authenticated, the wearable terminal unlocks the wearable terminal. For example, a voice input device such as a microphone mounted on the wearable terminal 1 and the smartphone is used to acquire voice data such as a heart sound waveform.

  When the user wears the wearable terminal, the user inputs voice data such as a heart waveform, a voice waveform, and a respiratory waveform via the wearable terminal and the microphone of the smartphone in order to release the lock by user authentication. The smartphone acquires voice data such as a user's heart sound waveform, and transmits the acquired voice data to the wearable terminal by wireless communication.

  The wearable terminal acquires sound data such as a heart sound waveform in its own terminal, and compares the acquired sound data with the sound data received from the smartphone. If the periods or timings of the characteristic portions in the waveforms of the two audio data to be compared match, the wearable terminal authenticates the user and releases the lock. The characteristic part is, for example, a part that becomes a peak indicating the highest value in one cycle of the waveform of the audio data.

When the user is authenticated and unlocked, the wearable terminal stops wireless communication with the smartphone. On the other hand, as with the first embodiment, the wearable terminal acquires heartbeat waveform data in its own terminal and confirms the wearing state. The wearable terminal remains in the unlocked state when it detects a heartbeat waveform. The wearable terminal sets a lock when the user removes the wearable terminal and no heartbeat waveform is detected. Note that whether or not the user has removed the wearable terminal may be determined based on whether or not sound data such as a heart waveform is detected.

<Hardware configuration>
FIG. 10 is a diagram illustrating an example of a hardware configuration of the wearable terminal 3 according to the second embodiment. The wearable terminal 3 includes an Application LSI 10a, a RAM 12a, an auxiliary storage device 13a, a network IC 14a, an antenna 15a, an audio IC 20a, and a microphone 21a. These are connected to each other by a bus. The wearable terminal 3 is an example of a “first device” or a “biometric authentication device”.

  The application LSI 10a, the RAM 12a, the auxiliary storage device 13a, the network IC 14a, and the antenna 15a are the same as those shown by the same reference numerals in FIG.

  The audio IC 20a is connected to a microphone 21a as an audio input device. The audio IC 20a is a circuit for converting a signal such as a sound input from the microphone 21a into an electric signal and outputting it to the CPU 11a. The microphone 21a is an example of a “voice input device”. Since the hardware configuration of the smartphone in the second embodiment is the same as the hardware configuration of the smartphone 2 illustrated in FIG. 3, the description thereof is omitted.

<Operation example>
Among the user authentication processes in the second embodiment, the standby cancellation of the wearable terminal 3 and the smartphone 2 and the wireless communication start process between the wearable terminal 3 and the smartphone 2 are the same as the operation example shown in FIG. 7A of the first embodiment. Therefore, the description is omitted. Moreover, since the process which confirms the mounting state of the wearable terminal 3 after user authentication is the same as the operation example shown by FIG. 7C of Embodiment 1, the description is abbreviate | omitted.

  FIG. 11 is a sequence diagram illustrating an operation example of user authentication processing according to the second embodiment. The operation example shown in FIG. 11 follows the operation example shown in FIG. 7A. In S60, user authentication processing of wearable terminal 3 is started. In S <b> 61, the smartphone 2 transmits an activation request for the unlock application to the wearable terminal 3.

  In S62, wearable terminal 3 activates the unlock application. In S <b> 63, the wearable terminal 3 transmits a lock release application activation completion notification to the smartphone 2.

  In S64, the smartphone 2 displays a user authentication screen for the unlock application. In S65, when the user authentication screen is displayed, the user starts a biometric authentication operation. The biometric authentication operation is an operation for causing the wearable terminal 3 and the smartphone 2 to detect the user's biometric information. The biological information in the second embodiment is a heart sound waveform, a voice sound waveform, a respiratory sound waveform, or the like.

  As a biometric authentication operation for the smartphone 2, the user can cause the smartphone 2 to detect a heart sound waveform by, for example, bringing the microphone 21b of the smartphone 2 into contact with a human body or bringing it close to a distance where heart sounds can be detected. . Moreover, the user can make the smart phone 2 detect a voice sound wave shape or a respiratory sound wave shape by uttering a voice with respect to the microphone 21b of the smart phone 2.

On the other hand, the wearable terminal 3 can detect a heart sound waveform as long as it is worn.
Moreover, the wearable terminal 3 can detect the voice sound waveform or the respiratory sound waveform from the detected voice by detecting the voice uttered by the user with respect to the microphone 21b of the smartphone 2 by the microphone 21a. When the wearable terminal 3 cannot detect the voice of the user, the user causes the wearable terminal 3 to detect a voice sound waveform or a respiratory sound waveform by uttering the wearable terminal 3 close to the mouth. be able to.

  In S <b> 66, the smartphone 2 transmits a biometric information acquisition start notification to the wearable terminal 3. In S67, the wearable terminal 3 and the smartphone 2 acquire biometric information. In S65, since the user has started an operation for biometric authentication such as voice input, the wearable terminal 3 and the smartphone 2 can detect biometric information.

  In S <b> 68, when the smartphone 2 acquires biological information for a predetermined period, the smartphone 2 transmits a data acquisition completion notification to the wearable terminal 3. For example, the predetermined period may be a period in which the waveform indicated by the biological information includes at least one cycle.

  In S <b> 69, the wearable terminal 3 transmits a biometric information transmission request to the smartphone 2 when receiving the data acquisition completion notification. In S <b> 70, the smartphone 2 transmits the acquired biological information to the wearable terminal 3.

  In S71, the wearable terminal 3 compares the biometric information acquired by its own terminal with the biometric information received from the smartphone 2, and determines whether or not the user can be authenticated. In S <b> 72, the wearable terminal 3 transmits a determination result indicating whether or not authentication is possible to the smartphone 2. If the user is not authenticated in S71, the processes from S65 to S71 are repeated (S73).

  The data of the heart sound waveform, the voice sound waveform or the respiratory sound waveform acquired by its own terminal (wearable terminal 3) is an example of “first biological information”. The data of the heart sound waveform, the voice sound waveform or the respiratory sound waveform received from the smartphone 2 is an example of “second biological information”. The first biological information and the second biological information are not limited to data of a heart sound waveform, a voice sound waveform, or a respiratory sound waveform. The first biological information acquired by the first device is in a form that can be collated with the second biological information acquired by the second device, and may be biological information that can identify the user.

  In S74, the smartphone 2 displays that the user authentication has been completed on the user authentication screen of the unlock application. In S75, the wearable terminal 3 releases the lock of the wearable terminal 3. The process of S75 should just be implemented after a user is authenticated in S71, and the process before and after S74, S76, and S77 is not ask | required.

  In S76, the user ends the biometric authentication operation. The biometric authentication operation may be continued until the wearable terminal 3 and the smartphone 2 complete the acquisition of biometric information in S67, and the process of S76 is not limited to the process from S68 to S75.

  In S77, the smartphone 2 ends wireless communication with the wearable terminal 3 and turns off the BT function. In S78, the smartphone 2 ends the unlock application. With the termination of the unlock application, the user authentication process of the wearable terminal 3 is completed in S79. The process is continued from b in FIG. 7C, and a wearing state confirmation process of the wearable terminal 3 is executed.

<Effects of Second Embodiment>
In the second embodiment, the wearable terminal 3 compares the voice data such as the user's heart sound waveform acquired by the terminal with the voice data of the user acquired by another device such as the smartphone 2, Judge whether the user can be authenticated. As a result, even if the user's state changes immediately after exercise or poor physical condition, it is compared with the voice data acquired in the changed state in other devices, so the influence of the state change in user authentication Can be suppressed.

  Further, the user can unlock the wearable terminal 3 by a simple operation such as utterance or breathing with respect to the microphone 21a of the wearable terminal 3 and the microphone microphone 21b of the smartphone 2. For this reason, the convenience in the authentication process of the wearable terminal 3 is improved.

  Moreover, the wearable terminal 3 and the smart phone 2 can acquire audio | voice data using the existing microphone 21a and the microphone 21b. For this reason, there is no cost for installing a new device for acquiring audio data.

1, 3 Wearable terminal 2 Smartphone 10a, 10b Application LSI
11a, 11b CPU
12a, 12b RAM
13a, 13b Auxiliary storage devices 14a, 14b Network IC
15a, 15b Antenna 16 Heart rate sensor 17 Touch panel 171 Electrostatic sensor 18 Display 19 Camera 191 Optical sensor 20a, 20b Audio IC
21a, 21b Microphone

Claims (10)

The first device is
Obtaining the user's first biological information,
Receiving second biological information acquired from the user in a form that can be collated with the first biological information by a second device connected to the first device;
Comparing the first biological information and the second biological information;
Biometric authentication method. The first device authenticates the user when the compared first biological information and second biological information satisfy a predetermined condition.
The biometric authentication method according to claim 1. The first biological information and the second biological information include waveforms capable of comparing peak intervals,
The first device includes:
Authenticating the user when the interval between the peaks included in the first biological information matches the interval between the peaks included in the second biological information within a range of a predetermined tolerance;
The biometric authentication method according to claim 1 or 2. The first biological information and the second biological information include a waveform associated with time information,
The first device includes:
The user is authenticated when the peak time of the waveform included in the first biological information matches the peak time of the waveform included in the second biological information within a predetermined tolerance. The biometric authentication method according to claim 1 or 2. The first biological information and the second biological information are acquired by a voice input device.
The biometric authentication method according to any one of claims 1 to 4. The first device includes:
When receiving a notification that the acquisition of the second biological information is completed from the second device, the second device is requested to transmit the second biological information.
The biometric authentication method according to any one of claims 1 to 5. The first device includes:
When the signal amplitude obtained as the first biological information to be obtained is smaller than a predetermined threshold, the lock is set on the first device;
The biometric authentication method according to any one of claims 1 to 6. The first device includes:
When the user is not authenticated by comparing the first biometric information and the second biometric information, a means for prompting the user to input authentication information is presented.
The biometric authentication method according to any one of claims 2 to 7. The first device includes:
Performing a user authentication process when receiving a notification that a predetermined operation has been performed on the second device;
The biometric authentication method according to any one of claims 1 to 8. A biometric authentication device,
A sensor for acquiring the first biological information of the user;
A receiving unit that receives second biometric information acquired from the user in a form that can be collated with the first biometric information by another device connected to the biometric authentication device;
An authentication unit for comparing the first biometric information and the second biometric information;
A biometric authentication device.