WO2017145730A1 - Wearable device - Google Patents

Abstract

Provided is a wearable device that quickly outputs the result of a personal authentication without the user having to perform a personal authentication process every time. This wearable device 1 is equipped with: an authentication processing unit 57 that performs a personal authentication of a user U wearing the wearable device 1; a detection unit that detects the wearing state of the wearable device 1; a determination processing unit 59 that, on the basis of the wearing state detected by the detection unit, determines whether to validate or to invalidate the personal authentication result; and a control unit 50 that, when the user has been personally authenticated (operation P2) by the authentication processing unit 57 and the determination processing unit 59 has determined to validate the personal authentication result, omits the personal authentication by the authentication processing unit 57 and outputs the personal authentication result (a command RP1 in accordance with a command RQ1, a command RP2 in accordance with a command RQ2).

Description

[Name of invention determined by ISA based on Rule 37.2] Equipment

The present invention relates to a mounted device, a payment system, and a payment method.

Conventionally, as shown in Patent Document 1, a wearing device that is worn on a body such as a user's wrist and performs personal authentication using the user's biometric information has been known. In the mounting device, the personal authentication result is transmitted to the external device, and the user who has been personally authenticated can operate the external device.

JP 2006-48667 A

However, in the mounting device described in Patent Document 1, since user authentication processing is performed every time personal authentication is required, it is necessary to wait for the external device to wait for a personal authentication verification result. It was. In Patent Document 1, vein pattern matching is cited as an authentication method. However, when readjustment of a vein imaging position or the like occurs, the time required for authentication processing is not constant depending on the operation time of the user.
For example, scenes in which card information such as a credit card or debit card that requires personal authentication is output to an external device include payment of a toll at the exit of a toll road and payment of a train or bus boarding fee. In these scenes, it is necessary to perform payment processing promptly. However, the wearing device described in Patent Document 1 requires a considerable amount of time for personal authentication processing, and the time required for personal authentication processing is indefinite. Therefore, it has been difficult to use in applications such as these.

In addition, in the mounting device described in Patent Document 1, when the mounting device is released from the user's intention despite the handling of information that requires high security such as card information, the mounting device The function to prevent unauthorized use of was not considered.

Also, with conventional wearing devices, if you want other trusted users to use the result of the user's personal authentication as a proxy, for example, you can share one wearing device with your family, In cases where financial processing or the like is desired, or when a guardian or the like acts as a substitute for the guardian and performs processing of property or the like, the result of the personal authentication of the user cannot be used by other users. Therefore, it has been desired to provide a mounting device that can easily and safely entrust (inherit) the result of personal authentication of a user to a reliable agent.

The present invention has been made in order to solve at least a part of the above-described problems. During a period when the result of personal authentication is valid as information, the result of personal authentication is performed without performing user personal authentication processing again. It is to provide a mounting device that outputs.

It is another object of the present invention to provide a mounting device that can easily pass on the result of personal authentication of a user performed by the mounting device to an agent with easy processing.

Application Example 1 A mounting device according to this application example is a mounting device that can be mounted on a user, and an authentication unit that performs personal authentication of the user on which the mounting device is mounted, and mounting of the mounting device A detection unit that detects a state; a determination unit that determines whether the result of personal authentication is valid or invalid based on the wearing state detected by the detection unit; and If the determination unit determines that the result of the personal authentication is valid after the user is authenticated, the personal authentication by the authentication unit is omitted and the result of the personal authentication is output. And a control unit.

According to this application example, the mounted device determines whether the personal authentication result is valid or invalid based on the mounting state after the personal authentication is performed, and outputs the determined result. For example, it outputs that the result of personal authentication is valid during a period in which the wearing state continues after personal authentication. During this time, personal authentication is not performed each time.
Therefore, during the period when the result of personal authentication is valid, the result of personal authentication can be output without performing user personal authentication processing again.

Application Example 2 The mounting device further includes a receiving unit that receives a mounting release instruction for the mounting device, and a notification unit that stimulates a sense of a living body including at least one of visual, auditory, and tactile information. The control unit includes the notification unit in a case where the mounting state is not mounted by the detection unit when the user has not received the mounting release instruction from the receiving unit. It is characterized by announcing abnormality information.

According to this application example, when the mounted device is not mounted when the mounting release instruction is not received, abnormality information is notified.
Accordingly, the wearing device has a function of preventing unauthorized use of the wearing device when the wearing device is released against the user's intention.

[Application Example 3] The storage device further stores financial processing information that enables financial processing using at least one of a credit card function, a cash card function, a debit card function, and a net banking function. The control unit is determined to validate the result of the personal authentication by the determination unit after the user who has mounted the wearing device is authenticated by the authentication unit. In this case, the financial processing is executed, and when it is determined that the result of the personal authentication is invalid, the financial processing is not executable.

According to this application example, financial processing can be performed on a personally-equipped wearable device, and financial processing cannot be performed on a wearable device that has not been personally authenticated. This prevents impersonation by anyone other than the user.

Application Example 4 The mounting device further includes a mounting portion for mounting on the user, the mounting portion having an annular shape around the wrist of the user, An opening / closing part that opens and closes an annular shape is provided, and the detection part detects the attachment state as non-attachment when the opening / closing part is opened.

According to this application example, for example, the mounting unit may be a belt that mounts the mounting device on the wrist, and the opening / closing unit may be, for example, one that fixes the belt to the arm with a pin-back buckle. .

Application Example 5 The mounting device further includes a mounting portion for mounting on the user, the mounting portion having an annular shape around the wrist of the user, An adjustment unit that variably adjusts the circumferential length of the annular shape, and the detection unit detects that the mounting state is not mounted when the adjustment unit becomes longer by a predetermined length than the circumferential length of the mounting state It is characterized by doing.

According to this application example, the mounting unit is, for example, a bracelet that mounts a mounting device on the wrist, and the adjustment unit is, for example, a single-open type, both-holes that are mounted on the wrist with a variable ring-shaped circumference. What is fixed to the arm with a buckle such as a double lock type can be employed.

Application Example 6 The authentication unit acquires the user's biometric information and performs the personal authentication.

According to this application example, it is possible to identify an individual using the physical characteristics of the user based on the biological information.

[Application Example 7] The authentication unit performs the personal authentication based on a password entered by the user.

According to this application example, an individual can be identified by a personal identification number stored by the user.

Application Example 8 The authentication unit is connected to an authentication server via a computer communication network, and collates information acquired from the user with the user's unique information stored in the authentication server, It is characterized by performing authentication.

According to this application example, personal authentication can be performed by using abundant unique information stored in the authentication server. For example, the accuracy of personal authentication can be improved.

Application Example 9 The wearing device further includes a biological reaction information acquisition unit that detects a biological reaction of the user and acquires biological reaction information, and the determination unit uses the biological reaction information acquisition unit to detect the biological reaction. Whether to validate or invalidate the result of the personal authentication is determined based on information indicating whether or not the information is continuously detected.

According to this application example, it is possible to validate the result of personal authentication while the biological reaction information is continuously detected. That is, when there is no particular change in the biological reaction information, it is determined that the result of personal authentication is valid, so personal authentication is not performed each time.

Application Example 10 The wearing device further includes a timekeeping unit that measures time, a position information obtaining unit that obtains a position of the wearing device, and a living body that detects biological reaction of the user and obtains biological reaction information. And at least one of a reaction information acquisition unit, and the authentication unit, when the time is a predetermined time, when the position is out of a predetermined range, and when the biological reaction information has changed, The personal authentication of the user is performed in at least one of the cases.

According to this application example, when the biological reaction information is not continuously detected, the personal authentication can be performed and reconfirmed. Also, personal authentication can be performed when the predetermined time comes or when the position of the mounted device is out of the predetermined range. Even when wearing is continued, personal authentication is performed at the above-described timing, which can be used, for example, to prevent unauthorized use.

Application Example 11 The mounting device further includes a temporary reception unit that receives temporary mounting release of the mounting device, and the control unit receives the temporary mounting release from the personally authenticated user. In such a case, the authentication unit is allowed to perform simple personal authentication.

適用 According to this application example, when a user who has been personally authenticated wants to temporarily reattach the device, personal authentication can be performed with a simple operation.

[Application Example 12] The detection unit detects a contact pressure on the wrist of the user and detects the wearing state based on the contact pressure when the user wears the wrist.

According to this application example, it is possible to detect that the user himself / herself is wearing the wearing device based on the contact pressure reflecting the characteristics of the user's wrist.

Application Example 13 The mounting device further includes a power generating unit that generates power, and the mounting device is operated by power from the power generating unit.

According to this application example, since the mounting device includes the power generating unit that generates power, for example, it is possible to improve the normal operability in the mounted state.

Application Example 14 A wearing device according to this application example is a wearing device that can be worn by a first user and a second user, and the first user and the second user wearing the wearing device. An authentication unit that performs personal authentication of a person, a detection unit that detects a mounting state of the mounting device, and whether the result of the personal authentication is valid or invalid based on the mounting state detected by the detection unit A determination processing unit that performs information processing necessary for determining whether to perform, a control unit that outputs information based on a result of the personal authentication by the authentication unit, an inheritance reception unit that receives a right inheritance instruction of the mounted device, It is characterized by providing.

According to this application example, in the wearing device in which personal authentication of the first user and the second user is performed, the right is inherited between the first user and the second user by the inheritance receiving unit. Can do. For example, information based on the result of personal authentication of the first user (user) performed on the wearing device can be sent to the second user (agent) by an easy process such as receiving a right inheritance instruction from the first user. Can be used. At this time, safety can be improved by performing personal authentication of the second user.
Therefore, it is possible to provide a mounting device that can easily pass on the result of the personal authentication of the first user (user) performed by the mounting device to the second user (agent) with easy processing. it can.

Application Example 15 In the wearing device according to the application example 14, the wearing device further includes a notification unit that stimulates and informs a sense of a living body including at least one of visual, auditory, and tactile information. The control unit, when the personal authentication of the second user is performed by the authentication unit when the inheritance reception unit is not inheriting the right inheritance instruction from the first user, Non-inheritance information is notified by a notification unit.

According to this application example, the second user wearing the wearing device can acquire the non-inheritance information that the right is not inherited by the first user from the notification unit.

Application Example 16 In the mounting device according to Application Example 14 or 15, the mounting device further includes a storage unit that stores first user information related to the first user, and the control unit includes: When the inheritance acceptance unit accepts the right inheritance instruction from the first user to the second user, the authentication unit performs the personal authentication of the second user, and the determination process When the result of the personal authentication of the second user is determined to be valid by the unit, the first user information of the first user is output.

According to this application example, the wearing device that has been subjected to the personal authentication of the second user can output the first user information when inheriting a right inheritance instruction from the first user.

[Application Example 17] In the wearing device according to Application Example 16, the first user information includes My Number information, credit card information, cash card information, debit card information, and net banking information of the first user. It is characterized by including at least one of these.

According to this application example, the first user information can include the personal identification number of the first user and financial information.

[Application Example 18] In the wearing device according to any one of Application Examples 14 to 17, the authentication unit acquires biometric information of users including the first user and the second user, and the individual It is characterized by performing authentication.

According to this application example, it is possible to identify an individual using the physical characteristics of the user based on the biological information.

Application Example 19 In the wearing device according to Application Example 18, the authentication unit performs the personal authentication using a personal identification number input by the user.

According to this application example, the individual user can be identified by the password stored by the user.

Application Example 20 In the mounting device according to Application Example 18 or 19, the authentication unit is connected to an authentication server via a computer communication network, and information acquired from the user is stored in the authentication server. The personal authentication is performed by collating with the unique information of the user.

According to this application example, personal authentication can be performed by using abundant unique information stored in the authentication server. For example, the accuracy of personal authentication can be improved.

Application Example 21 In the mounting device according to any one of the application examples 18 to 20, the mounting device further includes a biological reaction information acquisition unit that detects a biological reaction of the user and acquires biological reaction information. The determination processing unit validates or invalidates the result of the personal authentication based on information on whether or not the biological reaction information is continuously detected by the biological reaction information acquisition unit. It is characterized by determining.

According to this application example, it is possible to validate the result of personal authentication while the biological reaction information is continuously detected. That is, when there is no particular change in the biological reaction information, it is determined that the result of personal authentication is valid, so personal authentication is not performed each time.

Application Example 22 In the mounting device according to any one of the application examples 18 to 21, the mounting device further includes a time measuring unit that measures time, a position information acquisition unit that acquires a position of the mounting device, A biological reaction information acquisition unit that detects biological reaction of the user and acquires biological reaction information, and the authentication unit has a predetermined range when the time is a predetermined time. The personal authentication of the user is performed in at least one of a case where the user is out of the range and a case where the biological reaction information is changed.

According to this application example, when the biological reaction information is not continuously detected, the personal authentication can be performed and reconfirmed. Also, personal authentication can be performed when the predetermined time comes or when the position of the mounted device is out of the predetermined range. Even when wearing is continued, personal authentication is performed at the above-described timing, which can be used, for example, to prevent unauthorized use.

Application Example 23 In the mounting device according to any one of Application Examples 14 to 22, the mounting device further includes a power generating unit that generates power, and the mounting device receives power from the power generating unit. It operates by.

According to this application example, since the mounting device includes the power generating unit that generates power, for example, it is possible to improve the normal operability in the mounted state.

[Application Example 24] The settlement system according to this application example uses the above-mentioned mounting device.

According to this application example, in the payment system, the right is transferred between the first user and the second user in the wearing device in which the first user and the second user are personally authenticated. Can do. For example, a payment process based on financial information owned by a first user who is personally authenticated by the mounting device can be performed by a second user who is inherited by the mounting device and personally authenticated.

[Application Example 25] The settlement method according to this application example can be worn by the first user and the second user, and can be worn by the first user and the second user. The first user wears the wearing device and performs the personal authentication, the first user inherits the right of the wearing device to the second user, and the second user However, by mounting the wearing device and performing the personal authentication, the second user can make a payment using the wearing device on behalf of the first user.

According to this application example, it is possible to provide a settlement method in which the second user can settle using the wearing device as a proxy for the first user.

Explanatory drawing showing the outline | summary of the utilization form of a mounting apparatus. The figure explaining the outline | summary of an authentication sequence. The block diagram which shows schematic structure of a mounting apparatus. The figure which shows an example of a personal information table. The figure which shows an example of registration authentication data. The figure which shows an example of result data. The flowchart which shows the flow of a main control process. The flowchart which shows the flow of an initial registration process. The flowchart which shows the flow of a mounting | wearing event process. The flowchart which shows the flow of a non-wearing event process. The flowchart which shows the flow of an authentication request process. The flowchart which shows the flow of a non-wearing event process. Explanatory drawing showing the outline | summary of the utilization form of a mounting apparatus. Explanatory drawing showing the outline | summary of an authentication sequence. The block diagram which shows schematic structure of a mounting apparatus. The figure which shows an example of a personal information table. The figure which shows an example of result data. The flowchart which shows the flow of a main control process. The flowchart which shows the flow of a mounting | wearing event process. The flowchart which shows the flow of an authentication request process. The flowchart which shows the flow of an inheritance event process. The figure which shows an example of an inheritance destination designation | designated screen. The figure which shows an example of an inheritance information designation | designated screen. Explanatory drawing showing the outline | summary of the utilization form of the mounting apparatus concerning a modification. Explanatory drawing showing the outline | summary of the utilization form of the mounting apparatus concerning a modification. Explanatory drawing showing the outline | summary of the utilization form of the mounting apparatus concerning a modification. Explanatory drawing showing the outline | summary of the utilization form of the mounting apparatus concerning a modification. Explanatory drawing showing the outline | summary of the utilization form of the mounting apparatus concerning a modification.

Hereinafter, embodiments of the present invention will be described with reference to the drawings. In the following drawings, the scale of each part and each screen is made different from the actual scale so that each part and each screen can be recognized.

(Embodiment 1)
FIG. 1 is an explanatory diagram showing an outline of a usage form of a mounted device.
The wearing device 1 is a terminal worn on the wrist of the user U as a user. The wearing device 1 incorporates a display unit 31 that performs various types of flexible display that can be deformed flexibly on a band 11 that is wound around the wrist, and a touch panel operation unit 37 that covers the display unit 31. The wearing device 1 shown in FIG. 1 is attached to the left wrist of the user U, and is provided with a display unit 31 and an operation unit 37 on the back B side of the hand, and a band 11 on the palm F side of the same left hand. An opening / closing part 12 to be mounted and fixed is provided. In addition, a control unit 50 that is a CPU (Central Processing Unit), a biometric information detection unit 20 that detects biometric information of the user U, and a communication unit 41 that transmits and receives various data through wireless communication are associated with the inside of the band 11. It is built in with the circuit to do.

The fee system 5 pays the fee for the service used by the user U based on financial processing information that enables financial processing such as card information such as cash card, credit card, and debit card and account information such as net banking. This is a fee system for processing (corresponding to financial processing). The fee system 5 is installed in a place where a fee is paid, and transmits a command RQ requesting card information to the mounted device 1 by wireless communication when the user U approaches. When receiving the command RQ, the mounted device 1 transmits a command RP including card information to the fee system 5 after the time T has elapsed.

In the mounted device 1, the card information of the user U is stored in the storage unit 70 (described later). The mounted device 1 needs to determine whether or not the card information can be transmitted to the fee system 5. That is, it is necessary to transmit the card information of the user U after obtaining confirmation that the person wearing the mounting device 1 is the user U (user U who uses the service). For this purpose, a personal authentication process for the user U is performed.
In addition, when the card information is requested from the fee system 5, the mounted device 1 needs to promptly transmit the card information.
For example, in the case of an ETC (registered trademark) (Electronic Toll Collection) system installed at the exit where the toll system 5 pays the toll for automobiles, the card information within a certain time so as not to stop the traveling car. To complete the payment process. In such a case, the mounting device 1 is a substitute for the vehicle-mounted device in which the existing ETC card and the ETC card are inserted. That is, transmission / reception of card information and the like by the mounted device 1 needs to be processed within a certain time that is transmitted / received by at least the existing vehicle-mounted device and the ETC card.
However, in the personal authentication process for the user U, the authentication process takes a considerable amount of time. For example, in the method based on vein pattern identification used in Patent Document 1, vein image capturing and pattern analysis processing are performed. Such processing requires time for imaging processing and pattern analysis processing. Even if there is technology that can be processed at high speed, if the user U needs to readjust the mounting position of the mounted device during the personal authentication process, the time spent for the process cannot be predicted and is undefined. is there.

In the wearing device 1, a person wearing the wearing device 1 in a certain period of time can depend on the user U without depending on the time required for the personal authentication process of the user U and the time for the operation performed during the personal authentication process by the user U The user U's card information and the like can be transmitted with the confirmation that the user U is obtained (with the result that the user U is personally authenticated).
Next, an outline of the realization method will be described.

FIG. 2 is a diagram for explaining the outline of the authentication sequence.
The sequence diagram shown in FIG. 2 shows a part of the operation (U) performed by the user U, the process of the control unit 50 of the mounted device 1 and the process of the charge system 5 along the time flow (from top to bottom). To) Moreover, although mentioned later for details, the control part 50 has the authentication process part 57 and the determination process part 59 as a function part.

When the user U wears the wearing device 1 (operation P1), the wearing device 1 performs personal authentication processing of the user U (authentication processing unit 57). In the personal authentication process, the vein pattern of the user U registered in advance in the wearing device 1 is collated with the vein pattern analyzed from the vein image captured by controlling the imaging sensor 21.

Here, the time required for the personal authentication process is time T1. Further, after the personal authentication process is completed (operation P2), a time period from the user U removing the mounted device 1 to unmounting (operation P3) is defined as time T2.

When the payment process 5A of the charge system 5 occurs during this time T2, the charge system 5 sends a command RQ1 for requesting card information for the payment process to the mounted device 1. In the mounted device 1, the determination processing unit 59 and the control unit 50 perform processing corresponding to the command RQ1, and transmit (answer) the command RP1 including the card information of the user U. At this time, the control unit 50 determines that the result of the personal authentication processing is valid without executing the personal authentication processing by the authentication processing unit 57, so that the person wearing the mounting device 1 can change the user U. The user U's card information is transmitted to the charge system 5 side. A processing time from when the control unit 50 receives the command RQ1 to when the command RP1 is returned is a time T3.

Furthermore, when another payment process 5B of the fee system 5 occurs during time T2, a command RQ2 requesting card information is transmitted to the mounting device 1. In the control unit 50 of the mounted device 1, the determination processing unit 59 transmits (answers) the command RP2 including the card information of the user U by the same processing as described above. A processing time from the reception of the command RQ2 by the control unit 50 until the reply of the command RP2 is defined as time T4. The payment process 5B is a process of the fee system 5, but may be a process of a system different from the fee system 5.

Here, the description will focus on the time required for each process. The time T1 is a time required for the personal authentication process, and includes the processing time for executing the imaging process and the pattern analysis process in the example described above. Further, when the vein pattern is not collated, the cause may be the influence of the deviation of the imaging position (vein position), so that it is necessary for the user U to adjust the mounting position of the mounting device 1 or the like. Become. Therefore, the time T1 requires an uncertain time in addition to at least the predetermined time required for the analysis of the personal authentication process. In the prior art, when a request for card information or the like is made from the fee system 5, a time T1 is required for replying each time.
On the other hand, the determination processing unit 59 that is processed during the time period T2 reads the content of the flag that stores whether the result of the personal authentication processing is valid or invalid, and determines the flag data. The processing steps are not indefinite and are fixed (details will be described later). That is, the time T3 and the time T4 are shorter than the time T1 and fixed time. On the charge system 5 side, the commands RP1 and RP2 can be acquired by waiting for an answer to the transmitted commands RQ1 and RQ2 for a predetermined time.
Hereinafter, the configuration of the mounting device 1 capable of obtaining such an effect will be described in detail below.

(Configuration of equipment)
FIG. 3 is a block diagram illustrating a schematic configuration of the mounted device.
The mounting device 1 includes a mounting unit 10, a biological information detection unit 20, a notification unit 30, an operation unit 37, a timing unit 39, a communication unit 41, a control unit 50, and a storage unit 70. The mounted device 1 is connected to the fee system 5 via the communication 7.

The mounting part 10 includes a band 11 and an opening / closing part 12.
As described above, the band 11 and the opening / closing part 12 are members that fix the mounting device 1 by winding it around the user's wrist in an annular shape.
The opening / closing part 12 is a buckle provided with a switch sensor. The buckle may be of any type such as a single opening type, a double hole type, a double lock type, or a pin back type. The switch sensor is provided in the opening / closing operation part of the buckle. In a state where the band 11 is fixed to the wrist, the switch is turned on and an ON signal is output from the opening / closing unit 12. When the band 11 is removed from the wrist, an OFF signal is output from the opening / closing unit 12. The ON / OFF signal output from the opening / closing unit 12 is output to the control unit 50.
The switch sensor may be disposed at an arbitrary position on the wrist side of the band 11 in a state where the band 11 is wound around the wrist. In this configuration, the switch is turned on by pressing the wrist while being attached to the wrist, and the switch is turned off when the switch is removed from the wrist. Moreover, it may replace with a switch sensor and may be a press sensor which detects pushing pressure value. In the case of a pressure sensor, pressure data can be output without being limited to an ON / OFF signal.

The biological information detection unit 20 includes an imaging sensor 21, a biological sensor 23, and the like.
The imaging sensor 21 is a light source and a CCD (Charge Coupled Device) sensor, and the light source and the CCD are disposed on the wrist side of the user in a state where the mounting device 1 is mounted on the wrist of the user. The irradiation light of the light source is irradiated to the user from, for example, an LED (Light Emitting Diode) light source that emits near infrared rays. The CCD generates an imaging signal (image signal) by photoelectrically converting the amount of received light reflected by a blood vessel covering the human body. A vein image signal is extracted from the generated image using the characteristic that reduced hemoglobin in venous blood easily absorbs near infrared rays. The extracted vein image signal is output to the control unit 50. The imaging sensor 21 may use a CMOS sensor.

The biological sensor 23 is a sensor such as a pulse wave sensor or a temperature sensor, and is disposed on the wrist side of the user, detects a biological reaction such as the user's pulse wave waveform and skin temperature, and outputs biological reaction information.
The pulse wave sensor has a light emitting element such as an LED and a light receiving element such as a photodiode. The light emitted from the light emitting element is reflected by the blood vessel of the user's wrist, and the reflected light is collected and received by the light receiving element. To do. At this time, the pulse wave sensor detects the pulse wave waveform of the user from the variation information of the amount of received light by using a phenomenon in which the reflectance of light is different between when the blood vessel is dilated and when it is contracted. The detected pulse wave waveform data is output to the control unit 50.
The temperature sensor is a known sensor that detects the temperature of the skin temperature of the wrist, the subcutaneous depth, or the like in contact or non-contact. The detected temperature signal is output to the control unit 50.

The notification unit 30 includes a display unit 31, a sound output unit 33, a vibration unit 35, and the like.
The display unit 31 is a display device capable of displaying characters and icons, and is, for example, a flexible dot matrix type EPD (Electrophoretic Display) that can be flexibly deformed as described above. Various information is displayed based on the display signal input from the control unit 50.
The sound output unit 33 includes a piezoelectric buzzer, a piezoelectric vibrator, a piezoelectric speaker, and the like, and is a sound output device that performs various notifications based on an output signal input from the control unit 50.
The vibration unit 35 is a piezoelectric vibrator or a micro vibration motor, and is driven based on a signal input from the control unit 50 to vibrate the mounting device 1.

The operation unit 37 is an input device configured to include a touch sensor, a touch panel, or the like that covers the display surface of the display unit 31, and detects a touched part by a method such as a capacitance method or a resistance film method. A detection signal is output to the control unit 50. Note that the configuration of the operation unit 37 is not limited to this, and any configuration that allows a plurality of operation inputs may be used. The operation unit 37 includes an acceleration sensor, acquires an acceleration signal, and generates each acceleration signal generation pattern. A configuration in which an operation by a user is analyzed and output to the control unit 50 as an operation signal may be employed. According to this configuration, for example, when a part of the mounted device 1 is tapped three times by the user, an operation of detecting the acceleration signal and switching between a mode in which the payment processing 5A and the like may be accepted and a mode in which the payment processing 5A is not accepted is performed. Can be realized.

The timekeeping unit 39 is a real-time clock and has timekeeping functions such as a timer function, a calendar function, and a clock function. Time data such as the date and time that the time measuring unit 39 is measuring is read by the control unit 50.

The communication unit 41 is a short-range wireless adapter with reduced power consumption as a preferred example, such as a terminal such as a fee system 5, a register terminal, an ATM (Automated Teller Machine), various fee payment machines, a PC (Personal Computer), a smartphone. Various data such as (multi-function mobile phone) are connected so that various data can be communicated. The short-range wireless adapter only needs to be equipped with a method that is common to the method used in a system that requires payment processing. For example, a Bluetooth (Bluetooth) adapter, a system that performs payment processing is ETC, etc. If there is, a 5.8 GHz band active DSRC (Dedicated Short-Range Communication) may be used. When the communication unit 41 receives various data from an external device such as the fee system 5, the communication unit 41 outputs the received data to the control unit 50. For example, when a command RQ requesting card information is received from the fee system 5, the command RQ is output to the control unit 50, and transmitted to the fee system 5 when a command RP or the like transmitted from the control unit 50 is input. To do.
The communication unit 41 is equipped with IP (Internet Protocol) as a public wireless LAN adapter, and can communicate with various servers of the Internet and intranets and other IoT (Internet of Things) devices via a network as a computer communication network. May be connected.
The communication unit 41 communicates with an external device that communicates using a common protocol. In these protocols, a known encryption method is applied, and the security of data transmitted and received Is secured.

(Control part)
The control unit 50 includes a processor such as a CPU or a DSP (Digital Signal Processor), and is a control device and an arithmetic device that collectively control each unit of the mounted device 1. The control unit 50 realizes various functions of the mounted device 1 according to various programs including a control program (not shown) stored in the storage unit 70.
The control unit 50 includes a detection processing unit 52, a request detection processing unit 56, an authentication processing unit 57, a determination processing unit 59, a reception processing unit 61, and a notification processing unit 63 as main functional units. The functions of the mounted device 1 are realized by comprehensive control by the event processing unit 67. Further, the control unit 50 executes the function of the initial registration unit 65 before the above-described function unit is realized.

The initial registration unit 65 performs initial registration of a user who uses the mounted device 1. Specifically, the initial registration unit 65 controls the operation unit 37 and the display unit 31 to acquire information such as user personal information and card information. The acquired information is stored in the storage unit 70 as a personal information table 72 (FIG. 4). At the time of storage, the control unit 50 generates a UID (User Identification) for identifying the user and manages it as user information.

Here, the personal information table 72 will be described with reference to FIG. FIG. 4 is a diagram illustrating an example of the personal information table. In the personal information table 72, a column 72A, a column 72B, a column 72C, a column 72D, a row 72G, a row 72H, a row 72J, and a row 72K are shown. The column 72A stores the UID. The column 72B stores service types, the column 72C stores card numbers, and the column 72D stores incidental information. The row 72G indicates that the credit card service of the user whose UID is “0001” is “A card”, the card number is “01234567890123456789”, and the incidental information is “012”. The row 72H indicates that the personal information type of the user “0001”, which is the same as the row 72G, is “My Number” and the number is “000011112222”. In the row 72J and the row 72K, information of the user having the UID “0002” is stored in the same format as the UID “0001”.

Personal information is, for example, information such as my number, name, age, and address, and can be transmitted when requested by the fee system 5 or another system. The card information is, for example, a credit card number, a debit card number, a cash card number, or the like, and a security code, a password, or the like is stored as incidental information as necessary.

The initial registration unit 65 controls the operation unit 37 and the display unit 31 to prompt the user to wear the wearing device 1, and after the user wears the wearing device 1, biometric information that identifies the individual user is detected. As a suitable example, the biological information is a vein image signal with high individual identification accuracy. The initial registration unit 65 controls the biological information detection unit 20 to acquire a vein image signal. The feature point data of the vein pattern is calculated from the acquired vein image signal by applying known processing such as image binarization processing, thinning processing, feature point extraction, and the like. The feature point data includes, for example, a plurality of feature point data such as the interval and number of branch points of the vein pattern, the length and shape between the branch points, and the depression angle at the branch point. When the initial registration unit 65 calculates the feature point data of the user, it is associated with the user's UID and stored in the storage unit 70 as registration authentication data 81 (FIG. 5).

Here, the registration authentication data 81 will be described with reference to FIG. FIG. 5 is a diagram illustrating an example of registration authentication data. In the registration authentication data 81, a column 81A and a column 81B are shown. The column 81A stores the UID. Column 81B stores vein pattern feature point data. In the first line of the registration authentication data 81, feature point data with a UID “0001” is stored as “feature point data A”. The feature point data A is a numerical data group representing feature points. There may be a plurality of numerical data groups. In the second row, feature point data having a UID “0002” is stored as “feature point data B”.

Although the initial registration operation by the initial registration unit 65 is performed by controlling the operation unit 37 and the display unit 31, it communicates bidirectionally with other PCs and smartphones via the communication unit 41, Information such as user personal information and card information may be input on the smartphone side. The mounting device 1 may be configured to receive such information and store it in the storage unit 70.

The event processing unit 67 sets a mechanism for controlling each functional unit in the event driving method in the control unit 50, and starts an event processing loop. The various events include an event that detects the mounting of the mounting device 1 (mounting event IV1), an event that detects that the mounting device 1 is unmounted (non-mounting event IV3), and an event that receives a payment request from the fee system 5 (payment request). Event IV5). In the event processing loop, when these events occur, the process moves to an event handler (not shown) set for each event type. The event handler is a function in which processing corresponding to each event is described, and executes each functional unit as necessary to realize processing corresponding to the event. The flow of this process will be described later with reference to the flowcharts shown in FIGS.

The detection processing unit 52 includes an attachment detection unit 53 and a non-attachment detection unit 55.
The wearing detection unit 53 detects that the wearing device 1 is worn on the user's wrist, and notifies (outputs) the occurrence of the wearing detection event to the event processing unit 67. Specifically, the mounting detection unit 53 monitors an ON / OFF signal output from the mounting unit 10. When the signal changes from OFF to ON, the mounting event IV1 is output.
When the mounting event IV1 is notified to the event processing unit 67, the processing is moved to the event handler by the notification. In this event handler, the function of the authentication processing unit 57 is realized, and it is determined whether or not the user wearing the wearing device 1 is a user registered in advance by the initial registration unit 65. Details of the determination method will be described later in the authentication processing unit 57. If it is determined that the user is a registered user, the user's UID is stored in the result data 85 (FIG. 6).

Here, the result data 85 will be described with reference to FIG. FIG. 6 is a diagram illustrating an example of the result data. In the result data 85, a column 85A, a column 85B, a column 85C, and a column 85D are shown. In column 85A, “0001” indicating a user who has been personally authenticated in “UID” is displayed, in column 85B “1” indicating that the verification result is matched with “matching result”, and in column 85C “matching time” Is stored in the column 85D, and “valid flag” is stored with “1” indicating that the content of the verification result is valid.
If it is determined that the user is not registered, the UID stored in the column 85A of the result data 85 is deleted and becomes “NULL” data (for example, “−1”), and the other column 85B , 85C, 85D are also initialized to “NULL”.
In this manner, when the user who wears the wearing device 1 is personally authenticated by the event handler of the wearing event IV1, the result data 85 includes the UID, the matching result “1”, and the valid flag “1”. If stored and the user is not personally authenticated, the result data 85 is initialized.

The non-wearing detection unit 55 detects that the wearing device 1 has been removed from the user's wrist, and notifies (outputs) the occurrence of the non-wearing event IV3 to the event processing unit 67. Specifically, the non-mounting detection unit 55 monitors an ON / OFF signal output from the mounting unit 10. When the signal changes from ON to OFF, a non-wearing event IV3 is output.
When the non-wearing event IV3 is notified to the event processing unit 67, the processing is moved to the event handler by the notification. In this event handler, the valid flag in the column 85D (FIG. 6) of the result data 85 is updated to “0”. The validity flag “0” indicates that the user wearing the wearing device 1 has not been personally authenticated (invalidated).
The detection processing unit 52 and the biological information detection unit 20 correspond to a detection unit that detects the wearing state.

The request detection processing unit 56 monitors the reception data of the communication unit 41, and notifies (outputs) the payment request event IV5 to the event processing unit 67 when the received data is information requesting card information. The request detection processing unit 56 manages information such as a payment processing system (such as the fee system 5), a card company, and a service that can accept payment processing by the mounted device 1 and the user. These pieces of information are stored in advance in the storage unit 70 as a request acceptance source list (not shown). Note that the content of the request reception source list is updated based on information distributed from the information source via the network.
In the request detection processing unit 56, it is determined whether or not the received data received from the communication unit 41 is data included in the request receiving source list. IV5 is output to the event processing unit 67.

When the payment request event IV5 is notified to the event processing unit 67, the processing is moved to the event handler by the notification. In this event handler, the determination processing unit 59 is executed to determine whether the personal authentication of the user wearing the wearing device 1 is valid or invalid. If the user personal authentication is valid, an answer corresponding to the received data is generated and transmitted to the fee system 5 via the communication unit 41. The answer corresponding to the received data is, for example, information including card information if the received data is information requesting card information. In addition, since the content of the received data and the transmission / reception procedure depend on the agreement of the card company and the service, the content and the transmission / reception procedure corresponding to each company and service are applied.

The authentication processing unit 57 performs personal authentication processing when the mounting device 1 is mounted by the user. The authentication processing unit 57 is a functional unit that is implemented by being called from an event handler that is executed by notification of the mounting event IV1. The authentication processing unit 57 controls the biological information detection unit 20 (imaging sensor 21) to acquire a vein image signal as biological information. The feature point data of the vein pattern is calculated from the acquired vein image signal. For this processing, the same processing as that performed by the initial registration unit 65 is used. That is, by applying image signals having the same vein configuration to the initial registration unit 65 and the authentication processing unit 57, the same feature point data is calculated from each. The authentication processing unit 57 stores the calculated feature point data as acquired authentication data 83 in the storage unit 70.

The authentication processing unit 57 collates the feature point data of the registration authentication data 81 registered by the initial registration unit 65 with the feature point data of the acquired authentication data 83. For the collation, for example, determination based on the correlation between the two feature point data groups is used, and a correlation coefficient is calculated. If the correlation coefficient is greater than or equal to a predetermined value, it is determined that there is a strong correlation and the matching results match.
The authentication processing unit 57 controls the operation unit 37 and the display unit 31 to mount the mounting unit 10 or the like of the mounting device 1 when the correlation coefficient calculated from the collation result is less than the predetermined value. The user is prompted to adjust the position, finely adjust the position captured by the image sensor 21, etc., and repeat the above collation process. As a result of repeating the collation process a predetermined number of times or more, if the correlation coefficient is less than the predetermined value, the collation result is determined as a mismatch. In the authentication processing unit 57, since such processing depends on the operation of the user, the time until the result that the collation result matches is obtained (until the personal authentication is performed) is not constant but indefinite. is there.

Further, the authentication processing unit 57 may control the operation unit 37 and the display unit 31 to input a personal identification number known only by the user, an arbitrary character, or a figure. The personal identification number, arbitrary characters and figures are compared and collated with the personal identification number registered in the storage unit 70 of the wearing device 1 in advance. Moreover, you may perform comparison collation combining these methods and the collation by the above-mentioned biometric information.
Further, the authentication processing unit 57 may control the communication unit 41 to connect to an authentication server installed in the computer communication network. The authentication server stores user-specific unique information in advance. The unique information may be any information as long as it is information set by the user. For example, information such as the above-described biometric information, personal identification number, arbitrary characters and figures, and questions and answers set in advance by the user may be used. In the authentication processing unit 57, the information acquired from the user wearing the mounted device 1 is checked against the unique information stored in the authentication server, and a match or mismatch is determined. Further, the personal authentication by the authentication server may be executed redundantly with the above-described collation by the biometric information or the password.
Note that the authentication processing unit 57 corresponds to an authentication unit.

When the determination processing unit 59 receives a payment request from a payment processing system such as the fee system 5, the determination processing unit 59 determines whether the personal authentication of the user wearing the mounting device 1 is valid or invalid. The determination processing unit 59 is a functional unit that is implemented by being called from an event handler that is executed by notification of the payment request event IV5. The determination processing unit 59 refers to the result data 85 and outputs a determination result by the following (procedure 1) to (procedure 3).
Data of the result data 85 is read into an internal variable. ... (Procedure 1)
It is determined that the column 85A (UID) is not “NULL”. ... (Procedure 2)
It is determined whether the column 85B (collation result) is “1” and the column 85D (valid flag) is “1”. ... (Procedure 3)
Procedure 1 is a process for reading from the storage unit 70 into an internal variable, Procedure 2 is a process for comparing an internal variable with a numerical value, and if Procedure 2 is established, the procedure proceeds to a process of Procedure 3. In Procedure 3, a comparison is made between an internal variable and a numerical value. The process is processed twice. When the procedure 3 is established, it is determined that the user's personal authentication is valid. When the procedure 2 or the procedure 3 is not established, it is determined that the user's personal authentication is invalid.
In this way, the processing steps for realizing the procedures 1 to 3 can be realized with a fixed number of steps, and the processing time can be calculated based on the CPU processing speed (MIPS (Million instructions per second)) and is constant. is there.
The determination processing unit 59 corresponds to a determination unit.

The reception processing unit 61 and the notification processing unit 63 are functional units that function as a pair. The reception processing unit 61 controls the operation unit 37, the notification unit 30, and the like, and receives a mounting release instruction. In the notification processing unit 63, when the mounted device 1 is removed (not mounted), the result of personal authentication becomes invalid, and when an instruction to release the mounting is not accepted, a warning sound such as an alarm is output. . With this configuration, when the user removes the mounting device 1 without issuing a mounting release instruction, the user is warned that an unintentional removal action has been performed.

Specifically, the mounting release instruction is a predetermined operation that the user operates on the mounting device 1. The predetermined operation is an operation performed in a state where the user wears the wearing device 1 on the wrist, for example, an operation of inputting a simple password. The reception processing unit 61 determines whether or not a predetermined operation has been established when a predetermined operation corresponding to the mounting release instruction is performed. For example, when inputting a simple password, it is determined whether or not the password matches a password set in advance in the storage unit 70. When the predetermined operation is established, the mounting release flag (not shown) stored in the storage unit 70 is set to “ON” (indicating that mounting can be released). The mounting release flag is “OFF” (indicating that mounting cannot be released) when the authentication processing unit 57 is called in the event handler of the mounting event IV1 in which the mounting device 1 is mounted and personal authentication is performed. Set to

When the non-mounting event IV3 is notified to the event processing unit 67 in a state where such a mounting release flag is set, the event handler executed by the notification causes the column 85D (see FIG. The validity flag of 6) is updated to “0”. That is, the result of personal authentication is invalid. This event handler activates the notification processing unit 63 after the processing.
The notification processing unit 63 reads the contents of the mounting release flag. If the mounting release flag is not “ON” (including “OFF”), the notification processing unit 63 specifies the volume to the sound output unit 33 and outputs a warning sound. The volume of the warning sound is a volume that stimulates an unspecified number of hearings, and the warning sound may be an alarm sound or an audio signal such as “the mounted device 1 has been stolen”. A display signal indicating a warning may be output to the display unit 31. In that case, a display that stimulates an unspecified number of sights such as blinking the display unit 31 is preferable. Further, a vibration signal may be output to the vibration unit 35. In that case, it is preferable that the vibration amount of the vibration unit 35 is increased, and if a person other than the user takes away the wearing device 1, it is difficult to wear by stimulating the sense of touch. Moreover, the structure (it abbreviate | omitted illustration) which outputs electrical stimulation to the site | parts of human bodies, such as skin, may be the structure which stimulates the tactile sense of an output site strongly. The flow of this process will be described later with reference to FIG.
When the above-described mounting release flag is not “ON”, it corresponds to a non-acceptance time, and a warning sound, an alarm sound, a display signal indicating a warning, and a vibration signal correspond to abnormality information. The reception processing unit 61 corresponds to a reception unit, and the notification processing unit 63 corresponds to a notification unit.

The storage unit 70 is configured by a storage device such as a ROM (Read Only Memory), a flash ROM, a RAM (Random Access Memory), an FeRAM (registered trademark) (Ferroelectric RAM), and the like. Various programs (not shown) including the control program, data, and the like are stored. In addition, it has a work area for temporarily storing data being processed, variables, flag values, processing results, and the like of various processes.
The storage unit 70 stores a personal information table 72, registration authentication data 81, acquisition authentication data 83, result data 85, and the like.
The personal information table 72 includes personal information data 73 and card information data 75. The personal information data 73 and card information data 75 of the user including the user stored by the initial registration unit 65 as described above are stored. Yes.
The registration authentication data 81 stores feature point data of users including users registered by the initial registration unit 65 as described above.
The acquired authentication data 83 stores the feature point data calculated by the authentication processing unit 57 as described above.
As described above, the result data 85 stores the UID of the user who is personally authenticated by the mounted device 1, the collation result, the collation time, and the valid flag.

Note that the mounting device 1 may be provided with a power generating unit (not shown). The power generating unit included in the mounting device 1 generates power for operating the mounting device 1. The control unit 50 operates with power from the power generation unit and processes various types of information. In addition, each unit such as the mounting unit 10, the biological information detection unit 20, the notification unit 30, the operation unit 37, the timing unit 39, the communication unit 41, and the storage unit 70 controlled by the control unit 50 is also operated by power from the power generation unit. To do. The power generation of the power generation unit may be realized by solar power generation (solar cell), or may be expressed by vibration power generation, manual winding power generation, temperature difference power generation, or the like.

Further, the power supplied to the mounting device 1 by the power generating unit is not necessarily limited to the power generated by the power generation. For example, if the battery can be set to be unnecessary for one year or longer, the power supplied to the wearing device 1 may be power from a button battery or a similar battery built in a normal watch (watch). Moreover, the electric power expression part may be a rechargeable secondary battery that can be charged by a non-contact or charging terminal.

(Main control processing flow)
FIG. 7 is a flowchart showing the flow of the main control process. Hereinafter, description will be made with reference to FIG. The following flow is a flow of main control processing. The control unit 50 controls the mounting unit 10 and the biological information detection unit 20 based on a control program (not shown) stored in the storage unit 70. It is executed by controlling each part to be included.

Step S10 performs an initial registration process. This process will be described in detail in the flow shown in FIG. When the initial registration process is executed, user information is stored in the personal information table 72 and the registration authentication data 81.

Step S20 registers event processing. Define various events required for event-driven programming, and set event handlers corresponding to each event to be activated. Here, events such as a mounting event IV1, a non-mounting event IV3, and a payment request event IV5 used in subsequent steps are defined, and event handlers corresponding to the respective events are set.

Step S30 is an event processing loop. Each event handler (steps S40, S50, S60) is executed in response to the occurrence of various events. Events are queued and event handlers are executed in the order in which each event occurs (some emergency events have priority). When the event handler process is completed, the process returns to this step and waits for an event to occur.

Step S40 is an event handler that is processed when the event of the mounting event IV1 occurs. Details of the processing will be described in the flow shown in FIG. When this process is executed, the acquisition authentication data 83 is generated, and the result of matching the registration authentication data 81 and the acquisition authentication data 83 is stored in the result data 85.

Step S50 is an event handler that is processed when an event of the non-wearing event IV3 occurs. Details of the processing will be described in the flow shown in FIG. When this process is executed, it is recorded that the collation result of the result data 85 is invalid.

Step S60 is an event handler that is processed when the payment request event IV5 event occurs. Details of the processing will be described in the flow shown in FIG. When this processing is executed, if the collation result of the result data 85 matches and is valid, card information and the like are transmitted.

(Initial registration process flow)
FIG. 8 is a flowchart showing the flow of the initial registration process. This flow is a detail of the process of step S10 of the main control process shown in FIG.

In step S110, personal information is registered. The personal information data 73 and card information data 75 of the user who uses the mounted device 1 are acquired and stored in the personal information table 72.
In step S120, a captured image is acquired. The imaging sensor 21 is controlled to acquire a user's vein image.
In step S130, authentication data is generated and registered. The feature point data of the vein pattern is calculated from the vein image and registered (stored) in the registration authentication data 81. The feature point data registered in the registration authentication data 81 is feature point data for identifying the individual of the user.

(Installation event processing flow)
FIG. 9 is a flowchart showing the flow of the mounting event process. This flow is the details of the process of step S40 of the main control process shown in FIG.

In step S210, a captured image is acquired. Specifically, the imaging sensor 21 is controlled to acquire a user's vein image.
In step S220, authentication data is generated and stored. The feature point data of the vein pattern is calculated from the vein image and stored in the acquisition authentication data 83.
In step S230, the acquisition authentication data 83 and the registration authentication data 81 are collated. Specifically, the feature point data stored in the acquisition authentication data 83 is compared with the feature point data stored in the registration authentication data 81. Specifically, a correlation coefficient between both feature point data groups is calculated.
In step S240, it is determined whether or not the collation results match. Specifically, if the correlation coefficient calculated in step S230 is greater than or equal to a predetermined value, it is determined that the collation results match (Yes), and the process proceeds to S250. If the correlation coefficient is less than the predetermined value, the collation result is one. It determines with having not done (No) and progresses to S260. If feature point data of a plurality of users are registered in the registration authentication data 81, the feature point data of the registration authentication data 81 is switched for each user, and the processes in steps S230 and S240 are repeated.
In step S 250, the matching UID of the registration authentication data 81 is stored in the result data 85. Specifically, in step S240, a UID having feature point data with the matching result matched is acquired from the registration authentication data 81, and the UID, the matching result “1”, the matching time, and the validity flag “1” are stored in the result data 85. .
In step S260, the result data 85 is initialized. Specifically, the UID information stored in the result data 85 is deleted. Specifically, the UID information is updated to “NULL”, and the verification result is changed to “0”, the verification time is changed to “NULL”, and the valid flag is “0”. Since the result data 85 is referred to by the event handler (step S60, steps S410 to S450) of the payment request event IV5, when the user who wears the wearing device 1 is not registered in advance by such initialization, It is guarded so that card information is not transmitted.

(Non-wearing event process flow)
FIG. 10 is a flowchart showing the flow of the non-wearing event process. This flow is a detail of the process of step S50 of the main control process shown in FIG.

In step S310, data is written to the result data 85. Specifically, when the UID exists in the result data 85 (not “NULL”), the valid flag is changed to “0”. That is, the result of personal authentication is invalid.
The contents of the validity flag of the result data 85 are referred to by the event handler of the payment request event IV5. When the validity flag is not “1”, the card information is not transmitted. That is, by this step, the card information is controlled not to be transmitted when the mounted device 1 is not mounted.
FIG. 12 is a flowchart showing the flow of the non-wearing event process as in FIG.
FIG. 12 shows a flow of event processing when referring to the mounting release instruction after the processing performed in FIG. Specifically, this is a flow to be processed when the above-described function of the reception processing unit 61 is realized and the mounting release flag is set to “ON” or “OFF”.
Step S510 is the same flow as step S310.
In step S520, it is determined whether there is a mounting release instruction. Specifically, when the mounting release flag is “ON” (Yes), this flow is terminated, and when the mounting release flag is not “ON” (No), the process proceeds to step S530.
In step S530, an alert sound is generated and a warning is given.
According to such a flow, in the reception processing unit 61, when the mounting release flag is not set to “ON” and the mounting device 1 is not mounted (removed), an alert sound is generated and a warning is urged. be able to.

(Authentication request processing flow)
FIG. 11 is a flowchart showing the flow of the authentication request process. This flow is the detail of the process of step S60 of the main control process shown in FIG.

In step S410, the result data 85 is read. Specifically, the content of the result data 85 is read into an internal variable. The UID, verification result, verification time, and valid flag are read.

In step S420, it is determined whether or not data exists in the result data 85. Specifically, if the UID is not “NULL”, it is determined that there is data (Yes), and the process proceeds to step S430. If the UID is “NULL”, it is determined that there is no data (No). Proceed to step S450.

In step S430, it is determined whether or not the collation result is “1” and the valid flag is “1”. If the collation result is “1” and the valid flag is “1” (Yes), the process proceeds to step S440. If either the collation result or the valid flag is not “1” (No), step S450 is performed. Proceed to

In step S440, card information is transmitted. Specifically, the card information of the UID number read in step S410 is acquired with reference to the personal information table 72. The acquired card information is transmitted to the fee system 5 via the communication unit 41.

In step S450, an NG (No good) response is transmitted. Specifically, an NG response indicating that the card information cannot be transmitted is transmitted to the fee system 5 via the communication unit 41.

In step S440 and step S450, the card information and the NG response are transmitted. Actually, however, the information is variously changed in both directions based on the communication method, communication procedure, and transmission / reception data specifications determined in advance in the mounted device 1 and the charge system 5. Information is being sent and received. Security measures such as encryption are also taken.

As described above, when each flow shown in FIGS. 7 to 11 is processed, when a payment request is received from the fee system 5 via the communication unit 41, the payment request event IV5 is notified and the corresponding event handler. Card information is transmitted by the processing of the authentication request processing (steps S60, S410 to S450). At this time, if the collation result and the valid flag are both “1” (step S430), the card information is transmitted (step S440). The collation result “1” indicates that the wearing user has been personally authenticated, and the valid flag “1” indicates that the state continues. The contents of the collation result and the valid flag are set by the mounting event process (step S40) and the non-wearing event process (step S50) that are processed at a timing different from the authentication request process. Accordingly, in the authentication request process, after receiving the payment request, the result of the authentication process can be determined by processing the steps S410, S420, and S430. Steps S410, S420, and S430 are simple memory access and numerical value comparison processing. User operation with non-constant processing time, generation of authentication data that requires time for processing (step S220), and comparison and collation of feature point data The process (step S230) is not included. In this way, after receiving the payment request, the result of personal authentication of the user wearing the wearing device 1 is output in limited steps such as steps S410, S420, and S430.

As described above, in the mounting device 1 according to the present embodiment, the following effects can be obtained.
The mounting unit 10 and the detection processing unit 52 detect the mounting state of the mounting device 1. Specifically, the mounting event IV1 is output when the mounting device 1 is mounted, and the non-mounting event IV3 is output when the mounting device 1 is not mounted.
When the mounting event IV1 is output, the event handler calls the authentication processing unit 57 to perform personal authentication processing of the user wearing the mounting device 1. When the personal authentication is performed, the user UID is stored in the result data 85. Using the UID, card information, personal information, and the like of a user registered in advance in the mounting device 1 can be extracted. Further, the result data 85 stores “1” indicating that the personal authentication is performed and “1” indicating that the result of the personal authentication is valid and “1” indicating that the result of the personal authentication is valid.
When the non-wearing event IV3 is output, the event handler sets the valid flag of the result data 85 to “0”. This indicates that the result of personal authentication is invalid.
The request detection processing unit 56 monitors the communication unit 41. When the received data received from the external device is information requesting payment processing such as the fee system 5, a payment request event IV5 is output.
When the payment request event IV5 is output, the event handler calls and executes the determination processing unit 59. The determination processing unit 59 determines whether personal authentication is valid or invalid. The determination is realized by the procedure 1 to the procedure 3 in which the information of the result data 85 is read and the comparison result is compared with the contents of the valid flag. At this time, the authentication processing unit 57 is not called. In other words, after requesting payment processing, the fee system 5 side obtains a response in a simple and fixed processing time such as steps 1 to 3 without waiting for the processing time and indefinite time spent on the personal authentication processing. can do.
Therefore, when a payment request is made from the fee system 5, the mounting device 1 can determine the collation result without performing the personal authentication process, and can promptly process the response to the payment request.
In addition, when the mounted device 1 is removed by the reception processing unit 61 and the notification processing unit 63 of the mounted device 1 without receiving the mounting release instruction, the result of personal authentication is invalidated and a warning sound is output. Can do. Therefore, when the wearing device 1 is released from the user's intention, unauthorized use of the wearing device 1 can be prevented.

(Embodiment 2)
Embodiment 2 of the present invention will be described below with reference to the drawings. In the description of the present embodiment, the same components as those in the first embodiment described above are denoted by the same reference numerals, and the description thereof may be omitted or simplified here.
FIG. 13 is an explanatory diagram showing an outline of a usage form of a mounted device. FIG. 14 is an explanatory diagram showing an outline of the authentication sequence.
The wearing device 101 is a terminal worn on the wrist of the user U1 as the first user and the user U2 as the second user (or agent). The wearing device 101 includes a display unit 31 that performs various types of flexible types that can be flexibly deformed around a band 11 that is wound around the wrist, and a touch panel operation unit 37 that covers the display unit 31. The wearing device 101 shown in FIG. 13 is attached to the left wrists of the users U1 and U2, and is provided with a display unit 31 and an operation unit 37 on the back B side of the hand, and a band 11 on the palm F side of the same left hand. An opening / closing part 12 is provided to be attached and fixed to the wrist. Further, inside the band 11, a control unit 150, which is a CPU (Central Processing Unit), a living body that detects biological information of a user (hereinafter simply referred to as a user when the user U1 and the user U2 are not distinguished). An information detection unit 20 and a communication unit 41 that transmits and receives various data by wireless communication are incorporated together with related circuits. A user corresponds to a user.

The fee system 5 is based on financial information that enables financial processing such as card information such as cash cards, credit cards, and debit cards, and account information such as net banking. This is a fee system. The fee system 5 is installed at a place where the fee is paid, and when the user U1 or the user U2 wearing the attached device 101 approaches, transmits a command RQ requesting card information or the like to the attached device 101 by wireless communication. When receiving the command RQ, the mounted device 101 transmits a command RP including card information according to the request to the fee system 5.
The mounted device 101 and the fee system 5 correspond to a payment system.

The mounted device 101 stores the card information of the user U1 in the storage unit 170 (described later). The mounted device 101 has a function of entrusting payment processing to the user U2 who is another user with the card information of the user U1 when the user U1 cannot perform payment processing to the fee system 5 for some reason. Examples of the relationship between the user U1 and the user U2 include a relationship in which the user U2 is a guardian of the user U1, and a relationship in which the user U2 is a court agent in all matters relating to the property of the user U1. However, the user U2 is not limited to such a case, and may be a third party trusted by the user U1. In addition, the fee system 5 described above is not limited to financial processing, and may be another system as long as it is a system that requires identity verification. For example, a system that issues or delivers a ticket or an article reserved by the user U1 after confirming the identity, or a system that provides documents or information related to the user U1 after confirming the identity.

The inheritance process of the mounted device 101 and the authentication process with the charge system 5 will be described with reference to FIG. FIG. 14 is a diagram for explaining the outline of the inheritance and authentication sequence.
The sequence diagram shown in FIG. 14 shows the time for the mutually linked portions in the operation (U1) by the user U1, the operation (U2) by the user U2, the processing of the control unit 150 of the mounted device 101, and the processing of the fee system 5. Represents along the flow (from top to bottom). Note that the processing method shown in this sequence corresponds to a settlement method. Although details will be described later, the control unit 150 includes an authentication processing unit 57, an inheritance processing unit 69, a request detection processing unit 56, and a determination processing unit 159 as functional units.

When the user U1 wears the wearing device 101 (operation P11), the wearing device 101 performs personal authentication processing of the user U1 (authentication processing unit 57). In the personal authentication process, the vein pattern of the user U1 registered in advance in the wearing device 101 and the vein pattern analyzed from the captured image of the vein imaged by controlling the imaging sensor 21 are collated. Note that performing the personal authentication process of the user U1 corresponds to “the first user wears the wearing device and performs personal authentication”.

When the user U1 is personally authenticated, the mounted device 101 is operated by the user U1 and the inheritance process is performed (inheritance processing unit 69). In the inheritance process, an operation to be inherited by the user U1 to the user U2 is performed. The inheritance destination designation screen (screen D10) illustrated in FIG. 22 is an example of a screen displayed on the display unit 31 during an operation by the user U1. The operation of the inheritance process is an operation (right inheritance instruction) for inheriting the right to use the card information of the user U1 to the user U2 by using the mounted device 101 for which the user U1 has been personally authenticated. Note that performing the inheritance process corresponds to “the first user inherits the right of the mounted device to the second user”.

The user U1 removes the wearing device 101 from the wrist and removes it from the wrist (operation P13). The user U1 hands over the mounted device 101 to the user U2 (operation C).

When the user U2 wears the wearing device 101 (operation P15), the wearing device 101 performs a personal authentication process for the user U2 (authentication processing unit 57). In the personal authentication process, the vein pattern of the user U2 registered in advance in the wearing device 101 and the vein pattern analyzed from the captured image of the vein imaged by controlling the image sensor 21 are the same as the personal authentication process of the user U1 described above. Is matched. Note that performing the personal authentication process of the user U2 corresponds to “the second user wearing the wearing device and performing personal authentication”.

After the user U2 is personally authenticated, the user U2 moves close to the fee system 5.

When the payment process 5A of the fee system 5 occurs, a command RQ requesting card information for payment processing is transmitted from the fee system 5 to the mounted device 101. In the mounted device 101, the request detection processing unit 56, the determination processing unit 159, and the control unit 150 perform processing corresponding to the command RQ, and a command including card information of the user U1 based on inheritance information from the user U1 to the user U2. Send (answer) RP. In this way, the payment process based on the card information of the user U1 can be performed from the mounting device 101 attached to the user U2 until the user U2 removes the mounting device 101 and removes it (operation P17). Note that the payment using the card information of the user U1 from the mounting device 101 mounted on the user U2 corresponds to “the second user making a payment using the mounting device on behalf of the first user”.
In this way, the control unit 150 can entrust the user U2 with the payment process based on the card information of the user U1 that is made possible as a result of the personal authentication of the user U1.
Hereinafter, the configuration of the mounting device 101 capable of obtaining such an effect will be described in detail below.

(Configuration of equipment)
FIG. 15 is a block diagram illustrating a schematic configuration of the mounted device.
The mounting device 101 includes a mounting unit 10, a biological information detection unit 20, a notification unit 30, an operation unit 37, a timing unit 39, a communication unit 41, a control unit 150, and a storage unit 170. The mounted device 101 is connected to the fee system 5 via the communication 7.

The mounting device 101 according to the present embodiment is different from the mounting device 1 according to the first embodiment in that a control unit 150 is provided instead of the control unit 50 and a storage unit 170 is provided instead of the storage unit 70. The other points are the same as those of the mounted device 1. Therefore, the following description will focus on differences from the mounted device 1.

(Control part)
The control unit 150 includes a processor such as a CPU or a DSP (Digital Signal Processor), and is a control device and an arithmetic device that collectively control each unit of the mounted device 101. The control unit 150 implements various functions of the mounted device 101 according to various programs including a control program (not shown) stored in the storage unit 170.
The control unit 150 includes a detection processing unit 52, a request detection processing unit 56, an authentication processing unit 57, a determination processing unit 159, a reception processing unit 61, a notification processing unit 63, and an inheritance processing unit 69 as main functional units. These function units are collectively controlled by an event processing unit 67 and an event handler (described later) to realize the function of the mounted device 101. In addition, the control unit 150 executes the function of the initial registration unit 65 before the above-described function unit is realized.

(Initial Registration Department)
The initial registration unit 65 performs initial registration of a user who uses the mounted device 101. Specifically, the initial registration unit 65 controls the operation unit 37 and the display unit 31 to acquire information such as user personal information and card information. The acquired information is stored in the storage unit 170 as a personal information table 172 (FIG. 16). At the time of storage, the control unit 150 generates a UID (User Identification) for identifying the user and manages it as user information.

Here, the personal information table 172 will be described with reference to FIG. FIG. 16 is a diagram illustrating an example of the personal information table. In the personal information table 172, a column 72A, a column 72B, a column 72C, a column 72D, a column 72E, a row 72G, a row 72H, a row 72J, and a row 72K are shown. The column 72A stores the UID. The column 72B stores service types, the column 72C stores card numbers, and the column 72D stores incidental information. The column 72E stores inherited UIDs. The inherited UID is a UID stored by the inheritance processing unit 69 (details will be described later). The row 72G indicates that the credit card service of the user U1 whose UID is “0001” is “A card”, the card number is “01234567890123456789”, and the incidental information is “012”. The row 72H indicates that the personal information type of the user U1 having the same UID “0001” as the row 72G is “My Number”, and the number is “000011112222”. In the rows 72J and 72K, the information of the user U2 whose UID is “0002” is stored in the same format as the information of the user U1. Information relating to the user U1 stored in the personal information table 172 corresponds to first user information.

Personal information is, for example, information such as my number, name, age, and address, and can be transmitted when requested by the fee system 5 or another system. The card information is, for example, a credit card number (credit card information), debit card information (debit card information), a cash card number (cash card information), and an account number (net banking information) used for net banking. Security code, password, etc. are stored as incidental information as necessary. The personal information table 172 may store information shared between the user U1 and the user U2.

The initial registration unit 65 controls the operation unit 37 and the display unit 31 to prompt the user to wear the wearing device 101, and after the user wears the wearing device 101, biometric information that identifies the user individual is detected. As a suitable example, the biological information is a vein image signal with high individual identification accuracy. The initial registration unit 65 controls the biological information detection unit 20 to acquire a vein image signal. The feature point data of the vein pattern is calculated from the acquired vein image signal by applying known processing such as image binarization processing, thinning processing, feature point extraction, and the like. The feature point data includes, for example, a plurality of feature point data such as the interval and number of branch points of the vein pattern, the length and shape between the branch points, and the depression angle at the branch point. In the initial registration unit 65, when the user feature point data is calculated, the feature point data is associated with the user UID and stored in the storage unit 170 as registration authentication data 81 (FIG. 5).

Here, the registration authentication data 81 of the present embodiment will be described with reference to FIG. In the registration authentication data 81, a column 81A and a column 81B are shown. The column 81A stores the UID. Column 81B stores vein pattern feature point data. In the first line of the registration authentication data 81 of the present embodiment, feature point data having a UID “0001” (user U1) is stored as “feature point data A”. The feature point data A is a numerical data group representing feature points. There may be a plurality of numerical data groups. In the second row, feature point data having a UID “0002” (user U2) is stored as “feature point data B”.

Although the initial registration operation by the initial registration unit 65 is performed by controlling the operation unit 37 and the display unit 31, it communicates bidirectionally with other PCs and smartphones via the communication unit 41, Information such as user personal information and card information may be input on the smartphone side. The mounted device 101 may be configured to receive such information and store it in the storage unit 170.

(Event processing part)
The event processing unit 67 sets a mechanism for controlling each functional unit by the event driving method in the control unit 150 and starts an event processing loop. The various events include an event that detects the mounting of the mounting device 101 (mounting event IV1), an event that detects that the mounting device 101 is released (non-mounting event IV3), and an event that receives a payment request from the fee system 5 (payment request). Event IV5) and an event (inheritance event IV7) when the inheritance setting of the mounted device 101 is selected by a user operation. In the event processing loop, when these events occur, the process moves to an event handler (not shown) set for each event type. The event handler is a function unit that constitutes the control unit 150, and is a function in which processing corresponding to each event is described. Each function unit is executed as necessary to realize processing corresponding to the event. The event handler process flow will be described later with reference to the flowcharts shown in FIGS.

(Mounting detector)
The detection processing unit 52 includes an attachment detection unit 53 and a non-attachment detection unit 55.
The wearing detection unit 53 detects that the wearing device 101 is worn on the user's wrist, and notifies (outputs) the occurrence of a wearing detection event to the event processing unit 67. Specifically, the mounting detection unit 53 monitors an ON / OFF signal output from the mounting unit 10. When the signal changes from OFF to ON, the mounting event IV1 is output.

(Event handler for wearing event IV1)
When the mounting event IV1 is notified to the event processing unit 67, the processing is moved to the event handler by the notification. In this event handler, the function of the authentication processing unit 57 is realized, and it is determined whether or not the user wearing the wearing device 101 is a user registered in advance by the initial registration unit 65. Details of the determination method will be described later in the authentication processing unit 57. If it is determined that the user is a registered user, the user's UID is stored in the result data 185 (FIG. 17). Subsequently, in the event handler of the wearing event IV1, if the wearing user has inherited the rights from another user (for example, the user U2 from the user U1) (when inherited), the right inheriting source user (user U1) When the right is not inherited by any user (when not inherited), information indicating that the right is not inherited (non-inherited information) is output to the display unit 31. Each information is displayed on the display unit 31. Further, at this time, buzzer sound data for urgent attention to the sound output unit 33 or vibration data for stimulating tactile sensation may be output to the vibration unit 35. The notification unit 30 including the function for outputting information by the event handler and the display unit 31, the sound output unit 33, and the vibration unit 35 corresponds to the notification unit.

Here, the result data 185 will be described with reference to FIG. FIG. 17 is a diagram illustrating an example of result data. In the result data 185, a column 85A, a column 85B, a column 85C, and a column 85D are shown. The column 85A stores the UID, the column 85B stores “1” indicating that the collation result matches (the user of the corresponding UID has been personally authenticated), and the column 85C stores the collated time data. Yes. In the column 85D, “1” is stored in the validity flag when the contents of the collation result (contents in the column 85B) are valid, and “0” is stored in the validity flag when the contents are not valid. If it is determined that the user wearing the wearing device 101 is not a user registered in advance, the UID stored in the column 85A of the result data 185 is deleted and “NULL” data (for example, value Becomes “−1”), and the contents of the other columns 85B, 85C, and 85D are also initialized to “NULL”.
In the example of the result data 185 shown in FIG. 17, the user U1 has the valid flag “0” and the user U2 has the valid flag “1”. It shows that.

(Non-wearing detector)
The non-wearing detection unit 55 detects that the wearing device 101 has been removed from the user's wrist, and notifies (outputs) the occurrence of the non-wearing event IV3 to the event processing unit 67. Specifically, the non-mounting detection unit 55 monitors an ON / OFF signal output from the mounting unit 10. When the signal changes from ON to OFF, a non-wearing event IV3 is output.

(Event handler for non-wearing event IV3)
When the non-wearing event IV3 is notified to the event processing unit 67, the processing is moved to the event handler by the notification. In this event handler, the valid flag in the column 85D (FIG. 17) of the result data 185 is updated to “0”. The fact that the valid flag is set to “0” indicates that the result of personal authentication of the user wearing the wearing device 101 has become invalid.
The mounting unit 10, the detection processing unit 52, and the biological information detection unit 20 correspond to a detection unit that detects a mounting state.

(Request detection processing part)
The request detection processing unit 56 monitors the reception data of the communication unit 41, and notifies (outputs) the payment request event IV5 to the event processing unit 67 when the received data is information requesting card information. The request detection processing unit 56 manages information such as a payment processing system (such as the fee system 5), a card company, and a service that can accept payment processing by the mounted device 101 and the user. These pieces of information are stored in advance in the storage unit 170 as a request acceptance source list (not shown). Note that the content of the request reception source list is updated based on information distributed from the information source via the network.
The request detection processing unit 56 determines whether or not the received data acquired from the communication unit 41 is data included in the request reception source list. If the received data is present, the payment request event together with the content of the received data is present. IV5 is output to the event processing unit 67.

(Event handler for payment request event IV5)
When the payment request event IV5 is notified to the event processing unit 67, the processing is moved to the event handler by the notification. In this event handler, the determination processing unit 159 is executed to determine whether the result of personal authentication of the user wearing the wearing device 101 is valid or invalid.

If it is determined to be invalid, an NG (No good) response indicating that the card information cannot be transmitted is transmitted as response information of the received data.

If it is determined to be valid, response information corresponding to the received data is generated and transmitted to the fee system 5 via the communication unit 41. For example, if a specific service is designated in the received data, the response information is information on a card number in a row that matches the content of the service stored in the column 72B of the personal information table 172. At this time, the inherited UID in the column 72E is referenced. For example, when the personally authenticated user is the user U2 (UID is “0002”) and the result is determined to be valid, the card information of the row 72G in which “0002” exists in the column 72E of the personal information table 172 Select. The user of the UID stored in the column 72E has inherited the right to use the information stored in the same row. In the example of the personal information table 172, the card information of the service “A card” and the card number “01234567890123456789” in the row 72G is selected. In this way, in the mounted device 101 worn by the user U2, the card information of the user U1 stored in the storage unit 170 is used (output to the charge system 5) when the right is inherited from the user U1. The function of this event handler corresponds to a function of outputting information based on the result of personal authentication by the authentication unit.
The information output to the external fee system 5 is information based on the result of personal authentication, and is not limited to original data (data specifying an individual) as a result of personal authentication.
In addition, since the content of the received data and the transmission / reception procedure depend on the agreement of the card company and the service, the content and the transmission / reception procedure corresponding to each company and service are applied.

(Authentication processing part)
The authentication processing unit 57 performs personal authentication processing in the same manner as in the first embodiment when the mounting device 101 is mounted by the user. Note that the authentication processing unit 57 corresponds to an authentication unit.

(Judgment processing part)
When the determination processing unit 159 receives a payment request from a payment processing system such as the fee system 5, the determination processing unit 159 determines whether the personal authentication result of the user wearing the wearing device 101 is valid or invalid. . The determination processing unit 159 is a functional unit that is implemented by being called from an event handler that is executed by notification of the payment request event IV5. The determination processing unit 159 refers to the result data 185 and outputs a determination result by the following (procedure 1) to (procedure 3).
The data of the result data 185 is read into the internal variable line by line. ... (Procedure 1)
It is determined that the column 85A (UID) is not “NULL”. ... (Procedure 2)
It is determined whether the column 85B (collation result) is “1” and the column 85D (valid flag) is “1”. ... (Procedure 3)
The procedure 1 is a process of reading from the storage unit 170 to the internal variable, the procedure 2 is a comparison process of the internal variable and “NULL”, and if the procedure 2 is established, the process proceeds to the process of the procedure 3. In the procedure 3, the internal variable and the numerical value “ Comparison processing with “1” is performed. When the procedure 3 is established, the user of the corresponding UID is personally authenticated, and the result is determined to be valid. When the procedure 2 or the procedure 3 is not established, it is determined that the result of the user personal authentication is invalid.
In this way, the processing steps for realizing the procedures 1 to 3 can be realized with a fixed number of steps, and the processing time can be calculated based on the CPU processing speed (MIPS (Million instructions per second)) and is constant. is there.
In the above-described determination processing unit 159, an example is shown in which the determination processing unit 159 performs the final determination whether the personal authentication is valid or invalid. However, the determination processing unit 159 is not necessarily limited to this example. The determination processing unit 159 may be a process that outputs information necessary to make a final determination as to whether personal authentication is valid or invalid. In this case, based on the processing of the determination processing unit 159, the fee system 5 that is an external terminal makes a final determination as to whether the personal authentication is valid or invalid. Whether the personal authentication is valid or invalid based on the determination processing unit 159 regardless of whether the final determination of the personal authentication is performed inside the mounted device 101 or the fee system 5 that is an external device of the mounted device 101. There is no change in the determination.
Therefore, according to the information processing of the determination processing unit 159 described above, when the payment request is received from the charge system 5 in the mounting device 101, if the user wears the mounting device 101, the individual personal authentication process is not performed. Thus, the verification result can be determined and the reply process can be promptly performed for the payment request.
The determination processing unit 159 corresponds to a determination processing unit.

(Reception Processing Department and Notification Processing Department)
The reception processing unit 61 and the notification processing unit 63 are functional units that function as a pair as in the first embodiment.
In this embodiment, when the non-mounting event IV3 is notified to the event processing unit 67 in a state where the mounting release flag is set, the event handler executed by the notification causes the column 85D of the result data 185 (FIG. 17). Is updated to “0”. That is, the result of personal authentication is invalid. This processing flow is the same as the flow shown in FIG.

(Inheritance processing part)
The inheritance processing unit 69 performs a procedure of inheriting the right to use the mounted device 101 that holds the personally authenticated user (user U1) information to another user (user U2).
The control unit 150 controls the operation unit 37 and the display unit 31 to notify the event processing unit 67 of the inherited event IV7 when a predetermined operation is performed.

(Inheritance event IV7 event handler / inheritance processing section)
When the inherited event IV7 is notified to the event processing unit 67, the process is moved to the event handler by the notification. When this event handler is executed, the function of the inheritance processing unit 69 is realized.
The inheritance processing unit 69 corresponds to an inheritance accepting unit, and accepts a right inheritance instruction of the mounted device 101 from a user (user U1). Specifically, the inheritance processing unit 69 outputs to the display unit 31 an inheritance destination designation screen that allows the user U1 to select an inheritance destination user (user U2) and an inheritance information designation screen that designates inheritance information. Further, the inheritance processing unit 69 controls the operation unit 37 to acquire the operation signal selected by the user U1.
FIG. 22 is a diagram illustrating an example of the inheritance destination designation screen. FIG. 23 is a diagram illustrating an example of the inheritance information designation screen. The inheritance destination designation screen (screen D10) and the inheritance information designation screen (screen D20) are screens displayed on the display unit 31, and the screen D20 is displayed after the operation of the screen D10. A selection menu displayed by the operation unit 37 can be selected.

The inheritance processing unit 69 refers to the registration authentication data 81 and the personal information table 172, and acquires UIDs other than the user wearing the wearing device 101 and related information such as the name of the UID. A screen D10 is generated using the acquired UID and name. On the screen D10, the UID “0002” and the name “ABC” indicating the user U2 are displayed on the first line of the selection menu, and “Release All” is displayed on the second line. In addition, an “OK” button indicating the determination is displayed. When the user U1 selects the UID “0002” and the name “ABC”, the row is highlighted (not shown), and “OK” is selected, whereby the inheritance destination is determined to the user U2. When “cancel all specified” is selected, the designation of the inheritance destination is cancelled.
The inheritance processing unit 69 stores the UID “0002” in the internal variable.

The inheritance processing unit 69 refers to the personal information table 172, reads the information of the user (user U1, UID “0001”) wearing the mounted device 101, and generates a screen D20. On the screen D20, the service “A card” and the card number “01234567890123456789” are displayed on the first line of the selection menu, and the service “My number” and the card number “000011112222” are displayed on the second line. In addition, an “OK” button indicating determination and a “Cancel” button indicating cancellation are displayed. When a service to be inherited is selected by the operation of the user U1, the row of the selected service is highlighted (not shown), and “OK” is selected to determine the service to be inherited by the user U2. . The inheritance processing unit 69 stores the inheritance destination UID in the row corresponding to the service determined in the column 72E (inheritance UID) of the personal information table 172. Further, the column 72E (inherited UID) corresponding to the service corresponding to the menu not selected in the selected menu is updated to “NULL”. The example of the personal information table 172 shows a state where both the first and second rows of the selection menu on the screen D20 are selected, and the UID “0002” is stored in the rows 72G and 72H of the column 72E.
Further, in the inheritance processing unit 69, when “cancel all designated” is selected and determined on the screen D10, all the UIDs stored in the column 72E of the personal information table 172 are updated to “NULL”.

(Memory part)
The storage unit 170 is configured by a storage device such as a ROM (Read Only Memory), a flash ROM, a RAM (Random Access Memory), or a FeRAM (registered trademark) (Ferroelectric RAM), and implements each functional unit of the control unit 150. Various programs (not shown) including the control program, data, and the like are stored. In addition, it has a work area for temporarily storing data being processed, variables, flag values, processing results, and the like of various processes.
The storage unit 170 stores a personal information table 172, registration authentication data 81, acquisition authentication data 83, result data 185, and the like.
The personal information table 172 includes personal information data 73 and card information data 75. The personal information data 73 and card information data 75 of the user including the user stored by the initial registration unit 65 as described above are stored. Yes.
The registration authentication data 81 stores feature point data of users including users registered by the initial registration unit 65 as described above.
The acquired authentication data 83 stores the feature point data calculated by the authentication processing unit 57 as described above.
As described above, the result data 185 stores the UID of the user who is personally authenticated by the mounted device 101, the verification result, the verification time, and the valid flag.

(Power generation part)
Note that, similarly to the first embodiment, the mounting device 101 may include a power generating unit (not shown).

(Main control processing flow)
FIG. 18 is a flowchart showing the flow of the main control process. Hereinafter, description will be made with reference to FIGS. The following flow is a flow of main control processing. The control unit 150 controls the mounting unit 10 and the biological information detection unit 20 based on a control program (not shown) stored in the storage unit 170. It is executed by controlling each part to be included.

Step S10 performs an initial registration process. This process will be described in detail in the flow shown in FIG. 8 as in the first embodiment. When the initial registration process is executed, user information is stored in the personal information table 172 and the registration authentication data 81.

Step S20 registers event processing. Define various events required for event-driven programming, and set event handlers corresponding to each event to be activated. Here, mounting event IV1, non-mounting event IV3, payment request event IV5, and inheritance event IV7 used in the subsequent steps are defined, and event handlers corresponding to the respective events are set.

Step S30 is an event processing loop. Each event handler (steps S45, S50, S65, S70) is executed in response to the occurrence of various events. Events are queued and event handlers are executed in the order in which each event occurs (some emergency events have priority). When the event handler process is completed, the process returns to this step and waits for an event to occur.

Step S45 is an event handler that is processed when the event of the mounting event IV1 occurs, and performs mounting event processing. Details of the processing will be described in the flow shown in FIG. When this process is executed, the acquisition authentication data 83 is generated, and the result of matching the registration authentication data 81 and the acquisition authentication data 83 is stored in the result data 185.

Step S50 is an event handler that is processed when an event of the non-wearing event IV3 occurs, and performs non-wearing event processing. Details of the processing will be described in the flow shown in FIG. 10 as in the first embodiment. When this processing is executed, it is recorded that the collation result of the result data 185 is invalid.

Step S65 is an event handler that is processed when an event of the payment request event IV5 occurs, and performs an authentication request process. Details of the processing will be described in the flow shown in FIG. When this processing is executed, if the collation result of the result data 185 matches and is valid, card information and the like are transmitted.

Step S70 is an event handler that is processed when an event of the inheritance event IV7 occurs, and performs inheritance event processing. Details of the processing will be described in the flow shown in FIG. When this process is executed, the inheritance destination designation screen (screen D10) and the inheritance information designation screen (screen D20) are displayed on the display unit 31, and the inheritance UID is stored in the column 72E of the personal information table 172.

(Initial registration process flow)
FIG. 8 is a flowchart showing the flow of the initial registration process. This flow is the detail of the process of step S10 of the main control process shown in FIG.

In step S110, personal information is registered. In the present embodiment, personal information data 73 and card information data 75 of the user who uses the mounted device 101 are acquired and stored in the personal information table 172.
In step S120, a captured image is acquired. The imaging sensor 21 is controlled to acquire a user's vein image.
In step S130, authentication data is generated and registered. The feature point data of the vein pattern is calculated from the vein image and registered (stored) in the registration authentication data 81. The feature point data registered in the registration authentication data 81 is feature point data for identifying the individual of the user.

(Installation event processing flow)
FIG. 19 is a flowchart showing the flow of the mounting event process. This flow is the detail of the process of step S45 of the main control process shown in FIG.

In step S210, a captured image is acquired. Specifically, the imaging sensor 21 is controlled to acquire a user's vein image.
In step S220, authentication data is generated and stored. The feature point data of the vein pattern is calculated from the vein image and stored in the acquisition authentication data 83.

In step S230, the acquisition authentication data 83 and the registration authentication data 81 are collated. Specifically, the feature point data stored in the acquisition authentication data 83 is compared with the feature point data stored in the registration authentication data 81. Specifically, a correlation coefficient between both feature point data groups is calculated.
In step S240, it is determined whether or not the collation results match. Specifically, if the correlation coefficient calculated in step S230 is greater than or equal to a predetermined value, it is determined that the collation results match (Yes), and the process proceeds to step S250. If the correlation coefficient is less than the predetermined value, the collation result is It is determined that they do not match (No), and the process proceeds to step S260. If feature point data of a plurality of users are registered in the registration authentication data 81, the feature point data of the registration authentication data 81 is switched for each user, and the processes in steps S230 and S240 are repeated.
In step S250, the matching UID of the registration authentication data 81 is stored in the result data 185. More specifically, the UID having the matched feature point data is acquired from the registration authentication data 81 in step S240, the UID is stored in the result data 185, the collation result is “1”, the collation time, and the valid flag is “1”. Is stored respectively.
In step S260, the result data 185 is initialized. Specifically, the UID information stored in the result data 185 is deleted. Specifically, the UID information is updated to “NULL”, the collation result is changed to “0”, the collation time is “NULL”, and the valid flag is changed to “0”. Since the result data 185 is referred to by the event handler (step S65, steps S410 to S450) of the payment request event IV5, when the user who wears the wearing device 101 is not registered in advance by such initialization, It is guarded so that card information is not transmitted.

In step S270, the presence / absence of inheritance is determined. If it is determined that there is inheritance (Yes), the process proceeds to step S280. If it is determined that there is no inheritance (No), the process proceeds to step S290. The presence / absence of inheritance is determined by determining that there is inheritance when the UID acquired in step S250 matches the UID stored in the column 72E of the personal information table 172. It is determined that there is no inheritance.
In step S280, the information on the inherited UID (column 72E) in the personal information table 172 can be referred to. Specifically, in step S270, information on a row that matches the UID stored in the column 72E of the personal information table 172 is read into an internal variable.
In step S285, the inheritance source UID information is displayed. Specifically, information related to the UID stored in the column 72A is generated from the internal variable read in step S280, and is output to the display unit 31. Also, the inherited service, card number, etc. may be displayed.
In step S290, information indicating that it is not inherited (non-inherited information) is displayed. For example, “This device is not inherited by anyone” is displayed.

According to the flow shown in steps S270 to S290, if the right is inherited from another user after the user wears the wearing device 101 and is personally authenticated, the contents can be confirmed at the time of wearing. it can. For example, if the right is inherited from the user U1 when the user U2 wears the wearing device 101, “this wearing device has been inherited from Mr. XYZ with the UID“ 0001 ”” by the process of step S285. (XYZ is the name of the user U1) is displayed.

(Non-wearing event process flow)
FIG. 10 is a flowchart showing the flow of the non-wearing event process. This flow is the detail of the process of step S50 of the main control process shown in FIG.

In step S310 of this embodiment, data is written to the result data 185. Specifically, if the UID exists in the result data 185 (not “NULL”), the valid flag is changed to “0”. That is, the result of personal authentication is invalid.
The content of the valid flag of the result data 185 is referred to by the event handler of the payment request event IV5. When the valid flag is not “1”, the card information is not transmitted. That is, by this step, the card information is controlled not to be transmitted when the mounted device 101 is not mounted.

Also in this embodiment, the event processing when referring to the mounting release instruction can be performed after the processing performed in FIG. 10 by the flowchart showing the flow of the non-mounting event processing shown in FIG.
According to the flow of FIG. 12, in the reception processing unit 61, when the mounting release flag is not set to “ON” and the mounted device 101 is not mounted (removed), an alert sound is generated and a warning is prompted. be able to.

(Authentication request processing flow)
FIG. 20 is a flowchart showing the flow of the authentication request process. This flow is the detail of the process of step S65 of the main control process shown in FIG.

In step S410, the result data 185 is read. Specifically, the content of the result data 185 is read into an internal variable. The UID, verification result, verification time, and valid flag are read.

In step S420, it is determined whether or not data exists in the result data 185. Specifically, if the UID is not “NULL”, it is determined that there is data (Yes), and the process proceeds to step S435. If the UID is “NULL”, it is determined that there is no data (No), Proceed to step S450.

In step S435, a UID having a matching result “1” and a valid flag “1” is acquired. If there is no UID that is “1” for both, the process proceeds to step S450 (not shown).

In step S445, card information in which the inherited UID of the personal information table 172 matches the acquired UID is transmitted. Specifically, in step S270, information on a row that matches the UID stored in the column 72E of the personal information table 172 is read into an internal variable. The card information included in the internal variable is transmitted to the fee system 5 via the communication unit 41.

In step S450, an NG (No good) response is transmitted. Specifically, an NG response indicating that the card information cannot be transmitted is transmitted to the fee system 5 via the communication unit 41.

In step S445 and step S450, the card information and the NG response are transmitted. Actually, however, the information is variously changed in both directions based on the communication method, communication procedure, and transmission / reception data specifications determined in advance in the mounted device 101 and the charge system 5. Information is being sent and received. Security measures such as encryption are also taken.

(Inheritance event processing flow)
FIG. 21 is a flowchart showing the flow of inheritance event processing. This flow is a detail of the process of step S70 of the main control process shown in FIG. 18 (event handler of inheritance event IV7). The inheritance event IV7 is an event generated by an operation of the user U1 who is the inheritance source.

In step S610, an inheritance destination designation screen is displayed. Screen D10 (FIG. 22) is an example of the inheritance destination designation screen. Information on the inherited UID selected from the selection menu is acquired.
In step S620, an inheritance information designation screen is displayed. Screen D20 (FIG. 23) is an example of the inheritance information designation screen. Get inheritance information selected from the selection menu.
In step S630, the inherited UID is stored in the personal information table 172. Specifically, a row in which the content of the column 72A of the personal information table 172 matches the UID of the user U1 who is the inheritance source, and a row in which the content of the column 72B and the column 72C matches the acquired inheritance information is selected. The acquired inherited UID information is stored in the column 72E of the row.

When each flow shown in FIGS. 18 to 21 is processed, when a payment request is received from the fee system 5 via the communication unit 41, a payment request event IV5 is notified, and the corresponding event handler. Card information is transmitted by the processing of the authentication request processing (steps S65, S410 to S450). If the card information to be transmitted is set to be inherited from the inheritance source user U1 to the inheritance destination user U2 by the inheritance event process (steps S70, S610 to S630), the card information transmitted from the mounting device 101 worn by the user U2 to the user U1 card information is transmitted. If the inheritance event process is not set to be inherited, the card information of the user U2 wearing the wearing device 101 is transmitted. Card information can be switched and transmitted by such a flow of inherited event processing.

As described above, in the mounting device 101 according to the present embodiment, the following effects can be obtained.
The mounting unit 10 and the detection processing unit 52 detect the mounting state of the mounting device 101. Specifically, the mounting event IV1 is output when the mounting device 101 is mounted, and the non-mounting event IV3 is output when the mounting device 101 is not mounted.
When the mounting event IV1 is output, the event handler calls the authentication processing unit 57 to perform personal authentication processing of the user U1 wearing the mounting device 101. After the user U1 is personally authenticated, the function of the inheritance processing unit 69 can be realized by a predetermined operation of the user U1. In the inheritance processing unit 69, information for inheriting to the inheritance destination user (user U2) is set by the designation of the user U1. The setting by the inheritance processing unit 69 can be set by an easy setting screen and operation as shown in the screen D10 and the screen D20.
After that, when the wearing device 101 is worn by the user U2, personal authentication processing of the user U2 is performed by an event handler (authentication processing unit 57) based on the wearing event IV1. When the user U2 is personally authenticated, the inheritance information inherited from the user U1 (such as the card information of the user U1) is displayed on the display unit 31 of the mounted device 101 (step S285). After that, when the card system or the like is requested from the fee system 5, the mounting device 101 mounted on the user U2 can transmit the card information of the user U1 by the event handler of the payment request event IV5.
In this way, the wearing device 101 can pass down the result of the personal authentication of the user U1 performed by the wearing device 101 to the user U2 safely and easily.

Note that the present invention is not limited to the above-described embodiment, and various modifications and improvements can be added to the above-described embodiment. In the following, modifications will be described with the mounted device 1 as an example.

(Modification 1)
In the mounting device 1 according to the above-described embodiment, the case where a payment request is received from the fee system 5 is exemplified, but the application is not limited to such a payment request. For example, in a browsing system that browses asset information and the like using My Number, the user wearing the mounting device 1 can quickly display the user's asset information and the like by approaching the display screen of the browsing system. In this case, when the collation result of the result data 85 is “1” and the valid flag is “1”, the wearing device 1 transmits my number information to the browsing system side. In the browsing system, as a result of personal authentication of the user wearing the wearing device 1, it is possible to determine the situation in which my number information is being transmitted, so information quoted from the my number is displayed. By making the mounted device 1 available in such a browsing system, the browsing system installed in a public place such as a municipal office can be used efficiently.

(Modification 2)
In the above-described embodiment and modification, the authentication processing unit 57 acquires a vein image from the imaging sensor 21 and performs personal authentication processing. However, the personal authentication processing is not limited to such a method. The personal authentication process may be performed by acquiring, for example, a pulse waveform, an arterial image, a blood composition value that can be measured non-invasively, a combination thereof, and the like.

(Modification 3)
In the above-described embodiment and modification, the wearing device 1 is worn around the wrist, but the wearing device 1 may be a device worn on a portion other than the wrist. The modification will be described next with reference to the drawings. 24 to 28 are explanatory diagrams showing an outline of a usage form of the mounted device according to the modification.

(1) Ring-type or finger-sack-type mounting device The mounting device according to this modification can be a ring-type or finger-sack type in which a band of the mounting part is mounted around a hand or a toe. . For example, the ring-type mounting device 1A shown in FIG. 24 is mounted by winding the band 11A of the mounting portion 10A around the fingers of the hand. Then, the biometric information detection unit 20 acquires a blood vessel image of the finger by the imaging sensor 21, and performs personal authentication processing using the blood vessel pattern. The pulse waveform may be used for personal authentication processing by the biometric sensor 23. A fingerprint image of a finger or a heel image of the middle of a finger is acquired, and personal authentication processing is performed using a fingerprint pattern or a heel pattern. The validity flag is “1” until the band 11A is removed after the personal authentication.

(2) Glasses-type wearing device The wearing device of this modification can be a glasses-type device in which the wearing unit is worn on the face as a frame of glasses. For example, the spectacle-type wearing device 1B shown in FIG. 25 wears the wearing unit 10B on the face. Then, the biometric information detection unit 20 captures the pupil by the imaging sensor 21, acquires a capillary blood vessel image or iris image of the retina, and performs personal authentication processing using the capillary blood vessel pattern or iris pattern. After the personal authentication, the validity flag is “1” until the frame which is the wearing unit 10B is removed from the face.

(3) Glove-type wearing device The wearing device of this modification can be a glove-type or a palm-mounted type in which the mounting portion is mounted on the hand or palm. For example, in the glove-type wearing device 1C shown in FIG. 26, when the wearing unit 10C is worn on the hand, the biological information detection unit 20 acquires a palm image or a vein image obtained by imaging the palm of the palm by the imaging sensor 21. The personal authentication process is performed using the palm pattern or vein pattern. After the personal authentication, the validity flag is “1” until the mounting unit 10C is removed from the hand.

(4) Wearing device of ear wearing type The wearing device of this modification can be an ear wearing type in the shape of a headphone, an earphone, a pierced earring, or the like, in which the mounting portion is mounted on the ear. For example, in the pierce-shaped wearing device 1D shown in FIG. 27, when the wearing unit 10D is worn on the ear, the biological information detecting unit 20 takes an ear shape image, a vein image such as an earlobe, etc. by the imaging sensor 21. The personal authentication process is performed using the ear shape pattern and the vein pattern. After the personal authentication, the validity flag is “1” until the wearing unit 10D is removed from the ear.

(5) Clothing-type wearing device The wearing device according to the present modification can be a clothing type in the shape of a shirt, sweater, pants, socks, or the like that wears the mounting portion on the body. For example, in the shirt-shaped wearing device 1E shown in FIG. 28, when the wearing unit 10E is worn on the body, the biological information detection unit 20 uses the imaging sensor 21 to capture a vein image or a physical feature image of any part of the body. (Mole's position, size, etc.) is captured and acquired. Personal authentication processing is performed based on vein patterns and body feature patterns. The validity flag is “1” until the device 1E is removed after the personal authentication.

(Modification 4)
In the embodiment and the modification described above, the mounting unit 10 monitors the ON / OFF signal of the opening / closing unit 12 and the detection processing unit 52 detects the mounting and non-mounting, but the configuration is not limited thereto. For example, the band 11 of the mounting portion 10 is a metal bracelet or the like that is mounted around the user's wrist in an annular shape. The mounting portion 10 further includes an adjustment portion, and the adjustment portion is a band pressing member that can variably adjust the circumferential length of the annular shape of the band 11. The band pressing member may be a buckle such as a single opening type, a double hole type, or a double lock type. The adjustment unit includes a rotary mechanism that measures the circumference including the circumference where the band 11 is fixed to the wrist, an optical sensor that counts a certain length, or a switch sensor that detects that the buckle is folded. Is provided, and the measured circumference is output.

By using these mechanisms, it is possible to improve the detectability of a user who wears and does not wear the detection processing unit 52.
Specifically, the initial registration unit 65 performs personal authentication processing when the user wears the wearing device 1 on the wrist. At that time, the initial registration unit 65 measures the circumference when personal authentication is performed (referred to as the circumference in the mounted state). The measured circumference of the mounted state is stored in the storage unit 70.

When the detection processing unit 52 (mounting detection unit 53) acquires the circumference of the band 11 from the adjustment unit and becomes equal to the circumference of the wearing state stored in the storage unit 70, the wearing device 1 detects the wrist of the user. Is detected, and a mounting event IV1 is output. The determination that the circumferences are the same is made when the circumference of the band 11 is shorter than the circumference added by a predetermined length (for example, 2 mm) than the circumference in the wearing state in consideration of errors at the time of wearing. Is considered equivalent.
After that, the detection processing unit 52 (non-mounting detection unit 55) determines that the mounting device 1 is in the case where the measured circumference of the band 11 is a predetermined length (for example, 2 mm) or more than the circumference of the wearing state. It detects that the user's wrist has been removed, and outputs a non-wearing event IV3.

Further, the mounting event IV1 may be output when the pressure data (contact pressing) output from the pressing sensor provided in the opening / closing unit 12 reaches a predetermined pressure. In the predetermined pressure, as the processing of the initial registration unit 65 of the control unit 50, pressure data acquired when the user wears the wearing device 1 is registered. The predetermined pressure can be acquired as different pressure data depending on the wrist circumference or the elasticity of the wrist.

With the configuration as described above, it is possible to detect whether or not the user to be mounted is a user who has been personally authenticated in the mounting device 1, so that a more robust personal authentication process can be realized.

(Modification 5)
In the embodiment and the modification described above, the control unit 50 sets the valid flag of the result data 85 to “0” by the event handler process of the non-wearing event IV3. However, the configuration is not limited to such a configuration. The timing for setting the valid flag of the result data 85 to “0” may be performed by the following configurations (1) to (3).
The determination processing unit 59 can output the determination result with reference to the set valid flag at such timing. In addition, personal authentication may be performed by calling the authentication processing unit 57 at such timing. Such configurations (1) to (3) may be combined with a plurality of configurations instead of a single unit.

(1) Living body maintenance information acquisition unit (change in living body maintenance information)
The wearing device 1 further includes a biological maintenance information acquisition unit that acquires biological maintenance information for determining that the state of the user's biological body is maintained, and when the acquired biological maintenance information has changed, The valid flag may be set to “0”. The biological maintenance information is an example of biological reaction information, and the biological maintenance information acquisition unit corresponds to the biological reaction information acquisition unit.

The living body maintenance information is information related to a biological reaction such as a pulse wave waveform, a pulse rate, a skin temperature, and a deep skin temperature detected by the biological sensor 23. The living body maintenance information is continuously measured at regular intervals (for example, once / second). The state of living body maintenance is the state of maintenance of survival, maintenance of consciousness, maintenance of awakening, and the state of living body maintenance such as the state that each state has changed, the survival has been interrupted, the consciousness has been lost, or the sleep has fallen into sleep. When it changes, the measured value of the above-mentioned living body maintenance information changes. By monitoring the fluctuation state of the measured value and comparing it with a predetermined state, it is possible to capture a change in the state of living body maintenance. For example, when a predetermined pulsation waveform no longer exists in the pulse waveform, it is determined that the state of survival maintenance has changed.

In addition, information such as no fluctuation, no sudden change in momentum, no sudden change in exercise intensity is calculated as the living body maintenance information. These pieces of information can be calculated from the relationship between the body motion information per unit time acquired from the acceleration sensor provided in the operation unit 37 and the change in the pulse rate.
When these fluctuation states become a predetermined state, an event is generated, and the valid flag of the result data 85 is set to “0” in the event handler.

With the configuration as described above, when the user's survival is interrupted, the user loses consciousness, or the payment ability such as falling into sleep or the judgment ability to pay is lost, it becomes possible to cope with not accepting the payment process. Also, it is estimated that the user received some high-risk stimulus from the outside, such as when the user was upset, the user moved suddenly, or the user was subjected to a sudden exercise. In such a case, it is possible to cope with not accepting the payment process.

(2) Timekeeping part (change in time)
The wearing device 1 sets the valid flag to “0” when the time acquired from the time measuring unit 39 reaches a predetermined time.
The predetermined time is a time set by the user by the initial registration unit 65 of the control unit 50, and sets a time during which the result of personal authentication is valid. In other words, the result of the personal authentication process is valid until the predetermined time, but the result of the personal authentication process is invalidated when the predetermined time elapses. For example, if the predetermined time is determined to be 6:00 every morning, the result of the personal authentication process becomes invalid at 6:00 every morning, and if the user wants to continue using the wearing device 1, the personal authentication process is performed again. Can do. The predetermined time may be an elapsed time.
With such a configuration, the personal authentication process is performed at every predetermined time, so that the robustness of security is increased and a certain time from the predetermined time (for example, every morning from 6:00 to 30 minutes) It is possible to reserve it as a necessary time in a planned manner.

(3) Location information acquisition unit (change in location information)
The wearing device 1 further includes a positioning sensor (corresponding to a position information acquisition unit) that acquires user position information. When the position information acquired from the positioning sensor is out of a predetermined range, the valid flag is set to “0”. It may be set.
The position information is, for example, position information calculated based on a signal acquired from a GNSS (Global Navigation Satellite System) satellite or the like, and can be continuously acquired at regular time intervals (for example, once / second). .
The predetermined range is a range that is set by the user by the initial registration unit 65 of the control unit 50, and a user's action range including a place where the user may perform payment processing is set. That is, when the mounted device 1 is out of the user's action range, the validity flag is set to “0”, so that the robustness of security can be further enhanced in a place where payment processing is not necessary.

(Modification 6)
In the above-described embodiment and modification, a user who has been personally authenticated may be provided with a temporary reception unit that can be temporarily released (set to a non-wearing state) during wearing by a user's own operation.
The temporary reception unit controls the operation unit 37 and the display unit 31 to acquire a simple collation key from the user. A simple collation key is, for example, a 4-digit character or an answer to a question. The temporary reception unit outputs a simple verification key to the authentication processing unit 57.
When a simple verification key is input from the temporary reception unit, the authentication processing unit 57 prompts the user to input a simple verification key when called from the event handler of the mounting event IV1. If the character string input by the user matches the simple collation key, it is determined that personal authentication has been performed, and the collation result of the result data 85 is set to “1” and the valid flag is set to “1”. If the simple verification keys do not match, regular personal authentication processing is performed.

With such a configuration, for example, when the user wants to temporarily remove the wearer for his own intention, the personal authentication can be restored with a simple procedure. For example, it is a convenient function before and after bathing and before and after hand washing. Note that the simple collation key collation corresponds to performing simple personal authentication.

(Modification 7)
In the above-described embodiment and modification, the reception processing unit 61 has been illustrated by inputting a simple personal identification number and collating the predetermined operation to be operated by the user, but the predetermined operation is not limited to the input operation. For example, an action operation such as an operation of shaking the mounted device 1 or an operation of tapping the mounted device 1 may be used. The acceleration signal pattern detected by the acceleration sensor provided in the operation unit 37 can be identified by comparing with a predetermined pattern.
Moreover, in the temporary reception part in the above-mentioned modified example, although the input and collation by a collation key were illustrated, action operation with respect to the mounting apparatus 1 may be sufficient.

(Modification 8)
In the above-described embodiment and modification, the authentication request process (step S60) shown in FIG. 7 is an event handler when the payment request event IV5 occurs, but is the payment request received from the payment processing system? You may add the process which makes it determine in advance. For example, before a payment process is performed, when a predetermined operation (for example, tapping the mounted device 1 three times) is performed by the user, a process of receiving a payment request is added. By adding such a predetermined operation, the communication unit 41 and the request detection processing unit 56 can be in a reception waiting state only when payment processing is necessary, and it is necessary to wait for reception when payment processing is not necessary. Power consumption can be reduced.

DESCRIPTION OF SYMBOLS 1 ... Wearing apparatus, 5 ... Charge system, 5A ... Payment process, 5B ... Payment process, 7 ... Communication, 10 ... Wearing part, 11 ... Band, 12 ... Opening / closing part, 20 ... Biometric information detection part, 21 ... Imaging sensor, DESCRIPTION OF SYMBOLS 23 ... Biosensor, 30 ... Notification part, 31 ... Display part, 33 ... Sound output part, 35 ... Vibration part, 37 ... Operation part, 39 ... Time measuring part, 41 ... Communication part, 50 ... Control part, 52 ... Detection process , 53... Mounting detection unit, 55... Non-mounting detection unit, 56... Request detection processing unit, 57... Authentication processing unit, 59 ... determination processing unit, 61 ... reception processing unit, 63 ... notification processing unit, 65. , 67 ... event processing part, 70 ... storage part, 72 ... personal information table, 73 ... personal information data, 75 ... card information data, 81 ... registration authentication data, 83 ... acquisition authentication data, 85 ... result data.

Claims (13)

1. A wearing device that can be worn by a user,
   An authentication unit for performing personal authentication of the user to which the wearing device is attached;
   A detection unit for detecting a wearing state of the wearing device;
   A determination unit that determines whether the result of the personal authentication is valid or invalid based on the wearing state detected by the detection unit;
   When the authentication unit determines that the result of the personal authentication is valid after the user is authenticated by the authentication unit, the personal authentication by the authentication unit is omitted. A control unit for outputting the authentication result;
   A mounting device comprising:
2. The wearing device further includes:
   A receiving unit for receiving a mounting release instruction of the mounting device;
   A notification unit for stimulating and notifying information of a living body including at least one of visual, auditory, and tactile information;
   With
   The control unit notifies abnormality information by the notification unit when the wearing state is not mounted by the detection unit when the user does not receive the mounting release instruction to the receiving unit and is not received. The wearing device according to claim 1, wherein:
3. The wearing device further includes:
   A storage unit that stores financial processing information that enables financial processing using at least one of a credit card function, a cash card function, a debit card function, and a net banking function;
   The control unit, when the determination unit determines that the result of the personal authentication is valid after the user who has mounted the wearing device is authenticated by the authentication unit, Perform financial processing,
   The wearing device according to claim 1 or 2, wherein if it is determined that the result of the personal authentication is invalid, the financial processing is not executable.
4. The wearing device further includes:
   A mounting portion for mounting on the user;
   The mounting portion has an annular shape around the wrist of the user,
   The mounting portion has an opening / closing portion that opens and closes the annular shape,
   The mounting device according to any one of claims 1 to 3, wherein the detection unit detects that the mounting state is not mounted when the opening / closing unit is opened.
5. The wearing device further includes:
   A mounting portion for mounting on the user;
   The mounting portion has an annular shape around the wrist of the user,
   The mounting portion has an adjustment portion that variably adjusts the circumference of the annular shape,
   4. The detection unit according to claim 1, wherein the detection unit detects the wearing state as non-wearing when the adjustment unit increases the circumference of the wearing state by a predetermined length. 5. The wearing device according to Item 1.
6. The wearing device according to any one of claims 1 to 5, wherein the authentication unit acquires the user's biometric information and performs the personal authentication.
7. The wearing device according to any one of claims 1 to 6, wherein the authentication unit performs the personal authentication based on a password entered by the user.
8. The authentication unit is connected to an authentication server via a computer communication network, and performs personal authentication by collating information acquired from the user with unique information of the user stored in the authentication server. The mounting device according to any one of claims 1 to 7, wherein the mounting device is characterized.
9. The wearing device further includes:
   A biological reaction information acquisition unit for detecting the biological reaction of the user and acquiring biological reaction information;
   The determination unit determines whether to validate or invalidate the personal authentication result based on information on whether or not the biological reaction information is continuously detected by the biological reaction information acquisition unit. The mounting device according to any one of claims 1 to 8, wherein:
10. The wearing device further includes:
    At least one of a timing unit that measures time, a position information acquisition unit that acquires the position of the mounted device, and a biological reaction information acquisition unit that detects biological reaction of the user and acquires biological reaction information. Prepared,
    The authentication unit performs the personal authentication of the user in at least one of the case where the time is a predetermined time, the position is out of a predetermined range, and the biological reaction information is changed. The mounting device according to claim 1, wherein the mounting device is performed.
11. The wearing device further includes:
    A temporary reception unit for receiving temporary release of the attached device;
    The said control part makes the said authentication part perform simple personal authentication, when the said temporary mounting | wearing cancellation | release is received from the user who carried out the personal authentication. The mounting device according to any one of the above.
12. The detector is
    The contact state to the wrist of the user is detected, and the wearing state is detected based on the contact pressure at the time of the user's wearing. The mounting equipment described.
13. The wearing device further includes:
    Provided with a power expression unit that generates power,
    The mounting device according to any one of claims 1 to 12, wherein the mounting device is operated by electric power from the power generating unit.

Images