WO2018229949A1

WO2018229949A1 - Property-data transmission/reception system

Info

Publication number: WO2018229949A1
Application number: PCT/JP2017/022204
Authority: WO
Inventors: 堅二豊田
Original assignee: 株式会社ニコン
Priority date: 2017-06-15
Filing date: 2017-06-15
Publication date: 2018-12-20

Abstract

Provided is a property-data reception device including: (1) an authentication unit that executes personal authentication of a user; and (2) a first communication unit that receives property data when the personal authentication is affirmative.

Description

Property data transmission / reception system

This disclosure relates to a property data transmission / reception system, and a property data reception device, property data transmission device, method, and program used in the property data transmission / reception system.

Conventionally, an authentication system using electric field type near field communication (electric field near field communication, electric field type NFC, eNFC) is known. For example, Japanese Patent Laid-Open No. 2011-123729 discloses personal authentication between a human body communication module possessed by a user and an ATM (Automatic Teller Machine) placed in a financial institution. In Japanese Patent Application Laid-Open No. 2011-123729, ATM acquires first data including user biometric information stored in the human body communication module in the human body communication unit via human body communication, and also reads the user's biometric in the reading unit. The personal authentication is performed by directly reading the information to create the second data and collating the biometric information included in each of the first data and the second data.

A first aspect of the present disclosure is a property data receiving apparatus including an authentication unit that performs user authentication and a first communication unit that receives property data when the user authentication is positive.

A second aspect of the present disclosure is a property data transmitting apparatus that communicates with the property data receiving apparatus according to the first aspect, wherein the second communication unit transmits the property data when the personal authentication is affirmed. A property data transmitting apparatus including

A third aspect of the present disclosure is a property data transmission / reception system including the property data receiving apparatus according to the first aspect and the property data transmitting apparatus according to the second aspect.

The fourth aspect of the present disclosure is a property data receiving method that executes user authentication and receives property data when the user authentication is affirmed.

A fifth aspect of the present disclosure is a property data transmission / reception method using a store-side device and a user-side device, and causes the store-side device to acquire (i) first identification data of a user, and (ii) a user The second identification data is received from the user side device, and (iii) the user side authentication is executed using the acquired first identification data and the received second identification data, and the user side device (Iv) A property data transmission / reception method in which property data and the second identification data are recorded in advance, and (v) the property data is transmitted to the store side device when the personal authentication is affirmed. .

A sixth aspect of the present disclosure is a program that causes a computer to execute a process including executing user authentication and receiving property data when the user authentication is positive.

It is a figure which shows an example of schematic structure of the payment system of 1st Embodiment of this indication. It is a block diagram showing an example of the 2nd storage of the account server concerning a 1st embodiment of this indication. It is a block diagram showing an example of important section composition of an electric system of a personal digital assistant concerning a 1st embodiment of this indication. It is a block diagram which shows an example of a principal part structure of the electrical system of the shop front terminal which concerns on 1st Embodiment of this indication. It is a figure which shows an example of the aspect in which the human body communication performed in 1st Embodiment of this indication is performed. It is a figure which shows the structure of the biometric authentication part of the shop front terminal which concerns on 1st Embodiment of this indication. It is the first half of the flowchart which shows an example of the program which CPU of a portable terminal performs regarding the charge process which concerns on 1st Embodiment of this indication. It is the second half of the flowchart which shows an example of the program which CPU of a portable terminal performs regarding the charge process which concerns on 1st Embodiment of this indication. It is the first half of the flowchart which shows an example of the program which CPU of an account server performs regarding the charge process which concerns on 1st Embodiment of this indication. It is the second half of the flowchart which shows an example of the program which CPU of an account server performs regarding the charge process which concerns on 1st Embodiment of this indication. It is a figure which shows an example of the password request | requirement screen displayed on the display of a portable terminal. It is a figure which shows an example of the password re-request screen displayed on the display of a portable terminal. It is a figure which shows an example of the charge amount input screen displayed on the display of a portable terminal. It is a figure which shows an example of the limit excess screen displayed on the display of a portable terminal. It is a figure which shows an example of the account balance shortage screen displayed on the display of a portable terminal. It is a sequence figure showing exchange of information between a personal digital assistant and an account server about charge processing concerning a 1st embodiment of this indication. It is the first half of the flowchart which shows an example of the program which CPU of a shop front terminal performs regarding the payment process which concerns on 1st Embodiment of this indication. It is the latter half of the flowchart which shows an example of the program which CPU of a shop front terminal performs regarding the payment process which concerns on 1st Embodiment of this indication. It is a flowchart which shows the content of the subroutine of the shop front terminal which concerns on an authentication process regarding the payment process which concerns on 1st Embodiment of this indication. It is a flowchart which shows an example of the program which CPU of a portable terminal performs regarding the payment process which concerns on 1st Embodiment of this indication. It is a flowchart which shows the content of the subroutine of the portable terminal which concerns on an authentication process regarding the payment process which concerns on 1st Embodiment of this indication. It is a figure which shows an example of the payment start screen displayed on the display of the shop front terminal. It is a figure which shows an example of the re-imaging instruction | indication screen displayed on the display of a shop front terminal. It is a figure which shows an example of the authentication success screen displayed on the display of the shop front terminal. It is a figure which shows an example of the payment completion screen displayed on the display of the shop front terminal. It is a figure which shows an example of the charge balance shortage screen displayed on the display of the shop front terminal. It is a figure which shows an example of the authentication failure screen displayed on the display of the shop front terminal. It is a sequence figure showing exchange of information between a storefront terminal and a portable terminal about settlement processing concerning a 1st embodiment of this indication. It is a figure which shows the structure of the biometrics authentication part of the shop front terminal which concerns on 2nd Embodiment of this indication. It is a flowchart which shows an example of the program which CPU of a shop front terminal performs regarding the payment process which concerns on 2nd Embodiment of this indication. It is a flowchart which shows an example of the program which CPU of a portable terminal performs regarding the payment process which concerns on 2nd Embodiment of this indication. It is a figure which shows an example of the inquiry screen displayed on the display of the shop front terminal. It is a figure which shows an example of the payment cancellation screen displayed on the display of the shop front terminal. It is a sequence figure showing exchange of information between a storefront terminal and a portable terminal about settlement processing concerning a 2nd embodiment of this indication. It is a flowchart which shows an example of the program which CPU of a portable terminal performs regarding the charge process which concerns on 3rd Embodiment of this indication. It is a flowchart which shows an example of the program which CPU of an account server performs regarding the charge process which concerns on 3rd Embodiment of this indication. It is a sequence figure showing exchange of information between a personal digital assistant and an account server about charge processing concerning a 2nd embodiment of this indication. It is a flowchart which shows the content of the subroutine of the shop front terminal which concerns on an authentication process regarding the payment process which concerns on 3rd Embodiment of this indication. It is a flowchart which shows the content of the subroutine of the portable terminal which concerns on an authentication process regarding the payment process which concerns on 3rd Embodiment of this indication. It is a sequence figure showing exchange of information between a storefront terminal and a portable terminal about settlement processing concerning a 3rd embodiment of this indication. It is a figure which shows the aspect of the update of the vein data recorded on the portable terminal and the account server in 3rd Embodiment of this indication. It is a flowchart which shows the content of the subroutine of the shop front terminal which concerns on an authentication process regarding the payment process which concerns on 4th Embodiment of this indication.

Hereinafter, details of each embodiment of the present disclosure will be described with reference to the drawings.

<First Embodiment>
<System overview>
FIG. 1A shows an overall configuration of a payment system according to the first embodiment of the present disclosure.

The settlement system according to the first embodiment of the present disclosure includes an account server device 1 (hereinafter referred to as “account server 1”), a mobile terminal device 2 (hereinafter referred to as “mobile terminal 2”), and an in-store terminal device 3 ( Hereinafter, “shop front terminal 3”).

In this embodiment, the account server 1 and the mobile terminal 2 communicate via the network 4. Therefore, in this embodiment, at least the account server 1 and the mobile terminal 2 are connected to the network 4. Furthermore, communication between the portable terminal 2 and the storefront terminal 3 is performed as human body communication via the human body 5 as an example.

The storefront terminal 3 shown in FIG. 1A is an example of the “property data receiving device” of the present disclosure. The mobile terminal 2 is an example of the “property data transmission device” of the present disclosure.

FIG. 1A is a functional block diagram showing an example of main functions of the account server 1, the mobile terminal 2, and the storefront terminal 3 according to the first embodiment. Each device functions as each unit shown in the functional block diagram of FIG. 1A when a CPU (Central Processing Unit) executes various programs in each hardware configuration to be described later.

FIG. 1B is a block diagram illustrating an example of the secondary storage device 14 in the electrical configuration of the account server 1 according to the first embodiment. A plurality of individual account areas 111 are provided in a predetermined recording area of the secondary storage device 14. Each of the plurality of individual account areas 111 records account data of a specific individual or corporation.

Although illustration is omitted, the account server 1 is externally configured to transmit and receive data between the portable terminal 2 and the storefront terminal 3 via the CPU, the primary storage unit, and the network 4 similarly to the mobile terminal 2 and the storefront terminal 3 described later. I / F is included and these are connected via a bus (not shown). In the account server 1, the CPU reads out the program (specifically, the charge module shown in FIG. 1B) from the secondary storage device, develops it in the primary storage device, and executes it, so that the CPU is a functional block diagram of FIG. 1A. It functions as the account server charge unit 101 shown in FIG.

Note that the primary storage device means a volatile memory, for example, RAM (Random Access Memory). The secondary storage device means a non-volatile memory, for example, a flash memory or an HDD (Hard Disk Disk Drive).

The account server 1 is a server of a financial institution that records account data of various individuals or corporations. In the account server 1, a CPU (not shown) functions as an account server charge unit, whereby specific individual or corporate account data is recorded in each individual account area 111.

The following explanation is based on personal account data. The account data includes property data indicating the amount of property held by the individual in addition to data for identifying the individual who is the owner (name, address, telephone number, etc.).

In the present embodiment, the account data recorded in the individual account area 111 of the account server 1 particularly includes image data of a finger vein pattern of a predetermined hand of the owner of the individual account area 111. The image data identifies the owner and is used for personal authentication prior to a settlement process according to the present embodiment, which will be described later. Hereinafter, the image data is referred to as vein data.

Note that the predetermined finger of the owner is, for example, an index finger of an arm that is not the owner's dominant arm. However, the present invention is not limited to this.

An individual who is the owner of an account can record vein data for identifying himself / herself in a specific individual account area 111 corresponding to his / her own account. An individual can perform vein data registration work at a financial institution to which the account belongs. In this case, the account server 1 includes an imaging device corresponding to a biometric authentication unit 307 of the storefront terminal 3 to be described later, and can acquire user vein data via this imaging device. Further, for example, vein data may be registered or updated remotely from outside the account server 1 via the network 4.

In this embodiment, each individual account area 111 records single vein data as an example. The individual who is the owner of the account can create new vein data and update the vein data recorded in the individual account area 111.

The external I / F (not shown) of the account server 1 is connected to the network 4.

FIG. 2 is a block diagram showing an example of the main configuration of the electrical system of the mobile terminal 2 according to the first embodiment. As shown in FIG. 2, the mobile terminal 2 includes a CPU 20, a primary storage device 22, a secondary storage device 24, a touch panel display 28 including a touch panel 28 A and a display 28 B, and a human body 5 for performing human body communication described later. An external I / F 42A that transmits / receives data to / from the storefront terminal 3 and an external I / F 42B that transmits / receives data to / from the account server 1 via the network 4. Each unit shown in FIG. 2 of the portable terminal 2 is connected to each other by a bus 26.

In the mobile terminal 2, the CPU 20 reads out each program from the secondary storage device 24, develops it in the primary storage device 22, and executes it, whereby the CPU 20 performs the mobile terminal charging unit 201 shown in the functional block diagram of FIG. It functions as the terminal settlement unit 203. Specifically, the CPU 20 of the mobile terminal 2 functions as the mobile terminal charging unit 201 by executing the charge module shown in FIG. Further, the CPU 20 functions as the mobile terminal payment unit 203 by executing the payment module.

The portable terminal 2 is a portable terminal that is owned and carried by each individual who uses the payment system according to the first embodiment of the present disclosure.

As the mobile terminal 2, as is generally known, a smartphone, a portable personal computer (portable PC), a tablet PC, a smart watch, a wristband, and the like can be considered. As an example, the mobile terminal 2 will be described here by taking a smart watch as an example.

The mobile terminal 2 is connected to the network 4 via an external I / F 42B and a wireless communication line. The wireless communication line is, for example, WiFi, a cellular phone line, or the like.

The network 4 allows two-way communication between the mobile terminal 2 and the account server 1.

The touch panel display 28 of the portable terminal 2 displays various menus, dialogs, and the like on the display 28B, and constitutes an interface with the user. The touch panel display 28 includes a touch panel 28A that accepts an input operation by a user.

The external I / F 42A of the mobile terminal 2 performs communication by human body communication described later. When the finger (human body 5) of the user wearing the mobile terminal 2 contacts a predetermined portion of the storefront terminal 3, data is transmitted and received between the external I / F 42A and the storefront terminal 3.

The secondary storage device 24 of the mobile terminal 2 includes an area for storing property data downloaded from the account server 1 and user-specific biometric information used for biometric authentication, as will be described later.

The mobile terminal 2 in the present embodiment is configured to be able to record property data in the secondary storage device 24. That is, the portable terminal 2 can be precharged with property data in the same manner as a prepaid card known in Japan such as SUICA, PASMO, and Felica. The user can make payment using property data charged in the mobile terminal 2.

The mobile terminal 2 is associated with a specific individual account area 111 of the account server 1. Specifically, in the account server 1, the identification information of the mobile terminal 2 and the address of a specific individual account area 111 in which the user of the mobile terminal 2 is the owner are stored in association with each other. The individual who is the owner of the account pulls out the property data from the specific individual account area 111 of the account server 1 of the financial institution that stores his property and charges it to the mobile terminal 2 that he owns (that is, two Stored in the next storage device 24). As will be described later, this charging process can be performed remotely via the network 4.

Note that the mobile terminal 2 has a limit for charging property data. The limit amount can be determined in consideration of the limit of loss due to accidents such as loss or theft of the mobile terminal 2, and the number of mobile terminals when the user uses a plurality of mobile terminals 2. Recorded in the secondary storage device 24.

Furthermore, vein data (that is, image data of a vein pattern of a predetermined finger of the owner of the individual account area 111) can be recorded in the secondary storage device 24 of the mobile terminal 2 in the present embodiment. As will be described later, in this embodiment, vein data is downloaded from the account server 1 to the portable terminal 2 during the charge processing of property data.

In the present embodiment, as an example, the secondary storage device 24 of the portable terminal 2 has a single vein data corresponding to each individual account area 111 of the account server 1 recording a single vein data. Shall be recorded.

The single vein data recorded in the secondary storage device 24 of the portable terminal 2 can be updated each time a charging process described later is performed.

FIG. 3 is a block diagram showing an example of the main configuration of the electrical system of the storefront terminal 3 according to the first embodiment. As shown in FIG. 3, the storefront terminal 3 is connected to the CPU 30, the primary storage device 32, the secondary storage device 34, the touch panel display 38 including the touch panel 38 A and the display 38 B, and the human body 5 for performing human body communication described later. An external I / F 44A for transmitting / receiving data to / from the portable terminal 2 and a transmission / reception unit 306, and an external I / F 44B for transmitting / receiving data to / from the account server 1 via the network 4. 3 of the storefront terminal 3 are connected to each other by a bus 36.

In the storefront terminal 3, the CPU 30 reads out the program (specifically, the payment module shown in FIG. 3) from the secondary storage device 34, develops it in the primary storage device 32, and executes it. It functions as the storefront terminal payment unit 301 shown in the block diagram.

The touch panel display 38 of the storefront terminal 3 displays various menus, dialogs, and the like on the display 38B to constitute an interface with the user. The touch panel display 38 includes a touch panel 38A that accepts an input operation by a user.

The storefront terminal 3 is a device that is installed at the storefront of a store that provides products or services and performs settlement.

Note that the storefront terminal 3 is not necessarily a stationary device. The store terminal 3 may be, for example, a portable device that a clerk can bring to a customer's seat at a restaurant or the like, or a settlement terminal installed in a basket where a customer collects products to be purchased at a supermarket or a convenience store. Good. As an example, here, the storefront terminal 3 will be described by taking a stationary settlement storefront terminal installed in the store as an example.

The external I / F 44B of the storefront terminal 3 is connected to the network 4 via a communication line. In the present embodiment, the storefront terminal 3 is not necessarily connected to the network 4. Therefore, the storefront terminal according to the present embodiment may not include the external I / F 44B.

Further, the external I / F 44A of the storefront terminal 3 performs human body communication with the portable terminal 2 by performing a predetermined operation described later.

Note that the program of each device does not need to be stored in the secondary storage unit from the beginning. For example, the program can be stored in any portable storage medium such as an HDD (Hard Disk Drive), SSD (Solid State Drive), IC card, magneto-optical disk, CD-ROM, etc. that is connected to each device. You may keep it. Then, the CPU may acquire the program from these portable storage media and execute it. The program may be stored in a storage unit of an external computer such as a computer or a server device connected to each device via a communication line. In this case, the CPU acquires the program from the external computer and executes it.

FIG. 4 shows a mode in which human body communication according to this embodiment is performed.

The mobile terminal 2 as a smart watch is worn on the user's arm. As shown in FIG. 3, the transmission / reception unit 306 of the storefront terminal 3 is connected to the external I / F 44A. When the user's finger 501 belonging to the arm wearing the mobile terminal 2 comes into contact with the transmission / reception unit 306 of the storefront terminal 3, the user's human body (that is, the user's hand and arm) 5 functions as a human body antenna. Human body communication is established between the external I / F 42A and the external I / F 44A of the store terminal 3.

FIG. 5 shows the configuration of the biometric authentication unit 307 of the store terminal 3. The biometric authentication unit 307 is an example of the “acquisition unit” of the present disclosure.

In this embodiment, when the user places the finger 501 at a predetermined position of the biometric authentication unit 307, the above-described human body communication and personal authentication using biometric information (hereinafter referred to as biometric authentication) are performed simultaneously. .

On the upper surface of the storefront terminal 3, two finger guides 310 that are spaced apart by a predetermined distance are provided. Of the two finger guides 310, a part of the transmitting / receiving unit 306 is exposed from the tip of the finger guide 310 arranged in the tip direction (horizontal left direction in FIG. 5). When the user places the finger 501 on the two finger guides 310, a portion between the tip of the finger 501 and the first joint contacts the transmission / reception unit 306, and the store terminal 3 and the portable terminal 2 are connected as described above. Human body communication takes place between them.

A transparent window 311 is provided between the two finger guides 310. Below the transparent window 311, two illumination LEDs 312 that emit near-infrared light for detecting a finger vein pattern are disposed. The illumination LED 312 emits infrared light suitable for detecting a finger vein pattern from different directions, and illuminates a part of the finger 501 through the transparent window 311.

A lens 313 and an image sensor 314 are disposed directly opposite the transparent window 311. A part of the finger 501 illuminated by the illumination LED 312 is imaged on the image sensor 314 by the lens 313. The image sensor 314 captures a vein pattern in a part of the finger 501 and sends it as image data to the secondary storage device 34 of the storefront terminal 3 through wiring not shown. The vein pattern image data imaged by the image sensor 314 is hereinafter referred to as image data.

As will be described later, the CPU 30 of the storefront terminal 3 functions as the storefront terminal settlement unit 301, whereby the vein pattern of the finger 501 in the imaging data recorded in the secondary storage device 34 is obtained in the user's unique data separately acquired. Compared with the vein pattern, identity authentication is performed to determine whether the current user is the original owner of the mobile terminal.

<Charge processing>
Next, the process of charging property data in this embodiment will be described.

In the present embodiment, charging of property data refers to a process of transferring a part or all of personal property data recorded in the individual account area 111 of the account server 1 to the secondary storage device 24 of the portable terminal 2. . Here, as an example, a process of charging property data based on an operation input from the mobile terminal 2 will be described.

6 to 9 are flowcharts showing an example of a processing program for charging property data. 6 and 7 show an example of a processing program executed by the mobile terminal 2, and FIGS. 8 and 9 show an example of a processing program executed by the account server 1.

Here, the processing program executed by the mobile terminal 2 is specifically executed by the CPU 20 of the mobile terminal 2 functioning as the mobile terminal charging unit 201. The processing program executed by the account server 1 is executed by the CPU of the account server 1 (not shown) that functions as the account server charging unit 101. Communication between the portable terminal 2 and the account server 1 is performed via the external I / F 42B of the portable terminal 2 and the network 4 connected to the external I / F (not shown) of the account server 1.

When charging, the user operates the touch panel 28A on the screen 202 of the display 28B of the portable terminal 2 to start up the application software for charging. Thereby, execution of the processing program of the portable terminal 2 shown in FIGS. 6 and 7 is started, and a processing process for charging property data according to the present embodiment is started. Thereafter, the mobile terminal charging unit 201 executes the charging process according to the command of the application software.

In step S 602, the mobile terminal charging unit 201 sends a request for accessing the specific individual account area 111 to the account server 1. The request includes a user-specific ID number stored in the secondary storage device 24 of the mobile terminal 2.

When the account server 1 receives the request from the portable terminal 2, the execution of the processing program of the account server 1 shown in FIGS. 8 and 9 is started. In steps S802 to S806, the account server charge unit 101 identifies the individual account of the user based on the ID number received from the mobile terminal 2, and authenticates the individual account area 111 in which the currently accessed user is identified. Perform identity verification to confirm that you are the owner.

Specifically, identity authentication is performed according to the following flow.

In step S 802, the account server charging unit 101 sends a password request to the mobile terminal charging unit 201. In step S604, the mobile terminal charging unit 201 receives the password request. In step S606, the mobile terminal charging unit 201 displays a password request screen for entering a password as the screen 202 on the display 28B.

Fig. 10 shows an example of the password request screen. The password request screen includes a message display area 202a, an account number display area 202b, a password input area 202c, and a soft keyboard 202d.

In the message display area 202a, a message prompting the user to input a password is displayed. As an example, a message “Please enter your password” is displayed. In the account number display area 202b, the account number of the account of the financial institution corresponding to the specific individual account area 111 that the user desires to access is displayed. A password input by a user operation is displayed in the password input area 202c.

The soft keyboard 202d includes, for example, a numeric keypad, an ENTER key, an EXIT key, and a DELETE key (displayed as X in FIG. 10). When the user presses the numeric keypad, a number corresponding to the pressed key is input and displayed in the password input area 202c. When the user presses the ENTER key, the input of the numeric string displayed in the password input area 202c is confirmed. When the user presses the DELETE key, the number displayed in the password input area 202c is deleted.

When the password request screen is displayed as the screen 202 on the display 28B of the portable terminal 2, the user is displayed in the account number display area 202b using the soft keyboard 202d according to the message displayed in the message display area 202a. Enter the password corresponding to the account number.

In step S608, the mobile terminal charging unit 201 acquires the input password. In step S 610, the mobile terminal charging unit 201 transmits the acquired password to the account server 1.

When the account server charging unit 101 receives a password from the mobile terminal 2, the determination as to whether or not the password has been received from the mobile terminal 2 is affirmative in step S804. In this case, in step S806, the account server charge unit 101 checks the received password against the password recorded in the specified individual account area 111, so that the current user is the genuine owner of the individual account area 111. It is confirmed whether or not.

If the password received by the account server charge unit 101 from the mobile terminal 2 is different from the password recorded in the individual account area 111, the determination in step S806 is negative. In this case, the process of FIG. 8 returns to S802, and the account server charge unit 101 sends a password request to the mobile terminal 2 again. When the portable terminal charging unit 201 receives the password request again, the determination as to whether or not data has been received from the account server 1 is affirmative in step S612. Subsequently, in step S614, the determination as to whether or not the received data is a password request again is affirmative. In this case, the process of FIG. 6 proceeds to step S618, and the portable terminal charging unit 201 displays a password re-request screen as the screen 202 on the display 28B, and prompts the user to re-enter the password. Next, the processing of FIG. 6 returns to step S608, and steps S608 to S610 are executed again.

Fig. 11 shows an example of the password re-request screen. Similar to the password request screen shown in FIG. 10, the password re-request screen includes a message display area 202a, an account number display area 202b, a password input area 202c, and a soft keyboard 202d.

In the message display area 202a, a message prompting the user to re-enter the password is displayed. As an example, the message “The password you entered is incorrect. Please enter your password again.” Is displayed. The account number display area 202b, the password input area 202c, and the soft keyboard 202d function in the same manner as the password request screen shown in FIG.

When the steps S608 to S610 are executed again, the password is input again and transmitted from the portable terminal charging unit 201 to the account server 1 again.

When the account server charge unit 101 receives the password from the portable terminal 2 again, an affirmative determination is made in step S804, and the processing in FIG. 8 proceeds to step S806 again. In step S806, when the account server charge unit 101 confirms that the two verified passwords match, the personal authentication is affirmed. In this case, in step S808, the account server charge unit 101 reads the balance data and the biometric authentication vein data from the specified individual account area 111 and sends them to the portable terminal 2. And the process of the account server charge part 101 transfers to FIG.

When the portable terminal charging unit 201 receives the balance data and the vein data, an affirmative determination is made in step S612, and a negative determination is subsequently made in step S614. In this case, in step S616, the mobile terminal charging unit 201 records the received balance data and vein data in the secondary storage device 24. Subsequently, the processing of the mobile terminal charging unit 201 proceeds to FIG. 7, and in step S702, the mobile terminal charging unit 201 reads the charge balance and balance data recorded in the secondary storage device 24, and displays the screen on the display 28B. A charge amount input screen is displayed as 202.

FIG. 12 shows an example of the charge amount input screen. The charge amount input screen includes an account balance display area 202e, a charge balance display area 202f, a charge amount input area 202g, and a soft keyboard 202d.

The account balance display area 202e displays the balance of the account of the financial institution corresponding to the specific individual account area 111 accessed by the user. The charge balance display area 202 f displays the amount currently charged in the mobile terminal 2 recorded in the secondary storage device 24 of the mobile terminal 2. The charge amount input area 202g displays the amount input by the user operating the soft keyboard 202d. The soft keyboard 202d functions in the same manner as the password request screen shown in FIG.

When the charge amount input screen is displayed as the screen 202 on the display 28B of the portable terminal 2, the user can read the balance amount of the account displayed in the account balance display area 202e and the portable terminal displayed in the charge balance display area 202f. In consideration of the current charge amount of 2, the soft keyboard 202d is used to input the amount of money desired to be charged this time in the charge amount input area 202g.

Although not shown in the flowchart of FIG. 7, if the user desires to stop the charging operation on the charge amount input screen, the user ends the process by pressing the EXIT key of the soft keyboard 202d. be able to.

When the input of the charge amount is completed, the portable terminal charging unit 201 acquires the input charge amount in step S704. In step S 706, the mobile terminal charging unit 201 calculates a total amount obtained by adding the input charge amount and the charge balance recorded in the secondary storage device 24. In step S 708, the mobile terminal charging unit 201 compares the calculated total amount with a limit amount set in advance in the mobile terminal 2.

If the total amount is equal to or less than the limit amount, the determination in step S708 is negative, and the process in FIG. 7 proceeds to step S710. In step S 710, the mobile terminal charging unit 201 transmits the input charge amount to the account server 1.

In step S902 in FIG. 9, the account server charge unit 101 receives the charge amount. In step S 904, the account server charge unit 101 determines whether or not the received charge amount is larger than the balance data in the individual account area 111.

If the charge amount is less than or equal to the balance data in the individual account area 111, the determination in step S904 is negative. In this case, in step S 906, the account server charge unit 101 transmits property data for the charge amount to the mobile terminal 2. In step S 908, the account server charge unit 101 calculates a subtraction amount obtained by subtracting the charge amount from the balance data in the individual account area 111. In step S910, the account server charge unit 101 replaces the calculated subtraction amount with new balance data and records it in the individual account area 111. Thereby, the execution of the processing program of the account server charge unit 101 shown in FIGS. 8 and 9 ends (END in FIG. 9).

When the portable terminal charging unit 201 receives property data for the amount of charge from the account server 1, the determination as to whether or not the data has been received from the account server 1 is affirmative in step S712. Subsequently, in step S714, the determination as to whether the received data is insufficient balance information is negative. In this case, the process in FIG. 7 proceeds to step S716. In step S716, the mobile terminal charging unit 201 adds the amount of property data corresponding to the charge amount to the charge balance recorded in the secondary storage device 24 (that is, the total amount calculated in S706) as new property data. The charge balance is recorded in the secondary storage device 24.

On the other hand, when the total amount of the charge amount and the charge balance exceeds the limit amount set in advance in the portable terminal 2, the determination in step S708 is affirmative, and the processing in FIG. 7 proceeds to step S718. In step S718, the mobile terminal charging unit 201 calculates the excess amount exceeding the limit amount and displays a limit amount excess screen as the screen 202 on the display 28B. Thereafter, the processing of FIG. 7 returns to step S704, and steps S704 to S706 are executed again.

Fig. 13 shows an example of the limit excess screen. The limit amount excess screen includes a message display area 202a, an excess amount display area 202h, a modified charge amount input area 202i, and a soft keyboard 202d.

In the limit exceeded screen, the message display area 202a displays a message indicating that the limit has been exceeded. As an example, a message “The charge balance after charging exceeds the limit” is displayed. The excess amount display area 202h displays the excess amount exceeding the limit amount. The soft keyboard 202d functions in the same manner as the password request screen shown in FIG.

In the corrected charge amount input area 202i, a message prompting the user to correct the charge amount is displayed, and the corrected charge amount is input by the user operating the soft keyboard 202d. When the limit amount excess screen is displayed, the maximum value of the chargeable amount calculated by dividing the current charge balance from the limit amount is displayed in advance in the corrected charge amount input area 202i. . The user inputs the corrected charge amount by correcting this maximum value. Therefore, after the limit amount excess screen is displayed, if the user inputs the ENTER key without correcting the amount, charging up to the limit amount is instructed.

By executing steps S704 to S706 again, the charge amount is input again, and the total amount obtained by adding the input charge amount and the charge balance recorded in the secondary storage device 24 is calculated again. Thereafter, the determination is performed again in step S708.

If the charge amount transmitted from the mobile terminal 2 to the account server charge unit 101 exceeds the balance data in the individual account area 111, the determination in step S904 is affirmative, and the process in FIG. 9 proceeds to step S912. Transition. In step S 912, the account server charge unit 101 calculates a shortage amount exceeding the balance data, and transmits account balance shortage information to the mobile terminal 2. The account balance shortage information includes a message that the balance data has been exceeded and information on the shortage amount. In this case, the balance data recorded in the individual account area 111 is not changed.

When the mobile terminal charging unit 201 receives the account balance shortage information from the account server 1, the determination in step S712 is a positive determination, and the determination in step S714 is a positive determination. In this case, the process in FIG. 7 proceeds to step S720. In step S720, the mobile terminal charging unit 201 displays an account balance shortage screen as the screen 202 on the display 28B, and prompts the user to re-enter the charge amount. Thereafter, the processing of FIG. 7 returns to step S704, and steps S704 to S710 are executed again.

FIG. 14 shows an example of an account balance shortage screen. The account balance shortage screen includes a message display area 202a, a shortage amount display area 202j, a corrected charge amount input area 202i, and a soft keyboard 202d.

On the account balance shortage screen, the message display area 202a displays a message indicating that the account balance is insufficient. As an example, the message “Account balance is insufficient” is displayed. The shortage amount display area 202j displays a shortage amount corresponding to an amount in which the input charge amount exceeds the account balance recorded in the individual account area 111. The soft keyboard 202d functions in the same manner as the password request screen shown in FIG.

In the corrected charge amount input area 202i, a message prompting the user to correct the charge amount is displayed, and the corrected charge amount is input by the user operating the soft keyboard 202d. When the account balance shortage screen is displayed, the current charge of the account balance as the maximum chargeable amount is displayed in advance in the corrected charge amount input area 202i. The user inputs the corrected charge amount by correcting this maximum value. Accordingly, after the account balance shortage screen is displayed, if the user inputs the ENTER key without correcting the amount, the user is instructed to charge up to the current account balance amount.

By executing steps S704 to S710 again, the charge amount is input again, and the total amount obtained by adding the input charge amount and the charge balance recorded in the secondary storage device 24 is calculated again, and the charge amount is calculated. Is transmitted to the account server 1 again.

When the account server charge unit 101 receives the charge amount again from the mobile terminal 2, the determination in step S914 in FIG. In this case, the process in FIG. 9 returns to step S904. In step S904, it is determined again whether the received charge amount is larger than the balance data of the individual account area 111.

With respect to the charge processing according to the first embodiment of the present disclosure described above, FIG. 15 is a sequence diagram illustrating information exchange between the mobile terminal 2 and the account server 1. Each step shown in FIG. 15 corresponds to each step in FIGS. Note that, for convenience of illustration, in FIG. 15, branches existing during the charging process are omitted. Specifically, for mobile terminal 2, a case where an affirmative determination is made in any of step S614, step S708, and step S714 is omitted. Similarly, for the account server 1, a case of either a negative determination in step S806 and an affirmative determination in step S904 is omitted.

<Payment processing>
Next, a process when the user receives a product or service and performs payment for the payment at the store terminal 3 will be described.

FIGS. 16 to 20 are flowcharts showing an example of a processing program for performing settlement in the present embodiment. 16 to 18 show an example of a processing program executed by the store terminal 3, and FIGS. 19 and 20 show an example of a processing program executed by the mobile terminal 2. In the following, for the convenience of explanation, the entire payment process is described in three parts: (1) before the authentication process, (2) the authentication process subroutine, and (3) after the authentication process.

Here, the processing program executed by the storefront terminal 3 is specifically executed by the CPU 30 of the storefront terminal 3 functioning as the storefront terminal settlement unit 301. The processing program executed by the mobile terminal 2 is specifically executed by the CPU 20 of the mobile terminal 2 functioning as the mobile terminal settlement unit 203. Further, communication between the storefront terminal 3 and the mobile terminal 2 is performed by human body communication via the user's human body 5 by the external I / F 44A and the transmitting / receiving unit 306 of the storefront terminal 3 and the external I / F 42A of the mobile terminal 2. As done.

[Payment process 1: Before authentication process]
It is assumed that a user who has purchased a product or service wants to pay the price through payment using property data by the mobile terminal 2. In that case, the fact is input to the storefront terminal 3 in some form, for example, by the operation of the user or the store clerk. As a result, execution of the processing program of the storefront terminal 3 shown in FIGS. 16 to 18 is started, and a processing process for performing settlement according to the present embodiment is started. Note that the storefront terminal 3 may be set to automatically start the payment processing process. In other words, unless the store terminal 3 is specifically instructed not to pay by payment using property data by the mobile terminal 2, the price of goods or services will be paid by payment using property data by the mobile terminal 2. May be set. Hereinafter, the storefront terminal payment unit 301 executes a payment process.

In step S1602, the store terminal payment unit 301 displays a payment start screen as a screen 302 on the display 38B.

FIG. 21 shows an example of the settlement start screen. The settlement start screen includes a payment amount display area 302a, a message display area 302b, a breakdown display area 302c, and a scroll bar 302d.

On the settlement start screen, the payment amount display area 302a displays the consideration for the product or service purchased by the user. The message display area 302b displays a message prompting the user to make a payment. As an example, a message “Please pay with your finger on the finger guide if you like” is displayed. The breakdown display area 302c displays a breakdown of the price displayed in the payment amount display area 302a. Here, it is assumed that all of the breakdowns cannot be displayed at once in the breakdown display area 302c. In this case, the user may read the entire breakdown by scrolling the scroll bar 302d as necessary.

The user confirms the payment amount and the breakdown on the payment start screen, places the finger 501 belonging to the arm wearing the mobile terminal 2 on the finger guide 310 of the biometric authentication unit 307 of the storefront terminal 3, and is provided on the finger guide 310. The finger 501 is brought into contact with the transmission / reception unit 306 (see FIG. 5). By this operation, as described above, human body communication is started between the external I / F 44A of the storefront terminal 3 using the human body 5 as an antenna and the external I / F 42A of the portable terminal 2.

When the storefront terminal payment unit 301 detects the contact of the finger 501 with the biometric authentication unit 307, the determination as to whether or not the contact with the biometric authentication unit 307 has been detected becomes an affirmative determination in step S1604. In this case, the process in FIG. 16 proceeds to step S1606 via step S1605. In step S 1605, the storefront terminal payment unit 301 transmits contact detection information to the mobile terminal 2.

When the mobile terminal 2 receives the contact detection information, execution of the processing program of the mobile terminal 2 shown in FIGS. 19 and 20 is started (START in FIG. 19). Hereinafter, the mobile terminal payment unit 203 executes a payment process.

In step S1606, the storefront terminal payment unit 301 executes an authentication process. Thereafter, the processing of FIG. 16 proceeds to the authentication process subroutine of FIG. In step S1902 in FIG. 19 corresponding to step S1606 in FIG. 16, the mobile terminal settlement unit 203 executes an authentication process. Thereafter, the processing of FIG. 19 proceeds to the authentication process subroutine of FIG. The authentication process subroutine is the second stage of the settlement process of this embodiment.

[Payment process 2: Authentication process subroutine]

The authentication process in the settlement processing of the present embodiment is illustrated in FIGS. 18 and 20 as a subroutine. FIG. 18 is a subroutine showing an example of a processing program executed by the CPU 30 as the storefront terminal payment unit 301, and FIG. 20 is a subroutine showing an example of a processing program executed by the CPU 20 as the mobile terminal payment unit 203.

In FIG.18 S1802, the shop front terminal payment part 301 resets F and G by substituting 0 to the variables F and G memorize | stored in the secondary memory | storage device 34, respectively.

Here, F is an integer representing the number of authentication attempts. In the present embodiment, when the biometric authentication failure is repeated a predetermined number of times, the authentication failure is confirmed and settlement is not performed. In FIG. 18, as an example, it is assumed that authentication can be performed up to five times.

G is a binary variable representing success or failure of authentication in the in-store terminal settlement unit 301. In the RETURN of FIG. 18, when the authentication process subroutine of the in-store terminal settlement unit 301 ends, if G = 0, the authentication is successful, and if G = 1, the authentication fails.

In step S1804, the shop terminal payment unit 301 transmits a request for vein data to the mobile terminal 2.

Upon receiving this request, the mobile terminal settlement unit 203 starts an authentication process subroutine (START in FIG. 20). In step S2002, the mobile terminal settlement unit 203 substitutes 0 for a variable H stored in the secondary storage device 24.

H is a binary variable indicating success or failure of authentication in the mobile terminal settlement unit 203. In the RETURN of FIG. 20, when the authentication process subroutine of the mobile terminal settlement unit 203 is completed, if H = 0, the authentication succeeds, and if H = 1, the authentication fails.

In step S2004, the mobile terminal settlement unit 203 reads the requested vein data from the secondary storage device 24 and transmits it to the store terminal 3.

In FIG.18 S1806, the shop front terminal payment part 301 receives vein data from the portable terminal 2, and records it on the secondary storage device 34. FIG.

In step S1808, the storefront terminal payment unit 301 executes the following processing. The storefront terminal payment unit 301 images the contact object in contact with the finger guide 310 in the biometric authentication unit 307 and records the image data in the secondary storage device 34. As described above, the finger 501 of the user wearing the mobile terminal 2 is in contact with the transmission / reception unit 306 provided in the finger guide 310 of the biometric authentication unit 307 of the store terminal 3 (S1604, see FIG. 5).

The processing executed by the shop terminal payment unit 301 in S1808 is specifically as follows. The lens 313 shown in FIG. 5 forms an image of the vein pattern of the user's finger 501 illuminated by the illumination LED 312 on the image sensor 314, and the image sensor 314 images the vein pattern to obtain the image data. Record in the next storage device 34.

In step S1810, the storefront terminal payment unit 301 reads the image data captured by the image sensor 314 and the vein data received from the mobile terminal 2 from the secondary storage device 34, and compares the vein patterns included in the two data. To do. Comparing and collating the vein patterns included in the above two data is performing authentication of whether or not the current user is the person in the present embodiment.

If the vein patterns included in the two data match as a result of the collation, the determination of whether or not the two patterns match (that is, whether or not the current user is the user) is affirmative in step S1812. Judgment. In this case, the process in FIG. 18 proceeds to step S1814.

In step S1814, the storefront terminal payment unit 301 transmits authentication success information to the mobile terminal 2. Then, the storefront terminal payment unit 301 holds G = 0 (that is, authentication success) and ends the authentication process subroutine (RETURN in FIG. 18).

On the other hand, if the vein patterns included in the two data do not match as a result of the collation in S1810, the determination in step S1812 is negative. In this case, the process in FIG. 18 proceeds to step S1816.

In step S1816, the shop terminal payment unit 301 adds 1 to the variable F recorded in the secondary storage device. For example, if it is after the first authentication, since F = 0 is recorded in the secondary storage device 34 in step S1802, the variable F = 1 is newly added to the secondary storage device 34 by adding 1 in S1816. To be recorded.

In S1818, for variable F, a determination is made as to whether F = 5. As described above, the value of 5 is an example of the maximum number of biometric authentication attempts in the present embodiment.

If F is not equal to 5, the determination in S1818 is a negative determination. In this case, the process in FIG. 18 proceeds to step S1820. In step S1820, the shop terminal payment unit 301 displays a re-imaging instruction screen as a screen 302 on the display 38B. Then, the processing of FIG. 18 returns to step S1808, and steps S1808 to S1818 are executed again.

FIG. 22 shows an example of the re-imaging instruction screen. The re-imaging instruction screen includes a message display area 302b. In the re-imaging instruction screen, the message display area 302b displays a message indicating that the authentication has not been successful and prompting the finger 501 to be imaged again.

By executing steps S1808 to S1818 again, the imaging data related to the vein pattern of the user's finger 501 is captured again, and the vein pattern included in the imaging data and the vein data received from the portable terminal 2 is compared and verified again. . Furthermore, when the determination in S1812 is negative again, 1 is added to the variable F, and the determination as to whether F = 5 is performed again.

Unless the determination in step S1812 is affirmative, the processes in steps S1808 to S1818 are repeated. That is, vein pattern imaging and comparison / collation of imaging data and vein data are repeated. Each time a negative determination is made in step S1812 (that is, matching fails), 1 is added to the variable F in step S1816.

In the process of repeating the process as described above, if F = 5 is confirmed, the determination in S1818 is an affirmative determination. Thereby, the failure of the biometric authentication in this embodiment is decided.

In this case, the processing in FIG. 18 proceeds to step S1822. In step S1822, the storefront terminal payment unit 301 transmits authentication failure information to the mobile terminal. Subsequently, in step S1824, the shop terminal payment unit 301 substitutes 1 for a variable G recorded in the secondary storage device 34, holds G = 1 (that is, authentication failure), and ends the authentication process subroutine. (RETURN in FIG. 18).

As described above, the subroutine executed by the storefront terminal settlement unit 301 shown in FIG. 18 transmits authentication success information or authentication failure information to the mobile terminal 2 in step S1814 or S1822, and records it in the secondary storage device 34. With respect to the variable G being set, G = 0 (corresponding to authentication success) or G = 1 (corresponding to authentication failure) is given, and the processing is terminated (RETURN in FIG. 18).

On the other hand, after transmitting the vein data to the storefront terminal 3 in S2004 of FIG. 20, the mobile terminal settlement unit 203 waits for the authentication process result to be transmitted from the storefront terminal 3.

When the mobile terminal settlement unit 203 receives the authentication success information from the storefront terminal 3 within the predetermined time, in step S2006, the determination as to whether the authentication success information has been received within the predetermined time is an affirmative determination. In this case, the mobile terminal settlement unit 203 holds H = 0 (that is, authentication success) for the variable H stored in the secondary storage device 24 and ends the authentication process subroutine (RETURN in FIG. 20).

As long as the mobile terminal settlement unit 203 does not receive either authentication success information or authentication failure information from the store terminal 3, the determination in S2006 is a negative determination, and the determination in S2008 is a negative determination. Keeps waiting for.

On the other hand, when the mobile terminal settlement unit 203 receives the authentication failure information from the storefront terminal 3, the determination in step S2006 is a negative determination, and in step S2008, the determination whether the authentication failure information is received from the storefront terminal 3 is affirmative. Judgment. In this case, the process in FIG. 20 proceeds to step S2010.

In step S2010, the mobile terminal settlement unit 203 substitutes 1 for a variable H recorded in the secondary storage device 24. Then, the mobile terminal settlement unit 203 holds H = 1 (that is, authentication failure) and ends the authentication process subroutine (RETURN in FIG. 20).

As described above, the subroutine executed by the mobile terminal settlement unit 203 shown in FIG. 20 is H = 0 (corresponding to the authentication success) or H = 1 (for the variable H recorded in the secondary storage device 24). (Responding to authentication failure) is given and the process is terminated (RETURN in FIG. 20).

When G = 0 is obtained for the in-store terminal settlement unit 301 as a result of the authentication process subroutine, H = 0 is obtained for the mobile terminal settlement unit 203, and G = 1 is obtained for the over-the-counter settlement unit 301. Note that H = 1 is obtained for the mobile terminal settlement unit 203.

[Payment process 3: After authentication process]
As described above, when the processing of the authentication process is completed, the storefront terminal payment unit 301 holds G = 0 (corresponding to authentication success) or G = 1 (corresponding to authentication failure), and the mobile terminal payment unit 203 H = 0 (corresponding to authentication success) or H = 1 (corresponding to authentication failure) is held. In response to this result, the storefront terminal payment unit 301 and the mobile terminal payment unit 203 execute the third stage of the payment process.

First, the case of G = 0 (H = 0) will be described.

When G = 0 is obtained as a result of the authentication process subroutine shown in FIG. 18, in step S1608 of FIG. 16, the determination as to whether or not the authentication is successful is an affirmative determination. In this case, the process in FIG. 16 proceeds to step S1610.

In step S1610, the storefront terminal payment unit 301 displays an authentication success screen as a screen 302 on the display 38B. FIG. 23 shows an example of the authentication success screen. The authentication success screen includes a message display area 302b. On the authentication success screen, the message display area 302b displays a message indicating that the authentication is successful and that the payment process is being executed.

In step S1612, the in-store terminal settlement unit 301 transmits a request for property data corresponding to the payment amount as a price for the provision of the product or service to the mobile terminal 2. Thereafter, the processing of the storefront terminal payment unit 301 shifts to FIG. The payment amount is displayed on the settlement start screen in FIG. 21 in step S1602.

Since the case of G = 0 is considered now, as described above, H = 0 is obtained for the mobile terminal settlement unit 203 as a result of the authentication process subroutine. Accordingly, in S1904 of FIG. 19, the determination as to whether or not the authentication has succeeded is affirmative. In this case, the processing in FIG. 19 proceeds to step S1906.

In step S1906, the mobile terminal settlement unit 203 receives the property data request from the storefront terminal 3. In step S1908, the mobile terminal settlement unit 203 reads the charge balance recorded in the secondary storage device 24, and calculates a subtraction amount obtained by subtracting the requested payment amount from the charge balance. In step S1910, the mobile terminal settlement unit 203 determines whether or not the subtraction amount is 0 or more using the calculated subtraction amount.

If the subtraction amount is 0 or more, the determination of whether or not the subtraction amount is 0 or more is affirmative in step S1910. In this case, the processing in FIG. 19 proceeds to step S1912.

In step S1912, the mobile terminal settlement unit 203 transmits property data corresponding to the requested payment amount to the store terminal 3.

In subsequent step S1914, the portable terminal settlement unit 203 records the subtraction amount as a new charge balance in the secondary storage device 24, and ends the settlement process (END in FIG. 19).

On the other hand, the storefront terminal payment unit 301 transmits a request for property data to the mobile terminal 2 in step S1612, and then waits for reception of data from the mobile terminal 2.

When store terminal payment unit 301 receives property data from portable terminal 2, the determination as to whether or not the data has been received from portable terminal 2 is affirmative in step S1702 of FIG. 17, and the received data is charged in step S1704. The determination of whether or not the balance shortage information is a negative determination. In this case, the process in FIG. 17 proceeds to step S1706.

In step S 1706, the storefront terminal settlement unit 301 records the property data received from the mobile terminal 2 in the secondary storage device 34. As a result, the user pays the store terminal 3 using the property data charged in advance in the portable terminal 2.

In subsequent step S1708, the shop terminal payment unit 301 displays a payment completion screen as a screen 302 on the display 38B. FIG. 24 shows an example of the payment completion screen. The payment completion screen includes a message display area 302b. On the payment completion screen, the message display area 302b displays a message indicating that payment has been completed.

In S1710, the storefront terminal payment unit 301 deletes the imaging data and vein data recorded in the secondary storage device 34, and completes the payment process (END in FIG. 17). By erasing two types of data each time payment is completed, personal information such as a finger vein pattern can be prevented from being misused or misused.

On the other hand, if the subtraction amount calculated in step S1908 in FIG. 19 is a value smaller than 0, the determination in step S1910 is negative. In this case, the processing in FIG. 19 proceeds to step S1916.

In step S1916, the mobile terminal settlement unit 203 transmits the charge balance shortage information to the store terminal 3 and ends the settlement process (END in FIG. 19). In this case, property data is not transmitted from the portable terminal 2 to the storefront terminal 3.

When the shop terminal payment unit 301 receives the insufficient charge balance information from the mobile terminal 2, the determination in step S1702 in FIG. 17 is affirmative, and the determination in step S1704 is subsequently affirmative. In this case, the process in FIG. 17 proceeds to step S1712.

In step S1712, the storefront terminal payment unit 301 displays a charge balance shortage screen as a screen 302 on the display 38B. FIG. 25 shows an example of a charge balance shortage screen. The charge balance shortage screen includes a message display area 302b. In the insufficient charge balance screen, the message display area 302b displays a message indicating that payment cannot be made because the property data charged in the mobile terminal 2 is less than the current payment amount. Further, the message display area 302b on the insufficient charge balance screen may display a message prompting the user to pay by another method.

Subsequently, the processing of FIG. 17 proceeds to step S1710. In step S1710, the storefront terminal payment unit 301 deletes the imaging data and vein data recorded in the secondary storage device 34, and completes the payment process (END in FIG. 17). In this case, since the store terminal 3 has not received property data necessary for payment, the payment is not completed. Therefore, it is preferable that the storefront terminal 3 includes means for prompting the user to complete payment.

So far, the case of G = 0 (that is, H = 0) has been described. Second, the process when G = 1 (that is, H = 1) will be described.

When G = 1 is obtained as a result of the authentication process subroutine shown in FIG. 18, in step S1608 in FIG. 16, the determination as to whether or not the authentication is successful is negative. In this case, the process in FIG. 16 proceeds to step S1614.

In step S1614, the storefront terminal settlement unit 301 displays an authentication failure screen as the screen 302 on the display 38B. Subsequently, the processing of the storefront terminal settlement unit 301 shifts to FIG.

FIG. 26 shows an example of an authentication failure screen. The authentication failure screen includes a message display area 302b. On the authentication failure screen, the message display area 302b displays a message indicating that the authentication has failed and that the payment processing is to be stopped.

After the authentication failure screen is displayed in step S1614, the storefront terminal payment unit 301 deletes the imaging data and vein data (S1710), and ends the payment process (END in FIG. 17). In this case, as in the case where the charge balance is insufficient, the store terminal 3 has not received the property data necessary for payment, and thus payment has not been completed.

Since the case of G = 1 is considered now, as described above, H = 1 is obtained for the mobile terminal settlement unit 203 as a result of the authentication process subroutine. Therefore, in S1904 of FIG. 19, the determination as to whether or not the authentication is successful is a negative determination. In this case, the mobile terminal payment unit 203 ends the payment process (END in FIG. 19). In this case, property data is not transmitted from the portable terminal 2 to the store terminal 3 as in the case of insufficient charge balance.

FIG. 27 is a sequence diagram showing exchange of information between the storefront terminal 3 and the portable terminal 2 regarding the settlement processing according to the first embodiment of the present disclosure described above. Each step shown in FIG. 27 corresponds to each step in FIGS. It should be noted that for convenience of illustration, in FIG. 27, branches existing during the settlement process are omitted. Specifically, for the storefront terminal 3, a case where a negative determination in step S1608, an affirmative determination in step S1704, or a negative determination in step S1812 is omitted. Similarly, for the mobile terminal 2, a case of either a negative determination in step S1904 or step S1910 and an affirmative determination in step S2008 is omitted.

According to the present embodiment, biometric authentication for user authentication is performed using human body communication between the mobile terminal 2 and the storefront terminal 3 via the human body 5 of the user wearing the mobile terminal 2. When the biometric authentication is successful, the property data is transmitted from the portable terminal 2 to the storefront terminal 3. With this configuration, it is possible to execute a payment of a price for a product or service purchased by a user by a simple operation as a settlement using property data charged in the mobile terminal 2.

Further, in the present embodiment, vein data for biometric authentication is transmitted from the portable terminal 2 to the storefront terminal 3 each time a payment is made, and the vein data is deleted from the storefront terminal 3 after the settlement is completed. With this configuration, it is possible to prevent misuse such as the store terminal 3 incorrectly applying another person's vein pattern.

Furthermore, in this embodiment, the vein data recorded in the secondary storage device 24 of the mobile terminal 2 is transmitted from the account server 1 to the mobile terminal 2 when the property data is charged. With this configuration, even when the vein pattern changes due to aging or disease, a plurality of mobile phones corresponding to the individual account area can be corrected by correcting the vein pattern recorded in the individual account area 111 of the account server 1. The vein data of the terminal 2 can be updated.

Second Embodiment
Next, a second embodiment of the present disclosure will be described. In addition, about the part which is the structure similar to 1st Embodiment, the same code | symbol is attached | subjected and description is abbreviate | omitted.

<System overview>
FIG. 28 illustrates a configuration of the biometric authentication unit 307a according to the second embodiment of the present disclosure. In the biometric authentication unit 307a of this embodiment, the finger guide 310 arranged in the distal direction (horizontal left direction in FIG. 5) of the two finger guides is replaced with the transmission / reception unit 306 of the first embodiment. A rod 306a is disposed. In this embodiment, the rod 306a functions as an antenna (portion in contact with the human body) of the human body communication transmitting / receiving unit. That is, the rod 306a of this embodiment substitutes for the function of the transmission / reception unit 306 of the first embodiment.

The rod 306a is fitted to one of the finger guides 310 so as to be vertically movable in the vertical direction, and is urged vertically upward by a spring (not shown). A switch 316 is disposed below the rod 306a. When the rod 306a is pressed against the spring, the switch 316 changes from off to on, thereby detecting that the rod 306a is pressed.

<Payment processing>
29 and 30 are flowcharts illustrating an example of a processing program for performing settlement in the present embodiment. FIG. 29 shows an example of a processing program executed by the CPU 30 as the storefront terminal payment unit 301, and FIG. 30 shows an example of a processing program executed by the CPU 20 as the mobile terminal payment unit.

The processing executed by the storefront terminal payment unit 301 shown in FIG. 29 differs from the processing of the first embodiment shown in FIGS. 16 and 17 in that the data received in step S1704 is insufficient charge balance information. If the determination is NO, the process proceeds to step S1706 to execute payment (that is, the storefront terminal payment unit 301 records the property data received from the portable terminal 2 in the secondary storage device 34). Instead, the processing in steps S2902 to S2910 is executed to inquire the user whether or not settlement is possible.

In addition, corresponding to steps S2902 to S2910 in FIG. 29, the process executed by the mobile terminal settlement unit 203 shown in FIG. 30 is different from the process of the first embodiment shown in FIG. 19 in the following points. That is, if the determination in step S1910 is whether or not the subtraction amount is 0 or more is an affirmative determination, the process proceeds to step S1912, and the property data is not transmitted to the store terminal 3, but steps S3002 to S3006 are performed. Execute the process.

Hereinafter, the description starts from a case where the determination in step S1904 in FIG. 30 is affirmative. In this case, the processing in FIG. 30 proceeds to step S3002.

In step S3002, the mobile terminal settlement unit 203 transmits the inquiry information to the storefront terminal 3. When the inquiry information is received, the store terminal payment unit 301 according to the present embodiment inquires of the user whether the payment is possible.

Specifically, when in-store terminal settlement unit 301 receives inquiry information from portable terminal 2, in step S1702 in FIG. 29, it is determined whether or not data has been received from portable terminal 2, and then in step S1704. The determination whether the received data is insufficient charge balance information is a negative determination. In this case, the processing in FIG. 29 proceeds to step S2902.

In step S2902, the in-store terminal settlement unit 301 displays an inquiry screen as a screen 302 on the display 38B, and substitutes 0 for a variable T1 recorded in the secondary storage device 34 to start a soft timer.

The variable T1 indicates the time that has elapsed since the inquiry screen was displayed. When the soft timer is activated, the elapsed time T1 is measured.

FIG. 31 shows an example of an inquiry screen. The inquiry screen includes a message display area 302b, a payment amount display area 302e, and an approval message display area 302f. In the inquiry screen, the message display area 302b displays a message indicating that preparation for payment has been completed, the payment amount display area 302e displays the consideration (ie, payment amount), and the approval message display area 302f approves the current transaction. Display an inquiry message about whether or not to settle.

When the user wishes to approve the transaction and execute settlement, the user applies a force downward in the vertical direction with the finger 501 and presses the rod 306a with which the finger 501 is contacting against the repulsive force of the spring (see FIG. 28). As a result, the switch 316 of the biometric authentication unit 307a changes from off to on and detects pressing of the rod 306a.

The shop terminal payment unit 301 waits for the switch 316 of the biometric authentication unit 307a to detect the pressing of the rod 306a until a predetermined time elapses after the execution of step S2902. In FIG. 29, as an example, the predetermined time is 10 seconds.

Specifically, unless the switch 316 of the biometric authentication unit 307a detects the pressing of the rod 306a, the determination of whether or not the biometric authentication unit 307a has detected a press in step S2904 is a negative determination. Subsequently, in step S2908, the shop terminal payment unit 301 determines whether or not the elapsed time T1 has exceeded a predetermined time. Until either the determination in step S2904 is affirmative or the determination in step S2908 is affirmative, store terminal payment unit 301 continues to wait for detection of pressing of rod 306a.

When the switch 316 of the biometric authentication unit 307a detects the pressing of the rod 306a, in step S2904, the determination as to whether or not the pressing of the biometric authentication unit 307a has been detected is an affirmative determination. In this case, the processing in FIG. 29 proceeds to step S2906.

In step S2906, the shop terminal payment unit 301 transmits the approval information to the mobile terminal 2.

On the other hand, the mobile terminal settlement unit 203 according to the present embodiment waits for reception of information from the storefront terminal 3 when the determination in step S1910 of FIG. Specifically, whether or not the approval information is received from the storefront terminal 3 in step S3004 is affirmative, or whether or not non-approval information is received from the storefront terminal 3 is determined in the subsequent step S3006. The mobile terminal settlement unit 203 continues to wait for reception of information from the storefront terminal 3 until one of the determinations is satisfied.

When the mobile terminal settlement unit 203 receives the approval information from the storefront terminal 3, the determination in step S2604 becomes an affirmative determination. In this case, the processing in FIG. 30 proceeds to step S1912. The subsequent processing is the same as the processing of the first embodiment shown in FIGS.

Further, when the elapsed time T1 measured by the soft timer of the storefront terminal payment unit 301 exceeds 10 seconds, in step S2908, it is determined whether T1 has exceeded 10 seconds. In this case, the process in FIG. 29 proceeds to step S2910.

In step S2910, the shop terminal payment unit 301 transmits non-approval information to the mobile terminal 2, and displays a payment cancellation screen as a screen 302 on the display 38B.

FIG. 32 shows an example of the settlement cancellation screen. The inquiry screen includes a message display area 302b, a payment amount display area 302e, and an unapproved message display area 302g. In the settlement cancellation screen, the message display area 302b displays a message that the settlement has not been approved, the payment amount display area 302e displays the consideration (ie, the payment amount), and the non-approval message display area 302g displays the current transaction. A message prompting you to cancel the payment and prompting payment by other methods is displayed.

When the mobile terminal settlement unit 203 receives the non-approval information from the storefront terminal 3, the determination in step S2604 becomes a negative determination, and then the determination whether or not the non-approval information is received in step S2606 becomes a positive determination. In this case, the process in FIG. 30 ends.

FIG. 33 is a sequence diagram illustrating information exchange between the storefront terminal 3 and the mobile terminal 2 regarding the settlement processing according to the second embodiment of the present disclosure described above. Each step shown in FIG. 33 corresponds to each step in FIGS. For convenience of illustration, it should be noted that in FIG. 33, as in the sequence diagram of FIG. 27, branches existing during the settlement process are omitted.

In this embodiment, the elapsed time T1 from the time when the inquiry screen is displayed is measured. If the pressing of the rod 306a by the user is not detected even after the predetermined time has elapsed (for example, when T1 exceeds 10 seconds), the user considers that the current transaction has been rejected, and the process is performed without executing the settlement. finish.

According to the present embodiment, it is possible to prevent the settlement from being executed erroneously against the user's intention.

<Third Embodiment>
Next, a third embodiment of the present disclosure will be described. In addition, about the part which is the structure similar to 1st Embodiment, the same code | symbol is attached | subjected and description is abbreviate | omitted.

In the first embodiment and the second embodiment described above, the secondary storage device 24 of the mobile terminal 2 records only one vein data that can identify the owner of the individual account area 111. Correspondingly, the individual account area 111 of the account server 1 records single vein data.

Biological information for identifying an individual such as a vein pattern changes little by little due to aging or changes over time. If the degree of this change is slight, it can be covered by a known pattern recognition technique. However, if the registered pattern is very old from the viewpoint of the time scale of the change of the biometric information, the degree of change of the biometric information is large, so that the possibility of an authentication error increases. Here, specifically, the authentication mistake means that the authentication fails in the biometric authentication during the payment process even though the user who is the original owner of the mobile terminal 2 is executing the payment.
<System overview>

In the present embodiment, instead of one, a plurality of predetermined numbers of vein data are recorded in the individual account area 111 of the account server 1 and the secondary storage device 24 of the mobile terminal 2, and these plurality of vein data are in the process of settlement. Used for biometric authentication. The predetermined number will be described below as 5 as an example.

In the first and second embodiments described above, the vein data recorded in the specific individual account area 111 of the account server 1 is updated unless the user voluntarily performs an update operation. It was never done. On the other hand, the vein data recorded in the secondary storage device 24 of the portable terminal 2 has not been updated unless the user executes the charging process.

In the present embodiment, every time biometric authentication succeeds in the biometric authentication process in the settlement process, the image data captured by the image sensor 314 of the biometric authentication unit 307 of the storefront terminal 3 is transmitted to the mobile terminal 2 for secondary storage. Recorded in device 24. That is, every time biometric authentication succeeds in the payment process, the vein data recorded in the secondary storage device 24 of the mobile terminal 2 is updated with the latest imaging data.

Further, in the present embodiment, each time the personal authentication by the password is affirmed in the charge process, the vein data stored in the individual account area 111 of the account server 1 is stored in the currently stored five vein data of the mobile terminal 2. Of the 10 data including the 5 vein data recorded in the secondary storage device 24, the latest 5 are rewritten. That is, every time the personal authentication by the password is affirmed in the charging process, the vein data stored in the individual account area 111 of the account server 1 is updated to the latest one.

In the individual account area 111 of the account server 1 according to the present embodiment, five sets of vein data are registered in advance. By registering 5 sets instead of single data, for example, it is possible to absorb differences due to variations in finger positions during registration. Therefore, the user images the vein pattern five times in advance and registers each data as the first to fifth data. Each of the five sets of vein data is associated with data registration date and registration time information.

34 and 35 are flowcharts showing an example of a processing program for charging property data in this embodiment. FIG. 34 shows an example of a processing program executed by the mobile terminal charging unit 201, and FIG. 35 shows an example of a processing program executed by the account server charging unit 101.

The processing executed by the portable terminal charging unit 201 shown in FIG. 34 differs from the processing of the first embodiment shown in FIGS. 6 and 7 in that the data received in step S614 is a password request again. If the determination is NO, the process of steps S3402 to S3404 is executed instead of step S616, and the balance data and the five vein data are received from the account server 1 and stored in the secondary storage device 24. It is a point to record.

Further, the processing executed by the account server charge unit 101 shown in FIG. 35 corresponding to steps S3402 to S3404 of FIG. 34 is the same as the processing of the first embodiment shown in FIGS. Different. That is, if the determination whether the password received from the portable terminal 2 is correct in S806 is an affirmative determination, the process of steps S3502 to S3508 is executed instead of step S808, and the balance data and the updated data are updated. The latest five vein data are transmitted to the portable terminal 2.

Hereinafter, the description starts when the determination in step S806 in FIG. 35 (and FIG. 8) is affirmative. In this case, the processing in FIG. 35 proceeds to step S3502.

In step S3502, the account server charge unit 101 transmits a request for vein data to the mobile terminal 2.

When the mobile terminal charging unit 201 of the present embodiment receives a request for vein data from the account server 1, in step S 612 of FIG. 34 (and FIG. 6), a determination is made as to whether or not data has been received from the account server 1. It becomes. Subsequently, in step S614, the determination whether the received data is a password request again is negative. In this case, the process in FIG. 34 proceeds to step S3402.

In step S3402, the mobile terminal charging unit 201 transmits the five vein data recorded in the secondary storage device 24 to the account server 1.

In step S3504 in FIG. 35, the account server charge unit 101 receives five vein data from the portable terminal 2.

In step S3506, the account server charge unit 101 selects five sets with the newest data registration date and registration time from the current ten sets of vein data, and handles the selected five sets as new vein data. Are recorded in the individual account area 111 and the remaining five sets are deleted. Here, the current 10 sets of data include 5 sets of vein data stored in a specific individual account area 111 (specified by a password) owned by the user who is performing the charge process, and mobile data It consists of five sets of vein data received from the terminal 2.

In subsequent step S3508, account server charge unit 101 transmits the updated five vein data of individual account area 111 to portable terminal 2. Thereafter, the processing in FIG. 35 proceeds to step S902. The subsequent processing of the account server charge unit 101 is the same as the processing of the first embodiment shown in FIG.

34, the mobile terminal charging unit 201 receives the five vein data of the individual account area 111 updated from the account server 1 and records them in the secondary storage device 24. As a result, the five sets of vein data recorded in the specific individual account area 111 of the account server 1 and the five sets of vein data recorded in the secondary storage device 24 of the mobile terminal 2 are synchronized.

Thereafter, the processing of FIG. 34 proceeds to step S702. The subsequent processing of the portable terminal charging unit 201 is the same as the processing of the first embodiment shown in FIG.

With respect to the charge processing according to the third embodiment of the present disclosure described above, FIG. 36 is a sequence diagram illustrating information exchange between the mobile terminal 2 and the account server 1. Each step shown in FIG. 36 corresponds to each step in FIGS. For convenience of illustration, it should be noted that in FIG. 36, as in the sequence diagram of FIG. 15, branches existing during the charge process are omitted.

<Payment processing>
The settlement process of this embodiment is different from the process of the first embodiment only in the authentication process that is the second stage of the entire settlement process. Therefore, only the authentication process will be described below.

[Authentication process subroutine]
The authentication process in the settlement process of the present embodiment is illustrated in FIGS. 37 and 38 as a subroutine. FIG. 37 is a subroutine showing an example of a processing program executed by the CPU 30 as the shop terminal payment unit 301, and FIG. 38 is a subroutine showing an example of a processing program executed by the CPU 20 as the mobile terminal payment unit 203.

37. In step S3702 of FIG. 37, the storefront terminal settlement unit 301 substitutes 0 for a variable G stored in the secondary storage device 34. As described in the first embodiment, G is a binary variable representing success or failure of authentication in the storefront terminal payment unit 301.

Subsequently, the storefront terminal payment unit 301 transmits a request for vein data to the mobile terminal 2 in step S1804 as in the first embodiment.

Upon receipt of the vein data request from the storefront terminal 3, the mobile terminal settlement unit 203 of this embodiment starts an authentication process subroutine (START in FIG. 38). Similarly to the first embodiment, in step S2002, the mobile terminal settlement unit 203 substitutes 0 for a variable H stored in the secondary storage device 24.

In subsequent step S3802, the mobile terminal settlement unit 203 reads the requested five vein data from the secondary storage device 24 and transmits it to the store terminal 3. Note that, in step S3802 of FIG. 38, five sets of vein data are transmitted to the storefront terminal 3, unlike S2004 of the first embodiment shown in FIG.

37, the shop terminal payment unit 301 receives five vein data from the portable terminal 2 and records them in the secondary storage device 34. Note that, in step S3704 of FIG. 37, five sets of vein data are received from the portable terminal 2 unlike S1806 of the first embodiment shown in FIG.

In subsequent step S1808, as in the first embodiment, the storefront terminal settlement unit 301 captures the contact object in contact with the finger guide 310 in the biometric authentication unit 307 and records the captured data in the secondary storage device 34. To do. Thereafter, the processing in FIG. 37 proceeds to step S3706.

In step S3706, the shop terminal payment unit 301 substitutes 1 for a variable I stored in the secondary storage device.

Here, I is a natural number representing the number of authentication attempts and an ordinal number indicating each of the five sets of vein data received from the mobile terminal 2 in S3704. That is, I = 1 indicates the first set of vein data, and similarly, I = 2, 3, 4, and 5 indicate the second to fifth sets, respectively. In this embodiment, five sets of vein data are used as an example. Therefore, in the flow shown in FIG. 37, when the variable I becomes 6, it is determined that the authentication has failed in step S3714 described later. .

The natural number I as an ordinal number is assigned to 5 sets of vein data in the order of registration. Therefore, the first set of vein data is vein data registered at the latest time, and the fifth set is vein data registered at the oldest time.

Note that the integer I has a different meaning from the variable F, which is an integer representing the number of authentication attempts in the processing of the first embodiment shown in FIG. F indicates the number of times step S1808 is repeated in the process of FIG. That is, F indicates the number of times the biometric authentication unit 307 has created the imaging data. However, in the process of the present embodiment shown in FIG. 37, the execution of step S1808 is not repeated, and imaging data is created only once.

In step S3708, the shop terminal payment unit 301 reads the image data captured by the image sensor 314 and the I-th vein data from the secondary storage device 34, and compares the vein patterns included in the two data. In subsequent step S3710, store terminal settlement unit 301 adds 1 to variable I stored in secondary storage device 34. For example, after the first authentication, since I = 1 is recorded in the secondary storage device 34 in step S3706, the variable I = 2 is newly added to the secondary storage device 34 by adding 1 in S3710. To be recorded.

If the vein patterns included in the two data match as a result of the collation, the determination of whether or not the two patterns match (that is, whether or not the current user is the user) is affirmative in step S1812. Judgment. In this case, the process in FIG. 37 proceeds to step S3712.

In step S3712, the shop terminal payment unit 301 transmits the authentication success information and the imaged data imaged in S1808 to the mobile terminal 2. Then, the storefront terminal payment unit 301 holds G = 0 (that is, authentication success) and ends the authentication process subroutine (RETURN in FIG. 37).

On the other hand, if the vein patterns included in the two data do not match as a result of the collation in S3708, the determination in step S1812 is negative. In this case, the process in FIG. 37 proceeds to step S3714.

In step S 3714, it is determined whether or not I = 6 for the variable I recorded in the secondary storage device 34 of the storefront terminal 3. A value of I = 6 means that the fifth authentication, which is the maximum number of biometric authentication attempts in the process of FIG. 37, has already been completed.

If I is smaller than 6, the determination in step S3714 is a negative determination. In this case, the process in FIG. 37 returns to step S3708.

Unless the determination in step S1812 is affirmative, the above processes in steps S3708 to S3714 are repeated. That is, the comparison / collation between the imaging data and the I-th vein data is repeated. Each time collation is executed in step S3708, 1 is added to variable I in step S3710.

In the process of repeating the process as described above, if I = 6 is confirmed, the determination in step S3714 is an affirmative determination. In this case, authentication has already failed for all five sets of vein data, and biometric authentication failure in this embodiment is confirmed.

In this case, the processing in FIG. 37 proceeds to step S1822. In step S 1822, the storefront terminal payment unit 301 transmits authentication failure information to the mobile terminal 2. Subsequently, in step S1824, the shop terminal payment unit 301 substitutes 1 for a variable G recorded in the secondary storage device 34, holds G = 1 (that is, authentication failure), and ends the authentication process subroutine. (RETURN in FIG. 37).

Similar to the first embodiment, the subroutine executed by the storefront terminal settlement unit 301 shown in FIG. 37 transmits authentication success information or authentication failure information to the mobile terminal 2 in step S3713 or S1822, and also uses a secondary storage device. For the variable G recorded in 34, G = 0 (corresponding to authentication success) or G = 1 (corresponding to authentication failure) is given, and the process is terminated.

On the other hand, after transmitting five vein data to the storefront terminal 3 in step S3802 of FIG. 38, the mobile terminal settlement unit 203 waits for the result of the authentication process to be transmitted from the storefront terminal 3.

The subsequent process executed by the mobile terminal settlement unit 203 is substantially the same as the process of the first embodiment shown in FIG. 20, but is different only when the determination in step S2006 is an affirmative determination.

That is, when the mobile terminal settlement unit 203 receives the authentication success information from the storefront terminal 3 within a predetermined time, the determination in step S2006 is an affirmative determination. In this case, the processing in FIG. 38 proceeds to step S3804.

In step S3804, the mobile terminal settlement unit 203 receives the imaging data transmitted from the storefront terminal 3 in step S3712 of FIG. For convenience of explanation, in FIG. 38, reception of authentication success information and reception of imaging data are shown as separate steps. However, the authentication success information and the imaging data transmitted from the storefront terminal 3 in step S3712 are actually received by the mobile terminal settlement unit 203 at a time.

In the following step S3806, the mobile terminal settlement unit 203 deletes one set with the oldest registration time from the five sets of vein data recorded in the secondary storage device 24, and uses the imaging data received from the storefront terminal 3 as the received data. The replacement and authentication process subroutine ends (RETURN in FIG. 38).

As in the first embodiment, the subroutine executed by the mobile terminal settlement unit 203 shown in FIG. 38 is H = 0 (corresponding to authentication success) or H for the variable H recorded in the secondary storage device 24. = 1 (corresponding to authentication failure) is given and the process ends.

When G = 0 is obtained for the in-store terminal settlement unit 301 as a result of the authentication process subroutine, H = 0 is obtained for the mobile terminal settlement unit 203, and G = 1 is obtained for the over-the-counter settlement unit 301. As in the first embodiment, H = 1 is obtained for the mobile terminal settlement unit 203.

Furthermore, in the portable terminal 2 of the present embodiment, when H = 0 (corresponding to authentication success) is held and the authentication process subroutine ends, the most of the five vein data recorded in the secondary storage device 24 It should be noted that the old set is replaced with image data captured by the biometric authentication unit 307 of the storefront terminal 3.

Therefore, every time biometric authentication succeeds in the settlement processing of this embodiment, 5 sets of vein data recorded in the secondary storage device 24 of the portable terminal 2 and the individual account area 111 of the account server 1 are stored. There is a discrepancy between the 5 sets of vein data. However, this discrepancy does not pose a problem when executing the settlement process of this embodiment. This is because the settlement process of the present embodiment is performed between the mobile terminal 2 and the storefront terminal 3, and data held in the account server 1 is not interposed.

On the other hand, the above-described inconsistency is caused by the execution of step S3506 in FIG. 35 and step S3404 in FIG. 34 in the charge processing of the present embodiment, so that the five sets recorded in the specific individual account area 111 of the account server 1 The vein data and the five sets of vein data recorded in the secondary storage device 24 of the portable terminal 2 are synchronized to eliminate the vein data.

FIG. 39 is a sequence diagram showing exchange of information between the storefront terminal 3 and the portable terminal 2 regarding the settlement processing according to the third embodiment of the present disclosure described above. Each step shown in FIG. 39 corresponds to each step in FIGS. For convenience of illustration, it should be noted that in FIG. 39, as in the sequence diagram of FIG. 27, branches existing during the settlement process are omitted.

<Update of vein data>
Hereinafter, the update of vein data in the mobile terminal 2 and the account server 1 will be described again. In FIG. 40, an example of the update relationship of the vein data in the portable terminal 2 and the account server 1 is shown.

It is assumed that five types of vein data are registered in advance in a specific individual account area 111 of the account server 1. The registration date is as follows.
A1: Registration on April 2 at 15:00 A2: Registration on April 2 at 15:05 A3: Registration on April 2 at 15:10 A4: Registration on April 5 at 11:00 A5: Registration on April 5 11:05 registration

For example, the user accesses a specific individual account area 111 of the account server 1 remotely via the network 4 on April 2 using a bank dedicated terminal or the like, and registers A1 to A3. It is assumed that the individual account area 111 is accessed again every day to register A4 and A5.

At 11:10 on April 6, the user connects the mobile terminal 2 to the account server 1 and performs the first charging process. In the process of executing the charging process, the vein pattern data of A1 to A5 is downloaded from the account server 1 to the portable terminal 2 and recorded in the secondary storage device 24 in step S3404 shown in FIG.

Next, at 13:20 on April 6, the user performs the first shopping and pays the price by settlement using property data charged in the mobile terminal 2. In the process of executing the payment process, in step S3806 shown in FIG. 38, the oldest A1 is deleted from the secondary storage device 24 of the portable terminal 2 and is imaged by the biometric authentication unit 307 of the storefront terminal 3 instead. The imaging data is registered in the portable terminal as A6. On the other hand, the vein pattern data recorded in the corresponding individual account area 111 of the account server 1 does not change.

The vein data of the account server 1 is updated at 15:30 on April 8. The user accesses the individual account area 111 of the account server 1 and registers the data B1 at some occasion, or the user executes a charge process for another portable terminal 2a and is recorded in the portable terminal 2a. It is assumed that B1 is selected as one of the new individual account data in step S3506 shown in FIG. In any case, the vein pattern data B1 is newly registered in the account server 1, and A1 is deleted. On the other hand, the vein pattern data recorded in the secondary storage device 24 of the portable terminal 2 does not change.

At 10:30 on April 15, the user performs the second shopping and pays the price by settlement using property data charged in the mobile terminal 2. In the process of executing the payment process, in step S3806 shown in FIG. 38, the oldest A2 is deleted from the secondary storage device 24 of the portable terminal 2, and is imaged by the biometric authentication unit 307 of the storefront terminal 3 instead. The imaging data is registered in the portable terminal as A7. On the other hand, the vein pattern data recorded in the corresponding individual account area 111 of the account server 1 does not change.

At 15:00 on April 15, the user connects the mobile terminal 2 to the account server 1 and performs the second charging process. In the process of executing the charging process, in step S3506 shown in FIG. 35, the account server 1 records the five vein data recorded in the individual account area 111 and the secondary storage device 24 of the portable terminal 2. Each of the five vein data that has been stored is compared, and five sets of data are selected from the most recently registered data, and the other five sets of data are deleted. As a result, A7, B1, A6, A5, and A4 remain in the individual account area 111 of the account server 1 in order from the newest one. In step S3506 shown in FIG. 35, the account server 1 transfers this information to the mobile terminal 2, and as a result, in step S3404 of FIG. Will be synced to

The same processing is performed for the other mobile terminals 2a, 2b, 2c, etc. owned by the user in addition to the mobile terminal 2. As a result, the latest vein data is always recorded in the account server 1 for the vein data as biometric information for specifying the user, and is synchronized with the portable terminal 2 during the charge process.

Note that the date and time of registration described here is an example for showing the context.

In this embodiment, the account server charge unit 101 transmits a vein data request to the mobile terminal 2 in step S3502, receives five vein data recorded in the mobile terminal 2 in step S3504, and performs step S3506. Thus, the new and old relationships of the total 10 vein data are judged, the new 5 vein data are left, and the others are deleted. However, the account server charge unit 101 receives not only the vein data itself from the mobile terminal 2 but only the data indicating the anteroposterior relationship of each vein data, such as the registration date, and then determines the new / old relationship based on the data, and then necessary Only the vein data may be requested from the portable terminal 2 and received.

According to the present embodiment, biometric authentication can always be performed using the latest vein data, so that it is possible to prevent an authentication error from occurring during biometric authentication during settlement processing.

<Fourth embodiment>
Next, a fourth embodiment of the present disclosure will be described. In addition, about the part which is the structure similar to 1st Embodiment, the same code | symbol is attached | subjected and description is abbreviate | omitted.

In the first to third embodiments described above, the result of biometric authentication during the settlement process is either authentication success or authentication failure. However, in pattern recognition, it is well known to calculate a similarity indicating the degree of similarity as a result of comparison / collation of two images. .

In this embodiment, in the biometric authentication process in the settlement process, the similarity between the imaging data and the vein data is calculated, and the maximum number of trials that can be authenticated is set according to the similarity.

<System overview>
In the present embodiment, as in the third embodiment, a plurality of predetermined number of vein data is recorded in the individual account area 111 of the account server 1 and the secondary storage device 24 of the portable terminal 2, and the plurality of vein data is recorded. Is used for biometric authentication during the payment process. The predetermined number will be described below as 5 as an example.

[Authentication process subroutine]
The authentication process in the settlement process of this embodiment is shown in FIG. 41 as a subroutine. FIG. 41 is a subroutine showing an example of a processing program executed by the storefront terminal payment unit 301.

In this embodiment, the processing program executed by the mobile terminal settlement unit 203 is the same as the authentication process subroutine of the first embodiment shown in FIG. More precisely, in step S2004 of the processing program executed by the mobile terminal settlement unit 203 of the present embodiment, the mobile terminal settlement unit 203 transmits five sets of vein data to the store terminal 3 instead of one. Different from the embodiment.

41. In step S4102, the storefront terminal payment unit 301 substitutes 0 for a variable G stored in the secondary storage device 34. As described in the first embodiment, G is a binary variable representing success or failure of authentication in the storefront terminal payment unit 301.

In step S4104, the shop terminal payment unit 301 receives five vein data from the portable terminal 2 and records them in the secondary storage device 34. Subsequently, the processing of FIG. 41 proceeds to step S1808.

In step S 1808, as in the first embodiment, the storefront terminal payment unit 301 uses the biometric authentication unit 307 to image a contact object that is in contact with the finger guide 310 and records the image data in the secondary storage device 34. . Thereafter, the processing in FIG. 41 proceeds to step S4106.

In step S4106, the shop terminal payment unit 301 substitutes 0 for a variable I stored in the secondary storage device 34. The significance of the variable I is as described in the third embodiment.

In step S4108, the storefront terminal settlement unit 301 reads the image data captured by the image sensor 314 and the I-th vein data from the secondary storage device 34, compares the vein patterns included in the two data, and is similar. While calculating the degree, 1 is added to the variable I.

Note that, as the execution result of step S4108 of this embodiment, a pattern similarity or a mismatch is not obtained as in the first to third embodiments, but a quantitative similarity is calculated. I want to be. As an example, the description will be made assuming that the similarity is expressed in%.

In step S4110, the shop terminal payment unit 301 determines whether I is 1. If it is after the first authentication, since I = 0 is substituted in step S4106 and 1 is added to I in step S4108, I = 1 holds. If the determination in step S4110 is affirmative, the process in FIG. 41 proceeds to step S4114.

In step S4114, the shop terminal payment unit 301 determines whether or not the similarity obtained as a result of the execution of step S4108 is 90% or more. If the determination in step S4114 is affirmative, the process in FIG. 41 proceeds to step S1814.

In step S1814, the storefront terminal payment unit 301 transmits authentication success information to the mobile terminal 2. Then, the storefront terminal payment unit 301 holds G = 0 (that is, authentication success) and ends the authentication process subroutine (RETURN in FIG. 41).

On the other hand, if the similarity obtained as the execution result of step S4108 is less than 90%, the determination in step S4114 is negative. In this case, the process in FIG. 41 proceeds to step S4116.

In step S4116, the shop terminal payment unit 301 determines whether the similarity obtained as an execution result of step S4108 is 60% or more. If the determination in step S4116 is affirmative, the process in FIG. 41 proceeds to step S4120.

In step S4120, the shop terminal payment unit 301 substitutes 3 for the variable J stored in the secondary storage device. Subsequently, the processing of FIG. 41 proceeds to step S4126.

The variable J is a natural number representing the maximum number of authentication attempts in the present embodiment. In the present embodiment, the vein data is set to 5 sets as an example, and therefore the variable J does not take a value of 6 or more.

When the degree of similarity is 60% or more and less than 90%, it is assumed that the degree of change in biological information is small. Therefore, it is considered sufficient to perform biometric authentication at most three times.

On the other hand, if the similarity obtained as a result of the execution of step S4108 is less than 60%, the determination in step S4116 is negative. In this case, the processing in FIG. 41 proceeds to step S4118.

In step S4118, the shop terminal payment unit 301 determines whether the similarity obtained as an execution result of step S4108 is 30% or less. If the determination in step S4118 is a negative determination, the process in FIG. 41 proceeds to step S4122.

In step S412, the storefront terminal payment unit 301 substitutes 5 for a variable J stored in the secondary storage device. Subsequently, the processing of FIG. 41 proceeds to step S4126.

When the degree of similarity is 30% or more and less than 60%, it is assumed that the degree of change in biological information is large. Therefore, biometric authentication is set so that it can be performed a maximum of five times so that all five sets of vein data can be used.

On the other hand, if the similarity obtained as the execution result of step S4108 is less than 30%, the determination in step S4118 is affirmative. In this case, the process in FIG. 41 proceeds to step S4128.

If the degree of similarity is less than 30%, it is assumed that the degree of change in biometric information is too large to perform effective authentication, or that the user executing the payment process is not the original owner. . Therefore, in this case, authentication failure is confirmed.

In step S4128, the storefront terminal payment unit 301 transmits the authentication failure information to the mobile terminal 2, and substitutes 1 for a variable G recorded in the secondary storage device 34, so that G = 1 (that is, authentication failure). And the authentication process subroutine is terminated (RETURN in FIG. 41).

In step S4126, it is determined whether or not I = J for the variable I recorded in the secondary storage device 34 of the storefront terminal 3. Specifically, when the degree of similarity is 60% or more and less than 90%, J is set to 3 in step S4120, and therefore it is determined whether I = 3. If the degree of similarity is less than 60% and greater than 30%, J is set to 5 in step S4122, and therefore it is determined whether I = 5.

Since I = 1 after the first authentication, the determination in step S4126 is a negative determination. In this case, the process of FIG. 41 returns to step S4108.

In step S4108, the second and subsequent authentications are executed, and when 1 is added to I and the similarity is newly calculated, since I is 2 or more, the determination in step S4110 is negative. In this case, the process in FIG. 41 proceeds to step S4112.

In step S4112, it is determined whether or not the most recently calculated similarity is 80% or more. If the determination in step S4112 is affirmative, the process in FIG. 41 proceeds to step S1814 described above.

Unless the determination in step S4112 is affirmative, the processes in steps S4108, S4110, S4112, and S4126 are repeated. That is, the calculation of the similarity is repeated by comparing the imaging data with the I-th vein data. Each time collation is performed in step S4108, 1 is added to the variable I.

In the process of repeating the process as described above, if I = J is confirmed, the determination in step S4126 is affirmative. In this case, authentication of the maximum number of trials set based on the similarity calculated in the initial authentication has already been completed, and biometric authentication failure in this embodiment is confirmed.

In this case, the processing in FIG. 41 proceeds to step S4128. As described above, in step S4128, the shop terminal payment unit 301 transmits the authentication failure information to the mobile terminal 2 and substitutes 1 for the variable G recorded in the secondary storage device 34, so that G = 1 (that is, , Authentication failure) and the authentication process subroutine ends (RETURN in FIG. 41).

Similar to the first embodiment, the subroutine executed by the storefront terminal payment unit 301 shown in FIG. 41 transmits authentication success information or authentication failure information to the mobile terminal 2 in step S1814 or S4128, and also uses a secondary storage device. For the variable G recorded in 34, G = 0 (corresponding to authentication success) or G = 1 (corresponding to authentication failure) is given, and the process is terminated.

In the payment processing according to the fourth embodiment of the present disclosure, the exchange of information between the devices is illustrated in FIG. 27 except that five vein data are transmitted from the mobile terminal 2 to the store terminal 3. This is the same as in the first embodiment. Therefore, the sequence diagram regarding the payment processing according to the fourth embodiment of the present disclosure is omitted.

In the present embodiment, in the biometric authentication process during the settlement process, calculation is performed using the latest data (that is, I = 1) among the five sets of vein data recorded in the secondary storage device 24 of the mobile terminal 2. By setting the maximum number of trials at which authentication can be performed according to the initial similarity, efficient authentication can be performed.

In the first to fourth embodiments of the present application, the biometric information used in the biometric authentication process in the settlement process is a finger vein pattern of a predetermined hand of an individual who is an owner of a financial institution account. explained. However, the biometric information used in the biometric authentication process in the present disclosure is not limited to the finger vein pattern of the hand. For example, any biometric information such as a fingerprint of a finger, a palm print, a voice print, and a face image can be used as long as an individual can be identified and authenticated. In that case, the storefront terminal 3 of the present disclosure includes a biometric authentication device appropriately configured according to target biometric information, instead of the biometric authentication unit 307. Specifically, a voice authentication device that performs voice recognition on a voice print, an image authentication device that executes image recognition on a fingerprint of a finger, a palm print, or a face image.

Furthermore, authentication during the settlement process of the present disclosure is not necessarily limited to biometric authentication. For example, any identification information such as name, address, and password can be used as long as an individual can be identified and authenticated. In that case, the storefront terminal 3 according to the present disclosure includes an authentication device appropriately configured according to target identification information, instead of the biometric authentication unit 307. Specifically, a character string authentication apparatus that performs character string recognition for a name, an address, a password, and the like.

DESCRIPTION OF SYMBOLS 1 Account server 2 Portable terminal 3 Shop front terminal 4 Network 5 Human body 14 Secondary storage device 20 CPU
22 Primary storage device 24 Secondary storage device 26 Bus 28 Touch panel display 28A Touch panel 28B Display 30 CPU
32 Primary storage device 34 Secondary storage device 36 Bus 38 Touch panel display 38A Touch panel 38B Display 42A External I / F
42B External I / F
44A External I / F
44B External I / F
101 Account Server Charge Unit 111 Individual Account Area 201 Mobile Terminal Charge Unit 203 Mobile Terminal Settlement Unit 301 Store Terminal Settlement Unit 306 Transmit / Receive Unit 306a Rod 307 Biometric Authentication Unit 307a Biometric Authentication Unit 310 Finger Guide 311 Transparent Window 313 Lens 314 Image Sensor 316 Switch

Claims

An authentication unit that performs user authentication,
A first communication unit that receives property data when the personal authentication is affirmed;
A property data receiving device.
An acquisition unit for acquiring the first identification data of the user;
The first communication unit is configured to further receive second identification data of the user;
The authentication unit executes the personal authentication using the acquired first identification data and the received second identification data.
The property data receiving apparatus according to claim 1.
The first identification data and the second identification data are biological data of the user.
The property data receiving apparatus according to claim 2.
The biological data is human body data indicating physical characteristics of the user.
The property data receiving apparatus according to claim 3.
The human body data is vein data indicating veins in the body,
The property data receiving apparatus according to claim 4.
The first communication unit receives the second identification data as the human body data via a predetermined part of the user's body,
The human body data is neighboring human body data indicating characteristics in the vicinity of the predetermined part.
The property data receiving apparatus according to claim 4.
When the first communication unit comes into contact with the predetermined part of the user's body, the acquisition unit acquires the first identification data as the nearby human body data of the predetermined part.
The property data receiving apparatus according to claim 6.
The first communication unit includes a switching unit that performs switching between a first state in which reception of property data is not executable and a second state in which transmission of property data is executable.
The property data receiving apparatus according to any one of claims 1 to 7.
The first communication unit receives a plurality of the second identification data,
The authentication unit performs the personal authentication by comparing the first identification data with the plurality of received second identification data,
The first communication unit transmits the first identification data when the personal authentication is successful.
The property data receiving apparatus according to any one of claims 2 to 7.
The first communication unit receives the plurality of second identification data in order,
The authentication unit performs the identity authentication by comparing the first identification data with the plurality of received second identification data,
Based on the result of collation between the first identification data and the first identification data, the authentication unit determines how many of the second identification data are used to perform the personal authentication. decide,
The property data receiving apparatus according to any one of claims 2 to 7.
A property data transmitting device that communicates with the property data receiving device according to claim 1,
A second communication unit that transmits the property data when the personal authentication is affirmed;
Property data transmission device.
A third communication unit for receiving the property data;
At least a part of the property data received in the third communication unit is transmitted in the second communication unit;
The property data transmitting apparatus according to claim 11.
The property data receiving device according to any one of claims 1 to 10,
The property data transmitting device according to claim 11 or 12,
Including property data transmission / reception system.
Perform user authentication,
Receiving property data when the identity verification is affirmed;
Property data reception method.
A property data transmission / reception method using a store side device and a user side device,
In store side equipment,
Get the user's first identification data,
Receiving the second identification data of the user from the user side device;
Using the acquired first identification data and the received second identification data to perform user authentication,
On the user side device,
Property data and the second identification data are recorded in advance,
When the identity authentication is affirmed, the property data is transmitted to the store side device.
Property data transmission / reception method.
On the computer,
Perform user authentication,
Receiving property data when the identity verification is affirmed;
To execute a process that includes
program.